2009/1/15 Michal Jaegermann <michal(a)harddata.com>:
On Thu, Jan 15, 2009 at 03:27:14PM -0300, Horst H. von Brand wrote:
> Antonio M <antonio.montagnani(a)gmail.com> wrote:
> > No kernel 2.6.29.x is able to start any of my 3 F11 boxes.
>
> For me kernel-2.6.29-0.31.rc1.git2.fc11.x86_64 and 0.35 do work (kernels
> before that did hang on boot, crash X, ...).
>
> It could be a broken initrd, a new mkinitrd showed up in updates
> today.
Antonio is not saying very much what really happens so no wonder
that nobody is rushing with an advice. OTOH from what he eventually
posted on
https://bugzilla.redhat.com/show_bug.cgi?id=479525#c4 it
appears that this is way before initrd comes into play. What is
supposed to come on his machine(s) after
ata2.00: configured for UDM/33
ata2.01: configured for MWDMA2
is his own sweet secret.
I thought initially that he possibly gets "crc error", which
happened to me at the same time, but apparently this is not that and
starting with 2.6.29-0.28.rc1.fc11 on my hardware current kernels
boot again.
Michal
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
Tnx to both of you.
Michael there is no my secret, as after those lines system idles and I
have to do an hard reboot (unless someone suggests how to proceed in
digging)
And my system is fully updated (as rawhide, I mean).
I wonder why kernel 28 boot fine and 2'9's no...
If you have any suggestion, I will proceed to further tests: and for
sure at least two out of three boxes don't boot (or complete
booting..:)
Any option to include???
Tnx again
--
Antonio Montagnani
Skype : antoniomontag