[sane-devel] Accessing scanner through libusb fails with invalid argument
On Thu, 2005-03-10 at 23:56 +0100, Sebastian Reichelt wrote: Hello! I have a Tevion MD9458 scanner which I would like to get to work with Linux. Apparently it is supported by SANE, and sane-find-scanner detects it correctly. However, when I try to access it with xsane or scanimage, I get the message: open of device gt68xx:libusb:002:... failed: Invalid argument This happens when I am root or a normal user with appropriate permissions. The right number increases every time I try this, as somehow the file /proc/bus/usb/002/027 disappears and a new file /proc/bus/usb/002/028 appears, and so on. In syslog, there is also the message: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 192 rq 1 le n 64 ret -84 And when I do an strace, there are a lot of lines that look like this: ioctl(3, USBDEVFS_CONTROL, 0xbfffc790) = 64 I'm using a 2.6.10 custom-built kernel and the current SANE and libusb drivers from Debian testing (Debian version numbers are 1.0.15-6 for libsane and 0.1.10-2 for libusb-0.1-4, whatever that means). USB works, and I can also access a digital camera with libusb. I hope this is enough information so you can help me with this problem. Thanks in advance. -- Sebastian Reichelt To get some debug info type: export SANE_DEBUG_GT68XX=128 and then type xsane or xscanimage or scanimage and check the logs. See this page for some backend info (maybe done already?) http://www.meier-geinitz.de/sane/gt68xx-backend/ and check your gt68xx.conf file on the override artec-ultima-2000 option and check your firmware file? -- m.vr.gr. Gerard Klaver
[sane-devel] Accessing scanner through libusb fails with invalid argument
Hello! I got a different firmware (from a CD), and now it works. Thanks a lot! -- Sebastian Reichelt
[sane-devel] Accessing scanner through libusb fails with invalid argument
Hello! I have a Tevion MD9458 scanner which I would like to get to work with Linux. Apparently it is supported by SANE, and sane-find-scanner detects it correctly. However, when I try to access it with xsane or scanimage, I get the message: open of device gt68xx:libusb:002:... failed: Invalid argument This happens when I am root or a normal user with appropriate permissions. The right number increases every time I try this, as somehow the file /proc/bus/usb/002/027 disappears and a new file /proc/bus/usb/002/028 appears, and so on. In syslog, there is also the message: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 192 rq 1 le n 64 ret -84 And when I do an strace, there are a lot of lines that look like this: ioctl(3, USBDEVFS_CONTROL, 0xbfffc790) = 64 I'm using a 2.6.10 custom-built kernel and the current SANE and libusb drivers from Debian testing (Debian version numbers are 1.0.15-6 for libsane and 0.1.10-2 for libusb-0.1-4, whatever that means). USB works, and I can also access a digital camera with libusb. I hope this is enough information so you can help me with this problem. Thanks in advance. -- Sebastian Reichelt
[sane-devel] Accessing scanner through libusb fails with invalid argument
Sebastian Reichelt wrote: Hello! I have a Tevion MD9458 scanner which I would like to get to work with Linux. Apparently it is supported by SANE, and sane-find-scanner detects it correctly. However, when I try to access it with xsane or scanimage, I get the message: open of device gt68xx:libusb:002:... failed: Invalid argument This happens when I am root or a normal user with appropriate permissions. The right number increases every time I try this, as somehow the file /proc/bus/usb/002/027 disappears and a new file /proc/bus/usb/002/028 appears, and so on. This happened to me before I learned that my kernel was loading hpusbscsi. There are apparently some problems with this module--documented in this list's archive. I recommend that you run `lsmod` to see if this module is loaded. If it is, here's what I did: 1. Turn off the scanner--I unplugged mine. 2. run `modprobe -r hpusbscsi 3. Turn on the scanner 4. `scanimage -L 5. `xscanimage` [backend-name]:libusb:AAA:BBB, where AAA:BBB would be 002:027 or 002:028 from your info above. If this works, rename hpusbscsi in your kernels driver directory and you might be good to go. If it's not hpusbscsi, I'm sorry that I don't have enough expertise to provide any other recommendations. Good luck, Dan
