Date: Wed, 26 Mar 2008 22:33:18 -0400 From: Isaac Mushinsky <itz@mushinsky.net> To: freebsd-usb@freebsd.org Subject: Re: hplip setup problems Message-ID: <200803262233.18659.itz@mushinsky.net> In-Reply-To: <bbe9e35d0803260802t45b33f3bmfd61e5d4db618f6@mail.gmail.com> References: <bbe9e35d0803260802t45b33f3bmfd61e5d4db618f6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 26 March 2008 11:02:58 Isaac Mushinsky wrote: > I've tried freebsd-questions, but to no avail so far, so please excuse my > posting here in the hope to find people more familiar with this... > > I am having trouble setting up HP Photosmart C4280 all-in-one device for > printing. hpssd, cups are started in the correct order. Device node > permissions seem to be correct too. > > 1. This is an all-in-one device. (I did not try the scanner setup yet) > 2. ulpt, umass, uscanner modules are not in kernel and not kld-loaded. > 3. Machine is FreeBSD 7-stable/amd64. > 4. hplip is 2.8.2 > > $ usbdevs > addr 1: UHCI root hub, Intel > addr 1: UHCI root hub, Intel > addr 1: UHCI root hub, Intel > addr 1: EHCI root hub, Intel > addr 2: Photosmart C4200 series, HP > addr 1: UHCI root hub, Intel > addr 1: UHCI root hub, Intel > addr 1: UHCI root hub, Intel > addr 1: EHCI root hub, Intel > There is a ppd file for these series with the hplip distribution. > hpssd, cups started in the order needed. hp-setup detects the printer, and > then says 'Unable to create queue'. CUPS web interface actually adds the > printer, but then cannot print test page to it. cups user runs hpssd (I > tried root too). > /var/log/messages has: > Mar 25 23:57:56 omsk python: io/hpmud/musb.c 135: unable > get_string_descriptor -5: Input/output error > Mar 25 23:57:56 omsk python: io/hpmud/musb.c 1951: invalid serial id string > ret=-5 > > > With USB_DEBUG=4 (for libusb), the hp-setup fails like this: > > usb_os_find_devices: Found /dev/ugen0 on /dev/usb3 > usb_control_msg: 128 6 512 0 0x7fffffff9ed0 8 1000 > usb_control_msg: 128 6 512 0 0x80131d080 124 1000 > usb_control_msg: 128 6 770 1033 0x7fffffff9e40 255 5000 > usb_control_msg: 128 6 771 1033 0x7fffffff9e40 255 5000 > USB error: error sending control message: Input/output error > ... > device `hpaio:/usb/Photosmart_C4200_series?serial=0' is a Hewlett-Packard > Photosmart_C4200_series all-in-one > > This 'serial=0' seems to be the result of failed usb_control_msg call. > > I exhibited here all relevant output (/var/log/messages, usbdevs, ls -l > /dev etc.): > http://omsk.mushinsky.net/hplip-trouble > > Any help is appreciated. > -isaac- Latest piece of information, in case it helps solve the puzzle: sane cannot open the HP all-in-one as a scanner with same error (getting serial id). However, my Nikon LS40-ED (a 35mm film scanner) works fine. So the problem is apparently not my installation or libusb. ~> sane-find-scanner # 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. found USB scanner (vendor=0x04b0 [Nikon], product=0x4000 [LS-40 ED]) at libusb:/dev/usb2:/dev/ugen1 found USB scanner (vendor=0x03f0 [HP], product=0x5c11 [Photosmart C4200 series]) at libusb:/dev/usb3:/dev/ugen0 # 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. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. The Nikon scanner works, the HP device fails to return serial id as above. So it seems the Photosmart really fails to return a serial id. This does not seem to be an outright violation of USB standard, does it? At least once upon a time vendors were allowed not to provide id's. Then either (a) hplip should catch the failure and deal with it. Or, (b) hplip being HP-specific knows that HP always has a serial id; then the printer must be really busted.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803262233.18659.itz>