Le vendredi 29 juillet 2011 22:51:01 KasperH, vous avez ?crit :
> my HP ScanJet 3670 is not working under Fedora14. It used to work,
> when I was running WinXP on the same hardware. It is still working
> fine connected to my WinXP laptop's
>
> troubleshooting I've done so far:
>
> [root at fedje ~]# yum list installed | grep -i sane
> sane-backends.i686 1.0.22-3.fc14 @updates
> sane-backends-libs.i686 1.0.22-3.fc14 @updates
> sane-backends-libs-gphoto2.i686 1.0.22-3.fc14 @updates
> sane-frontends.i686 1.0.14-10.fc14 @fedora
> xsane.i686 0.998-4.fc14
> @updates xsane-common.i686 0.998-4.fc14
> @updates [root at fedje ~]# sane-find-scanner
> ...
> found USB scanner (vendor=0x03f0, product=0x1405, chip=GL646_HP?) at
> libusb:002:002
> ...
> [root at fedje ~]# scanimage --version
> scanimage (sane-backends) 1.0.22; backend version 1.0.22
> [root at fedje ~]# scanimage -L
> No scanners were identified.
> ...
> [root at fedje ~]# lsusb
> ...
> Bus 002 Device 002: ID 03f0:1405 Hewlett-Packard ScanJet 3670
> ...
> [root at fedje ~]# cat /proc/bus/usb/devices
> ...
> T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
> P: Vendor=03f0 ProdID=1405 Rev= 1.00
> S: Manufacturer=Hewlett-Packard
> S: Product=HP Scanjet Scanner
> S: SerialNumber=CN399S289R
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 48mA
> I:* If#= 0 Alt= 0 #EPs= 3 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
> E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=8ms
> ...
>
> in /etc/sane.d/genesys.conf
> # Hewlett Packard ScanJet 3670c/3690c
> usb 0x03f0 0x1405
>
> So all usb tools tell me, it is there, and it can be communicated with
> (serial#, pwr,)
> Is sane-find-scanner(1) not sure, why is the question mark (chip=GL646_HP?)
> scanimage -L does not detect it
>
> someone a clue why I cannot use this supported and working scanner
> under Fedora 14?
>
> Thanks for your time
> Kasper
Hello,
I had the same kind of problem with this scanner. In my case I am
suspecting an hardware/kernel combination as the root of the problem. Could
you run scanimage -L after setting USB debug traces with:
export SANE_DEBUG_SANEI_USB=255
scanimage -L 2>probe.log
and send the log ?
Regards,
Stef
