Ive just purchased an HP PCM 2355 for a friend on the basis that HP printers and scanner are some of the best supported devices under linux. The printer installation went fine, but the scanner resists all attempts to make it work. I feel a right charlie as I recommended it! Even HP's support line keeps me hanging on at premium rate and then tells me my query is out of scope!

The operating system is fedora core 4, and I've installed sane and hplip. The printer works fine under cups.
Sorry if this post is long, I've tried to include all pertinent information.

[Hmm after preview its got to be cut by 75%, so its no longer got all the info in it, Darn! ]

The result of doing an lspci is as follows:

00:00.0 Host bridge: Intel Corporation 82810 GMCH [Graphics Memory Controller Hub] (rev 03)
00:01.0 VGA compatible controller: Intel Corporation 82810 CGC [Chipset Graphics Controller] (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02)
00:1f.2 USB Controller: Intel Corporation 82801AA USB (rev 02)
00:1f.3 SMBus: Intel Corporation 82801AA SMBus (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio (rev 02)
00:1f.6 Modem: Intel Corporation 82801AA AC'97 Modem (rev 02)
01:03.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
01:04.0 USB Controller: NEC Corporation USB (rev 41)
01:04.1 USB Controller: NEC Corporation USB (rev 41)
01:04.2 USB Controller: NEC Corporation USB 2.0 (rev 02)

the result of uname -r is as follows:
2.6.11-1.1369_FC4

The results of dmesg are asfollows: note that this is not after a recent boot, but contains some intresting stuff that I dont understand:

[ posted here, wont let me post urls, so have added some spaces to obfurscate: h t t p : / / w w w . jetmark.co.uk/Mark/.tmp/dmesg.txt ]

Perhaps I should mention that the machine has a USB card in it that the scanner is pluggeed in to an original usb socket.
Is that what the last lines in the dmsg log mean ?

The result of doing a sane-find-scanner as non root or root is as follows:
Note that I have the following 2 variables set to help me figure out what is going on:
SANE_DEBUG_HP=128
SANE_DEBUG_SANEI_USB=128


[sanei_debug] Setting debug level of sanei_usb to 128.
usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 006 on 004
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 001
[sanei_usb] sanei_usb_init: found libusb device (0x03f0/0x4911) interface 0 at libusb:004:006
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
[sanei_usb] sanei_usb_init: found 1 devices
[sanei_usb] sanei_usb_open: trying to open device `/dev/usb/scanner'
[sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner' in list
[sanei_usb] sanei_usb_open: trying to open device `/dev/usb/scanner0'
[sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner0' in list

snip!

[sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner15' in list
[sanei_usb] sanei_usb_open: trying to open device `/dev/usbscanner'
[sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner' in list
[sanei_usb] sanei_usb_open: trying to open device `/dev/usbscanner0'
[sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner0' in list
[sanei_usb] sanei_usb_open: trying to open device `/dev/usbscanner1'

[sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner15' in list

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating system.
# If using Linux, try "modprobe sg".

found USB scanner (vendor=0x03f0 [HP], product=0x4911 [PSC 2350 series]) at libusb:004:006
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.

# Not checking for parallel port scanners.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.


This seems ok to me.

I have modified the file /etc/sane.d/hp.dll by adding the following 3 lines:

# Markw added
# for HP PSC 2355
usb 0x03f0 0x4911

These seemed to be called for by various documentations that I found. Not sure if its really necessary.

Now I try scanimage -L

This instantly and quietly exits with no message and exit status 141 when run as root or user


If I do scanimage -d hp

Then the first time I do this after power cycling the printer I get an assertion failure, subsequent times, it just hangs. In both cases there seem to be protocol errors. This is what I get after a power cycle:

[ posted here, wont let me post urls, so have added some spaces to obfurscate:
h t t p : / / w w w . jetmark.co.uk/Mark/.tmp/scanimage.txt ]

Repeating this gives a hang, at a similar protocol error rather earlier in the proceedings. Running scanimage without the -d gives no output and a very quick termination.

I'm running this as root, as a user there seems to be a permissions issue that prevents it getting so far.

Does anyone one have any clues about this ?

Seems like I should just give up on this one and take the printer back to the shop? Recommend that my friend uses windows?