Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

I'm printing documents and images to a Samsung ML1630. It used to work fine, but now it prints white instead of black, black instead of white. Text documents come out white text on solid black background. Of course, it used to work fine. Before declaring the printer itself guilty, is it possible that something in my Linux setup, the kernel or printer driver or some hidden setting somewhere is causing this trouble?

Since this problem appeared about a month ago, I've updated everything with the package manager, rebooted a couple times, and the problem persists. Can't blame it on a cosmic ray!

share|improve this question
    
How did you add the printer? What's the driver name? Is that driver recommended (system-config-printer displays a list of drivers, and notes what's recommended)? –  Tshepang Nov 29 '10 at 20:20
1  
@DarenW: To see whether the problem is in the printer or in your computer system, try printing the printer's test page (if there's a way to do this from the printer on this model), or from a live CD/USB. –  Gilles Nov 29 '10 at 20:28
    
I have a Knoppix CD somewhere. Running that could be informative, in case it's a goofed-up bit of software or config –  DarenW Dec 1 '10 at 5:39
    
I got something off the Samsung site, and I recall some forum stating that normal CUPS won't work but to download some modified CUPS. Now, months later, I don't recall any of the details. –  DarenW Dec 1 '10 at 5:43
    
The package manager tells me cups-usblp 1.4.4-1 is installed. This is Arch Linux, if I didn't mention already. –  DarenW Dec 1 '10 at 5:44
show 1 more comment

1 Answer

up vote 1 down vote accepted

I had something like this happen a while back and we eventually tracked it down to some Postscript code which told the printer to print in negative, but was not revoked, and was persistent through reboot.

Rest to defaults fixed it, but it took us a while going back through the logs to figure it out.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.