Date: Sun, 07 Dec 2003 14:59:14 -0700 From: Aaron <aaron@justaaron.com> To: freebsd-questions@freebsd.org Subject: /dev/ulpt0: Device not configured Message-ID: <3FD3A2B2.2090401@justaaron.com>
next in thread | raw e-mail | index | archive | help
I can't figure out how to bind my usb printer to ulpt0,
rather than ugen1 as it is now.
My physical setup:
first usb port: logitech wingman hub
second usb port: HP OfficeJet K80xi
The hub has an HP 7400c scanjet, and the cable for a camera,
with nothing currently connected to the cable. In a
previous freebsd install with this same setup, I've
downloaded pictures through that cable, haven't tried that
yet with this install. Never tried scanning.
But back to printing ...
Here's my failure indication (besides not printing). I'm
using apsfilter to set up my printer. When I try printing a
test page I get this:
Printing test page...
-rw-r--r-- 1 root wheel 3808147 Dec 7 13:56
/tmp/apsfilter320/test_page.aps
/usr/local/share/apsfilter/SETUP: line 1: /dev/ulpt0: Device not
configured
So I guess I have to figure out what "Device not configured"
means, and how to fix it.
I'm using the generic kernel supplied with FreeBSDMall's 4.9
CD set
# uname -a
FreeBSD haiku.krelm.com 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Oct
27 17:51:09 GMT 2003
root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC i386
All manner of usb is enabled in the generic kernel,
/usr/src/sys/i386/conf/GENERIC:
# USB support
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device usb # USB Bus (required)
device ugen # Generic
device uhid # "Human Interface Devices"
device ukbd # Keyboard
device ulpt # Printer
device umass # Disks/Mass storage - Requires scbus
and da
device ums # Mouse
device uscanner # Scanners
device urio # Diamond Rio MP3 Player
# USB Ethernet, requires mii
device aue # ADMtek USB ethernet
device cue # CATC USB ethernet
device kue # Kawasaki LSI USB ethernet
Some dmesg output:
# dmesg | grep -i ugen
ugen0: hp hp scanjet 7400c, rev 1.00/0.01, addr 3
ugen1: Hewlett-Packard OfficeJet K80xi, rev 1.00/1.00, addr 4
# dmesg | grep -i usb
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x1080-0x109f
irq 9 at device 7.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.00/1.00, addr 2
# dmesg | grep -i ulpt
#
# dmesg | grep -i lpt
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
usbdevs output:
# usbdevs -dv
Controller /dev/usb0:
addr 1: self powered, config 1, UHCI root hub(0x0000), Intel(0x0000),
rev 1.00
uhub0
port 1 addr 2: power 100 mA, config 1, UT-USB41 hub(0x1446), Texas
Instruments(0x0451), rev 1.00
uhub1
port 1 addr 3: self powered, config 1, hp scanjet 7400c(0x0801),
hp(0x03f0), rev 0.01
ugen0
port 2 powered
port 3 powered
port 4 powered
port 2 addr 4: self powered, config 1, OfficeJet K80xi(0x0811),
Hewlett-Packard(0x03f0), rev 1.00
ugen1
At this point let me ask, if a new entry in /etc/usbd.conf
turns out to be the solution, would the values shown above
for port 2 addr 4 be plugged into that entry? If so, how to
translate the rev 1.00 to usbd.conf format? Finally, if
that *is* the solution, would anyone care to post their
entry for a usb printer?
Back to the data:
If I unplug the cable from the printer, the console says
this, immediately:
ugen1: at uhub0 port 2 (addr 4) disconnected
ugen1: detached
Plugging the cable back in gets this on the console,
immediately:
ugen1: Hewlett-Packard OfficeJet K80xi, rev 1.00/1.00, addr 4
After disconnecting and connecting the cable, here's what
dmesg says, which appears to be a combination of what it
said before disconnect/connect, plus the console message
just reported:
# dmesg | grep -i ugen
ugen0: hp hp scanjet 7400c, rev 1.00/0.01, addr 3
ugen1: Hewlett-Packard OfficeJet K80xi, rev 1.00/1.00, addr 4
ugen1: at uhub0 port 2 (addr 4) disconnected
ugen1: detached
ugen1: Hewlett-Packard OfficeJet K80xi, rev 1.00/1.00, addr 4
The rest of dmesg wrt to usb hasn't changed.
Here's my devices:
# ll ulpt* unlpt* ugen*
crw-rw---- 1 root operator 114, 0 Nov 26 11:07 ugen0
crw-rw---- 1 root operator 114, 1 Nov 26 11:07 ugen0.1
crw-rw---- 1 root operator 114, 10 Nov 26 11:07 ugen0.10
crw-rw---- 1 root operator 114, 11 Nov 26 11:07 ugen0.11
crw-rw---- 1 root operator 114, 12 Nov 26 11:07 ugen0.12
crw-rw---- 1 root operator 114, 13 Nov 26 11:07 ugen0.13
crw-rw---- 1 root operator 114, 14 Nov 26 11:07 ugen0.14
crw-rw---- 1 root operator 114, 15 Nov 26 11:07 ugen0.15
crw-rw---- 1 root operator 114, 2 Nov 26 11:07 ugen0.2
crw-rw---- 1 root operator 114, 3 Nov 26 11:07 ugen0.3
crw-rw---- 1 root operator 114, 4 Nov 26 11:07 ugen0.4
crw-rw---- 1 root operator 114, 5 Nov 26 11:07 ugen0.5
crw-rw---- 1 root operator 114, 6 Nov 26 11:07 ugen0.6
crw-rw---- 1 root operator 114, 7 Nov 26 11:07 ugen0.7
crw-rw---- 1 root operator 114, 8 Nov 26 11:07 ugen0.8
crw-rw---- 1 root operator 114, 9 Nov 26 11:07 ugen0.9
crw-rw---- 1 root operator 114, 16 Dec 6 06:07 ugen1
crw-rw---- 1 root operator 114, 17 Dec 6 06:07 ugen1.1
crw-rw---- 1 root operator 114, 26 Dec 6 06:07 ugen1.10
crw-rw---- 1 root operator 114, 27 Dec 6 06:07 ugen1.11
crw-rw---- 1 root operator 114, 28 Dec 6 06:07 ugen1.12
crw-rw---- 1 root operator 114, 29 Dec 6 06:07 ugen1.13
crw-rw---- 1 root operator 114, 30 Dec 6 06:07 ugen1.14
crw-rw---- 1 root operator 114, 31 Dec 6 06:07 ugen1.15
crw-rw---- 1 root operator 114, 18 Dec 6 06:07 ugen1.2
crw-rw---- 1 root operator 114, 19 Dec 6 06:07 ugen1.3
crw-rw---- 1 root operator 114, 20 Dec 6 06:07 ugen1.4
crw-rw---- 1 root operator 114, 21 Dec 6 06:07 ugen1.5
crw-rw---- 1 root operator 114, 22 Dec 6 06:07 ugen1.6
crw-rw---- 1 root operator 114, 23 Dec 6 06:07 ugen1.7
crw-rw---- 1 root operator 114, 24 Dec 6 06:07 ugen1.8
crw-rw---- 1 root operator 114, 25 Dec 6 06:07 ugen1.9
crw------- 1 root wheel 113, 0 Dec 7 13:56 ulpt0
crw------- 1 root wheel 113, 1 Dec 6 06:11 ulpt1
crw------- 1 root wheel 113, 64 Dec 3 11:45 unlpt0
crw------- 1 root wheel 113, 65 Dec 6 06:10 unlpt1
# ll usb*
crw-rw---- 1 root operator 108, 255 Nov 26 11:07 usb
crw-rw---- 1 root operator 108, 0 Nov 26 11:07 usb0
So, is that enough? Any suggestions, or requests for more
information?
Thanks.
--
Aaron
aaron@justaaron.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FD3A2B2.2090401>