scanner question
#1
scanner question
Hello,

I try to setup my old scanner (using the factory documentation) but I have problems...
This is an o2 with irix 6.5.22

As root I had to create a /dev/scanner folder and a link to the /dev/scsi/sc2d1l0 item (this represent my scanner on the scsi controller2):
ln -s /dev/scsi/sc2d1l0 /dev/scanner

after that I had to do a chmod 666 /dev/scanner (after this the /dev/scanner folder has the rw-/rw-/rw- permission)

The link is created (I see it with italic letters on the desktop) it is a 17Bytes file (link) permissions: rwx/r-x/r-x

The original item in /dev/scsi/ is 0Bytes long and had the permissions rw-/---/--- as the other scsi items.

Logged as root everythig is fine.

But when I log in with my user account, I see nothing in the /dev/scanner folder (nor the scanner software, so it doesn't see the scanner).
What do I wrong?

UPDATE: i don't know why, but after I set execute permissions for everyone on the /dev/scanner/sc2d1l0 the file (link) appeared in the user account.
I can only see 0Byte long files in the /dev/scsi folder is it normal?
Now when I start the scanning software I get the following error messages:
scan: execution of inquiry_standard command failed (status unknown)
scan: unable to inquiry scanner
It seems the software cannot communicate with the scanner with the scsi inquiry command.
The scanner is properly connected, the scsi chain is terminated, the scanner is visible in hinv.
Something with this link is not correct.
Is there any way to communicate with a scsi scanner via command line, e.g. manually check a status like ping in networking?

[Image: o2.png]
(This post was last modified: 05-24-2021, 06:04 PM by blaiserulez.)
blaiserulez
Supporter

Trade Count: (0)
Posts: 27
Threads: 3
Joined: Apr 2021
Location: Hungary
Find Reply
05-24-2021, 09:03 AM
#2
RE: scanner question
(05-24-2021, 09:03 AM)blaiserulez Wrote:  As root I had to create a /dev/scanner folder and a link to the /dev/scsi/sc2d1l0 item (this represent my scanner on the scsi controller2):
ln -s /dev/scsi/sc2d1l0 /dev/scanner

Are you sure /dev/scanner is supposed to be a "folder" (or "directory" as it is called in Unix)?  I would think that it should be a direct link /dev/scanner -> /dev/scsi/sc2d1l0.  In other words, you should NOT create the "folder" (or remove the existing one);  just type the "ln" command as given above to create a direct link rather than a link in a folder.  (But again, that's my speculation.  I'm not 100% sure of the above.)

(05-24-2021, 09:03 AM)blaiserulez Wrote:  The link is created (I see it with italic letters on the desktop) it is a 17Bytes file (link) permissions: rwx/r-x/r-x

The 17 bytes looks right.  The permissions don't.  I think they should be rw-rw-rw-.  I don't see why you'd need execute permission (the 'x' bit), but you would need write permission ('w') to send SCSI commands to it.  Try that first, before the above suggestion.

(05-24-2021, 09:03 AM)blaiserulez Wrote:  The original item in /dev/scsi/ is 0Bytes long and had the permissions rw-/---/--- as the other scsi items.

That is perfectly normal.  The files under /dev aren't real files.  They're special to the operating system kernel.

SGI:  Indigo, Indigo2, Octane, Origin 300
Sun:  SPARCstation 20 (x4), Ultra 2, Blade 2500, T5240
HP:  9000/380, 425e, C8000
Digital: DECstation 5000/125, PWS 600au
jpstewart
Developer

Trade Count: (1)
Posts: 444
Threads: 6
Joined: May 2018
Location: SW Ontario, CA
Find Reply
05-24-2021, 11:33 PM
#3
RE: scanner question
(05-24-2021, 11:33 PM)jpstewart Wrote:  
(05-24-2021, 09:03 AM)blaiserulez Wrote:  As root I had to create a /dev/scanner folder and a link to the /dev/scsi/sc2d1l0 item (this represent my scanner on the scsi controller2):
ln -s /dev/scsi/sc2d1l0 /dev/scanner

Are you sure /dev/scanner is supposed to be a "folder" (or "directory" as it is called in Unix)?  I would think that it should be a direct link /dev/scanner -> /dev/scsi/sc2d1l0.  In other words, you should NOT create the "folder" (or remove the existing one);  just type the "ln" command as given above to create a direct link rather than a link in a folder.  (But again, that's my speculation.  I'm not 100% sure of the above.)

(05-24-2021, 09:03 AM)blaiserulez Wrote:  The link is created (I see it with italic letters on the desktop) it is a 17Bytes file (link) permissions: rwx/r-x/r-x

The 17 bytes looks right.  The permissions don't.  I think they should be rw-rw-rw-.  I don't see why you'd need execute permission (the 'x' bit), but you would need write permission ('w') to send SCSI commands to it.  Try that first, before the above suggestion.

(05-24-2021, 09:03 AM)blaiserulez Wrote:  The original item in /dev/scsi/ is 0Bytes long and had the permissions rw-/---/--- as the other scsi items.

That is perfectly normal.  The files under /dev aren't real files.  They're special to the operating system kernel.

Thank You, jpstewart! I removed the /dev/scanner directory and created the direct link. With the link the scanner is working perfectly.
Now I have a working large format scanner at home again... It's a huge monster Smile

[Image: o2.png]
blaiserulez
Supporter

Trade Count: (0)
Posts: 27
Threads: 3
Joined: Apr 2021
Location: Hungary
Find Reply
05-25-2021, 06:04 AM


Forum Jump:


Users browsing this thread: 1 Guest(s)