> The /dev/sg? devices are the so-called "generic" SCSI devices
> and programs use them to send specific, non-standard commands
> to those SCSI devices.
>
> To activate those devices, you have to have "Generic SCSI
> support" compiled into your kernel.
I didn't. I have it now.............
> Afterwards, the devices are mapped to the generic SCSI devices
> in their order of recognition, i.e. usually sorted by SCSI ID.
> A "dmesg" will usually give you a hint about which physical
> device is linked to which generic device.
>
> As an example:
>
> If you have three SCSI devices with the following parameters:
>
> ID 0: harddisk
> ID 2: CD ROM
> ID 6: scanner
>
> Then the harddisk would be /dev/sga, the cd-rom would be /dev/sgb
> and the scanner would be /dev/sgc.
I kinda-sorta thought that too, but I was unable to test it before I
re-compiled the kernel for scsi generic support. On mine it turns
out to be /dev/sge.
> As a side note, those "generic SCSI devices" are also used to
> properly access CD-ROM writers and other such "unusual" devices.
Hmmm, all this time my cd has been working without scsi-generic. Must
have been luck. 8-)
> Hope this helped you a bit,
Every little bit helps
> Manfred Lemke (ukpr@rz.uni-karlsruhe.de)
>
> P.S.: Can anyone tell me how to contact the SANE developer team
> for the Mustek backend? My scanner has a firmware release that's
> not included in the "working" sections, but it almost works
> (see my previous posting).
Is there not a developer's name on the backend driver page? Hmm, I just
looked. There are names, but no e-mails. Perhaps if you post to the list,
they'll answer.
Mike DuFresne
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com