Very Computer

        I had a long, detailed post here, and Deja.com trashed it because I
hadn't logged in before posting, so this one is gonna be short.  >:-(

        Basically, I built a new kernel on my system (Mandrake/Redhat 5.3), to
upgrade from 2.0.36 to 2.2.11-4.  Now, I cannot print anything.  I have
changed /etc/printcap to reference lp0 instead of lp1, and the module
parport_pc.o loads, but then tells me I need to use procfs to enable
interrupt-driven printing.  I've got /etc/conf.modules set with this,
per the documentation:

alias parport_lowlevel parport_pc
options parport_pc io=0x378 irq=auto

        (I also tried it with irc=7, which is where my BIOS says the parallel
port lives.)

        /proc/parport/0 exists and is populated with files that look ok.

        Instead of printing, lpc tells me it's waiting for the printer to be
ready, and I get kernel messages that kmod can't locate modules
char-major-[either 6, 14, or 108 here, though 6 is by far the most
frequent].  These messages mostly happen when I try to print, but seem
to occur rarely by themselves -- though I haven't noticed anything else
not working... yet.  :)

        I hope somebody else out there has had and fixed this problem, or knows
how, as I rather need to be able to print!

Thanks for any assistance,
Carl

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

    John

"General Setup" that "Parallel Support" and "PC-Style Hardware" were set
as modules.  Change them from "M" to "Y" and recompile the kernel.

-pc

Quote:> > upgrade from 2.0.36 to 2.2.11-4.  Now, I cannot print anything.  I
have
> > changed /etc/printcap to reference lp0 instead of lp1, and the
module
> > parport_pc.o loads, but then tells me I need to use procfs to enable

Quote:> >         Instead of printing, lpc tells me it's waiting for the
printer to be
> > ready, and I get kernel messages that kmod can't locate modules
> > char-major-[either 6, 14, or 108 here, though 6 is by far the most
> > frequent].  These messages mostly happen when I try to print, but
seem
> > to occur rarely by themselves -- though I haven't noticed anything
else
> > not working... yet.  :)
>     I had the problem you're talking about with RH 5.2/Kernel 2.2.9
and cleared it
> only by saying YES to all ParPort stuff instead of modules.  Hopefully

[...]

Quote:> kernel yet).  If you're desperate to print, you can try this as a

        I don't think this will have any effect, as I just had time to look
more into the problem and, preparing to rebuild, noticed that I *had*
compiled parallel printer support into the kernel, instead of doing it
as a module.  I have since rebooted, using 'append="parport=0x378,7
parport=auto"' (the auto was just in case it would detect something
other than what my BIOS says the parallel port should be at) in
lilo.conf, and nothing has changed.

        More info in another post...

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.