Thanks for the help. A vulgar end to the work week means I couldn't get back to this sooner. Contextual replies below... On 27/02/2020 15:03, Simon Becherer wrote:
Have you check apparmor? / disable it for test.
I've disabled both this and the firewall. Tried almost every configuration I can conceive of in YaST and the CUPS interface, but nothing makes any difference.
my brother mfc-7480dn works without problems... here what i have done:
from brother homepage for printer: mfc7460dnlpr-2.1.0-1.i386.rpm cupswrapperMFC7460DN-2.0.4-2.i386.rpm
I've seen a cupswrapper file in various other posts but there's none in the download options for this model, and none that gets pulled in by the script.
and scanner: brscan4-0.4.4-3.x86_64.rpm
On the contrary I get an additional scan-related package, 'brscan-skey-0.2.4-1.x86_64.rpm'
and for fax: brmfcfaxlpd-1.0.0-1.i386.rpm brmfcfaxcups-1.0.0-1.i386.rpm
There's no fax functionality on this DCP model so we can skip that.
put all into a directory "./Downloaded-rpm" and let createreop create a repository-index from it createrepo ./Downloaded-rpm (maybe install with yast before "createrepo_c") add this repo to your repos.
now install with yast (i installed each rpm single) mfc7460dnlpr cupswrapperMFC7460DN
I'll come back to this.
now inside cups there is a new printer.- but it has usb connection. this has to be changed to (in my case) lpd://192.168.0.13/binary_p1 (you have of course to course your ip-address (and mybe your tring for "binary_p1)) all other setup things at my system where ok print testpage, success.
I've tried the lpd option with the string proposed automatically in YaST connection wizard, where it replaces the ip address with a 15-character string based on the MAC address. I've also tried it with the ip address. I've tried TCP using port 9100 or 54921 (the latter being mentioned on Brother's website). I've tried ipp. I've probably tried about thirty configurations exhausting all the options I can find in that YaST connection wizard, and other variables in the CUPS interface.
if not check / disable appamor + firewall for test purpose, maybe put printer to usb-connection (before changeing anything) and maybe try as root to print
I decided to hook it up directly via USB, which is not really how I want it configured, but just to try. Then I used the auto-detected YaST USB options. It sees the printer, just as it can see it sometimes under various network config options, but it outright refuses to actually print. Also tried printing a simple text file as root via USB, no joy. And I have my user in the lp group just in case. If I ever get it to work, these are all things I can eliminate again afterwards. [snip fax comments]
scanner: yast each file single-install: libusb-0_1-4 brscan4
yast scanner: "brother4 no scanner present"
as root: Add network scanner entry Command : brsaneconfig4 -a name=(name your device) model=(model name) ip=xx.xx.xx.xx brsaneconfig4 -a name=BROTHER model=MFC-7460DN ip=192.168.0.13
Confirm network scanner entry Command : brsaneconfig4 -q | grep (name of your device) brsaneconfig4 -q | grep BROTHER
yast: install xsane now scanner working.
Scanning works fine, even when YaST doesn't recognize the setup. It just communicates direct via 192.168.0.57. And that signifies the crux of the matter. I don't think it's a problem with setup and communication. The computer receives scans. When I go into YaST's printer connection wizard, some options present a 'Test connection' button. On pressing that, the printer screen lights up and says 'hello yes I'm here'. The PC knows the printer is there. They've been communicating fine all this time and having a party. The problem is that when the PC sends its messenger boy out to deliver a letter, instead of cycling across town in the wind he just dumps it in a dustbin and heads to Starbucks thinking no-one will notice. To come back to the earlier point about your install of the files via YaST, I've already done the install numerous times from different directories, either with the rpms in situ or downloaded fresh from the script. Within YaST Software Management I see the rpms as 'installed' so they should be in the rpm database. I could uninstall and reinstall for the umpteenth time and do it all in YaST without the script. Maybe when I've got more mental energy tomorrow. But I can't see how that would really change anything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org