Hardware - Unable to Configure Printer After Power Outage michael7 - 28.07.2006, 00:10 Uhr Titel: Unable to Configure Printer After Power Outage
Today, while I was at work, the electricity to my house (and neighborhood) was switched off. I had left my computer powered on and came home to find that it had shut down.
I rebooted and noticed a couple of messages that indicated that the filesystem was not clean. So far, I've discovered two problems. First, my optical mouse won't work plugged into the USB port. That I fixed by attaching an adapter and plugging it into the serial mouse port. The second problem has proved more difficult.
I connect to my printer using a USB cable. When I tried to print something, nothing happened. There was a message on the screen indicating that the job had been sent to the printer, but the printer didn't do anything. I tried to reconfigure the printer by clicking the Kanotix fish button on the kicker and selecting the Configure Printer option. When I did that, I got the following message:
Error-- KDE Control Module
Unable to retrieve the printer list. Error message received from manager. Connection to CUPS server failed. Check that CUPS server is correctly installed and running. Error: host not found.
At the bottom of that screen, I see the following information: server: /var/run/cups/cups.sock: 631
When I proceed to the Backend Selection screen, the local printer option is grayed out.
Obviously, I have a corrupted file or files. What should I remove and replace? All the USB files? All the CUPS files? All of both?
Any help is appreciated.
michael7 - 28.07.2006, 03:40 Uhr Titel: Problem solved
I solved the problem by installing a new kernel. I guess you could call it the "Fred Flintstone" approach-- brute force and awkwardness.
schnorrer - 28.07.2006, 08:48 Uhr Titel: Problem solved
Why not? Powerchras has crashed your kernel partly.
michael7 - 29.07.2006, 03:39 Uhr Titel:
schnorrer,
You're right. USB support is either built into the kernel or contained in a module and the outage corrupted it. Installing a new kernel corrects the damage.