It would be nice to be able to use it as a scanner and faxer, too, but for now I’d be really happy to print.
I upgraded from 11.4 to 12.1 and haven’t printed since. I kept all the old sysconfig and ppd files and such,
but it won’t respond at all any more.
but the recommendations there did not work. I fuzzily remember command line ways of telling CUPS that the usb connected
printer should be treated as a parallel port printer and testing it. But I’ve forgotten both those instructions and the right
Google search to recover those instructions.
but the recommendations there did not work. I fuzzily remember command line ways of telling CUPS that the usb connected
printer should be treated as a parallel port printer and testing it.
I’ve never had to resort to this kind of trick with a usb-connected printer. Does the CUPS usb backend not support it properly?
Can you post your /etc/cups/printers.conf contents?
Yast flat out won’t see it, both before and after messing with the drivers, per the Brother Solutions Center.
The “add printer” cups interface does not see anything local, so it asks if I want to use an HP setup or
some filter command. There are no discovered network printers (it is USB and local), so I have to invent my own.
I tried copying from my old installation. Same printer. Same computer. Same printers.conf.
I was going to say: Doesn’t work now.
except restarting the printer the nth time caused it to work.
Likely I fiddled something because I’ve tried one fiddle after another.
The following does not work if the DeviceURI says “usb” instead of “parallel”.
I have the same issue with a Brother HL-2170W. I installed the drivers from the Brother website in the proper order and it is still a no go. I have not been able to figure it out either. You are not alone on this one.
I have seen evidence of this backend failing when certain printer stings are not correctly parsed, but that is a CUPS error, not specific to your printer or driver.
They have upgraded the CUPS package recently with several bug fixes, allegedly correcting this problem. I wonder how long it might take to see those same fixes in the openSUSE CUPS package.