Re: printing with kernel 2.1.94
On Fri, Apr 10, 1998 at 07:14:16AM -0400, David Z. Maze wrote:
>
> Aria Prima Novianto <aria@purdue.edu> writes:
> APN> On Thu, Apr 09, 1998 at 10:38:47PM -0400, James Dietrich wrote:
> JD>
> JD> But I still haven't figured out what needs to be done to properly
> JD> configure the parallel port and/or printer modules. (I have enabled
> JD> the parallel port and PC-style parallel port and parallel printer
> JD> all as modules).
Thank you both for your suggestions. However, none of the methods outlined
below seem to work.
> JD>
> APN>
> APN> Edit /lib/modules/2.1.94/modules.dep
> APN>
> APN> Change
> APN> /lib/modules/2.1.94/misc/lp.o: /lib/modules/2.1.94/misc/parport.o
> APN> to
> APN> /lib/modules/2.1.94/misc/lp.o: /lib/modules/2.1.94/misc/parport_pc.o
If I do this, then after giving the command to print a file (lpr <filename>)
this appears in syslog
Apr 10 13:02:40 debian kernel: parport0: PC-style at 0x378 [SPP]
Apr 10 13:02:41 debian kernel: lp0: using parport0 (polling).
and lpq says this
waiting for lp to become ready (offline ?)
Rank Owner Job Files Total Size
1st jdietrch 162 helloworld 42 bytes
and nothing prints.
The three modules parport, parport_pc, and lp all get loaded.
Yes, the printer is on :-)
>
> The better thing to do (which won't have to be redone with every
> kernel upgrade) is to put an alias in your /etc/conf.modules for the
> parport_lowlevel driver, like so:
>
> alias parport_lowlevel parport_pc
If I do this, then this appears in syslog
Apr 10 13:12:11 debian kernel: lp: driver loaded but no devices found
and lpq reports the same problem as above and nothing prints.
The parport and lp modules get loaded.
>
> Unfortunately, I've not had much luck with this at all. Instead, I
> have
>
> post-install parport modprobe "-k" "-s" "parport_pc"
When I add this line to /etc/conf.modules the error message
in syslog is
Apr 10 07:45:36 debian modprobe: post-install /lib/modules/2.1.94/misc/parport.o failed
Furthermore, lsmod doesn't report that any of the needed modules are
loaded.
>
> This seems to work significantly better. It's the same trick I use to
> get the 2.1.x modularized sound driver working properly; I don't know
> if there's a better way.
Interestingly, the post-install line
post-install sb modprobe "-k" "adlib_card"
I added when figuring out my sound problem produces this error in syslog
Apr 10 13:16:33 debian modprobe: post-install /lib/modules/2.1.94/misc/sb.o failed
which looks a lot like the error I get from the similar line
for the parport post-install line.
Just wondering:
Do I need to specify any further paramaters in /etc/conf.modules? It
looks like they are being detected (or defaulting!) to proper values.
Does it make any difference if the printer is driven by interrupts or
polling?
Again, thanks for your quick responses to my first question. If you
or anyone else has any more ideas about how to get this going, I'd
really appreciate it. And if any further information would be helpful
feel free to ask.
Thanks.
James
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: