wrote:
> Hi Chris!
>
> I'm also using an Epson Perfection 1200 with the ADF option for several years
> for pretty the same purpose as you do. I am satisfied with its performance,
> only a hissing noise when it's idle is a little bit disturbing... (-;
> If you're going to purchase one if its sucessors and are interested, i can
> send you the script i'm using.
> at the moment i am also writing a java application to scan multiple-page
> documents in an easy way...
>
> ciao,
> ~klemens
>
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
From kladit@t-online.de Fri Jan 16 15:34:07 2004
From: kladit@t-online.de (Klaus Dittrich)
Date: Fri, 16 Jan 2004 16:34:07 +0100
Subject: [sane-devel] linux-2.6.1-smp,usb,oops,sane-backends-1.0.13,epson-1640
In-Reply-To: <20040115201928.GC1768@meier-geinitz.de>
References: <20040115172800.GA648@xeon2.local.here> <20040115201928.GC1768@meier-geinitz.de>
Message-ID: <20040116153407.GA2115@xeon2.local.here>
Using libusb I get no errors.
So the bug seems to be with the kernel scanner driver.
I noticed two system things.
First /sbin/hotplug is now called every time I do a scanimage -L or -f.
Second every time I switch the scanner on or off the device number
gets incremented.
scanimage -L now works. (worked not in sane-backend-1.0.12)
device `epson:libusb:002:005' is a Epson Perfection1640 flatbed scanner
The ADF is not detectable ?
scanimage -d epson:libusb:002:005 --test works too.
scanimage -d epson:libusb:002:005 --source 'Automatic Document Feeder'
does _not_ work. After a long time I get ..
scanimage: sane_start: Error during device I/O
Any ideas ?
--
Klaus
From SCOTTNAVARRE@peoplepc.com Fri Jan 16 06:44:13 2004
From: SCOTTNAVARRE@peoplepc.com (Scott Navarre)
Date: Thu, 15 Jan 2004 23:44:13 -0700
Subject: [sane-devel] How to set permissions on my scasnner device files?
Message-ID: <001001c3dbfc$2868bc60$0100a8c0@cybertron>
This is a multi-part message in MIME format.
------=_NextPart_000_000D_01C3DBC1.7ACC8260
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I am setting up an Epson Perfection 1260/Photo scanner thru USB (uses =
the Plustek driver). I have upgraded my Red Hat 8.0's SANE backend =
drivers to version 1.0.13.
And now, I can see the scanner using both 'scanimage -L' and =
'sane-find-scanner', as root only (I can also use 'xsane' as root only). =
If I am not root, 'scanimage -L' finds nothing, and =
'sane-find-scanners' finds a scanner on the USB but doesn't identify it. =
The man page said something about not having the permissions of the =
device file set right if this happens.
The thing is that when it is displayed, it only shows 'libusb:001:004' =
as the device name, not something in '/dev' (such as the =
'/dev/usbscanner0' or '/dev/sg0' as mentioned in the man page). So how =
or where do I go to change the permissions??? Out of frustration, I did =
a 'chmod -R 777 /dev' but it didn't help...
Here are my outputs of the 2 commands by root:
[root@tepeyac root]# scanimage -L =
=20
device `plustek:libusb:001:004' is a Epson Perfection 1260/Photo USB =
flatbed sca
nner =
=20
[root@tepeyac root]# sane-find-scanner =
=20
=
=20
# No SCSI scanners found. If you expected something different, make =
sure that=20
# you have loaded a SCSI driver for your SCSI adapter. =
=20
=
=20
found USB scanner (vendor=3D0x04b8 [EPSON], product=3D0x011d [EPSON =
Scanner], chip=3DL
M9832/3) at libusb:001:004 =
=20
# Your USB scanner was (probably) detected. It may or may not be =
supported by=20
# SANE. Try scanimage -L and read the backend's manpage. =
=20
=
=20
# Scanners connected to the parallel port or other proprietary ports =
can't be=20
# detected by this program. =
=20
[root@tepeyac root]#
And here are my outputs of the same 2 commands by a non-root user:
[claudia@tepeyac claudia]$ scanimage -L =
=20
=
=20
No scanners were identified. If you were expecting something different, =
=20
check that the scanner is plugged in, turned on and detected by the =
=20
sane-find-scanner tool (if appropriate). Please read the documentation =
=20
which came with this software (README, FAQ, manpages). =
=20
[claudia@tepeyac claudia]$ sane-find-scanner =
=20
=
=20
# No SCSI scanners found. If you expected something different, make =
sure that=20
# you have loaded a SCSI driver for your SCSI adapter. =
=20
=
=20
found USB scanner (vendor=3D0x04b8, product=3D0x011d, chip=3DLM983x?) at =
libusb:001:00
4 =
=20
# Your USB scanner was (probably) detected. It may or may not be =
supported by=20
# SANE. Try scanimage -L and read the backend's manpage. =
=20
=
=20
# Scanners connected to the parallel port or other proprietary ports =
can't be=20
# detected by this program. =
=20
=
=20
# You may want to run this program as root to find all devices. Once =
you =20
# found the scanner devices, be sure to adjust access permissions as =
=20
# necessary. =
=20
[claudia@tepeyac claudia]$
Thanks in advance,
Scott Navarre
------=_NextPart_000_000D_01C3DBC1.7ACC8260
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I am setting up an Epson =
Perfection=20
1260/Photo scanner thru USB (uses the Plustek driver). I have =
upgraded my=20
Red Hat 8.0's SANE backend drivers to version 1.0.13.
And now, I can see the scanner =
using both=20
'scanimage -L' and 'sane-find-scanner', as root only (I can also use =
'xsane' as=20
root only). If I am not root, 'scanimage -L' finds nothing, and=20
'sane-find-scanners' finds a scanner on the USB but doesn't identify =
it. =20
The man page said something about not having the permissions of the =
device file=20
set right if this happens.
The thing is that when it is =
displayed, it=20
only shows 'libusb:001:004' as the device name, not something in '/dev' =
(such as=20
the '/dev/usbscanner0' or '/dev/sg0' as mentioned in the man =
page). So how=20
or where do I go to change the permissions??? Out of frustration, =
I did a=20
'chmod -R 777 /dev' but it didn't help...
Here are my outputs of the 2=20
commands by root:
[root@tepeyac root]# scanimage=20
-L =
; =
&=
nbsp; =20
device `plustek:libusb:001:004' is a Epson Perfection 1260/Photo USB =
flatbed=20
sca
nner &n=
bsp; &nb=
sp; &nbs=
p; =
; =
&=
nbsp; =20
[root@tepeyac root]# =20
sane-find-scanner &n=
bsp; &nb=
sp; &nbs=
p; =20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
# No SCSI scanners found. If you expected something =
different, make=20
sure that
# you have loaded a SCSI driver for your SCSI=20
adapter. =
; =
=20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
found USB scanner (vendor=3D0x04b8 [EPSON], product=3D0x011d [EPSON =
Scanner],=20
chip=3DL
M9832/3) at=20
libusb:001:004 =
; =
&=
nbsp; &n=
bsp; =20
# Your USB scanner was (probably) detected. It may or may not =
be=20
supported by
# SANE. Try scanimage -L and read the backend's=20
manpage. =
; =20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
# Scanners connected to the parallel port or other =
proprietary ports=20
can't be
# detected by this=20
program. =
; =
&=
nbsp; &n=
bsp; =20
[root@tepeyac root]#
And here are my outputs of the =
same 2=20
commands by a non-root user:
[claudia@tepeyac claudia]$ =
scanimage=20
-L =
; =
&=
nbsp; =20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
No scanners were identified. If you were expecting something=20
different,
check =
that the=20
scanner is plugged in, turned on and detected by=20
the &nbs=
p;=20
sane-find-scanner tool (if appropriate). Please read the=20
documentation =
which=20
came with this software (README, FAQ,=20
manpages). &nb=
sp; &nbs=
p; =20
[claudia@tepeyac claudia]$=20
sane-find-scanner &n=
bsp; &nb=
sp; &nbs=
p; =20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
# No SCSI scanners found. If you expected something =
different, make=20
sure that
# you have loaded a SCSI driver for your SCSI=20
adapter. =
; =
=20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
found USB scanner (vendor=3D0x04b8, product=3D0x011d, =
chip=3DLM983x?) at=20
libusb:001:00
4 &=
nbsp; &n=
bsp; &nb=
sp; &nbs=
p; =
; =
=20
# Your USB scanner was (probably) detected. It may or may not =
be=20
supported by
# SANE. Try scanimage -L and read the backend's=20
manpage. =
; =20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
# Scanners connected to the parallel port or other =
proprietary ports=20
can't be
# detected by this=20
program. =
; =
&=
nbsp; &n=
bsp; =20
&nb=
sp; &nbs=
p; =
; =
&=
nbsp; &n=
bsp; =20
# You may want to run this program as root to find all =
devices. Once=20
you
# found the scanner =
devices, be=20
sure to adjust access permissions=20
as
#=20
necessary. &nb=
sp; &nbs=
p; =
; =
&=
nbsp; =20
[claudia@tepeyac claudia]$
Thanks in advance,
Scott =
Navarre
------=_NextPart_000_000D_01C3DBC1.7ACC8260--
From kladit@t-online.de Fri Jan 16 19:33:27 2004
From: kladit@t-online.de (Klaus Dittrich)
Date: Fri, 16 Jan 2004 20:33:27 +0100
Subject: [sane-devel] How to set permissions on my scasnner device files?
In-Reply-To: <001001c3dbfc$2868bc60$0100a8c0@cybertron>
References: <001001c3dbfc$2868bc60$0100a8c0@cybertron>
Message-ID: <20040116193327.GA27345@xeon2.local.here>
On Thu, Jan 15, 2004 at 11:44:13PM -0700, Scott Navarre wrote:
> Hi,
>
> I am setting up an Epson Perfection 1260/Photo scanner thru USB (uses the Plustek driver). I have upgraded my Red Hat 8.0's SANE backend drivers to version 1.0.13.
> And now, I can see the scanner using both 'scanimage -L' and 'sane-find-scanner', as root only (I can also use 'xsane' as root only). If I am not root, 'scanimage -L' finds nothing, and 'sane-find-scanners' finds a scanner on the USB but doesn't identify it. The man page said something about not having the permissions of the device file set right if this happens.
> The thing is that when it is displayed, it only shows 'libusb:001:004' as the device name, not something in '/dev' (such as the '/dev/usbscanner0' or '/dev/sg0' as mentioned in the man page). So how or where do I go to change the permissions??? Out of frustration, I did a 'chmod -R 777 /dev' but it didn't help...
>
> Here are my outputs of the 2 commands by root:
>
> [root@tepeyac root]# scanimage -L
> device `plustek:libusb:001:004' is a Epson Perfection 1260/Photo USB flatbed sca
> nner
> [root@tepeyac root]# sane-find-scanner
>
> # No SCSI scanners found. If you expected something different, make sure that
> # you have loaded a SCSI driver for your SCSI adapter.
>
> found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON Scanner], chip=L
> M9832/3) at libusb:001:004
> # Your USB scanner was (probably) detected. It may or may not be supported by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> # Scanners connected to the parallel port or other proprietary ports can't be
> # detected by this program.
> [root@tepeyac root]#
>
> And here are my outputs of the same 2 commands by a non-root user:
>
> [claudia@tepeyac claudia]$ scanimage -L
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> [claudia@tepeyac claudia]$ sane-find-scanner
>
> # No SCSI scanners found. If you expected something different, make sure that
> # you have loaded a SCSI driver for your SCSI adapter.
>
> found USB scanner (vendor=0x04b8, product=0x011d, chip=LM983x?) at libusb:001:00
> 4
> # Your USB scanner was (probably) detected. It may or may not be supported by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> # Scanners connected to the parallel port or other proprietary ports can't be
> # detected by this program.
>
> # You may want to run this program as root to find all devices. Once you
> # found the scanner devices, be sure to adjust access permissions as
> # necessary.
> [claudia@tepeyac claudia]$
>
> Thanks in advance,
> Scott Navarre
In /etc/fstab change to
none /proc/bus/usb usbfs defaults,devmode=0666 0 0
Source of information : Henning Meier-Geinitz + man sane-usb
--
Klaus
From jimquigley9@eircom.net Sat Jan 17 01:52:18 2004
From: jimquigley9@eircom.net (Jim Quigley)
Date: Sat, 17 Jan 2004 01:52:18 +0000
Subject: [sane-devel] re epson perfection 1200 problems libusb kernel 2.6.1-rc1
Message-ID: <40089552.9060106@eircom.net>
This is a multi-part message in MIME format.
--------------090808010205010105020404
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Hi I have installed the kernel 2.6.1-rc1 over Suse 9 and have as far as
I know installed most usb drivers as modules except the scanner.o module
since it is obsolete and I wanted to use libusb. I have an epson
perfection 1200 photo scanner but I can not get it to work properly. It
initialises but then crashes and then scanimage -L does not recognise
it. Xsane also does the same. Below are some of the programs I use and
some config files including sane, xsane, fstab, dmesg etc. Appreciate
some help. Thanks
rpm -q sane
sane-1.0.10-243
rpm -q xsane
xsane-0.91-135
rpm -q hotplug
hotplug-2002_08_26-85
cat /etc/fstab
/dev/hdc1 / ext2
defaults 1 1
/dev/hdc2 /home ext2
defaults 1 2
/dev/hdc3 swap swap
pri=42 0 0
devpts /dev/pts devpts
mode=0620,gid=5 0 0
proc /proc proc
defaults 0 0
none /proc/bus/usb usbfs defaults 0 0
/dev/cdrom /media/cdrom auto
ro,noauto,user,exec 0 0
/dev/dvd /media/dvd auto
ro,noauto,user,exec 0 0
/dev/fd0 /media/floppy auto
noauto,user,sync 0 0
/dev/sr0 /media/sr0 auto ro,noauto,user,exec 0 0
/dev/sda1 /media/sda1 auto sync,noauto,user,exec 0 0
cat /proc/bus/usb/devices
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.2
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=07(print) Sub=01 Prot=02 MxPS=64 #Cfgs= 1
P: Vendor=04b8 ProdID=0001 Rev= 1.00
S: Manufacturer=EPSON
S: Product=USB Printer
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.1
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=04b8 ProdID=0104 Rev= 1.03
S: Manufacturer=EPSON
S: Product=Perfection1200
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.0
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:10.3
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0d49 ProdID=3005 Rev= 1.00
S: Manufacturer=Maxtor
S: Product=3000LS v01.00.00
S: SerialNumber=DEF10647FBB9
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
sane-find-scanner
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04b8, product=0x0104) at libusb:003:002
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Scanners connected to the parallel port or other proprietary ports
can't be
# detected by this program.
# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
scanimage -L
device `epson:libusb:003:002' is a Epson Perfection1200 flatbed scanner
LmCogs
--------------090808010205010105020404
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi I have installed the kernel 2.6.1-rc1 over Suse 9 and have as far as
I know installed most usb drivers as modules except the scanner.o
module since it is obsolete and I wanted to use libusb. I have an
epson perfection 1200 photo scanner but I can not get it to work
properly. It initialises but then crashes and then scanimage -L does
not recognise it. Xsane also does the same. Below are some of the
programs I use and some config files including sane, xsane, fstab,
dmesg etc. Appreciate some help. Thanks
rpm -q sane
sane-1.0.10-243
rpm -q xsane
xsane-0.91-135
rpm -q hotplug
hotplug-2002_08_26-85
cat /etc/fstab
/dev/hdc1 / ext2
defaults 1 1
/dev/hdc2 /home ext2
defaults 1 2
/dev/hdc3 swap swap
pri=42 0 0
devpts /dev/pts devpts
mode=0620,gid=5 0 0
proc /proc proc
defaults 0 0
none /proc/bus/usb usbfs defaults
0 0
/dev/cdrom /media/cdrom auto
ro,noauto,user,exec 0 0
/dev/dvd /media/dvd auto
ro,noauto,user,exec 0 0
/dev/fd0 /media/floppy auto
noauto,user,sync 0 0
/dev/sr0 /media/sr0 auto ro,noauto,user,exec 0 0
/dev/sda1 /media/sda1 auto sync,noauto,user,exec 0 0
cat /proc/bus/usb/devices
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.2
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=07(print) Sub=01 Prot=02 MxPS=64 #Cfgs= 1
P: Vendor=04b8 ProdID=0001 Rev= 1.00
S: Manufacturer=EPSON
S: Product=USB Printer
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.1
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=04b8 ProdID=0104 Rev= 1.03
S: Manufacturer=EPSON
S: Product=Perfection1200
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.0
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:10.3
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0d49 ProdID=3005 Rev= 1.00
S: Manufacturer=Maxtor
S: Product=3000LS v01.00.00
S: SerialNumber=DEF10647FBB9
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50
Driver=usb-storage
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
sane-find-scanner
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04b8, product=0x0104) at libusb:003:002
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Scanners connected to the parallel port or other proprietary ports
can't be
# detected by this program.
# You may want to run this program as root to find all devices. Once
you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
scanimage -L
device `epson:libusb:003:002' is a Epson Perfection1200 flatbed scanner
LmCogs
--------------090808010205010105020404--
From kladit@t-online.de Sat Jan 17 11:33:05 2004
From: kladit@t-online.de (Klaus Dittrich)
Date: Sat, 17 Jan 2004 12:33:05 +0100
Subject: [sane-devel] re epson perfection 1200 problems libusb kernel 2.6.1-rc1
In-Reply-To: <40089552.9060106@eircom.net>
References: <40089552.9060106@eircom.net>
Message-ID: <20040117113116.GB14513@xeon2.local.here>
On Sat, Jan 17, 2004 at 01:52:18AM +0000, Jim Quigley wrote:
> Hi I have installed the kernel 2.6.1-rc1 over Suse 9 and have as far as
> I know installed most usb drivers as modules except the scanner.o module
> since it is obsolete and I wanted to use libusb. I have an epson
> perfection 1200 photo scanner but I can not get it to work properly. It
> initialises but then crashes and then scanimage -L does not recognise
> it. Xsane also does the same. Below are some of the programs I use and
> some config files including sane, xsane, fstab, dmesg etc. Appreciate
> some help. Thanks
>
>
> rpm -q sane
> sane-1.0.10-243
>
> rpm -q xsane
> xsane-0.91-135
>
> rpm -q hotplug
> hotplug-2002_08_26-85
>
> cat /etc/fstab
> /dev/hdc1 / ext2
> defaults 1 1
> /dev/hdc2 /home ext2
> defaults 1 2
> /dev/hdc3 swap swap
> pri=42 0 0
> devpts /dev/pts devpts
> mode=0620,gid=5 0 0
> proc /proc proc
> defaults 0 0
>
> none /proc/bus/usb usbfs defaults 0 0
> /dev/cdrom /media/cdrom auto
> ro,noauto,user,exec 0 0
> /dev/dvd /media/dvd auto
> ro,noauto,user,exec 0 0
> /dev/fd0 /media/floppy auto
> noauto,user,sync 0 0
> /dev/sr0 /media/sr0 auto ro,noauto,user,exec 0 0
> /dev/sda1 /media/sda1 auto sync,noauto,user,exec 0 0
>
> cat /proc/bus/usb/devices
>
> T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 2.06
> S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
> S: Product=UHCI Host Controller
> S: SerialNumber=0000:00:10.2
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
>
> T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=07(print) Sub=01 Prot=02 MxPS=64 #Cfgs= 1
> P: Vendor=04b8 ProdID=0001 Rev= 1.00
> S: Manufacturer=EPSON
> S: Product=USB Printer
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
> E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>
> T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 2.06
> S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
> S: Product=UHCI Host Controller
> S: SerialNumber=0000:00:10.1
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
>
> T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
> P: Vendor=04b8 ProdID=0104 Rev= 1.03
> S: Manufacturer=EPSON
> S: Product=Perfection1200
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>
> T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 2.06
> S: Manufacturer=Linux 2.6.1-rc1 uhci_hcd
> S: Product=UHCI Host Controller
> S: SerialNumber=0000:00:10.0
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
>
> T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
> B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 2.06
> S: Manufacturer=Linux 2.6.1-rc1 ehci_hcd
> S: Product=EHCI Host Controller
> S: SerialNumber=0000:00:10.3
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
>
> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=0d49 ProdID=3005 Rev= 1.00
> S: Manufacturer=Maxtor
> S: Product=3000LS v01.00.00
> S: SerialNumber=DEF10647FBB9
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
> E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>
>
> sane-find-scanner
>
> # No SCSI scanners found. If you expected something different, make
> sure that
> # you have loaded a SCSI driver for your SCSI adapter.
>
> found USB scanner (vendor=0x04b8, product=0x0104) at libusb:003:002
> # Your USB scanner was (probably) detected. It may or may not be
> supported by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> # Scanners connected to the parallel port or other proprietary ports
> can't be
> # detected by this program.
>
> # You may want to run this program as root to find all devices. Once you
> # found the scanner devices, be sure to adjust access permissions as
> # necessary.
>
>
> scanimage -L
> device `epson:libusb:003:002' is a Epson Perfection1200 flatbed scanner
>
> LmCogs
Same here.
Is your machine smp ?
Do you have preemptive syscalls enabeld ?
Do you use linuxthreads or nptl ?
If you need a quick fix use the kernel scanner-driver of linux-2.6,
_not_ libusb, and install backends-1.0.12.
I tested backends-1.0.12 with libusb and it may damage the mechanics of your epson-scanner.
--
Klaus
From khk@khk.net Sat Jan 17 12:27:05 2004
From: khk@khk.net (Karl Heinz Kremer)
Date: Sat, 17 Jan 2004 07:27:05 -0500
Subject: [sane-devel] re epson perfection 1200 problems libusb kernel 2.6.1-rc1
In-Reply-To: <20040117113116.GB14513@xeon2.local.here>
References: <40089552.9060106@eircom.net> <20040117113116.GB14513@xeon2.local.here>
Message-ID: <75C3A852-48E8-11D8-A5BE-000A957E40E8@khk.net>
On Jan 17, 2004, at 6:33 AM, Klaus Dittrich wrote:
[ ... ]
> I tested backends-1.0.12 with libusb and it may damage the mechanics
> of your epson-scanner.
>
It's actually very unlikely that you will damage your scanner if you
have a "real" EPSON scanner (that is one that is natively supported by
the EPSON backend). The hardware is not controlled directly by the
commands that the backend sends to the device. There are no commands to
position any of the moving parts directly, you just tell the scanner
how and what to scan, and the scanner firmware then calculates the
commands it sends to the motors. You have this one additional layer
that protects the hardware from the user (or my software :-) Other
scanners allow the frontend to control the motors directly, this is
much more dangerous.
From nicos@svinomatka.ru Sat Jan 17 12:29:06 2004
From: nicos@svinomatka.ru (Nikanorov Andrey)
Date: Sat, 17 Jan 2004 15:29:06 +0300
Subject: [sane-devel] Mustek 1200 UB Plus
Message-ID: <1074342546.4347.5.camel@localhost.localdomain>
Is it posible to configure Mustek 1200 UB Plus scanner?
When I run XSane I see an error (unable to open device
'gt68xx:/dev/usb/scanner0').
When I run scanimage:
[root@localhost root]# scanimage -L
device `gt68xx:/dev/usb/scanner0' is a Mustek BearPaw 1200 CU flatbed
scanner
From henning@meier-geinitz.de Sat Jan 17 15:26:22 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 17 Jan 2004 16:26:22 +0100
Subject: [sane-devel] Mustek 1200 UB Plus
In-Reply-To: <1074342546.4347.5.camel@localhost.localdomain>
References: <1074342546.4347.5.camel@localhost.localdomain>
Message-ID: <20040117152622.GB5434@meier-geinitz.de>
Hi,
On Sat, Jan 17, 2004 at 03:29:06PM +0300, Nikanorov Andrey wrote:
> Is it posible to configure Mustek 1200 UB Plus scanner?
Yes, see man sane-gt68xx.
> When I run XSane I see an error (unable to open device
> 'gt68xx:/dev/usb/scanner0').
>
>
> When I run scanimage:
>
> [root@localhost root]# scanimage -L
> device `gt68xx:/dev/usb/scanner0' is a Mustek BearPaw 1200 CU flatbed
> scanner
The firmware is placed in the right directory and you have enabled the
override for that scanner in gt68xx.conf?
Bye,
Henning
From jimquigley9@eircom.net Sat Jan 17 14:15:08 2004
From: jimquigley9@eircom.net (Jim Quigley)
Date: Sat, 17 Jan 2004 14:15:08 +0000
Subject: [sane-devel] re epson perfection 1200 problems libusb kernel 2.6.1-rc1
Message-ID: <4009436C.1080901@eircom.net>
Klaus Dittrich wrote:
> Same here.
> Is your machine smp ?
> Do you have preemptive syscalls enabeld ?
> Do you use linuxthreads or nptl ?
>
> If you need a quick fix use the kernel scanner-driver of linux-2.6,
> _not_ libusb, and install backends-1.0.12.
> I tested backends-1.0.12 with libusb and it may damage the mechanics
> of your epson-scanner.
>
> --
> Klaus
>
>
>
>
> Hi Don't know what 'smp' or linuxthreads' 'nptl' are but I did compile
> the kernel with preemptive kernel.
>
>
I recompiled the kernel with ISA support enabled and i20 device support
but I still got errors like
scanimage -d epson:libusb:003:002 --test scanimage: scanning image of
size 424x584 pixels at 1 bits/pixel
scanimage: acquiring gray frame, 1 bits/sample
scanimage: reading one scanline, 53 bytes...
FAIL Error: Error during device I/O[epson] option: fatal error
I also had tried before loading scanner.o driver and that worked when I
used 'modprobe scanner' but I then had problems with epson printer usblp
and hotplug could not unload the module when closing down. I now have
printer compiled into the kernel not as a module and I did not choose
the scanner module which it says is obsolete.
LmCogs
From henning@meier-geinitz.de Sat Jan 17 15:58:45 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 17 Jan 2004 16:58:45 +0100
Subject: [sane-devel] re epson perfection 1200 problems libusb kernel 2.6.1-rc1
In-Reply-To: <4009436C.1080901@eircom.net>
References: <4009436C.1080901@eircom.net>
Message-ID: <20040117155845.GB6163@meier-geinitz.de>
Hi,
On Sat, Jan 17, 2004 at 02:15:08PM +0000, Jim Quigley wrote:
> Klaus Dittrich wrote:
>
> >Is your machine smp ?
> >Do you have preemptive syscalls enabeld ?
> >Do you use linuxthreads or nptl ?
I don't think that linuxthreads or nptl is involved as by default SANE
uses processes (fork), not threads.
>Hi Don't know what 'smp'
SMP: Symmetric MultiProcessing = more than one processor.
> or linuxthreads' 'nptl' are
These are two different ways of using threads.
> but I did compile the kernel with preemptive kernel.
I suspect that this may be a possible reason for your problems. Also
SMP may be a reason. I'll now try 2.6 with some of these options
enabled.
> scanimage -d epson:libusb:003:002 --test scanimage: scanning image of
> size 424x584 pixels at 1 bits/pixel
> scanimage: acquiring gray frame, 1 bits/sample
> scanimage: reading one scanline, 53 bytes...
> FAIL Error: Error during device I/O[epson] option: fatal error
The kernel messages that occur when the scan fails for the first time
may be important (e.g. in /var/log/messages).
> I also had tried before loading scanner.o driver and that worked when I
> used 'modprobe scanner' but I then had problems with epson printer usblp
> and hotplug could not unload the module when closing down. I now have
> printer compiled into the kernel not as a module and I did not choose
> the scanner module which it says is obsolete.
The scanner module should also work but may have the same problems as
libusb with SMP and/or preemptible kernel.
Bye,
Henning
From henning@meier-geinitz.de Sat Jan 17 16:06:17 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 17 Jan 2004 17:06:17 +0100
Subject: [sane-devel] Mustek 1200 UB Plus
In-Reply-To: <1074355051.6126.7.camel@localhost.localdomain>
References: <1074342546.4347.5.camel@localhost.localdomain> <20040117152622.GB5434@meier-geinitz.de> <1074355051.6126.7.camel@localhost.localdomain>
Message-ID: <20040117160617.GC6163@meier-geinitz.de>
Hi,
I'm cc'ing to the mailing list just in case anyone has the same problem.
On Sat, Jan 17, 2004 at 06:57:31PM +0300, Nikanorov Andrey wrote:
> I've solved my problem.
>
> I am getting SBfw.usb file from CDROM (from scanner
> disk[file:/mnt/cdrom/WinXP]). After I create directory 'gt68xx' in
> '/usr/share/sane/' and put file
> (SBfw.usb) in it. Then I renamed SBfw.usb to PS1fw.usb.
This is an ugly hack but it may work in this case.
Explanation: There are some different scanners which all use the same
USB ids and they aren't distinguishable from each other by software.
They also use different firmware files.
That's why there are "override" directives in gt68xx.conf.
By default it's assumed that you have a Mustek BearPaw 1200 CU and
that one uses the firmware "PS1fw.usb". That's why the backend uses
that name. If you had enabled the override
"mustek-scanexpress-1200-ub-plus", it would search for sbfw.usb and
the correct scanner name would be displayed.
Bye,
Henning
From henning@meier-geinitz.de Sat Jan 17 18:01:26 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 17 Jan 2004 19:01:26 +0100
Subject: [sane-devel] linux-2.6.1-smp,usb,oops,sane-backends-1.0.13,epson-1640
In-Reply-To: <20040115172800.GA648@xeon2.local.here>
References: <20040115172800.GA648@xeon2.local.here>
Message-ID: <20040117180126.GB659@meier-geinitz.de>
Hi,
On Thu, Jan 15, 2004 at 06:28:00PM +0100, Klaus Dittrich wrote:
> linux-2.6.1-smp,usb,oops,sane-backends-1.0.13,epson-1640
[oops]
Ok, some tests on my system with linux 2.6.1 and some Mustek USB
scanners:
- no problems with libusb
- with the kernel scanner driver, I get an oops when unplugging a
scanner
- with the kernel scanner driver and "preemptible kernel" I get an
oops when running scanimage -L
So I guess for now the kernel scanner driver in 2.6 isn't really
usable. It's marked "obsolete" anyway so better use libusb.
Bye,
Henning
From till.kamppeter@gmx.net Sat Jan 17 20:04:40 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Sat, 17 Jan 2004 20:04:40 +0000
Subject: [sane-devel] linux-2.6.1-smp,usb,oops,sane-backends-1.0.13,epson-1640
In-Reply-To: <20040117180126.GB659@meier-geinitz.de>
References: <20040115172800.GA648@xeon2.local.here> <20040117180126.GB659@meier-geinitz.de>
Message-ID: <40099558.9010208@gmx.net>
Is there a way to block the usage of the scanner.o module by means of
the SAME package (compile-time config or so)? Or is it the best to ask
our kernel maintainer to make a kernel package without scanner.o? Is it
safe to publish a distro (Mandrake Linux 10.0) without scanner.o in its
kernel? Would I loose compatibility for certain scanner models or not?
And does the oops only appear with the SMP kernel 2.6.x or also with the
standard kernel 2.6.x.
Till
Henning Meier-Geinitz wrote:
> Hi,
>
> On Thu, Jan 15, 2004 at 06:28:00PM +0100, Klaus Dittrich wrote:
>
>>linux-2.6.1-smp,usb,oops,sane-backends-1.0.13,epson-1640
>
>
> [oops]
>
> Ok, some tests on my system with linux 2.6.1 and some Mustek USB
> scanners:
>
> - no problems with libusb
> - with the kernel scanner driver, I get an oops when unplugging a
> scanner
> - with the kernel scanner driver and "preemptible kernel" I get an
> oops when running scanimage -L
>
> So I guess for now the kernel scanner driver in 2.6 isn't really
> usable. It's marked "obsolete" anyway so better use libusb.
>
> Bye,
>
> Henning
>
From henning@meier-geinitz.de Sat Jan 17 21:22:41 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 17 Jan 2004 22:22:41 +0100
Subject: [sane-devel] linux-2.6.1-smp,usb,oops,sane-backends-1.0.13,epson-1640
In-Reply-To: <40099558.9010208@gmx.net>
References: <20040115172800.GA648@xeon2.local.here> <20040117180126.GB659@meier-geinitz.de> <40099558.9010208@gmx.net>
Message-ID: <20040117212241.GD659@meier-geinitz.de>
Hi,
On Sat, Jan 17, 2004 at 08:04:40PM +0000, Till Kamppeter wrote:
> Is there a way to block the usage of the scanner.o module by means of
> the SAME package (compile-time config or so)?
No and that wouldn't help. When the kernel scanner driver is loaded,
it claims the USB devices it knows. libusb can't access them in this
case.
> Or is it the best to ask
> our kernel maintainer to make a kernel package without scanner.o? Is it
> safe to publish a distro (Mandrake Linux 10.0) without scanner.o in its
> kernel? Would I loose compatibility for certain scanner models or not?
To my knowledge, every scanner that works with the scanner module also
works with libusb. But this is only true for SANE, I don't know if
it's the same for other software like vuescan.
If that's possible I would include the scanner driver, but not load it
by default. So if the user really needs it, he can load it. I have no
idea how to do that with hotplug, however.
> And does the oops only appear with the SMP kernel 2.6.x or also with the
> standard kernel 2.6.x.
There seem to be two oopses (maybe related): One that happens on
unplugging a scanner. That one happens also without SMP and without
preemtible kernel.
The other one that seems to accour when a scanner is accessed (e.g.
scanimage -L) only occurs with preemption turned on. I haven't tested
SMP.
I can't reproduce any of the libusb problems but I use different
scanners.
Bye,
Henning
From neundorf@kde.org Sun Jan 18 11:28:59 2004
From: neundorf@kde.org (Alexander Neundorf)
Date: Sun, 18 Jan 2004 12:28:59 +0100
Subject: [sane-devel] Question about the Canon Lide 30 behaviour
Message-ID: <200401181228.59012.neundorf@kde.org>
Hi,
since some weeks I have a Canon Lide 30 scanner and everything works well.
I have sane 1.0.13 installed.
The only question I have is the following:
when I start scanning (full or preview) the scanner starts doing some stuff,
which takes several seconds, maybe up to 20 seconds or something, and after
this it actually starts scanning, i.e. the scan line starts to move.
What is it what is happening at the beginning ? Is this some kind of
calibration ? Maybe white reference ?
Is it required that this is done before every single scan ?
Bye
Alex
--
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org - http://www.kde.org
alex@neundorf.net - http://www.neundorf.net
From gerhard@gjaeger.de Sun Jan 18 12:12:29 2004
From: gerhard@gjaeger.de (Jaeger, Gerhard)
Date: Sun, 18 Jan 2004 13:12:29 +0100
Subject: [sane-devel] linux-2.6.1-smp,usb,oops,sane-backends-1.0.13,epson-1640
In-Reply-To: <20040117212241.GD659@meier-geinitz.de>
References: <20040115172800.GA648@xeon2.local.here> <40099558.9010208@gmx.net> <20040117212241.GD659@meier-geinitz.de>
Message-ID: <200401181312.29525.gerhard@gjaeger.de>
Hi,
On Samstag, 17. Januar 2004 22:22, Henning Meier-Geinitz wrote:
> Hi,
>
> On Sat, Jan 17, 2004 at 08:04:40PM +0000, Till Kamppeter wrote:
> > Is there a way to block the usage of the scanner.o module by means of
> > the SAME package (compile-time config or so)?
>
> No and that wouldn't help. When the kernel scanner driver is loaded,
> it claims the USB devices it knows. libusb can't access them in this
> case.
>
> > Or is it the best to ask
> > our kernel maintainer to make a kernel package without scanner.o? Is it
> > safe to publish a distro (Mandrake Linux 10.0) without scanner.o in its
> > kernel? Would I loose compatibility for certain scanner models or not?
>
> To my knowledge, every scanner that works with the scanner module also
> works with libusb. But this is only true for SANE, I don't know if
> it's the same for other software like vuescan.
AFAIK vuescan works only with the scanner module.
> If that's possible I would include the scanner driver, but not load it
> by default. So if the user really needs it, he can load it. I have no
> idea how to do that with hotplug, however.
Using hotplug, you should add the scanner module to the "blacklist" file
in /etc/hotplug
> > And does the oops only appear with the SMP kernel 2.6.x or also with the
> > standard kernel 2.6.x.
>
> There seem to be two oopses (maybe related): One that happens on
> unplugging a scanner. That one happens also without SMP and without
> preemtible kernel.
>
> The other one that seems to accour when a scanner is accessed (e.g.
> scanimage -L) only occurs with preemption turned on. I haven't tested
> SMP.
Probably you need to some spinlocks to protect the driver from being scheduled
in some cases!?
If I find some time, I'll check that...
Ciao,
Gerhard
> I can't reproduce any of the libusb problems but I use different
> scanners.
>
> Bye,
> Henning
From gerhard@gjaeger.de Sun Jan 18 12:16:19 2004
From: gerhard@gjaeger.de (Jaeger, Gerhard)
Date: Sun, 18 Jan 2004 13:16:19 +0100
Subject: [sane-devel] Question about the Canon Lide 30 behaviour
In-Reply-To: <200401181228.59012.neundorf@kde.org>
References: <200401181228.59012.neundorf@kde.org>
Message-ID: <200401181316.19815.gerhard@gjaeger.de>
Hi,
On Sonntag, 18. Januar 2004 12:28, Alexander Neundorf wrote:
[SNIPSNAP]
> when I start scanning (full or preview) the scanner starts doing some
> stuff, which takes several seconds, maybe up to 20 seconds or something,
> and after this it actually starts scanning, i.e. the scan line starts to
> move.
>
> What is it what is happening at the beginning ? Is this some kind of
> calibration ? Maybe white reference ?
> Is it required that this is done before every single scan ?
What you see is the calibration step. It consists of two parts:
- coarse calibration
- fine calibration
In the end, the fine calibration needs to be done for each scan-step, the
coarse calibration only for each scan-mode. The backend contains a
configuratation switch (in plustek.conf), called
option cacheCalData
Try and set this to 1 and see if this helps. It should save the
coarse-calibration results and reuse it. This feature is not very well
tested...
Ciao,
Gerhard
From jesper@pobox.com Sun Jan 18 14:38:53 2004
From: jesper@pobox.com (Jesper Anderson)
Date: Sun, 18 Jan 2004 15:38:53 +0100
Subject: [sane-devel] xsane and Gimp 2.0
Message-ID: <20040118143853.GA13079@acheron.the-domination.com>
Is it possible to compile xsane 0.92 against the Gimp 2.0 prerelease?
I use this version exclusively, and it would be very nice to have
xsane integrated in it.
Thanks in advance,
Jesper
From jb@jblache.org Sun Jan 18 15:56:33 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sun, 18 Jan 2004 16:56:33 +0100
Subject: [sane-devel] xsane and Gimp 2.0
In-Reply-To: <20040118143853.GA13079@acheron.the-domination.com> (Jesper
Anderson's message of "Sun, 18 Jan 2004 15:38:53 +0100")
References: <20040118143853.GA13079@acheron.the-domination.com>
Message-ID: <87d69h8d3i.fsf@frigate.technologeek.org>
Jesper Anderson wrote:
Hi,
> Is it possible to compile xsane 0.92 against the Gimp 2.0 prerelease?
> I use this version exclusively, and it would be very nice to have
> xsane integrated in it.
Yes, it is, with this patch that a few debian users have been using
for the past months :
Apply to a clean source tree with patch -p1, run configure, build. It
defaults to GTK2+GIMP2.0. (you don't need to run autoconf)
WARNING: the autoconf check that comes with GIMP 2.0 expects version
strings of the form x.y.z, and GIMP 2.0 pre-versions have a version
string of the form 2.0preX, so the check barfs.
You'll have to edit either gimptool or the .pc file for GIMP 2.0 so
that they return 2.0.0 as the version string.
Oliver, this is the patch I wanted to send you, so feel free to take a
look at it :)
JB.
--
Julien BLACHE
GPG KeyID 0xF5D65169
From leoncogs@eircom.net Sun Jan 18 18:35:55 2004
From: leoncogs@eircom.net (Lm Cogs)
Date: Sun, 18 Jan 2004 18:35:55 +0000
Subject: [sane-devel] re epson percection 1200 problems libusb kernel 2.6.1-rc1
Message-ID: <200401181835.55840.leoncogs@eircom.net>
Well Its a success at last
I tried without smp amd preemting complied but it was no success, then as you
suggeste I looked in var/log/messages. and it seemed to suggest that it was
looking for a module usbcore. I recompiled the kernel with a the option for
'support for usb' chosen to be compiled as a module. The scanner now works.
I used xsane and all went well. I also change a line in fstab but I don't
think this made a difference.
When I get time I will try recompiling the kernel with 'preemptible kernel', I
don't think I need smp.
I would appeciate it if you take a look at my fstab and var/log/message files
below
I guess I don't need to set permission in epson_scanner if I set it in fstab
globally. Another question where do I go to set up libusb and epson printer,
it works if i modprobe usblp and then set it up in Yast?
fstab
/dev/hdc1 / ext2 defaults 1 1
/dev/hdc2 /home ext2 defaults 1 2
/dev/hdc3 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
none /proc/bus/usb usbfs devmode=0666 0 0
usbfs /proc/bus/usb usbfs defautls,noauto 0 0
/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
/dev/dvd /media/dvd auto ro,noauto,user,exec 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
/dev/sr0 /media/sr0 auto ro,noauto,user,exec 0 0
/dev/sda1 /media/sda1 auto sync,noauto,user,exec 0 0
/var/log/messages
Jan 18 16:35:33 desktop syslogd 1.4.1: restart.
Jan 18 16:35:35 desktop /sbin/hotplug[692]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:35:35 desktop /etc/hotplug/usb.rc[681]: loaded HCD: ehci-hcd
Jan 18 16:35:35 desktop /etc/hotplug/usb.rc[681]: loaded HCD: ohci-hcd
Jan 18 16:35:35 desktop /sbin/hotplug[733]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:35:35 desktop /sbin/hotplug[772]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:35:35 desktop /sbin/hotplug[811]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:35:35 desktop /etc/hotplug/usb.rc[681]: loaded HCD: uhci-hcd
Jan 18 16:35:35 desktop /etc/hotplug/usb.rc[681]: loaded HCD: ehci-hcd
Jan 18 16:35:35 desktop /etc/hotplug/usb.rc[681]: FATAL: Module mousedev not
found.
Jan 18 16:35:35 desktop /etc/hotplug/usb.rc[681]: FATAL: Module keybdev not
found.
Jan 18 16:35:35 desktop /etc/hotplug/usb.rc[681]: FATAL: Module printer not
found.
Jan 18 16:35:38 desktop /etc/hotplug/usb.agent[895]: Bad USB agent invocation
Jan 18 16:35:38 desktop kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 18 16:35:38 desktop kernel: Inspecting /boot/System.map-2.6.1-rc1
Jan 18 16:35:38 desktop kernel: Loaded 24789 symbols from /boot/
System.map-2.6.1-rc1.
Jan 18 16:35:38 desktop kernel: Symbols match kernel version 2.6.1.
Jan 18 16:35:38 desktop kernel: No module symbols loaded - kernel modules not
enabled.
Jan 18 16:35:38 desktop kernel: eth0: link down
Jan 18 16:35:38 desktop kernel: NET: Registered protocol family 17
Jan 18 16:35:38 desktop kernel: raw1394: /dev/raw1394 device initialized
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: registered new driver
usbfs
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: registered new driver
hub
Jan 18 16:35:38 desktop kernel: ehci_hcd: block sizes: qh 128 qtd 96 itd 128
sitd 64
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: EHCI Host Controller
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: reset hcs_params 0x3206
dbg=0 cc=3 pcc=2 ordered !ppc ports=6
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: reset hcc_params 6872
thresh 7 uframes 256/512/1024
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: capability 0001 at 68
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: irq 21, pci mem
e089d000
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: new USB bus registered,
assigned bus number 1
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: reset command 080002
(park)=0 ithresh=8 period=1024 Reset HALT
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: init command 010009
(park)=0 ithresh=1 period=256 RUN
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI
1.00, driver 2003-Jun-13
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: root hub device address
1
Jan 18 16:35:38 desktop kernel: usb usb1: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:35:38 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:35:38 desktop kernel: usb usb1: Product: EHCI Host Controller
Jan 18 16:35:38 desktop kernel: usb usb1: Manufacturer: Linux 2.6.1-rc1
ehci_hcd
Jan 18 16:35:38 desktop kernel: usb usb1: SerialNumber: 0000:00:10.3
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: usb usb1: registering 1-0:1.0 (config #1,
interface 0)
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: usb_probe_interface
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: usb_probe_interface - got id
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: USB hub found
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: 6 ports detected
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: standalone hub
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: ganged power switching
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: individual port over-current
protection
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: Single TT
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: TT requires at most 8 FS bit
times
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: Port indicators are not supported
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: power on to power good time: 0ms
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: local power source is good
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: no over-current condition exists
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: enabling power on all ports
Jan 18 16:35:38 desktop kernel: ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host
Controller (OHCI) Driver (PCI)
Jan 18 16:35:38 desktop kernel: ohci_hcd: block sizes: ed 64 td 64
Jan 18 16:35:38 desktop kernel: drivers/usb/host/uhci-hcd.c: USB Universal
Host Controller Interface driver v2.1
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.0: UHCI Host Controller
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.0: irq 21, io base
0000d400
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.0: new USB bus registered,
assigned bus number 2
Jan 18 16:35:38 desktop kernel: drivers/usb/host/uhci-hcd.c: detected 2 ports
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.0: root hub device address
1
Jan 18 16:35:38 desktop kernel: usb usb2: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:35:38 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:35:38 desktop kernel: usb usb2: Product: UHCI Host Controller
Jan 18 16:35:38 desktop kernel: usb usb2: Manufacturer: Linux 2.6.1-rc1
uhci_hcd
Jan 18 16:35:38 desktop kernel: usb usb2: SerialNumber: 0000:00:10.0
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: usb usb2: registering 2-0:1.0 (config #1,
interface 0)
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: usb_probe_interface
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: usb_probe_interface - got id
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: USB hub found
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: 2 ports detected
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: standalone hub
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: ganged power switching
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: global over-current protection
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: Port indicators are not supported
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: power on to power good time: 2ms
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: local power source is good
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: no over-current condition exists
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: enabling power on all ports
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.1: UHCI Host Controller
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
001803 POWER sig=j CSC CONNECT
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: port 5, status 501, change 1, 480
Mb/s
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.1: irq 21, io base
0000d800
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.1: new USB bus registered,
assigned bus number 3
Jan 18 16:35:38 desktop kernel: drivers/usb/host/uhci-hcd.c: detected 2 ports
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.1: root hub device address
1
Jan 18 16:35:38 desktop kernel: usb usb3: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:35:38 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:35:38 desktop kernel: usb usb3: Product: UHCI Host Controller
Jan 18 16:35:38 desktop kernel: usb usb3: Manufacturer: Linux 2.6.1-rc1
uhci_hcd
Jan 18 16:35:38 desktop kernel: usb usb3: SerialNumber: 0000:00:10.1
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: usb usb3: registering 3-0:1.0 (config #1,
interface 0)
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: usb_probe_interface
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: usb_probe_interface - got id
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: USB hub found
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: 2 ports detected
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: standalone hub
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: ganged power switching
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: global over-current protection
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: Port indicators are not supported
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: power on to power good time: 2ms
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: local power source is good
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: no over-current condition exists
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: enabling power on all ports
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.2: UHCI Host Controller
Jan 18 16:35:38 desktop kernel: hub 1-0:1.0: debounce: port 5: delay 100ms
stable 4 status 0x501
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.2: irq 21, io base
0000dc00
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.2: new USB bus registered,
assigned bus number 4
Jan 18 16:35:38 desktop kernel: drivers/usb/host/uhci-hcd.c: detected 2 ports
Jan 18 16:35:38 desktop kernel: uhci_hcd 0000:00:10.2: root hub device address
1
Jan 18 16:35:38 desktop kernel: usb usb4: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:35:38 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:35:38 desktop kernel: usb usb4: Product: UHCI Host Controller
Jan 18 16:35:38 desktop kernel: usb usb4: Manufacturer: Linux 2.6.1-rc1
uhci_hcd
Jan 18 16:35:38 desktop kernel: usb usb4: SerialNumber: 0000:00:10.2
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: port 5 full speed -->
companion
Jan 18 16:35:38 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
003801 POWER OWNER sig=j CONNECT
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: port 1, status 100, change 3, 12
Mb/s
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: port 2, status 100, change 3, 12
Mb/s
Jan 18 16:35:38 desktop kernel: usb usb4: registering 4-0:1.0 (config #1,
interface 0)
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: usb_probe_interface
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: usb_probe_interface - got id
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: USB hub found
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: 2 ports detected
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: standalone hub
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: ganged power switching
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: global over-current protection
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: Port indicators are not supported
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: power on to power good time: 2ms
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: local power source is good
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: no over-current condition exists
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: enabling power on all ports
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: port 1, status 100, change 3, 12
Mb/s
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: port 2, status 100, change 3, 12
Mb/s
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: port 1 enable change, status 100
Jan 18 16:35:38 desktop kernel: hub 2-0:1.0: port 2 enable change, status 100
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: port 1, status 101, change 3, 12
Mb/s
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: debounce: port 1: delay 100ms
stable 4 status 0x101
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: new USB device on port 1,
assigned address 2
Jan 18 16:35:38 desktop kernel: usb 4-1: new device strings: Mfr=1, Product=2,
SerialNumber=0
Jan 18 16:35:38 desktop kernel: drivers/usb/core/message.c: USB device number
2 default language ID 0x409
Jan 18 16:35:38 desktop kernel: usb 4-1: Product: USB Printer
Jan 18 16:35:38 desktop kernel: usb 4-1: Manufacturer: EPSON
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: usb 4-1: registering 4-1:1.0 (config #1,
interface 0)
Jan 18 16:35:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: port 2, status 100, change 3, 12
Mb/s
Jan 18 16:35:38 desktop kernel: hub 4-0:1.0: port 2 enable change, status 100
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: port 1 enable change, status 100
Jan 18 16:35:38 desktop kernel: hub 3-0:1.0: port 2 enable change, status 100
Jan 18 16:35:38 desktop kernel: drivers/usb/host/uhci-hcd.c: d400: suspend_hc
Jan 18 16:35:38 desktop kernel: drivers/usb/host/uhci-hcd.c: d800: suspend_hc
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:35:41 desktop /etc/hotplug/usb.agent[942]: Bad USB agent invocation
Jan 18 16:35:43 desktop modprobe: FATAL: Module battery not found.
Jan 18 16:35:43 desktop kernel: via82xx: Assuming DXS channels with 48k fixed
sample rate.
Jan 18 16:35:43 desktop kernel: Please try dxs_support=1 option and
report if it works on your machine.
Jan 18 16:35:43 desktop kernel: PCI: Setting latency timer of device
0000:00:11.5 to 64
Jan 18 16:35:44 desktop kernel: ACPI: Power Button (FF) [PWRF]
Jan 18 16:35:44 desktop kernel: ACPI: Processor [CPU0] (supports C1 C2, 2
throttling states)
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: modules.usbmap
unparsable line:
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: .
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: modules.usbmap
unparsable line:
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: .
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: modules.usbmap
unparsable line:
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: .
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: modules.usbmap
unparsable line:
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1060]: .
Jan 18 16:35:44 desktop /etc/hotplug/usb.agent[1099]: Bad USB agent invocation
Jan 18 16:35:44 desktop smpppd[1021]: smpppd version 1.06 started
Jan 18 16:35:44 desktop kernel: NET: Registered protocol family 10
Jan 18 16:35:45 desktop kernel: Disabled Privacy Extensions on device c0386e20
(lo)
Jan 18 16:35:45 desktop kernel: IPv6 over IPv4 tunneling driver
Jan 18 16:35:45 desktop sshd[1106]: Server listening on :: port 22.
Jan 18 16:35:45 desktop kernel: request_module: failed /sbin/modprobe --
snd-card-1. error = 256
Jan 18 16:35:47 desktop kernel: parport0: PC-style at 0x378 [PCSPP(,...)]
Jan 18 16:35:47 desktop kernel: lp0: using parport0 (polling).
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: modules.usbmap
unparsable line:
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: .
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: modules.usbmap
unparsable line:
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: .
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: modules.usbmap
unparsable line:
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: .
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: modules.usbmap
unparsable line:
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1309]: .
Jan 18 16:35:47 desktop /etc/hotplug/usb.agent[1354]: Bad USB agent invocation
Jan 18 16:35:48 desktop kernel: request_module: failed /sbin/modprobe --
char-major-4-72. error = 256
Jan 18 16:35:48 desktop /usr/sbin/cron[1481]: (CRON) STARTUP (fork ok)
Jan 18 16:35:49 desktop kernel: drivers/usb/serial/usb-serial.c: USB Serial
support registered for Generic
Jan 18 16:35:49 desktop kernel: usbserial 4-1:1.0: usb_probe_interface
Jan 18 16:35:49 desktop kernel: usbserial 4-1:1.0: usb_probe_interface - got
id
Jan 18 16:35:49 desktop kernel: drivers/usb/core/usb.c: registered new driver
usbserial
Jan 18 16:35:49 desktop kernel: drivers/usb/serial/usb-serial.c: USB Serial
Driver core v2.0
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: modules.usbmap
unparsable line:
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: .
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: modules.usbmap
unparsable line:
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: .
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: modules.usbmap
unparsable line:
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: .
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: modules.usbmap
unparsable line:
Jan 18 16:35:50 desktop /etc/hotplug/usb.agent[1572]: .
Jan 18 16:35:53 desktop kernel: request_module: failed /sbin/modprobe --
char-major-195-255. error = 256
Jan 18 16:35:54 desktop modprobe: FATAL: Module printer not found.
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: modules.usbmap
unparsable line:
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: .
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: modules.usbmap
unparsable line:
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: .
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: modules.usbmap
unparsable line:
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: .
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: modules.usbmap
unparsable line:
Jan 18 16:35:54 desktop /etc/hotplug/usb.agent[1651]: .
Jan 18 16:35:54 desktop kdm[1643]: IO Error in XOpenDisplay
Jan 18 16:35:54 desktop kdm[1617]: Server for display :0 terminated
unexpectedly
Jan 18 16:35:55 desktop kernel: eth0: no IPv6 routers present
Jan 18 16:35:55 desktop kernel: request_module: failed /sbin/modprobe --
char-major-195-255. error = 256
Jan 18 16:35:56 desktop kdm[1694]: IO Error in XOpenDisplay
Jan 18 16:35:56 desktop kdm[1617]: Server for display :0 terminated
unexpectedly
Jan 18 16:35:56 desktop kdm[1617]: Display :0 cannot be opened
Jan 18 16:35:56 desktop kernel: request_module: failed /sbin/modprobe --
char-major-195-255. error = 256
Jan 18 16:35:57 desktop kdm[1703]: IO Error in XOpenDisplay
Jan 18 16:35:57 desktop kdm[1617]: Server for display :0 terminated
unexpectedly
Jan 18 16:35:57 desktop kdm[1617]: Display :0 cannot be opened
Jan 18 16:35:57 desktop /etc/hotplug/usb.agent[1716]: Bad USB agent invocation
Jan 18 16:35:57 desktop kernel: request_module: failed /sbin/modprobe --
char-major-195-255. error = 256
Jan 18 16:35:58 desktop kdm[1712]: IO Error in XOpenDisplay
Jan 18 16:35:58 desktop kdm[1617]: Server for display :0 terminated
unexpectedly
Jan 18 16:35:58 desktop kdm[1617]: Display :0 cannot be opened
Jan 18 16:35:58 desktop kdm[1617]: Display :0 is being disabled (restarting
too fast)
Jan 18 16:36:17 desktop login[1636]: FAILED LOGIN 1 FROM /dev/tty1 FOR
UNKNOWN, User not known to the underlying authentication module
Jan 18 16:38:35 desktop kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan 18 16:41:28 desktop init: Switching to runlevel: 6
Jan 18 16:41:34 desktop sshd[1106]: Received signal 15; terminating.
Jan 18 16:41:34 desktop smpppd[1130]: terminating on signal 15
Jan 18 16:41:34 desktop kernel: request_module: failed /sbin/modprobe --
snd-card-1. error = 256
Jan 18 16:41:35 desktop kernel: drivers/usb/serial/usb-serial.c: USB Serial
deregistering driver Generic
Jan 18 16:41:35 desktop kernel: drivers/usb/core/usb.c: deregistering driver
usbserial
Jan 18 16:41:35 desktop kernel: Kernel logging (proc) stopped.
Jan 18 16:41:35 desktop kernel: Kernel log daemon terminating.
Jan 18 16:41:36 desktop exiting on signal 15
Jan 18 16:44:11 desktop syslogd 1.4.1: restart.
Jan 18 16:44:13 desktop /sbin/hotplug[692]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:44:13 desktop /etc/hotplug/usb.rc[681]: loaded HCD: ehci-hcd
Jan 18 16:44:13 desktop /etc/hotplug/usb.rc[681]: loaded HCD: ohci-hcd
Jan 18 16:44:13 desktop /sbin/hotplug[733]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:44:13 desktop /sbin/hotplug[772]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:44:13 desktop /sbin/hotplug[811]: no runnable /etc/hotplug/
usb_host.agent is installed
Jan 18 16:44:13 desktop /etc/hotplug/usb.rc[681]: loaded HCD: uhci-hcd
Jan 18 16:44:13 desktop /etc/hotplug/usb.rc[681]: loaded HCD: ehci-hcd
Jan 18 16:44:13 desktop /etc/hotplug/usb.rc[681]: FATAL: Module mousedev not
found.
Jan 18 16:44:14 desktop /etc/hotplug/usb.rc[681]: FATAL: Module keybdev not
found.
Jan 18 16:44:14 desktop /etc/hotplug/usb.rc[681]: FATAL: Module printer not
found.
Jan 18 16:44:16 desktop /etc/hotplug/usb.agent[895]: Bad USB agent invocation
Jan 18 16:44:16 desktop kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 18 16:44:16 desktop kernel: Inspecting /boot/System.map-2.6.1-rc1
Jan 18 16:44:17 desktop kernel: Loaded 24789 symbols from /boot/
System.map-2.6.1-rc1.
Jan 18 16:44:17 desktop kernel: Symbols match kernel version 2.6.1.
Jan 18 16:44:17 desktop kernel: No module symbols loaded - kernel modules not
enabled.
Jan 18 16:44:17 desktop kernel: eth0: link down
Jan 18 16:44:17 desktop kernel: NET: Registered protocol family 17
Jan 18 16:44:17 desktop kernel: raw1394: /dev/raw1394 device initialized
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: registered new driver
usbfs
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: registered new driver
hub
Jan 18 16:44:17 desktop kernel: ehci_hcd: block sizes: qh 128 qtd 96 itd 128
sitd 64
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: EHCI Host Controller
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: reset hcs_params 0x3206
dbg=0 cc=3 pcc=2 ordered !ppc ports=6
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: reset hcc_params 6872
thresh 7 uframes 256/512/1024
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: capability 0001 at 68
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: irq 21, pci mem
e089d000
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: new USB bus registered,
assigned bus number 1
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: reset command 080002
(park)=0 ithresh=8 period=1024 Reset HALT
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: init command 010009
(park)=0 ithresh=1 period=256 RUN
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI
1.00, driver 2003-Jun-13
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: root hub device address
1
Jan 18 16:44:17 desktop kernel: usb usb1: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:44:17 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:44:17 desktop kernel: usb usb1: Product: EHCI Host Controller
Jan 18 16:44:17 desktop kernel: usb usb1: Manufacturer: Linux 2.6.1-rc1
ehci_hcd
Jan 18 16:44:17 desktop kernel: usb usb1: SerialNumber: 0000:00:10.3
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: usb usb1: registering 1-0:1.0 (config #1,
interface 0)
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: usb_probe_interface
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: usb_probe_interface - got id
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: USB hub found
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: 6 ports detected
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: standalone hub
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: ganged power switching
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: individual port over-current
protection
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: Single TT
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: TT requires at most 8 FS bit
times
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: Port indicators are not supported
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: power on to power good time: 0ms
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: local power source is good
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: no over-current condition exists
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: enabling power on all ports
Jan 18 16:44:17 desktop kernel: ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host
Controller (OHCI) Driver (PCI)
Jan 18 16:44:17 desktop kernel: ohci_hcd: block sizes: ed 64 td 64
Jan 18 16:44:17 desktop kernel: drivers/usb/host/uhci-hcd.c: USB Universal
Host Controller Interface driver v2.1
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.0: UHCI Host Controller
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.0: irq 21, io base
0000d400
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.0: new USB bus registered,
assigned bus number 2
Jan 18 16:44:17 desktop kernel: drivers/usb/host/uhci-hcd.c: detected 2 ports
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.0: root hub device address
1
Jan 18 16:44:17 desktop kernel: usb usb2: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:44:17 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:44:17 desktop kernel: usb usb2: Product: UHCI Host Controller
Jan 18 16:44:17 desktop kernel: usb usb2: Manufacturer: Linux 2.6.1-rc1
uhci_hcd
Jan 18 16:44:17 desktop kernel: usb usb2: SerialNumber: 0000:00:10.0
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: usb usb2: registering 2-0:1.0 (config #1,
interface 0)
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: usb_probe_interface
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: usb_probe_interface - got id
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: USB hub found
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: 2 ports detected
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: standalone hub
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: ganged power switching
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: global over-current protection
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: Port indicators are not supported
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: power on to power good time: 2ms
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: local power source is good
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: no over-current condition exists
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: enabling power on all ports
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.1: UHCI Host Controller
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
001803 POWER sig=j CSC CONNECT
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: port 5, status 501, change 1, 480
Mb/s
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.1: irq 21, io base
0000d800
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.1: new USB bus registered,
assigned bus number 3
Jan 18 16:44:17 desktop kernel: drivers/usb/host/uhci-hcd.c: detected 2 ports
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.1: root hub device address
1
Jan 18 16:44:17 desktop kernel: usb usb3: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:44:17 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:44:17 desktop kernel: usb usb3: Product: UHCI Host Controller
Jan 18 16:44:17 desktop kernel: usb usb3: Manufacturer: Linux 2.6.1-rc1
uhci_hcd
Jan 18 16:44:17 desktop kernel: usb usb3: SerialNumber: 0000:00:10.1
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: usb usb3: registering 3-0:1.0 (config #1,
interface 0)
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: usb_probe_interface
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: usb_probe_interface - got id
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: USB hub found
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: 2 ports detected
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: standalone hub
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: ganged power switching
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: global over-current protection
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: Port indicators are not supported
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: power on to power good time: 2ms
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: local power source is good
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: no over-current condition exists
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: enabling power on all ports
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.2: UHCI Host Controller
Jan 18 16:44:17 desktop kernel: hub 1-0:1.0: debounce: port 5: delay 100ms
stable 4 status 0x501
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.2: irq 21, io base
0000dc00
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: port 5 full speed -->
companion
Jan 18 16:44:17 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
003801 POWER OWNER sig=j CONNECT
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.2: new USB bus registered,
assigned bus number 4
Jan 18 16:44:17 desktop kernel: drivers/usb/host/uhci-hcd.c: detected 2 ports
Jan 18 16:44:17 desktop kernel: uhci_hcd 0000:00:10.2: root hub device address
1
Jan 18 16:44:17 desktop kernel: usb usb4: new device strings: Mfr=3,
Product=2, SerialNumber=1
Jan 18 16:44:17 desktop kernel: drivers/usb/core/message.c: USB device number
1 default language ID 0x409
Jan 18 16:44:17 desktop kernel: usb usb4: Product: UHCI Host Controller
Jan 18 16:44:17 desktop kernel: usb usb4: Manufacturer: Linux 2.6.1-rc1
uhci_hcd
Jan 18 16:44:17 desktop kernel: usb usb4: SerialNumber: 0000:00:10.2
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: port 1, status 100, change 3, 12
Mb/s
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: port 2, status 100, change 3, 12
Mb/s
Jan 18 16:44:17 desktop kernel: usb usb4: registering 4-0:1.0 (config #1,
interface 0)
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: usb_probe_interface
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: usb_probe_interface - got id
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: USB hub found
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: 2 ports detected
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: standalone hub
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: ganged power switching
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: global over-current protection
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: Port indicators are not supported
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: power on to power good time: 2ms
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: hub controller current
requirement: 0mA
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: local power source is good
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: no over-current condition exists
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: enabling power on all ports
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: port 1, status 100, change 3, 12
Mb/s
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: port 2, status 100, change 3, 12
Mb/s
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: port 1 enable change, status 100
Jan 18 16:44:17 desktop kernel: hub 2-0:1.0: port 2 enable change, status 100
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: port 1, status 101, change 3, 12
Mb/s
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: debounce: port 1: delay 100ms
stable 4 status 0x101
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: new USB device on port 1,
assigned address 2
Jan 18 16:44:17 desktop kernel: usb 4-1: new device strings: Mfr=1, Product=2,
SerialNumber=0
Jan 18 16:44:17 desktop kernel: drivers/usb/core/message.c: USB device number
2 default language ID 0x409
Jan 18 16:44:17 desktop kernel: usb 4-1: Product: USB Printer
Jan 18 16:44:17 desktop kernel: usb 4-1: Manufacturer: EPSON
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: usb 4-1: registering 4-1:1.0 (config #1,
interface 0)
Jan 18 16:44:17 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: port 2, status 100, change 3, 12
Mb/s
Jan 18 16:44:17 desktop kernel: hub 4-0:1.0: port 2 enable change, status 100
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: port 1 enable change, status 100
Jan 18 16:44:17 desktop kernel: hub 3-0:1.0: port 2 enable change, status 100
Jan 18 16:44:17 desktop kernel: drivers/usb/host/uhci-hcd.c: d400: suspend_hc
Jan 18 16:44:17 desktop kernel: drivers/usb/host/uhci-hcd.c: d800: suspend_hc
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: modules.usbmap unparsable
line:
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[907]: .
Jan 18 16:44:19 desktop /etc/hotplug/usb.agent[942]: Bad USB agent invocation
Jan 18 16:44:22 desktop modprobe: FATAL: Module battery not found.
Jan 18 16:44:22 desktop kernel: via82xx: Assuming DXS channels with 48k fixed
sample rate.
Jan 18 16:44:22 desktop kernel: Please try dxs_support=1 option and
report if it works on your machine.
Jan 18 16:44:22 desktop kernel: PCI: Setting latency timer of device
0000:00:11.5 to 64
Jan 18 16:44:22 desktop kernel: ACPI: Power Button (FF) [PWRF]
Jan 18 16:44:22 desktop kernel: ACPI: Processor [CPU0] (supports C1 C2, 2
throttling states)
Jan 18 16:44:22 desktop smpppd[1021]: smpppd version 1.06 started
Jan 18 16:44:22 desktop kernel: NET: Registered protocol family 10
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: modules.usbmap
unparsable line:
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: .
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: modules.usbmap
unparsable line:
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: .
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: modules.usbmap
unparsable line:
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: .
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: modules.usbmap
unparsable line:
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1059]: .
Jan 18 16:44:22 desktop /etc/hotplug/usb.agent[1101]: Bad USB agent invocation
Jan 18 16:44:22 desktop kernel: Disabled Privacy Extensions on device c0386e20
(lo)
Jan 18 16:44:22 desktop kernel: IPv6 over IPv4 tunneling driver
Jan 18 16:44:22 desktop sshd[1056]: Server listening on :: port 22.
Jan 18 16:44:23 desktop kernel: request_module: failed /sbin/modprobe --
snd-card-1. error = 256
Jan 18 16:44:25 desktop kernel: parport0: PC-style at 0x378 [PCSPP(,...)]
Jan 18 16:44:25 desktop kernel: lp0: using parport0 (polling).
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: modules.usbmap
unparsable line:
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: .
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: modules.usbmap
unparsable line:
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: .
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: modules.usbmap
unparsable line:
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: .
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: modules.usbmap
unparsable line:
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1340]: .
Jan 18 16:44:25 desktop /etc/hotplug/usb.agent[1378]: Bad USB agent invocation
Jan 18 16:44:26 desktop /usr/sbin/cron[1462]: (CRON) STARTUP (fork ok)
Jan 18 16:44:27 desktop kernel: request_module: failed /sbin/modprobe --
char-major-4-72. error = 256
Jan 18 16:44:27 desktop kernel: drivers/usb/serial/usb-serial.c: USB Serial
support registered for Generic
Jan 18 16:44:27 desktop kernel: usbserial 4-1:1.0: usb_probe_interface
Jan 18 16:44:27 desktop kernel: usbserial 4-1:1.0: usb_probe_interface - got
id
Jan 18 16:44:27 desktop kernel: drivers/usb/core/usb.c: registered new driver
usbserial
Jan 18 16:44:27 desktop kernel: drivers/usb/serial/usb-serial.c: USB Serial
Driver core v2.0
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: modules.usbmap
unparsable line:
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: .
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: modules.usbmap
unparsable line:
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: .
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: modules.usbmap
unparsable line:
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: .
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: modules.usbmap
unparsable line:
Jan 18 16:44:28 desktop /etc/hotplug/usb.agent[1574]: .
Jan 18 16:44:32 desktop /etc/hotplug/usb.agent[1625]: Bad USB agent invocation
Jan 18 16:44:33 desktop kernel: eth0: no IPv6 routers present
Jan 18 16:44:35 desktop modprobe: FATAL: Module printer not found.
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: modules.usbmap
unparsable line:
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: .
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: modules.usbmap
unparsable line:
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: .
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: modules.usbmap
unparsable line:
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: .
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: modules.usbmap
unparsable line:
Jan 18 16:44:35 desktop /etc/hotplug/usb.agent[1633]: .
Jan 18 16:44:43 desktop login[1619]: FAILED LOGIN 1 FROM /dev/tty1 FOR
UNKNOWN, User not known to the underlying authentication module
Jan 18 16:45:03 desktop kernel: atkbd.c: Unknown key released (translated set
2, code 0x7a on isa0060/serio0).
Jan 18 16:46:52 desktop kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan 18 16:46:52 desktop kernel: 0: nvidia: loading NVIDIA Linux x86 nvidia.o
Kernel Module 1.0-4496 Wed Jul 16 19:03:09 PDT 2003
Jan 18 16:46:53 desktop modprobe: WARNING: Error inserting agpgart (/lib/
modules/2.6.1-rc1/kernel/drivers/char/agp/agpgart.ko): Unknown symbol in
module, or unknown parameter (see dmesg)
Jan 18 16:46:53 desktop kernel: agpgart: Unknown parameter
`agp_try_unsupported'
Jan 18 16:46:53 desktop kernel: 0: NVRM: AGPGART: unable to retrieve symbol
table
Jan 18 16:46:53 desktop kernel: atkbd.c: Unknown key released (translated set
2, code 0x7a on isa0060/serio0).
Jan 18 16:47:45 desktop kernel: mtrr: no MTRR for d8000000,4000000 found
Jan 18 16:48:34 desktop login[2248]: FAILED LOGIN 1 FROM /dev/tty1 FOR jim,
Authentication failure
Jan 18 16:48:46 desktop modprobe: WARNING: Error inserting agpgart (/lib/
modules/2.6.1-rc1/kernel/drivers/char/agp/agpgart.ko): Unknown symbol in
module, or unknown parameter (see dmesg)
Jan 18 16:48:46 desktop kernel: agpgart: Unknown parameter
`agp_try_unsupported'
Jan 18 16:48:46 desktop kernel: 0: NVRM: AGPGART: unable to retrieve symbol
table
Jan 18 16:48:47 desktop kernel: atkbd.c: Unknown key released (translated set
2, code 0x7a on isa0060/serio0).
Jan 18 16:48:47 desktop kernel: atkbd.c: Unknown key released (translated set
2, code 0x7a on isa0060/serio0).
Jan 18 16:49:07 desktop kernel: request_module: failed /sbin/modprobe --
sound-slot-1. error = 256
Jan 18 16:49:20 desktop kernel: request_module: failed /sbin/modprobe --
snd-card-1. error = 256
Jan 18 16:49:23 desktop kernel: request_module: failed /sbin/modprobe --
snd-card-1. error = 256
Jan 18 16:49:36 desktop kernel: hdh: ATAPI 48X DVD-ROM drive, 512kB Cache
Jan 18 16:49:36 desktop kernel: Uniform CD-ROM driver Revision: 3.12
Jan 18 16:49:36 desktop /sbin/hotplug[2533]: no runnable /etc/hotplug/
block.agent is installed
Jan 18 16:50:34 desktop su: (to root) jim on /dev/pts/1
Jan 18 16:50:34 desktop su: pam_unix2: session started for user root, service
su
Jan 18 16:52:38 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 3 status
001803 POWER sig=j CSC CONNECT
Jan 18 16:52:38 desktop kernel: hub 1-0:1.0: port 3, status 501, change 1, 480
Mb/s
Jan 18 16:52:38 desktop kernel: hub 1-0:1.0: debounce: port 3: delay 100ms
stable 4 status 0x501
Jan 18 16:52:38 desktop kernel: ehci_hcd 0000:00:10.3: port 3 high speed
Jan 18 16:52:38 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 3 status
001005 POWER sig=se0 PE CONNECT
Jan 18 16:52:38 desktop kernel: hub 1-0:1.0: new USB device on port 3,
assigned address 2
Jan 18 16:52:38 desktop kernel: usb 1-3: new device strings: Mfr=73,
Product=80, SerialNumber=98
Jan 18 16:52:38 desktop kernel: drivers/usb/core/message.c: USB device number
2 default language ID 0x409
Jan 18 16:52:38 desktop kernel: usb 1-3: Product: USB CDRW6402EXT-B
Jan 18 16:52:38 desktop kernel: usb 1-3: Manufacturer: Iomega
Jan 18 16:52:38 desktop kernel: usb 1-3: SerialNumber: 5300000000032151
Jan 18 16:52:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:52:38 desktop kernel: usb 1-3: registering 1-3:2.0 (config #2,
interface 0)
Jan 18 16:52:38 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:52:38 desktop kernel: usbserial 1-3:2.0: usb_probe_interface
Jan 18 16:52:38 desktop kernel: usbserial 1-3:2.0: usb_probe_interface - got
id
Jan 18 16:52:38 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
003802 POWER OWNER sig=j CSC
Jan 18 16:52:38 desktop kernel: hub 1-0:1.0: port 5, status 0, change 1, 12
Mb/s
Jan 18 16:52:41 desktop /etc/hotplug/usb.agent[2595]: Bad USB agent invocation
Jan 18 16:52:45 desktop kernel: Initializing USB Mass Storage driver...
Jan 18 16:52:45 desktop kernel: usb-storage 1-3:2.0: usb_probe_interface
Jan 18 16:52:45 desktop kernel: usb-storage 1-3:2.0: usb_probe_interface - got
id
Jan 18 16:52:45 desktop kernel: scsi0 : SCSI emulation for USB Mass Storage
devices
Jan 18 16:52:45 desktop /sbin/hotplug[2632]: no runnable /etc/hotplug/
scsi_host.agent is installed
Jan 18 16:52:47 desktop kernel: Vendor: IOMEGA Model: CDRW6402EXT-B
Rev: OOX1
Jan 18 16:52:47 desktop kernel: Type: CD-ROM
ANSI SCSI revision: 02
Jan 18 16:52:47 desktop /sbin/hotplug[2639]: no runnable /etc/hotplug/
scsi.agent is installed
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: modules.usbmap
unparsable line:
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: .
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: modules.usbmap
unparsable line:
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: .
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: modules.usbmap
unparsable line:
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: .
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: modules.usbmap
unparsable line:
Jan 18 16:52:47 desktop /etc/hotplug/usb.agent[2603]: .
Jan 18 16:52:47 desktop /sbin/hotplug[2640]: no runnable /etc/hotplug/
scsi_device.agent is installed
Jan 18 16:52:47 desktop kernel: WARNING: USB Mass Storage data integrity not
assured
Jan 18 16:52:47 desktop kernel: USB Mass Storage device found at 2
Jan 18 16:52:47 desktop kernel: drivers/usb/core/usb.c: registered new driver
usb-storage
Jan 18 16:52:47 desktop kernel: USB Mass Storage support registered.
Jan 18 16:52:47 desktop kernel: Attached scsi generic sg0 at scsi0, channel 0,
id 0, lun 0, type 5
Jan 18 16:52:47 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-0. error = 256
Jan 18 16:52:53 desktop kernel: sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/
form2 cdda tray
Jan 18 16:52:53 desktop kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0,
id 0, lun 0
Jan 18 16:52:53 desktop /sbin/hotplug[2700]: no runnable /etc/hotplug/
block.agent is installed
Jan 18 16:52:53 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 16:52:58 desktop kernel: end_request: I/O error, dev sr0, sector 0
Jan 18 16:52:58 desktop kernel: Buffer I/O error on device sr0, logical block
0
Jan 18 16:52:58 desktop kernel: end_request: I/O error, dev sr0, sector 0
Jan 18 16:52:58 desktop kernel: FAT: unable to read boot sector
Jan 18 16:53:17 desktop kernel: FAT: bogus number of reserved sectors
Jan 18 16:53:17 desktop kernel: VFS: Can't find a valid FAT filesystem on dev
sr0.
Jan 18 16:53:34 desktop kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
Jan 18 16:53:34 desktop kernel: ISO 9660 Extensions: RRIP_1991A
Jan 18 16:54:20 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 2 status
001803 POWER sig=j CSC CONNECT
Jan 18 16:54:20 desktop kernel: hub 1-0:1.0: port 2, status 501, change 1, 480
Mb/s
Jan 18 16:54:20 desktop kernel: hub 1-0:1.0: debounce: port 2: delay 100ms
stable 4 status 0x501
Jan 18 16:54:20 desktop kernel: ehci_hcd 0000:00:10.3: port 2 high speed
Jan 18 16:54:20 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 2 status
001005 POWER sig=se0 PE CONNECT
Jan 18 16:54:20 desktop kernel: hub 1-0:1.0: new USB device on port 2,
assigned address 3
Jan 18 16:54:20 desktop kernel: usb 1-2: new device strings: Mfr=56,
Product=63, SerialNumber=80
Jan 18 16:54:20 desktop kernel: drivers/usb/core/message.c: USB device number
3 default language ID 0x409
Jan 18 16:54:20 desktop kernel: usb 1-2: Product: 3000LS v01.00.00
Jan 18 16:54:20 desktop kernel: usb 1-2: Manufacturer: Maxtor
Jan 18 16:54:20 desktop kernel: usb 1-2: SerialNumber: DEF10647FBB9
Jan 18 16:54:20 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:54:20 desktop kernel: usb 1-2: registering 1-2:1.0 (config #1,
interface 0)
Jan 18 16:54:20 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:54:20 desktop kernel: usbserial 1-2:1.0: usb_probe_interface
Jan 18 16:54:20 desktop kernel: usbserial 1-2:1.0: usb_probe_interface - got
id
Jan 18 16:54:20 desktop kernel: usb-storage 1-2:1.0: usb_probe_interface
Jan 18 16:54:20 desktop kernel: usb-storage 1-2:1.0: usb_probe_interface - got
id
Jan 18 16:54:20 desktop kernel: scsi1 : SCSI emulation for USB Mass Storage
devices
Jan 18 16:54:20 desktop /sbin/hotplug[2870]: no runnable /etc/hotplug/
scsi_host.agent is installed
Jan 18 16:54:23 desktop /etc/hotplug/usb.agent[2877]: Bad USB agent invocation
Jan 18 16:54:24 desktop /sbin/hotplug[2886]: no runnable /etc/hotplug/
scsi.agent is installed
Jan 18 16:54:24 desktop kernel: Vendor: Maxtor 2 Model: F040J0
Rev: 0 0
Jan 18 16:54:24 desktop /sbin/hotplug[2893]: no runnable /etc/hotplug/
block.agent is installed
Jan 18 16:54:24 desktop kernel: Type: Direct-Access
ANSI SCSI revision: 02
Jan 18 16:54:24 desktop kernel: SCSI device sda: 80293248 512-byte hdwr
sectors (41110 MB)
Jan 18 16:54:24 desktop kernel: sda: assuming drive cache: write through
Jan 18 16:54:24 desktop /sbin/hotplug[2900]: no runnable /etc/hotplug/
block.agent is installed
Jan 18 16:54:24 desktop /sbin/hotplug[2901]: no runnable /etc/hotplug/
scsi_device.agent is installed
Jan 18 16:54:24 desktop kernel: sda: sda1
Jan 18 16:54:24 desktop kernel: Attached scsi disk sda at scsi1, channel 0, id
0, lun 0
Jan 18 16:54:24 desktop kernel: Attached scsi generic sg1 at scsi1, channel 0,
id 0, lun 0, type 0
Jan 18 16:54:24 desktop kernel: WARNING: USB Mass Storage data integrity not
assured
Jan 18 16:54:24 desktop kernel: USB Mass Storage device found at 3
Jan 18 16:54:24 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
003802 POWER OWNER sig=j CSC
Jan 18 16:54:24 desktop kernel: hub 1-0:1.0: port 5, status 0, change 1, 12
Mb/s
Jan 18 16:54:26 desktop modprobe: FATAL: Module usb_storage already in kernel.
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: modules.usbmap
unparsable line:
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: .
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: modules.usbmap
unparsable line:
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: .
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: modules.usbmap
unparsable line:
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: .
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: modules.usbmap
unparsable line:
Jan 18 16:54:26 desktop /etc/hotplug/usb.agent[2914]: .
Jan 18 16:54:26 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 16:56:29 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 4 status
001803 POWER sig=j CSC CONNECT
Jan 18 16:56:29 desktop kernel: hub 1-0:1.0: port 4, status 501, change 1, 480
Mb/s
Jan 18 16:56:29 desktop kernel: hub 1-0:1.0: debounce: port 4: delay 100ms
stable 4 status 0x501
Jan 18 16:56:29 desktop kernel: ehci_hcd 0000:00:10.3: port 4 full speed -->
companion
Jan 18 16:56:29 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 4 status
003801 POWER OWNER sig=j CONNECT
Jan 18 16:56:29 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
003802 POWER OWNER sig=j CSC
Jan 18 16:56:29 desktop kernel: hub 1-0:1.0: port 5, status 0, change 1, 12
Mb/s
Jan 18 16:56:29 desktop kernel: drivers/usb/host/uhci-hcd.c: d800: wakeup_hc
Jan 18 16:56:29 desktop kernel: hub 3-0:1.0: port 2, status 101, change 1, 12
Mb/s
Jan 18 16:56:29 desktop kernel: hub 3-0:1.0: debounce: port 2: delay 100ms
stable 4 status 0x101
Jan 18 16:56:29 desktop kernel: hub 3-0:1.0: new USB device on port 2,
assigned address 2
Jan 18 16:56:29 desktop kernel: usb 3-2: new device strings: Mfr=1, Product=2,
SerialNumber=0
Jan 18 16:56:29 desktop kernel: drivers/usb/core/message.c: USB device number
2 default language ID 0x409
Jan 18 16:56:29 desktop kernel: usb 3-2: Product: Perfection1200
Jan 18 16:56:29 desktop kernel: usb 3-2: Manufacturer: EPSON
Jan 18 16:56:29 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:56:29 desktop kernel: usb 3-2: registering 3-2:1.0 (config #1,
interface 0)
Jan 18 16:56:29 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:56:29 desktop kernel: usbserial 3-2:1.0: usb_probe_interface
Jan 18 16:56:29 desktop kernel: usbserial 3-2:1.0: usb_probe_interface - got
id
Jan 18 16:56:32 desktop /etc/hotplug/usb.agent[3123]: Bad USB agent invocation
Jan 18 16:56:35 desktop modprobe: FATAL: Module scanner not found.
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: modules.usbmap
unparsable line:
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: .
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: modules.usbmap
unparsable line:
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: .
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: modules.usbmap
unparsable line:
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: .
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: modules.usbmap
unparsable line:
Jan 18 16:56:35 desktop /etc/hotplug/usb.agent[3131]: .
Jan 18 16:56:36 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 16:58:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:28 desktop sane-find-scanner: resmgr: server response code 200
Jan 18 16:58:28 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:28 desktop sane-find-scanner: resmgr: server response code 200
Jan 18 16:58:28 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:28 desktop sane-find-scanner: resmgr: server response code 200
Jan 18 16:58:28 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:28 desktop sane-find-scanner: resmgr: server response code 200
Jan 18 16:58:28 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:28 desktop kernel: usbfs: USBDEVFS_CONTROL failed cmd
sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -32
Jan 18 16:58:28 desktop kernel: usbfs: USBDEVFS_CONTROL failed cmd
sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -32
Jan 18 16:58:47 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:47 desktop scanimage: resmgr: server response code 200
Jan 18 16:58:47 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:47 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:47 desktop scanimage: resmgr: server response code 200
Jan 18 16:58:47 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:47 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:47 desktop scanimage: resmgr: server response code 200
Jan 18 16:58:47 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:47 desktop resmgr[971]: accepted connection from user jim
Jan 18 16:58:47 desktop scanimage: resmgr: server response code 200
Jan 18 16:58:47 desktop resmgr[971]: disconnect from jim
Jan 18 16:58:47 desktop kernel: usb 3-2: usb_disable_device nuking non-ep0
URBs
Jan 18 16:58:47 desktop kernel: usb 3-2: unregistering interface 3-2:1.0
Jan 18 16:58:47 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:58:47 desktop kernel: usb 3-2: registering 3-2:1.0 (config #1,
interface 0)
Jan 18 16:58:47 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 16:58:47 desktop kernel: usbserial 3-2:1.0: usb_probe_interface
Jan 18 16:58:47 desktop kernel: usbserial 3-2:1.0: usb_probe_interface - got
id
Jan 18 16:58:51 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 16:58:51 desktop kernel: usb 3-2: control timeout on ep0in
Jan 18 16:58:51 desktop kernel: usb 3-2: hcd_unlink_urb cec4df40 fail -22
Jan 18 16:58:51 desktop modprobe: FATAL: Module scanner not found.
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: modules.usbmap
unparsable line:
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: .
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: modules.usbmap
unparsable line:
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: .
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: modules.usbmap
unparsable line:
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: .
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: modules.usbmap
unparsable line:
Jan 18 16:58:51 desktop /etc/hotplug/usb.agent[3368]: .
Jan 18 16:58:51 desktop kernel: usb 3-2: control timeout on ep0in
Jan 18 16:58:51 desktop kernel: usb 3-2: hcd_unlink_urb cec4df40 fail -22
Jan 18 16:58:52 desktop /etc/hotplug/usb.agent[3356]: /var/run/hotplug/
usb-remover-%4b8%104%103%255%255%255: line 3: /etc/hotplug/usb/epson_scanner:
Permission denied
Jan 18 16:58:52 desktop /etc/hotplug/usb.agent[3356]: FATAL: Module scanner
not found.
Jan 18 16:58:52 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-13. error = 256
Jan 18 16:59:00 desktop /USR/SBIN/CRON[3663]: (root) CMD ( rm -f /var/spool/
cron/lastrun/cron.hourly)
Jan 18 17:01:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:01:28 desktop xsane: resmgr: server response code 200
Jan 18 17:01:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:01:28 desktop resmgr[971]: disconnect from jim
Jan 18 17:01:28 desktop resmgr[971]: disconnect from jim
Jan 18 17:01:28 desktop xsane: resmgr: server response code 200
Jan 18 17:01:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:01:28 desktop xsane: resmgr: server response code 200
Jan 18 17:01:28 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:01:28 desktop resmgr[971]: disconnect from jim
Jan 18 17:01:28 desktop resmgr[971]: disconnect from jim
Jan 18 17:01:28 desktop xsane: resmgr: server response code 200
Jan 18 17:01:28 desktop kernel: usb 3-2: usb_disable_device nuking non-ep0
URBs
Jan 18 17:01:28 desktop kernel: usb 3-2: unregistering interface 3-2:1.0
Jan 18 17:01:28 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:01:28 desktop kernel: usb 3-2: registering 3-2:1.0 (config #1,
interface 0)
Jan 18 17:01:28 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:01:28 desktop kernel: usbserial 3-2:1.0: usb_probe_interface
Jan 18 17:01:28 desktop kernel: usbserial 3-2:1.0: usb_probe_interface - got
id
Jan 18 17:01:28 desktop kernel: usb 3-2: usb_disable_device nuking non-ep0
URBs
Jan 18 17:01:28 desktop kernel: usb 3-2: unregistering interface 3-2:1.0
Jan 18 17:01:28 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:01:28 desktop kernel: usb 3-2: registering 3-2:1.0 (config #1,
interface 0)
Jan 18 17:01:28 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:01:28 desktop kernel: usbserial 3-2:1.0: usb_probe_interface
Jan 18 17:01:28 desktop kernel: usbserial 3-2:1.0: usb_probe_interface - got
id
Jan 18 17:01:31 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 17:01:32 desktop modprobe: FATAL: Module scanner not found.
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: .
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: .
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: .
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: .
Jan 18 17:01:32 desktop kernel: usb 3-2: control timeout on ep0in
Jan 18 17:01:32 desktop kernel: usb 3-2: hcd_unlink_urb cea0a640 fail -22
Jan 18 17:01:32 desktop kernel: usb 3-2: control timeout on ep0in
Jan 18 17:01:32 desktop kernel: usb 3-2: hcd_unlink_urb cea0a240 fail -22
Jan 18 17:01:32 desktop modprobe: FATAL: Module scanner not found.
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: .
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: .
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: .
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: modules.usbmap
unparsable line:
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: .
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: cannot get config
descriptor 0, Broken pipe (32)
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: cannot get config
descriptor 0, Broken pipe (32)
Jan 18 17:01:32 desktop kernel: usbfs: USBDEVFS_CONTROL failed cmd usbmodules
dev 2 rqt 128 rq 6 len 9 ret -32
Jan 18 17:01:32 desktop kernel: usbfs: USBDEVFS_CONTROL failed cmd usbmodules
dev 2 rqt 128 rq 6 len 32 ret -32
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3755]: cannot get config
descriptor 0, Broken pipe (32)
Jan 18 17:01:32 desktop /etc/hotplug/usb.agent[3813]: cannot get config
descriptor 0, Broken pipe (32)
Jan 18 17:01:32 desktop kernel: usbfs: USBDEVFS_CONTROL failed cmd usbmodules
dev 2 rqt 128 rq 6 len 9 ret -32
Jan 18 17:01:32 desktop kernel: usbfs: USBDEVFS_CONTROL failed cmd usbmodules
dev 2 rqt 128 rq 6 len 9 ret -32
Jan 18 17:01:32 desktop kernel: usb 3-2: control timeout on ep0in
Jan 18 17:01:32 desktop kernel: usb 3-2: hcd_unlink_urb cea0a240 fail -22
Jan 18 17:01:32 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 17:01:33 desktop /etc/hotplug/usb.agent[3766]: /var/run/hotplug/
usb-remover-%4b8%104%103%255%255%255: line 3: /etc/hotplug/usb/epson_scanner:
Permission denied
Jan 18 17:01:33 desktop /etc/hotplug/usb.agent[3766]: FATAL: Module scanner
not found.
Jan 18 17:01:33 desktop kernel: request_module: failed /sbin/modprobe --
char-major-9-0. error = 256
Jan 18 17:01:35 desktop /etc/hotplug/usb.agent[3804]: FATAL: Module scanner
not found.
Jan 18 17:07:45 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 4 status
003802 POWER OWNER sig=j CSC
Jan 18 17:07:45 desktop kernel: hub 1-0:1.0: port 4, status 0, change 1, 12
Mb/s
Jan 18 17:07:45 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
001002 POWER sig=se0 CSC
Jan 18 17:07:45 desktop kernel: hub 1-0:1.0: port 5, status 100, change 1, 12
Mb/s
Jan 18 17:07:45 desktop kernel: hub 4-0:1.0: port 1, status 100, change 3, 12
Mb/s
Jan 18 17:07:45 desktop kernel: usb 4-1: USB disconnect, address 2
Jan 18 17:07:45 desktop kernel: usb 4-1: usb_disable_device nuking all URBs
Jan 18 17:07:45 desktop kernel: usb 4-1: unregistering interface 4-1:1.0
Jan 18 17:07:45 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:07:45 desktop kernel: usb 4-1: unregistering device
Jan 18 17:07:45 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:07:46 desktop kernel: hub 4-0:1.0: port 1 enable change, status 100
Jan 18 17:07:46 desktop kernel: drivers/usb/host/uhci-hcd.c: dc00: suspend_hc
Jan 18 17:07:49 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 17:07:52 desktop /etc/hotplug/usb.agent[4549]: Bad USB agent invocation
Jan 18 17:08:01 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 4 status
003802 POWER OWNER sig=j CSC
Jan 18 17:08:01 desktop kernel: hub 1-0:1.0: port 4, status 0, change 1, 12
Mb/s
Jan 18 17:08:01 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
001803 POWER sig=j CSC CONNECT
Jan 18 17:08:01 desktop kernel: hub 1-0:1.0: port 5, status 501, change 1, 480
Mb/s
Jan 18 17:08:01 desktop kernel: hub 1-0:1.0: debounce: port 5: delay 100ms
stable 4 status 0x501
Jan 18 17:08:01 desktop kernel: ehci_hcd 0000:00:10.3: port 5 full speed -->
companion
Jan 18 17:08:01 desktop kernel: ehci_hcd 0000:00:10.3: GetStatus port 5 status
003801 POWER OWNER sig=j CONNECT
Jan 18 17:08:01 desktop kernel: drivers/usb/host/uhci-hcd.c: dc00: wakeup_hc
Jan 18 17:08:01 desktop kernel: hub 4-0:1.0: port 1, status 101, change 1, 12
Mb/s
Jan 18 17:08:01 desktop kernel: hub 4-0:1.0: debounce: port 1: delay 100ms
stable 4 status 0x101
Jan 18 17:08:01 desktop kernel: hub 4-0:1.0: new USB device on port 1,
assigned address 3
Jan 18 17:08:01 desktop kernel: usb 4-1: new device strings: Mfr=1, Product=2,
SerialNumber=0
Jan 18 17:08:01 desktop kernel: drivers/usb/core/message.c: USB device number
3 default language ID 0x409
Jan 18 17:08:01 desktop kernel: usb 4-1: Product: USB Printer
Jan 18 17:08:01 desktop kernel: usb 4-1: Manufacturer: EPSON
Jan 18 17:08:01 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:08:01 desktop kernel: usb 4-1: registering 4-1:1.0 (config #1,
interface 0)
Jan 18 17:08:01 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:08:01 desktop kernel: usbserial 4-1:1.0: usb_probe_interface
Jan 18 17:08:01 desktop kernel: usbserial 4-1:1.0: usb_probe_interface - got
id
Jan 18 17:08:05 desktop /etc/hotplug/usb.agent[4592]: Bad USB agent invocation
Jan 18 17:08:08 desktop modprobe: FATAL: Module printer not found.
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: modules.usbmap
unparsable line:
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: .
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: modules.usbmap
unparsable line:
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: .
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: modules.usbmap
unparsable line:
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: .
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: modules.usbmap
unparsable line:
Jan 18 17:08:08 desktop /etc/hotplug/usb.agent[4600]: .
Jan 18 17:08:08 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 17:10:04 desktop kernel: usblp 4-1:1.0: usb_probe_interface
Jan 18 17:10:04 desktop kernel: usblp 4-1:1.0: usb_probe_interface - got id
Jan 18 17:10:04 desktop kernel: drivers/usb/class/usblp.c: usblp0: USB
Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0001
Jan 18 17:10:04 desktop kernel: drivers/usb/core/file.c: looking for a minor,
starting at 0
Jan 18 17:10:04 desktop kernel: drivers/usb/core/usb.c: registered new driver
usblp
Jan 18 17:10:04 desktop kernel: drivers/usb/class/usblp.c: v0.13: USB Printer
Device Class driver
Jan 18 17:10:07 desktop /etc/hotplug/usb.agent[4785]: Bad USB agent invocation
Jan 18 17:10:52 desktop su: (to root) jim on /dev/pts/4
Jan 18 17:10:52 desktop su: pam_unix2: session started for user root, service
su
Jan 18 17:10:52 desktop su: pam_unix2: session finished for user root, service
su
Jan 18 17:10:52 desktop su: (to root) jim on /dev/pts/4
Jan 18 17:10:52 desktop su: pam_unix2: session started for user root, service
su
Jan 18 17:11:17 desktop kernel: pnp: Device 00:0d disabled.
Jan 18 17:11:18 desktop kernel: pnp: Device 00:0d activated.
Jan 18 17:11:18 desktop kernel: parport0: PC-style at 0x378 [PCSPP(,...)]
Jan 18 17:11:18 desktop kernel: lp0: using parport0 (polling).
Jan 18 17:11:18 desktop kernel: pnp: Device 00:0d disabled.
Jan 18 17:11:18 desktop kernel: pnp: Device 00:0d activated.
Jan 18 17:11:18 desktop kernel: parport0: PC-style at 0x378 [PCSPP(,...)]
Jan 18 17:11:18 desktop kernel: usb 4-1: hcd_unlink_urb cdcb27c0 fail -22
Jan 18 17:11:18 desktop kernel: usb 4-1: hcd_unlink_urb cdcb2340 fail -22
Jan 18 17:11:18 desktop kernel: usb 4-1: hcd_unlink_urb cdcb27c0 fail -22
Jan 18 17:11:18 desktop kernel: usb 4-1: hcd_unlink_urb cdcb2340 fail -22
Jan 18 17:11:31 desktop kernel: lp0: using parport0 (polling).
Jan 18 17:11:31 desktop kernel: request_module: failed /sbin/modprobe --
char-major-4-72. error = 256
Jan 18 17:11:31 desktop kernel: usb 4-1: hcd_unlink_urb cdcb27c0 fail -22
Jan 18 17:11:31 desktop kernel: usb 4-1: hcd_unlink_urb cdcb2340 fail -22
Jan 18 17:11:33 desktop kernel: request_module: failed /sbin/modprobe --
char-major-4-72. error = 256
Jan 18 17:11:33 desktop kernel: usb 4-1: hcd_unlink_urb cdcb27c0 fail -22
Jan 18 17:12:53 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:12:53 desktop xsane: resmgr: server response code 200
Jan 18 17:12:53 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:12:53 desktop resmgr[971]: disconnect from jim
Jan 18 17:12:53 desktop resmgr[971]: disconnect from jim
Jan 18 17:12:53 desktop xsane: resmgr: server response code 200
Jan 18 17:12:53 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:12:53 desktop xsane: resmgr: server response code 200
Jan 18 17:12:53 desktop resmgr[971]: accepted connection from user jim
Jan 18 17:12:53 desktop resmgr[971]: disconnect from jim
Jan 18 17:12:53 desktop resmgr[971]: disconnect from jim
Jan 18 17:12:53 desktop xsane: resmgr: server response code 200
Jan 18 17:12:53 desktop kernel: usb 3-2: usb_disable_device nuking non-ep0
URBs
Jan 18 17:12:53 desktop kernel: usb 3-2: unregistering interface 3-2:1.0
Jan 18 17:12:53 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:12:53 desktop kernel: usb 3-2: registering 3-2:1.0 (config #1,
interface 0)
Jan 18 17:12:53 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:12:53 desktop kernel: usbserial 3-2:1.0: usb_probe_interface
Jan 18 17:12:53 desktop kernel: usbserial 3-2:1.0: usb_probe_interface - got
id
Jan 18 17:12:54 desktop kernel: usb 3-2: usb_disable_device nuking non-ep0
URBs
Jan 18 17:12:54 desktop kernel: usb 3-2: unregistering interface 3-2:1.0
Jan 18 17:12:54 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:12:54 desktop kernel: usb 3-2: registering 3-2:1.0 (config #1,
interface 0)
Jan 18 17:12:54 desktop kernel: drivers/usb/core/usb.c: usb_hotplug
Jan 18 17:12:54 desktop kernel: usbserial 3-2:1.0: usb_probe_interface
Jan 18 17:12:54 desktop kernel: usbserial 3-2:1.0: usb_probe_interface - got
id
Jan 18 17:12:57 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 17:12:57 desktop modprobe: FATAL: Module scanner not found.
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: modules.usbmap
unparsable line:
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: .
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: modules.usbmap
unparsable line:
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: .
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: modules.usbmap
unparsable line:
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: .
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: modules.usbmap
unparsable line:
Jan 18 17:12:57 desktop /etc/hotplug/usb.agent[5304]: .
Jan 18 17:12:57 desktop kernel: usb 3-2: control timeout on ep0in
Jan 18 17:12:57 desktop kernel: usb 3-2: hcd_unlink_urb cdcb2bc0 fail -22
Jan 18 17:12:58 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 17:13:00 desktop modprobe: FATAL: Module scanner not found.
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: modules.usbmap
unparsable line:
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: .
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: modules.usbmap
unparsable line:
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: .
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: modules.usbmap
unparsable line:
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: .
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: modules.usbmap
unparsable line:
Jan 18 17:13:00 desktop /etc/hotplug/usb.agent[5591]: .
Jan 18 17:13:00 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-1. error = 256
Jan 18 17:13:01 desktop kernel: request_module: failed /sbin/modprobe --
block-major-11-13. error = 256
Jan 18 17:13:02 desktop /etc/hotplug/usb.agent[5744]: /var/run/hotplug/
usb-remover-%4b8%104%103%255%255%255: line 3: /etc/hotplug/usb/epson_scanner:
Permission denied
Jan 18 17:13:02 desktop /etc/hotplug/usb.agent[5744]: FATAL: Module scanner
not found.
Jan 18 17:13:11 desktop kernel: usb 4-1: hcd_unlink_urb cdcb27c0 fail -22
Jan 18 17:13:11 desktop kernel: usb 4-1: hcd_unlink_urb cdcb2340 fail -22
Jan 18 17:14:01 desktop su: pam_unix2: session finished for user root, service
su
Jan 18 17:14:07 desktop gconfd (jim-5909): starting (version 2.2.1), pid 5909
user 'jim'
Jan 18 17:14:07 desktop gconfd (jim-5909): Resolved address "xml:readonly:/
etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only config source at
position 0
Jan 18 17:14:07 desktop gconfd (jim-5909): Resolved address "xml:readonly:/
etc/opt/gnome/gconf/preconf/gconf.xml.defaults" to a read-only config source
at position 1
Jan 18 17:14:07 desktop gconfd (jim-5909): Resolved address "xml:readwrite:/
home/jim/.gconf" to a writable config source at position 2
Jan 18 17:14:56 desktop kernel: ksysguardd: numerical sysctl 7 2 1 is
obsolete.
Jan 18 17:44:11 desktop -- MARK --
From jesper@pobox.com Mon Jan 19 01:00:37 2004
From: jesper@pobox.com (Jesper Anderson)
Date: Mon, 19 Jan 2004 02:00:37 +0100
Subject: [sane-devel] xsane and Gimp 2.0
In-Reply-To: <87d69h8d3i.fsf@frigate.technologeek.org>
References: <20040118143853.GA13079@acheron.the-domination.com> <87d69h8d3i.fsf@frigate.technologeek.org>
Message-ID: <20040119010037.GA2972@acheron.the-domination.com>
On Sun, Jan 18, 2004 at 04:56:33PM +0100, Julien BLACHE wrote:
>
>
>
> Apply to a clean source tree with patch -p1, run configure, build. It
> defaults to GTK2+GIMP2.0. (you don't need to run autoconf)
>
> WARNING: the autoconf check that comes with GIMP 2.0 expects version
> strings of the form x.y.z, and GIMP 2.0 pre-versions have a version
> string of the form 2.0preX, so the check barfs.
>
> You'll have to edit either gimptool or the .pc file for GIMP 2.0 so
> that they return 2.0.0 as the version string.
I found that when I edit gimptool, that is not enough; I had to edit
the pc file as well to make it work. I didn't try with only the pc
file edited, and not gimptool.
It's running fine for me; Slackware 9.1, just installed the new gimp
and xsane from source, no problems at all (except the occasional
stubborness of my old skool parallel port Epson GT 6000, and that I
need saned to be run as root in debug mode; but that's not xsane's
problem).
Great work, thanks a bunch!
Jesper
From jb@jblache.org Mon Jan 19 11:33:57 2004
From: jb@jblache.org (Julien BLACHE)
Date: Mon, 19 Jan 2004 12:33:57 +0100
Subject: [sane-devel] xsane and Gimp 2.0
In-Reply-To: <20040119010037.GA2972@acheron.the-domination.com> (Jesper
Anderson's message of "Mon, 19 Jan 2004 02:00:37 +0100")
References: <20040118143853.GA13079@acheron.the-domination.com>
<87d69h8d3i.fsf@frigate.technologeek.org>
<20040119010037.GA2972@acheron.the-domination.com>
Message-ID: <87wu7o5g0q.fsf@frigate.technologeek.org>
Jesper Anderson wrote:
Hi,
>> You'll have to edit either gimptool or the .pc file for GIMP 2.0 so
>> that they return 2.0.0 as the version string.
>
> I found that when I edit gimptool, that is not enough; I had to edit
> the pc file as well to make it work. I didn't try with only the pc
> file edited, and not gimptool.
If you have package-config installed, the autoconf check uses
package-config, so editing the .pc file is enough. Otherwise you have
to edit gimptool, sorry if I didn't make it clear :)
Glad to hear that it works fine :-)
JB.
--
Julien BLACHE
GPG KeyID 0xF5D65169
From jim.george@blueyonder.co.uk Mon Jan 19 21:50:12 2004
From: jim.george@blueyonder.co.uk (Jim George)
Date: Mon, 19 Jan 2004 21:50:12 -0000 (GMT)
Subject: [sane-devel] Canon LIDE 20 or LIDE 30 or EPSON 1660 P
Message-ID: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
Chaps,
does anyone know if either of the above are supported by SANE?
I was unable to find them on the supported device page but thought that
maybe they were known by another name.
I also noted in the spec of my local supplier that the USB port is USB 2.0
compatible, does this mean it doesn't work with USB 1.1? I ask because my
Linux system is an old Dell Latitude.
Brgrds,
Jim
From xiphmont@xiph.org Mon Jan 19 20:59:23 2004
From: xiphmont@xiph.org (Monty)
Date: Mon, 19 Jan 2004 15:59:23 -0500
Subject: [sane-devel] Canon LIDE 20 or LIDE 30 or EPSON 1660 P
In-Reply-To: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
References: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
Message-ID: <20040119205923.GI2972@lips.xiph.org>
On Mon, Jan 19, 2004 at 09:50:12PM -0000, Jim George wrote:
> Chaps,
>
> does anyone know if either of the above are supported by SANE?
>
> I was unable to find them on the supported device page but thought that
> maybe they were known by another name.
Both are fully supported by 1.0.13, and you do want at least that version.
> I also noted in the spec of my local supplier that the USB port is USB 2.0
> compatible, does this mean it doesn't work with USB 1.1? I ask because my
> Linux system is an old Dell Latitude.
It will work with USB 1.1.
Monty
From xiphmont@xiph.org Mon Jan 19 21:02:15 2004
From: xiphmont@xiph.org (Monty)
Date: Mon, 19 Jan 2004 16:02:15 -0500
Subject: [sane-devel] Canon LIDE 20 or LIDE 30 or EPSON 1660 P
In-Reply-To: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
References: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
Message-ID: <20040119210215.GJ2972@lips.xiph.org>
(sorry, I missed the third scanner; I know the LiDE 20 and 30 are well
supported)
Monty
From neundorf@kde.org Mon Jan 19 21:24:31 2004
From: neundorf@kde.org (Alexander Neundorf)
Date: Mon, 19 Jan 2004 22:24:31 +0100
Subject: [sane-devel] Canon LIDE 20 or LIDE 30 or EPSON 1660 P
In-Reply-To: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
References: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
Message-ID: <200401192224.31750.neundorf@kde.org>
On Monday 19 January 2004 22:50, Jim George wrote:
> Chaps,
>
> does anyone know if either of the above are supported by SANE?
>
> I was unable to find them on the supported device page but thought that
> maybe they were known by another name.
...
See:
http://www.sane-project.org/sane-supported-devices.html
I own a Canon Lide 30, and it works good.
The calibrating steps before the actual scanning starts takes a bit long,
maybe 20 seonds, otherwise it works very good, and takes away almost no
space :-)
Bye
Alex
--
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org - http://www.kde.org
alex@neundorf.net - http://www.neundorf.net
From khk@khk.net Mon Jan 19 23:27:48 2004
From: khk@khk.net (Karl Heinz Kremer)
Date: Mon, 19 Jan 2004 18:27:48 -0500
Subject: [sane-devel] Canon LIDE 20 or LIDE 30 or EPSON 1660 P
In-Reply-To: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
References: <1242.192.168.0.20.1074549012.squirrel@tassi.local>
Message-ID: <17946756-4AD7-11D8-A5BE-000A957E40E8@khk.net>
I don't know where you looked, but the Perfection 1660 is listed here :
http://www.sane-project.org/sane-mfgs.html#EPSON :-) The "Photo"
extension does not make a difference, and I'm not even sure if you can
buy the scanner without the Photo designation.
And yes, it's supported.
Karl Heinz
On Jan 19, 2004, at 4:50 PM, Jim George wrote:
> Chaps,
>
> does anyone know if either of the above are supported by SANE?
>
> I was unable to find them on the supported device page but thought that
> maybe they were known by another name.
>
> I also noted in the spec of my local supplier that the USB port is USB
> 2.0
> compatible, does this mean it doesn't work with USB 1.1? I ask
> because my
> Linux system is an old Dell Latitude.
>
> Brgrds,
>
> Jim
>
>
>
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request@lists.alioth.debian.org
From Franz Bakan"
Hello,
On Mon, 12 Jan 2004 21:00:16 +0100, Oliver Rauch wrote:
>I just replaced the fork() calls by sanei_thread_*() calls for the sane-umax
>backend. I tested it wirk fork() and threads on linux. This version is in the
>sane cvs now.
>
>Please could some Mac OS-X and OS/2 users test this version!
I have testers, but no definite result so far regarding the thread()-version.
But an error-report regarding 1.0.13:
Scanner: UMAX S-6E V2.0C
SCSI-Card: Adpatec AHA-1520/1522
When the user does not redirect '1' to a file the scanner works and finishes normal.
When he redirects the image-data to a file image.pnm the scanner starts to work,
but after a while it ends with:
[umax] starting scan
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 1
[umax] do_calibration
[umax] wait_scanner
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 0
[sanei_scsi] sanei_scsi_cmd: command 0x00 failed.
PSRBlock->status= 0x04
PSRBlock->u.chm.ha_status= 0x00
PSRBlock->u.cmd.target_status= 0x00
[umax] scanner reports Error during device I/O, waiting ...
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 0
[sanei_scsi] sanei_scsi_cmd: command 0x00 failed.
PSRBlock->status= 0x04
PSRBlock->u.chm.ha_status= 0x00
PSRBlock->u.cmd.target_status= 0x00
...
PSRBlock->status= 0x04
PSRBlock->u.chm.ha_status= 0x00
PSRBlock->u.cmd.target_status= 0x00
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 0
[umax] check condition sense handler (scsi_fd = 0)
[umax] check condition sense: VENDOR SPECIFIC
[umax] -> no error (#0)
[umax] -> calibration by driver
[umax] scanner ready
[umax] driver is doing calibration
[umax] request sense call is disabled
[umax] WARNING: missing information about shading-data
[umax] driver tries to guess missing values!
[umax] Calibration is done with selected image geometry and depth!
[umax] scanner sends 66 lines with 7647 pixels and 1 bytes/pixel
[umax] calculating average value for 8 bit shading data!
[umax] read_shading_data
[sanei_scsi] sanei_scsi_cmd: Reading PSRBlock->u.cmd.data_len= 7647
[umax] 8 bit shading-line 1 read
...
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 7647
[umax] shading-data sent
[umax] start_scan
[umax] starting scan
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 1
[umax] sane_get_parameters
[umax] reader_process started
[umax] reader_process: allocating SCSI buffer[1]
[umax] reader_process: starting to READ data
[umax] trim_rowbufsize: row_bufsize = 33150 bytes = 13 lines
[umax] reading 2983500 bytes in blocks of 33150 bytes
[umax] wait_scanner
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 0
[sanei_scsi] sanei_scsi_cmd: command 0x00 failed.
PSRBlock->status= 0x04
PSRBlock->u.chm.ha_status= 0x00
PSRBlock->u.cmd.target_status= 0x00
[umax] scanner reports Error during device I/O, waiting ...
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 0
[sanei_scsi] sanei_scsi_cmd: command 0x00 failed.
PSRBlock->status= 0x04
PSRBlock->u.chm.ha_status= 0x11
PSRBlock->u.cmd.target_status= 0x00
[sanei_scsi] sanei_scsi_cmd: Writing PSRBlock->u.cmd.data_len= 0
[umax] scanner ready
[umax] umax_queue_read_image_data_req for buffer[0], length = 33150
[sanei_scsi] sanei_scsi_cmd: Reading PSRBlock->u.cmd.data_len= 33150
[umax] umax_queue_read_image_data_req: id for buffer[0] is 0
[umax] umax_reader_process: read image data queued for buffer[0]
[umax] umax_queue_read_image_data_req for buffer[1], length = 33150
[sanei_scsi] sanei_scsi_cmd: Reading PSRBlock->u.cmd.data_len= 33150
[umax] umax_queue_read_image_data_req: id for buffer[1] is 0
[umax] umax_reader_process: read image data queued for buffer[1]
[umax] umax_wait_queued_image_data for buffer[0] (id=0)
[umax] sane_read: read 8192 bytes
[umax] sane_read: read 8192 bytes
[umax] sane_read: read 8192 bytes
[umax] sane_read: read 8192 bytes
[umax] umax_reader_process: buffer of 33150 bytes read; 2950350 bytes to go
...
[umax] umax_reader_process: buffer of 33150 bytes read; 1657500 bytes to go
[umax] umax_queue_read_image_data_req for buffer[1], length = 33150
[sanei_scsi] sanei_scsi_cmd: Reading PSRBlock->u.cmd.data_len= 33150
[umax] sane_read: read 382 bytes
[umax] umax_queue_read_image_data_req: id for buffer[1] is 0
[umax] umax_reader_process: read image data queued for buffer[1]
[umax] umax_wait_queued_image_data for buffer[0] (id=0)
[umax] sane_read: read 8192 bytes
[umax] sane_read: read 8192 bytes
[umax] sane_read: read 8192 bytes
[umax] sane_read: read 8192 bytes
[umax] umax_reader_process: buffer of 33150 bytes read; 1624350 bytes to go
[umax] umax_queue_read_image_data_req for buffer[0], length = 33150
[sanei_scsi] sanei_scsi_cmd: Reading PSRBlock->u.cmd.data_len= 33150
[sanei_scsi] sanei_scsi_cmd: DosDevIOCtl failed. rc= 65314
[umax] umax_queue_read_image_data_req: command returned status Error during device I/O
[umax] ERROR: umax_reader_process: unable to queue read image data request!
...
DosDevIOCtl failed. rc= 65314 means 'Interface Busy'
Do you think it makes sense to add 'wait()s' and retry a few times before
giving up or should I suggest to change the card/scanner/cables?
BTW: Sane 1.0.5 works for this user.
Franz
From randy@lemnar.com Tue Jan 20 23:55:41 2004
From: randy@lemnar.com (Randy Becker)
Date: Tue, 20 Jan 2004 18:55:41 -0500
Subject: [sane-devel] Fwd: TWAIN SANE Interface for MacOS X
Message-ID: <2724A547-4BA4-11D8-9D29-0050E4108A1A@lemnar.com>
--Apple-Mail-2--301023028
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
delsp=yes;
format=flowed
Any help?
also, i've begun scanning via the command line over the network and
after a few (~ 15) scans the remote box seems to lock up, and I need to
reboot
it...
-Randy
Begin forwarded message:
> From: Randy Becker
> Date: January 18, 2004 10:56:21 PM EST
> To: mattias.ellert@tsl.uu.se
> Subject: TWAIN SANE Interface for MacOS X
>
> Hello, I just dug up an old scanner of mine, and got it set up with
> saned on my linux box, and am able to use scanimage to scan via it,
> but when I use an application such as Photoshop or GraphicConverter
> and attempt to select the source, the app crashes/disappears. I
> enabled the test interface, so when I bring up the acquire menu, I can
> see and use the test backends, but when I select my networked scanner
> from the list, it crashes. I followed the instructions, and did this:
>
> $ SANE_DEBUG_NET=255 \>
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/
> LaunchCFMApp /Users/rbecker/Desktop/GraphicConverter\ US\
> X/GraphicConverter.app
> [sanei_debug] Setting debug level of net to 255.
> [net] sane_init: authorize = 0x477b6e0, version_code = 0xbfffd830
> [net] sane_init: SANE net backend version 1.0.12 (AF-indep+IPv6) from
> sane-backends 1.0.13
> [net] sane_init: Client has big endian byte order
> [net] sane_init: searching for config file
> [net] sane_init: trying to add 192.168.1.1
> [net] add_device: adding backend 192.168.1.1
> [net] add_device: backend 192.168.1.1 added
> [net] sane_init: done reading config
> [net] sane_init: evaluating environment variable SANE_NET_HOSTS
> [net] sane_init: done
> [net] sane_get_devices: local_only = 0
> [net] connect_dev: trying to connect to 192.168.1.1
> [net] connect_dev: [0] connection succeeded (IPv4)
> [net] connect_dev: sanei_w_init
> [net] connect_dev: net_init (user=rbecker, local version=1.0.3)
> [net] connect_dev: freeing init reply (status=Success, remote
> version=1.0.3)
> [net] connect_dev: done
> [net] sane_get_devices: got 192.168.1.1:umax:/dev/scanner
> [net] sane_get_devices: got 192.168.1.1:umax:/dev/sg0
> [net] sane_get_devices: finished (2 devices)
> [net] sane_open("192.168.1.1:umax:/dev/scanner")
> [net] sane_open: host = 192.168.1.1, device = umax:/dev/scanner
> [net] sane_open: device found in list
> [net] sane_open: net_open
> [net] sane_open: success
> [net] sane_get_option_descriptor: option 1
> [net] sane_get_option_descripter: getting option descriptors
> [net] fetch_options: 0x3da380
> [net] fetch_options: get_option_descriptors
> [net] fetch_options: creating 68 local option descriptors
> [net] fetch_options: copying 68 option descriptors
> [net] fetch_options: 68 options fetched
> Abort trap
>
> Which is where it closes.
>
> Any ideas?
>
> -Randy Becker
>
--Apple-Mail-2--301023028
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
charset=US-ASCII
Any help?
also, i've begun scanning via the command line over the network and
after a few (~ 15) scans the remote box seems to lock up, and I need
to reboot
it...
-Randy
Begin forwarded message:
0000,0000,0000From:
Randy Becker <
0000,0000,0000Date: January
18, 2004 10:56:21 PM EST
0000,0000,0000To:
mattias.ellert@tsl.uu.se
0000,0000,0000Subject: TWAIN SANE
Interface for MacOS X
Hello, I just dug up an old scanner of mine, and got it set up with
saned on my linux box, and am able to use scanimage to scan via it,
but when I use an application such as Photoshop or GraphicConverter
and attempt to select the source, the app crashes/disappears. I
enabled the test interface, so when I bring up the acquire menu, I can
see and use the test backends, but when I select my networked scanner
from the list, it crashes. I followed the instructions, and did this:
$ SANE_DEBUG_NET=255 \>
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
/Users/rbecker/Desktop/GraphicConverter\ US\ X/GraphicConverter.app
[sanei_debug] Setting debug level of net to 255.
[net] sane_init: authorize = 0x477b6e0, version_code = 0xbfffd830
[net] sane_init: SANE net backend version 1.0.12 (AF-indep+IPv6) from
sane-backends 1.0.13
[net] sane_init: Client has big endian byte order
[net] sane_init: searching for config file
[net] sane_init: trying to add 192.168.1.1
[net] add_device: adding backend 192.168.1.1
[net] add_device: backend 192.168.1.1 added
[net] sane_init: done reading config
[net] sane_init: evaluating environment variable SANE_NET_HOSTS
[net] sane_init: done
[net] sane_get_devices: local_only = 0
[net] connect_dev: trying to connect to 192.168.1.1
[net] connect_dev: [0] connection succeeded (IPv4)
[net] connect_dev: sanei_w_init
[net] connect_dev: net_init (user=rbecker, local version=1.0.3)
[net] connect_dev: freeing init reply (status=Success, remote
version=1.0.3)
[net] connect_dev: done
[net] sane_get_devices: got 192.168.1.1:umax:/dev/scanner
[net] sane_get_devices: got 192.168.1.1:umax:/dev/sg0
[net] sane_get_devices: finished (2 devices)
[net] sane_open("192.168.1.1:umax:/dev/scanner")
[net] sane_open: host = 192.168.1.1, device = umax:/dev/scanner
[net] sane_open: device found in list
[net] sane_open: net_open
[net] sane_open: success
[net] sane_get_option_descriptor: option 1
[net] sane_get_option_descripter: getting option descriptors
[net] fetch_options: 0x3da380
[net] fetch_options: get_option_descriptors
[net] fetch_options: creating 68 local option descriptors
[net] fetch_options: copying 68 option descriptors
[net] fetch_options: 68 options fetched
Abort trap
Which is where it closes.
Any ideas?
-Randy Becker
--Apple-Mail-2--301023028--
From mike@alezan.org Wed Jan 21 10:50:47 2004
From: mike@alezan.org (Mickael Profeta)
Date: Wed, 21 Jan 2004 11:50:47 +0100
Subject: [sane-devel] HP Scanjet 3690 support
In-Reply-To: <20040115201730.GB1768@meier-geinitz.de>
References: <20040115201730.GB1768@meier-geinitz.de>
Message-ID: <400E5987.60100@alezan.org>
Hi
>> The logs are in http://www.alezan.org/hp3670/, in SnoopyPro binary format. I
>>tried to use usblogdump in Linux but it doesn't work very well for me. I had to
>>analyze them in Windoze using SnoopyPro.
>
>
> I'll check later. I don't have a working Windows or WINE installation
> currently.
sorry about that, I manage to export once in xml format, but do not
manage anymore???
I tried also to use sniffusb-0.13, but the debugger (dbview) failed to
connect (can not contact driver???). Maybe because I am using windows XP
Home, does someone know a workaround? Another usb sniffer?
> You can try that for testing. But this can't be used in the published
> version because control messages like that will confuse non-gl646
> scanners. That's the reason we use the descriptor to identify the
> chipset first and then send specific commands. That's not absolutely
> safe either but better then writing directly.
I will try to test this to see if we can get some informations...
Mike
From gerard@gkall.hobby.nl Wed Jan 21 13:33:19 2004
From: gerard@gkall.hobby.nl (gerard klaver)
Date: Wed, 21 Jan 2004 12:33:19 -0100
Subject: [sane-devel] HP Scanjet 3690 support
In-Reply-To: <400E5987.60100@alezan.org>
References:
<20040115201730.GB1768@meier-geinitz.de> <400E5987.60100@alezan.org>
Message-ID: <1074691999.2002.1.camel@gk-lex3>
On Wed, 2004-01-21 at 09:50, Mickael Profeta wrote:
> Hi
>
> >> The logs are in http://www.alezan.org/hp3670/, in SnoopyPro binary format. I
> >>tried to use usblogdump in Linux but it doesn't work very well for me. I had to
> >>analyze them in Windoze using SnoopyPro.
> >
> >
> > I'll check later. I don't have a working Windows or WINE installation
> > currently.
>
> sorry about that, I manage to export once in xml format, but do not
> manage anymore???
> I tried also to use sniffusb-0.13, but the debugger (dbview) failed to
> connect (can not contact driver???). Maybe because I am using windows XP
> Home, does someone know a workaround? Another usb sniffer?
>
Did you try sniff-usb 1.8
See http://benoit.papillault.free.fr/usbsnoop/index.en.php
--
----------
m.vr.gr.
Gerard Klaver
From gerhard@gjaeger.de Wed Jan 21 19:07:20 2004
From: gerhard@gjaeger.de (Jaeger, Gerhard)
Date: Wed, 21 Jan 2004 20:07:20 +0100
Subject: [sane-devel] Test-Backend, pthreads & MacOSX
Message-ID: <200401212007.20275.gerhard@gjaeger.de>
Hi,
I've changed the test-backend, that way, that the reader-process now
terminates, when running as thread.
This change should allow to run the test-backend on MacOSX without
patching the sanei_thread lib.
Mattias, you might can check this. By removing your patch from the
MacOSX SANE-version, the plustek backend and probably others should
also run again without hanging after a scan....
Ciao,
Gerhard
From jb@jblache.org Wed Jan 21 21:35:40 2004
From: jb@jblache.org (Julien BLACHE)
Date: Wed, 21 Jan 2004 22:35:40 +0100
Subject: [sane-devel] xsane and Gimp 2.0
In-Reply-To: <87d69h8d3i.fsf@frigate.technologeek.org> (Julien BLACHE's
message of "Sun, 18 Jan 2004 16:56:33 +0100")
References: <20040118143853.GA13079@acheron.the-domination.com>
<87d69h8d3i.fsf@frigate.technologeek.org>
Message-ID: <87n08hf0ib.fsf@frigate.technologeek.org>
Julien BLACHE wrote:
Hi,
>
>
> Apply to a clean source tree with patch -p1, run configure, build. It
> defaults to GTK2+GIMP2.0. (you don't need to run autoconf)
I updated the patch, as GIMP 2.0pre2 got fixed with regard to the
version string. 2.0pre2 outputs 1.3.25 as its version string, so the
autoconf works fine.
Also, gimptool-1.3 was renamed to gimptool-2.0 and the gimp-1.3.pc
file was renamed to gimp-2.0.pc, so the macro for the autoconf test
had to be updated.
Oliver, please apply this patch instead of the previous one.
JB.
--
Julien BLACHE
GPG KeyID 0xF5D65169
From stewart@midtoad.homelinux.org Thu Jan 22 07:20:35 2004
From: stewart@midtoad.homelinux.org (Stewart Midwinter)
Date: Thu, 22 Jan 2004 00:20:35 -0700
Subject: [sane-devel] HP 5500c scanner support?
In-Reply-To: <20040122053613.31650.45428.Mailman@quantz.debian.org>
References: <20040122053613.31650.45428.Mailman@quantz.debian.org>
Message-ID: <20040122002035.263116f0.stewart@midtoad.homelinux.org>
Has anyone done any work on getting the HP 5500c scanner supported? I know it's not on the compatibility list, but...
Seeing as how I have one, is there anything I could could do to help this along? run some tools? generate a log/debug file?
thanks
Stewart in Calgary
From mike@alezan.org Thu Jan 22 09:26:49 2004
From: mike@alezan.org (Mickael Profeta)
Date: Thu, 22 Jan 2004 10:26:49 +0100
Subject: [sane-devel] HP Scanjet 3690 support
In-Reply-To: <1074691999.2002.1.camel@gk-lex3>
References: <20040115201730.GB1768@meier-geinitz.de> <400E5987.60100@alezan.org> <1074691999.2002.1.camel@gk-lex3>
Message-ID: <400F9759.6010803@alezan.org>
Hi
> Did you try sniff-usb 1.8
> See http://benoit.papillault.free.fr/usbsnoop/index.en.php
Great Idea!!
This works perfectly and I can get all the transaction even during and
after the previsualisation scan
I put here the log (in ascii format this time) of the initialisation of
the scanner : usbsnoop_init.log
and of a session from initialisation to the and of the preview scan
usbsnoop_preview.log.gz (careful, it is 5Mo compressed)
I also try to play with sane-find scanner
log_sane_find_scanner is the original output
log_sane_find_scanner_modify is a bad hack where I remove the return 0;
lines in check-usb-chip for the check_gl646 function
Don't know if it can give information but it does not seems to say it
can not read or write the registers....
If you have any idea or comments...
Mike
From Oliver.Rauch@Rauch-Domain.DE Thu Jan 22 16:37:55 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: Thu, 22 Jan 2004 17:37:55 +0100
Subject: [sane-devel] xsane and Gimp 2.0
In-Reply-To: <87n08hf0ib.fsf@frigate.technologeek.org>
References: <20040118143853.GA13079@acheron.the-domination.com> <87d69h8d3i.fsf@frigate.technologeek.org> <87n08hf0ib.fsf@frigate.technologeek.org>
Message-ID: <200401221737.57819.Oliver.Rauch@Rauch-Domain.DE>
Hello Julien,
Thanks for the new patch. I will take a look at it when I have some more =
time.=20
It will take some time to do the tests with different gimp and gtk versio=
ns=20
and disabling gimp, forcing it to use a special version, etc.
Oliver
Am Mittwoch, 21. Januar 2004 22:35 schrieb Julien BLACHE:
> Julien BLACHE wrote:
>
> Hi,
>
> >
> >
> > Apply to a clean source tree with patch -p1, run configure, build. It
> > defaults to GTK2+GIMP2.0. (you don't need to run autoconf)
>
> I updated the patch, as GIMP 2.0pre2 got fixed with regard to the
> version string. 2.0pre2 outputs 1.3.25 as its version string, so the
> autoconf works fine.
>
> Also, gimptool-1.3 was renamed to gimptool-2.0 and the gimp-1.3.pc
> file was renamed to gimp-2.0.pc, so the macro for the autoconf test
> had to be updated.
>
> Oliver, please apply this patch instead of the previous one.
>
> JB.
--=20
http://www.xsane.org
http://www.rauch-domain.de
http://www.sane-project.org
From joerg.pr@olivfabric.de Thu Jan 22 18:46:59 2004
From: joerg.pr@olivfabric.de (joerg.pr@olivfabric.de)
Date: Thu, 22 Jan 2004 19:46:59 +0100
Subject: [sane-devel] Unsupported: Mustek BearPaw 4800TA Pro II
Message-ID:
J=F6rg Preisend=F6rfer | http://www.olivfabric.de
Berlin, Jan. 22nd 2004
Hi there,
I've just encountered the following unsupported scanner:
MUSTEK Be@rPaw 4800TA Pro II
Pls note it reports to be manufactured by Hewlett-Packard.
------------------
emtry in /proc/bus/usb/devices:
T: Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D01 Cnt=3D01 Dev#=3D 2 Spd=3D12 MxCh=
=3D 0
D: Ver=3D 2.00 Cls=3D00(>ifc ) Sub=3D00 Prot=3D00 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D055f ProdID=3D040a Rev=3D 1.00
S: Manufacturer=3DHewlett-Packard.
S: Product=3DUSB2.0 Scanner
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D100mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3Dff(vend.) Sub=3Dff Prot=3Dff Driver=3D=
usbscanner
E: Ad=3D01(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D83(I) Atr=3D03(Int.) MxPS=3D 1 Ivl=3D3ms
------------------
chipset (in order of increasing size):
1.
SQ [brand]
SQ100A
A335-9901
---
2.
UTC QGOB
L6219
TB
[O in 1st line may be a Zero]
---
3.
ISSI [brand]
IS42S16100A1-7T
X11882000D 0336
----
4.
SQ [brand]
SQ113C
0335-1408
D0KNS-013
[Zeroes may be O]
Any ideas?
Cheers,
J=F6rg (=3D Georg)
From llopis@verizon.net Fri Jan 23 01:02:16 2004
From: llopis@verizon.net (Noel Llopis)
Date: Thu, 22 Jan 2004 20:02:16 -0500
Subject: [sane-devel] Timeout problems with HP ScanJet 4100C
Message-ID: <200401222002.16604.llopis@verizon.net>
Hello,
I have recently bought a scanner HP ScanJet 4100C USB specifically because I
saw it as one of the ones that had complete support in the SANE web site:
http://www.sane-project.org/sane-supported-devices.html
I'm running Mandrake 9.2 with the 2.4.22 kernel.
I plugged it in and it was automatically mounted on dev/usb/scanner0. I was
able to use it with Kooka and with The Gimp plugin directly. So I was very
pleased.
However, there's something weird going on. If I leave the scanner plugged in
and I reboot my computer, it will sit for about one minute at the "Checking
for new hardware" step and eventually continue. When I check dmesg I see all
these warnings:
usb.c: registered new driver usbscanner
scanner.c: USB scanner device (0x03f0/0x0101) now attached to scanner0
scanner.c: 0.4.14:USB Scanner Driver
[...snip...]
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb-uhci.c: interrupt, status 2, frame# 1962
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 100 ret -110
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 100 ret -110
usb-uhci.c: interrupt, status 2, frame# 2039
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 6 rqt 128 rq 6 len 100 ret -110
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 100 ret -110
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 100 ret -110
usb_control/bulk_msg: timeout
The problem isn't just that. If I type cat /proc/bus/usb/devices, I will get a
similar pause, and the same thing will happen when I try to run the Mandrake
Control Center or HardDrake.
Incidentally, here's the output of my usb/devices with only the scanner
plugged in:
T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.04
S: Manufacturer=Linux 2.4.22-21mdksmpcustom ehci_hcd
S: Product=Intel Corp. 82801EB USB2
S: SerialNumber=00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=ff20
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=03f0 ProdID=0101 Rev= 1.00
S: SerialNumber=00MY8B5534VD
C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=usbscanner
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=ff40
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=ff60
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=ff80
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
And sane-find-scanner reports the following:
found USB scanner (vendor=0x03f0, product=0x0101) at /dev/usb/scanner0
found USB scanner (vendor=0x03f0, product=0x0101) at libusb:004:006
Any idea what is going on? Everything seems to work fine except for those
delays. Is there anything I can check or change to try to diagnose the
problem a bit better? I'm willing to try anything.
Thanks in advance.
--Noel
From maher@its.caltech.edu Fri Jan 23 07:49:25 2004
From: maher@its.caltech.edu (Joseph M. Maher)
Date: Thu, 22 Jan 2004 23:49:25 -0800 (PST)
Subject: [sane-devel] sane on linux 2.6
Message-ID:
I have a hp 2110, and I'm running debian unstable on a vanilla 2.6.1
kernel.
Printing works, but scanning doesn't.
I guess this is a bug, but I'm not sure which package to report it
against...
>ariadne:/home/maher# scanimage --list devices
>
>No scanners were identified. If you were expecting something different,
>check that the scanner is plugged in, turned on and detected by the
>sane-find-scanner tool (if appropriate). Please read the documentation
>which came with this software (README, FAQ, manpages).
Running sane-find-scanner (which I know isn't meant to work for hpoj)
gives me a kernel oops:
Jan 22 23:17:33 ariadne kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000003
Jan 22 23:17:33 ariadne kernel: printing eip:
Jan 22 23:17:33 ariadne kernel: c01565c0
Jan 22 23:17:33 ariadne kernel: *pde = 00000000
Jan 22 23:17:33 ariadne kernel: Oops: 0000 [#1]
Jan 22 23:17:33 ariadne kernel: CPU: 0
Jan 22 23:17:33 ariadne kernel: EIP: 0060:[chrdev_open+80/320] Not
tainted
Jan 22 23:17:33 ariadne kernel: EFLAGS: 00010206
Jan 22 23:17:33 ariadne kernel: EIP is at chrdev_open+0x50/0x140
Jan 22 23:17:33 ariadne kernel: eax: 00000003 ebx: d6366a00 ecx:
d6366a3c edx: d17b2a1c
Jan 22 23:17:33 ariadne kernel: esi: 00000000 edi: 00000000 ebp:
d17b2914 esp: d1ab3f20
Jan 22 23:17:33 ariadne kernel: ds: 007b es: 007b ss: 0068
Jan 22 23:17:33 ariadne kernel: Process sane-find-scann (pid: 1117,
threadinfo=d1ab2000 task=d241a6a0)
Jan 22 23:17:33 ariadne kernel: Stack: 00000000 01500000 d1ab3f2c 00000000
d1e2c480 d17b2914 00000000 d7ff41c0
Jan 22 23:17:33 ariadne kernel: c014d530 d17b2914 d1e2c480 00000882
00020000 d40b7000 d1ab2000 c014d418
Jan 22 23:17:33 ariadne kernel: d17cc880 d7ff41c0 00000882 d1ab3f70
d17cc880 d7ff41c0 fffffff4 d40b7000
Jan 22 23:17:33 ariadne kernel: Call Trace:
Jan 22 23:17:33 ariadne kernel: [dentry_open+272/416]
dentry_open+0x110/0x1a0
Jan 22 23:17:33 ariadne kernel: [filp_open+104/112] filp_open+0x68/0x70
Jan 22 23:17:33 ariadne kernel: [sys_open+91/144] sys_open+0x5b/0x90
Jan 22 23:17:33 ariadne kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Jan 22 23:17:33 ariadne kernel:
Jan 22 23:17:33 ariadne kernel: Code: 8b 00 85 c0 74 0b 83 38 02 74 60 ff
80 00 01 00 00 8b 43 38
Jan 22 23:17:38 ariadne kernel: spurious 8259A interrupt: IRQ7.
Jan 22 23:39:56 ariadne kernel: request_module: failed /sbin/modprobe --
char-major-81-0. error = 256
I'd be happy to supply any more information if it would be useful.
Yours
Joseph
From gough@gsc.riken.jp Fri Jan 23 15:39:29 2004
From: gough@gsc.riken.jp (Julian Gough)
Date: 24 Jan 2004 00:39:29 +0900
Subject: [sane-devel] Epson GT-7400U not detected
In-Reply-To: <871xq0h9vo.fsf@zen.epkowa.co.jp>
References: <1072823795.721.38.camel@invigiator.invigiator.com>
<20031231100823.GI1003@meier-geinitz.de> <878ykkehan.fsf@zen.epkowa.co.jp>
<200401111535.31596.Oliver.Schwartz@gmx.de>
<1073919837.4417.8.camel@localhost.localdomain>
<87k73wu0wz.fsf@zen.epkowa.co.jp>
<1073960870.4410.4.camel@localhost.localdomain>
<873caktv64.fsf@zen.epkowa.co.jp> <1073963701.4558.90.camel@tao>
<871xq0h9vo.fsf@zen.epkowa.co.jp>
Message-ID: <1074872369.3873.6.camel@localhost.localdomain>
> I would not (yet) call it a dead-end.
I didn't mean the whole scanner, just this approach to getting it
sorted.
> It just doesn't work for you at
> this point in time. It may very well be that a couple of tweaks here
> and there in the snapscan backend will make it work. Unfortunately, I
> am not familiar with this backend and lack time and access to a
> GT-7400.
>
> BTW, I haven't seen any 'SANE_DEBUG_SNAPSCAN=128 scanimage' output fly
> by, IIRC. Maybe that can shed some light on your problems.
as always
[me@localhost]# SANE_DEBUG_SCANPSCAN=128 scanimage
scanimage: no SANE devices found
[me@localhost]#
From henning@meier-geinitz.de Fri Jan 23 16:36:05 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 23 Jan 2004 17:36:05 +0100
Subject: [sane-devel] Epson GT-7400U not detected
In-Reply-To: <1074872369.3873.6.camel@localhost.localdomain>
References: <20031231100823.GI1003@meier-geinitz.de> <878ykkehan.fsf@zen.epkowa.co.jp> <200401111535.31596.Oliver.Schwartz@gmx.de> <1073919837.4417.8.camel@localhost.localdomain> <87k73wu0wz.fsf@zen.epkowa.co.jp> <1073960870.4410.4.camel@localhost.localdomain> <873caktv64.fsf@zen.epkowa.co.jp> <1073963701.4558.90.camel@tao> <871xq0h9vo.fsf@zen.epkowa.co.jp> <1074872369.3873.6.camel@localhost.localdomain>
Message-ID: <20040123163605.GB1659@meier-geinitz.de>
Hi,
On Sat, Jan 24, 2004 at 12:39:29AM +0900, Julian Gough wrote:
> > BTW, I haven't seen any 'SANE_DEBUG_SNAPSCAN=128 scanimage' output fly
> > by, IIRC. Maybe that can shed some light on your problems.
>
> as always
>
> [me@localhost]# SANE_DEBUG_SCANPSCAN=128 scanimage
> scanimage: no SANE devices found
> [me@localhost]#
SANE_DEBUG_SNAPSCAN not SANE_DEBUG_SCANPSCAN.
This should pront debug messages.
Bye,
Henning
From rm.riches@verizon.net Sat Jan 24 03:59:11 2004
From: rm.riches@verizon.net (Robert M. Riches Jr.)
Date: Fri, 23 Jan 2004 19:59:11 -0800
Subject: [sane-devel] (resend) how to undo saved working directory?
Message-ID: <200401240359.i0O3xBPA025286@one.localnet>
(Apologies if this gets posted twice. I made the mistake of
subscribing an email address that is a forwarding service,
so I can't send from that address, so postings are blocked
for moderator review. Apologies in advance if I make any
more breaches of list etiquette.)
When using the version of xsane that comes with Red Hat
Linux 9, which claims to be xsane-0.89, I find an
interesting feature. Now, xsane remembers the "working
directory" from some earlier session and puts all the files
from --save mode there, rather than the _real_ working
directory where I'm working today. I realize most
GUI-oriented users probably want all their image files
stored in one directory, and they start xsane from their
Gnome or KDE menus. However, when I'm working in directory
Z and bring up xsane from the command line while in
directory Z, I want xsane to put the files in directory Z.
Tomorrow, I will be in another directory, and I want xsane
put the files there.
I found the "working directory" file squirreled away in file
~/.sane/xsane/xsane.rc, lines 5 and 6. A quick wrapper
script in Perl could update the file to reflect the
directory from which I'm invoking xsane. That would be much
easier than hacking the source code to the program to change
this unwelcome-to-me feature.
Is there a better and/or easier way to get xsane to use the
current working directory from which it is invoked?
Thanks.
Robert Riches
rm.riches@verizon.net
From ojt@gexcon.com Sat Jan 24 12:15:47 2004
From: ojt@gexcon.com (Ole Jacob Taraldset)
Date: Sat, 24 Jan 2004 13:15:47 +0100
Subject: [sane-devel] iscan: "Could not send command to scanner"
Message-ID: <200401241315.47918.ojt@gexcon.com>
Hi,
I have an Epson Perfection 1650 Photo which I have been using with iscan. Now
suddenly iscan doesn't work any more and just give me a dialog box saying
"Could not send command to scanner". Xsane still works and recognizes my
scanner without any problems.
My system is a RedHat 9 box with freshrpms updates and the following:
sane-backends-1.0.9-5.1
sane-frontends-1.0.9-2
xsane-0.89-3
iscan-1.5.2-1.redhat.8.0
I've also tried iscan 1.4, but get the same result.
My /etc/sane.d/epkowa.conf contains:
usb /dev/usb/scanner0
My /etc/sane.d/epson.conf contains:
usb /dev/usb/scanner0
I have tried to remove one or the other but this doesn't seem to help.
Regards,
Ole Jacob
--
GexCon AS, Bergen, Norway
PGP key :
ICQ UIN : 5366306 | Jabber: ojt@jabber.org
From jimquigley9@eircom.net Sat Jan 24 19:38:34 2004
From: jimquigley9@eircom.net (Jim Quigley)
Date: Sat, 24 Jan 2004 19:38:34 +0000
Subject: [sane-devel] sane on linux 2.6
Message-ID: <4012C9BA.8000500@eircom.net>
hi
One possible reason it happened to me on suse 9, linux 2.6.1, you have
to compile all usb options incl usb support as modules.
LmCogs
From amitofsk@obiwan.csl.uiuc.edu Sat Jan 24 21:56:51 2004
From: amitofsk@obiwan.csl.uiuc.edu (Andy Mitofsky)
Date: Sat, 24 Jan 2004 15:56:51 -0600
Subject: [sane-devel] sane frontend questions
In-Reply-To: <87wu7vqqa7.fsf@zen.epkowa.co.jp>
References: <20040113053607.GB10111@obiwan.csl.uiuc.edu> <87wu7vqqa7.fsf@zen.epkowa.co.jp>
Message-ID: <20040124215651.GA8359@obiwan.csl.uiuc.edu>
I just wanted to say thanks for the help from about a week ago,
especially to Olaf Meeuwissen. I was able to get iscan to work on my computer.
For the record, to get it to work, I installed an older version of gtk,
gtk+-1.2.10, and used the suggested version of iscan, iscan-1.5.2-1.redhat.8.0.tar.gz. I
At that point, I got compile errors relating to libgdk_imlib. I had the
file /usr/lib/libgdk_imlib.so.1 on my machine but not gdk_imlib.h. To
get around this, I deleted the lines including gdk_imlib.hfrom
pisa_structs.h. and pisa_view_manager.cc. I also changed some lines of
pisa_view_manager.cc from
::gdk_imlib_init ( );
::gtk_widget_push_visual ( ::gdk_imlib_get_visual ( ) );
::gtk_widget_push_colormap ( ::gdk_imlib_get_colormap ( ) );
to
::gtk_widget_push_visual ( ::gdk_rgb_get_visual ( ) );
::gtk_widget_push_colormap ( ::gdk_rgb_get_cmap ( ) );
I'm not sure what this did, but it seemed to work. Again, thanks
for your help. Bye, Andy
>
> If you insist on compiling from "source" with gcc-3.2 or later, please
> get the correct tar-ball: iscan-1.5.2-1.redhat.8.0.tar.gz.
>
> The C++ ABI changed a few times between 2.9x and 3.2 and the iscan
> "sources" contain several closed C++ source based binary objects. The
> regular iscan-1.5.2-1.tar.gz is for g++-2.9x, the one mentioned above
> is for g++-3.2 or later.
>
> Hope this helps,
> --
> Olaf Meeuwissen EPSON KOWA Corporation, ECS
> GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
> Penguin's lib! -- I hack, therefore I am -- LPIC-2
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request@lists.alioth.debian.org
From jb@jblache.org Sun Jan 25 13:09:00 2004
From: jb@jblache.org (Julien BLACHE)
Date: Sun, 25 Jan 2004 14:09:00 +0100
Subject: [sane-devel] xsane and Gimp 2.0
In-Reply-To: <200401221737.57819.Oliver.Rauch@Rauch-Domain.DE> (Oliver
Rauch's message of "Thu, 22 Jan 2004 17:37:55 +0100")
References: <20040118143853.GA13079@acheron.the-domination.com>
<87d69h8d3i.fsf@frigate.technologeek.org>
<87n08hf0ib.fsf@frigate.technologeek.org>
<200401221737.57819.Oliver.Rauch@Rauch-Domain.DE>
Message-ID: <87oessyy37.fsf@frigate.technologeek.org>
Oliver Rauch wrote:
Hi Oliver,
> Thanks for the new patch. I will take a look at it when I have some more time.
> It will take some time to do the tests with different gimp and gtk versions
> and disabling gimp, forcing it to use a special version, etc.
Patch updated again, added a call (mandatory) to gimp_extension_ack()
before running the xsane interface.
New patch at
JB.
--
Julien BLACHE
GPG KeyID 0xF5D65169
From meuk@olifantasia.com Sun Jan 25 17:43:16 2004
From: meuk@olifantasia.com (Martin)
Date: Sun, 25 Jan 2004 18:43:16 +0100
Subject: [sane-devel] patch to make sane-backends compile and work on cygwin (cygwin without
shared mem)
Message-ID: <40140034.9000102@olifantasia.com>
This is a multi-part message in MIME format.
--------------030304050206040903000404
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Hi all,
I use sane on cygwin on windows 2000.
A little while back I hacked sane-backends to compile on cygwin (only for scsi scanners and no fork support)
Recently I found out that the official cvs version of sane-backends now supports cygwin (better than my hackwork).
It works wonderfully both with scsi as with usb scanners (thanks to libusb-win32)
I did however have to make two small changes to make it compile on my cygwin.
Disable the artec_eplus48u backend since it needs shared memory (not supported on all cygwin installations)
#undef interface because some win32api include defines this and the name interface is used as a variable.
So if a recent sane snapshot does not compile on your cygwin installation try this patch.
The patch is made against the cvs version of sane-backends of 1 december 2003 (snapshot sane-backends-2003-12-01.tar.gz)
You can also find this patch on:
http://sourceforge.net/tracker/index.php?func=detail&aid=858540&group_id=71382&atid=531104
This is the patches page of
http://sourceforge.net/projects/hp5400backend/
I tested the patch with the microtek2 backend (parallel scsi, original windows driver has to be installed for the parallel scsi driver)
and hp5400 backend (usb, using libusb-win32)
They both work fine
I hope this patch is of use for anyone.
greetings,
Martin Dvh
--------------030304050206040903000404
Content-Type: text/plain;
name="sane_cygwin.patch.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="sane_cygwin.patch.txt"
diff -urN sane-backends_orig/backend/dll.conf sane-backends/backend/dll.conf
--- sane-backends_orig/backend/dll.conf 2003-11-24 09:53:30.000000000 +0100
+++ sane-backends/backend/dll.conf 2003-12-02 01:41:50.000000000 +0100
@@ -5,7 +5,7 @@
apple
avision
artec
-artec_eplus48u
+#artec_eplus48u
as6e
bh
canon
diff -urN sane-backends_orig/configure sane-backends/configure
--- sane-backends_orig/configure 2003-11-24 09:53:30.000000000 +0100
+++ sane-backends/configure 2003-12-02 01:39:56.000000000 +0100
@@ -23919,7 +23919,8 @@
microtek2 mustek mustek_pp mustek_usb nec pie plustek \
plustek_pp ricoh s9036 sceptre sharp \
sp15c st400 tamarack test teco1 teco2 teco3 umax umax_pp umax1220u \
- artec_eplus48u ma1509 ibm hp5400"
+ ma1509 ibm hp5400"
+ BACKENDS_THAT_NEEDSHARED_MEM="artec_eplus48u"
if test "${sane_cv_use_libjpeg}" != "yes"; then
echo "*** disabling DC210 backend (failed to find JPEG library)"
diff -urN sane-backends_orig/configure.in sane-backends/configure.in
--- sane-backends_orig/configure.in 2003-11-24 09:53:30.000000000 +0100
+++ sane-backends/configure.in 2003-12-02 01:40:32.000000000 +0100
@@ -280,7 +280,8 @@
microtek2 mustek mustek_pp mustek_usb nec pie plustek \
plustek_pp ricoh s9036 sceptre sharp \
sp15c st400 tamarack test teco1 teco2 teco3 umax umax_pp umax1220u \
- artec_eplus48u ma1509 ibm hp5400"
+ ma1509 ibm hp5400"
+ BACKENDS_THAT_NEEDSHARED_MEM="artec_eplus48u"
if test "${sane_cv_use_libjpeg}" != "yes"; then
echo "*** disabling DC210 backend (failed to find JPEG library)"
diff -urN sane-backends_orig/tools/sane-find-scanner.c sane-backends/tools/sane-find-scanner.c
--- sane-backends_orig/tools/sane-find-scanner.c 2003-09-24 05:41:48.000000000 +0200
+++ sane-backends/tools/sane-find-scanner.c 2003-12-02 02:15:54.000000000 +0100
@@ -40,6 +40,9 @@
#include
#include
#endif
+#ifdef interface
+#undef interface
+#endif
#include "../include/sane/sanei.h"
#include "../include/sane/sanei_scsi.h"
--------------030304050206040903000404--
From Oliver.Rauch@Rauch-Domain.DE Sun Jan 25 22:01:53 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: Sun, 25 Jan 2004 23:01:53 +0100
Subject: [sane-devel] (resend) how to undo saved working directory?
In-Reply-To: <200401240359.i0O3xBPA025286@one.localnet>
References: <200401240359.i0O3xBPA025286@one.localnet>
Message-ID: <200401252301.56058.Oliver.Rauch@Rauch-Domain.DE>
You can change the working directory in the menu
preferences->change direcotry
XSane always uses the working directory that is listed in the xsane.rc fi=
le.
When there is no xsane.rc file or there is no working directory listed in=
the
xsane.rc file then xsane uses the recent working directory.
xsane always saves the selected working direcotry line to the xsane.rc fi=
le
when xsane exits.
Oliver
Am Samstag, 24. Januar 2004 04:59 schrieb Robert M. Riches Jr.:
> (Apologies if this gets posted twice. I made the mistake of
> subscribing an email address that is a forwarding service,
> so I can't send from that address, so postings are blocked
> for moderator review. Apologies in advance if I make any
> more breaches of list etiquette.)
>
> When using the version of xsane that comes with Red Hat
> Linux 9, which claims to be xsane-0.89, I find an
> interesting feature. Now, xsane remembers the "working
> directory" from some earlier session and puts all the files
> from --save mode there, rather than the _real_ working
> directory where I'm working today. I realize most
> GUI-oriented users probably want all their image files
> stored in one directory, and they start xsane from their
> Gnome or KDE menus. However, when I'm working in directory
> Z and bring up xsane from the command line while in
> directory Z, I want xsane to put the files in directory Z.
> Tomorrow, I will be in another directory, and I want xsane
> put the files there.
>
> I found the "working directory" file squirreled away in file
> ~/.sane/xsane/xsane.rc, lines 5 and 6. A quick wrapper
> script in Perl could update the file to reflect the
> directory from which I'm invoking xsane. That would be much
> easier than hacking the source code to the program to change
> this unwelcome-to-me feature.
>
> Is there a better and/or easier way to get xsane to use the
> current working directory from which it is invoked?
>
> Thanks.
>
> Robert Riches
> rm.riches@verizon.net
--=20
http://www.xsane.org
http://www.rauch-domain.de
http://www.sane-project.org
From maher@its.caltech.edu Sun Jan 25 20:29:01 2004
From: maher@its.caltech.edu (Joseph M. Maher)
Date: Sun, 25 Jan 2004 12:29:01 -0800 (PST)
Subject: [sane-devel] sane on linux 2.6
Message-ID:
>I have a hp 2110, and I'm running debian unstable on a vanilla 2.6.1
>kernel.
>
>Printing works, but scanning doesn't.
Scanning works with the cvs version of hpoj.
Joseph
From rm.riches@verizon.net Mon Jan 26 01:31:27 2004
From: rm.riches@verizon.net (Robert M. Riches Jr.)
Date: Sun, 25 Jan 2004 17:31:27 -0800
Subject: [sane-devel] (resend) how to undo saved working directory?
Message-ID: <200401260131.i0Q1VRWS017869@one.localnet>
> From: Oliver Rauch
> Date: Sun, 25 Jan 2004 23:01:53 +0100
>
> You can change the working directory in the menu
> preferences->change direcotry
>
> XSane always uses the working directory that is listed in the xsane.rc file.
> When there is no xsane.rc file or there is no working directory listed in the
> xsane.rc file then xsane uses the recent working directory.
>
> xsane always saves the selected working direcotry line to the xsane.rc file
> when xsane exits.
Thank you for pointing out the path to the working directory
menu item. I had searched under preferences->setup->save
and had missed the obvious at the bottom of the menu.
So, let's say on Monday I'm working in directory A and use
the menu item to have xsane put files there. Then, on
Tuesday, I have an xterm in directory B and start up xsane
from that xterm, so that the xsane process's cwd (current
working directory) from the OS is B. Xsane will put the
files in A, where I was on Monday (unless I go through the
menu to tell xsane information it already has)? I would say
that's undesirable behavior for any user other than ones
whose world revolves around "My Documents". I, for one,
liked the older (circa 0.84) behavior on this point.
What is the potential for an RFE or patch submission for a
command line option or environment variable to allow the
user to control whether xsane uses the OS's cwd vs. the
directory saved in the xsanerc file from the previous
session? (I'm about 50% for minor enhancement patch
submissions to other programs: one accept, one reject, one
accept with modifications.)
Or, should I just write a quick Perl wrapper script to
modify the xsanerc file before invoking the real xsane?
Thanks.
Robert Riches
rm.riches@verizon.net
From satimis@icare.com.hk Mon Jan 26 05:33:25 2004
From: satimis@icare.com.hk (Stephen Liu)
Date: Mon, 26 Jan 2004 13:33:25 +0800
Subject: [sane-devel] OT: Equivalent software to PaperPort etc. for Win
Message-ID: <4014A6A5.20501@icare.com.hk>
Hi all folks,
I am using SANE for scanning on Linux.
I have been searching for a software from Open Source running on
Linux/Unix equivalent to PaperPort/PageMaker/OmniPage/BZ.Doc of BiziSoft
etc. for Win. They are graphic editing software with database
integrated. They have a platform/table to retain scanned documents
visually and combine them as a file which can be saved in many formats.
Each page inside the file can be rearranged, i.e. page-1 can be
re-inserted as page-13, etc. and all pages will be re-numbered
automatically thereafter. The pages can be editted both graphically or
textwise.
They have a powerful database to search documents on their titiles or
contents. The database can be update at night at a pre-fixed time. The
documents can be OCR.
To my understanding any graphic editing software on Linux with Plugin
for scanner such as GIMP can do the job. But the operation would not be
so simple and handy.
Any advice???
TIA
B.R.
Stephen Liu
From till.kamppeter@gmx.net Mon Jan 26 19:12:48 2004
From: till.kamppeter@gmx.net (Till Kamppeter)
Date: Mon, 26 Jan 2004 19:12:48 +0000
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a linux application?
In-Reply-To:
References:
Message-ID: <401566B0.70109@gmx.net>
I recommend that you post this on the SANE mailing list
(http://www.sane-project.org/), as this is a scanning problem. I am
CCing this posting to there.
AFAIK noone has written a driver for scanner buttons yet (also not for
other scanner models). The scanner probably sends a certain signal
through the USB which is caught by a background process under Windows.
This process then starts a program to do the scan. The best way to write
a similar program under Linux is to use a USB sniffer to analyze how the
signal looks like and then write a daemon which listens for such signals.
Till
Alton Hernandez wrote:
> Hi,
>
> Can anyone tell me how I can link the Scan Button of CX3100 to a Linux
> application? I believe in the Windows environment, you can just press this
> button and the printer will scan the document and send it to your application
> of choice. But in Linux, this button seems to be useless because it does not
> do anything.
From jester@panix.com Mon Jan 26 18:35:29 2004
From: jester@panix.com (Jesse Sheidlower)
Date: Mon, 26 Jan 2004 13:35:29 -0500
Subject: [sane-devel] Canon LiDE 80 backend?
Message-ID: <20040126183528.GA6678@panix.com>
I see from the support list that the Canon LiDE 80 is not
currently supported. Is this something that's likely to
change in the very near future, or is no one working on it?
There didn't seem to be any discussion of this printer in
the archives of this list.
I like the LiDE series because of the supersmall size, but
I'd prefer the higher resolution of the LiDE 80 to the
currently supported LiDE 30. (The HP ScanJet 4600, also
small, seems also to be unsupported by SANE.)
Thanks. My main use of this would be on a Mac, but I'd
like to be able to use the scanner with a FreeBSD laptop
while travelling.
Jesse Sheidlower
From Oliver.Rauch@Rauch-Domain.DE Mon Jan 26 18:38:25 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: Mon, 26 Jan 2004 19:38:25 +0100
Subject: [sane-devel] (resend) how to undo saved working directory?
In-Reply-To: <200401260131.i0Q1VRWS017869@one.localnet>
References: <200401260131.i0Q1VRWS017869@one.localnet>
Message-ID: <200401261938.28565.Oliver.Rauch@Rauch-Domain.DE>
Hello Robert,
The problem is that different people like different behaviours.
I added the working directory options because a lot of people
asked for it. You are the first one who asked for the old behaviour
since I changed it so I think it is not of general interest.
I suggest you wirte a script or patch the sourcecoud yourself.
When I add options to change the behavior this makes the
program more complex and so I prefer to keep it as it is.
Best regards
Oliver
Am Montag, 26. Januar 2004 02:31 schrieb Robert M. Riches Jr.:
> > From: Oliver Rauch
> > Date: Sun, 25 Jan 2004 23:01:53 +0100
> >
> > You can change the working directory in the menu
> > preferences->change direcotry
> >
> > XSane always uses the working directory that is listed in the xsane.r=
c
> > file. When there is no xsane.rc file or there is no working directory
> > listed in the xsane.rc file then xsane uses the recent working direct=
ory.
> >
> > xsane always saves the selected working direcotry line to the xsane.r=
c
> > file when xsane exits.
>
> Thank you for pointing out the path to the working directory
> menu item. I had searched under preferences->setup->save
> and had missed the obvious at the bottom of the menu.
>
> So, let's say on Monday I'm working in directory A and use
> the menu item to have xsane put files there. Then, on
> Tuesday, I have an xterm in directory B and start up xsane
> from that xterm, so that the xsane process's cwd (current
> working directory) from the OS is B. Xsane will put the
> files in A, where I was on Monday (unless I go through the
> menu to tell xsane information it already has)? I would say
> that's undesirable behavior for any user other than ones
> whose world revolves around "My Documents". I, for one,
> liked the older (circa 0.84) behavior on this point.
>
> What is the potential for an RFE or patch submission for a
> command line option or environment variable to allow the
> user to control whether xsane uses the OS's cwd vs. the
> directory saved in the xsanerc file from the previous
> session? (I'm about 50% for minor enhancement patch
> submissions to other programs: one accept, one reject, one
> accept with modifications.)
>
> Or, should I just write a quick Perl wrapper script to
> modify the xsanerc file before invoking the real xsane?
>
> Thanks.
>
> Robert Riches
> rm.riches@verizon.net
--=20
http://www.xsane.org
http://www.rauch-domain.de
http://www.sane-project.org
From henning@meier-geinitz.de Mon Jan 26 18:51:53 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 26 Jan 2004 19:51:53 +0100
Subject: [sane-devel] HP 5500c scanner support?
In-Reply-To: <20040122002035.263116f0.stewart@midtoad.homelinux.org>
References: <20040122053613.31650.45428.Mailman@quantz.debian.org> <20040122002035.263116f0.stewart@midtoad.homelinux.org>
Message-ID: <20040126185153.GC2555@meier-geinitz.de>
Hi,
On Thu, Jan 22, 2004 at 12:20:35AM -0700, Stewart Midwinter wrote:
> Has anyone done any work on getting the HP 5500c scanner supported?
> I know it's not on the compatibility list, but...
I don't think that anyone is working on a driver for that device
currently.
> Seeing as how I have one, is there anything I could could do to help
> this along? run some tools? generate a log/debug file?
You could try to get log files with USB snoopy or sniffusb. However,
this only helps if you start to develop a driver yourself or if there
already is a driver for the chipset your scanner uses.
Writing a driver just by looking at the USB log file without having
access to such a scanner or at least a similar device is nearly
impossible. And even if it were possible, I guess nobody would have
the patience to do it.
So better start writing a driver yourself now :-)
Bye,
Henning
From henning@meier-geinitz.de Mon Jan 26 19:02:30 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 26 Jan 2004 20:02:30 +0100
Subject: [sane-devel] Canon LiDE 80 backend?
In-Reply-To: <20040126183528.GA6678@panix.com>
References: <20040126183528.GA6678@panix.com>
Message-ID: <20040126190230.GD2555@meier-geinitz.de>
Hi,
On Mon, Jan 26, 2004 at 01:35:29PM -0500, Jesse Sheidlower wrote:
> I see from the support list that the Canon LiDE 80 is not
> currently supported. Is this something that's likely to
> change in the very near future, or is no one working on it?
It may change in future. I'm (still) working on a backend for the
Genesys gl646 and gl841 chips but it's still not finished and I don't
have much time at the moment.
See http://www.meier-geinitz.de/sane/genesys-backend/
I wouldn't buy a scanner just because someone intends to write a
backend. Better buy an already supported device.
Could anyone who already owns such a scanner send me the output of
sane-find-scanner -v -v of SANE 1.0.13 or later?
Bye,
Henning
From rm.riches@verizon.net Mon Jan 26 20:52:40 2004
From: rm.riches@verizon.net (Robert M. Riches Jr.)
Date: Mon, 26 Jan 2004 12:52:40 -0800
Subject: [sane-devel] (resend) how to undo saved working directory?
Message-ID: <200401262052.i0QKqeIY006929@one.localnet>
> From: Oliver Rauch
> Date: Mon, 26 Jan 2004 19:38:25 +0100
>
> The problem is that different people like different behaviours.
> I added the working directory options because a lot of people
> asked for it. You are the first one who asked for the old behaviour
> since I changed it so I think it is not of general interest.
>
> I suggest you wirte a script or patch the sourcecoud yourself.
> When I add options to change the behavior this makes the
> program more complex and so I prefer to keep it as it is.
Nobody else wanted the saved files in the _real_ working
directory? That's curious.
How about a convention that if the working directory from
the xsane file is the null string the program would use the
OS's CWD? With luck, that should only take a couple lines
of code. Would you be willing to accept a patch that would
do that? If the patch would be accepted into the main code
stream, it would be worth doing. If just for my use, a Perl
wrapper would be more efficient.
Worst case, a Perl wrapper script should be pretty quick to
cobble. Would it be appropriate to post the script just in
case someone later searches out this thread and wants it?
Thanks for xsane.
Robert Riches
rm.riches@verizon.net
From martin@mkcollins.org Mon Jan 26 21:37:34 2004
From: martin@mkcollins.org (Martin Collins)
Date: Mon, 26 Jan 2004 21:37:34 +0000
Subject: [sane-devel] (resend) how to undo saved working directory?
In-Reply-To: <200401262052.i0QKqeIY006929@one.localnet>
References: <200401262052.i0QKqeIY006929@one.localnet>
Message-ID: <20040126213734.221eb911.martin@mkcollins.org>
On Mon, 26 Jan 2004 12:52:40 -0800
"Robert M. Riches Jr." wrote:
> Nobody else wanted the saved files in the _real_ working
> directory?
Sure they did, they just remembered to set it manually :-)
> How about a convention that if the working directory from
> the xsane file is the null string the program would use the
> OS's CWD?
It already does that doesn't it? The problem (from your point of view)
is that xsane writes the CWD into xsane.rc and uses it next time. How
about xsane leaving a null string null unless it is explicitly set?
Martin
From rm.riches@verizon.net Mon Jan 26 21:52:13 2004
From: rm.riches@verizon.net (Robert M. Riches Jr.)
Date: Mon, 26 Jan 2004 13:52:13 -0800
Subject: [sane-devel] (resend) how to undo saved working directory?
Message-ID: <200401262152.i0QLqDFB008864@one.localnet>
> From: Martin Collins
> Date: Mon, 26 Jan 2004 21:37:34 +0000
>
> On Mon, 26 Jan 2004 12:52:40 -0800
> "Robert M. Riches Jr." wrote:
>
> > Nobody else wanted the saved files in the _real_ working
> > directory?
>
> Sure they did, they just remembered to set it manually :-)
>
> > How about a convention that if the working directory from
> > the xsane file is the null string the program would use the
> > OS's CWD?
>
> It already does that doesn't it? The problem (from your point of view)
> is that xsane writes the CWD into xsane.rc and uses it next time. How
> about xsane leaving a null string null unless it is explicitly set?
Good point. I had forgotten about that side of the process.
That may take a few more lines of code, and a state variable
set when the xsane.rc file is read, used when the file is
written. If that might be acceptable for inclusion into the
main code stream, that would still be worth doing. Any
guidance on where the state variable should be declared?
(I haven't yet unpacked and looked at the source code.)
Thanks.
Robert Riches
rm.riches@verizon.net
From khk@khk.net Mon Jan 26 22:07:11 2004
From: khk@khk.net (Karl Heinz Kremer)
Date: Mon, 26 Jan 2004 17:07:11 -0500
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a linux application?
In-Reply-To: <401566B0.70109@gmx.net>
References: <401566B0.70109@gmx.net>
Message-ID:
I assume this is an EPSON CX-3100. In this case, the scanner does not
send anything when you press the button. The Windows software checks
every half second or second or so to find out if the button was
pressed.
The problem with handling buttons with Sane is that we don't have an
API for this, so every backend would potentially handle this
differently. Also, there is no official way to communicate a button
event to a frontend.
The EPSON backend has a mode where you can setup your scan, and then
configure it to wait for a button event. This would not allow you to
send the scans to another application, but it's a start :-)
On Jan 26, 2004, at 2:12 PM, Till Kamppeter wrote:
> I recommend that you post this on the SANE mailing list
> (http://www.sane-project.org/), as this is a scanning problem. I am
> CCing this posting to there.
>
> AFAIK noone has written a driver for scanner buttons yet (also not for
> other scanner models). The scanner probably sends a certain signal
> through the USB which is caught by a background process under Windows.
> This process then starts a program to do the scan. The best way to
> write a similar program under Linux is to use a USB sniffer to analyze
> how the signal looks like and then write a daemon which listens for
> such signals.
>
> Till
>
> Alton Hernandez wrote:
>> Hi,
>> Can anyone tell me how I can link the Scan Button of CX3100 to a Linux
>> application? I believe in the Windows environment, you can just
>> press this
>> button and the printer will scan the document and send it to your
>> application
>> of choice. But in Linux, this button seems to be useless because it
>> does not
>> do anything.
>
>
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request@lists.alioth.debian.org
From mattias.ellert@tsl.uu.se Mon Jan 26 22:42:26 2004
From: mattias.ellert@tsl.uu.se (Mattias Ellert)
Date: Mon, 26 Jan 2004 23:42:26 +0100
Subject: [sane-devel] MacOS X and pthread_cancel
Message-ID: <401597D2.7050305@tsl.uu.se>
Hi!
I have made a new binary package for MacOS X from a fresh CVS checkout
and with a new version of the pthread_cancel workaround patch. The new
version of the patch mimics the behaviour of the original code very
closely (but without calling pthred_cancel) and does not change the
stucture of the thread implementation as the previous patch did.
If you have experienced any thread related problems with SANE on MacOS X
the new version might help you. Some backends have also been updated to
use the sanei_thread routines instead of fork since the release, so this
package based on the CVS checkout should work better for scanners using
such backends.
The packages are available on http://www.ellert.se/twain-sane/ together
with a new version of the TWAIN SANE Interface.
Mattias
--
________________________________________________________________________
mattias.ellert@tsl.uu.se tel: +46 18 471 32 58
http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13
________________________________________________________________________
From martin@mkcollins.org Mon Jan 26 22:45:51 2004
From: martin@mkcollins.org (Martin Collins)
Date: Mon, 26 Jan 2004 22:45:51 +0000
Subject: [sane-devel] (resend) how to undo saved working directory?
In-Reply-To: <200401262152.i0QLqDFB008864@one.localnet>
References: <200401262152.i0QLqDFB008864@one.localnet>
Message-ID: <20040126224551.0ac4e71c.martin@mkcollins.org>
On Mon, 26 Jan 2004 13:52:13 -0800
"Robert M. Riches Jr." wrote:
> Any
> guidance on where the state variable should be declared?
Shouldn't be necessary. Just change the code in xsane.c that checks
preferences.working_directory to not set it if it is null.
Not tested, DYOR etc.
Martin
From olaf@epkowa.co.jp Tue Jan 27 05:32:10 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Tue, 27 Jan 2004 14:32:10 +0900
Subject: [sane-devel] iscan: "Could not send command to scanner"
In-Reply-To: <200401241315.47918.ojt@gexcon.com> (Ole Jacob Taraldset's
message of "Sat, 24 Jan 2004 13:15:47 +0100")
References: <200401241315.47918.ojt@gexcon.com>
Message-ID: <87n08a5545.fsf@zen.epkowa.co.jp>
Ole Jacob Taraldset writes:
> Hi,
Hi,
> I have an Epson Perfection 1650 Photo which I have been using with
> iscan. Now suddenly iscan doesn't work any more and just give me a
> dialog box saying "Could not send command to scanner". Xsane still
> works and recognizes my scanner without any problems.
>
> My system is a RedHat 9 box with freshrpms updates and the following:
> sane-backends-1.0.9-5.1
> sane-frontends-1.0.9-2
> xsane-0.89-3
> iscan-1.5.2-1.redhat.8.0
Hmm, that ought to work provided the libsane.so symlink points to the
right library. There is a known bug on RH9 where /usr/lib/libsane.so
points to the v4l SANE backend. Check if this is the case and fix it
if so.
To check:
$ ls -l /usr/lib/libsane.so
To fix (requires root permissions):
# ln -fs libsane.so.1.0.9 /usr/lib/libsane.so
> I've also tried iscan 1.4, but get the same result.
Never mind that version. It was very much not nice in that it quietly
overwrote the epson backend.
> My /etc/sane.d/epkowa.conf contains:
>
> usb /dev/usb/scanner0
That should be fine.
> My /etc/sane.d/epson.conf contains:
>
> usb /dev/usb/scanner0
For the record, iscan does not use the epson backend. It is *not* a
proper SANE frontend in that respect.
> I have tried to remove one or the other but this doesn't seem to help.
Hope this helps,
--
Olaf Meeuwissen EPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
From olaf@epkowa.co.jp Tue Jan 27 05:35:10 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Tue, 27 Jan 2004 14:35:10 +0900
Subject: [sane-devel] sane frontend questions
In-Reply-To: <20040124215651.GA8359@obiwan.csl.uiuc.edu> (Andy Mitofsky's
message of "Sat, 24 Jan 2004 15:56:51 -0600")
References: <20040113053607.GB10111@obiwan.csl.uiuc.edu>
<87wu7vqqa7.fsf@zen.epkowa.co.jp>
<20040124215651.GA8359@obiwan.csl.uiuc.edu>
Message-ID: <87isiy54z5.fsf@zen.epkowa.co.jp>
Andy Mitofsky writes:
> I just wanted to say thanks for the help from about a week ago,
> especially to Olaf Meeuwissen. I was able to get iscan to work on my computer.
> For the record, to get it to work, I installed an older version of gtk,
> gtk+-1.2.10, and used the suggested version of iscan, iscan-1.5.2-1.redhat.8.0.tar.gz. I
> At that point, I got compile errors relating to libgdk_imlib. I had the
> file /usr/lib/libgdk_imlib.so.1 on my machine but not gdk_imlib.h. To
> get around this, I deleted the lines including gdk_imlib.hfrom
> pisa_structs.h. and pisa_view_manager.cc. I also changed some lines of
> pisa_view_manager.cc from
> ::gdk_imlib_init ( );
> ::gtk_widget_push_visual ( ::gdk_imlib_get_visual ( ) );
> ::gtk_widget_push_colormap ( ::gdk_imlib_get_colormap ( ) );
> to
> ::gtk_widget_push_visual ( ::gdk_rgb_get_visual ( ) );
> ::gtk_widget_push_colormap ( ::gdk_rgb_get_cmap ( ) );
> I'm not sure what this did, but it seemed to work. Again, thanks
> for your help. Bye, Andy
Just so you know, you will not be able to use iscan as a GIMP plugin.
You could have installed the gimp-devel package and leave the sources
as they were instead.
# FYI, Debian users need gdk-imlib1-dev.
Hope this helps,
--
Olaf Meeuwissen EPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
From olaf@epkowa.co.jp Tue Jan 27 06:02:23 2004
From: olaf@epkowa.co.jp (Olaf Meeuwissen)
Date: Tue, 27 Jan 2004 15:02:23 +0900
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a
linux application?
In-Reply-To: (Karl Heinz
Kremer's message of "Mon, 26 Jan 2004 17:07:11 -0500")
References: <401566B0.70109@gmx.net>
Message-ID: <87ektm53ps.fsf@zen.epkowa.co.jp>
Karl Heinz Kremer writes:
> I assume this is an EPSON CX-3100. In this case, the scanner does not
> send anything when you press the button. The Windows software checks
> every half second or second or so to find out if the button was
> pressed.
With most of the more recent scanners and all-in-ones, including the
3200PHOTO and the CX-3100, pressing the scan button starts the EPSON
Smart Panel application under Windows.
Obviously, doing something like this under a Unix-like OS, or any true
multi-user OS for that matter, is just plain ... eh ... stupid because
there is absolutely no knowing for which user you need to fire up the
app. Let alone trying to figure at on which terminal.
Per user daemons polling for a button event to start an application
won't work either because there may be any number of such daemons
running (so you might as well use a single system-wide one).
If anyone thinks otherwise, I'd like to know.
The best one can probably do is what Karl has done in the epson
backend (and I merged into the epkowa backend with iscan-1.6.0) is
have the user set up the scan and tell the backend to wait until the
button is pressed before commencing the scan.
We are contemplating additional GUI bells and whistles for "Image
Scan! for Linux" for this functionality but haven't quite made up our
minds as to the most natural way of doing this. There's also the case
of the most desired behaviour when using the ADF ...
Needless to say, your suggestions are welcome ;-)
> The problem with handling buttons with Sane is that we don't have an
> API for this, so every backend would potentially handle this
> differently. Also, there is no official way to communicate a button
> event to a frontend.
>
> The EPSON backend has a mode where you can setup your scan, and then
> configure it to wait for a button event. This would not allow you to
> send the scans to another application, but it's a start :-)
>
>
> On Jan 26, 2004, at 2:12 PM, Till Kamppeter wrote:
>
>> I recommend that you post this on the SANE mailing list
>> (http://www.sane-project.org/), as this is a scanning problem. I am
>> CCing this posting to there.
>>
>> AFAIK noone has written a driver for scanner buttons yet (also not
>> for other scanner models). The scanner probably sends a certain
>> signal through the USB which is caught by a background process under
>> Windows. This process then starts a program to do the scan. The best
>> way to write a similar program under Linux is to use a USB sniffer
>> to analyze how the signal looks like and then write a daemon which
>> listens for such signals.
>>
>> Till
>>
>> Alton Hernandez wrote:
>>> Hi,
>>> Can anyone tell me how I can link the Scan Button of CX3100 to a Linux
>>> application? I believe in the Windows environment, you can just
>>> press this
>>> button and the printer will scan the document and send it to your
>>> application
>>> of choice. But in Linux, this button seems to be useless because
>>> it does not
>>> do anything.
--
Olaf Meeuwissen EPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
From ojt@gexcon.com Tue Jan 27 08:04:38 2004
From: ojt@gexcon.com (Ole Jacob Taraldset)
Date: Tue, 27 Jan 2004 09:04:38 +0100
Subject: [sane-devel] iscan: "Could not send command to scanner"
In-Reply-To: <87n08a5545.fsf@zen.epkowa.co.jp>
References: <200401241315.47918.ojt@gexcon.com> <87n08a5545.fsf@zen.epkowa.co.jp>
Message-ID: <200401270904.38164.ojt@gexcon.com>
This might have been an easier fix, but I got a hint in a previous post. I
downloaded an experimental sane-backends package and now iscan works just
fine.
-Ole Jacob
On Tuesday 27 January 2004 6:32 am, Olaf Meeuwissen wrote:
> Ole Jacob Taraldset writes:
> > Hi,
>
> Hi,
>
> > I have an Epson Perfection 1650 Photo which I have been using with
> > iscan. Now suddenly iscan doesn't work any more and just give me a
> > dialog box saying "Could not send command to scanner". Xsane still
> > works and recognizes my scanner without any problems.
> >
> > My system is a RedHat 9 box with freshrpms updates and the following:
> > sane-backends-1.0.9-5.1
> > sane-frontends-1.0.9-2
> > xsane-0.89-3
> > iscan-1.5.2-1.redhat.8.0
>
> Hmm, that ought to work provided the libsane.so symlink points to the
> right library. There is a known bug on RH9 where /usr/lib/libsane.so
> points to the v4l SANE backend. Check if this is the case and fix it
> if so.
>
> To check:
>
> $ ls -l /usr/lib/libsane.so
>
> To fix (requires root permissions):
>
> # ln -fs libsane.so.1.0.9 /usr/lib/libsane.so
>
> > I've also tried iscan 1.4, but get the same result.
>
> Never mind that version. It was very much not nice in that it quietly
> overwrote the epson backend.
>
> > My /etc/sane.d/epkowa.conf contains:
> >
> > usb /dev/usb/scanner0
>
> That should be fine.
>
> > My /etc/sane.d/epson.conf contains:
> >
> > usb /dev/usb/scanner0
>
> For the record, iscan does not use the epson backend. It is *not* a
> proper SANE frontend in that respect.
>
> > I have tried to remove one or the other but this doesn't seem to help.
>
> Hope this helps,
--
Process and Safetey, Dept. of Physics,
PGP key :
ICQ 5366306 | Jabber ojt@jabber.org | AIM ojtaraldset
Yahoo ojtaraldset | MSN ojt@gexcon.com
From anoah@pfeiffer.edu Tue Jan 27 16:10:35 2004
From: anoah@pfeiffer.edu (m. allan noah)
Date: Tue, 27 Jan 2004 11:10:35 -0500 (EST)
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a
linux application?
In-Reply-To: <87ektm53ps.fsf@zen.epkowa.co.jp>
Message-ID:
this also is an issue for any other scanners that have buttons, esp. the
adf models. unfortunately, i dont see a good way to handle multiple
scanners, since a frontend would have to load and unload multiple
backends many times per minute to monitor buttons...
what about a simple frontend that forks a separate child to load each
backend, and the child exit(1) if no scanners are found, or stays running
if there are. (might have to fork off child for each scanner not just
each backend)
then each child could monitor it's scanner by looking at the option
descriptor for each button (we would have to decide what to call them)
every couple seconds.
when a child decides a button is pressed, it would exec() to a program of
the user's choice.
problems with this idea include: what to do on a multi-user system, esp w/
regard to X windows, how do we decide which scanning frontend to run on
which button event for each scanner, and what to do about scanners with
lots of buttons and wheels and such.
allan
On Tue, 27 Jan 2004, Olaf Meeuwissen wrote:
> Karl Heinz Kremer writes:
>
> > I assume this is an EPSON CX-3100. In this case, the scanner does not
> > send anything when you press the button. The Windows software checks
> > every half second or second or so to find out if the button was
> > pressed.
>
> With most of the more recent scanners and all-in-ones, including the
> 3200PHOTO and the CX-3100, pressing the scan button starts the EPSON
> Smart Panel application under Windows.
>
> Obviously, doing something like this under a Unix-like OS, or any true
> multi-user OS for that matter, is just plain ... eh ... stupid because
> there is absolutely no knowing for which user you need to fire up the
> app. Let alone trying to figure at on which terminal.
>
> Per user daemons polling for a button event to start an application
> won't work either because there may be any number of such daemons
> running (so you might as well use a single system-wide one).
>
> If anyone thinks otherwise, I'd like to know.
>
> The best one can probably do is what Karl has done in the epson
> backend (and I merged into the epkowa backend with iscan-1.6.0) is
> have the user set up the scan and tell the backend to wait until the
> button is pressed before commencing the scan.
>
> We are contemplating additional GUI bells and whistles for "Image
> Scan! for Linux" for this functionality but haven't quite made up our
> minds as to the most natural way of doing this. There's also the case
> of the most desired behaviour when using the ADF ...
>
> Needless to say, your suggestions are welcome ;-)
>
> > The problem with handling buttons with Sane is that we don't have an
> > API for this, so every backend would potentially handle this
> > differently. Also, there is no official way to communicate a button
> > event to a frontend.
> >
> > The EPSON backend has a mode where you can setup your scan, and then
> > configure it to wait for a button event. This would not allow you to
> > send the scans to another application, but it's a start :-)
> >
> >
> > On Jan 26, 2004, at 2:12 PM, Till Kamppeter wrote:
> >
> >> I recommend that you post this on the SANE mailing list
> >> (http://www.sane-project.org/), as this is a scanning problem. I am
> >> CCing this posting to there.
> >>
> >> AFAIK noone has written a driver for scanner buttons yet (also not
> >> for other scanner models). The scanner probably sends a certain
> >> signal through the USB which is caught by a background process under
> >> Windows. This process then starts a program to do the scan. The best
> >> way to write a similar program under Linux is to use a USB sniffer
> >> to analyze how the signal looks like and then write a daemon which
> >> listens for such signals.
> >>
> >> Till
> >>
> >> Alton Hernandez wrote:
> >>> Hi,
> >>> Can anyone tell me how I can link the Scan Button of CX3100 to a Linux
> >>> application? I believe in the Windows environment, you can just
> >>> press this
> >>> button and the printer will scan the document and send it to your
> >>> application
> >>> of choice. But in Linux, this button seems to be useless because
> >>> it does not
> >>> do anything.
>
>
--
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
From bruce@brucebertrand.com Tue Jan 27 16:11:31 2004
From: bruce@brucebertrand.com (Bruce Bertrand)
Date: Tue, 27 Jan 2004 11:11:31 -0500
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a linux
application?
In-Reply-To: <401566B0.70109@gmx.net>
References: <401566B0.70109@gmx.net>
Message-ID: <40168DB3.7030604@brucebertrand.com>
Till Kamppeter wrote:
> I recommend that you post this on the SANE mailing list
> (http://www.sane-project.org/), as this is a scanning problem. I am
> CCing this posting to there.
>
> AFAIK noone has written a driver for scanner buttons yet (also not for
> other scanner models). The scanner probably sends a certain signal
> through the USB which is caught by a background process under Windows.
> This process then starts a program to do the scan. The best way to
> write a similar program under Linux is to use a USB sniffer to analyze
> how the signal looks like and then write a daemon which listens for
> such signals.
>
> Till
If this is the case, then it would only take one sniffer for all
scanners that operate in this manner. Sort of like those universal
"learning" remotes, where you hold up an existing remote to the learning
remote, hit a "listen" button and then press a button on the old one,
assigning whatever signal it receives to some function on the learning
remote.
Bruce
From anoah@pfeiffer.edu Tue Jan 27 16:27:19 2004
From: anoah@pfeiffer.edu (m. allan noah)
Date: Tue, 27 Jan 2004 11:27:19 -0500 (EST)
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a
linux application?
In-Reply-To: <40168DB3.7030604@brucebertrand.com>
Message-ID:
On Tue, 27 Jan 2004, Bruce Bertrand wrote:
> Till Kamppeter wrote:
>
> > I recommend that you post this on the SANE mailing list
> > (http://www.sane-project.org/), as this is a scanning problem. I am
> > CCing this posting to there.
> >
> > AFAIK noone has written a driver for scanner buttons yet (also not for
> > other scanner models). The scanner probably sends a certain signal
> > through the USB which is caught by a background process under Windows.
> > This process then starts a program to do the scan. The best way to
> > write a similar program under Linux is to use a USB sniffer to analyze
> > how the signal looks like and then write a daemon which listens for
> > such signals.
> >
> > Till
>
> If this is the case, then it would only take one sniffer for all
> scanners that operate in this manner. Sort of like those universal
> "learning" remotes, where you hold up an existing remote to the learning
> remote, hit a "listen" button and then press a button on the old one,
> assigning whatever signal it receives to some function on the learning
> remote.
> Bruce
not so simple as that. for machines with adf, you will usually have a
couple other sensors like paper thickness, input or output hopper
empty/full, cover open, lamp warm, etc. if the scanner sends all those as
a bitmask in one packet, then the user doing a button-press might show up
as a dozen different codes, based on those other flags. your 'generic'
button monitor would have to know a whole lot more about each individual
model than you would want (esp when things like which usb endpoint to use
and bulk v/s interrupt are taken into account)
all-in-all this sort of thing (reading the raw output from the scanner)
belongs in the backend, with suitable abstraction that a frontend could
use. finding that abstraction is more problematic...
allan
>
>
--
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
From brill@fs.math.uni-frankfurt.de Tue Jan 27 18:00:42 2004
From: brill@fs.math.uni-frankfurt.de (Bjoern Brill)
Date: Tue, 27 Jan 2004 19:00:42 +0100 (CET)
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a
linux application?
In-Reply-To: <87ektm53ps.fsf@zen.epkowa.co.jp>
References: <401566B0.70109@gmx.net>
<87ektm53ps.fsf@zen.epkowa.co.jp>
Message-ID:
[I've cut CCs to people who I know to be on sane-devel]
On Tue, 27 Jan 2004, Olaf Meeuwissen wrote:
> Karl Heinz Kremer writes:
>
> > I assume this is an EPSON CX-3100. In this case, the scanner does not
> > send anything when you press the button. The Windows software checks
> > every half second or second or so to find out if the button was
> > pressed.
>
> With most of the more recent scanners and all-in-ones, including the
> 3200PHOTO and the CX-3100, pressing the scan button starts the EPSON
> Smart Panel application under Windows.
>
> Obviously, doing something like this under a Unix-like OS, or any true
> multi-user OS for that matter, is just plain ... eh ... stupid because
> there is absolutely no knowing for which user you need to fire up the
> app. Let alone trying to figure at on which terminal.
>
Yes.
> Per user daemons polling for a button event to start an application
> won't work either because there may be any number of such daemons
> running (so you might as well use a single system-wide one).
>
AFAIR, the SANE 2 proposal contains a provision whereby a frontend would
have to obtain an exclusive lock on a scanner's buttons before polling
them (and a mechanism to steal the lock after a timeout so noone can block
the device forever by forgetting to close the frontend).
I didn't like the technical implementation in the proposal, but the
idea seems OK.
> If anyone thinks otherwise, I'd like to know.
>
I think it is OK to cover only a few common setups. Two which come to
mind:
1.) "home use": scanner is accessible only from the PC it's
attached to, and that PC has no more than one user logged in at any
given time (typically with an X session). In this case, a per user
daemon with session lifetime does the job even without locking.
2.) "large office": scanner is networked, accessible from many different
terminals. People have to walk several metres to the scanner, maybe
even into a different room. In this case, a simple remote control
feature like the one described below (set up scan parameters from
terminal, scan once for every scanner button press) would be extremely
useful.
With increasing distance from terminal to scanner, more complex
remote control functionality becomes convenient, e.g. walk up to the
scanner with a bunch of documents and route them to different
applications right from the scanner. Given the scanner has enough
buttons of course :)
Here, locking is a Good Thing, but it may suffice to implement
it inside saned.
> The best one can probably do is what Karl has done in the epson
> backend (and I merged into the epkowa backend with iscan-1.6.0) is
> have the user set up the scan and tell the backend to wait until the
> button is pressed before commencing the scan.
>
> We are contemplating additional GUI bells and whistles for "Image
> Scan! for Linux" for this functionality but haven't quite made up our
> minds as to the most natural way of doing this. There's also the case
> of the most desired behaviour when using the ADF ...
>
> Needless to say, your suggestions are welcome ;-)
>
> > The problem with handling buttons with Sane is that we don't have an
> > API for this, so every backend would potentially handle this
> > differently. Also, there is no official way to communicate a button
> > event to a frontend.
> >
> > The EPSON backend has a mode where you can setup your scan, and then
> > configure it to wait for a button event. This would not allow you to
> > send the scans to another application, but it's a start :-)
> >
> >
> > On Jan 26, 2004, at 2:12 PM, Till Kamppeter wrote:
> >
> >> I recommend that you post this on the SANE mailing list
> >> (http://www.sane-project.org/), as this is a scanning problem. I am
> >> CCing this posting to there.
> >>
> >> AFAIK noone has written a driver for scanner buttons yet (also not
> >> for other scanner models). The scanner probably sends a certain
> >> signal through the USB which is caught by a background process under
> >> Windows. This process then starts a program to do the scan. The best
> >> way to write a similar program under Linux is to use a USB sniffer
> >> to analyze how the signal looks like and then write a daemon which
> >> listens for such signals.
> >>
> >> Till
> >>
> >> Alton Hernandez wrote:
> >>> Hi,
> >>> Can anyone tell me how I can link the Scan Button of CX3100 to a Linux
> >>> application? I believe in the Windows environment, you can just
> >>> press this
> >>> button and the printer will scan the document and send it to your
> >>> application
> >>> of choice. But in Linux, this button seems to be useless because
> >>> it does not
> >>> do anything.
>
Best regards,
Bjoern Brill
--
Bj"orn Brill
Frankfurt am Main, Germany
From christopherlmarshall@yahoo.com Tue Jan 27 20:21:11 2004
From: christopherlmarshall@yahoo.com (Christopher Marshall)
Date: Tue, 27 Jan 2004 12:21:11 -0800 (PST)
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a linux application?
In-Reply-To:
Message-ID: <20040127202111.74633.qmail@web41508.mail.yahoo.com>
>
> not so simple as that. for machines with adf, you will usually have a
> couple other sensors like paper thickness, input or output hopper
> empty/full, cover open, lamp warm, etc. if the scanner sends all those as
> a bitmask in one packet, then the user doing a button-press might show up
> as a dozen different codes, based on those other flags. your 'generic'
> button monitor would have to know a whole lot more about each individual
> model than you would want (esp when things like which usb endpoint to use
> and bulk v/s interrupt are taken into account)
>
> all-in-all this sort of thing (reading the raw output from the scanner)
> belongs in the backend, with suitable abstraction that a frontend could
> use. finding that abstraction is more problematic...
>
> allan
>
How about adding a front-end switch that instead of requesting a scan, requests the backend to sit
and listen for button events and write them out to stdout? The format of the message written
could vary by backend.
For example, the command
scanimage -d plustek:libusb:001:004 -report-button
would wait for the next button press. Pressing a button would cause the command to exit and write
a text description of the button pressed to stdout.
This would allow the user to write bash scripts to respond to the button presses. This style of
interaction is close to how xmessage works when invoked with -print.
button=$(scanimage -d plustek:libusb:001:004 -report-buttons)
if [ "$button" == "copy" ] ; then
# scan and print
scanimage -d plustek:libusb:001:004 > image.pnm
pnmtops iamge.pnm > image.ps
lpr print.ps
elif ...
else
echo "unrecognized button"
exit 1
fi
This scheme might not solve all problems but it would be a big step up from no support at all.
Chris Marshall
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
From anoah@pfeiffer.edu Tue Jan 27 21:01:48 2004
From: anoah@pfeiffer.edu (m. allan noah)
Date: Tue, 27 Jan 2004 16:01:48 -0500 (EST)
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a
linux application?
In-Reply-To: <20040127202111.74633.qmail@web41508.mail.yahoo.com>
Message-ID:
On Tue, 27 Jan 2004, Christopher Marshall wrote:
> >
> > not so simple as that. for machines with adf, you will usually have a
> > couple other sensors like paper thickness, input or output hopper
> > empty/full, cover open, lamp warm, etc. if the scanner sends all those as
> > a bitmask in one packet, then the user doing a button-press might show up
> > as a dozen different codes, based on those other flags. your 'generic'
> > button monitor would have to know a whole lot more about each individual
> > model than you would want (esp when things like which usb endpoint to use
> > and bulk v/s interrupt are taken into account)
> >
> > all-in-all this sort of thing (reading the raw output from the scanner)
> > belongs in the backend, with suitable abstraction that a frontend could
> > use. finding that abstraction is more problematic...
> >
> > allan
> >
>
> How about adding a front-end switch that instead of requesting a scan, requests the backend to sit
> and listen for button events and write them out to stdout? The format of the message written
> could vary by backend.
>
> For example, the command
>
> scanimage -d plustek:libusb:001:004 -report-button
>
> would wait for the next button press. Pressing a button would cause the command to exit and write
> a text description of the button pressed to stdout.
>
> This would allow the user to write bash scripts to respond to the button presses. This style of
> interaction is close to how xmessage works when invoked with -print.
>
> button=$(scanimage -d plustek:libusb:001:004 -report-buttons)
> if [ "$button" == "copy" ] ; then
> # scan and print
> scanimage -d plustek:libusb:001:004 > image.pnm
> pnmtops iamge.pnm > image.ps
> lpr print.ps
> elif ...
> else
> echo "unrecognized button"
> exit 1
> fi
>
> This scheme might not solve all problems but it would be a big step up from no support at all.
you could have a flag to a front-end that told it to load the backend, but
instead of scan, constantly check the option descriptor for a button's
status. the front-end could print this, or even take a series of command
line switches that tell it what to do in case of a particular event. but
in all cases, this front-end would have to disconnect from the scanner, so
that the second front-end could load the backend and connect. but, it
would have to still run, so that it could re-connect and continue
monitoring. unless, you wanted to re-start it from your script.
but you definately dont want backends printing.
allan
>
> Chris Marshall
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool. Try it!
> http://webhosting.yahoo.com/ps/sb/
>
>
--
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
From christopherlmarshall@yahoo.com Tue Jan 27 22:50:20 2004
From: christopherlmarshall@yahoo.com (Christopher Marshall)
Date: Tue, 27 Jan 2004 14:50:20 -0800 (PST)
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a linux application?
In-Reply-To:
Message-ID: <20040127225020.24544.qmail@web41502.mail.yahoo.com>
> you could have a flag to a front-end that told it to load the backend, but
> instead of scan, constantly check the option descriptor for a button's
> status. the front-end could print this, or even take a series of command
> line switches that tell it what to do in case of a particular event. but
> in all cases, this front-end would have to disconnect from the scanner, so
> that the second front-end could load the backend and connect. but, it
> would have to still run, so that it could re-connect and continue
> monitoring. unless, you wanted to re-start it from your script.
>
> but you definately dont want backends printing.
>
> allan
>
Is there a problem with restarting it from a script? That seems a natural way to me to separate
mechanism from policy and I can imagine a lot of nice uses of what I described.
I had assumed that when you pushed a button on a usb scanner, it send a message over the usb that
the backend, if it was listening, would get. The way you describe it, the scanner sets a flag
internally, meaning something like "button 1 pushed", and the flag stays in that state until the
backend asks for its button status, then tells it to reset the status back to "button 1 unpushed".
Is that correct?
Assuming I've got it, then I think what you described is the way to go. Have the front-end
disconnect and exit, printing out a message as to which button was pressed. The script could then
invoke scanimage again to scan an image and print the result (if the script author wants to
interpret the pressed button that way).
You seem to be worried about what would happen if the user pressed a button twice, and the second
button press was missed because the controlling script had exited the first front-end invocation
and began another to scan. I take it the second button press would be either be dropped, or you
wouldn't be able to process it until after the first scan finished, which would mean you couldn't
use one of the buttons as a "cancel" button to cancel the scan in progress.
If not being able to implement a cancel button bothers you, then how about this? Have another
front-end flag that lets you name a file you want button events written to that occur during a
scan. Then you could implement the cancel button by specifying a fifo for the file argument, and
having a background process read lines from the file, interpret them, and kill the scan in
progress in the event of a cancel button push. That's very straight forward in bash.
Even without the ability to implement a cancel button, I would love to be able to map scanner
buttons to mean things like "scan low res, gray, and write to a spool directory", "scan high res,
color, to a spool directory" and "print the next scan". That's assuming I have 3 buttons to work
with, of course. So if I want to do a low res scan and have it printed, I hit button 3, wait a
second, then hit button 1. If I didn't want it printed, I'd just his button 1 or 2.
Hmmm. Would it be possible to push-and-hold button 1, then push-and-release button2, and then
release button 1, and have the backend tell the difference from push-and-release 1 followed by
push-and-release 2?
What exactly generates an event (usb message sent device-to-host) in the case of button presses
and releases? Does anyone know?
Chris Marshall
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
From david_b_brown@mac.com Wed Jan 28 11:31:14 2004
From: david_b_brown@mac.com (David B Brown)
Date: Wed, 28 Jan 2004 11:31:14 +0000
Subject: [sane-devel] SANE - Mac OS X 10.3.2 and Microtek Scanmaker
Message-ID: <7B669FF7-5185-11D8-98EA-000A278D424C@mac.com>
--Apple-Mail-13-345510911
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Hi,
I tried out SANE a couple of months back just after Mac OS X SCSI
support was added. At the time it didn't work and I posted a few notes
and worked off line with Guy Brooker but we didn't fix the issues.
Now I saw that Mattias Ellert was offering per-compiled Mac OS X
packages, built form CVS as off 25-01-2004 so I though I'd give it
another go. Unfortunately it still doesn't appear to work. The good
news from my point of view is that unlike before I don't have to
re-boot between tests.
Here's the latest trace :-
[microtek] .wait_ready 0...
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Trasferred 0 bytes
[microtek] .start_scan...
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Trasferred 0 bytes
[microtek] .get_scan_status 0...
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:6 isWrite:0
[sanei_scsi] isRead dst_size:6
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Trasferred 0 bytes
[microtek] get_scan_status(0): 0, 0, 0 -> #0
[microtek] > 0 0 0 0 0 0
[microtek] sane_start: SCSI buffer smaller that one scan line!
[microtek] end_scan...
[microtek] .stop_scan...
[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:0 isWrite:1
[sanei_scsi] isWrite src_size:0
[sanei_scsi] Executing command
[sanei_scsi] ExecuteTaskSync OK Trasferred 0 bytes
scanimage: sane_start: Out of memory
[microtek] sane_cancel...
[microtek] end_scan...
[microtek] sane_close...
[microtek] sane_exit...
[microtek] sane_exit: MICROTEK says goodbye.
[MacCoylton:~] dave%
Cheers
David
--Apple-Mail-13-345510911
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
name=smime.p7s
Content-Disposition: attachment;
filename=smime.p7s
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGHjCCAtcw
ggJAoAMCAQICAwtFyDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDMxMjA1MDkzODM3WhcNMDQxMjA0MDkzODM3WjBHMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSQwIgYJKoZIhvcNAQkBFhVkYXZpZF9iX2Jyb3duQG1h
Yy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC0b6rHkfXZ63RUPvNy+ubvwc8w
s8Aj8qqHP/g/47aQWHGozv2dUNDWk7GsprJUh6bVMZq6k5TaXkAbbjR0vcyd9rD5nP3XOK2YNVjE
xIjDq1jr2RLpE1ue/s956sv+bLlv37uWfD3XfGqIEqcS/vo93dWmNP0pzaSIwDfrMhkDoL56x/hJ
ObBD639ANrOtp8Yiv3sDLQsQDNZimlo8g/6cZL3oveYg9kbsh2kRxUVrXY+/fH2NS6mQRMigM0qa
YJ7yj55qpq37+O7JLPunCioQZAxftSwYhY+etPiG9AQIKdWhd8/RyOlGJQ+dT0/SJk3DuMuScjIG
+7Rrye5y2wVxAgMBAAGjMjAwMCAGA1UdEQQZMBeBFWRhdmlkX2JfYnJvd25AbWFjLmNvbTAMBgNV
HRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAGDb+a4KUHFcqJNzwtwGUiNcyitED7lgyEBm0uzs
NKEme28RpAav6Mov6LE90/08OrFo5+5Bd/YVpkd5qV97ztMRpZ2wl0iytfZ7mHOvWZKXFWlrLkcf
wfKPPOfkImg6IZ3QR0yK26smzH+gugKkhUMzwGOZP8VWMzEZkoaFu/1rMIIDPzCCAqigAwIBAgIB
DTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES
MBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMf
Q2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFs
IEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29t
MB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT
HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK
mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbL
rzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZ
cmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0
cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQD
AgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0B
AQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3h
YWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1
TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAucwggLjAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLRcgwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcNAQkDMQsG
CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDQwMTI4MTEzMTE1WjAjBgkqhkiG9w0BCQQxFgQU
8LYpz5fhhVq5Yak5CZeV69Cm1TkweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwtFyDB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1Ro
YXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLRcgwDQYJKoZIhvcNAQEBBQAEggEA
n3a94qc+TiAETV2wu+TrErjn42nrGscIKQpdjEwItvfeaIVbCyZTi9XtpfVT3C4rzEuDxSbLkD02
/6Jgp8oRkdr5DzNZwSSP4+4bA1uHSczgDoMBJv0//fczv/Nf0pd0yAcdr13VqdE+wqUfqpDEBVnf
PsdnxCrS2qdZ5JdrcJQB14E/rwwhSzXckE76Y6M+TNxSbhNWFM2yH5J8TtCOo+PPLvipP8zAEyAV
oyYSPLION+Qu2sl3ZPG4wtlGq8lD1+fSGm6WbQCJz3bvlsqyJaQkJLcrjEjWS1jjOhI03ZteLPgd
38CMTjDUYTzXIWMuAu9OFewnDuiZsgPJAxzp6QAAAAAAAA==
--Apple-Mail-13-345510911--
From anoah@pfeiffer.edu Wed Jan 28 14:30:51 2004
From: anoah@pfeiffer.edu (m. allan noah)
Date: Wed, 28 Jan 2004 09:30:51 -0500 (EST)
Subject: [sane-devel] Re: How to link the Scan Button of CX3100 to a
linux application?
In-Reply-To: <20040127225020.24544.qmail@web41502.mail.yahoo.com>
Message-ID:
On Tue, 27 Jan 2004, Christopher Marshall wrote:
> > you could have a flag to a front-end that told it to load the backend, but
> > instead of scan, constantly check the option descriptor for a button's
> > status. the front-end could print this, or even take a series of command
> > line switches that tell it what to do in case of a particular event. but
> > in all cases, this front-end would have to disconnect from the scanner, so
> > that the second front-end could load the backend and connect. but, it
> > would have to still run, so that it could re-connect and continue
> > monitoring. unless, you wanted to re-start it from your script.
> >
> > but you definately dont want backends printing.
> >
> > allan
> >
>
> Is there a problem with restarting it from a script? That seems a natural way to me to separate
> mechanism from policy and I can imagine a lot of nice uses of what I described.
perhaps it would be ok. cant see all the implications at this second...
>
> I had assumed that when you pushed a button on a usb scanner, it send a message over the usb that
> the backend, if it was listening, would get.
to be technically accurate, all usb communications start at the host. that
said, it is possible if the device supports it, to sometimes setup an
interrupt pipe between the host and the device to 'automatically' request
data from the device at certain time intervals. some scanners work this
way. many do not.
The way you describe it, the scanner sets a flag
> internally, meaning something like "button 1 pushed", and the flag stays in that state until the
> backend asks for its button status, then tells it to reset the status back to "button 1 unpushed".
> Is that correct?
yes, it seems that many more scanners, especially ones that use an
existing parallel or scsi model with usb grafted onto them, just store a
bitmask of sensor statuses (stati?) until a timer runs out (3 secs on
fujitsu) or until the backend requests the current status.
>
> Assuming I've got it, then I think what you described is the way to go. Have the front-end
> disconnect and exit, printing out a message as to which button was pressed. The script could then
> invoke scanimage again to scan an image and print the result (if the script author wants to
> interpret the pressed button that way).
that would work for trivial cases, and only for certain events.
for more complex situations: ie: the
stock fujitsu windows software will read the status of the hopper paper
sensor, and begin scanning the papers without any button press. if you
want to emulate this, then your 'scanmonitor' frontend would have to
report that event and exit. but, if your wrapper script does not care
about paper insertion, then it will never get the button press, cause
scanmonitor has already exited. so your wrapper would have to handle this
by restarting the scanmonitor on any unknown events. which is fine, except
that re-loading the backend again can be time consuming and can clear the
status of any buttons, meaning that the button pressed right after the
paper was inserted, gets lost.
>
> You seem to be worried about what would happen if the user pressed a button twice, and the second
> button press was missed because the controlling script had exited the first front-end invocation
> and began another to scan. I take it the second button press would be either be dropped, or you
> wouldn't be able to process it until after the first scan finished, which would mean you couldn't
> use one of the buttons as a "cancel" button to cancel the scan in progress.
>
among other things, this is a concern, yes.
> If not being able to implement a cancel button bothers you, then how about this? Have another
> front-end flag that lets you name a file you want button events written to that occur during a
> scan. Then you could implement the cancel button by specifying a fifo for the file argument, and
> having a background process read lines from the file, interpret them, and kill the scan in
> progress in the event of a cancel button push. That's very straight forward in bash.
ok, lets talk about that idea. any backend that has button support could
open a fifo and print 'events' to that as they happen. so all you need is
either a flag to the frontend to constantly call a function in the backend
that will do this, or a flag to the backend that causes it to while(1) in
one of the early sane_* functions.
now you still need some way for your bash wrapper to signal the
frontend/backend to stop watching the device so that you can fire-up a
specific program. that would be alot easier if bash wrapper was not
involved, and instead your monitor front-end was smart enough to read a
config file of programs to run, and it could perhaps 'control' the backend
a bit better.
and, even better than that, the frontend could perhaps handle some of the
events internally, so it would not have to disconnect the backend, just to
have another front-end re-load it.
>
> Even without the ability to implement a cancel button, I would love to be able to map scanner
> buttons to mean things like "scan low res, gray, and write to a spool directory", "scan high res,
> color, to a spool directory" and "print the next scan". That's assuming I have 3 buttons to work
> with, of course. So if I want to do a low res scan and have it printed, I hit button 3, wait a
> second, then hit button 1. If I didn't want it printed, I'd just his button 1 or 2.
that last one is tough to do via this whole bash script thing, unless you
have the backend buffer the button presses for a couple seconds to see if
anymore happen (like 3 button mouse emulation). much easier to get a
scanner with more inputs. fujitsu has a user-setable seven-element led
char and two scan buttons, making for 20 possible combinations.
>
> Hmmm. Would it be possible to push-and-hold button 1, then push-and-release button2, and then
> release button 1, and have the backend tell the difference from push-and-release 1 followed by
> push-and-release 2?
depends entirely on the scanner.
>
> What exactly generates an event (usb message sent device-to-host) in the case of button presses
> and releases? Does anyone know?
>
depends entirely on the scanner, hell even on different firmware revsion
of the same scanner it can change. hence why this needs to be handled in
the backend.
> Chris Marshall
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool. Try it!
> http://webhosting.yahoo.com/ps/sb/
>
--
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
From christian.poetsch@schott.com Wed Jan 28 14:35:46 2004
From: christian.poetsch@schott.com (Poetsch, Christian)
Date: Wed, 28 Jan 2004 15:35:46 +0100
Subject: [sane-devel] HiRes scanning with external lamp
Message-ID:
hello,
For a special application I wanted to use a Epson 2400 Perfection Scanner
with a external lamp. Therefore I need to turn off the internal lamp.
Karl Heinz Kremer kindly answered that there is no possibility to do this
with software in modern scanners. For my application I need a resolution of
at least 1.200dpi, preferebly 2.400dpi . Is there anyone, who have
experience in things like that? Is there a scanner that is more matching
for my purposes? Some ideas?
Thanks
From henning@meier-geinitz.de Wed Jan 28 17:50:45 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Wed, 28 Jan 2004 18:50:45 +0100
Subject: [sane-devel] HiRes scanning with external lamp
In-Reply-To:
References:
Message-ID: <20040128175045.GC3551@meier-geinitz.de>
Hi,
On Wed, Jan 28, 2004 at 03:35:46PM +0100, Poetsch, Christian wrote:
> For a special application I wanted to use a Epson 2400 Perfection Scanner
> with a external lamp. Therefore I need to turn off the internal lamp.
> Karl Heinz Kremer kindly answered that there is no possibility to do this
> with software in modern scanners.
Actually that's not a problem of "modern" or old. It depends on the
level of intelligence of the scanner. The intelligent (and usually
more expensive) scanners use their own firmware and get commands like
"scan image with resolution foo". Most cheaper scanners need lower
level commands like "move scan slider 300 motor steps". In the latter
case, turning off the lamp is usually no problem. Example: Scanners
using the GT6801 and GT6816 chips.
Also any scanners using external lamps for scanning
films/negatives/transparencies may be used for your perpose. Maybe
it's necessary to cheat the scanner into thinking that an external
transparency adapter is connected.
Bye,
Henning
From svoltz@wanadoo.fr Thu Jan 29 01:10:37 2004
From: svoltz@wanadoo.fr (svoltz@wanadoo.fr)
Date: Wed, 28 Jan 2004 20:10:37 -0500
Subject: [sane-devel] HiRes scanning with external lamp
In-Reply-To:
References:
Message-ID: <20040129011037.GA1922@wanadoo.fr>
On Wed, Jan 28, 2004 at 03:35:46PM +0100, Poetsch, Christian wrote:
> hello,
> For a special application I wanted to use a Epson 2400 Perfection Scanner
> with a external lamp. Therefore I need to turn off the internal lamp.
> Karl Heinz Kremer kindly answered that there is no possibility to do this
> with software in modern scanners. For my application I need a resolution of
> at least 1.200dpi, preferebly 2.400dpi . Is there anyone, who have
> experience in things like that? Is there a scanner that is more matching
> for my purposes? Some ideas?
>
> Thanks
>
>
The Umax astra 1220P can do such a thing. Unfortunatly, it is
only able to scan at 600x1200 dpi max.
Regards,
Stef
From karsten.festag@gmx.de Thu Jan 29 20:42:20 2004
From: karsten.festag@gmx.de (Karsten Festag)
Date: Thu, 29 Jan 2004 21:42:20 +0100
Subject: [sane-devel] Re: Micortek SANE USB Config
In-Reply-To:
References:
Message-ID: <200401292142.20849.karsten.festag@gmx.de>
Hi Race,
i'm afraid you will not be able to use the USB interface with this scanner and
SANE under OSX. The microtek2 backend was written for SCSI scanners and the
way some of the Microtek USB scanners work under Linux is a special kernel
module called 'microtek.o' which makes the USB scanner appear as a SCSI
device. I don't know if there is a similar possibility in OSX and I don't
have the possibilitiy to include libusb support to the microtek2 backend
because I don't have an USB scanner available and I have not enough leisure
time left for such kind of project. But maybe someone else would like to do
this?
Best regards
Karsten
On Tuesday 27 January 2004 23:58, you wrote:
> I have installed all the appropriate software to utilize your SANE Microtek
> backend with my Scanmaker V6USL but I am having a hell of a time
> configuring it to work at all. I want to use the USB interface.
>
> I am on on OSX X.3.2 and have installed
> TWAIN-SANE-Interface.pkg v0.4
> sane-backends.pkg 1.0.13-cvs 2004-01-25
> libusb.pkg 0.1.8 beta 2004-01-25
>
>
>
> When Running sane-find-scanner I receive:
>
>
> Race:~ race$ sane-find-scanner
>
> # No SCSI scanners found. If you expected something different, make sure
> that
> # you have loaded a SCSI driver for your SCSI adapter.
>
> found USB scanner (vendor=0x05da, product=0x00a3) at
> libusb:002:002-05da-00a3-ff-03
> # Your USB scanner was (probably) detected. It may or may not be
> supported by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> # Scanners connected to the parallel port or other proprietary ports
> can't be
> # detected by this program.
>
> # You may want to run this program as root to find all devices. Once you
> # found the scanner devices, be sure to adjust access permissions as
> # necessary.
> Race:~ race$
>
>
>
> The Config. File microtek2.config is set to:
>
> # See sane-microtek2(5) for a description of the options
>
> option dump 1
> option strip-height 14.0
> option no-backtrack-option on
> option lightlid-35 on
> option toggle-lamp on
> option lineart-autoadjust on
> option backend-calibration on
> #option colorbalance-adjust on
> scsi * * Scanner
>
>
>
>
>
>
> Can you please advise.
>
>
>
>
>
> Race
From Oliver.Rauch@Rauch-Domain.DE Thu Jan 29 21:20:18 2004
From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch)
Date: Thu, 29 Jan 2004 22:20:18 +0100
Subject: [sane-devel] sane-umax backend works on Mac OS-X
Message-ID: <200401292220.19457.Oliver.Rauch@Rauch-Domain.DE>
Hello.
I just got the feedback that the sane-umax patch for Mac OS-X
that is in the sane-cvs since 2004-01-12 does work. The user was
able to do a scan with scanimage.
He also sent a link to a sane-backends binary that includes the
sane-umax patch:
=09http://www.ellert.se/twain-sane/
If someone knows a link to a xsane binary for Mac OS-X
please post it here!
Oliver
--=20
http://www.xsane.org
http://www.rauch-domain.de
http://www.sane-project.org
From mattias.ellert@tsl.uu.se Fri Jan 30 10:03:14 2004
From: mattias.ellert@tsl.uu.se (Mattias Ellert)
Date: Fri, 30 Jan 2004 11:03:14 +0100
Subject: [sane-devel] sane-umax backend works on Mac OS-X
In-Reply-To: <200401292220.19457.Oliver.Rauch@Rauch-Domain.DE>
References: <200401292220.19457.Oliver.Rauch@Rauch-Domain.DE>
Message-ID: <401A2BE2.9080305@tsl.uu.se>
Oliver Rauch wrote:
> Hello.
>
> I just got the feedback that the sane-umax patch for Mac OS-X
> that is in the sane-cvs since 2004-01-12 does work. The user was
> able to do a scan with scanimage.
>
> He also sent a link to a sane-backends binary that includes the
> sane-umax patch:
>
> http://www.ellert.se/twain-sane/
Please note that these binaries were compiled with the (new version of)
the pthread_cancel workaround patch attached to the bug report at:
https://alioth.debian.org/tracker/index.php?func=detail&aid=300434&group_id=1308&atid=410366
The status of the bug report is "Pending", so hopefully the patch should
go into CVS soon.
Mattias Ellert
From gerhard@gjaeger.de Fri Jan 30 15:52:51 2004
From: gerhard@gjaeger.de (Gerhard Jaeger)
Date: Fri, 30 Jan 2004 16:52:51 +0100
Subject: [sane-devel] sane-umax backend works on Mac OS-X
In-Reply-To: <401A2BE2.9080305@tsl.uu.se>
References: <200401292220.19457.Oliver.Rauch@Rauch-Domain.DE> <401A2BE2.9080305@tsl.uu.se>
Message-ID: <200401301652.51918.gerhard@gjaeger.de>
Hi,
On Friday 30 January 2004 11:03, Mattias Ellert wrote:
[SNIPSNAP]
> https://alioth.debian.org/tracker/index.php?func=detail&aid=300434&group_id
>=1308&atid=410366
>
> The status of the bug report is "Pending", so hopefully the patch should
> go into CVS soon.
It will... please be patient, probably this weekend...
Ciao,
Gerhard
From henning@meier-geinitz.de Fri Jan 30 17:13:09 2004
From: henning@meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 30 Jan 2004 18:13:09 +0100
Subject: [sane-devel] Unsupported: Mustek BearPaw 4800TA Pro II
In-Reply-To:
References:
Message-ID: <20040130171309.GD5384@meier-geinitz.de>
Hi,
On Thu, Jan 22, 2004 at 07:46:59PM +0100, joerg.pr@olivfabric.de wrote:
> I've just encountered the following unsupported scanner:
> MUSTEK Be@rPaw 4800TA Pro II
Thanks for your information. I've added that to our lists:
I don't know which chipset that is.
http://www.sane-project.org/unsupported/mustek-bearpaw-4800ta-pro-ii.html
Bye,
Henning
From legendary_fox@aliceposta.it Sat Jan 31 09:38:48 2004
From: legendary_fox@aliceposta.it (Dario Berzano)
Date: Sat, 31 Jan 2004 10:38:48 +0100
Subject: [sane-devel] Mustek 1200CP scanner does not release parallel port
Message-ID: <401B77A8.8060807@aliceposta.it>
Hi,
I own a Mustek 1200CP flatbed scanner connected via a parallel port.=20
After scanning, it seems that the SANE backend mustek_pp hangs and waits=20
for some data from the scanner, locking the parallel port. As a result,=20
the scanning head's lamp stays turned on and it does not return to its=20
home position. The only way to unlock the port is to kill the scanning=20
program (e.g. scanimage or xsane). I do not use saned.
Another strange aspect is that I had to set up the cis600 driver=20
instead of the proper cis1200 one. With cis1200 (or cis1200+), the=20
scanned image is vertically stretched, and the scanning head tries to=20
scan out of range, making a loud, awful noise and damaging my hardware.
Any ideas? Thanks in advance.
--=20
dario berzano :: la volpe leggendaria :: http://flemma.knows.it/
=20
,-,
_.-=3D;~ /_
_-~ ' ;.
_.-~ ' .-~-~`-._
.--~~:. --.____88
__....-~~' .' . . _..-----~~
_..--~~~~' .' .' ,'
_.-~ . . ` ,'
.' :. ./
.: ,/ ` ::. ,'
.:' ,( ;. ::. ,-'
.' ./'.`. . . /::._... _/:.o/
/ ./'. . .) . _.,' `88;?88|
,' . .,/'._,-~ /_.o8P' 88P ?8b
_,'' . .,/',-~ d888P' 88' 88|
_.'~ . .,:oP' ?88b _..--- 88.--'8b.--..__
: ...' 88o __,------.88o _.=3D~- . `~~ `~~ ~-._
`.;;;:=3D' ~~ ~~~ ~- - - -
=20
=BB proud and happy linux user =AB
From charlie@cgrosvenor.co.uk Sat Jan 31 13:38:35 2004
From: charlie@cgrosvenor.co.uk (Charlie Grosvenor)
Date: Sat, 31 Jan 2004 13:38:35 -0000
Subject: [sane-devel] scanmagic 1200 CU Plus reset device
Message-ID:
I have a scanmagic 1200 CU Plus, I have this set up for use with sane.
Sometimes when it fails to scan, the scanner head get left not in its rest
place. When this occurs I have to unplug the scanner from the Linux machine,
plug it into a windows machine and scan something, to get it to reset. Is
there any way to get sane to reset the scanner?
Thank you
Charlie
From jochen@penguin-breeder.org Sat Jan 31 17:26:51 2004
From: jochen@penguin-breeder.org (Jochen Eisinger)
Date: Sat, 31 Jan 2004 18:26:51 +0100
Subject: [sane-devel] Mustek 1200CP scanner does not release parallel
port
In-Reply-To: <401B77A8.8060807@aliceposta.it>
References: <401B77A8.8060807@aliceposta.it>
Message-ID: <401BE55B.4060504@penguin-breeder.org>
Hi,
The bug you're describing should be fixed in CVS. Please try using CVS
snapshot version.
Why it behaves like a 600 CP scanner, I have no idea.
best regards
-- jochen
From legendary_fox@aliceposta.it Sat Jan 31 17:59:21 2004
From: legendary_fox@aliceposta.it (Dario Berzano)
Date: Sat, 31 Jan 2004 18:59:21 +0100
Subject: [sane-devel] Mustek 1200CP scanner does not release parallel
port
In-Reply-To: <401BE55B.4060504@penguin-breeder.org>
References: <401B77A8.8060807@aliceposta.it> <401BE55B.4060504@penguin-breeder.org>
Message-ID: <401BECF9.8060701@aliceposta.it>
Jochen Eisinger wrote:
>The bug you're describing should be fixed in CVS. Please try using CVS
>snapshot version.
>
It is actually fixed. My scanner now works fine - I mean: the scanning=20
head returns to its starting position when I cancel the operation and=20
when the operation finishes. Thank you.
--=20
dario berzano :: la volpe leggendaria :: http://flemma.knows.it/
=20
,-,
_.-=3D;~ /_
_-~ ' ;.
_.-~ ' .-~-~`-._
.--~~:. --.____88
__....-~~' .' . . _..-----~~
_..--~~~~' .' .' ,'
_.-~ . . ` ,'
.' :. ./
.: ,/ ` ::. ,'
.:' ,( ;. ::. ,-'
.' ./'.`. . . /::._... _/:.o/
/ ./'. . .) . _.,' `88;?88|
,' . .,/'._,-~ /_.o8P' 88P ?8b
_,'' . .,/',-~ d888P' 88' 88|
_.'~ . .,:oP' ?88b _..--- 88.--'8b.--..__
: ...' 88o __,------.88o _.=3D~- . `~~ `~~ ~-._
`.;;;:=3D' ~~ ~~~ ~- - - -
=20
=BB proud and happy linux user =AB
From edg1@tiscali.be Sat Jan 31 19:45:01 2004
From: edg1@tiscali.be (edg1@tiscali.be)
Date: Sat, 31 Jan 2004 20:45:01 +0100
Subject: [sane-devel] Mustek 1200CP scanner does not release parallel port
In-Reply-To: <401BECF9.8060701@aliceposta.it>; from legendary_fox@aliceposta.it on za, jan 31, 2004 at 18:59:21 +0100
References: <401B77A8.8060807@aliceposta.it> <401BE55B.4060504@penguin-breeder.org> <401BECF9.8060701@aliceposta.it>
Message-ID: <20040131194501.GA4675@reddot.erps-kwerps.be>
Dario Berzano wrote:
> Jochen Eisinger wrote:
>
>> The bug you're describing should be fixed in CVS. Please try using
>> CVS snapshot version.
>>
> It is actually fixed. My scanner now works fine - I mean: the
> scanning head returns to its starting position when I cancel the
> operation and when the operation finishes. Thank you.
Great!
I had just put up a web page describing the bug and possible solutions:
http://home.tiscali.be/EddyDeGreef/Sane/bug-1.0.13.html
but it looks like Jochen already helped you out (thanks, Jochen).
Best regards,
Eddy
From edg1@tiscali.be Sat Jan 31 21:25:23 2004
From: edg1@tiscali.be (edg1@tiscali.be)
Date: Sat, 31 Jan 2004 22:25:23 +0100
Subject: [sane-devel] Mustek 1200CP scanner does not release parallel port
In-Reply-To: <20040131200732.GC4675@reddot.erps-kwerps.be>; from edg1@tiscali.be on za, jan 31, 2004 at 21:07:32 +0100
References: <401B77A8.8060807@aliceposta.it> <20040131200732.GC4675@reddot.erps-kwerps.be>
Message-ID: <20040131212523.GF4675@reddot.erps-kwerps.be>
Dario Berzano wrote:
> Another strange aspect is that I had to set up the cis600 driver
> instead of the proper cis1200 one. With cis1200 (or cis1200+), the
> scanned image is vertically stretched, and the scanning head tries to
> scan out of range, making a loud, awful noise and damaging my
> hardware.
Sorry, I forgot this in my previous message:
Most likely, your scanner is not a true 1200CP. It looks like there are
600CP's out there that are labeled as 1200CP's.
I have had a few similar reports before. I don't know who is
responsible for this, ie., whether it is Mustek itself or some
reseller.
If your scanner works fine with the cis600 setting, then it's indeed
better not to try the cis1200 or cis1200+ settings, because that can be
damaging to your scanner, as you found out.
Best regards,
Eddy
From jim.george at blueyonder.co.uk Sun Jan 4 20:14:22 2004
From: jim.george at blueyonder.co.uk (Jim George)
Date: Sun, 4 Jan 2004 20:14:22 -0000
Subject: Fw: [sane-devel] mustek_pp trouble
Message-ID: <000401c3d2ff$5857d330$0400a8c0@jav.co.uk>
Re: [sane-devel] mustek_pp trouble
----- Original Message -----
From: jim.george at blueyonder.co.uk
To: jochen at penguin-breeder.org
Cc: jim.george at blueyonder.co.uk ; sane-devel at lists.alioth.debian.org
Sent: Friday, January 02, 2004 8:25 PM
Subject: Re: [sane-devel] mustek_pp trouble
> Hi,
>
> Jim George wrote:
>> [sanei_pa4s2] sanei_pa4s2_open: could not find scanner
>> [sanei_pa4s2] sanei_pa4s2_open: reported ASIC id 0xb5
> this looks like the backend couldn't find your scanner (0xa5 would =ave
> been a valid ID for example)
>
>> [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value =
>> [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0'
> here the port is released again (at least it should be)
>
> can you actually scan with SANE and your scanner? This looks all =ery
> strange to me...
>
> regards
> -- jochen
Jochen,
yes I have been able to scan but after an apparently sucessful scan =he
parallel port locks up (such that I can neither scan again nor print =gain
until I have rebooted).
I have sent logs up previously that Henning took a look at before
suggesting that you or Eddy might be able to help. Eddy has asked =e to
install gdb (if I have the room on my very small system) and run it =gain
and send the output up. I'll do this some time over the weekend =I've
literally just got back off holiday though so it'll take a couple of =ays
to get myself settled).
Thanks for your interest.
Jim
)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From gerhard at gjaeger.de Fri Jan 2 12:37:06 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Fri, 2 Jan 2004 13:37:06 +0100
Subject: [sane-devel] strange thread code?
In-Reply-To:
References:
Message-ID: <200401021337.06363.gerhard@gjaeger.de>
Hi,
On Mittwoch, 31. Dezember 2003 18:10, m. allan noah wrote:
> i am converting the fujitsu backend to use sanei_thread instead of fork.
okay - good ;-)
>
> in reading the threading code, i found something that i dont understand,
> and was hoping someone who knows a bit more could explain it to me:
let's try.
> in the function sanei_thread_waitpid(), the #ifdef PTHREAD section always
> returns pid (around line 354). but farther down, in the #else section, the
> return val from the waitpid() call is returned (which is the pid on
> success, but 0 or -1 otherwise)
>
> so if you are calling sanei_thread_waitpid() and there is an error, you
> might, or might not, get a negative return value?
The idea is, that sanei_thread_waitpid should be some replacement for waitpid,
and if this waitpid fails, you should get back exactly the code it delivers...
Only the case ECHILD is handled different (guess it was because of some
internals in the plustek backend ;-) )
In case of the pthread_join stuff, there's no proper replacement for waitpid,
and that's why this part always returns the pid (maybe this can also be
done better, but currently I don't see any problems there)
So you can use sanei_thread_waitpid the same way you have used it in
your backend...
> am i not reading this code correctly?
no, you're reading it correctly...
Hope this helps a bit,
Gerhard
From karsten.festag at gmx.de Sat Jan 3 20:52:24 2004
From: karsten.festag at gmx.de (Karsten Festag)
Date: Sat, 3 Jan 2004 21:52:24 +0100
Subject: [sane-devel] problems with microtek X6 scanner in TMA mode
In-Reply-To: <200312212000.41268.joheid@ttiger.in-berlin.de>
References: <200312152206.08204.joheid@ttiger.in-berlin.de> <200312201723.10871.karsten.festag@gmx.de> <200312212000.41268.joheid@ttiger.in-berlin.de>
Message-ID: <200401032027.15111.karsten.festag@gmx.de>
Hi Joachim,
I hope I found the bug. It is in the function 'attach'. There are several
calls like
status = scsi_read_attributes(&md->info[MD_SOURCE_ADF], md->name,
MD_SOURCE_ADF);
They all must have the first parameter &md->info[0] so that they look like:
status = scsi_read_attributes(&md->info[0], md->name, MD_SOURCE_ADF);
Are you able to check if this is the solution to the problem by recompiling
SANE with this modification? (The best thing is to use the source rpm provided
by SUSE and modify them.)
Karsten
On Sunday 21 December 2003 20:00, you wrote:
> Am Samstag, 20. Dezember 2003 17:23 schrieben Sie:
> > Hi Joachim,
> >
> > thanks for the logfiles, it looks like the backend uses the wrong
> > values, I'll have to check this.
> >
> > Do you remember which SANE version the TMA used to work with
> > before?
>
> Hi Karsten,
> I'm not 100% shure, but I think that it worked up to at least SuSE
> 7.3.
> I'n the beginning (around 1998/99) there were some problems with the
> microtek firmware (at least V 1.6 was required) but then everything
> worked o.k.
> Yours
From henning at meier-geinitz.de Mon Jan 5 18:44:29 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 5 Jan 2004 19:44:29 +0100
Subject: [sane-devel] Cannot connect to saned
In-Reply-To: <1072726235.11758.13.camel@hauke.coltzimski>
References: <1072715179.8227.14.camel@hauke.coltzimski> <20031229164525.GD1280@meier-geinitz.de> <1072726235.11758.13.camel@hauke.coltzimski>
Message-ID: <20040105184429.GF1651@meier-geinitz.de>
Hi,
On Mon, Dec 29, 2003 at 08:31:07PM +0100, Hauke Coltzau wrote:
> > > On the other hand, the sane server itself seems to be fine,
> > > since I can run scanimage -L on localhost and telnet to
> > > port 6566 from both localhost and remote.
> >
> > So it doesn't look like a saned problem on first sight. What happens
> > when you do:
> > scanimage -d net:192.168.0.1 -T
>
> The client says that it is out of memory. It shouldn't be since
> there's lots of free mem available. The same thing happens, if
> I try scanimage -d net:192.168.0.1 -t on the server.
> Can it be a bug?
Yes. Probably in the backend on the server. Please show us the exact
error message. You may also get some debug messages like this:
SANE_DEBUG_NET=255 scanimage -d net:192.168.0.1 -T
> > Does scanning work? I.e. id you start saned in debug mode on the
> > server, does "scanimage -d net:192.168.0.1 >image.pnm" on the client
> > scan something? If not, what's the error message?
>
> As above, out of memory. Nothing more, nothing in /var/log/messages
Nothing? At least when running in (x)inetd mode, daned does print some
messages into syslog.
In debug mode, it prints the messages to stderr.
Bye,
Henning
From henning at meier-geinitz.de Mon Jan 5 18:50:47 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 5 Jan 2004 19:50:47 +0100
Subject: [sane-devel] Visioneer OneTouch Pro 8820 USB
In-Reply-To: <3FF119FB.7030909@vonostingroup.com>
References: <3FF119FB.7030909@vonostingroup.com>
Message-ID: <20040105185047.GG1651@meier-geinitz.de>
Hi,
On Tue, Dec 30, 2003 at 01:23:55AM -0500, Frank Laszlo wrote:
> I have the above scanner, And I wondered if it was supported by sane?
> (or anything in linux)
>
> I believe this model is discontinued, though im not 100% sure. please
> let me know of any effort for a driver to be developed. Thanks
At least our lists don't know anything about that scanner which is
usually bad. If nobody cries out loudly I'll add this scanner to the
"unsupported" list.
Bye,
Henning
From henning at meier-geinitz.de Mon Jan 5 18:54:44 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 5 Jan 2004 19:54:44 +0100
Subject: [sane-devel] Umax 2200 smearing/dangerous options
In-Reply-To: <20031231140600.F744@green.nat.fasttrackmonkey.com>
References: <20031231140600.F744@green.nat.fasttrackmonkey.com>
Message-ID: <20040105185444.GH1651@meier-geinitz.de>
Hi,
On Wed, Dec 31, 2003 at 02:16:40PM -0500, Charles Sprickman wrote:
> Also, is there a wiki-type thing somewhere where people can share
> information about their particular models? It seems that I stumbled all
> over things that just aren't documented on the site, but are common
> knowledge once you're on the list for a while (ie: don't use the OS
> driver, use libusb, scanner won't work w/o quality control disabled, etc.)
As far as I know there is no wiki. This is information that should
really be added to the backend's manpage. In case of options that
should be disabled: ideally, the backend should do that automatically.
I suggest to add a (wishlist) bug for that backend on our bug-tracking
system.
Bye,
Henning
From edg1 at tiscali.be Sat Jan 3 20:06:48 2004
From: edg1 at tiscali.be (edg1 at tiscali.be)
Date: Sat, 3 Jan 2004 21:06:48 +0100
Subject: [sane-devel] mustek_pp trouble (was: saned doesn't release the parallel port when finished)
In-Reply-To: <20040103193953.GB4122@reddot.erps-kwerps.be>; from edg1@tiscali.be on za, jan 03, 2004 at 20:39:53 +0100
References: <4240.192.168.0.4.1072433618.squirrel@tassi.local> <20031226093600.GJ1498@meier-geinitz.de> <4549.192.168.0.4.1072448029.squirrel@tassi.local> <20031226131822.GK1498@meier-geinitz.de> <1177.192.168.0.4.1072455738.squirrel@tassi.local> <20031226153605.GL1498@meier-geinitz.de> <20031226230048.GA3250@reddot.erps-kwerps.be> <3613.192.168.0.4.1073080152.squirrel@tassi.local> <20040103193953.GB4122@reddot.erps-kwerps.be>
Message-ID: <20040103200648.GC4768@reddot.erps-kwerps.be>
On 02-01-04 22:49:12 Jim George wrote:
> I tried that but got the following before I'd had a chance to run
> scanimage.
>
> Have a lot of fun...
> tassi:~ # SANE_DEBUG_MUSTEK_PP=255 gdb saned
> ...
> (gdb) r -d128
> Starting program: /usr/sbin/saned -d128
> [saned] main: starting debug mode (level 128)
> [saned] main: trying to get port for service `sane' (getaddrinfo)
> [saned] main: [0] socket () using IPv6
> [saned] main: [0] setsockopt ()
> [saned] main: [0] bind () to port 6566
> [saned] main: [0] bind failed: Address already in use
> [saned] main: [1] socket () using IPv4
> [saned] main: [1] setsockopt ()
> [saned] main: [1] bind () to port 6566
> [saned] main: [1] bind failed: Address already in use
> [saned] main: couldn't bind an address. Exiting.
>
> Program exited with code 01.
> (gdb)
>
> Any ideas as to how I can progress this?
Sorry, I forgot to mention that you first have to stop xinetd:
/etc/rc.d/init.d/xinetd stop
Best regards,
Eddy
From jim.george at blueyonder.co.uk Mon Jan 5 21:46:39 2004
From: jim.george at blueyonder.co.uk (Jim George)
Date: Mon, 5 Jan 2004 21:46:39 -0000 (GMT)
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
Message-ID: <1687.192.168.0.4.1073339199.squirrel@tassi.local>
Eddy and Joachen,
when I tried to run saned under gdb I got the following output. Doesn't
look good does it? Can you tell me what I should do now?
SANE_DEBUG_MUSTEK_PP=255 gdb
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are welcome to change it and/or distribute copies of it under certain
conditions. Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details. This GDB was configured as "i586-suse-linux".
(gdb) exec-file /usr/sbin/saned
(gdb) r -d128
Starting program: /usr/sbin/saned -d128
[saned] main: starting debug mode (level 128)
[saned] main: trying to get port for service `sane' (getaddrinfo)
[saned] main: [0] socket () using IPv6
[saned] main: [0] setsockopt ()
[saned] main: [0] bind () to port 6566
[saned] main: [0] bind failed: Address already in use
[saned] main: [1] socket () using IPv4
[saned] main: [1] setsockopt ()
[saned] main: [1] bind () to port 6566
[saned] main: [1] bind failed: Address already in use
[saned] main: couldn't bind an address. Exiting.
Program exited with code 01.
(gdb)
TIA,
Jim
From jb at jblache.org Mon Jan 5 20:50:31 2004
From: jb at jblache.org (Julien BLACHE)
Date: Mon, 05 Jan 2004 21:50:31 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel
port
In-Reply-To: <1687.192.168.0.4.1073339199.squirrel@tassi.local> (Jim
George's message of "Mon, 5 Jan 2004 21:46:39 -0000 (GMT)")
References: <1687.192.168.0.4.1073339199.squirrel@tassi.local>
Message-ID: <87r7ye3yso.fsf@frigate.technologeek.org>
"Jim George" wrote:
Hi,
> [saned] main: [0] bind failed: Address already in use
> [saned] main: [1] bind failed: Address already in use
> [saned] main: couldn't bind an address. Exiting.
>
> Program exited with code 01.
I guess you have (x)inetd configured to listen on port 6566 ... ?
JB.
--
Julien BLACHE
GPG KeyID 0xF5D65169
From gerhard at gjaeger.de Mon Jan 5 21:07:59 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Mon, 5 Jan 2004 22:07:59 +0100
Subject: [sane-devel] Plustek OpticPro U12 (product-id:0x0001)
Message-ID: <200401052207.59219.gerhard@gjaeger.de>
Hi list,
finally we now have a backend called U12 which should support the following
scanner:
Plustek OpticPro U12
Plustek OpticPro UT12
Plustek OpticPro 1212U (all having the product-ID 0x0001)
also the
Genius ColorPage Vivid III V2 USB should work (Plustek vendor & product id)
and
Genius HR6 USB V1 (vendor-ID: 0x0458, product-ID: 0x2004)
should work.
The backend currently is in alpha state, which means, that only
color scanning will work and we have some other problems, which
require sometimes a restart of the backend - I hope to improve this
ASAP.
As I have only a U12 as test-device, the others are not tested...
To test it with your device, you have to download the latest CVS-version
of SANE and to activate the u12 backend...
Have fun,
Gerhard
From henning at meier-geinitz.de Mon Jan 5 21:43:08 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 5 Jan 2004 22:43:08 +0100
Subject: [sane-devel] Plustek OpticPro U12 (product-id:0x0001)
In-Reply-To: <200401052207.59219.gerhard@gjaeger.de>
References: <200401052207.59219.gerhard@gjaeger.de>
Message-ID: <20040105214308.GJ1651@meier-geinitz.de>
Hi,
On Mon, Jan 05, 2004 at 10:07:59PM +0100, Jaeger, Gerhard wrote:
> finally we now have a backend called U12 which should support the following
> scanner:
> Genius ColorPage Vivid III V2 USB should work (Plustek vendor & product id)
> Genius HR6 USB V1 (vendor-ID: 0x0458, product-ID: 0x2004) should work.
I don't have any of these scanners but the " Genius Colorpage Vivid
III V2 USB" was reported to me as supported by the gt68xx backend. According
to that report the scanner has the same ids as the Genius Colorpage
Vivid 3x. The ids are reported to be 0x0458/0x2011. Two scanners with
the same name?
The "Genius Colorpage Vivid III" (without the "V2") is however
reported to have these ids: 0x07b3 0x0001 (see unsupported.desc). So I
guess that one IS supported by your backend.
Good work!
Don't forget to update sane.man :-)
Bye,
Henning
From henning at meier-geinitz.de Mon Jan 5 21:58:37 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Mon, 5 Jan 2004 22:58:37 +0100
Subject: [sane-devel] Umax 2200 smearing/dangerous options
In-Reply-To: <20031231140600.F744@green.nat.fasttrackmonkey.com>
References: <20031231140600.F744@green.nat.fasttrackmonkey.com>
Message-ID: <20040105215837.GL1651@meier-geinitz.de>
Hi,
On Wed, Dec 31, 2003 at 02:16:40PM -0500, Charles Sprickman wrote:
> This will hopefully be the last time I bother the list. My Umax 2200 is
> now basically working, but the scans look pretty bad. They have what I
> could best describe as "banding" or "smearing". An example from a 300dpi
> scan is here (white areas on the left are the scanner lid and show the
> pattern rather well - looks like the output of a really bad inkjet
> printer):
>
> http://home.manymonkeys.com/out.png (approx. 1MB png)
On first sight I would have said: the image is ok. When I looked with
gimp and it's magnifying option I found two effects:
a) There is a small line distance correction error. That means that
the colors are not exactly centered vertically. You can see that
effect best at the top edge of the photo. There is a blue/brown
stripe. Possible causes: Bug in the backend or scanner firmware. Or low
quality scanner.
b) High noise. The colors of two adjacent pixels should be (mostly)
the same in the white area. Possible causes: Low quality sensor.
Defective or old lamp. Bug in the backend or firmware (calibration).
I guess the horizontal lines that look like an old inkjet print are
cause by problem a). As I don't own such a scanner I have no clue how
to solve it (if possible), however.
Bye,
Henning
From benedict.prescott at virgin.net Mon Jan 5 23:15:01 2004
From: benedict.prescott at virgin.net (Ben Prescott)
Date: Mon, 5 Jan 2004 23:15:01 +0000
Subject: [sane-devel] Trust Imagery 9600
Message-ID: <20040105231501.35fe567c.benedict.prescott@virgin.net>
I'm having problems getting this working.
I've searched the archive and there's nothing in there apart from the
announcement when the teco3 backend was released.
I also note that the man pages states that it is untested. I would
hypothesise that they've littered the output from /inquiry/ with
some extra spaces, which is why its failing.
FCC ID is, BTW, 'E8OVM3552'
The final test I did is as follows:
# export SANE_DEBUG_TECO3=128
# scanimage -d teco3:/dev/sg3
The output is attached in a plain text file; my email client is wrapping
it and making a mess.
The error returned from all the front ends is 'invalid argument', as in:
scanimage: open of device teco3:/dev/sg3 failed: Invalid argument
I'm guessing the key lines in the debug are as follows:
[teco3] device is "Aashima " "IMAGERY 9600SP " "1.07" "TECO VM6552"
[teco3] teco_identify_scanner: exit, device not supported
[teco3] ERROR: attach_scanner: scanner-identification failed
Some background ...
I stripped out the backend config file (I'm running Suse 8.2; YAST has
filled it with other stuffas well) as per the man page's statement
about what it should contain, but I would guess that is irrelevant given
the way I ran it.
# cat /etc/sane.d/teco3.conf
/dev/sg3
Versions:
scanimage --version
scanimage (sane-backends) 1.0.11; backend version 1.0.11
/usr/lib/sane/libsane-teco3.so.1.0.11
The SCSI adapter is an on-board Adaptec aic7895. Also on the same bus
are:
Vendor: COMPAQ Model: ST32171W Rev: 0682
Type: Direct-Access ANSI SCSI revision: 02
blk: queue c1b67c18, I/O limit 4095Mb (mask 0xffffffff)
Vendor: SCANNER Model: Rev: 2.00
Type: Scanner ANSI SCSI revision: 01
blk: queue c1b67618, I/O limit 4095Mb (mask 0xffffffff)
Vendor: PLEXTOR Model: CD-ROM PX-40TS Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 02
blk: queue c1b67218, I/O limit 4095Mb (mask 0xffffffff)
The Trust unit registers as follows:
Vendor: Aashima Model: IMAGERY 9600SP Rev: 1.07
Type: Scanner ANSI SCSI revision: 02
blk: queue c1b33a18, I/O limit 4095Mb (mask 0xffffffff)
And the following is generated by the host adapter driver for this
device:
<4>(scsi0:A:5:0): refuses synchronous negotiation. Using asynchronous
All other devices work correctly. The main reason why the other scanner
is there (Mustek A3 SP, works a treat in Linux, blue screens NT -
thankyou very much for SANE!!) is to do with the combination of cables
and terminators I've got.
Thankyou in advance for your help. If I/we can get it working, I'm happy
to put the thing through a test cycle so it can acquire 'tested' status.
Assuming anyone cares, of course!
regards, Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagery.txt
Type: application/octet-stream
Size: 1968 bytes
Desc: not available
URL:
From ecr959 at yahoo.com Tue Jan 6 00:56:23 2004
From: ecr959 at yahoo.com (Eddie Colon)
Date: Mon, 5 Jan 2004 16:56:23 -0800 (PST)
Subject: [sane-devel] 4600 scanner info
Message-ID: <20040106005623.14529.qmail@web41408.mail.yahoo.com>
I just sent you a message with some info on this model. I'm sorry
that I used my other email, please accept my info, I really am a new
member of your DEV list, but I registered with this email, not my
othere one.
Eddie
=====
Eddie Colon
Bayamon, PR 00959
"The best things in life are not things"
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
From gerhard at gjaeger.de Tue Jan 6 09:39:13 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Tue, 6 Jan 2004 10:39:13 +0100
Subject: [sane-devel] Plustek OpticPro U12 (product-id:0x0001)
In-Reply-To: <20040105214308.GJ1651@meier-geinitz.de>
References: <200401052207.59219.gerhard@gjaeger.de> <20040105214308.GJ1651@meier-geinitz.de>
Message-ID: <200401061039.14088.gerhard@gjaeger.de>
Moin,
On Montag, 5. Januar 2004 22:43, Henning Meier-Geinitz wrote:
[SNIPSNAP]
> I don't have any of these scanners but the " Genius Colorpage Vivid
> III V2 USB" was reported to me as supported by the gt68xx backend.
> According to that report the scanner has the same ids as the Genius
> Colorpage Vivid 3x. The ids are reported to be 0x0458/0x2011. Two scanners
> with the same name?
>
> The "Genius Colorpage Vivid III" (without the "V2") is however
> reported to have these ids: 0x07b3 0x0001 (see unsupported.desc). So I
> guess that one IS supported by your backend.
Okay, no problem! I only searched through some older mails here on
the plustek list and that's why I decided to use Vivid III V2...
But you're right, the 0x07b3 0x0001 is the correct one (obviously, because
of the Plustek vendor ID ;-)
> Good work!
>
> Don't forget to update sane.man :-)
Hmmmmpf, I think this already happens :-))))))))))))
Ciao,
Gerhard
BTW.:
Any progress on the GL646 stuff??
From jochen at penguin-breeder.org Tue Jan 6 10:54:50 2004
From: jochen at penguin-breeder.org (Jochen Eisinger)
Date: Tue, 06 Jan 2004 11:54:50 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel
port
In-Reply-To: <1687.192.168.0.4.1073339199.squirrel@tassi.local>
References: <1687.192.168.0.4.1073339199.squirrel@tassi.local>
Message-ID: <3FFA93FA.80103@penguin-breeder.org>
Hello,
I've thought long about your problem but I still don't get how your
parport can be locked that badly.
What kernel version are you using? What Linux distribution? Could you
please send the output of (after rebooting - that is in a state where
the scan will work?)
SANE_DEBUG_SANEI_PA4S2=6 scanimage --test
regards
-- jochen
From eddiecr at caribe.net Tue Jan 6 00:40:30 2004
From: eddiecr at caribe.net (Eddie Colon)
Date: Mon, 05 Jan 2004 19:40:30 -0500
Subject: [sane-devel] here is info for the HP scanjet 4600 scanner
Message-ID: <1073349630.2585.17.camel@localhost.localdomain>
Hello everybody,
Happy New Year to all. this is my first contribution to this
forum. I just bought an HP scanjet 4600 scanner, it has USB
connection. I really like it, want to use it on my Mandrake PC, here
is the "cat /proc/bus/usb/devices " printout. I hope this helps
create a driver for it.
[root at localhost /]# cat /proc/bus/usb/devices
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.04
S: Manufacturer=Linux 2.4.22-10mdk ehci_hcd
S: Product=VIA Technologies, Inc. USB 2.0
S: SerialNumber=00:10.3
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
T: Bus=04 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=03f0 ProdID=3005 Rev= 1.00
S: Manufacturer=Hewlett-Packard.
S: Product=hp scanjet
S: SerialNumber=CN3B4B502993
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=500us
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=e400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=e800
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=ec00
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
[root at localhost /]#
--
Eddie Colon
Bayamon, Puerto Rico
"The best things in life are not things."
From anoah at pfeiffer.edu Tue Jan 6 15:15:12 2004
From: anoah at pfeiffer.edu (m. allan noah)
Date: Tue, 6 Jan 2004 10:15:12 -0500 (EST)
Subject: [sane-devel] strange thread code?
In-Reply-To: <200401021337.06363.gerhard@gjaeger.de>
Message-ID:
On Fri, 2 Jan 2004, Jaeger, Gerhard wrote:
> Hi,
>
> On Mittwoch, 31. Dezember 2003 18:10, m. allan noah wrote:
> > i am converting the fujitsu backend to use sanei_thread instead of fork.
>
> okay - good ;-)
>
> >
> > in reading the threading code, i found something that i dont understand,
> > and was hoping someone who knows a bit more could explain it to me:
>
> let's try.
>
> > in the function sanei_thread_waitpid(), the #ifdef PTHREAD section always
> > returns pid (around line 354). but farther down, in the #else section, the
> > return val from the waitpid() call is returned (which is the pid on
> > success, but 0 or -1 otherwise)
> >
> > so if you are calling sanei_thread_waitpid() and there is an error, you
> > might, or might not, get a negative return value?
>
> The idea is, that sanei_thread_waitpid should be some replacement for waitpid,
> and if this waitpid fails, you should get back exactly the code it delivers...
> Only the case ECHILD is handled different (guess it was because of some
> internals in the plustek backend ;-) )
ok, i understand this, sanei_thread_waitpid should mimic waitpid()
functionality....
> In case of the pthread_join stuff, there's no proper replacement for waitpid,
> and that's why this part always returns the pid (maybe this can also be
> done better, but currently I don't see any problems there)
>
ok, so sanei_thread_waitpid does not mimic waitpid, in the case of
threading?
> So you can use sanei_thread_waitpid the same way you have used it in
> your backend...
unless threading is used, cause i cant use the return val in that case,
instead i must use the status pointer?
seems like this abstraction layer is not quite abstracted enough...
>
> > am i not reading this code correctly?
>
> no, you're reading it correctly...
>
> Hope this helps a bit,
> Gerhard
>
>
thanks for the tips, thought i was missing something...
allan
--
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
From henning at meier-geinitz.de Tue Jan 6 17:46:49 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Tue, 6 Jan 2004 18:46:49 +0100
Subject: [sane-devel] here is info for the HP scanjet 4600 scanner
In-Reply-To: <1073349630.2585.17.camel@localhost.localdomain>
References: <1073349630.2585.17.camel@localhost.localdomain>
Message-ID: <20040106174649.GE1515@meier-geinitz.de>
Hi,
On Mon, Jan 05, 2004 at 07:40:30PM -0500, Eddie Colon wrote:
> Happy New Year to all. this is my first contribution to this
> forum. I just bought an HP scanjet 4600 scanner, it has USB
> connection. I really like it, want to use it on my Mandrake PC, here
> is the "cat /proc/bus/usb/devices " printout. I hope this helps
> create a driver for it.
Thanks. I'll add that scanner to our list. However, that won't help
much until someone (you?) starts to write a driver :-)
Can you really see the image while it's scanned? The description of
that scanner looks a bit strange.
Bye,
Henning
From joheid at ttiger.in-berlin.de Tue Jan 6 21:20:45 2004
From: joheid at ttiger.in-berlin.de (joachim heidemeier)
Date: Tue, 6 Jan 2004 22:20:45 +0100
Subject: [sane-devel] problems with microtek X6 scanner in TMA mode
In-Reply-To: <200401032027.15111.karsten.festag@gmx.de>
References: <200312152206.08204.joheid@ttiger.in-berlin.de> <200312212000.41268.joheid@ttiger.in-berlin.de> <200401032027.15111.karsten.festag@gmx.de>
Message-ID: <200401062220.45298.joheid@ttiger.in-berlin.de>
Am Samstag, 3. Januar 2004 21:52 schrieb Karsten Festag:
> Hi Joachim,
>
> I hope I found the bug. It is in the function 'attach'. There are
> several calls like
>
> status = scsi_read_attributes(&md->info[MD_SOURCE_ADF], md->name,
> MD_SOURCE_ADF);
>
> They all must have the first parameter &md->info[0] so that they
> look like:
>
> status = scsi_read_attributes(&md->info[0], md->name,
> MD_SOURCE_ADF);
>
> Are you able to check if this is the solution to the problem by
> recompiling SANE with this modification? (The best thing is to use
> the source rpm provided by SUSE and modify them.)
>
> Karsten
>
> On Sunday 21 December 2003 20:00, you wrote:
> > Am Samstag, 20. Dezember 2003 17:23 schrieben Sie:
> > > Hi Joachim,
> > >
> > > thanks for the logfiles, it looks like the backend uses the
> > > wrong values, I'll have to check this.
> > >
> > > Do you remember which SANE version the TMA used to work with
> > > before?
> >
> > Hi Karsten,
> > I'm not 100% shure, but I think that it worked up to at least
> > SuSE 7.3.
> > I'n the beginning (around 1998/99) there were some problems with
> > the microtek firmware (at least V 1.6 was required) but then
> > everything worked o.k.
> > Yours
Hi Karsten,
I checked your patches and everything is o.k. :-).
Yours
--
Dr. J. Heidemeier
Email: joheid at ttiger.in-berlin.de
From jochen at penguin-breeder.org Tue Jan 6 22:21:27 2004
From: jochen at penguin-breeder.org (Jochen Eisinger)
Date: Tue, 06 Jan 2004 23:21:27 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel
port
In-Reply-To: <1687.192.168.0.4.1073339199.squirrel@tassi.local>
References: <1687.192.168.0.4.1073339199.squirrel@tassi.local>
Message-ID: <3FFB34E7.3080107@penguin-breeder.org>
Hello,
another idea. May it be, that there are any saned or scanimage running
after the first scan attempt?
regards
-- jochen
Jim George wrote:
> Eddy and Joachen,
>
> when I tried to run saned under gdb I got the following output. Doesn't
> look good does it? Can you tell me what I should do now?
>
> SANE_DEBUG_MUSTEK_PP=255 gdb
> GNU gdb 5.2.1
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are welcome to change it and/or distribute copies of it under certain
> conditions. Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details. This GDB was configured as "i586-suse-linux".
> (gdb) exec-file /usr/sbin/saned
> (gdb) r -d128
> Starting program: /usr/sbin/saned -d128
> [saned] main: starting debug mode (level 128)
> [saned] main: trying to get port for service `sane' (getaddrinfo)
> [saned] main: [0] socket () using IPv6
> [saned] main: [0] setsockopt ()
> [saned] main: [0] bind () to port 6566
> [saned] main: [0] bind failed: Address already in use
> [saned] main: [1] socket () using IPv4
> [saned] main: [1] setsockopt ()
> [saned] main: [1] bind () to port 6566
> [saned] main: [1] bind failed: Address already in use
> [saned] main: couldn't bind an address. Exiting.
>
> Program exited with code 01.
> (gdb)
>
>
> TIA,
>
> Jim
>
>
>
>
From olaf at epkowa.co.jp Wed Jan 7 00:25:20 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Wed, 07 Jan 2004 09:25:20 +0900
Subject: [sane-devel] Epson GT-7400U not detected
In-Reply-To: <20031231100823.GI1003@meier-geinitz.de> (Henning
Meier-Geinitz's message of "Wed, 31 Dec 2003 11:08:23 +0100")
References: <1072823795.721.38.camel@invigiator.invigiator.com>
<2EF6A039-3B1F-11D8-B259-000A957E40E8@khk.net>
<1072829396.721.49.camel@invigiator.invigiator.com>
<20031231100823.GI1003@meier-geinitz.de>
Message-ID: <878ykkehan.fsf@zen.epkowa.co.jp>
Henning Meier-Geinitz writes:
> Hi,
>
> On Wed, Dec 31, 2003 at 09:09:56AM +0900, Julian Gough wrote:
>> Under windows it is reported as an Epson Perfection 1270, and seems to
>> work, but the software is in Japanese.
>>
>> I can see that the 1250 and 1260 use the plustek driver. I've configured
>> /etc/sane.d/plustek.conf as follows:
>> [usb] 0x04B8 0x0120
>> device auto
>>
>> but still I get nothing detected. I can see no way to try to *force* the
>> plustek driver to be used so that I can see if it works.
>
> You may also try the snapscan backend. At least the 1670 is supported
> by that backend. Maybe these scanners are similar? But you will need
> the latest development version of SANE. Maybe the manintainer of the
> snapscan backend has heard baout that scanner: Oliver Schwartz
>
Sorry for the late follow-up.
I've checked around a little bit and found some tidbits of information
that seems to indicate that the GT-7400U is the little sister of the
GT-8400U. There is a reasonable chance that this scanner works with
the snapscan backend. You will probably have to muck around a bit to
get it to load the right firmware file and copy that file from the
Windoze software.
No guarantees though ;-)
--
Olaf Meeuwissen EPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
From kent-cdr at greendot.com.ph Wed Jan 7 00:45:17 2004
From: kent-cdr at greendot.com.ph (kent E.)
Date: Wed, 07 Jan 2004 08:45:17 +0800
Subject: [sane-devel] using saned
Message-ID: <1073436317.916.4.camel@leprechaun.cdr.com>
does any have any docs on how to setup a network scanner using saned, i
am following the one in http://www.penguin-breeder.org/sane/saned/ but
still i am confused, i am using rh9 and my 3-in-1 model is hp1100a
any ideas?
TIA
Kent
From vhodge at sympatico.ca Wed Jan 7 03:32:12 2004
From: vhodge at sympatico.ca (vhodge at sympatico.ca)
Date: Tue, 6 Jan 2004 22:32:12 -0500
Subject: [sane-devel] Mustek 1200USB scanner (VID 055F PID 0003)
Message-ID: <20040107033212.WHRT23150.tomts13-srv.bellnexxia.net@[67.68.54.6]>
January 6, 2004
Hi,
I've just bought this unboxed, at least I already had a
power brick, now I'm looking to program it. I turn to Linux,
which leads me to this SANE forum, and the statement that
this scanner is unsupported but "programming information is
available". Do I have to sign anything?
Background: I'm building USB drivers under DOS as a hobby,
have written UHCI mouse, drawing tablet drivers. My only
product will be a confirmation that the information was
found to be correct.
Victor Hodge
From edg1 at tiscali.be Wed Jan 7 08:50:02 2004
From: edg1 at tiscali.be (edg1 at tiscali.be)
Date: Wed, 7 Jan 2004 09:50:02 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <3FFB34E7.3080107@penguin-breeder.org>
Message-ID: <3FFB29D700000243@ocpmta2.freegates.net>
Hi,
as I said before (but I don't know whether it came through because of the
mail hickups), the problem in gdb is almost certainly caused by xinetd
that is still running and listening to port 6566. xinetd has to be stopped
first before running saned in gdb:
/etc/rc.d/init.d/xinetd stop
After that, it should be possible to get a stack trace of the point where
saned hangs.
Eddy
Jochen Eisinger wrote:
> Hello,
>
> another idea. May it be, that there are any saned or scanimage running
> after the first scan attempt?
>
> regards
> -- jochen
>
> Jim George wrote:
> > Eddy and Joachen,
> >
> > when I tried to run saned under gdb I got the following output. Does
> >'t
> > look good does it? Can you tell me what I should do now?
> >
> > SANE_DEBUG_MUSTEK_PP=255 gdb
> > GNU gdb 5.2.1
> > Copyright 2002 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and
you
> > are wel
> >ome to change it and/or distribute copies of it under certain
> > conditions. Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB. Type "show warranty" for
> > details. This GDB was configured as "i586-suse-linux".
> > (
> >db) exec-file /usr/sbin/saned
> > (gdb) r -d128
> > Starting program: /usr/sbin/saned -d128
> > [saned] main: starting debug mode (level 128)
> > [saned] main: trying to get port for service `sane' (getaddrinfo)
> > [saned] main: [0] socket () using IPv6
> >
> >[saned] main: [0] setsockopt ()
> > [saned] main: [0] bind () to port 6566
> > [saned] main: [0] bind failed: Address already in use
> > [saned] main: [1] socket () using IPv4
> > [saned] main: [1] setsockopt ()
> > [saned] main: [1] bind () to port 6566
> >
> >[saned] main: [1] bind failed: Address already in use
> > [saned] main: couldn't bind an address. Exiting.
> >
> > Program exited with code 01.
> > (gdb)
> >
> >
> > TIA,
> >
> > Jim
---------------------------------------------------------------
Tiscali ADSL: 12 maanden aan 29,50 ?/maand! Snel Internet, en voor iedereen.
http://reg.tiscali.be/default.asp?lg=nl
From jim.george at blueyonder.co.uk Wed Jan 7 10:20:39 2004
From: jim.george at blueyonder.co.uk (Jim George)
Date: Wed, 7 Jan 2004 10:20:39 -0000 (GMT)
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <3FFB29D700000243@ocpmta2.freegates.net>
References: <3FFB34E7.3080107@penguin-breeder.org>
<3FFB29D700000243@ocpmta2.freegates.net>
Message-ID: <1856.192.168.0.4.1073470839.squirrel@tassi.local>
> Hi,
>
> as I said before (but I don't know whether it came through because of
> the mail hickups), the problem in gdb is almost certainly caused by
> xinetd that is still running and listening to port 6566. xinetd has to
> be stopped first before running saned in gdb:
>
> /etc/rc.d/init.d/xinetd stop
>
> After that, it should be possible to get a stack trace of the point
> where saned hangs.
>
> Eddy
>
Eddy,
I have now run saned through gdb and done two scans. The first appeared
to complete successfully so I ran the second but the client timed out and
eventually saned quit (as you will see from the attached).
Thanks for your continued help,
Jim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ZOC0401.zip
Type: application/x-zip-compressed
Size: 11671 bytes
Desc: not available
URL:
From gerard at gkall.hobby.nl Wed Jan 7 12:00:18 2004
From: gerard at gkall.hobby.nl (gerard klaver)
Date: Wed, 07 Jan 2004 11:00:18 -0100
Subject: [sane-devel] Trust Imagery 9600
In-Reply-To: <20040105231501.35fe567c.benedict.prescott@virgin.net>
References: <20040105231501.35fe567c.benedict.prescott@virgin.net>
Message-ID: <1073476817.1987.29.camel@gk-lex3>
On Mon, 2004-01-05 at 22:15, Ben Prescott wrote:
> I'm having problems getting this working.
>
> I've searched the archive and there's nothing in there apart from the
> announcement when the teco3 backend was released.
see the teco mailinglist at yahoo, also mail archive is present.
http://groups.yahoo.com/group/teco-sane-devel/
teco3 homepage
http://www.zago.net/sane/#teco
>
> I'm guessing the key lines in the debug are as follows:
>
> [teco3] device is "Aashima " "IMAGERY 9600SP " "1.07" "TECO VM6552"
> [teco3] teco_identify_scanner: exit, device not supported
> [teco3] ERROR: attach_scanner: scanner-identification failed
>
To get this scanner working you have to patch the following files
teco3.conf with the name of the scanner:
scsi "Aashima" "IMAGERY 9600SP"
teco3.h change
TECO_VM3552 to
TECO_VM3552,
TECO_VM6552
teco3.c for a start add something like:
{
6, "TECO VM6552",
TECO_VM6552,
"Aashima", IMAGERY 9600SP",
(.. .. ..), values for your resolution
...., .... your max x and y resolution
}
There should more be changed to get the scanner working, but this should
be a start (maybe scsi traces are needed to get a correct working
scanner) some example on http://gkall.hobby.nl/notes1.html
Frank Zago (teco3 maintaniner) should be able to tell more about the
changes which are needed to get this scanner working.
--
----------
m.vr.gr.
Gerard Klaver
From jochen at penguin-breeder.org Wed Jan 7 12:50:43 2004
From: jochen at penguin-breeder.org (jochen)
Date: Wed, 7 Jan 2004 13:50:43 +0100
Subject: [sane-devel] using saned
In-Reply-To: <1073436317.916.4.camel@leprechaun.cdr.com>
References: <1073436317.916.4.camel@leprechaun.cdr.com>
Message-ID: <20040107125043.GA6660@coffee.homeunix.org>
hello,
what exactly is confusing you? please give some more details, so we can
probably help you.
regards
-- jochen
On Wed, Jan 07, 2004 at 08:45:17AM +0800, kent E. wrote:
> does any have any docs on how to setup a network scanner using saned, i
> am following the one in http://www.penguin-breeder.org/sane/saned/ but
> still i am confused, i am using rh9 and my 3-in-1 model is hp1100a
>
> any ideas?
> TIA
>
> Kent
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
>
>
From edg1 at tiscali.be Wed Jan 7 12:54:29 2004
From: edg1 at tiscali.be (edg1 at tiscali.be)
Date: Wed, 7 Jan 2004 13:54:29 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <1856.192.168.0.4.1073470839.squirrel@tassi.local>
Message-ID: <3FFB29D70000062E@ocpmta2.freegates.net>
Jim George wrote:
> Eddy,
>
> I have now run saned through gdb and done two scans. The first appeared
> to complete successfully so I ran the second but the client timed out and
> eventually saned quit (as you will see from the attached).
>
> Thanks for your continued help,
>
> Jim
>
Hi Jim,
I think it's normal that saned exits after one scan. Normally, it's
xinetd that restarts saned when a new request comes in.
To restart saned in gdb, you only have to enter "r" at the prompt
and then you can perform another scan.
What surprises me is that, now, saned doesn't hang at the end.
IIRC, when you started saned -d128 without gdb, it did hang.
I'm getting confused. Could you repeat the following tests, such
that I get a clear picture:
1) With xinetd
- Make sure xinetd is running (/etc/rc.d/init.d/xinetd restart).
- scanimage -d net:localhost:mustek_pp:Mustek-1200CP > test.pnm
* Does scanimage hang?
* If it hangs and you kill scanimage, is saned still running?
(ps aux | grep saned)
* If saned still runs, just kill it.
2) Without xinetd, no gdb
- Make sure xinetd is stopped (/etc/rc.d/init.d/xinetd stop).
- SANE_DEBUG_MUSTEK_PP=255 saned -d128
- In another window:
scanimage -d net:localhost:mustek_pp:Mustek-1200CP > test.pnm
* Does scanimage hang?
* Does saned exit? (It should).
* If it hangs, please show the last few lines of debug output.
3) Without xinetd, in gdb
- Make sure xinetd is stopped (/etc/rc.d/init.d/xinetd stop).
- SANE_DEBUG_MUSTEK_PP=255 gdb saned
- At the gdb prompt: r -d128
- In another window:
scanimage -d net:localhost:mustek_pp:Mustek-1200CP > test.pnm
* Does scanimage hang?
* Does saned exit (ie., do you get the gdb prompt back)?
* If saned hangs, hit Ctrl-C in the gdb window and request a
stack trace: bt
* To restart saned: just enter "r" at the gdb prompt.
If a certain test doesn't give any problems, please repeat it a few
times to make sure it isn't just luck.
Best regards,
Eddy
---------------------------------------------------------------
Tiscali ADSL: 12 maanden aan 29,50 ?/maand! Snel Internet, en voor iedereen.
http://reg.tiscali.be/default.asp?lg=nl
From mattias.ellert at tsl.uu.se Wed Jan 7 16:09:11 2004
From: mattias.ellert at tsl.uu.se (Mattias Ellert)
Date: Wed, 07 Jan 2004 17:09:11 +0100
Subject: [sane-devel] TWAIN SANE Interface for Mac OS X version 0.3
Message-ID: <3FFC2F27.4000303@tsl.uu.se>
Release notes, version 0.3, 2004-01-05
* All mandatory TWAIN operations have been implemented.
* This version has been tested with the OmniPage application.
* New localization: Japanese (Thanks to RedGecko for the contribution).
* Fixed a bug where the TWAIN capability containers were not
dereferenced correctly.
* Fixed a bug where the TWAIN image info reported planar rather
than chunky byteorder.
* Black and white images are now sent inverted w.r.t. the previous
version because OmniPage wants it that way and GraphicConverter has an
option that can be set to invert black and white images from TWAIN
sources. With this option set in GraphicConverter the new version works
with both applications.
* Compiled on MacOS X 10.3.2 using the cross-compilation SDKs to
provide binary packages for older versions of MacOS X.
* A patch to the sane-backend package has been applied the work
around the broken implementation of pthread_cancel in MacOS X. With the
patch the test backend works again.
* A new libusb package is provided, since a number of new MacOS X
specific changes have been done in the cvs repository since the last
release.
* sane-backends 1.0.13 (patched), libusb 0.1.8 beta (2004-01-05)
and gettext 0.11.5.
* maciconv 1.0 (for the 10.1 and 10.2 builds only)
The packages are available on http://www.ellert.se/twain-sane/
Mattias Ellert
--
________________________________________________________________________
mattias.ellert at tsl.uu.se tel: +46 18 471 32 58
http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13
________________________________________________________________________
From jim.george at blueyonder.co.uk Wed Jan 7 21:39:06 2004
From: jim.george at blueyonder.co.uk (Jim George)
Date: Wed, 7 Jan 2004 21:39:06 -0000 (GMT)
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <3FFB29D70000062E@ocpmta2.freegates.net>
References: <1856.192.168.0.4.1073470839.squirrel@tassi.local>
<3FFB29D70000062E@ocpmta2.freegates.net>
Message-ID: <2581.192.168.0.4.1073511546.squirrel@tassi.local>
Hi Eddy,
see in-line below.
Jim
> Hi Jim,
>
> I think it's normal that saned exits after one scan. Normally, it's
> xinetd that restarts saned when a new request comes in.
> To restart saned in gdb, you only have to enter "r" at the prompt and
> then you can perform another scan.
>
> What surprises me is that, now, saned doesn't hang at the end.
> IIRC, when you started saned -d128 without gdb, it did hang.
>
> I'm getting confused. Could you repeat the following tests, such
> that I get a clear picture:
>
> 1) With xinetd
>
SuSE uses inetd not xinetd
> - Make sure xinetd is running (/etc/rc.d/init.d/xinetd restart). -
> scanimage -d net:localhost:mustek_pp:Mustek-1200CP > test.pnm
>
> * Does scanimage hang?
Yes
> * If it hangs and you kill scanimage, is saned still running?
> (ps aux | grep saned)
Yes
> * If saned still runs, just kill it.
>
Done
> 2) Without xinetd, no gdb
>
> - Make sure xinetd is stopped (/etc/rc.d/init.d/xinetd stop).
> - SANE_DEBUG_MUSTEK_PP=255 saned -d128
> - In another window:
> scanimage -d net:localhost:mustek_pp:Mustek-1200CP > test.pnm
>
> * Does scanimage hang?
It didn't even get started. I got the following error message:
scanimage: open of device net:localhost:mustek_pp:Mustek-1200CP failed:
Invalid argument
> * Does saned exit? (It should).
This was all the output from saned when it exited (it didn't hang).
[saned] main: starting debug mode (level 128)
[saned] main: trying to get port for service `sane' (getaddrinfo)
[saned] main: [0] socket () using IPv6
[saned] main: [0] setsockopt ()
[saned] main: [0] bind () to port 6566
[saned] main: [0] listen ()
[saned] main: [1] socket () using IPv4
[saned] main: [1] setsockopt ()
[saned] main: [1] bind () to port 6566
[saned] main: [1] bind failed: Address already in use
[saned] main: waiting for control connection
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.13 ready
[saned] check_host: access by remote host: ::1
[saned] check_host: remote host is IN6_LOOPBACK: access granted
[saned] init: access granted
[saned] init: access granted to jgeorge@::1
[saned] process_request: waiting for request
[saned] process_request: got request 2
[saned] process_request: access to resource `mustek_pp' granted
[sanei_debug] Setting debug level of mustek_pp to 255.
[mustek_pp] sane-mustek_pp, version 0.12-alpha. build for SANE 1.0.13
[mustek_pp] backend by Jochen Eisinger
[mustek_pp] cis_attach: couldn't attach to `parport0' (Invalid argument)
[mustek_pp] sane_open: unknown devicename ``Mustek-1200CP''
[saned] process_request: waiting for request
[saned] process_request: got request 10
[mustek_pp] sane_exit: all drivers unloaded
[saned] quit: exiting
> * If it hangs, please show the last few lines of debug output.
>
> 3) Without xinetd, in gdb
>
> - Make sure xinetd is stopped (/etc/rc.d/init.d/xinetd stop).
> - SANE_DEBUG_MUSTEK_PP=255 gdb saned
> - At the gdb prompt: r -d128
> - In another window:
> scanimage -d net:localhost:mustek_pp:Mustek-1200CP > test.pnm
>
> * Does scanimage hang?
No it exits immediately with the following error message:
scanimage: open of device net:localhost:mustek_pp:Mustek-1200CP failed:
Invalid argument
> * Does saned exit (ie., do you get the gdb prompt back)?
Yes it exited and I did get back to the gdb prompt. Here is the output.
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...
(gdb) r -d128
Starting program: /usr/sbin/saned -d128
[saned] main: starting debug mode (level 128)
[saned] main: trying to get port for service `sane' (getaddrinfo)
[saned] main: [0] socket () using IPv6
[saned] main: [0] setsockopt ()
[saned] main: [0] bind () to port 6566
[saned] main: [0] listen ()
[saned] main: [1] socket () using IPv4
[saned] main: [1] setsockopt ()
[saned] main: [1] bind () to port 6566
[saned] main: [1] bind failed: Address already in use
[saned] main: waiting for control connection
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.13 ready
[saned] check_host: access by remote host: ::1
[saned] check_host: remote host is IN6_LOOPBACK: access granted
[saned] init: access granted
[saned] init: access granted to jgeorge@::1
[saned] process_request: waiting for request
[saned] process_request: got request 2
[saned] process_request: access to resource `mustek_pp' granted
[sanei_debug] Setting debug level of mustek_pp to 255.
[mustek_pp] sane-mustek_pp, version 0.12-alpha. build for SANE 1.0.13
[mustek_pp] backend by Jochen Eisinger
[mustek_pp] cis_attach: couldn't attach to `parport0' (Invalid argument)
[mustek_pp] sane_open: unknown devicename ``Mustek-1200CP''
[saned] process_request: waiting for request
[saned] process_request: got request 10
[mustek_pp] sane_exit: all drivers unloaded
[saned] quit: exiting
Program exited normally.
(gdb)
> * If saned hangs, hit Ctrl-C in the gdb window and request a
> stack trace: bt
> * To restart saned: just enter "r" at the gdb prompt.
>
> If a certain test doesn't give any problems, please repeat it a few
> times to make sure it isn't just luck.
>
All three tests gave problems as you can see.
> Best regards,
>
> Eddy
>
>
> ---------------------------------------------------------------
> Tiscali ADSL: 12 maanden aan 29,50 ?/maand! Snel Internet, en voor
> iedereen. http://reg.tiscali.be/default.asp?lg=nl
From oliver.rauch at rauch-domain.de Wed Jan 7 23:07:04 2004
From: oliver.rauch at rauch-domain.de (Oliver Rauch)
Date: Thu, 8 Jan 2004 00:07:04 +0100
Subject: [sane-devel] UMAX Astra 2200 SU via USB
Message-ID: <200401080007.07136.oliver.rauch@rauch-domain.de>
Hello,
I just updated the umax backend (sane-umax) in the CVS.
Now it disables the quality calibration for the Astra 2200 SU via USB.
When the option is set then you can not do a final scan.
Please can someone with an Astra 2200 SU
a) connected via USB test the new version and confirm that
a1) the scanner does a final scan
a2) there is no option quality-calibration any more
b) connected via SCSI confirm that nothing has changed.
Oliver
--
http://www.xsane.org
http://www.mostang.com/sane
http://www.rauch-domain.de
mailto:Oliver.Rauch at Rauch-Domain.DE
From ecr959 at yahoo.com Thu Jan 8 00:16:35 2004
From: ecr959 at yahoo.com (Eddie Colon)
Date: Wed, 7 Jan 2004 16:16:35 -0800 (PST)
Subject: [sane-devel] Re: (sane-devel) info HP scanjet 4600 scanner
In-Reply-To: <20040107053536.20689.18784.Mailman@quantz.debian.org>
Message-ID: <20040108001635.98501.qmail@web41405.mail.yahoo.com>
Hello Henning
I'm glad you are including this scanner into your project list. I
would love to start the ball rolling and bang out a rough driver, but I
don't know any programming at all. Sorry. :-) But I'm not shy
with hardware, if you give me some instruction, tell me what to type at
the command prompt, I can try a few things for you.
About your other question, I haven't been able to scan at all.
Mandrake will detect the scanner, and say "it is not supported. Would
you like to install it manually ?" When I say yes, I choose a driver,
(usually another model from the HP list) then Mandrake says "not
supported" and stops right there. Like a loop.
If it helps this forum at all, I searched on the web for any info and
someone had written that this scanner is actually manufactured by
another company, and that's why the HP drivers won't work. I looked
all around and couldn't find another company name.
What do you suggest
=====
Eddie Colon
Bayamon, PR 00959
"The best things in life are not things"
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
From harri.jarvi at ajatus.org Thu Jan 8 09:45:03 2004
From: harri.jarvi at ajatus.org (=?iso-8859-1?Q?Harri_J=E4rvi?=)
Date: Thu, 8 Jan 2004 11:45:03 +0200
Subject: [sane-devel] Finnish translation for backends
Message-ID: <20040108094503.GA17111@kirja.lake>
Hi,
I'm starting to translate the backends .po file into Finnish.
I'm also interested in translating the xsane frontend. So I'll probably
do that too.
Yours,
Harri J?rvi
From adrianpj at users.sourceforge.net Thu Jan 8 11:13:08 2004
From: adrianpj at users.sourceforge.net (Adrian Perez Jorge)
Date: Thu, 08 Jan 2004 11:13:08 +0000
Subject: [sane-devel] Re: (sane-devel) info HP scanjet 4600 scanner
In-Reply-To: <20040108001635.98501.qmail@web41405.mail.yahoo.com>
References: <20040108001635.98501.qmail@web41405.mail.yahoo.com>
Message-ID: <3FFD3B44.40100@users.sourceforge.net>
Hi Eddie,
Some years ago I was in the same situation as you, but fortunatelly I
know about programming (more or less ;) I had to develop hp4200 backend
and I could obtain some results without too much documentation available
(later I could get much more docs and then improve my results). Some
guys here were able to do the same and develop a SANE backend for its
scanner.
There are some standard steps to solve the situation:
* find out what chipset is using your scanner:
- open the scanner and read big-chip numbers, or
- sometimes .inf files or file names from the window$ drivers
will help, or
- using a sniffer like USBSnoopy
(http://www.wingmanteam.com/usbsnoopy/) in a window$ machine to look at
the protocol and somebody in the list could identify if (usbsnoopy log
files can be real big; don't send that stuff to the list; give some URL;
log for few seconds, not the entire page).
* look for a backend that supports the chipset and use it
* if there is no backend, then develop a new backend using chipset
manufacturer information, the log files from snoopy, imagination,
reverse-engeneering (disassembling window$ drivers; there are PE
disassemblers for linux available) and help from the list.
That's my suggestion. Cheers,
Adrian P.
Eddie Colon wrote:
>Hello Henning
>
>I'm glad you are including this scanner into your project list. I
>would love to start the ball rolling and bang out a rough driver, but I
>don't know any programming at all. Sorry. :-) But I'm not shy
>with hardware, if you give me some instruction, tell me what to type at
>the command prompt, I can try a few things for you.
>
>About your other question, I haven't been able to scan at all.
>Mandrake will detect the scanner, and say "it is not supported. Would
>you like to install it manually ?" When I say yes, I choose a driver,
>(usually another model from the HP list) then Mandrake says "not
>supported" and stops right there. Like a loop.
>
>If it helps this forum at all, I searched on the web for any info and
>someone had written that this scanner is actually manufactured by
>another company, and that's why the HP drivers won't work. I looked
>all around and couldn't find another company name.
>
>What do you suggest
>
>=====
>Eddie Colon
>Bayamon, PR 00959
>
>"The best things in life are not things"
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
>http://hotjobs.sweepstakes.yahoo.com/signingbonus
>
>
>
From edg1 at tiscali.be Thu Jan 8 12:09:06 2004
From: edg1 at tiscali.be (edg1 at tiscali.be)
Date: Thu, 8 Jan 2004 13:09:06 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <2581.192.168.0.4.1073511546.squirrel@tassi.local>
Message-ID: <3FFB28C9000013A4@ocpmta1.freegates.net>
Jim George wrote:
> > 2) Without xinetd, no gdb
> > * Does scanimage hang?
> It didn't even get started. I got the following error message:
> scanimage: open of device net:localhost:mustek_pp:Mustek-1200CP failed:
> Invalid argument
Sorry, I forgot to mention this: you have to run saned as root.
Did you do that?
> [mustek_pp] cis_attach: couldn't attach to `parport0' (Invalid argument)
This is probably because saned didn't run as root.
> > 3) Without xinetd, in gdb
> > * Does scanimage hang?
> No it exits immediately with the following error message:
> scanimage: open of device net:localhost:mustek_pp:Mustek-1200CP failed:
> Invalid argument
Probably the same problem here: gdb has to be started as root.
Please try tests 2 and 3 again, running saned/gdb as root
(unless you already did that).
Sorry for not being clear the first time.
Eddy
---------------------------------------------------------------
Tiscali ADSL: 12 maanden aan 29,50 ?/maand! Snel Internet, en voor iedereen.
http://reg.tiscali.be/default.asp?lg=nl
From christopherlmarshall at yahoo.com Thu Jan 8 14:52:19 2004
From: christopherlmarshall at yahoo.com (Christopher Marshall)
Date: Thu, 8 Jan 2004 06:52:19 -0800 (PST)
Subject: [sane-devel] CanoScan LiDE 30 mysteriously stopped working on me in linux
Message-ID: <20040108145219.31849.qmail@web41507.mail.yahoo.com>
I had it working great through libusb on three different linux machines (all running slackware
9.0) for a week or so and now, all of a sudden, it either gives me black scans (vertical bands of
black and white), or it makes a hideous noise (as if it is trying to move the motor in the wrong
direction).
I wondered if perhaps I did something to get the scanner in a wierd state, so I did a scan on a
windows machine (using the software that came with the scanner) and it worked normally. Then I
put it back on the nearest linux machine and got the same hideous noise.
I'm crushed :-(
Any ideas?
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
From henning at meier-geinitz.de Thu Jan 8 16:54:02 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 8 Jan 2004 17:54:02 +0100
Subject: [sane-devel] Finnish translation for backends
In-Reply-To: <20040108094503.GA17111@kirja.lake>
References: <20040108094503.GA17111@kirja.lake>
Message-ID: <20040108165402.GA1191@meier-geinitz.de>
Hi,
On Thu, Jan 08, 2004 at 11:45:03AM +0200, Harri J?rvi wrote:
> I'm starting to translate the backends .po file into Finnish.
> I'm also interested in translating the xsane frontend. So I'll probably
> do that too.
That's cool!
Once you have finished the translation for sane-backends, please send
it to me for inclusion.
The translation for xsane should be sent to Oliver Rauch.
Bye,
Henning
From christopherlmarshall at yahoo.com Thu Jan 8 17:24:51 2004
From: christopherlmarshall at yahoo.com (Christopher Marshall)
Date: Thu, 8 Jan 2004 09:24:51 -0800 (PST)
Subject: [sane-devel] CanoScan LiDE 30 mystery solved
In-Reply-To: <20040108145219.31849.qmail@web41507.mail.yahoo.com>
Message-ID: <20040108172451.2266.qmail@web41508.mail.yahoo.com>
--- Christopher Marshall wrote:
> I had it working great through libusb on three different linux machines (all running slackware
> 9.0) for a week or so and now, all of a sudden, it either gives me black scans (vertical bands
> of
> black and white), or it makes a hideous noise (as if it is trying to move the motor in the wrong
> direction).
>
> I wondered if perhaps I did something to get the scanner in a wierd state, so I did a scan on a
> windows machine (using the software that came with the scanner) and it worked normally. Then I
> put it back on the nearest linux machine and got the same hideous noise.
>
> I'm crushed :-(
>
> Any ideas?
>
I figured it out. I was not copying my plustek.conf file to the proper place (in my case
/usr/local/etc/sane.d/plustek.conf). However, since I was working in the same directory I had
written the correct plustek.conf file in, scanimage was working there. When I would go to another
directory, it would stop working.
That's because the plustek backend looks in the current directory and if it finds a plustek.conf
file there, uses it instead of the one in /etc or /usr/local/etc. That really threw me for a
loop.
The man page for sane-plustek doesn't mention that it looks in the current directory for
plustek.conf.
Chris Marshall
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
From henning at meier-geinitz.de Thu Jan 8 17:51:08 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 8 Jan 2004 18:51:08 +0100
Subject: [sane-devel] CanoScan LiDE 30 mystery solved
In-Reply-To: <20040108172451.2266.qmail@web41508.mail.yahoo.com>
References: <20040108145219.31849.qmail@web41507.mail.yahoo.com> <20040108172451.2266.qmail@web41508.mail.yahoo.com>
Message-ID: <20040108175108.GC1191@meier-geinitz.de>
Hi,
On Thu, Jan 08, 2004 at 09:24:51AM -0800, Christopher Marshall wrote:
> That's because the plustek backend looks in the current directory and if it finds a plustek.conf
> file there, uses it instead of the one in /etc or /usr/local/etc. That really threw me for a
> loop.
All SANE configuration files are searched in the current directory
first.
> The man page for sane-plustek doesn't mention that it looks in the current directory for
> plustek.conf.
True. Most man pages contain something like this:
ENVIRONMENT
SANE_CONFIG_DIR
This environment variable specifies the list of
directories that may contain the configuration file.
Under UNIX, the directories are separated by a colon
(:'), under OS/2, they are separated by a semi-colon
(;'). If this variable is not set, the configuration
file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment
variable ends with the directory separator character,
then the default directories are searched after the
explicitly specified directories. For example, setting
SANE_CONFIG_DIR to "/tmp/config:" would result in
directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
I guess that should be added to sane-plustek.man. Also there is no
mention of "SANE_DEBUG_PLUSTEK".
Bye,
Henning
From ndaniels at mac.com Thu Jan 8 19:17:24 2004
From: ndaniels at mac.com (Noah Daniels)
Date: Thu, 08 Jan 2004 14:17:24 -0500
Subject: [sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
Message-ID: <13617772.1073589444350.JavaMail.ndaniels@mac.com>
Hi,
I'm still having the same problem with the plustek backend that several people have reported, even using this latest build of the various SANE packages.
Basically, sane-find-scanner finds the scanner, but scanimage -L does not. However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner DOES start working, and scans a partial low-res image before hanging. I know this behavior has been reported before, by Henrik Rintala.
I can provide a debug log if anyone's interested... I'd love to be able to get this working (printing to a Canoscan 650).
thanks!
--
Noah Daniels
ndaniels at mac.com
From henning at meier-geinitz.de Thu Jan 8 19:26:15 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 8 Jan 2004 20:26:15 +0100
Subject: [sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
In-Reply-To: <13617772.1073589444350.JavaMail.ndaniels@mac.com>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com>
Message-ID: <20040108192615.GG1191@meier-geinitz.de>
Hi,
On Thu, Jan 08, 2004 at 02:17:24PM -0500, Noah Daniels wrote:
> Basically, sane-find-scanner finds the scanner, but scanimage -L does
> not. However, if I set SANE_DEBUG_PLUSTEK to a high number, the
> scanner DOES start working, and scans a partial low-res image before
> hanging. I know this behavior has been reported before, by Henrik
> Rintala.
Wasn't that a bug in libusb, not in SANE? Has anyone contacted the
libusb maintainers?
Bye,
Henning
From gklaver at wanadoo.nl Thu Jan 8 21:14:21 2004
From: gklaver at wanadoo.nl (gerard klaver)
Date: Thu, 08 Jan 2004 20:14:21 -0100
Subject: [sane-devel] patch for include/sane/saneopts.h
Message-ID: <1073596460.3309.24.camel@gk-lex3>
Hello,
For the teco2 backend i use at the moment the white_level option for
manual changing the calibration value downloaded to the scanner.
To improve the calibration part i made a patch to add the white_value_r,
white_value_g and white_value_b to the saneopts.h file.
With this when for example the red calibration is not correct the user
can change this by changing the value of the white_level_r used as a
advanced option.
See the attached file for the patch.
Before adding the patch to the saneopts.h file in cvs i like to know
if there are any comments about it.
--
----------
m.vr.gr.
Gerard Klaver
-------------- next part --------------
A non-text attachment was scrubbed...
Name: saneopts-08122004.diff
Type: text/x-patch
Size: 1771 bytes
Desc: not available
URL:
From henning at meier-geinitz.de Thu Jan 8 21:12:03 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu, 8 Jan 2004 22:12:03 +0100
Subject: [sane-devel] patch for include/sane/saneopts.h
In-Reply-To: <1073596460.3309.24.camel@gk-lex3>
References: <1073596460.3309.24.camel@gk-lex3>
Message-ID: <20040108211203.GI1191@meier-geinitz.de>
Hi,
On Thu, Jan 08, 2004 at 08:14:21PM -0100, gerard klaver wrote:
> For the teco2 backend i use at the moment the white_level option for
> manual changing the calibration value downloaded to the scanner.
>
> To improve the calibration part i made a patch to add the white_value_r,
> white_value_g and white_value_b to the saneopts.h file.
>
> With this when for example the red calibration is not correct the user
> can change this by changing the value of the white_level_r used as a
> advanced option.
>
> See the attached file for the patch.
>
> Before adding the patch to the saneopts.h file in cvs i like to know
> if there are any comments about it.
Looks ok for me.
Is there any need for a per-color black level?
Bye,
Henning
From jim.george at blueyonder.co.uk Thu Jan 8 23:27:57 2004
From: jim.george at blueyonder.co.uk (Jim George)
Date: Thu, 8 Jan 2004 23:27:57 -0000 (GMT)
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <3FFB28C9000013A4@ocpmta1.freegates.net>
References: <2581.192.168.0.4.1073511546.squirrel@tassi.local>
<3FFB28C9000013A4@ocpmta1.freegates.net>
Message-ID: <1174.192.168.0.7.1073604477.squirrel@tassi.local>
Eddy,
Without inetd...
scanimage hung and when I ctrl-c'd out of scanimage I get the following
"scanimage: received signal 2
scanimage: trying to stop scanner "
saned did not quit. When I killed it, the saned window showed these last
few lines
"[saned] do_scan: read 0 bytes from scanner
[saned] do_scan: status = `End of file reached'
[saned] do_scan: statuscode `End of file reached' was added to buffer
[saned] do_scan: select_fd was closed --> EOF
[saned] do_scan: trying to write 9 bytes to client
[saned] do_scan: wrote 9 bytes to client
[saned] do_scan: done, status=End of file reached
[saned] process_request: waiting for request
[saned] process_request: got request 8
[saned] process_request: waiting for request
[saned] process_request: got request 3
[mustek_pp] sane_close: maybe waiting for lamp...
[mustek_pp] cis_close: resetting device.[mustek_pp] cis_reset_device:
resetting
device
[mustek_pp] cis_set_dpi_value: dpi: 300 -> value 0x20
[mustek_pp] cis_config_ccd: Skip count: 67 (x32)
[mustek_pp] cis_config_ccd: skipcount: 12 imagebytes: 0
[mustek_pp] cis_config_ccd: adjust skip: 0 bytecount: 3
[mustek_pp] cis_return_home: returning home; nowait: 1
[mustek_pp] cis_set_dpi_value: dpi: 300 -> value 0x20
[mustek_pp] cis_config_ccd: Skip count: 67 (x32)
[mustek_pp] cis_config_ccd: skipcount: 12 imagebytes: 0
[mustek_pp] cis_config_ccd: adjust skip: 0 bytecount: 3
Terminated"
and scanimage window showed
"scanimage: received signal 13
scanimage: aborting"
without inetd running but with gdb.........
scanimage hung and when I crtl-c'd out I get the following
"scanimage: received signal 2
scanimage: trying to stop scanner"
saned didn't quit. When I pressed ctrl-c in gdb I got
"[saned] do_scan: select_fd was closed --> EOF
[saned] do_scan: trying to write 9 bytes to client
[saned] do_scan: wrote 9 bytes to client
[saned] do_scan: done, status=End of file reached
[saned] process_request: waiting for request
[saned] process_request: got request 8
[saned] process_request: waiting for request
[saned] process_request: got request 3
[mustek_pp] sane_close: maybe waiting for lamp...
[mustek_pp] cis_close: resetting device.[mustek_pp] cis_reset_device:
resetting
device
[mustek_pp] cis_set_dpi_value: dpi: 300 -> value 0x20
[mustek_pp] cis_config_ccd: Skip count: 67 (x32)
[mustek_pp] cis_config_ccd: skipcount: 12 imagebytes: 0
[mustek_pp] cis_config_ccd: adjust skip: 0 bytecount: 3
[mustek_pp] cis_return_home: returning home; nowait: 1
[mustek_pp] cis_set_dpi_value: dpi: 300 -> value 0x20
[mustek_pp] cis_config_ccd: Skip count: 67 (x32)
[mustek_pp] cis_config_ccd: skipcount: 12 imagebytes: 0
[mustek_pp] cis_config_ccd: adjust skip: 0 bytecount: 3
Program received signal SIGINT, Interrupt.
0x4027786d in sanei_debug_sanei_pa4s2_call ()
from /usr/lib/sane/libsane-mustek_pp.so.1 "
I then did 'bt' and got
"#0 0x4027786d in sanei_debug_sanei_pa4s2_call ()
from /usr/lib/sane/libsane-mustek_pp.so.1
#1 0x40279090 in sanei_pa4s2_readbyte ()
from /usr/lib/sane/libsane-mustek_pp.so.1
#2 0x4026ff0e in Mustek_PP_1015_wait_bit ()
from /usr/lib/sane/libsane-mustek_pp.so.1
#3 0x4027219c in cis_motor_control ()
from /usr/lib/sane/libsane-mustek_pp.so.1
#4 0x402721fb in cis_return_home () from
/usr/lib/sane/libsane-mustek_pp.so.1
#5 0x40272d0c in cis_drv_close () from /usr/lib/sane/libsane-mustek_pp.so.1
#6 0x4026ef62 in sane_mustek_pp_close ()
from /usr/lib/sane/libsane-mustek_pp.so.1
#7 0x4003bd31 in sane_dll_close () from /usr/lib/libsane.so.1
#8 0x08049d1d in close_handle ()
#9 0x0804b6d0 in process_request ()
#10 0x0804bc92 in main ()
#11 0x401594c2 in __libc_start_main () from /lib/i686/libc.so.6"
I hope this helps.
Jim
From sampln at sbcglobal.net Fri Jan 9 05:43:24 2004
From: sampln at sbcglobal.net (Lincoln Peters)
Date: Thu, 08 Jan 2004 21:43:24 -0800
Subject: [sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
Message-ID: <1073627002.30821.10634.camel@odysseus>
I had heard that my EPSON Perfection 2400 scanner was supported by
SANE. I plugged it into the USB port on a computer running Red Hat
Linux 9.0, installed SANE from source, and then ran the
"sane-find-scanner" program. I got the following output:
# sane-find-scanner
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".
found USB scanner (vendor=0x04b8, product=0x011b) at /dev/usb/scanner0
found USB scanner (vendor=0x04b8 [EPSON], product=0x011b [EPSON Scanner]) at libusb:001:002
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Scanners connected to the parallel port or other proprietary ports can't be
# detected by this program.
As the "sane-find-scanner" program suggested, I ran "scanimage -L", and
got the following:
# scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
As the HOWTO suggested, I tried it again:
# scanimage -L
device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner
I know that my scanner is NOT an Epson GT-9300! I seem to be able to
scan pictures even when the scanner is incorrectly identified, but they
come out as line art (perhaps this is because I haven't yet looked up
the EPSON-specific command line options).
I have commented out every driver listed in /etc/sane.d/dll.conf
*except* the "epson" driver, to minimize the chance of SANE using the
wrong driver. Furthermore, the /etc/sane.d/epson.conf file has every
line commented out except for:
usb /dev/usb/scanner0
I also double-checked that libusb is installed. I don't have any other
USB devices connected to the computer, but I am reasonably sure that the
USB interface itself is properly configured (I wouldn't expect a
misconfigured USB interface to be able to report that I have an EPSON
scanner). I am also sure that the problem does not lie in the
permissions (I'm using it while logged in as root).
I have also found that, for some reason, if I leave it and come back a
few minutes later, SANE will fail to find my scanner. The
"sane-find-scanner" command works as before, but "scanimage -L" fails to
detect a scanner no matter how many times I try it. If I try to scan
the image using the command:
# scanimage -d epson:/dev/usb/scanner0 --format tiff > new.tiff
I get the following error:
scanimage: open of device /dev/usb/scanner0 failed: Invalid argument
According to both the website and the mailing list archives, the EPSON
Perfection 2400 PHOTO scanner works with SANE, but I cannot figure out
how. What am I doing wrong?
--
Lincoln Peters
From gene.heskett at verizon.net Fri Jan 9 05:58:49 2004
From: gene.heskett at verizon.net (Gene Heskett)
Date: Fri, 9 Jan 2004 00:58:49 -0500
Subject: [sane-devel] 2.6.1-rc3 lost scanner, gnomeradio's gui segfaults
Message-ID: <200401090058.49513.gene.heskett@verizon.net>
Greets everyone;
I'm setup to use libusb here, rahter than drivers/usb/scanner in the
kernel config.
Up to 2.6.1-rc1-mm1 and possibly a little later, my scanner worked
just fine. But now on 2.6.1-rc3 its disappeared.
I also have everything in the i2c category except i2c-dev (builtin) as
modules trying to find some combination that will let sensors run.
I had all that compiled in the last time it worked.
Also, gnomeradio just segfaulted on startup and left the radio on when
it did. That also worked previously.
Ideas?
--
Cheers, Gene
AMD K6-III at 500mhz 320M
Athlon1600XP at 1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
From olaf at epkowa.co.jp Fri Jan 9 06:09:52 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Fri, 09 Jan 2004 15:09:52 +0900
Subject: [sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
In-Reply-To: <1073627002.30821.10634.camel@odysseus> (Lincoln Peters's
message of "Thu, 08 Jan 2004 21:43:24 -0800")
References: <1073627002.30821.10634.camel@odysseus>
Message-ID: <87y8shejpr.fsf@zen.epkowa.co.jp>
Lincoln Peters writes:
> I had heard that my EPSON Perfection 2400 scanner was supported by
> SANE.
Rest assured, it is.
> # scanimage -L
> device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner
>
> I know that my scanner is NOT an Epson GT-9300!
You may know that, but your scanner doesn't ;-)
The problem is that EPSON decided to market the same scanner under a
different name abroad (here is Japan it's a GT-9300), but didn't
bother to change the name returned by the scanner. The epson (and
epkowa) backend(s) use the name returned by the scanner, not what is
printed on the label (for rather obvious reasons).
> [snip]
Hope this helps,
--
Olaf Meeuwissen EPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
From sampln at sbcglobal.net Fri Jan 9 06:30:40 2004
From: sampln at sbcglobal.net (Lincoln Peters)
Date: Thu, 08 Jan 2004 22:30:40 -0800
Subject: [sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
In-Reply-To: <87y8shejpr.fsf@zen.epkowa.co.jp>
References: <1073627002.30821.10634.camel@odysseus>
<87y8shejpr.fsf@zen.epkowa.co.jp>
Message-ID: <1073629832.30821.10880.camel@odysseus>
On Thu, 2004-01-08 at 22:09, Olaf Meeuwissen wrote:
> > # scanimage -L
> > device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner
> >
> > I know that my scanner is NOT an Epson GT-9300!
>
> You may know that, but your scanner doesn't ;-)
> The problem is that EPSON decided to market the same scanner under a
> different name abroad (here is Japan it's a GT-9300), but didn't
> bother to change the name returned by the scanner. The epson (and
> epkowa) backend(s) use the name returned by the scanner, not what is
> printed on the label (for rather obvious reasons).
That is reassuring. However, having made one (low-res) scan,
"scanimage" now fails to detect the scanner. I don't know what I might
have done to cause it to stop working.
--
Lincoln Peters
From mattias.ellert at tsl.uu.se Fri Jan 9 08:31:42 2004
From: mattias.ellert at tsl.uu.se (Mattias Ellert)
Date: Fri, 09 Jan 2004 09:31:42 +0100
Subject: [sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
In-Reply-To: <13617772.1073589444350.JavaMail.ndaniels@mac.com>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com>
Message-ID: <3FFE66EE.2020503@tsl.uu.se>
Noah Daniels wrote:
> Hi,
>
> I'm still having the same problem with the plustek backend that several people have reported, even using this latest build of the various SANE packages.
>
> Basically, sane-find-scanner finds the scanner, but scanimage -L does not. However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner DOES start working, and scans a partial low-res image before hanging. I know this behavior has been reported before, by Henrik Rintala.
>
> I can provide a debug log if anyone's interested... I'd love to be able to get this working (printing to a Canoscan 650).
>
> thanks!
>
> --
> Noah Daniels
Using the latest version of libusb from CVS (or the binary packages from
2004-01-05) has been reported to fix the problem that scanimage -L does
not see the scanner unless the DEBUG environment is used.
The following gdb log of the state of scanimage at the time it freezes
after a scan was provided by a user having a Canon N670U scanner that
uses the Plustek backend on MacOS X.
To me it looks like the reader process has finished and is waiting to be
killed, but the main process is still trying to read from it.
Note that the patch in the bug report
https://alioth.debian.org/tracker/index.php?func=detail&aid=300434&group_id=1308&atid=410366
has been applied here, in order to avoid calling pthread_cancel which is
broken on MacOS X.
Mattias
--
________________________________________________________________________
mattias.ellert at tsl.uu.se tel: +46 18 471 32 58
http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13
________________________________________________________________________
-------------- next part --------------
(gdb) info threads
2 process 799 thread 0x1c43 0x90017048 in semaphore_wait_signal_trap ()
* 1 process 799 thread 0x307 0x9000ebc4 in read ()
(gdb) thread 1
[Switching to thread 1 (process 799 thread 0x307)]
#0 0x9000ebc4 in read ()
(gdb) backtrace
#0 0x9000ebc4 in read ()
#1 0x0021ab44 in sane_plustek_read (handle=0xdd000, data=0xbfff7820 "xN,~K$fO*qT)f=$SR\"gV,", '?' , "???\215uM\\E,jF4\237~e", '?' ..., max_length=32768, length=0xbffff860) at plustek.c:2071
#2 0x00004600 in scan_it () at scanimage.c:1142
#3 0x00006078 in main (argc=45792, argv=0xa000104c) at scanimage.c:1975
(gdb) thread 2
[Switching to thread 2 (process 799 thread 0x1c43)]
#0 0x90017048 in semaphore_wait_signal_trap ()
(gdb) backtrace
#0 0x90017048 in semaphore_wait_signal_trap ()
#1 0x9000e890 in _pthread_cond_wait ()
#2 0x0021d91c in local_thread (arg=0x25bd1c) at sanei_thread.c:221
#3 0x900247e8 in _pthread_body ()
(gdb)
From gerhard at gjaeger.de Fri Jan 9 08:44:20 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Fri, 9 Jan 2004 09:44:20 +0100
Subject: [sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
In-Reply-To: <13617772.1073589444350.JavaMail.ndaniels@mac.com>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com>
Message-ID: <200401090944.20977.gerhard@gjaeger.de>
Hi,
On Donnerstag, 8. Januar 2004 20:17, Noah Daniels wrote:
[SNIPSNAP]
> Basically, sane-find-scanner finds the scanner, but scanimage -L does not.
> However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner DOES
> start working, and scans a partial low-res image before hanging. I know
> this behavior has been reported before, by Henrik Rintala.
>
> I can provide a debug log if anyone's interested... I'd love to be able to
> get this working (printing to a Canoscan 650).
you can send me these logs, but I'm pretty sure, that the backend itself is
not the problem. Probably we can find some workaround, when doing some
delays on the correct positions - but in the end, as you already noted,
the scanner will hang during the scan...
The best solution will be to contact the libusb guys and fix the problems,
where they come from...
Ciao,
Gerhard
From gerhard at gjaeger.de Fri Jan 9 08:48:40 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Fri, 9 Jan 2004 09:48:40 +0100
Subject: [sane-devel] CanoScan LiDE 30 mystery solved
In-Reply-To: <20040108175108.GC1191@meier-geinitz.de>
References: <20040108145219.31849.qmail@web41507.mail.yahoo.com> <20040108172451.2266.qmail@web41508.mail.yahoo.com> <20040108175108.GC1191@meier-geinitz.de>
Message-ID: <200401090948.40198.gerhard@gjaeger.de>
On Donnerstag, 8. Januar 2004 18:51, Henning Meier-Geinitz wrote:
[SNIPSNAP]
> True. Most man pages contain something like this:
Okay, okay, I got it ;-)))
The next version will contain this part.
>
> ENVIRONMENT
> SANE_CONFIG_DIR
> This environment variable specifies the list of
> directories that may contain the configuration file.
> Under UNIX, the directories are separated by a colon
> (:'), under OS/2, they are separated by a semi-colon
> (;'). If this variable is not set, the configuration
> file is searched in two default directories: first, the
> current working directory (".") and then in
> /usr/local/etc/sane.d. If the value of the environment
> variable ends with the directory separator character,
> then the default directories are searched after the
> explicitly specified directories. For example, setting
> SANE_CONFIG_DIR to "/tmp/config:" would result in
> directories "tmp/config", ".", and
> "/usr/local/etc/sane.d" being searched (in this order).
>
> I guess that should be added to sane-plustek.man. Also there is no
> mention of "SANE_DEBUG_PLUSTEK".
This in fact is not true, have a look at "CONTACT AND BUG-REPORTS"...
Ciao,
Gerhard
From gerhard at gjaeger.de Fri Jan 9 08:57:50 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Fri, 9 Jan 2004 09:57:50 +0100
Subject: [sane-devel] Re: TWAIN SANE Interface for Mac OS X version 0.3
In-Reply-To: <3FFE66EE.2020503@tsl.uu.se>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com> <3FFE66EE.2020503@tsl.uu.se>
Message-ID: <200401090957.50504.gerhard@gjaeger.de>
Hi,
I already got this report and check it here on my box...
Ciao,
Gerhard
On Freitag, 9. Januar 2004 09:31, Mattias Ellert wrote:
> Noah Daniels wrote:
> > Hi,
> >
> > I'm still having the same problem with the plustek backend that several
> > people have reported, even using this latest build of the various SANE
> > packages.
> >
> > Basically, sane-find-scanner finds the scanner, but scanimage -L does
> > not. However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner
> > DOES start working, and scans a partial low-res image before hanging. I
> > know this behavior has been reported before, by Henrik Rintala.
> >
> > I can provide a debug log if anyone's interested... I'd love to be able
> > to get this working (printing to a Canoscan 650).
> >
> > thanks!
> >
> > --
> > Noah Daniels
>
> Using the latest version of libusb from CVS (or the binary packages from
> 2004-01-05) has been reported to fix the problem that scanimage -L does
> not see the scanner unless the DEBUG environment is used.
>
> The following gdb log of the state of scanimage at the time it freezes
> after a scan was provided by a user having a Canon N670U scanner that
> uses the Plustek backend on MacOS X.
>
> To me it looks like the reader process has finished and is waiting to be
> killed, but the main process is still trying to read from it.
>
> Note that the patch in the bug report
> https://alioth.debian.org/tracker/index.php?func=detail&aid=300434&group_id
>=1308&atid=410366
>
> has been applied here, in order to avoid calling pthread_cancel which is
> broken on MacOS X.
>
> Mattias
From khk at khk.net Fri Jan 9 12:17:53 2004
From: khk at khk.net (khk at khk.net)
Date: Fri, 9 Jan 2004 07:17:53 -0500 (EST)
Subject: [sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
In-Reply-To: <1073627002.30821.10634.camel@odysseus>
References: <1073627002.30821.10634.camel@odysseus>
Message-ID: <39925.198.176.225.25.1073650673.squirrel@home.khk.net>
The scanner is fully supported with Sane. It is also correctly identified:
The GT-9300 is the internal name of the device. The name "Perfection 2400"
is not stored anywhere in the firmware, it's just printed on the outside.
The Sane backend only sees the internal name, and this is what it reports.
If you change the scanning mode on the commmand line, you will be able
to scan both grayscale and color in addition to the black&white (or
lineart mode).
Is it possible that RH9 unloads the driver if you are not scanning for
a while and has a problem reloading it? This is very likely not a Sane
problem, but a problem with your USB subsystem. I'm not familiar with
RH9, so I'm not in a position to comment on that. Sorry.
Karl Heinz
> I had heard that my EPSON Perfection 2400 scanner was supported by
> SANE. I plugged it into the USB port on a computer running Red Hat
> Linux 9.0, installed SANE from source, and then ran the
> "sane-find-scanner" program. I got the following output:
>
> # sane-find-scanner
>
> # No SCSI scanners found. If you expected something different, make sure
> that
> # you have loaded a SCSI driver for your SCSI adapter.
> # Also you need support for SCSI Generic (sg) in your operating system.
> # If using Linux, try "modprobe sg".
>
> found USB scanner (vendor=0x04b8, product=0x011b) at /dev/usb/scanner0
> found USB scanner (vendor=0x04b8 [EPSON], product=0x011b [EPSON Scanner])
> at libusb:001:002
> # Your USB scanner was (probably) detected. It may or may not be
> supported by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> # Scanners connected to the parallel port or other proprietary ports
> can't be
> # detected by this program.
>
> As the "sane-find-scanner" program suggested, I ran "scanimage -L", and
> got the following:
>
> # scanimage -L
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
>
> As the HOWTO suggested, I tried it again:
>
> # scanimage -L
> device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner
>
> I know that my scanner is NOT an Epson GT-9300! I seem to be able to
> scan pictures even when the scanner is incorrectly identified, but they
> come out as line art (perhaps this is because I haven't yet looked up
> the EPSON-specific command line options).
>
> I have commented out every driver listed in /etc/sane.d/dll.conf
> *except* the "epson" driver, to minimize the chance of SANE using the
> wrong driver. Furthermore, the /etc/sane.d/epson.conf file has every
> line commented out except for:
>
> usb /dev/usb/scanner0
>
> I also double-checked that libusb is installed. I don't have any other
> USB devices connected to the computer, but I am reasonably sure that the
> USB interface itself is properly configured (I wouldn't expect a
> misconfigured USB interface to be able to report that I have an EPSON
> scanner). I am also sure that the problem does not lie in the
> permissions (I'm using it while logged in as root).
>
>
> I have also found that, for some reason, if I leave it and come back a
> few minutes later, SANE will fail to find my scanner. The
> "sane-find-scanner" command works as before, but "scanimage -L" fails to
> detect a scanner no matter how many times I try it. If I try to scan
> the image using the command:
>
> # scanimage -d epson:/dev/usb/scanner0 --format tiff > new.tiff
>
> I get the following error:
>
> scanimage: open of device /dev/usb/scanner0 failed: Invalid argument
>
>
> According to both the website and the mailing list archives, the EPSON
> Perfection 2400 PHOTO scanner works with SANE, but I cannot figure out
> how. What am I doing wrong?
>
> --
> Lincoln Peters
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
>
From md0josch at mdstud.chalmers.se Fri Jan 9 12:38:57 2004
From: md0josch at mdstud.chalmers.se (Christian Josefsson)
Date: Fri, 9 Jan 2004 13:38:57 +0100
Subject: [sane-devel] HP Scanjet 3670...
Message-ID: <20040109123857.GA27118@sugarpie>
Hi!
I'm a Computer Science student, which has come to the point of writing
my Master Thesis. Since I'm interested in systems programming and Linux
and in the posession of a unsupported scanner, namely hp scanjet 3670,
I've concidered writing a driver for that scanner as part of my Thesis
(the thesis would also contain other investigations ...).
But since there appears to be some activity going on in writing a driver
for the scanjet 3670 I would like to hear, how far you have come, and
if it would be feasible for one more person trying to write the driver...
However in case the driver is already close to finished and/or there already
are enough developers aiming at the same driver, I'd stop pursuing this
idea and instead find myself another subject for my Thesis.
Kind regards
// Christian
-------------------------------------------------------------------------------
Christian Josefsson mail=md0josch@[mdstud,medic,cs,math,md,etek].chalmers.se
God made machine language; all the rest is the work of man.
-------------------------------------------------------------------------------
From edg1 at tiscali.be Fri Jan 9 14:57:53 2004
From: edg1 at tiscali.be (edg1 at tiscali.be)
Date: Fri, 9 Jan 2004 15:57:53 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <1174.192.168.0.7.1073604477.squirrel@tassi.local>
Message-ID: <3FFB28C9000021E0@ocpmta1.freegates.net>
Jim George wrote:
> without inetd running but with gdb.........
>
> scanimage hung and when I crtl-c'd out I get the following
> "scanimage: received signal 2
> scanimage: trying to stop scanner"
>
> saned didn't quit. When I pressed ctrl-c in gdb I got
>
> [...]
>
> Program received signal SIGINT, Interrupt.
> 0x4027786d in sanei_debug_sanei_pa4s2_call ()
> from /usr/lib/sane/libsane-mustek_pp.so.1 "
>
> I then did 'bt' and got
> "#0 0x4027786d in sanei_debug_sanei_pa4s2_call ()
> from /usr/lib/sane/libsane-mustek_pp.so.1
> #1 0x4079090 in sanei_pa4s2_readbyte ()
> from /usr/lib/sane/libsane-mustek_pp.so.1
> #2 0x4026ff0e in Mustek_PP_1015_wait_bit ()
> from /usr/lib/sane/libsane-mustek_pp.so.1
> #3 0x4027219c in cis_motor_control ()
> from /usr/lib/sane/libsane-mustek_pp.so.1
> #4 0x402721fb in cis_return_home () from /usr/lib/sane/libsane-mustek_pp.so.1
> #5 0x40272d0c in cis_drv_close () from /usr/lib/sane/libsane-mustek_pp.so.1
> #6 0x4026ef62 in sane_mustek_pp_close () from /usr/lib/sane/libsane-mustek_pp.so.1
> #7 0x4003bd31 in sane_dll_close () from /usr/lib/libsane.so.1
> #8 0x08049d1d in close_handle ()
> #9 0x0804b6d0 in process_request ()
> #10 0x0804bc92 in main ()
> #11 0x401594c2 in __libc_start_main () from /lib/i686/libc.so.6"
>
> I hope this helps.
Hi Jim,
now we are getting somewhere.
It looks like the driver is waiting for the scanner motor to stabilize,
but it waits forever, either because it doesn't stabilize, or because
the communication with the scanner is somehow messed up.
Do you have libieee1284 installed? If so, what version is it?
It would be useful to also see the debug output of sanei_pa4s2.
I know you are short of disk space, so I won't ask you to collect
all output. Just let it scroll off the screen. I'm only interested
in the last few tens of lines or so (as long as the last few lines
of mustek_pp output are included):
- stop inetd
- as root:
SANE_DEBUG_MUSTEK_PP=128 SANE_DEBUG_SANEI_PA4S2=255 saned -d128
- in another window:
scanimage -d net:localhost:mustek_pp:Mustek-1200CP > /dev/null
Best regards,
Eddy
---------------------------------------------------------------
Tiscali ADSL: 12 maanden aan 29,50 ?/maand! Snel Internet, en voor iedereen.
http://reg.tiscali.be/default.asp?lg=nl
From henning at meier-geinitz.de Fri Jan 9 17:34:53 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 9 Jan 2004 18:34:53 +0100
Subject: [sane-devel] CanoScan LiDE 30 mystery solved
In-Reply-To: <200401090948.40198.gerhard@gjaeger.de>
References: <20040108145219.31849.qmail@web41507.mail.yahoo.com> <20040108172451.2266.qmail@web41508.mail.yahoo.com> <20040108175108.GC1191@meier-geinitz.de> <200401090948.40198.gerhard@gjaeger.de>
Message-ID: <20040109173453.GB1416@meier-geinitz.de>
Hi,
On Fri, Jan 09, 2004 at 09:48:40AM +0100, Jaeger, Gerhard wrote:
> > I guess that should be added to sane-plustek.man. Also there is no
> > mention of "SANE_DEBUG_PLUSTEK".
>
> This in fact is not true, have a look at "CONTACT AND BUG-REPORTS"...
Ah, ok. I just looked at the environment section. :-)
Bye,
Henning
From henning at meier-geinitz.de Fri Jan 9 18:03:33 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Fri, 9 Jan 2004 19:03:33 +0100
Subject: [sane-devel] HP Scanjet 3670...
In-Reply-To: <20040109123857.GA27118@sugarpie>
References: <20040109123857.GA27118@sugarpie>
Message-ID: <20040109180333.GC1416@meier-geinitz.de>
Hi,
On Fri, Jan 09, 2004 at 01:38:57PM +0100, Christian Josefsson wrote:
> I'm a Computer Science student, which has come to the point of writing
> my Master Thesis. Since I'm interested in systems programming and Linux
> and in the posession of a unsupported scanner, namely hp scanjet 3670,
> I've concidered writing a driver for that scanner as part of my Thesis
> (the thesis would also contain other investigations ...).
> But since there appears to be some activity going on in writing a driver
> for the scanjet 3670 I would like to hear, how far you have come, and
> if it would be feasible for one more person trying to write the driver...
I haven't heard from mancio_and at libero.it after his initial posting
(http://lists.alioth.debian.org/pipermail/sane-devel/2003-November/009360.html).
If he doesn't answer on this list, try to contact him directly.
> However in case the driver is already close to finished and/or there already
> are enough developers aiming at the same driver, I'd stop pursuing this
> idea and instead find myself another subject for my Thesis.
At least I don't remember anyone posted a link to code or a website
for that scanner. If that doesn't happen some weeks after the first
announcement, this usually menas that the project is dead. But I like
to be surprised otherwise :-)
Anyway, even if someone worked on this project, you could still try to
write a backend for any of the other unsupported scanners. The list is
so long, you shouldn't have trouble to find one :-)
Bye,
Henning
From jim.george at blueyonder.co.uk Sat Jan 10 00:03:17 2004
From: jim.george at blueyonder.co.uk (Jim George)
Date: Sat, 10 Jan 2004 00:03:17 -0000 (GMT)
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
Message-ID: <2750.192.168.0.7.1073692997.squirrel@tassi.local>
> Hi Jim,
>
> now we are getting somewhere.
> It looks like the driver is waiting for the scanner motor to stabilize,
but it waits forever, either because it doesn't stabilize, or because the
communication with the scanner is somehow messed up.
>
> Do you have libieee1284 installed? If so, what version is it?
>
> It would be useful to also see the debug output of sanei_pa4s2.
> I know you are short of disk space, so I won't ask you to collect all
output. Just let it scroll off the screen. I'm only interested in the
last few tens of lines or so (as long as the last few lines of mustek_pp
output are included):
>
> - stop inetd
> - as root:
> SANE_DEBUG_MUSTEK_PP=128 SANE_DEBUG_SANEI_PA4S2=255 saned -d128
> - in another window:
> scanimage -d net:localhost:mustek_pp:Mustek-1200CP > /dev/null
>
> Best regards,
>
> Eddy
Eddy,
I am running libieee1284-0.2.8-0.pm.0
As root I stopped inetd, and executed the above commands. The first time
I did this I got the contents of first.txt.
So I rebooted the server and tried again but didn't appear to get any
output from scanimage (I didn't use > /dev/null but > test.pnm which
didn't appear to grow at all).
So I ran SANE_DEBUG_MUSTEK_PP=128 SANE_DEBUG_SANEI_PA4S2=255 saned -d128
and scanimage -d net:localhost:mustek_pp:Mustek-1200CP -T but there
appeared to be no output from the scanimage -T.
So I then ran saned -d128 and scanimage -d
net:localhost:mustek_pp:Mustek-1200CP and got the output found in the
attachment sanedonly.txt
I then tried again with the original commands you requested but, in the
end I lost my courage because it didn't appear to be doing anything still
so I stopped.
Finally I tried ANE_DEBUG_MUSTEK_PP=128 SANE_DEBUG_SANEI_PA4S2=255
scanimage -d mustek_pp:Mustek-1200CP > test.pnm but again there is was no
file generated so I decided to stop the output for fear of breaking my
scanner.
Hope this helps.
Jim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: first.LOG
Type: application/octet-stream
Size: 5384 bytes
Desc: not available
URL:
-------------- next part --------------
saned -d128
[saned] main: starting debug mode (level 128)
[saned] main: trying to get port for service `sane' (getaddrinfo)
[saned] main: [0] socket () using IPv6
[saned] main: [0] setsockopt ()
[saned] main: [0] bind () to port 6566
[saned] main: [0] listen ()
[saned] main: [1] socket () using IPv4
[saned] main: [1] setsockopt ()
[saned] main: [1] bind () to port 6566
[saned] main: [1] bind failed: Address already in use
[saned] main: waiting for control connection
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.13 ready
[saned] check_host: access by remote host: ::1
[saned] check_host: remote host is IN6_LOOPBACK: access granted
[saned] init: access granted
[saned] init: access granted to root@::1
[saned] process_request: waiting for request
[saned] process_request: got request 2
[saned] process_request: access to resource `mustek_pp' granted
[sanei_debug] Setting debug level of mustek_pp to 2.
[saned] process_request: waiting for request
[saned] process_request: got request 4
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 7
[saned] start_scan: using port 1088 for data
[saned] process_request: waiting for data connection
[saned] process_request: access to data port from ::1
[saned] do_scan: start
[saned] do_scan: processing RPC request on fd 4
[saned] process_request: waiting for request
[saned] process_request: got request 6
[mustek_pp] sane_get_parameters: can't set parameters while scanning
[saned] do_scan: trying to read 8188 bytes from scanner
[saned] do_scan: read 4096 bytes from scanner
[saned] do_scan: trying to write 4100 bytes to client
[saned] do_scan: wrote 4100 bytes to client
[saned] do_scan: trying to read 4088 bytes from scanner
[saned] do_scan: read 4088 bytes from scanner
[saned] do_scan: trying to write 4092 bytes to client
[saned] do_scan: wrote 4092 bytes to client
[saned] do_scan: trying to read 8188 bytes from scanner
[saned] do_scan: read 8 bytes from scanner
[saned] do_scan: processing RPC request on fd 4
[saned] process_request: waiting for request
[saned] process_request: got request 8
[saned] do_scan: done, status=Success
[saned] process_request: waiting for request
[saned] process_request: got request 3
[saned] process_request: waiting for request
[saned] process_request: got request 10
[saned] quit: exiting
tassi:~ #
From olaf at epkowa.co.jp Sat Jan 10 00:31:52 2004
From: olaf at epkowa.co.jp (Olaf Meeuwissen)
Date: Sat, 10 Jan 2004 09:31:52 +0900
Subject: [sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
In-Reply-To: <1073629832.30821.10880.camel@odysseus> (Lincoln Peters's
message of "Thu, 08 Jan 2004 22:30:40 -0800")
References: <1073627002.30821.10634.camel@odysseus>
<87y8shejpr.fsf@zen.epkowa.co.jp>
<1073629832.30821.10880.camel@odysseus>
Message-ID: <87u134od8n.fsf@zen.epkowa.co.jp>
Lincoln Peters writes:
> On Thu, 2004-01-08 at 22:09, Olaf Meeuwissen wrote:
>> > # scanimage -L
>> > device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner
>> >
>> > I know that my scanner is NOT an Epson GT-9300!
>>
>> You may know that, but your scanner doesn't ;-)
>> The problem is that EPSON decided to market the same scanner under a
>> different name abroad (here is Japan it's a GT-9300), but didn't
>> bother to change the name returned by the scanner. The epson (and
>> epkowa) backend(s) use the name returned by the scanner, not what is
>> printed on the label (for rather obvious reasons).
>
> That is reassuring. However, having made one (low-res) scan,
> "scanimage" now fails to detect the scanner. I don't know what I might
> have done to cause it to stop working.
Neither do I, but you might try replugging the scanner and making sure
that the kernel hasn't loaded the scanner module (which forces the use
of libusb).
Check with '/sbin/lsmod | grep scanner'. You can use 'rmmod scanner'
to remove the module.
Hope this helps,
--
Olaf Meeuwissen EPSON KOWA Corporation, ECS
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
From khk at khk.net Sat Jan 10 00:49:14 2004
From: khk at khk.net (Karl Heinz Kremer)
Date: Fri, 9 Jan 2004 19:49:14 -0500
Subject: [sane-devel] Cannot set up an EPSON Perfection 2400 PHOTO
In-Reply-To: <87u134od8n.fsf@zen.epkowa.co.jp>
References: <1073627002.30821.10634.camel@odysseus> <87y8shejpr.fsf@zen.epkowa.co.jp> <1073629832.30821.10880.camel@odysseus> <87u134od8n.fsf@zen.epkowa.co.jp>
Message-ID:
To permanently disable the kernel scanner driver, you probably have to
modify the hotplug configuration so that the module is no longer
automatically loaded. One crude way of doing this is to rename
the scanner.o file.
Karl Heinz
On Jan 9, 2004, at 7:31 PM, Olaf Meeuwissen wrote:
> Lincoln Peters writes:
>
>> On Thu, 2004-01-08 at 22:09, Olaf Meeuwissen wrote:
>>>> # scanimage -L
>>>> device `epson:/dev/usb/scanner0' is a Epson GT-9300 flatbed scanner
>>>>
>>>> I know that my scanner is NOT an Epson GT-9300!
>>>
>>> You may know that, but your scanner doesn't ;-)
>>> The problem is that EPSON decided to market the same scanner under a
>>> different name abroad (here is Japan it's a GT-9300), but didn't
>>> bother to change the name returned by the scanner. The epson (and
>>> epkowa) backend(s) use the name returned by the scanner, not what is
>>> printed on the label (for rather obvious reasons).
>>
>> That is reassuring. However, having made one (low-res) scan,
>> "scanimage" now fails to detect the scanner. I don't know what I
>> might
>> have done to cause it to stop working.
>
> Neither do I, but you might try replugging the scanner and making sure
> that the kernel hasn't loaded the scanner module (which forces the use
> of libusb).
>
> Check with '/sbin/lsmod | grep scanner'. You can use 'rmmod scanner'
> to remove the module.
>
> Hope this helps,
> --
> Olaf Meeuwissen EPSON KOWA Corporation, ECS
> GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
> Penguin's lib! -- I hack, therefore I am -- LPIC-2
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
From dave at dminor.com Sat Jan 10 06:53:01 2004
From: dave at dminor.com (David Minor)
Date: Sat, 10 Jan 2004 00:53:01 -0600
Subject: [sane-devel] OS X and umax 1220u
Message-ID:
Using the new version of libusb that Mattias Ellert packaged with his
twain interface, OS X 10.3 is responding much friendlier towards the
1220u. Unfortunately, it still doesn't scan. However, it first sees
the scanner and reports that it knows what it is, then when you try to
scan, it complains about an Invalid argument. The output of scanimage
with SANE_DEBUG_UMAX1220U=128 is below. Any ideas on why it is dumping
or what I might try?
Thanks,
dm
dminor at ginger:~$ scanimage
[sanei_debug] Setting debug level of umax1220u to 128.
[umax1220u] sane_init: version_code != 0, authorize != 0
[umax1220u] sane_init: SANE umax1220u backend version 1.0.1 from
sane-backends 1.0.13
[umax1220u] reading configure file umax1220u.conf
[umax1220u] attach_matching_devices(usb 0x1606 0x0010)
[umax1220u] attach_scanner: libusb:001:005
[umax1220u] attach_scanner: opening libusb:001:005
[umax1220u] UMAX_open_device: `libusb:001:005'
[umax1220u] csend: cmd = 0
[umax1220u] usync: len = 0, cmd = 0
[umax1220u] usync: s0 = 0x53 s4 = 0xc8
[umax1220u] doing xxxops
[umax1220u] UMAX_close_device:
[umax1220u] attach_matching_devices(usb 0x1606 0x0030)
[umax1220u] attach_matching_devices(usb 0x1606 0x0130)
[umax1220u] finished reading configure file
[umax1220u] sane_get_devices(local_only = 0)
[umax1220u] sane_open
[umax1220u] sane_open: devicename=libusb:001:005
[umax1220u] UMAX_open_device: `libusb:001:005'
[umax1220u] UMAX_open_device: couldn't open device `libusb:001:005':
Invalid argument
scanimage: open of device umax1220u:libusb:001:005 failed: Invalid
argument
[umax1220u] sane_exit
From jonathan at buzzard.me.uk Sat Jan 10 08:13:50 2004
From: jonathan at buzzard.me.uk (Jonathan Buzzard)
Date: Sat, 10 Jan 2004 08:13:50 +0000
Subject: [sane-devel] USB/Parallel Scanner pages
Message-ID:
Due to problems with the ISP that was hosting my domain these pages have
probably been unavailable for at least the last week and remain so.
I have managed to wrestle one of my domains from this bunch of jokers
and you should now be able to find the pages at
http://www.buzzard.me.uk/jonathan/scanners.html
http://www.buzzard.me.uk/jonathan/scanners-usb.html
As I am off abroad skiing, it will be sometime before the buzzard.org.uk
domain is sorted out and they can be viewed on their original page.
Even when it does I intend to make these the primary URL's for the
said pages so if you could update any URL's to these I would be grateful.
There is no major rush other than buzzard.org.uk is unreachable at the
moment) as I intend to keep the domain indefinitely.
JAB.
--
Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk
Northumberland, United Kingdom. Tel: +44 1661-832195
From henning at meier-geinitz.de Sat Jan 10 10:01:50 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 10 Jan 2004 11:01:50 +0100
Subject: [sane-devel] USB/Parallel Scanner pages
In-Reply-To:
References:
Message-ID: <20040110100149.GA978@meier-geinitz.de>
Hi,
On Sat, Jan 10, 2004 at 08:13:50AM +0000, Jonathan Buzzard wrote:
> Due to problems with the ISP that was hosting my domain these pages have
> probably been unavailable for at least the last week and remain so.
>
> I have managed to wrestle one of my domains from this bunch of jokers
> and you should now be able to find the pages at
>
> http://www.buzzard.me.uk/jonathan/scanners.html
> http://www.buzzard.me.uk/jonathan/scanners-usb.html
>
> As I am off abroad skiing, it will be sometime before the buzzard.org.uk
> domain is sorted out and they can be viewed on their original page.
I've changed the links on our supported scanners page.
I'm a bit surprised that nobody complained to us about the broken
link. I guess I have to rerun the link checker, maybe there are other
broken links.
Bye,
Henning
From henning at meier-geinitz.de Sat Jan 10 10:06:40 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sat, 10 Jan 2004 11:06:40 +0100
Subject: [sane-devel] OS X and umax 1220u
In-Reply-To:
References:
Message-ID: <20040110100640.GB978@meier-geinitz.de>
Hi,
On Sat, Jan 10, 2004 at 12:53:01AM -0600, David Minor wrote:
> dminor at ginger:~$ scanimage
> [sanei_debug] Setting debug level of umax1220u to 128.
> [umax1220u] sane_init: version_code != 0, authorize != 0
> [umax1220u] sane_init: SANE umax1220u backend version 1.0.1 from sane-backends 1.0.13
> [umax1220u] reading configure file umax1220u.conf
> [umax1220u] attach_matching_devices(usb 0x1606 0x0010)
> [umax1220u] attach_scanner: libusb:001:005
> [umax1220u] attach_scanner: opening libusb:001:005
> [umax1220u] UMAX_open_device: `libusb:001:005'
> [umax1220u] csend: cmd = 0
> [umax1220u] usync: len = 0, cmd = 0
> [umax1220u] usync: s0 = 0x53 s4 = 0xc8
> [umax1220u] doing xxxops
> [umax1220u] UMAX_close_device:
Ok, the device was closed and open successfully. That's in sane_init,
when SANE scans for devices.
> [umax1220u] attach_matching_devices(usb 0x1606 0x0030)
> [umax1220u] attach_matching_devices(usb 0x1606 0x0130)
Some other USB devices (non-scanners).
> [umax1220u] sane_get_devices(local_only = 0)
The frontend asks for a list of devices ...
> [umax1220u] sane_open
> [umax1220u] sane_open: devicename=libusb:001:005
> [umax1220u] UMAX_open_device: `libusb:001:005'
...and wants to sane_open the device (the same as above).
> [umax1220u] UMAX_open_device: couldn't open device `libusb:001:005': Invalid argument
Bu this time the open fails.
I don't know why and I'm not thte backend maintainer but maybe you get
more information if you enable debugging for USB also (in addition to
SANEI_USB_UAMX1220): SANE_DEBUG_SANEI_USB=255
To reduce the amount of data you get, you should disabel everything
but umax1220u in dll.conf.
Bye,
Henning
From gerhard at gjaeger.de Sat Jan 10 15:09:16 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Sat, 10 Jan 2004 16:09:16 +0100
Subject: [sane-devel] pthread_cancel and MacOS X (was: TWAIN SANE Interface for Mac OS X version 0.3)
In-Reply-To: <3FFE66EE.2020503@tsl.uu.se>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com> <3FFE66EE.2020503@tsl.uu.se>
Message-ID: <200401101609.16585.gerhard@gjaeger.de>
Hi again,
in the meantime (even Henning urged me to do something with that sanei_thread
stuff ;-) I've included Mattias patch within sanei_thread_kill() and checked
it here on my box with a CanoScan 650.
Result: It will not work - it hangs. Why? Because the plustek backend and
also the plustek_pp and u12 didn't use the pthread_cancel function.
As I do really like the "graceful shutdown" of a process or thread, the
reader_process in the plustek backend terminates, when it has done it's
work. But when using the patch, it is urged to wait on a point where it
does not expect to wait. That's the difference to the test-backend.
The test-backend implements also a "hanging" backend. After it has
done it's work it's sleeping...
When writing the sanei_thread stuff, I expected pthread_cancel to work
correctly, and probably it will work correctly in the near future. I also
think, that pthread_cancel should normally not be needed by any backend
to shutdown a reader-process, when this one is done. It's only needed
to cancel such a thread...
I also think, that a working test-backend is not that essential, as working
"real" backends.
So what to do?
I suggest to skip the sanei_thread-patch from Mattias Ellert, as this patch
is not really a workaround for the buggy pthread_cancel on OSX. It only
tries to cure one symptome.
My 2 cents on that,
Gerhard
On Freitag, 9. Januar 2004 09:31, Mattias Ellert wrote:
> Noah Daniels wrote:
> > Hi,
> >
> > I'm still having the same problem with the plustek backend that several
> > people have reported, even using this latest build of the various SANE
> > packages.
> >
> > Basically, sane-find-scanner finds the scanner, but scanimage -L does
> > not. However, if I set SANE_DEBUG_PLUSTEK to a high number, the scanner
> > DOES start working, and scans a partial low-res image before hanging. I
> > know this behavior has been reported before, by Henrik Rintala.
> >
> > I can provide a debug log if anyone's interested... I'd love to be able
> > to get this working (printing to a Canoscan 650).
> >
> > thanks!
> >
> > --
> > Noah Daniels
>
> Using the latest version of libusb from CVS (or the binary packages from
> 2004-01-05) has been reported to fix the problem that scanimage -L does
> not see the scanner unless the DEBUG environment is used.
>
> The following gdb log of the state of scanimage at the time it freezes
> after a scan was provided by a user having a Canon N670U scanner that
> uses the Plustek backend on MacOS X.
>
> To me it looks like the reader process has finished and is waiting to be
> killed, but the main process is still trying to read from it.
>
> Note that the patch in the bug report
> https://alioth.debian.org/tracker/index.php?func=detail&aid=300434&group_id
>=1308&atid=410366
>
> has been applied here, in order to avoid calling pthread_cancel which is
> broken on MacOS X.
>
> Mattias
From jim.george at blueyonder.co.uk Sat Jan 10 20:59:13 2004
From: jim.george at blueyonder.co.uk (Jim George)
Date: Sat, 10 Jan 2004 20:59:13 -0000 (GMT)
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
Message-ID: <1729.192.168.0.7.1073768353.squirrel@tassi.local>
Hi Eddy,
I do have a printer connected to the same port. It's an Epson Photo
Stylus 820cxi if that makes any difference.
I tried turning off/on my scanner but that made no difference, then I
rebooted and when I tried again I got the attached (which was the same as
when I had to turn the scanner off/on).
Could it be a simple configuration issue, something like using EPP on the
port?
Anyway please find the SANE?I_PA4S2 output from this aborted attempted
attached.
Best Regards,
Jim
-------------- next part --------------
/etc/init.d/inetd stop
SANE_DEBUG_MUSTEK_PP=128 SANE_DEBUG_SANEI_PA4S2=255 saned -d128
[saned] main: starting debug mode (level 128)
[saned] main: trying to get port for service `sane' (getaddrinfo)
[saned] main: [0] socket () using IPv6
[saned] main: [0] setsockopt ()
[saned] main: [0] bind () to port 6566
[saned] main: [0] listen ()
[saned] main: [1] socket () using IPv4
[saned] main: [1] setsockopt ()
[saned] main: [1] bind () to port 6566
[saned] main: [1] bind failed: Address already in use
[saned] main: waiting for control connection
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.13 ready
[saned] check_host: access by remote host: ::1
[saned] check_host: remote host is IN6_LOOPBACK: access granted
[saned] init: access granted
[saned] init: access granted to root@::1
[saned] process_request: waiting for request
[saned] process_request: got request 2
[saned] process_request: access to resource `mustek_pp' granted
[sanei_debug] Setting debug level of mustek_pp to 128.
[mustek_pp] sane-mustek_pp, version 0.12-alpha. build for SANE 1.0.13
[mustek_pp] backend by Jochen Eisinger
[sanei_debug] Setting debug level of sanei_pa4s2 to 255.
[sanei_pa4s2] sanei_pa4s2: interface called for the first time
[sanei_pa4s2] sanei_pa4s2_open: called for device 'parport0'
[sanei_pa4s2] sanei_pa4s2_open: trying to connect to port
[sanei_pa4s2] pa4s2_open: trying to attach dev `parport0`
[sanei_pa4s2] pa4s2_init: static int first_time = 1
[sanei_pa4s2] pa4s2_init: called for the first time
[sanei_pa4s2] pa4s2_init: initializing libieee1284
[sanei_pa4s2] pa4s2_init: 1 ports reported by IEEE 1284 library
[sanei_pa4s2] pa4s2_init: port 0 is `parport0`
[sanei_pa4s2] pa4s2_init: allocating port list
[sanei_pa4s2] pa4s2_init: initialized successfully
[sanei_pa4s2] pa4s2_open: looking up port in list
[sanei_pa4s2] pa4s2_open: port is in list at port[0]
[sanei_pa4s2] pa4s2_open: setting up port data
[sanei_pa4s2] pa4s2_open: name=parport0 in_use=SANE_TRUE
[sanei_pa4s2] pa4s2_open: enabled=SANE_FALSE mode=PA4S2_MODE_NIB
[sanei_pa4s2] pa4s2_open: opening device
[sanei_pa4s2] pa4s2_open: device `parport0` opened...
[sanei_pa4s2] pa4s2_open: returning SANE_STATUS_GOOD
[sanei_pa4s2] pa4s2_open: open dev `parport0` as fd 0
[sanei_pa4s2] sanei_pa4s2_open: connected to device using fd 0
[sanei_pa4s2] sanei_pa4s2_open: checking for scanner
[sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1
[sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0'
[sanei_pa4s2] pa4s2_enable: prelock[] = {0x04, 0xd8, 0x0c}
[sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: reading ASIC id
[sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0
[sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin
[sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at 'parport0'
[sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0
[sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called
[sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok...
[sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's
[sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down.
[sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode
[sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xb5 from 'parport0'
[sanei_pa4s2] sanei_pa4s2_readbyte: read finished
[sanei_pa4s2] sanei_pa4s2_readbyte: got value 0xb5
[sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_readend: called for fd 0
[sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called
[sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok...
[sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's
[sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down.
[sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend
[sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0
[sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: could not find scanner
[sanei_pa4s2] sanei_pa4s2_open: reported ASIC id 0xb5
[sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0
[sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0'
[sanei_pa4s2] pa4s2_disable: state restored
[sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: closing port
[sanei_pa4s2] sanei_pa4s2_close: fd = 0
[sanei_pa4s2] sanei_pa4s2_close: freeing resources
[sanei_pa4s2] pa4s2_close: fd=0
[sanei_pa4s2] pa4s2_close: this is port 'parport0'
[sanei_pa4s2] pa4s2_close: checking whether port is enabled
[sanei_pa4s2] pa4s2_close: trying to free io port
[sanei_pa4s2] pa4s2_close: marking port as unused
[sanei_pa4s2] pa4s2_close: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_close: finished
[sanei_pa4s2] sanei_pa4s2_open: returning SANE_STATUS_INVAL
[mustek_pp] cis_attach: couldn't attach to `parport0' (Invalid argument)
[mustek_pp] sane_open: unknown devicename ``Mustek-1200CP''
[saned] process_request: waiting for request
[saned] process_request: got request 10
[mustek_pp] sane_exit: all drivers unloaded
[saned] quit: exiting
From dave at dminor.com Sat Jan 10 22:38:59 2004
From: dave at dminor.com (David Minor)
Date: Sat, 10 Jan 2004 16:38:59 -0600
Subject: [sane-devel] OS X and umax 1220u
In-Reply-To: <20040110100640.GB978@meier-geinitz.de>
References: <20040110100640.GB978@meier-geinitz.de>
Message-ID:
On Jan 10, 2004, at 4:06 AM, Henning Meier-Geinitz wrote:
> The frontend asks for a list of devices ...
>
>> [umax1220u] sane_open
>> [umax1220u] sane_open: devicename=libusb:001:005
>> [umax1220u] UMAX_open_device: `libusb:001:005'
>
> ...and wants to sane_open the device (the same as above).
>
>> [umax1220u] UMAX_open_device: couldn't open device `libusb:001:005':
>> Invalid argument
>
> Bu this time the open fails.
>
> I don't know why and I'm not thte backend maintainer but maybe you get
> more information if you enable debugging for USB also (in addition to
> SANEI_USB_UAMX1220): SANE_DEBUG_SANEI_USB=255
>
> To reduce the amount of data you get, you should disabel everything
> but umax1220u in dll.conf.
>
I commented out everything in dll.conf but umax1220u, set USB debug
output to 255 in addition to the umax1220u debug at 128 as before. I
also disconnected all other USB devices to simplify matters. I'm not
going to pretend to being able to interpret the output, but I will
attach for anyone to look over and see if the problem can be isolated.
Thanks,
dm
-------------- next part --------------
[sanei_debug] Setting debug level of umax1220u to 128.
[umax1220u] sane_init: version_code != 0, authorize != 0
[umax1220u] sane_init: SANE umax1220u backend version 1.0.1 from sane-backends 1.0.13
[sanei_debug] Setting debug level of sanei_usb to 255.
usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 002
usb_os_find_devices: Found USB device at location 0x18000000
usb_os_find_devices: Found 001 on 001 at location 0x18000000
usb_os_find_devices: Found USB device at location 0x18100000
usb_os_find_devices: Found 003 on 001 at location 0x18100000
usb_os_find_devices: Found USB device at location 0x19000000
usb_os_open: 1606:0010
usb_os_open(USBDeviceOpenSeize): another process has device opened for exclusive access
usb_control_msg: 128 6 512 0 0xbfffeab8 8 1000
usb_control_msg: 128 6 512 0 0x300a00 39 1000
usb_os_close: 1606:0010
usb_os_open: 05ac:8005
usb_os_open(USBDeviceOpenSeize): another process has device opened for exclusive access
usb_control_msg: 128 6 512 0 0xbfffeab8 8 1000
usb_control_msg: 128 6 512 0 0x300ab0 27 1000
usb_os_close: 05ac:8005
usb_os_find_devices: Found USB device at location 0x18000000
usb_os_find_devices: Found USB device at location 0x18100000
usb_os_find_devices: Found USB device at location 0x19000000
usb_os_find_devices: Found 001 on 002 at location 0x19000000
usb_os_open: 05ac:8005
usb_os_open(USBDeviceOpenSeize): another process has device opened for exclusive access
usb_control_msg: 128 6 512 0 0xbfffeab8 8 1000
usb_control_msg: 128 6 512 0 0x300f00 27 1000
usb_os_close: 05ac:8005
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces
[sanei_usb] sanei_usb_init: found libusb device (0x1606/0x0010) interface 0 at libusb:001:003
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look like a scanner (9/9)
[sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces
[sanei_usb] sanei_usb_init: found 1 devices
[umax1220u] reading configure file umax1220u.conf
[umax1220u] attach_matching_devices(usb 0x1606 0x0010)
[sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0010
[umax1220u] attach_scanner: libusb:001:003
[umax1220u] attach_scanner: opening libusb:001:003
[umax1220u] UMAX_open_device: `libusb:001:003'
[sanei_usb] sanei_usb_open: trying to open device `libusb:001:003'
usb_os_open: 1606:0010
usb_set_configuration: called for config 1
usb_claim_interface: called for interface 0
Interface 0 of device is 0x130b
claim_interface: Interface 0 of device from QueryInterface is 0x3020d0
[sanei_usb] sanei_usb_open: found bulk-out endpoint (address 1)
[sanei_usb] sanei_usb_open: found bulk-in endpoint (address 2)
[sanei_usb] sanei_usb_open: found interupt-in endpoint (address 3)
[sanei_usb] sanei_usb_open: opened usb device `libusb:001:003' (*dn=0)
[sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x1606, productID: 0x0010
[umax1220u] csend: cmd = 0
[umax1220u] usync: len = 0, cmd = 0
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 2, index = 0, len = 0
usb_control_msg: 64 3 2 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] 0000: 55 AA U...............
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=2 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffaeb0 1 30000
[sanei_usb] 0000: C8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 4, index = 0, len = 0
usb_control_msg: 64 3 4 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes
[sanei_usb] 0000: 00 00 00 00 ................
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=4 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 4 bytes, wrote 4 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 0, len = 1
usb_control_msg: 192 0 0 0 0xbfffaf20 1 30000
[sanei_usb] 0000: 53 S...............
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffaf21 1 30000
[sanei_usb] 0000: C8 ................
[umax1220u] usync: s0 = 0x53 s4 = 0xc8
[umax1220u] doing xxxops
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 2, index = 3, len = 0
usb_control_msg: 64 1 2 3 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 14, index = 2, len = 0
usb_control_msg: 64 1 14 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 64, index = 0, len = 0
usb_control_msg: 64 1 64 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 6, index = 2, len = 0
usb_control_msg: 64 1 6 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffaee0 1 30000
[sanei_usb] 0000: 38 8...............
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 7, index = 2, len = 0
usb_control_msg: 64 1 7 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffaee0 1 30000
[sanei_usb] 0000: 38 8...............
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 4, index = 2, len = 0
usb_control_msg: 64 1 4 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffaee0 1 30000
[sanei_usb] 0000: F8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 5, index = 2, len = 0
usb_control_msg: 64 1 5 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 2, len = 1
usb_control_msg: 192 0 0 2 0xbfffaee0 1 30000
[sanei_usb] 0000: 05 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 4, index = 2, len = 0
usb_control_msg: 64 1 4 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 30, index = 3, len = 0
usb_control_msg: 64 1 30 3 0x0 0 30000
[umax1220u] UMAX_close_device:
[sanei_usb] sanei_usb_close: closing device 0
usb_os_close: 1606:0010
[umax1220u] attach_matching_devices(usb 0x1606 0x0030)
[sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0030
[umax1220u] attach_matching_devices(usb 0x1606 0x0130)
[sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0130
[umax1220u] finished reading configure file
[umax1220u] sane_get_devices(local_only = 0)
[umax1220u] sane_open
[umax1220u] sane_open: devicename=libusb:001:003
[umax1220u] UMAX_open_device: `libusb:001:003'
[sanei_usb] sanei_usb_open: trying to open device `libusb:001:003'
usb_os_open: 1606:0010
usb_set_configuration: called for config 1
usb_claim_interface: called for interface 0
Interface 0 of device is 0x1313
claim_interface: Interface 0 of device from QueryInterface is 0x302470
[sanei_usb] sanei_usb_open: found bulk-out endpoint (address 1)
[sanei_usb] sanei_usb_open: we already have a bulk-out endpoint (address: 1), ignoring the new one
[sanei_usb] sanei_usb_open: found bulk-in endpoint (address 2)
[sanei_usb] sanei_usb_open: we already have a bulk-in endpoint (address: 130), ignoring the new one
[sanei_usb] sanei_usb_open: found interupt-in endpoint (address 3)
[sanei_usb] sanei_usb_open: we already have a int-in endpoint (address: 131), ignoring the new one
[sanei_usb] sanei_usb_open: opened usb device `libusb:001:003' (*dn=0)
[sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x1606, productID: 0x0010
[umax1220u] csend: cmd = 0
[umax1220u] usync: len = 0, cmd = 0
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 2, index = 0, len = 0
usb_control_msg: 64 3 2 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] 0000: 55 AA U...............
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=2 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbffff3b0 1 30000
[sanei_usb] 0000: C8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 4, index = 0, len = 0
usb_control_msg: 64 3 4 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes
[sanei_usb] 0000: 00 00 00 00 ................
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=4 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 4 bytes, wrote 4 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 0, len = 1
usb_control_msg: 192 0 0 0 0xbffff420 1 30000
[sanei_usb] 0000: 53 S...............
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbffff421 1 30000
[sanei_usb] 0000: C8 ................
[umax1220u] usync: s0 = 0x53 s4 = 0xc8
[umax1220u] doing xxxops
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 2, index = 3, len = 0
usb_control_msg: 64 1 2 3 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 14, index = 2, len = 0
usb_control_msg: 64 1 14 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 64, index = 0, len = 0
usb_control_msg: 64 1 64 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 6, index = 2, len = 0
usb_control_msg: 64 1 6 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbffff3e0 1 30000
[sanei_usb] 0000: 38 8...............
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 7, index = 2, len = 0
usb_control_msg: 64 1 7 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbffff3e0 1 30000
[sanei_usb] 0000: 38 8...............
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 4, index = 2, len = 0
usb_control_msg: 64 1 4 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbffff3e0 1 30000
[sanei_usb] 0000: F8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 5, index = 2, len = 0
usb_control_msg: 64 1 5 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 2, len = 1
usb_control_msg: 192 0 0 2 0xbffff3e0 1 30000
[sanei_usb] 0000: 05 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 4, index = 2, len = 0
usb_control_msg: 64 1 4 2 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 1, value = 30, index = 3, len = 0
usb_control_msg: 64 1 30 3 0x0 0 30000
[umax1220u] sane_control_option: handle=0x1a000, opt=0, act=0, val=0xbffff9ec, info=0x0
[umax1220u] sane_control_option: handle=0x1a000, opt=0, act=0, val=0xbffff540, info=0x0
[umax1220u] sane_get_option_descriptor: option = 0
[umax1220u] sane_get_option_descriptor: option = 1
[umax1220u] sane_get_option_descriptor: option = 2
[umax1220u] sane_get_option_descriptor: option = 3
[umax1220u] sane_get_option_descriptor: option = 4
[umax1220u] sane_get_option_descriptor: option = 5
[umax1220u] sane_control_option: handle=0x1a000, opt=5, act=0, val=0xb34c, info=0x0
[umax1220u] sane_get_option_descriptor: option = 6
[umax1220u] sane_control_option: handle=0x1a000, opt=6, act=0, val=0xb350, info=0x0
[umax1220u] sane_get_option_descriptor: option = 7
[umax1220u] sane_control_option: handle=0x1a000, opt=3, act=0, val=0xbffff544, info=0x0
[umax1220u] sane_control_option: handle=0x1a000, opt=4, act=0, val=0xbffff544, info=0x0
[umax1220u] sane_control_option: handle=0x1a000, opt=3, act=0, val=0xbffff9f0, info=0x0
[umax1220u] sane_get_option_descriptor: option = 5
[umax1220u] sane_control_option: handle=0x1a000, opt=5, act=1, val=0xbffff9f4, info=0xbffff568
[umax1220u] sane_control_option: handle=0x1a000, opt=4, act=0, val=0xbffff9f0, info=0x0
[umax1220u] sane_get_option_descriptor: option = 6
[umax1220u] sane_control_option: handle=0x1a000, opt=6, act=1, val=0xbffff9f4, info=0xbffff568
[umax1220u] sane_start
[umax1220u] UMAX_set_scan_parameters:
[umax1220u] color = 1
[umax1220u] xo = 0, yo = 0
[umax1220u] w = 0, h = 0
[umax1220u] xres = 75, yres = 75
[umax1220u] left = 0, top = 0
[umax1220u] right = 0, bottom = 0
scanimage: sane_start: Invalid argument
[umax1220u] sane_cancel: handle = 0x1a000
[umax1220u] sane_cancel: canceling is unsupported in this backend
[umax1220u] sane_close
[umax1220u] UMAX_set_lamp_state: state = 0
[umax1220u] csend: cmd = 0
[umax1220u] usync: len = 0, cmd = 0
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 2, index = 0, len = 0
usb_control_msg: 64 3 2 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] 0000: 55 AA U...............
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=2 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbffff820 1 30000
[sanei_usb] 0000: C8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 4, index = 0, len = 0
usb_control_msg: 64 3 4 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes
[sanei_usb] 0000: 00 00 00 00 ................
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=4 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 4 bytes, wrote 4 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 0, len = 1
usb_control_msg: 192 0 0 0 0xbffff890 1 30000
[sanei_usb] 0000: 53 S...............
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbffff891 1 30000
[sanei_usb] 0000: C8 ................
[umax1220u] usync: s0 = 0x53 s4 = 0xc8
[umax1220u] cwritev_opc1: set lamp state = off
[umax1220u] cwrite: cmd = 2, len = 16
[umax1220u] usync: len = 16, cmd = 130
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 2, index = 0, len = 0
usb_control_msg: 64 3 2 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] 0000: 55 AA U...............
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=2 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb6f0 1 30000
[sanei_usb] 0000: C8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 4, index = 0, len = 0
usb_control_msg: 64 3 4 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes
[sanei_usb] 0000: 00 00 10 82 ................
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=4 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 4 bytes, wrote 4 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 0, len = 1
usb_control_msg: 192 0 0 0 0xbfffb760 1 30000
[sanei_usb] 0000: 53 S...............
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb761 1 30000
[sanei_usb] 0000: C8 ................
[umax1220u] usync: s0 = 0x53 s4 = 0xc8
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb760 1 30000
[sanei_usb] 0000: C8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 16, index = 0, len = 0
usb_control_msg: 64 3 16 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 16 bytes
[sanei_usb] 0000: 01 00 01 70 00 00 60 2F 13 05 00 00 00 80 90 00 ...p..`/........
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=16 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 16 bytes, wrote 16 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb7d1 1 30000
[sanei_usb] 0000: C0 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 0, len = 1
usb_control_msg: 192 0 0 0 0xbfffb7d0 1 30000
[sanei_usb] 0000: 53 S...............
[umax1220u] cwrite: s0 = 0x53 s4 = 0xc0
[umax1220u] cread: cmd = 2, len = 16
[umax1220u] usync: len = 16, cmd = 194
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 2, index = 0, len = 0
usb_control_msg: 64 3 2 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes
[sanei_usb] 0000: 55 AA U...............
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=2 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb6f0 1 30000
[sanei_usb] 0000: C8 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 0, index = 0, len = 0
usb_control_msg: 64 4 0 0 0x0 0 30000
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 3, value = 4, index = 0, len = 0
usb_control_msg: 64 3 4 0 0x0 0 30000
[sanei_usb] sanei_usb_write_bulk: trying to write 4 bytes
[sanei_usb] 0000: 00 00 10 C2 ................
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: pipeRef for ep address 0x01 found: 0x01
usb_bulk_write: endpoint=0x01 size=4 TO=30000
write completed
[sanei_usb] sanei_usb_write_bulk: wanted 4 bytes, wrote 4 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 0, len = 1
usb_control_msg: 192 0 0 0 0xbfffb760 1 30000
[sanei_usb] 0000: 53 S...............
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb761 1 30000
[sanei_usb] 0000: D0 ................
[umax1220u] usync: s0 = 0x53 s4 = 0xd0
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb760 1 30000
[sanei_usb] 0000: D0 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 2, value = 16, index = 0, len = 0
usb_control_msg: 64 2 16 0 0x0 0 30000
[sanei_usb] sanei_usb_read_bulk: trying to read 16 bytes
usb_bulk_read: ep addr = 0x82
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 0 number: 1
ep_to_pipeRef: Pipe 2: DIR: 1 number: 2
ep_to_pipeRef: pipeRef for ep address 0x82 found: 0x02
usb_bulk_read: endpoint=0x82 size=16 timeout=30.000000sec
[sanei_usb] 0000: 01 00 01 70 00 00 60 2F 13 05 00 00 00 80 90 00 ...p..`/........
[sanei_usb] sanei_usb_read_bulk: wanted 16 bytes, got 16 bytes
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 4, len = 1
usb_control_msg: 192 0 0 4 0xbfffb7d1 1 30000
[sanei_usb] 0000: C0 ................
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 0, value = 0, index = 0, len = 1
usb_control_msg: 192 0 0 0 0xbfffb7d0 1 30000
[sanei_usb] 0000: 53 S...............
[umax1220u] cwrite: s0 = 0x53 s4 = 0xc0
[umax1220u] UMAX_close_device:
[sanei_usb] sanei_usb_close: closing device 0
usb_os_close: 1606:0010
[umax1220u] sane_exit
-------------- next part --------------
From gilles at ffii.org Sun Jan 11 02:29:54 2004
From: gilles at ffii.org (gilles at ffii.org)
Date: Sun, 11 Jan 2004 03:29:54 +0100
Subject: [sane-devel] HP5370C - Distorted image
Message-ID: <20040111022954.GA24214@ffii.org>
Hello.
First: Thanks a lot for your continuous efforts to make this scanner work with
Linux!
[Last time I had tried it (several months ago), with 'hpusbscsi', I had to
quickly power off the scanner as the awful noise and erratic motion of the
scanning made me believe it would fall apart...
Today I compiled kernel 2.6.0, and reading that 'hpusbscsci' was now
obsolete, I thought I could give it a try.]
Now the scanner doesn't seem to suffer anymore :-) but the image produced
is distorted: I'm among the unlucky ones who get a 45 degrees
shifted-wrapped image (cf. a post from November 26).
Is the source of the problem known? Any chance that the scanner will be
working properly? [Scanning is the last and only thing which I must do on
M$-Windows!]
Best regards,
Gilles
P.S. System info:
# scanimage --version
scanimage (sane-backends) 1.0.13; backend version 1.0.13
Debian GNU/Linux testing/unstable
From kleptog at svana.org Sun Jan 11 03:15:39 2004
From: kleptog at svana.org (Martijn van Oosterhout)
Date: Sun, 11 Jan 2004 14:15:39 +1100
Subject: [sane-devel] HP5370C - Distorted image
In-Reply-To: <20040111022954.GA24214@ffii.org>
References: <20040111022954.GA24214@ffii.org>
Message-ID: <20040111031539.GA19236@svana.org>
While I can't really tell you how to fix it, what causes the problem is
actually trivial.
Lets say that the scanning software is expecting the scanner to send 541
pixels per line and the scanner actually sends 542, each row gets offset by
one leading to a very nice 45 degree slant to the right. If it sends 540 you
get a slant to the left.
It's a very simple off-by-one error. Maybe if you try scanning different
sizes to see which ones work and which ones don't you can get some kind of
idea of where the discrepancy lies.
Hope this helps,
On Sun, Jan 11, 2004 at 03:29:54AM +0100, gilles at ffii.org wrote:
> Hello.
>
> First: Thanks a lot for your continuous efforts to make this scanner work with
> Linux!
>
> [Last time I had tried it (several months ago), with 'hpusbscsi', I had to
> quickly power off the scanner as the awful noise and erratic motion of the
> scanning made me believe it would fall apart...
> Today I compiled kernel 2.6.0, and reading that 'hpusbscsci' was now
> obsolete, I thought I could give it a try.]
>
> Now the scanner doesn't seem to suffer anymore :-) but the image produced
> is distorted: I'm among the unlucky ones who get a 45 degrees
> shifted-wrapped image (cf. a post from November 26).
>
> Is the source of the problem known? Any chance that the scanner will be
> working properly? [Scanning is the last and only thing which I must do on
> M$-Windows!]
>
>
> Best regards,
>
> Gilles
>
> P.S. System info:
> # scanimage --version
> scanimage (sane-backends) 1.0.13; backend version 1.0.13
>
> Debian GNU/Linux testing/unstable
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
--
Martijn van Oosterhout http://svana.org/kleptog/
> (... have gone from d-i being barely usable even by its developers
> anywhere, to being about 20% done. Sweet. And the last 80% usually takes
> 20% of the time, too, right?) -- Anthony Towns, debian-devel-announce
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL:
From mancio_and at libero.it Sun Jan 11 14:07:26 2004
From: mancio_and at libero.it (mancio_and at libero.it)
Date: Sun, 11 Jan 2004 15:07:26 +0100
Subject: [sane-devel] HP Scanjet 3670...
Message-ID:
>
> I haven't heard from mancio_and at libero.it after his initial posting
> (http://lists.alioth.debian.org/pipermail/sane-devel/2003-November/009360.html).
> If he doesn't answer on this list, try to contact him directly.
>
Hi,
I'm sorry, I had no time enough to begin the project.
Bye.
From henning at meier-geinitz.de Sun Jan 11 14:15:41 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 11 Jan 2004 15:15:41 +0100
Subject: [sane-devel] OS X and umax 1220u
In-Reply-To:
References: <20040110100640.GB978@meier-geinitz.de>
Message-ID: <20040111141541.GB683@meier-geinitz.de>
Hi,
On Sat, Jan 10, 2004 at 04:38:59PM -0600, David Minor wrote:
> I commented out everything in dll.conf but umax1220u, set USB debug
> output to 255 in addition to the umax1220u debug at 128 as before. I
> also disconnected all other USB devices to simplify matters. I'm not
> going to pretend to being able to interpret the output, but I will
> attach for anyone to look over and see if the problem can be isolated.
I'm not the author of that backend so I may be completely wrong...
However, this time you get a completely different error. Openeing the
scanner works, but starting the scan doesn't:
> [umax1220u] sane_start
> [umax1220u] UMAX_set_scan_parameters:
> [umax1220u] color = 1
> [umax1220u] xo = 0, yo = 0
> [umax1220u] w = 0, h = 0
> [umax1220u] xres = 75, yres = 75
> [umax1220u] left = 0, top = 0
> [umax1220u] right = 0, bottom = 0
> scanimage: sane_start: Invalid argument
There is no tranfer to the scanner involved at all. Looks like a
backend bug. It sets widths and height to 0 by default.
Try again with scanimage but set width and height explicitely to e.g.
10 mm (see scanimage --help for details).
Bye,
Henning
From mbwdbuit at gmx.net Sat Jan 10 23:08:46 2004
From: mbwdbuit at gmx.net (M.B.W.D. Buitenhuis)
Date: Sun, 11 Jan 2004 00:08:46 +0100
Subject: [sane-devel] RX500 MFP scanner
Message-ID: <1073776126.3316.1.camel@localhost.localdomain>
Could someone help me to get the scanner part of this device working?
I haven't got it working although I've got it recognised as a RX500.
The problem is that it somehow cannot switch the device on.
output of command "lsusb" is:
Bus 001 Device 002: ID 04b8:0807 Seiko Epson Corp.
output of "sane-find-scanner" is:
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04b8 [EPSON], product=0x0807 [USB2.0 MFP])
at libusb:001:002
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Scanners connected to the parallel port or other proprietary ports
can't be
# detected by this program.
output of scanimage -L
[epson] Unknown type R or level d, using B3
device `v4l:/dev/video0' is a Noname Terratec Cinergy 400 TV virtual
device
device `epson:libusb:001:002' is a Epson RX500 flatbed scanner
If I start xsane as a user I don't get to see the device, but as root it
gives me the option of using my TV-card or the RX500 device.
After selecting the RX500 xsane starts well. Now if I want to make a
scan or a prescan it generates a message that it cant switch on the
device. "wrong/false argument".
Seems I close but I haven't got enough administrator experience with
these type of devices.
Am I missing something simple here?
//Marcellino
From thomas.pasch at gmx.de Sun Jan 11 13:34:24 2004
From: thomas.pasch at gmx.de (Thomas Pasch)
Date: Sun, 11 Jan 2004 14:34:24 +0100
Subject: [sane-devel] Sane USB problem with HP ScanJet 5300C on FreeBSD-5.2-RC2/amd64
Message-ID: <200401111434.24177.thomas.pasch@gmx.de>
Hello,
I'm trying to get my scanner to work on FreeBSD 5.2-RC2/amd64. I can "see"
the scanner with sane-find-scanner and usbdevs but scanimage seems to hang.
I'm using the sane-backends-1.0.12_3 and sane-frontends-1.0.11 and
libusb-0.1.7_1 from the package tree (but also tried ports and a newer
backends version as well).
See attached the DEBUG output of "scanimage -L". For me it looks like
the scanner is found and a request is written to it, but there is never an
anwer.
Beside, how do I use libusb on 5.2? The man pages are saying something
about creating /dev/ugen* but as 5.2 uses devfs, you can't create it and it
isn't there.
Cheers,
aanno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: scanimage.log.gz
Type: application/x-gzip
Size: 779 bytes
Desc: not available
URL:
From edg1 at tiscali.be Sun Jan 11 14:14:59 2004
From: edg1 at tiscali.be (Eddy De Greef)
Date: Sun, 11 Jan 2004 15:14:59 +0100
Subject: [sane-devel] Problems with mustek_pp and releasing the parallel port
In-Reply-To: <1729.192.168.0.7.1073768353.squirrel@tassi.local>; from jim.george@blueyonder.co.uk on za, jan 10, 2004 at 21:59:13 +0100
References: <1729.192.168.0.7.1073768353.squirrel@tassi.local>
Message-ID: <20040111141459.GA3254@reddot.erps-kwerps.be>
Op 10-01-04 21:59:13 schreef Jim George:
> Hi Eddy,
>
> I do have a printer connected to the same port. It's an Epson Photo
> Stylus 820cxi if that makes any difference.
Have you tried disconnecting it?
> I tried turning off/on my scanner but that made no difference, then I
> rebooted and when I tried again I got the attached (which was the
> same as when I had to turn the scanner off/on).
>
> Could it be a simple configuration issue, something like using EPP on
> the port?
That's unlikely, but you never know. You can try changing the port
settings in the BIOS. You can usually choose between EPP, ECP, ...
Maybe it makes a difference.
> Anyway please find the SANE?I_PA4S2 output from this aborted
> attempted attached.
The scanner still isn't recognized. Can you still scan at all
in non-debug mode?
Best regards,
Eddy
From mattias.ellert at tsl.uu.se Sun Jan 11 14:28:40 2004
From: mattias.ellert at tsl.uu.se (Mattias Ellert)
Date: Sun, 11 Jan 2004 15:28:40 +0100
Subject: [sane-devel] Re: pthread_cancel and MacOS X
In-Reply-To: <200401101609.16585.gerhard@gjaeger.de>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com> <3FFE66EE.2020503@tsl.uu.se> <200401101609.16585.gerhard@gjaeger.de>
Message-ID: <40015D98.1030907@tsl.uu.se>
Jaeger, Gerhard wrote:
> Hi again,
>
> I also think, that a working test-backend is not that essential, as working
> "real" backends.
Here I must strongly disagree. A working test backend is extremely
essential. It is a very important tool in debugging.
If a frontend works with the test backend, but not with some other
backend, you know that the problem is (most probably) in that backend
and not in the frontend itself.
If you can change the test backend in some other way so that the patch
is not needed, that would be fine, but giving up a working test backend
is not a viable solution to the problem.
Mattias
--
________________________________________________________________________
mattias.ellert at tsl.uu.se tel: +46 18 471 32 58
http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13
________________________________________________________________________
From Oliver.Schwartz at gmx.de Sun Jan 11 14:35:29 2004
From: Oliver.Schwartz at gmx.de (Oliver Schwartz)
Date: Sun, 11 Jan 2004 15:35:29 +0100
Subject: [sane-devel] Epson GT-7400U not detected
In-Reply-To: <878ykkehan.fsf@zen.epkowa.co.jp>
References: <1072823795.721.38.camel@invigiator.invigiator.com> <20031231100823.GI1003@meier-geinitz.de> <878ykkehan.fsf@zen.epkowa.co.jp>
Message-ID: <200401111535.31596.Oliver.Schwartz@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
> > You may also try the snapscan backend. At least the 1670 is
> > supported by that backend. Maybe these scanners are similar? But
> > you will need the latest development version of SANE. Maybe the
> > manintainer of the snapscan backend has heard baout that scanner:
> > Oliver Schwartz
>
> I've checked around a little bit and found some tidbits of
> information that seems to indicate that the GT-7400U is the little
> sister of the GT-8400U. There is a reasonable chance that this
> scanner works with the snapscan backend. You will probably have to
> muck around a bit to get it to load the right firmware file and
> copy that file from the Windoze software.
With a bit of luck it's sufficient to add the USB IDs in snapscan.conf
and edit the path to the firmware file in snapscan.conf. The firmware
file is installed with your windows driver, it's probably named *.bin
and located somewhere under WINNT/Twain32.
If possible please send me a debug log from
"SANE_DEBUG_SNAPSCAN scanimage -L > debug.log"
- -Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQFAAV8x/V6sbrmfIuMRAnWqAJ9fqP+YuDyqG+0jEnbFAs6MtNMbXwCffAJP
GhiyguWWkjD6DnEOEs5+VSE=
=zEd0
-----END PGP SIGNATURE-----
From mike at alezan.org Sun Jan 11 14:50:36 2004
From: mike at alezan.org (Mickael Profeta)
Date: Sun, 11 Jan 2004 15:50:36 +0100
Subject: [sane-devel] HP Scanjet 3670...
In-Reply-To: <20040109123857.GA27118@sugarpie>
References: <20040109123857.GA27118@sugarpie>
Message-ID: <400162BC.5040308@alezan.org>
Hi,
Sanjay.Chigurupati at lntinfotech.com has a HP scanjet 2400 and it seems to
be the same driver.
After the mail of mancio_and at libero.it we just received, I think I am
the last one to try to write a driver for this scanner :( If I forget
someone just send an e-mail...
Personnaly, I just defend my PhD and due to that I had no time to go on
with this driver, but now i will have much time and I am still very
interested to do it.
I tried to ask HP for some technical doc but with no results... if you
want to try...
I tried to log the usb transaction under windows, bur unfortunately I
can only log the beginning of the transaction... I don't receive
anything in the log after the preview scan :(
So as you can see we are at the very beginning of this job, but if you
are interested I will be very very happy to collaborate.
Do not hesitate to e-mail me, and we can start a more robust project to
lead to this driver if you want...
Sincerely
Mike
Christian Josefsson wrote:
> Hi!
>
> I'm a Computer Science student, which has come to the point of writing
> my Master Thesis. Since I'm interested in systems programming and Linux
> and in the posession of a unsupported scanner, namely hp scanjet 3670,
> I've concidered writing a driver for that scanner as part of my Thesis
> (the thesis would also contain other investigations ...).
> But since there appears to be some activity going on in writing a driver
> for the scanjet 3670 I would like to hear, how far you have come, and
> if it would be feasible for one more person trying to write the driver...
>
> However in case the driver is already close to finished and/or there already
> are enough developers aiming at the same driver, I'd stop pursuing this
> idea and instead find myself another subject for my Thesis.
>
> Kind regards
> // Christian
From gerhard at gjaeger.de Sun Jan 11 17:57:09 2004
From: gerhard at gjaeger.de (Jaeger, Gerhard)
Date: Sun, 11 Jan 2004 18:57:09 +0100
Subject: [sane-devel] Re: pthread_cancel and MacOS X
In-Reply-To: <40015D98.1030907@tsl.uu.se>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com> <200401101609.16585.gerhard@gjaeger.de> <40015D98.1030907@tsl.uu.se>
Message-ID: <200401111857.09710.gerhard@gjaeger.de>
Hoh, hoh...
stop, I don't say, that it is not needed or not useful!!!
I only mean, that we should not spend too much time on a problem
which needs to be fixed outside of SANE.
Also please remember:
Using the pthread approach instead of the Unix process stuff has also
been done, because of MacOSX is not able to inherit file descriptors
to a child process. Now that the sanei_thread stuff seems to work for
quite a lot of platforms, we ran into the next MacOSX trouble...
What comes next?
I mean I appreciate your work as I think it is useful to spread SANE
over another platform, but I don't think that SANE should work around
each OS bug, especially here, when there's no clean solution for this
problem. This needs to be solved by the guys, that implemented the
pthread stuff there.
Henning, what do you think about changing the test-backend. As far
as I understood, the test-backend simulates, when the reader-process
has finished, a "hanging" backend, that is "killed" by the parent process.
Probably we can accept a workaround only for the MacOS platform...
Hope we find a good solution on that. I'll recheck some other approaches...
Ciao,
Gerhard
On Sonntag, 11. Januar 2004 15:28, Mattias Ellert wrote:
> Jaeger, Gerhard wrote:
> > Hi again,
> >
> > I also think, that a working test-backend is not that essential, as
> > working "real" backends.
>
> Here I must strongly disagree. A working test backend is extremely
> essential. It is a very important tool in debugging.
>
> If a frontend works with the test backend, but not with some other
> backend, you know that the problem is (most probably) in that backend
> and not in the frontend itself.
>
> If you can change the test backend in some other way so that the patch
> is not needed, that would be fine, but giving up a working test backend
> is not a viable solution to the problem.
>
> Mattias
From henning at meier-geinitz.de Sun Jan 11 18:39:02 2004
From: henning at meier-geinitz.de (Henning Meier-Geinitz)
Date: Sun, 11 Jan 2004 19:39:02 +0100
Subject: [sane-devel] Re: pthread_cancel and MacOS X
In-Reply-To: <200401111857.09710.gerhard@gjaeger.de>
References: <13617772.1073589444350.JavaMail.ndaniels@mac.com> <200401101609.16585.gerhard@gjaeger.de> <40015D98.1030907@tsl.uu.se> <200401111857.09710.gerhard@gjaeger.de>
Message-ID: <20040111183902.GF683@meier-geinitz.de>
Hi,
On Sun, Jan 11, 2004 at 06:57:09PM +0100, Jaeger, Gerhard wrote:
> Henning, what do you think about changing the test-backend. As far
> as I understood, the test-backend simulates, when the reader-process
> has finished, a "hanging" backend, that is "killed" by the parent process.
> Probably we can accept a workaround only for the MacOS platform...
I think that generally there should be no OS-specific code in the
backends at all. The whole idea of sanei_thread and the other sanei_
code is to abstract the OS and hardware access.
The idea behind the "hanging" reader process is that the SANE standard
wants the backend to close the select filedescriptor at the end of the
scan. That's done by the test backend.
Some time ago we had trouble with frontends that couldn't cope with
closing the select file descriptor. This descriptor is usually a pipe
and is it not enough to close the reader process part of that pipe.
The parent process side has to be close and that's the signal for the
frontend that scanning is finished (no more data).
If the reader process doesn't hang until sane_cancel, there is a race
condition between closing both sides of the pipe. To make sure that
all frontends can cope with closing only the main process side of the
pipe, the reader process waits.
So if a frontend (or sanei_ implementation) can't cope with that,
there is usually a general problem that just don't happen that often
with other backends because most of the time the reader process
terminates too fast.
However, with threads I guess a file descriptor isn't closed after
exiting the thread (?). In this case we can ignore that problem so I
don't mind removing the endless loop if we are using threads in the
test backend.
I don't know about the patch concerning sanei_thread itsself as I'm
rather clueless about threads :-)
Generally speaking, this should be fixed where it is broken. If there
are simple and not too ugly workarounds in SANE, that's ok for me. But
otherwise I guess it's "not our fault".
Bye,
Henning
From henrik at rintala.de Sun Jan 11 20:54:53 2004
From: henrik at rintala.de (Henrik Rintala)
Date: Sun, 11 Jan 2004 21:54:53 +0100
Subject: [sane-devel] Scanning with CanoScan N650U under Mac OS X 10.3.2
Message-ID: <67AF90F8-4478-11D8-BA9F-0030655567DA@rintala.de>
I could not get sane to work. But I by chance found another solution
for me. Anyone who has a .mac membership can get the Mac OS X version
of ArcSoft Photostudio for free. And if you download the appropriate
Photoshop plugin from Canon for the N650U you can put the plug-in file
into Photostudio's plugin folder and scan with Photostudio for free.
Works for basic scanning. The plugin also works with Graphicconverter
(shareware app).
//
\\ Henrik Rintala
//
From dave at dminor.com Sun Jan 11 22:03:47 2004
From: dave at dminor.com (David Minor)
Date: Sun, 11 Jan 2004 16:03:47 -0600
Subject: [sane-devel] Re: OS X and umax 1220u
In-Reply-To: <20040111141541.GB683@meier-geinitz.de>
References: <20040110100640.GB978@meier-geinitz.de> <20040111141541.GB683@meier-geinitz.de>
Message-ID: <07BBF9FD-4482-11D8-9548-000393B4CC12@dminor.com>
some info may be repeated as I'm cross-posting to the backend devel
list.
On Jan 11, 2004, at 8:15 AM, Henning Meier-Geinitz wrote:
> On Sat, Jan 10, 2004 at 04:38:59PM -0600, David Minor wrote:
>> I commented out everything in dll.conf but umax1220u, set USB debug
>> output to 255 in addition to the umax1220u debug at 128 as before. I
>> also disconnected all other USB devices to simplify matters. I'm not
>> going to pretend to being able to interpret the output, but I will
>> attach for anyone to look over and see if the problem can be isolated.
>
> I'm not the author of that backend so I may be completely wrong...
>
> However, this time you get a completely different error. Openeing the
> scanner works, but starting the scan doesn't:
>
>> [umax1220u] sane_start
>> [umax1220u] UMAX_set_scan_parameters:
>> [umax1220u] color = 1
>> [umax1220u] xo = 0, yo = 0
>> [umax1220u] w = 0, h = 0
>> [umax1220u] xres = 75, yres = 75
>> [umax1220u] left = 0, top = 0
>> [umax1220u] right = 0, bottom = 0
>> scanimage: sane_start: Invalid argument
>
> There is no tranfer to the scanner involved at all. Looks like a
> backend bug. It sets widths and height to 0 by default.
>
> Try again with scanimage but set width and height explicitely to e.g.
> 10 mm (see scanimage --help for details).
>
versions:
scanner: umax 1220u
system: OS X 10.3.2
scanimage (sane-backends) 1.0.13; backend version 1.0.13 (patched)
TWAIN SANE interface: 0.3
libusb: 0.1.8 beta 2004-01-05
$ scanimage -L
device `umax1220u:libusb:001:004' is a UMAX Astra 1220U flatbed scanner
$ scanimage -T
scanimage: sane_start: Invalid argument
$ scanimage -x 200 -y 200
I can successfully scan if I pass width/height params. What a great
sound to hear this old dust collector chugging away!
Using TWAIN Acquire in Graphic Convertor still does not work. No
feedback from it at all. So it works, but not out of the box. It
would be great if I could find a way to 1) get TWAIN working and 2) get
the backend automatically come up with the dimensions needed.
Thanks, Henning, for your consistent review and prompt reply on this
list. Thanks to all the developers related to this process for keeping
at it.
I would be happy to continue to test/try things for the os x/umax 1220u
environment.
dm
From benedict.prescott at virgin.net Sun Jan 11 20:42:09 2004
From: benedict.prescott at virgin.net (Ben Prescott)
Date: Sun, 11 Jan 2004 20:42:09 +0000
Subject: [sane-devel] Trust Imagery 9600
In-Reply-To: <1073476817.1987.29.camel@gk-lex3>
References: <20040105231501.35fe567c.benedict.prescott@virgin.net>
<1073476817.1987.29.camel@gk-lex3>
Message-ID: <20040111204209.6db53bfd.benedict.prescott@virgin.net>
On Wed, 07 Jan 2004 11:00:18 -0100
gerard klaver wrote:
> see the teco mailinglist at yahoo, also mail archive is present.
> To get this scanner working you have to patch the following files
> teco3.conf with the name of the scanner:
> scsi "Aashima" "IMAGERY 9600SP"
> Frank Zago (teco3 maintaniner) should be able to tell more about the
> changes which are needed to get this scanner working.
thanks; gives me something to be getting on with. It'll be a while, but
I guess no-one else is missing it!
regards, Ben.
From Sanjay.Chigurupati at lntinfotech.com Mon Jan 12 04:18:40 2004
From: Sanjay.Chigurupati at lntinfotech.com (Sanjay Chigurupati)
Date: Mon, 12 Jan 2004 09:48:40 +0530
Subject: [sane-devel] HP Scanjet 3670...
Message-ID:
Hi,
I tried contacting HP too. Had met Bdale garbee at Linux Bangalore meet. he
said he would try to see if he could help. will send him one more e-mail
and see if it works. also tried contacting one of the R &D people. Bdale
said that some of the scanner chipsets are from 3rdparty and may have
non-disclosure agreement.
Regards,
Sanjay
Mickael Profeta