On 8/14/07, Beso <[EMAIL PROTECTED]> wrote: > 9. i really don't get why your disk tries to put itself on udma33, but mine > used to do the same thing when i switched to 2.6.21. I added > libata.atapi_enabled=1 to my boot line and it worked. this is something due > to the sata driver. i don't really get why it is happening and why this > option (which i think it enables the sata pata support) works also if you're > using the old pata modules, but on my box it works. first give it a try > removing the noapic, then if it doesn't work, remove noapic and use instead > libata.atapi_enabled=1.
Kernel command line: root=/dev/hda1 noapic libata.atapi_enabled=1 Unknown boot option `libata.atapi_enabled=1': ignoring :( ciao maxxer -- [EMAIL PROTECTED] mailing list
