Hi Tim and the group,
I'm not sure what version of the snapscan 1212u you are running, but mine
(a 1212u_2) requires a firmware download before it is recognized by the
sane code. Is the led on the front of your scanner indicating steady on?
This
means the scanner is ready for commands. If it is flashing, it means busy
and if
it flashes out a code, then it is confused with some kind of error.
I dont have the link handy, but there is a download script for loading the
scanner
firmware. I wonder if we should consider adding this code to sane... I keep
forgetting how to load mine. It is on a ups and on all the time, so it is
typically
months between reloading the firmware. I havent had a chance to test the new
backend yet.
Any recommendations as to what kernel would be best to try? I have
2.4.0-test9
running at the moment.
=======================================================
Lawrence Glaister VE7IT email: lg@jfm.bc.ca
1462 Madrona Drive http://jfm.bc.ca
Nanoose Bay BC Canada
V9P 9C9
=======================================================
----- Original Message -----
From: Timothy Little <tim@lilly-villa.little-possums.net>
To: <sane-devel@mostang.com>
Sent: Friday, November 03, 2000 11:59 PM
Subject: Re: [snapscan] Core testing group
> On Fri, Nov 03, 2000 at 10:04:46PM -0600, Chris Bagwell wrote:
> > I'm assuming the U in 1212U is for USB, right? You mention at the end
> > that you got it working with an older USB patched sane-1.0.3. The debug
> > below shows that you've still got SCSI support compiled into your SANE
> > drivers instead of USB support for the snapscan driver.
>
> OK, thanks for the info. I've touched snapscan.c, recompiled and
> re-installed. At least I get "usb_open" appearing in my debug output
> now. This time I get the following results from "scanimage -T":
>
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=32768 bytes
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [snapscan] add_device(/dev/usbscanner)
> [snapscan] usb_open(/dev/usbscanner)
> [snapscan] mini_inquiry
> [snapscan] sanei_usb_cmd(8,0xbfffe6b8,6,0xbfffe694,0xbfffe690 (36))
> [snapscan] atomic_usb_cmd(8,0xbfffe6b8,6,0xbfffe694,0xbfffe690 (36))
> [snapscan] usb_cmd(8,0xbfffe6b8,6,0xbfffe694,0xbfffe690 (36))
> [snapscan] usb_cmd: cmdlen=6, datalen=0
> [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00
>
> Here it hangs. After a couple of minutes, I tried "kill -9". After a
> another minute, still nothing. Eventually (a few more minutes), it
> stopped, saying "Killed".
>
> I tried it a few more times. On one occasion, it returned extra
> information after the above debug dump (still with no scanner
> activity at all):
>
> [snapscan] usb_write Only -1 bytes written
> [snapscan] mini_inquiry: sanei_scsi_cmd command failed: Error during
device I/O
> [snapscan] add_device: mini_inquiry failed with Error during device I/O.
> [snapscan] usb_close(8)
> [snapscan] sane_snapscan_get_devices (0xbffff7c4, 0)
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=32768 bytes
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=32768 bytes
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `option dump 1' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directory[sanei_debug] Setting debug level of sanei_scsi to 255.
> [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file
or directoryscanimage: no SANE devices found
> [snapscan] sane_snapscan_exit
>
>
> - Tim
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sat Nov 04 2000 - 00:05:36 PST