Sebastian Rode wrote:
>  Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in advance.
>
>   
Hi.  This is a bug I have found a work around for.  The problem is that 
the bootloader insists on putting something like 
root=UUID=a8cke9d;l5dfl;ksdjdsfo83tljas,
instead of something my system can understand like root=/dev/hda1.
I can get around the problem, but its annoying that I have to.   Also 
note that simply putting 'root=/dev/hda1' in the kopt line of menu.conf 
doesn't solve the problem, as update-grub rewrites the kopt line (back 
to root=UUID=a8cke9d;l5dfl;ksdjdsfo83tljas), and the system, when 
booting, cannot find device a8cke9d;l5dfl;ksdjdsfo83tljas.

Thanks,
Bob

-- 
feisty final does not boot
https://bugs.launchpad.net/bugs/108633
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to