Bug 33074
| Summary: | USB printer support does not detect printers | ||
|---|---|---|---|
| Product: | Base System | Reporter: | papowell |
| Component: | kern | Assignee: | joe <joe> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | papowell |
| Priority: | Normal | ||
| Version: | 4.4-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-bugs->joe Joseph, this area is of interest to you, no? State Changed From-To: open->feedback A lot has changed in the usb stack since this report. Can you confirm whether the problem still exists please? State Changed From-To: feedback->closed Feedback timed out. |
System: various, including ASUS A7V. Does not appear to be a motherboard/system issue. PRINTER: HP2200, HP Deskjet, Ricoh (i.e. - not a printer issue) Note: RedHat Linux does detection, as does MS 2000, so it does not appear to be defective combination Fix: I sure would like to know... How-To-Repeat: 1. start GENERIC system. Plug and Play USB support is enabled. 2. kill usbd (killall usbd) 3. start usbd: usbd -v -d usbd: opened /dev/usb0 usbd: reading configuration file /etc/usbd.conf usbd: opened /dev/usb usbd: detach event at 1008976442.172197000, product 0x0217, Hewlett Packard: vndr=0x03f0 prdct=0x0217 rlse=0x0100 clss=0x0000 subclss=0x0000 prtcl=0x0000 usbd: Found action 'Printer' for product 0x0217, Hewlett Packard usbd: attach event at 1008976447.059681000, HP LaserJet 2200, HewLett Packard: vndr=0x03f0 prdct=0x0217 rlse=0x0100 clss=0x0000 subclss=0x0000 prtcl=0x0000 usbd: Found action 'Printer' for HP LaserJet 2200, HewLett Packard usbd: Executing '/usr/bin/uprinter ${DEVNAME}' usbd.conf has the following added: # The entry below starts moused when a mouse is plugged in. Moused # stops automatically (actually it bombs :) when the device disappears. # device "Printer" class 0x0000 attach "/usr/bin/uprinter ${DEVNAME}" Note: /usr/bin/uprinter is just: #!/bin/sh echo "$0" "$@" >/tmp/log printenv >>/tmp/log exit 0 and we get in /tmp/log: /usr/bin/uprinter ugen0 DEVNAME=ugen0 ----- Basically, it appears that the ulpt driver is either not being called during the probing, or it is not detecting the HP printer. This is, as they say, VERY odd. However, /dev/ugen0.1 is attached to the printer, and you can write data to it. I am totally baffled.