Vuescan + Redhat 9 + LS-5000: Scanner not ready

[Christian Tsotras]

Hello.

I just bought a Coolscan LS-5000.

The scanner is recognized by Vuescan 8.0.4, as it shows Source=LS-5000,
but when I launch a Preview or a Scan, Vuescan always says "Scanner not
ready".


Yesterday I made a lot of operations (chmod, chown, modprobe
scanner, modprobe ehci-hcd) that made the scanner work only once with
Vuescan, after one hour of unsuccessful tries.

And I made a 4000dpi scan successfully. But at next reboot, nothing worked.

Since then, Vuescan still recognizes the scanner, but always says
"Scanner not ready". Made many rmmod, modprobe and electrical power
off/on, but no result.


Does someone can help me ?

Thank you.


Config:
Redhat 9
kernel 2.4.20-19.9
libusb-0.1.7-3.i386.rpm
libusb-devel-0.1.7-3.i386.rpm
Vuescan 8.0.4

 

[Dances With Crows]

I just bought a Coolscan LS-5000. The scanner is recognized by
Vuescan 8.0.4, as it shows Source=LS-5000, but when I launch a Preview
or a Scan, Vuescan always says "Scanner not ready".

Yesterday I made a lot of operations (chmod, chown, modprobe scanner,
modprobe ehci-hcd) that made the scanner work only once with Vuescan,
after one hour of unsuccessful tries. kernel 2.4.20-19.9

It's time to upgrade that kernel. Preferably to an official version;
I've never trusted Redhat's custom kernels at all, and the supported
device list for USB is larger in 2.4.26 than it was in 2.4.20. This
shouldn't affect Vuescan much 'cause it uses libusb to do things to the
scanner, but there may have been bugs in 2.4.20.Redhat's ehci-hcd or
usb-uhci that have been patched in 2.4.26.official.

What were the exact commands you used? Execute "dmesg | grep -i usb"
and post the results. Also look in Vuescan's error logs and post
anything interesting/weird that you find.

libusb-0.1.7-3.i386.rpm Vuescan 8.0.4

The libusb is current. Écrivez en français si vous preferez, je peux le
lire. Bonne chance!

 

[Christian Tsotras]

<Please, deactivate word-wrapping for better viewing>

What were the exact commands you used?

I tried anything, even unrelated commands:

chown -hR cts /proc/bus/usb
find /proc/bus/usb -type d -exec chmod 777 {} \;
find /proc/bus/usb -type f -exec chmod 666 {} \;


modprobe scanner vendor=0x04b0 product=0x4002
modprobe ehci-hcd
(and removed other usb modules [visor, usbserial, adiusbadsl]
to avoid interference, but nothing happened)


ln -s /dev/usb/scanner0 /dev/usbscanner
chmod 666 /dev/usb/scanner*
chown cts /dev/sg[0123]

Execute "dmesg | grep -i usb"

Here is the result of many modprobe, rmmod, off/on, ...

[root@greco root]# dmesg | grep -i usb
usb.c: USB disconnect on device 00:09.2-3 address 3
hub.c: new USB device 00:09.2-3, assigned address 4
usb.c: USB device 4 (vend/prod 0x4b0/0x4002) is not claimed by any active driver.
usb.c: USB disconnect on device 00:09.2-3 address 4
hub.c: new USB device 00:09.2-3, assigned address 5
usb.c: USB device 5 (vend/prod 0x4b0/0x4002) is not claimed by any active driver.
usb.c: USB disconnect on device 00:09.2-3 address 5
hub.c: new USB device 00:09.2-2, assigned address 6
usb.c: USB device 6 (vend/prod 0x4b0/0x4002) is not claimed by any active driver.
usb.c: USB disconnect on device 00:09.2-2 address 6
hub.c: new USB device 00:09.2-2, assigned address 7
usb.c: USB device 7 (vend/prod 0x4b0/0x4002) is not claimed by any active driver.
usb.c: registered new driver usbscanner
scanner.c: USB scanner device (0x04b0/0x4002) now attached to scanner0
scanner.c: 0.4.12:USB Scanner Driver
scanner.c: probe_scanner: User specified USB scanner -- Vendorroduct - 4b0:4002
usb.c: USB disconnect on device 00:09.2-0 address 1
usb.c: USB disconnect on device 00:09.2-2 address 7
usb.c: USB bus 4 deregistered
hub.c: new USB device 00:09.0-2, assigned address 2
scanner.c: USB scanner device (0x04b0/0x4002) now attached to scanner0
ehci-hcd 00:09.2: VIA Technologies, Inc. USB 2.0
usb.c: new USB bus registered, assigned bus number 4
ehci-hcd 00:09.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22
usb.c: USB disconnect on device 00:09.0-2 address 2
hub.c: USB hub found
hub.c: new USB device 00:09.2-2, assigned address 2
scanner.c: USB scanner device (0x04b0/0x4002) now attached to scanner0
usb.c: USB disconnect on device 00:09.2-2 address 2
<6>hub.c: new USB device 00:09.2-2, assigned address 3
scanner.c: USB scanner device (0x04b0/0x4002) now attached to scanner0
usb_control/bulk_msg: timeout
usb.c: USB disconnect on device 00:09.2-0 address 1
usb.c: USB disconnect on device 00:09.2-2 address 3
usb.c: USB bus 4 deregistered
hub.c: new USB device 00:09.0-2, assigned address 3
scanner.c: USB scanner device (0x04b0/0x4002) now attached to scanner0
ehci-hcd 00:09.2: VIA Technologies, Inc. USB 2.0
usb.c: new USB bus registered, assigned bus number 4
ehci-hcd 00:09.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22
usb.c: USB disconnect on device 00:09.0-2 address 3
hub.c: USB hub found
hub.c: new USB device 00:09.2-2, assigned address 2
scanner.c: USB scanner device (0x04b0/0x4002) now attached to scanner0

and post the results. Also look in Vuescan's error logs and post
anything interesting/weird that you find.

Here is a simple session:

Start Vuescan in log mode
Preview => Scanner not ready
(several times)
Exit

VueScan 8.0.4 Linux
5115 0 TEST UNIT READY 0 0 0 0 0 0 f0020004 0500
5115 0 INQUIRY 12 1 1 0 4 0 00000004 0500 R 6 1 0 7
5115 0 INQUIRY 12 1 1 0 b 0 0000000b 0500 R 6 1 0 7 6 4d 6f 75 6e 74 0
5115 0 INQUIRY 12 1 c1 0 4 0 00000004 0500 R 6 c1 0 53
5115 0 INQUIRY 12 1 c1 0 57 0 00000057 0500 R 6 c1 0 53 3 0 3d 0 f 0 0 1 0 1 1 0 3 22 f a0 f a0 0 5a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 f 6a f a0 f a0 0 5a 0 0 16 95 0 0 0 0 0 0 0 0 0 0 16 96 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 43 0 0 10 f 6a 1 2
5116 0 TEST UNIT READY 0 0 0 0 0 0 f0020004 0500
5116 0 INQUIRY 12 1 1 0 4 0 00000004 0500 R 6 1 0 7
5116 0 INQUIRY 12 1 1 0 b 0 0000000b 0500 R 6 1 0 7 6 4d 6f 75 6e 74 0
5116 0 INQUIRY 12 1 c1 0 4 0 00000004 0500 R 6 c1 0 53
5116 0 INQUIRY 12 1 c1 0 57 0 00000057 0500 R 6 c1 0 53 3 0 3d 0 f 0 0 1 0 1 1 0 3 22 f a0 f a0 0 5a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 f 6a f a0 f a0 0 5a 0 0 16 95 0 0 0 0 0 0 0 0 0 0 16 96 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 43 0 0 10 f 6a 1 2
5117 0 TEST UNIT READY 0 0 0 0 0 0 f0020004 0500
5117 0 INQUIRY 12 1 1 0 4 0 00000004 0500 R 6 1 0 7
5117 0 INQUIRY 12 1 1 0 b 0 0000000b 0500 R 6 1 0 7 6 4d 6f 75 6e 74 0
5117 0 INQUIRY 12 1 c1 0 4 0 00000004 0500 R 6 c1 0 53
5117 0 INQUIRY 12 1 c1 0 57 0 00000057 0500 R 6 c1 0 53 3 0 3d 0 f 0 0 1 0 1 1 0 3 22 f a0 f a0 0 5a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 f 6a f a0 f a0 0 5a 0 0 16 95 0 0 0 0 0 0 0 0 0 0 16 96 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 43 0 0 10 f 6a 1 2
5117 0 TEST UNIT READY 0 0 0 0 0 0 f0020004 0500
5117 0 INQUIRY 12 1 1 0 4 0 00000004 0500 R 6 1 0 7
5117 0 INQUIRY 12 1 1 0 b 0 0000000b 0500 R 6 1 0 7 6 4d 6f 75 6e 74 0
5117 0 INQUIRY 12 1 c1 0 4 0 00000004 0500 R 6 c1 0 53
5117 0 INQUIRY 12 1 c1 0 57 0 00000057 0500 R 6 c1 0 53 3 0 3d 0 f 0 0 1 0 1 1 0 3 22 f a0 f a0 0 5a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 f 6a f a0 f a0 0 5a 0 0 16 95 0 0 0 0 0 0 0 0 0 0 16 96 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 43 0 0 10 f 6a 1 2
5118 0 TEST UNIT READY 0 0 0 0 0 0 f0020004 0500
5118 0 INQUIRY 12 1 1 0 4 0 00000004 0500 R 6 1 0 7
5118 0 INQUIRY 12 1 1 0 b 0 0000000b 0500 R 6 1 0 7 6 4d 6f 75 6e 74 0
5118 0 INQUIRY 12 1 c1 0 4 0 00000004 0500 R 6 c1 0 53
5118 0 INQUIRY 12 1 c1 0 57 0 00000057 0500 R 6 c1 0 53 3 0 3d 0 f 0 0 1 0 1 1 0 3 22 f a0 f a0 0 5a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 f 6a f a0 f a0 0 5a 0 0 16 95 0 0 0 0 0 0 0 0 0 0 16 96 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 43 0 0 10 f 6a 1 2
5119 0 TEST UNIT READY 0 0 0 0 0 0 f0020004 0500
5119 0 INQUIRY 12 1 1 0 4 0 00000004 0500 R 6 1 0 7
5119 0 INQUIRY 12 1 1 0 b 0 0000000b 0500 R 6 1 0 7 6 4d 6f 75 6e 74 0
5119 0 INQUIRY 12 1 c1 0 4 0 00000004 0500 R 6 c1 0 53
5119 0 INQUIRY 12 1 c1 0 57 0 00000057 0500 R 6 c1 0 53 3 0 3d 0 f 0 0 1 0 1 1 0 3 22 f a0 f a0 0 5a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 f 6a f a0 f a0 0 5a 0 0 16 95 0 0 0 0 0 0 0 0 0 0 16 96 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 43 0 0 10 f 6a 1 2



Thanks.

 

[Christian Tsotras]

It's time to upgrade that kernel. Preferably to an official version

Tried 2.4.26 : same results
Still "Scanner not ready"

With 2.4.20, the scanner worked *once*, but since then I couldn't
reproduce these working conditions ...

I don't know what to do.

 

[Christian Tsotras]

It's time to upgrade that kernel. Preferably to an official version

Tried 2.4.26 : same results [...]
I don't know what to do.

I found the solution:

This Nikon scanner dosn't want to scan a *completely* black slide (made of
an aluminium sheet between two black slides).

When using a normal slide, the scanner works.


My Minolta Elite scanned everything, it didn't check if a slide was
"visible" or not.

 

[Ed Hamrick]

I found the solution:

This Nikon scanner dosn't want to scan a *completely* black slide (made of
an aluminium sheet between two black slides).

It's actually the auto focus that doesn't work in this case. Turn
off the auto focus, and there shouldn't be any problem scanning an
aluminum sheet.

Regards,
Ed Hamrick

 

[Christian Tsotras]

It's actually the auto focus that doesn't work in this case. Turn off the
auto focus, and there shouldn't be any problem scanning an aluminum sheet.

The scanner reacts differently when I use the "aluminium" slide, with
Vuescan started or not. Same result with Nikonscan.

When I use the "aluminium" slide, the scanner doesn't produce the same
noises (much shorter) just after inserting the slide than when I insert a
normal film (multiple longer noises).

If you're right, this would mean that the scanner makes an autofocus
before using any software to control it. And that the aluminium prevents
it to autofocus successfully. When I remove the aluminium, but keep the
two black slides, the scanner works.