Public bug reported:
Binary package hint: grub
Hello, I should start by saying that I'm not entirely sure whether or
not this is a grub issue, so please walk me through this. This is the
best package to file the bug under that I could think of, though.
I'm on a Dell E1505 laptop from about three and a half years ago. Core
Duo CPU, ATI X1400 Mobility graphics, 2 GB RAM, etc. Up until this
point, clean installs of Ubuntu have worked flawlessly.
Initially, I upgraded to Ubuntu 9.10 via an upgrade, but did not like
the result. I went back and did a clean install, so my issue occurs on
a CLEAN INSTALL.
When selecting "Ubuntu, Linux 2.6.31-14-generic" after a successful
install (yes, the computer boots to a live CD or flash drive
successfully), the computer does not do anything at all. I get a
blinking cursor for a few moments, then a blank screen. No hard drive
activity (can't hear anything, indicator light not blinking.) However,
"Ubuntu, Linux 2.6.31-14-generic (recovery mode)" DOES work.
Here is the thing, though - I can't boot to Ubuntu with the default grub
options. I can boot successfully after making the following changes.
--------------------------------------------------------------------------
Original grub entry for "Ubuntu, Linux 2.6.31-14-generic":
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,4)
search --no-floppy --fs-uuid --set b7d0b17b-7c0e-4f3f-ac99-dd54922ebd93
linux /boot/vmlinuz-2.6.31-14-generic
root=UUID=b7d0b17b-7c0e-4f3f-ac99-dd54922ebd93 ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
--------------------------------------------------------------------------
Original grub entry for "Ubuntu, Linux 2.6.31-14-generic (recovery mode)":
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,4)
search --no-floppy --fs-uuid --set b7d0b17b-7c0e-4f3f-ac99-dd54922ebd93
linux /boot/vmlinuz-2.6.31-14-generic
root=UUID=b7d0b17b-7c0e-4f3f-ac99-dd54922ebd93 ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
--------------------------------------------------------------------------
Modified grub entry for "Ubuntu, Linux 2.6.31-14-generic" (this boots, whereas
the unmodified grub entry fails to boot):
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,4)
search --no-floppy --fs-uuid --set b7d0b17b-7c0e-4f3f-ac99-dd54922ebd93
linux /boot/vmlinuz-2.6.31-14-generic
root=UUID=b7d0b17b-7c0e-4f3f-ac99-dd54922ebd93 ro
initrd /boot/initrd.img-2.6.31-14-generic
}
--------------------------------------------------------------------------
I noticed that the entry for the recovery mode did not have "set quiet=1" or
"quiet splash", so I removed those, and what do you know? It boots!
Anyway, because I did a clean install, I can't believe I'm the only one
to have this problem. I'm reporting this bug because a clean install
with all stock/default options FAILED TO BOOT. Had I not looked at the
grub entries, I would not have been able to boot. I imagine some other
people would give up on Ubuntu for this reason.
I realize that I will need to post more information; my problems
probably involve the specific hardware I have. Please walk me through
posting further information, whether that be the output of commands,
logs, or just information about my hardware.
Thanks for taking the time to look!
** Affects: grub (Ubuntu)
Importance: Undecided
Status: New
--
Unable to boot - clean install
https://bugs.launchpad.net/bugs/465350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
