FC2 USB scanner - HP 6200

[msewing]

My HP ScanJet 6200C was working fine with FC1, using direct kernel support. Under FC2, it's really weird. sane-find-scanner gives "found USB scanner (vendor=0x03f0, product=0x0201) at libusb:002:002" . So far, so good.

Now scanimage -L (run as root) gives one of 3 responses:
1. Segmentation fault
2. device `hp:libusb:002:002' is a Hewlett-Packard ScanJet 62x0C flatbed scanner (good!), or
3. No scanners were identified....

I get all 3 responses randomly as I retry 'scanimage -L'. I have tried reorganizing my USB ports, power cycling, etc. - same kind of thing.

/var/log/messages (after my su to root):
May 21 10:43:57 localhost kernel: ppdev: user-space parallel port driver
May 21 10:44:05 localhost kernel: usb 1-1: control timeout on ep0out
May 21 10:45:22 localhost last message repeated 4 times
May 21 10:45:44 localhost last message repeated 4 times
May 21 10:45:54 localhost kernel: usb 1-1: USB disconnect, address 3
May 21 10:45:58 localhost kernel: usb 2-1: new full speed USB device using address 2
May 21 10:46:43 localhost kernel: usb 2-1: control timeout on ep0in
May 21 10:46:44 localhost kernel: usb 2-1: control timeout on ep0in
May 21 10:46:59 localhost kernel: usb 2-1: control timeout on ep0out
May 21 10:47:18 localhost last message repeated 2 times

All this is on an ASUS A7V8X-MX, Athlon 2000+, 1 GB RAM, etc., etc.

TIA for any clues! - Martin

p.s. Here is my 'lsmod'

Module Size Used by
ppdev 5888 0
sd_mod 16384 0
snd_ens1371 17120 1
snd_mixer_oss 13824 2
snd_via82xx 19104 4
snd_pcm 68872 2 snd_ens1371,snd_via82xx
snd_timer 17156 1 snd_pcm
snd_ac97_codec 50436 2 snd_ens1371,snd_via82xx
snd_page_alloc 7940 2 snd_via82xx,snd_pcm
gameport 3328 2 snd_ens1371,snd_via82xx
snd_mpu401_uart 4864 1 snd_via82xx
snd_rawmidi 17184 2 snd_ens1371,snd_mpu401_uart
snd_seq_device 6152 1 snd_rawmidi
snd 38372 15 snd_ens1371,snd_mixer_oss,snd_via82xx,snd_pcm,snd_ timer,snd_ac97_codec,snd_mpu401_uart,snd_rawmidi,s nd_seq_device
soundcore 6112 3 snd
w83781d 26240 0
eeprom 6024 0
i2c_sensor 2176 2 w83781d,eeprom
i2c_isa 1792 0
i2c_viapro 5388 0
i2c_core 16388 5 w83781d,eeprom,i2c_sensor,i2c_isa,i2c_viapro
vmnet 25360 4
vmmon 41912 0
parport_pc 19392 1
lp 8236 0
parport 29640 3 ppdev,parport_pc,lp
nfsd 158496 9
exportfs 4224 1 nfsd
lockd 47944 2 nfsd
ipv6 184288 10
autofs4 10624 1
sunrpc 101064 19 nfsd,lockd
via_rhine 15624 0
mii 3584 1 via_rhine
floppy 47440 0
sg 27552 0
scsi_mod 91344 2 sd_mod,sg
dm_mod 33184 0
ehci_hcd 21896 0
uhci_hcd 23708 0
button 4504 0
battery 6924 0
asus_acpi 8472 0
ac 3340 0
ext3 102376 4
jbd 40216 1 ext3

[msewing]

Well, this looks like a Kernel 2.6 / USB problem. I got the very newest SANE source (0.94 backends etc) and compiled and installed same. No change in behavior. That's the bad news.

The good news is that this scanner has a SCSI personality, and when I hook it up with a SCSI card, it works.

More good news: I have a very shiny bit of software. More bad news: My SCSI cable is too short...

-mse

[inti]

I have the same scanner, also worked fine in FC 1. I have the same problem you describe, except for the fact that the scanner is consistently recognized by 'scanimage -L'. So I always get:

device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 62x0C flatbed scanner

However, whenever I run scanimage or xsane, it get the following error: "scanimage: unable to determine option count" . I found a similar problem to this with the Mustek backend on the sane-devel list. Unfortunately, it looks like it might be time to fall back to an older version of sane.

Matt