VueScan under Linux

  • Thread starter Thread starter Detlef Braungardt
  • Start date Start date
D

Detlef Braungardt

Hello,


i would connect my scanner with pc.

My configuration:
Linux - Debian Woody - Kernel 2.4.26
Scanner - Microtek ScanMaker 8700
VueScan 7.6.64

VueScan supported Microtek ScanMaker 8700. Can i use VueScan also under
Linux?

I tried with usb connection. I load the module 'scanner' with options
'vendor=0x05da product=0x20b1'. Then '/var/log/syslog' displayed me a
success and '/dev/usb/scanner0' is connected.
But 'VueScan' had no connection. I set the environment variables
SCANNER0, SCANVID0 and SCANPID0 with these lines:
export SCANNER0="/dev/usb/scanner0"
export SCANVID0="05da"
export SCANPID0="20b1"
'VueScan' had also no connection.

The 'vuescan.log' display 49 lines:
---------------------------------------------
VueScan 7.6.64 Linux
5913 0 INQUIRY 12 0 0 0 24 0 80000004 0000
....
5913 0 INQUIRY 12 0 0 0 24 0 80000004 0007
5913 0 INQUIRY 12 0 0 0 24 0 80000004 0100
....
5913 0 INQUIRY 12 0 0 0 24 0 80000004 0107
5913 0 INQUIRY 12 0 0 0 24 0 80000004 0200
....
....
5913 0 INQUIRY 12 0 0 0 24 0 80000004 0507
---------------------------------------------

I tried with firewire connection. I load the module sbp2. The module
found the scanner, but the device is not added. I am added the device
manually with
echo "scsi add-single-device 1 0 0 0" >/proc/scsi/scsi
After this the 'cat /proc/scsi/scsi' display a new device, but the
vendor and other entrys are not correct. 'VueScan' had also no connection.

How i connect 'VueScan' with ScanMaker 8700 under Linux?

I would test it with new version 8.0 of 'VueScan', but he found not the
lib 'libstdc++.so.5'. I found not this lib for debian.

Can you help me? Thanks in advance!


Detlef
 
Hi!

Detlef said:
Linux - Debian Woody - Kernel 2.4.26
Scanner - Microtek ScanMaker 8700
VueScan 7.6.64

VueScan supported Microtek ScanMaker 8700. Can i use VueScan also under
Linux?

I tried with usb connection. I load the module 'scanner' with options
'vendor=0x05da product=0x20b1'. Then '/var/log/syslog' displayed me a
success and '/dev/usb/scanner0' is connected.
But 'VueScan' had no connection. I set the environment variables
SCANNER0, SCANVID0 and SCANPID0 with these lines:
export SCANNER0="/dev/usb/scanner0"
export SCANVID0="05da"
export SCANPID0="20b1"
'VueScan' had also no connection.
Click to expand...

Do yao have either libusb installed or the scanner.o module loaded? The
first option is the better one!

If you have libusb and scanner.o is not loaded, then you should NOT set
SCANNER0.
The 'vuescan.log' display 49 lines:
Click to expand...

What does the kernel log say? dmesg or /var/log/syslog
I would test it with new version 8.0 of 'VueScan', but he found not the
Click to expand...

Will probably not change *this* problem.
lib 'libstdc++.so.5'. I found not this lib for debian.
Click to expand...

This library comes from gcc-33, so it is not in base woody. Go to bunk
for it: http://www.fs.tum.de/~bunk/debian

Bye
 
Hello!

Thanks for your answer!

Norbert said:
Hi!




Do yao have either libusb installed or the scanner.o module loaded? The
first option is the better one!
Click to expand...

I have installed libusb from woody. The installation had no effects for
'VueScan'. I think, 'libusb' are not loaded from 'VueScan'. I write a
'strace' - Log from 'VueScan', and i have not look a entry for 'libusb'.
Any Idea?

The 'VueScan' access to usb is logged with strace:
----------------------------------------------------------------------
open("/dev/usbscanner", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usbscanner0", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usb/scanner", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usb/scanner0", O_RDWR) = -1 ENODEV (No such device)
open("", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usbscanner1", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usb/scanner1", O_RDWR) = -1 ENODEV (No such device)
open("", O_RDWR) = -1 ENOENT (No such file or
directory)
....
open("/dev/usbscanner7", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usb/scanner7", O_RDWR) = -1 ENODEV (No such device)
open("", O_RDWR) = -1 ENOENT (No such file or
directory)
----------------------------------------------------------------------

If i loaded 'scanner.o', than the log had one success, but 'VueScan'
have not a connection:

----------------------------------------------------------------------
open("/dev/usbscanner", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usbscanner0", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usb/scanner", O_RDWR) = -1 ENOENT (No such file or
directory)
open("/dev/usb/scanner0", O_RDWR) = 7
ioctl(7, 0x80045520, 0xbfffe4b0) = 0
ioctl(7, 0x80045521, 0xbfffe4ac) = 0
open("/dev/usbscanner1", O_RDWR) = -1 ENOENT (No such file or
directory)
....
open("/dev/usb/scanner7", O_RDWR) = -1 ENODEV (No such device)
open("", O_RDWR) = -1 ENOENT (No such file or
directory)
----------------------------------------------------------------------
If you have libusb and scanner.o is not loaded, then you should NOT set
SCANNER0.



What does the kernel log say? dmesg or /var/log/syslog
Click to expand...

'/var/log/syslog' say:
----------------------------------------------------------------------
.... kernel: hub.c: new USB device 00:1d.0-1, assigned address 2
.... kernel: usb.c: USB device 2 (vend/prod 0x5da/0x20b1) is not claimed
by any active driver.
----------------------------------------------------------------------

If i loaded 'scanner.o' with line 'modprobe scanner vendor=0x05da
product=0x20b1', than '/var/log/syslog' say:
----------------------------------------------------------------------
.... kernel: scanner.c: USB scanner device (0x05da/0x20b1) now attached
to scanner0
.... kernel: scanner.c: 0.4.16:USB Scanner Driver
.... kernel: scanner.c: probe_scanner: User specified USB scanner --
Vendor:Product - 5da:20b1
----------------------------------------------------------------------
Will probably not change *this* problem.



This library comes from gcc-33, so it is not in base woody. Go to bunk
for it: http://www.fs.tum.de/~bunk/debian
Click to expand...

I think, the installation of gcc-3.x is not good on woody, because the
'libstdc++.so.5' is depending on more libs.
Bye
Click to expand...

Does anyone have any further ideas? Thanks for advance!


Bye
 
Hi Detlef!

Detlef said:
I have installed libusb from woody. The installation had no effects for
'VueScan'. I think, 'libusb' are not loaded from 'VueScan'. I write a
Click to expand...

Hmm, then I wonder how vuescan talks to the scanner. I suppose a version
of libusb is compiled in. Because here I have no kernel modules
scanner.o loaded and vuescan is talking to my scanner.
'strace' - Log from 'VueScan', and i have not look a entry for 'libusb'.
Any Idea?
Click to expand...

Yeah, I got a new idea: Did you try as root? There can be a permission
problem, very simple! You must have rw rights on /prob/bus/usb/XXX/YYY
according to your device.
I think, the installation of gcc-3.x is not good on woody, because the
'libstdc++.so.5' is depending on more libs.
Click to expand...

No, from the depends:
Depends: gcc-3.3-base, libc6 (>= 2.2.4-4), libgcc1 (>= 1:3.3-0pre9)
and from apt-cache policy:
libc6:
Installed: 2.2.5-11.5
Candidate: 2.2.5-11.5
Version Table:
*** 2.2.5-11.5 0
990 http://ftp.at.debian.org stable/main Packages

libgcc1 and gcc-3.3-base are both from bunk.
Does anyone have any further ideas? Thanks for advance!
Click to expand...

Permission, it hit me too. See the release notes for vuescan on a
description how to get it right.

Bye
 
Hi Norbert!

Norbert said:
Hi Detlef!




Hmm, then I wonder how vuescan talks to the scanner. I suppose a version
of libusb is compiled in. Because here I have no kernel modules
scanner.o loaded and vuescan is talking to my scanner.
Click to expand...

Hmmm ... Which scanner do you have?
Yeah, I got a new idea: Did you try as root? There can be a permission
problem, very simple! You must have rw rights on /prob/bus/usb/XXX/YYY
according to your device.
Click to expand...

This was a good idea, but i have correct rights for all user.
The 'ls -l /dev/usb/*' said:
----------------------------------------------------------------------
crw-rw-rw- 1 root root 180, 48 Mar 14 2002 /dev/usb/scanner0
crw-rw-rw- 1 root root 180, 49 Mar 14 2002 /dev/usb/scanner1
crw-rw-rw- 1 root root 180, 58 Mar 14 2002 /dev/usb/scanner10
crw-rw-rw- 1 root root 180, 59 Mar 14 2002 /dev/usb/scanner11
crw-rw-rw- 1 root root 180, 60 Mar 14 2002 /dev/usb/scanner12
crw-rw-rw- 1 root root 180, 61 Mar 14 2002 /dev/usb/scanner13
crw-rw-rw- 1 root root 180, 62 Mar 14 2002 /dev/usb/scanner14
crw-rw-rw- 1 root root 180, 63 Mar 14 2002 /dev/usb/scanner15
crw-rw-rw- 1 root root 180, 50 Mar 14 2002 /dev/usb/scanner2
crw-rw-rw- 1 root root 180, 51 Mar 14 2002 /dev/usb/scanner3
crw-rw-rw- 1 root root 180, 52 Mar 14 2002 /dev/usb/scanner4
crw-rw-rw- 1 root root 180, 53 Mar 14 2002 /dev/usb/scanner5
crw-rw-rw- 1 root root 180, 54 Mar 14 2002 /dev/usb/scanner6
crw-rw-rw- 1 root root 180, 55 Mar 14 2002 /dev/usb/scanner7
crw-rw-rw- 1 root root 180, 56 Mar 14 2002 /dev/usb/scanner8
crw-rw-rw- 1 root root 180, 57 Mar 14 2002 /dev/usb/scanner9
----------------------------------------------------------------------

--> I'm sorry to say: No success!

I tried also with user root. -> No success!
No, from the depends:
Depends: gcc-3.3-base, libc6 (>= 2.2.4-4), libgcc1 (>= 1:3.3-0pre9)
and from apt-cache policy:
libc6:
Installed: 2.2.5-11.5
Candidate: 2.2.5-11.5
Version Table:
*** 2.2.5-11.5 0
990 http://ftp.at.debian.org stable/main Packages

libgcc1 and gcc-3.3-base are both from bunk.
Click to expand...

Thanks for this idea! I have installed the version 3.2 and i receive
more depends. The installation with version 3.3 are successfully.
But 'VueScan' said:
----------------------------------------------------------------------
../vuescan: /lib/libc.so.6: version `GLIBC_2.3' not found (required by
../vuescan)
----------------------------------------------------------------------

I found this 'libc.so.6' with 'GLIBC_2.3' only for Debian sarge and sid.
I searched at 'apt-get.org'.
Many entrys in newsgroups warns for installation mix.
Permission, it hit me too. See the release notes for vuescan on a
description how to get it right.

Bye
Click to expand...

I think, 'VueScan' supported not the scanner under Linux.

Thanks for your time!


Bye!
 
Detlef Braungardt said:
My configuration:
Linux - Debian Woody - Kernel 2.4.26
Scanner - Microtek ScanMaker 8700
VueScan 7.6.64
Click to expand...

You need to use libusb if you use the USB connection to this
scanner, and you need to load the sbp2 module if you use the
Firewire connection.

You might also make sure you're using the latest version
of VueScan (8.0.2).

You don't need to use scanner.o

It's probably something related to the old software in Debian.

Regards,
Ed Hamrick
 
Hello!

Thanks for your answer!

Ed said:
You need to use libusb if you use the USB connection to this
scanner, and you need to load the sbp2 module if you use the
Firewire connection.
Click to expand...

I don't have a correct configuration of 'libusb'. I found information
on 'http://www.freecolormanagement.com/sane/libusb.html', but the trials
have not success.


I load the sbp2 modul for firewire connection, but 'VueScan' don't
connect to the scanner.

I add the device with
echo "add-single-device 1 0 0 0" >/proc/scsi/scsi
and a new device '/dev/sg7' is open. But the vendor and model is not
correct.

syslog:
-----------------------------------------------------------------------
.... kernel: ieee1394: got invalid ack 11 from node 65472 (tcode 4)
.... last message repeated 2 times
.... kernel: ieee1394: ConfigROM quadlet transaction error for node 0-00:1023
.... kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023
.... kernel: scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices
.... kernel: blk: queue d5fa2218, I/O limit 4095Mb (mask 0xffffffff)
.... kernel: ieee1394: sbp2: Logged into SBP-2 device
.... kernel: ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max
payload [2048]
.... kernel: ieee1394: NodeMgr: hotplug policy returned -2
.... kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[00d0b900b1000000]
.... kernel: scsi singledevice 1 0 0 0
.... kernel: blk: queue d4dd4818, I/O limit 4095Mb (mask 0xffffffff)
.... kernel: Vendor: \225 ¨`Á Model: \220 ïÔ[\203*ÀX ïÔ Rev: ÿÿÿÿ
.... kernel: Type: Direct-Access ANSI SCSI
revision: 02
.... kernel: blk: queue d4dd4a18, I/O limit 4095Mb (mask 0xffffffff)
-----------------------------------------------------------------------

'VueScan' have rights to connect the device, but it don't found the scanner.

A 'strace'-log from 'VueScan':
-----------------------------------------------------------------------
....
open("/dev/sg6", O_RDWR|O_NONBLOCK) = 8
ioctl(8, 0x2276, 0xbfffe274) = 0
close(8) = 0
open("/dev/sg7", O_RDWR|O_NONBLOCK) = 8
ioctl(8, 0x2276, 0xbfffe274) = 0
close(8) = 0
read(7, "", 1024) = 0
close(7) = 0
munmap(0x40015000, 4096) = 0
....
close(7) = 0
time(NULL) = 1086181982
time(NULL) = 1086181982
write(6, " 4702 0 INQUIRY "..., 89) = 89
open("/dev/sg7", O_RDWR|O_NONBLOCK|O_EXCL) = 7
ioctl(7, 0x2201, 0xbfffe02c) = 0
ioctl(7, 0x2282, 0x82cefd8) = 0
ioctl(7, 0x2276, 0xbfffe034) = 0
close(7) = 0
time(NULL) = 1086181982
time(NULL) = 1086181982
write(6, " 4702 0 INQUIRY "..., 89) = 89
....
-----------------------------------------------------------------------

Can you help me for advanced trouble-shooting?
You might also make sure you're using the latest version
of VueScan (8.0.2).
Click to expand...

I installed a new version of 'VueScan', but it said:
----------------------------------------------------------------------
../vuescan: /lib/libc.so.6: version `GLIBC_2.3' not found (required by
../vuescan)
----------------------------------------------------------------------

I found this 'libc.so.6' with 'GLIBC_2.3' only for Debian sarge and sid.
I searched at 'apt-get.org'.
Many entrys in newsgroups warns for installation mix on debian woody.
You don't need to use scanner.o
Click to expand...

It's okay, but the libusb can't connect to the scanner. Why? I don't
know. If i load the 'scanner.o', then a device is open and 'VueScan'
tried the device. I found this information in the 'strace'-log.
It's probably something related to the old software in Debian.
Click to expand...

It's probaly, but the kernel and the modules are new (2.4.26).
Regards,
Ed Hamrick
Click to expand...

Thanks for your time! Have you other ideas for me? If 'VueScan' works
correctly, then i would buy the 'VueScan'.


Regards

Detlef Braungardt
 
Back
Top