On Wed, 9 Jan 2002 21:47, Keith Antoine wrote: > > *could* edit /etc/rc.local and type the magic words > > > > /sbin/modprobe ide-scsi > > Unfortunately this is distro dependent, or would seem so as in Suse the > cdrom drive I want as scsi is not seen as scsi until the append is > inserted. Also the cdrecoder is appended in lilo as a default. Mandrake > acts differently again.
You are completely right about this. For those trying to get a handle, the bottom line is: *either* you want your cd drive(s) to be ide, OR, you want them to be scsi. What they turn out to be is solely determined by which of two modules get loaded first, *either* ide-cdrom, *or*, ide-scsi The append statement, while a very unsatisfactory kludge, is the cleanest means of ensuring that ide-scsi grabs a cd regardless of how the initscripts are configured. Although I know the kernel cdrom api fairly well, I'm at a loss why there's an ide-cdrom driver at all. Removing it (from kernel source) would solve the issue. I can't recall any cd function in the api that isn't handled by the scsi driver. What's even more curious (for me) is loading ide-scsi ALSO removes the need for ide-floppy (eg zip and ls120 ide drives). Either the scsi performance is attrocious or we have Maintainer's egos getting in the soup. -- http://linux.nf -- [EMAIL PROTECTED] _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
