2011/8/1 stef wrote: > Le dimanche 31 juillet 2011 10:18:00 KasperH, vous avez ?crit : > Hello, > > I see nothing obvious USB wise. Can you raise genesys debug trace > level > and run scanimage -L again ? > export SANE_DEBUG_GENESYS=255 > export SANE_DEBUG_GENESYS_LOW=255 > export SANE_DEBUG_GENESYS_GL646=255 > scanimage -L 2>probe.log > > Then send the log. You can compress it to get the attachment > smaller. > > Regards, > Stef >
compressing, offcourse, why did I not think of that here follows the debugging result: [kas at fedje ~]$ lsusb | sort Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1058:1001 Western Digital Technologies, Inc. External Hard Disk [Elements] Bus 001 Device 005: ID 152d:2336 JMicron Technology Corp. / JMicron USA Technology Corp. Hard Disk Drive Bus 001 Device 006: ID 152d:2336 JMicron Technology Corp. / JMicron USA Technology Corp. Hard Disk Drive Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 03f0:1405 Hewlett-Packard ScanJet 3670 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [kas at fedje ~]$ export SANE_DEBUG_GENESYS=255 [kas at fedje ~]$ export SANE_DEBUG_GENESYS_LOW=255 [kas at fedje ~]$ export SANE_DEBUG_GENESYS_GL646=255 [kas at fedje ~]$ scanimage -L 2>probe.log 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). [kas at fedje ~]$ su - Password: [root at fedje ~]# export SANE_DEBUG_GENESYS=255 [root at fedje ~]# export SANE_DEBUG_GENESYS_LOW=255 [root at fedje ~]# export SANE_DEBUG_GENESYS_GL646=255 [root at fedje ~]# scanimage -L 2> ~kas/probe.log.root 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). [root at fedje ~]# Now I thought, if I tried an Ubuntu Live CD, why not try a Fedora 14 live CD, so I downloaded and burned one. to my surprise, it sees the scanner, and is able to scan! conclusion, my current Fedora 14 Workstation environment is not quite sane, I mean healthy. Since I will be building a new Fedora 14 environment (Amahi.org), with a vanilla Fedora 14 install, on different hardware (just got it in today, need to assemble it) and will hook the scanner to that, I'll wait and see how that goes. Thank you Kasper PS actual scanning with the TRUST does not work, although it is recognized by "scanimage -L" by the regular user, but that is some other matter, did not try it with the Live Fedora 14 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110801/f0c759fe/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: probe.log Type: application/octet-stream Size: 947 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110801/f0c759fe/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: probe.log.root Type: application/octet-stream Size: 947 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110801/f0c759fe/attachment-0001.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: probe.log.live Type: application/octet-stream Size: 935 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110801/f0c759fe/attachment-0002.obj>