F12: Latest Three Kernels Won't Boot (was: F12: Latest Two Kernels Won't Boot)
Oliver Ruebenacker wrote:
> Still same problem on same machine (at a location I am not using
> often). After not using the machine for two weeks, I installed the
> latest updates, including a new kernel, and the new kernel does not
> boot either.
> None of the reported bugs I have seen so far seems to be my problem.
> What next? Thanks!
> Take care
> On Thu, Jan 21, 2010 at 3:34 PM, Oliver Ruebenacker <firstname.lastname@example.org> wrote:
>> When a few weeks ago the new auto-updated kernel would not boot,
>> used an older kernel, waiting for the next update. This was today, and
>> now the two latest kernels don't work. Booting stops after the Fedora
>> logo fills up white, after which it says (copying manually from
>> screen, whitespaces probably not correct):
>> ERROR: asr: wrong # of devices in RAID set "asr_BOOT " [1/2] on /dev/sda
>> No root device found
>> Boot has failed, sleeping forever
>> The third oldest kernel apparently boots fine. Interestingly, Google
>> finds nothing for "ERROR: asr: wrong".
>> I am attaching grub.conf.
I have not seen a working kernel since 126.96.36.199 for my laptops. However, the
2.6.33-rc6 and later work fine, so I don't have to run in single user mode. All
of the recent Fedora kernels lose the touchpad.
I'm still waiting months later for
to even be assigned, so don't have a lot of hope that a bug that don't hit
developer's machines are going to get much attention unless it hits a lot of
people. Very hard to debug without the effected hardware, and great hope that
the user or hardware will die and stop complaining. Or switch to a distribution
Bill Davidsen <email@example.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
users mailing list
To unsubscribe or change subscription options: