kernel 2.6.22.14 won't start

Bug #152863 reported by apalosilla
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

The 2.6.22.14 kernel does not start. It started with 2.6.22.12 (updating Feisty to Gutsy), but from 2.6.22.13 on, it does not start.
I also have this problem with the Ubuntu 7.10 RC Live CD.

The error:

"udev-event [2239]: run-program 'sbin/modprobe' anormal exit

(initramfs)

Nanley Chery (nanoman)
description: updated
Revision history for this message
Alberto (darkxer0x) wrote :

I also have thie same problem when I try to install Ubuntu 7.10 (Amd 64). When the live cd is loading, an error message appears:
udev-event[2455]: run-program ´/sbin/modprobe´ abnormal exit
BusyBos...
(initramfs)

And there are more people with the same problem: http://ubuntuforums.org/showthread.php?t=579493

Asus m2v
amd dual-core 3800
Ati x1550

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2 which is set to come out around Dec 20. However, here are the instructions to install if you choose to do so, otherwise just wait for Alpha2 to come out:

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I opened a new task against the actively developed kernel and am closing this against linux-source-2.6.22. Thanks.

Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
acor (adrian2007) wrote : Re: kernel 2.6.22.14 won't start and also kernel 2.6.24-1

I tried it unsuccessfully with linux-image-2.6.24-1-generic from "deb http://archive.ubuntu.com/ubuntu hardy main restricted".

During update-initramfs within the installation process I saw errors about missing files under "/lib/firmware/2.6.24...". I tried a boot anyway but got grub error 15. So I have switched back to kernel 2.6.20-16-generic and hope that this kernel (from Feisty) will work well.

It seemes that I had accepted the online update to 7.10 (Gutsy Gibbon) too rashly. I am Kubuntu beginner and did not expect such basic errors (initramfs could not detect root filesystem on IDE). Particularly after I was content with Version 7.04 (Feisty).

Revision history for this message
apalosilla (apalosilla) wrote :

(Sorry for my english, this is a automatic translation)

I have updated to the 2.6.24.1 and, still having the same error that
"acor", yes that I have been able to start normally. I believe that it
is solved.

At the moment I am in "Gutsy" with kernel 2.6.22.14 with the solution
that they give here:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/154591

And indeed, it seems to be that problem with the HD Seagate, those two
models in concrete.

Thanks!

Revision history for this message
acor (adrian2007) wrote :

The hint given by "apalosilla" fits perfectly to my case. I am able to boot now with the additional boot param "all_generic_ide" in /boot/grub/menu.lst:

"kernel /vmlinuz-2.6.22-14-generic root=UUID=... ro all_generic_ide"

which is descipted in "https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/154591". Similar as mentioned there by "yamar" the command "df" shows /dev/sda and /dev/sdb and for CDROM /dev/scd0 instead of /dev/hda, hdb ... (but my /etc/fstab is left unchanged in contrast to yamar's perhaps because the devices are entered by UUID).

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the update. Just to share some information, the reason your devices are showing up as /dev/sd* rather than /dev/hd* is because the kernel is now using the libata subsystem which makes all ATA devices appear with the /dev/sd* syntax.

After reviewing bug 154591, it seems this report is a duplicate of that one so I will mark it as such. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.