Hi folks,
I installed the panda-quantal_developer_20130128-58.img.gz on an old Pandaboard A1 and apt-get update got a new kernel and have overwritten the preEnv.txt boot=UUID=...hash... into boot=UUID=rootfs, only that rootfs is not a device.
It fell back to busybox saying couldn't find root, so I re-wrote the file to have the correct UUID and it booted correctly.
Not sure anyone has seen this, but seems like a simple bug to fix...
cheers, --renato
Hi Renato,
On 29 March 2013 15:28, Renato Golin renato.golin@linaro.org wrote:
Hi folks,
I installed the panda-quantal_developer_20130128-58.img.gz on an old Pandaboard A1 and apt-get update got a new kernel and have overwritten the preEnv.txt boot=UUID=...hash... into boot=UUID=rootfs, only that rootfs is not a device.
It fell back to busybox saying couldn't find root, so I re-wrote the file to have the correct UUID and it booted correctly.
Not sure anyone has seen this, but seems like a simple bug to fix...
I haven't seen that before but it should be easy to reproduce.
btw, we don't ship images with preEnv.txt but boot.txt/scr instead. When the kernel is updated, flash-kernel is called and should update the UUID. The rootfs is mounted by default using UUID but you can mount by label: root=LABEL=rootfs
It seems something wrong is happening with flash-kernel...
Oh, one more thing, and that's not specific to this image, but to many Linaro images I tried.
The ports.ubuntu.com/ubuntu-ports Apt source is on both sources.list and sources.list.d, yielding an error of duplicated entries.
I just removed the sources.list (since it was the only entry) and all went well.
cheers, --renato
On 29 March 2013 14:14, Fathi Boudra fathi.boudra@linaro.org wrote:
Hi Renato,
On 29 March 2013 15:28, Renato Golin renato.golin@linaro.org wrote:
Hi folks,
I installed the panda-quantal_developer_20130128-58.img.gz on an old
Pandaboard A1 and apt-get update got a new kernel and have overwritten the preEnv.txt boot=UUID=...hash... into boot=UUID=rootfs, only that rootfs is not a device.
It fell back to busybox saying couldn't find root, so I re-wrote the
file to have the correct UUID and it booted correctly.
Not sure anyone has seen this, but seems like a simple bug to fix...
I haven't seen that before but it should be easy to reproduce.
btw, we don't ship images with preEnv.txt but boot.txt/scr instead. When the kernel is updated, flash-kernel is called and should update the UUID. The rootfs is mounted by default using UUID but you can mount by label: root=LABEL=rootfs
It seems something wrong is happening with flash-kernel...
-
Fathi Boudra -
Renato Golin