Subject: Re: using a printer with usb -> parallel cable
To: None <netbsd-help@netbsd.org>
From: Russell McManus <russell_mcmanus@yahoo.com>
List: netbsd-help
Date: 10/16/2003 12:42:54
After a cold reboot, I am able to print now. I didn't change a thing
in the configuration, and I've tried rebooting before, too.
But I think I figured out a quirk with my HP laserjet 6L, which
doesn't seem to make a difference with windows, but does with NetBSD.
There is a power button on the front of the printer, which I normally
don't have to mess with. When you press the power button, a little
led turns green, and stays on for a while until the printer shuts
itself off automatically a little while later. If the led is green,
and you press the power button again, a test page comes out of the
printer.
I think that the difference this time might be that when I rebooted, I
had the led in the green state, and I did not when I rebooted
previously. I only figured this out after monkeying with the printer
quite a bit; I've never needed to do anything with the power button
before to get the printer to work.
Sorry for the noise to the list. I mention the above details for
future googling.
-russ
russell_mcmanus@yahoo.com (Russell McManus) writes:
> perry@piermont.com (Perry E. Metzger) writes:
>
>> Russell McManus <russell_mcmanus@yahoo.com> writes:
>>> ulpt0 at uhub0 port 1 configuration 1 interface 0
>>> ulpt0: Keyspan UP-6C Keyspan UP-6C Printer Cable, rev 1.00/2.02, addr 2, iclass 7/1
>>> ulpt0: using bi-directional mode
>>>
>>> Looks promising. So I print something with lpq, and nothing comes
>>> out. Here is output from lpq:
>>
>> A fix was put in by Lennart just last night that may address this
>> problem. Could you try out the latest ulpt from current and see if it
>> fixes things for you?
>>
>>> thelonious.dyndns.org:/var/log [54] # lpq
>>> waiting for lp to become ready (offline ?)
>>> Rank Owner Job Files Total Size
>>> 1st russe 0 (standard input) 33228 bytes
>
> I've taken your suggestions, and I'm running netbsd.GENERIC from
> releng 20030928 directory right now, and the problem persists.
>
> Clearly, I am missing something very simple, because this seems to
> work for other folks. Argghh!!
>
> -russ