On Thu, Jan 15, 2009 at 09:07:11PM +0100, Antonio M wrote: > 2009/1/15 Michal Jaegermann <michal@xxxxxxxxxxxx>: > > > > 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. > > > these are the lines in dmesg in a regular boot: any comment??? > > scsi 0:0:0:0: Direct-Access ATA Maxtor 6L200P0 BAH4 PQ: 0 ANSI: 5 > sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors: (203 GB/189 GiB) > sd 0:0:0:0: [sda] Write Protect is off > sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't > support DPO or FUA ..... Well, attachment to https://bugzilla.redhat.com/show_bug.cgi?id=479525 is not of an application/octet-stream type, as left there, but your regular text. Few lines is usually more than enough here. Here and there you mean that this is what you expect to see in a normal boot but it not coming. Right? You are not perfectly clear. If this happens then, if you installed kernel-doc package, in /usr/share/doc/kernel-doc-2.6.29/Documentation/kernel-parameters.txt there are described various 'libata....' parameters which you may want to try. It is also possible that in that part of dmesg you are not showing, and from a failing boot, there are some errors and/or hints which can give you an information. If you will find some options which allow you to boot then this is a valuable information for developers. If you want the whole story then in subdirectory DocBook/libata you will find the whole big reference. Michal -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
