On Tue, Apr 17, 2007 at 04:42:41PM -0400, Jeff Garzik wrote: > Jesse Keating wrote: > >On Tuesday 17 April 2007 15:30:57 Dave Jones wrote: > >>jesse, wanna give that a shot? booting with the installer with > >>sata_nv.adma=0 should do the trick. > > > >That didn't effect anything. I still saw a message about "using ADMA > >mode" right before the panic(s). > > > >I added "sata_nv.adma=0" to the kernel arguments. > > If you still saw ADMA mode, then it's not seeing the module parameter. > > It sounds like putting sata_nv.adma on the kernel command line didn't do > the trick? > If it's a module, putting it on the kernel command line won't fix it, you have to break into the initramfs and add the module param. I've got a patch to send out later to apply saved_command_line[] checking to modules that I really wish I had been able to get into feisty. Cheers, Kyle - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html