On Mar 11, 2008, at 8:32 PM, John Summerfield wrote:
Michal Jaegermann wrote:
On Tue, Mar 11, 2008 at 04:59:50PM +0900, John Summerfield wrote:
Note that the ATA buses are detected - a full transcription is here:
https://bugzilla.redhat.com/process_bug.cgi
https://bugzilla.redhat.com/show_bug.cgi?id=436099
Try again, please. (I made the same "copy-and-waste" in a hurry
mistakes in the past. :-)
I normally double-click and that doesn't stop at the "?." I am
cursed with the "swapped buttons" bug and that's been making lide
difficult.
https://bugzilla.redhat.com/show_bug.cgi?id=436099
and so's the SATA DVD drive, Just not the two SATA drives.
Does the following look familiar?
Looks familiar, but I don't think it's the same. I don't get a
timeout. B'sides, mine's Intel CPU and chips.
https://bugzilla.redhat.com/show_bug.cgi?id=436591
Note also URL references mentioned in comments. What about
nvidia chips. Mine are Chipzilla.
http://lkml.org/lkml/2008/3/9/136
and other messages in the same thread? If that is the case
then maybe 'irqpoll' has a chance to alleviate the problem
at least enough to boot?
Michal
The Jones boy think it's mkinitrd. I'm sceptical, it the same works
for other kernels, but I do wish it would go away.
There were a *lot* of people who were unable to boot after we moved to
pre-release 2.6.25 kernels:
0) mkinitrd figures out what device types / modules it's dealing with
by poking around in /sys.
1) There are big changes in the layout of /sys in 2.6.25 kernels.
2) Therefore, initrds created for 2.6.25 kernels fail under certain
(common) conditions.
So, nearly all of the "cannot find /dev/root" problems we've seen have
been mkinitrd-related. So davej is correct: it is very likely to be a
mkinitrd bug. It *might* actually be something in the sata driver..
but I can't really tell one way or the other.
What's your disk layout / fstab look like?
-w
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
