[lkml]   [2002]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Dont understand hdc=ide-scsi behaviour.
Use the line
hdc=ide-scsi hdd=ide-floppy

and all should be well, even if using ide-floppy as a module

Miles Lane wrote:

>On Thu, 2002-09-19 at 23:46, Brad Hards wrote:
>>Hash: SHA1
>>On Fri, 20 Sep 2002 07:08, Reg Clemens wrote:
>>>I dont understand the behaviour of kernel 2.4.18 (and probably all others)
>>>when I put the line
>>> hdc=ide-scsi
>>>on the load line.
>>>I would EXPECT to get the ide-scsi driver for hdc (my cdwriter) but instead
>>>get it for BOTH hdc and hdd, the cdwriter and the zip drive.
>>>After starting this way (with hdc=ide-scsi), I find that
>>> /dev/cdrom2 -> /dev/scd0
>>>and that to access the zip drive I have to use /dev/sda1 (or /dev/sda4)
>>There are two slightly different things happening, I think.
>>1. When you say hdc=ide-scsi, you are telling the IDE system that you don't
>>want to use the normal IDE interfaces to userland (such as ide-cdrom), but
>>instead want all access to this device to be accessed through the SCSI
>>midlayer (and associated SCSI interfaces, like the sg and scd drivers). So
>>ide-scsi becomes the driver, instead of ide-cdrom. You should be able to see
>>this in /proc/ide/hdc/driver
>>2. ide-scsi is greedy, and will grab any IDE device without a driver. ATAPI
>>floppy devices (hopefully) like your zip drive need the IDE floppy device
>>driver, which is probably not loaded. What does CONFIG_BLK_DEV_IDEFLOPPY
>>equal in your kernel config?


ICQ: 11965223

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:29    [W:0.047 / U:3.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site