Quote:
Originally Posted by Jimmyjack67
Could it be the System-Product-Name shown could be the problem? If it is, would there be a way to delete it?
|
That's just the "hostname" of your system; the "syslog" file can keep the log for several different machines, so each entry begins with a timestamp followed by the name of the machine to which it applies. That's a bit confusing when you have only one machine involved but most of us eventually just "filter it out" mentally and never seem to notice it.
The word that follows it in these excerpts, such as "kernel:" in the important three you quote, tells which module of the system made the entry. All three taken together indicate that for some unknown reason, a critical part of the print driver (the FIFO, first-in-first-out storage area) that's in the kernel (the central processing code that makes everything work) is not doing its job correctly. The driver code then tries again, with the same result, and it never stops.
If the driver were working properly, this loop would eventually time out and simply stop. Since that's not happening, I suspect that there's hidden damage that's NOT being logged.
I also suspect that a reinstallation is going to be your only solution. It's probable that the actual driver is part of the "ppd" file that could be changed, but it's also probable that whatever went wrong damaged other portions of the kernel code, and changing to a different ppd file would NOT fix that.
The kernel can be reinstalled, and sometimes that happens as part of a system update, but doing so outside of an update is much trickier than a simple reinstall -- and doesn't guarantee that the whole system is back to "normal" either.
Thank you all
