SEO

Tony Curtis wrote:

>> I used to use a scanner on my Sun Ultra 80 with Jorg
>> Schilling's libsgc SCSI driver. I just installed the latest
>> Solaris release and found I could not get that to work as
>> expected.

> Maybe you need an appropriate inquiry-config-list in sgen.conf
> too? sgen(7D) for more (although I'm sure you know that).

My understanding is that something in the device-type-config-list will
bind if it's of the correct type - i.e. *any* scanner if one sets:

device-type-config-list = "scanner";

whereas any device made by umax on SCSI ID 4 would bind with:

inquiry-config-list = "umax", "*";
name="sgen" class="scsi" target=4 lun=0;

I've just tried the latter and get:

sparrow /kernel/drv # devfsadm -v -i sgen
devfsadm: driver failed to attach: sgen
exit status = 11

(what exactly exit code 11 means is not documented).

If I have in the conf file

name="sgen" class="scsi" target=4 lun=0;
device-type-config-list = "scanner";

I get no error messages:

sparrow /kernel/drv # devfsadm -v -i sgen
sparrow /kernel/drv #

suggesting it is binding to a scanner, but does not seem to be bind to
a umanx device of any sort.

Having all sgen.conf file:

inquiry-config-list = "umax", "*";
device-type-config-list = "scanner";
name="sgen" class="scsi" target=4 lun=0;

I get:

sparrow /kernel/drv # devfsadm -v -i sgen
devfsadm: driver failed to attach: sgen
exit status = 11

I might try again with Jorg Schilling's libscg. I have just made a
copy of the OS to tape, just after installation, by booting from a CD.
Hence restoring the OS to a 'just installed' state won't take long.
I'll try libscg then, since that did work before on Solaris 9.

>> On 11 Nov 2003 13:47:13 -0800,
>> see_my_signature_for_my_real_address@hotmail.com (Dr. David Kirkby) said:

> My understanding is that something in the
> device-type-config-list will bind if it's of the correct
> type - i.e. *any* scanner if one sets:

> device-type-config-list = "scanner";

> whereas any device made by umax on SCSI ID 4 would bind
> with:

> inquiry-config-list = "umax", "*"; name="sgen" class="scsi"
> target=4 lun=0;

Hummm, 'twas but a guess.

The only other experience I have to contribute is getting the
SCSI id wrong. That tends to prevent things working :-)

Tony Curtis wrote:

>> My understanding is that something in the
>> device-type-config-list will bind if it's of the correct
>> type - i.e. *any* scanner if one sets:

>> device-type-config-list = "scanner";

>> whereas any device made by umax on SCSI ID 4 would bind
>> with:

>> inquiry-config-list = "umax", "*"; name="sgen" class="scsi"
>> target=4 lun=0;

>Hummm, 'twas but a guess.

>The only other experience I have to contribute is getting the
>SCSI id wrong. That tends to prevent things working :-)

I don't think its the SCSI ID, since I did at one point uncomment all
the SCSI id's, so it should have bound to a scanner on any of them.

I did finally 'solve' it. When I re-read the instructions from Jorg
Schilling's libscg driver, I realised I had installed in incorrectly -
I had only installed a 64-bit driver, not a 32-bit one too. (I
originally done it years ago, so forgot the details). When I followed
the instructions carefully, his libscg driver worked and now my
scanner is working once again.

So whilst Sun's driver won't access the scanner, libscg will.

PS. Sorry for not posting in the usual way, so the thread follows. I
am posting from Google to hide my email address, but it takes several
hours between posting a message and it appearing on Google Groups.
However, I can read the posts instantly via my ISP's news server.
Hence I tend to post with one method and read with another.

Dr. David Kirkby.