Dakota Surmonde wrote:
> that wasn't the whole problem, though -- lpd *still* doesn't work, even
> though pdq works fine, once I turned off parallel port polling (but left
> PNP on), except that netscape won't print (only problem that I've found so
> far) even though I told it to use pdq instead
On Sat, 29 Jan 2000, Nils Philippsen wrote:
> What's this? I guess it's some kind of automatic converter for the various
> formats into postscript/ascii.
It's a print, erm, non-spooler -- like lpd, but instead of queueing, it
just sends directly to the printer. BTW, it's working (nearly) pefectl
On Thu, 27 Jan 2000, Dakota Surmonde wrote:
> On Wed, 26 Jan 2000, Nils Philippsen wrote:
>
> > What does `lsmod | grep parport` give?
>
> since I've got a monolithic kernel absolutely nothing :) but dmesg | grep
> parport gives
>
> parport0: PC-style at 0x3bc [SPP,PS2]
> parport0: no IEEE-128
On Wed, 26 Jan 2000, Nils Philippsen wrote:
> What does `lsmod | grep parport` give?
since I've got a monolithic kernel absolutely nothing :) but dmesg | grep
parport gives
parport0: PC-style at 0x3bc [SPP,PS2]
parport0: no IEEE-1284 device present.
lp0: using parport0 (polling).
um..also, I s
On Tue, 25 Jan 2000, Dakota Surmonde wrote:
>
> Yup. I live :)
Fine :-)
> So, I upgraded my kernel from 2.0.36 to 2.2.13 (yeah yeah, and this was a
> few months ago..can we say the cobbler's children go without shoes? )
> and the printer quit working. It worked fine previously. In part, this
On Wed, 26 Jan 2000, Britta Koch wrote:
> Glad to hear that ;)
thanks. glad to be back, really :)
> I used to have a similar problem(even with the ports) - do you have
> parport support as modules? Have you loaded all the necessary modules
> (i think parport.o AND parport_core.o or something l
>Yup. I live :)
Glad to hear that ;)
>So, I upgraded my kernel from 2.0.36 to 2.2.13 (yeah yeah, and this was a
>few months ago..can we say the cobbler's children go without shoes? )
>and the printer quit working. It worked fine previously. In part, this was
>because the parallel port moved f
yeah.
/etc/printcap looks like (sans comments)
lp:\
:sd=/var/spool/lpd/lp:\
:mx#0:\
:sh:\
:lp=/dev/lp0:
and catting to /dev/lp0 works :(...
Vinnie
On Tue, 25 Jan 2000, Laurel Fan wrote:
> Does printcap mention the correct port?
>
>
> [EMAIL PR
Does printcap mention the correct port?
[EMAIL PROTECTED] http://www.linuxchix.org
Yup. I live :)
So, I upgraded my kernel from 2.0.36 to 2.2.13 (yeah yeah, and this was a
few months ago..can we say the cobbler's children go without shoes? )
and the printer quit working. It worked fine previously. In part, this was
because the parallel port moved from lp1 to lp0 (why, I dunno
10 matches
Mail list logo
