I was surprised! After running dmesg I found my printer working again.
I don't understand why this is so but, as I had done nothing else (I
send these messages from another computer), dmseg must have corrected
the problem.
Thanks again for the help.
Tom George
Thomas H. George,,,610-444-2626 wrote:
Thanks for the suggestion. I had not learned about dmesg.
Unfortunately it reported everything in order - i.e. parport0 using
0378 and irq 7. I must look elsewhere for the problem.
Tom George
ktb wrote:
On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:
My printer was working perfectly. I rebuilt the kernel allowing
autoprobe. Printer no longer responds even to
cat lptest > /dev/lp0 where lptest is a small text file
and
lp lptest
responds normally but nothing is printed and nothing is in the print que.
cat /proc/ioports shows the correct value (0378-037f) for
parport0
cat /proc/parport/0/irq reports none (should be irq 7 but is
this needed?)
Documentation/parport indicates that a lilo command parport=0x378,7
should work but /sbin/lilo rejects this line placed anywhere in
lilo.conf. The documentation also implies that the irq value reported
by cat/proc/parport/0/irq can be changed but I don't understand how.
It seems to me that everything is working normally but the printer is
not receiving the transmission. The printcap file is unaltered and lp
is !
directed to lp0.
Where is the missing link?
What does dmesg say about parport?
kent
