Dear misc@ readers,
I'm not sure if the topic is more suited for misc@ or ports@; I opted
for the former, 'cause I don't know if the problem is related to the
hplip ports or some other parts of the OS; if it's the case, please move
the thread.
OBSD -current here, just a slightly outdated snapshot:
just22@poseidon:[~]> uname -a
OpenBSD poseidon.atlantide.net 5.7 GENERIC.MP#875 amd64
I have an old HP multifunctional printer (Deskjet F4280); both printer
and scanner always worked (from 5.4 on).
Now I'm facing a lot of troubles; printer is not working with CUPS (but
that's another story: [0] - I worked around reverting on lpd and
using the PPD from hpijs).
And the scanner is not usable, too.
USB connection seems ok:
just22@poseidon:[~]> usbdevs -dv
Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
Intel(0x8086), rev 1.00
uhub2
port 1 powered
port 2 powered
port 3 powered
port 4 powered
Controller /dev/usb1:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
Intel(0x8086), rev 1.00
uhub6
port 1 addr 2: high speed, self powered, config 1, USB2.0 Hub(0x0608), Genesys
Logic(0x05e3), rev 9.01
uhub7
port 1 addr 3: high speed, self powered, config 1, USB2.0 Hub(0x0608),
Genesys Logic(0x05e3), rev 9.01
uhub8
port 1 powered
port 2 addr 4: low speed, power 100 mA, config 1, HP Basic USB
Keyboard(0x0024), CHICONY(0x03f0), rev 3.00
uhidev0
port 3 addr 5: high speed, self powered, config 1, Deskjet F4200
series(0x2504), HP(0x03f0), rev 1.00, iSerialNumber CN8C54F12J05BR
ulpt0
ugen0
port 4 powered
port 2 addr 6: low speed, power 98 mA, config 1, USB-PS/2 Optical
Mouse(0xc050), Logitech(0x046d), rev 27.20
uhidev1
port 3 addr 7: full speed, power 100 mA, config 1, product 0x089d(0x089d),
Logitech(0x046d), rev 1.00
uaudio0
ugen1
port 4 powered
[...]
All the relevant packages are installed:
just22@poseidon:[~]> pkg_info -a | egrep "hp|sane"
hpaio-3.15.2 HP sane(7) scanner backend
hpijs-3.15.2 HP ghostscript driver (spooler independent)
hplip-common-3.15.2 HPLIP applications common files
sane-backends-1.0.24p2 API for accessing scanners, backends
xsane-0.999p0-gimp scanner frontend for SANE
Device permissions are ok,too (and my user is in the _saned group):
just22@poseidon:[~]> ll /dev/ugen0.*
crw-rw---- 1 root _saned 63, 0 Mar 6 17:45 /dev/ugen0.00
crw-rw---- 1 root _saned 63, 1 Mar 6 17:45 /dev/ugen0.01
crw-rw---- 1 root _saned 63, 2 Mar 6 17:45 /dev/ugen0.02
crw-rw---- 1 root _saned 63, 3 Mar 6 17:45 /dev/ugen0.03
crw-rw---- 1 root _saned 63, 4 Mar 6 17:45 /dev/ugen0.04
crw-rw---- 1 root _saned 63, 5 Mar 6 17:45 /dev/ugen0.05
crw-rw---- 1 root _saned 63, 6 Mar 6 17:45 /dev/ugen0.06
crw-rw---- 1 root _saned 63, 7 Mar 6 17:45 /dev/ugen0.07
crw-rw---- 1 root _saned 63, 8 Mar 6 17:45 /dev/ugen0.08
crw-rw---- 1 root _saned 63, 9 Mar 6 17:45 /dev/ugen0.09
crw-rw---- 1 root _saned 63, 10 Mar 6 17:45 /dev/ugen0.10
crw-rw---- 1 root _saned 63, 11 Mar 6 17:45 /dev/ugen0.11
crw-rw---- 1 root _saned 63, 12 Mar 6 17:45 /dev/ugen0.12
crw-rw---- 1 root _saned 63, 13 Mar 6 17:45 /dev/ugen0.13
crw-rw---- 1 root _saned 63, 14 Mar 6 17:45 /dev/ugen0.14
crw-rw---- 1 root _saned 63, 15 Mar 6 17:45 /dev/ugen0.15
just22@poseidon:[~]> groups
just22 wheel operator wsrc _saned
I added the hpaio backend to sane's dll.conf:
just22@poseidon:[~]> grep hp /etc/sane.d/dll.conf
hp
hpaio
hp3900
#hpsj5s
hp3500
hp4200
hp5400
hp5590
hpljm1005
scanimage correctly recognize the scanner:
just22@poseidon:[~]> scanimage -L
device `hpaio:/usb/Deskjet_F4200_series?serial=CN8C54F12J05BR' is a
Hewlett-Packard Deskjet_F4200_series all-in-one
But when I try to scan (or also just launch xsane):
just22@poseidon:[~]> scanimage --format=tiff > ./scanner_test.tiff
Abort trap
This is what is reported in /var/log/messages:
just22@poseidon:[~]> tail /var/log/messages
Mar 11 10:05:59 poseidon scanimage: io/hpmud/musb.c 527: invalid
set_altinterface 7/1/2 altset=0: Invalid argument
Mar 11 10:05:59 poseidon scanimage: backwards memcpy
I tried the downgrade to hplip 3.14.6, which is the version used in
5.6-STABLE, but the result is exactly the same... (this is because I
don't think the problem is directly related to the new port version).
Any hints? Suggestions for further debugging are welcome, of course.
Thanks in advance for your time
[0] http://marc.info/?l=openbsd-misc&m=141761605715886&w=2
--
Alessandro DE LAURENZIS
[mailto:[email protected]]
LinkedIn: http://it.linkedin.com/in/delaurenzis