Date: Mon, 15 Apr 2013 15:14:56 -0500 From: Joshua Isom <jrisom@gmail.com> To: Hans Petter Selasky <hps@bitfrost.no> Cc: freebsd-hackers@FreeBSD.org Subject: Re: USB Printer quirks Message-ID: <516C5FC0.9060507@gmail.com> In-Reply-To: <516BD94F.7030507@bitfrost.no> References: <5169DFFB.4030101@gmail.com> <516BD94F.7030507@bitfrost.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/15/2013 5:41 AM, Hans Petter Selasky wrote:
> Hi,
>
> What does dmesg say about your printer.
>
> Is cups hooked up the correct /dev/uxxx device ?
>
> --HPS
Here's what I got the last time I plugged it in.
Apr 13 07:38:17 jri root: Unknown USB device: vendor 0x040a product
0x4043 bus uhub7
Apr 13 07:38:17 jri kernel: ugen8.2: <Eastman Kodak Company> at usbus8
Apr 13 07:38:17 jri kernel: ulpt0: <Print> on usbus8
Apr 13 07:38:17 jri kernel: ulpt0: using bi-directional mode
Apr 13 07:38:17 jri kernel: umass0: <MSCD> on usbus8
Apr 13 07:38:17 jri kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000
Apr 13 07:38:17 jri kernel: umass0:14:0:-1: Attached to scbus14
Apr 13 07:38:17 jri kernel: (da0:umass-sim0:0:0:0): got CAM status 0x50
Apr 13 07:38:17 jri kernel: (da0:umass-sim0:0:0:0): fatal error, failed
to attach to device
Apr 13 07:38:17 jri kernel: (da0:umass-sim0:0:0:0): lost device - 0
outstanding, 4 refs
Apr 13 07:38:17 jri kernel: (da0:umass-sim0:0:0:0): removing device entry
The umass is probably for the card reader, I've never tried it with
FreeBSD. Cups would sometimes work, at most I'd be able to print one
document/test and then it'd hang. I would actually have to power cycle
the printer to try again. I think it was a problem reading from usb.
What I'm really curious about is why it would work properly in a linux
jail and not on FreeBSD. The closest hint I have is a kernel message
"linux: pid 8781 (usb): ioctl fd=5, cmd=0x604 ('^F',4) is not implemented".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?516C5FC0.9060507>