Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The bug is rock solid reproducible and has been around for about 7-10 days.
With a cold boot and nothing in the CUPS print queues; (lp1 double sided A4, lp2 single sided A4) when I "print" a document it gets no further than the print queue. and there is no /dev/lp0. same if I do a test print from within CUPS is queued. Restarting the spooler from inside the CUPS GUI had no effect.
If I then reboot the m/c. I can now see /dev/lp0 (parallel port) is now present,
crw-rw---- 1 root lp 6, 0 2010-02-01 14:21 /dev/lp0,
the documents in the queue from before the reboot are now printed,
and I am able to print any further documents until the next reboot.
K7S6A with 1GB of RAM and 4 IDE disks.
o/s is : “Linux tigger 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686 GNU/Linux”
print chain: CUPS and HP 4050TN connected to parallel port by cable (D25 to Centronics)
1) SIG 9 is SIGKILL what I used to kill (sledgehammer) hung processes (as it cannot be ignored), nasty but works every time.
I ran a one hour batter test on the RAM, with no errors, so it looks OK.
I can see the printer being recognized correctly at paraport0 during the boot process.
From the Web interface, trying to print a test page, with a cold booted m/c and emptym print queues, I see the message ""Printer not connected; will retry in 30 seconds..." but the printer is connected and if I then reboot the test page is printed and this message not seen. As already stated, when I then try a new test page it prints and anything else I send to the printer. [printing is normal ?]
In the fault mode looking at the /var/log/cups files:
error.log is empty
Anyone able to say quickly which pins on the D25 and Centronics plugs do I test continuity through, in case I have a cable fault? I do not believe I have as the reboot clears the fault. I suspect it is software but (?) What else can I try? any pointers appreciated. And thank you all.
While searching line by line in syslog found with printer off "cwdeamon" was trying to seize the paraport0 with exclusive access at boot time. Why it was doing this is unknown but deleted cwdeamon package and all is back to normal. Thank you all for help.regards, (spirals -dja.)