FS#15226 - [sane] gt68xx-backend doesn't work

Attached to Project: Arch Linux
Opened by Christian Galander (igprolin) - Tuesday, 23 June 2009, 12:49 GMT
Last edited by Paul Mattal (paul) - Monday, 09 November 2009, 12:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I would scan some images with my usb scanner but i can't use it.
i can configure it and scanimage -L find the scanner as user and root but they can't access the scanner.
my system is up2date with kernel 2.6.29-4
Firmware for the gt68xx backend is installed.
I attached the gt68xx.conf to this report.

i doesn't have a another scanner, to test it. All other devices are working like my mp3-player or keyboard and mouse.

scanimage -L:
[christian@Lin2Core ~]$ scanimage -L
device `gt68xx:libusb:002:004' is a Lifetec LT 9452 flatbed scanner

scanimage -T:
scanimage: open of device gt68xx:libusb:002:005 failed: Invalid argument

dmesg:
usb 2-2: new full speed USB device using ohci_hcd and address 4
usb 2-2: configuration #1 chosen from 1 choice
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd skanlite rqt 192 rq 1 len 64 ret -71
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd skanlite rqt 64 rq 1 len 64 ret -71
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd skanlite rqt 64 rq 1 len 64 ret -71
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd xsane rqt 64 rq 1 len 64 ret -71
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq 1 len 64 ret -71

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
Connect a scanner (gt68xx-backend) to the computer.
This task depends upon

Closed by  Paul Mattal (paul)
Monday, 09 November 2009, 12:04 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream. No responses in ~6 months. Please reopen if necessary.
Comment by Tobias Powalowski (tpowa) - Tuesday, 23 June 2009, 15:00 GMT
using a driver which needs firmware, might be related that firmware doesn't fit anymore.
Just a guess, also only enable the backend you use want to use that no other backend interferes here.

Loading...