Ubuntu

Still cannot boot -14 kernel in Gutsy

Asked by tajreed

I updated from Feisty via the recommended method. It only provided the -14 and -12 kernels and I can only use the -12 kernel. I've also tried a fresh install using the live CD and the Alternate install. Neither will get beyond the "loading the kernel stage". Strangely enough I was able to reinstall using the Gutsy Beta release. But after some 395 updates I still ended up with the same two kernels and the -14 does not work.
One error that comes up is "Cannot find /rev/...by/uuid". But it does exist.

AMD processor 3.06
1G memory
Nvidia 6200
2 hd's
Boot HD 20g, boot, home and swap partitions. 2nd hd 40g backup/and storage
No floppy, and it has been removed from the bios

Any thoughts? I want to use the -14 kernel so that I can use Virtualbox.

Thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier
Solved:
Last query:
Last reply:
Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#1

At boot when you see the GRUB row press ESC key.
Select the desired kernel row then press "e" key
Another windows appear in front of you select the:
"kernel /boot/....... " row
then press the "e" key
and remove the "splash" and "quiet" parameter
press "Enter"
and "b" for boot
You can see more boot kernel messages that help you to find more detailed boot error.
To browse up and down boot messages use the Shift+PgUp / Shift+PgDown

Give us some feedback

Hope This Help you

Revision history for this message
tajreed (tajreed-charter) said : 		#2

Removing "splash and "quiet did not help.
Here the only anamolies that I could in find the boot script.
-ACPI extension AE-not found, processor dev is not present.
-via-rhine broken bios detected avoid d3 enabled
-Unable to handle kernel null pointer dereference....
-Udevd-event(2337) sbin/modprobe abnormal exit
-Alert-dev/disk/bu uuid......... does not exist

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#3

Using same procedure try to add common boot parameters the first i suggest you is noacpi

Here all parameters list https://help.ubuntu.com/community/BootOptions

HTH

Revision history for this message
tajreed (tajreed-charter) said : 		#4

Tried "noacpi", "nolapic" and "pic=noacpi" to no avail. Any other suggestions?

Revision history for this message
Best Olivier (olivier-lacroix) said : 		#5

Hi !

You may try booting with the boot option all_generic_ide

see here

http://ubuntuforums.org/showthread.php?t=584601

just a guess anyway

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#6

Find your UUID
sudo vol_id /dev/sda1 or sudo vol_id /dev/hda1

Here is mine
sudo vol_id /dev/sda1

ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=81ab79c8-7317-4c95-b504-763ca386fd8e
ID_FS_UUID_ENC=81ab79c8-7317-4c95-b504-763ca386fd8e
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=

My boot kernel row
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=81ab79c8-7317-4c95-b504-763ca386fd8e ....

Find yours and add it to your kernel parameter

Hope this help

Revision history for this message
tajreed (tajreed-charter) said : 		#7

Thanks Olivier, that solved my question.

Revision history for this message
Olivier (olivier-lacroix) said : 		#8

Glad that works !

Could you please make a bug report against kernel-source 2.6.22 linking to that question ? I could not find anything similar in launchpad