On Tue, Feb 01, 2011 at 09:23:38PM +0100, Michael Opdenacker wrote: > On 02/01/2011 03:50 PM, Robert Nelson wrote: > > On Tue, Feb 1, 2011 at 8:11 AM, Avik Sil <avik....@linaro.org> wrote: > >> After trying all the suggestions finally I had to resort to linaro kernel > >> packaging (https://wiki.linaro.org/PackageYourOwnKernel) to deploy the > >> kernel which gave me the maximum sane output, but still failed to get the > >> shell: http://paste.ubuntu.com/560935/
> >> I tried disabling UUID validation as given in > >> https://wiki.linaro.org/Mentoring/KernelDeploy, but that too did not help. > > you might still have the reference to that uuid in /etc/fstab that > > it's tripping over.. > Mmm, the log suggests that you are still using an initrd (initramfs indeed). > Another possibility is a bootcmd setting in U-boot that says > "root=UUID=xxxxxxx". > Before running "run bootcmd", you may display the value of 'bootcmd' and > replace the 'root=UUID=xxxxxxx" setting by "root=/dev/mmcblk0p2". > Ubuntu's initramfs scripts use /proc/cmdline to find out which root > filesystem to mount. This should fix your problem. I've poked around at this with Avik; the problem seems to be that the omap2plus_defconfig doesn't enable the driver for the MMC interface by default. Note that this root=UUID= line is set by linaro-media-create using the UUID of the newly-created root filesystem; it would be quite unusual for the fs UUID to change. All the same, we've ruled this out now. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
