[Bug 277475] New: Sane gt68xx backend unable to scan on AMD64
https://bugzilla.novell.com/show_bug.cgi?id=277475 Summary: Sane gt68xx backend unable to scan on AMD64 Product: openSUSE 10.3 Version: Alpha 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mt@novell.com QAContact: qa@suse.de While it works fine with same configuration on a i686 Box, it fails to scan on x86_64 (AMD64 X2) completely. /etc/sane.d/gt68xx.conf: # Mustek ScanExpress 1200 UB Plus: override "mustek-scanexpress-1200-ub-plus" firmware "/etc/sane.d/firmware/sbfw.usb" # rpm -qa | grep sane sane-frontends-1.0.14-85 sane-backends-1.0.18-30 # scanimage scanimage: open of device gt68xx:libusb:002:004 failed: Invalid argument in /var/log/messages: May 23 18:02:57 xanthos kernel: usb 2-4.2: usbfs: interface 0 claimed by usbfs while 'xscanimage' sets config #1 May 23 18:03:10 xanthos kernel: usb 2-4.2: usbfs: USBDEVFS_CONTROL failed cmd xscanimage rqt 192 rq 1 len 64 ret -110 May 23 18:03:48 xanthos kernel: usb 2-4.2: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 192 rq 1 len 64 ret -110 May 23 18:04:31 xanthos kernel: usb 2-4.2: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 192 rq 1 len 64 ret -110 May 23 18:05:12 xanthos kernel: usb 2-4.2: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 192 rq 1 len 64 ret -110 May 23 18:13:32 xanthos kernel: usb 2-4.2: USB disconnect, address 4 May 23 18:13:32 xanthos kernel: usb 2-4.2: new full speed USB device using ehci_hcd and address 6 May 23 18:13:32 xanthos kernel: usb 2-4.2: new device found, idVendor=05d8, idProduct=4002 May 23 18:13:32 xanthos kernel: usb 2-4.2: new device strings: Mfr=0, Product=0, SerialNumber=0 May 23 18:13:32 xanthos kernel: usb 2-4.2: configuration #1 chosen from 1 choice -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=277475 ------- Comment #1 from mt@novell.com 2007-05-23 10:26 MST ------- Created an attachment (id=141786) --> (https://bugzilla.novell.com/attachment.cgi?id=141786&action=view) scanimage debug output export SANE_DEBUG_GT68XX=128 export SANE_DEBUG_DLL=4 export SANE_DEBUG_SANEI_USB=128 scanimage -d gt68xx:libusb:002:004 -T &>/tmp/scanimage.debug -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=277475 mt@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |jsmeix@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=277475 mt@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #2 from mt@novell.com 2007-05-23 10:46 MST ------- Ups... USB cable <= 1m and it works... sorry! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=277475 ------- Comment #3 from jsmeix@novell.com 2007-05-24 01:19 MST ------- Thanks for the valuable report. It is interesting for me to learn from attachment #141786 that an error message like ------------------------------------------------------------------------ USB error: error sending control message: Broken pipe [sanei_usb] sanei_usb_control_msg: libusb complained: error sending control message: Broken pipe ------------------------------------------------------------------------ could indicate that the actual reason could be the USB cable. I would never ever have thought about the cable because of such an error message. Only for your information: Regarding USB cable see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2#USB_Cabl... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=277475 ------- Comment #4 from mt@novell.com 2007-05-24 08:41 MST ------- Created an attachment (id=142055) --> (https://bugzilla.novell.com/attachment.cgi?id=142055&action=view) Success output I'm relieved to read that this report provided valuable info to you. In my first (few months ago) try, I've connected the scanner using ~2m cable extension to the new x86_64 machine (~3m all together). It didn't worked (same/similar Invalid argument and syslog messages), I was in a hurry, and I just connected it to the old (32bit) machine scanned and forgot to report it. The "scanimage: open of device gt68xx:libusb:002:004 failed: Invalid argument" let me suspect a 64bit problem. Now I remembered about and wanted to retest on 10.3 - "same problem". The difference was, that now there was a HUB between... there was no difference if the (optional) power supply of the HUB was connected or not. The scanner takes power via USB. This let me thinking, but after I already reported this Bug... I've connected it directly and voila, it works fine on both 10.2 and 10.3 as the attachment shows. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com