On F18, updated.
I've got a Brother MFC-7360N printer on 10.10.10.153. I can bring up its web page. I can print from a W7 laptop, and used to print from F17.
I've attached the screenshot of the printer properties window as it was set up by the printer config utility.
It has a device URI: lpd://BRN001BA9967E79/BINARY_P1
When I try to print I get for status:
Processing - not connected?
I've changed the URI to use the ip address:
lpd://10.10.10.153/BINARY_P1
That doesn't work either, can't print a test page. BUT, it generates no errors. F18/cups thinks all went well.
Any help appreciated.
sean
On Sun, 2013-02-03 at 14:18 -0500, sean darcy wrote:
I've changed the URI to use the ip address:
lpd://10.10.10.153/BINARY_P1
That doesn't work either, can't print a test page. BUT, it generates no errors. F18/cups thinks all went well.
It looks to me like this is not a PostScript-capable printer, but you are using a PostScript-based driver.
You may need to download Brother's own Linux driver for this printer from their website.
Tim. */
On 02/03/2013 02:18 PM, sean darcy wrote:
On F18, updated.
I've got a Brother MFC-7360N printer on 10.10.10.153. I can bring up its web page. I can print from a W7 laptop, and used to print from F17.
I've attached the screenshot of the printer properties window as it was set up by the printer config utility.
It has a device URI: lpd://BRN001BA9967E79/BINARY_P1
When I try to print I get for status:
Processing - not connected?
I've changed the URI to use the ip address:
lpd://10.10.10.153/BINARY_P1
That doesn't work either, can't print a test page. BUT, it generates no errors. F18/cups thinks all went well.
Any help appreciated.
sean
Sean, I noticed that the Brother MFC-7360N isn't shown in Fedora 18 printer drivers, did you have to download the drivers from Brother ?
If so , and you have the drivers installed.
do a ; setenforce 0; fixfiles -F restore; setenforce 1; reboot , as SU
Normally Selinux has problems with drivers that don't come with Fedora. I have two printers where I have to download the drivers from Samsung and I have to run the setenforce command to get Selinux to label the drivers before I can get the printer to work.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/04/2013 12:05 PM, Jim wrote:
On 02/03/2013 02:18 PM, sean darcy wrote:
On F18, updated.
I've got a Brother MFC-7360N printer on 10.10.10.153. I can bring up its web page. I can print from a W7 laptop, and used to print from F17.
I've attached the screenshot of the printer properties window as it was set up by the printer config utility.
It has a device URI: lpd://BRN001BA9967E79/BINARY_P1
When I try to print I get for status:
Processing - not connected?
I've changed the URI to use the ip address:
lpd://10.10.10.153/BINARY_P1
That doesn't work either, can't print a test page. BUT, it generates no errors. F18/cups thinks all went well.
Any help appreciated.
sean
Sean, I noticed that the Brother MFC-7360N isn't shown in Fedora 18 printer drivers, did you have to download the drivers from Brother ?
If so , and you have the drivers installed.
do a ; setenforce 0; fixfiles -F restore; setenforce 1; reboot , as SU
Normally Selinux has problems with drivers that don't come with Fedora. I have two printers where I have to download the drivers from Samsung and I have to run the setenforce command to get Selinux to label the drivers before I can get the printer to work.
No need to do setenforce 0; setenforce 1
The admin user (probably unoconfined_t) should be able to fix labels without turning off enforcing.
If you know where the files were placed, running restorecon -R would be faster then relabeling the entire machine.
On 02/04/2013 01:07 PM, Daniel J Walsh wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/04/2013 12:05 PM, Jim wrote:
On 02/03/2013 02:18 PM, sean darcy wrote:
On F18, updated.
I've got a Brother MFC-7360N printer on 10.10.10.153. I can bring up its web page. I can print from a W7 laptop, and used to print from F17.
I've attached the screenshot of the printer properties window as it was set up by the printer config utility.
It has a device URI: lpd://BRN001BA9967E79/BINARY_P1
When I try to print I get for status:
Processing - not connected?
I've changed the URI to use the ip address:
lpd://10.10.10.153/BINARY_P1
That doesn't work either, can't print a test page. BUT, it generates no errors. F18/cups thinks all went well.
Any help appreciated.
sean
Sean, I noticed that the Brother MFC-7360N isn't shown in Fedora 18 printer drivers, did you have to download the drivers from Brother ?
If so , and you have the drivers installed.
do a ; setenforce 0; fixfiles -F restore; setenforce 1; reboot , as SU
Normally Selinux has problems with drivers that don't come with Fedora. I have two printers where I have to download the drivers from Samsung and I have to run the setenforce command to get Selinux to label the drivers before I can get the printer to work.
No need to do setenforce 0; setenforce 1
The admin user (probably unoconfined_t) should be able to fix labels without turning off enforcing.
If you know where the files were placed, running restorecon -R would be faster then relabeling the entire machine.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlEP+M0ACgkQrlYvE4MpobMf9ACeOPYBeQezKjtEClJ7IamqtF35 DYgAoMYFFu0XojkIUdUDjUIbOrUQiGoh =yHFG -----END PGP SIGNATURE-----
Thats a True statement but your not going to know all the different locations the Driver will install.
On 02/04/2013 06:34 AM, Tim Waugh wrote:
On Sun, 2013-02-03 at 14:18 -0500, sean darcy wrote:
I've changed the URI to use the ip address:
lpd://10.10.10.153/BINARY_P1
That doesn't work either, can't print a test page. BUT, it generates no errors. F18/cups thinks all went well.
It looks to me like this is not a PostScript-capable printer, but you are using a PostScript-based driver.
You may need to download Brother's own Linux driver for this printer from their website.
Tim. */
I already had the Brother drivers which come packaged as rpm's. Unfortunately the rpm's don't check dependencies. They are i686 rpms and depend on glibc.i686. And no error to syslog or otherwise is generated when you use them on an x86-64 machine. Installing glibc.i686 makes it all work.
But the print config wizard still uses the node name for machine the URI:
lpd://BRN001BA9967E79/BINARY_P1
This generates the no connection error. You have to change the node name to the ip address.
sean
-
Daniel J Walsh -
Mickey -
sean darcy -
Tim Waugh