kernel-2..6.17-1.2174_FC5 will not start; unknown scsi parameter on SATA laptop

Dave Jones davej at redhat.com
Tue Aug 15 20:38:52 UTC 2006


On Tue, Aug 15, 2006 at 11:51:43AM -0500, Paul Johnson wrote:
 > I have never seen this before with any kernel updates.  Currently all
 > versions 2.6.16 start fine, and the 2.6.17 before 2.7.2174 are OK.
 > 
 > I am running FC5 on a Dell Latitude D820 that has SATA hard disk that
 > FC5 treats as scsi, and it also has a CDRom which plugs into a modular
 > bay. As best I can describe it, this is a USB device, but linux will
 > treat it either as ide or scsi, depending on whether the parameter
 > hdc=noprobe is in the kernel start line.
 > 
 > Now, the problem with kernel-2.6.17-1.2174 (and the kernel-smp version as well)
 > 
 > The kernel panics and it does not leave behind a log file. But I've
 > copied down the messages that seem important.
 > 
 > scsi_mod: Unknown parameter max_scsi_luns
 > 
 > insmod: error inserting /lib/scsi-mod.ko -1 unknown symbol
 > (a few more insmod errors concerning scsi)
 > 
 > Unable to access resume device
 > 
 > mount: could not find file system
 > 
 > then the panic happens.
 > 
 > I don't know what else might be relevant.  I'm running the
 > gnome-power-manager and related updates for hal from the Utopia
 > website.  That's the devel series that Richard Hughes offers.
 > 
 > I previously had trouble getting a picture card reader to mount in the
 > scsi subsystem and did put in an option max_scsi_luns in to
 > modprobe.conf, but when this kernel problem came up, I removed that
 > option and retried. Same result.

Did you rebuild the initrd after removing that option ?
(The option isn't needed anymore because kernels since FC3 or so
 scan all LUNs by default).

		Dave

-- 
http://www.codemonkey.org.uk




More information about the fedora-list mailing list