The computer has many linux partition. It has one main Linux (ubuntu 6.06) partition which is the ONLY ONE having grub installed. Feisty was installed in a separate parition. During feisty installation, grub installation was skipped BUT the dialog box indicated to boot feisty from /dev/sdb7. I added the following grub entry which worked fine (note it's 2.6.20-12);
Grub Parameters for that kernel;
title Ubuntu 7.04 Hdb7, kernel 2.6.20-12
root (hd1,6)
kernel /boot/vmlinuz-2.6.20-12-generic root=/dev/sdb7 ro vga=0x31A
initrd /boot/initrd.img-2.6.20-12-generic
boot
I always used /dev/hdb7 in previous linux installed I found strange to use /dev/sdb7 but someone indicated that feisty was using /dev/sdbNN because of the new libpata... Feisty was running fine with the grub entry above. Trying to use root=/dev/hdb7 with feisty kernel 2.6.20-12 was not working.
Then during one feisty update, kernel 2.6.20-13 was installed. Feisty kernel upgrade couldn't update the grub entry above since it's in another linux partition. I had to manually update the grub entry above entry by changing 2.6.20-12 by 2.6.20-13 and leaving root=/dev/sdb7.
When booting this new 2.6.20-13, the kernel hang at "Uniform CD-ROM drive Revision: 3.20" and I raised the problem in launchpad.
After some more experientation with Linux Kernel SysRequest debuggin feature. I have been able to see the message like "couldn't find /dev/sdb7". I then tried to update the grub entry to pass root=/dev/hdb7. Since then the kernel 2.6.20-13 is working as expected.
I do not know if the other people on IRC who indicated that they had the problem, where kernel stop at CD-ROM line, were also using root=/dev/sdbNN instead of root=/dev/hdbNN in their grub menu.lst. Is this something that has changed between kernel 2.6.20-12 and 2.6.20-13?
P.S> I would have liked in first place that during feisty install, when skipping the grub installation, the ubuntu installation should write a sample grub menul.lst file in /root updated for the system being installed.
thanks
Is there any information that could be usefull for you?
The computer has many linux partition. It has one main Linux (ubuntu 6.06) partition which is the ONLY ONE having grub installed. Feisty was installed in a separate parition. During feisty installation, grub installation was skipped BUT the dialog box indicated to boot feisty from /dev/sdb7. I added the following grub entry which worked fine (note it's 2.6.20-12); 2.6.20- 12-generic root=/dev/sdb7 ro vga=0x31A img-2.6. 20-12-generic
Grub Parameters for that kernel;
title Ubuntu 7.04 Hdb7, kernel 2.6.20-12
root (hd1,6)
kernel /boot/vmlinuz-
initrd /boot/initrd.
boot
I always used /dev/hdb7 in previous linux installed I found strange to use /dev/sdb7 but someone indicated that feisty was using /dev/sdbNN because of the new libpata... Feisty was running fine with the grub entry above. Trying to use root=/dev/hdb7 with feisty kernel 2.6.20-12 was not working.
Then during one feisty update, kernel 2.6.20-13 was installed. Feisty kernel upgrade couldn't update the grub entry above since it's in another linux partition. I had to manually update the grub entry above entry by changing 2.6.20-12 by 2.6.20-13 and leaving root=/dev/sdb7.
When booting this new 2.6.20-13, the kernel hang at "Uniform CD-ROM drive Revision: 3.20" and I raised the problem in launchpad.
After some more experientation with Linux Kernel SysRequest debuggin feature. I have been able to see the message like "couldn't find /dev/sdb7". I then tried to update the grub entry to pass root=/dev/hdb7. Since then the kernel 2.6.20-13 is working as expected.
I do not know if the other people on IRC who indicated that they had the problem, where kernel stop at CD-ROM line, were also using root=/dev/sdbNN instead of root=/dev/hdbNN in their grub menu.lst. Is this something that has changed between kernel 2.6.20-12 and 2.6.20-13?
P.S> I would have liked in first place that during feisty install, when skipping the grub installation, the ubuntu installation should write a sample grub menul.lst file in /root updated for the system being installed.
thanks
Is there any information that could be usefull for you?