I am building a complet boot/kernel/rootfs using the last Buildroot Release: 08-2016. My board is SAM9G25EK.
Under buildroot, I use the at91sam9x5ek_defconfig to generate images. I just change the uboot env to make it read the device tree before reading kernel and booting it. The "/dev management" is set to "Dynamic using devtmpfs only" (default).
On boot, no error displayed. Everything seems ok.
I need to change "/dev management" to "Dynamic using devtmpfs + eudev" (to use Atmel Wifi Card: https://github.com/linux4sc/wireless-dr ... e-for-WiFi). After new generation, the following errors are displayed:
Code: Select all
udevd: starting eudev-3.2 UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16 UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
I made a "touch test" and "sync". After reboot, the file is still there. So rootfs is working.
Any idea what could be those errors?