Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #184617 > unrolled thread

pesky and persistent "driverless" Brother MFC-9340CDW

Back to article view | Back to linux.debian.user

Contents

  pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-04 04:00 +0200
    Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-04 12:40 +0200
      Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-04 20:20 +0200
        Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-05 00:50 +0200
          Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-05 02:30 +0200
            Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-05 15:00 +0200
              Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-05 17:50 +0200
              Re: pesky and persistent "driverless" Brother MFC-9340CDW Curt <curty@free.fr> - 2017-08-05 18:50 +0200
                Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-05 19:20 +0200
                  Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-05 20:30 +0200
                    Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-05 20:50 +0200
                      Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-05 21:20 +0200
                        Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-06 00:50 +0200
    Re: pesky and persistent "driverless" Brother MFC-9340CDW Curt <curty@free.fr> - 2017-08-04 14:30 +0200
      Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-04 15:00 +0200
        Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-04 20:30 +0200
        Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-04 22:20 +0200
          Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-05 01:10 +0200
            Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-05 02:40 +0200
      Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-04 20:20 +0200
        Re: pesky and persistent "driverless" Brother MFC-9340CDW Brian <ad44@cityscape.co.uk> - 2017-08-05 01:10 +0200
          Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-05 02:50 +0200
      Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-04 22:10 +0200
        Re: pesky and persistent "driverless" Brother MFC-9340CDW Richard Hector <richard@walnut.gen.nz> - 2017-08-06 01:40 +0200
          Re: pesky and persistent "driverless" Brother MFC-9340CDW Jape Person <japers@comcast.net> - 2017-08-06 02:10 +0200

Page 1 of 2  [1] 2  Next page →

#184617 — pesky and persistent "driverless" Brother MFC-9340CDW

A few weeks ago a CUPS upgrade to our Debian testing systems started 
showing a new driver for our Brother MFC-9340CDW in print dialogs and in 
the CUPS printer list and in the system-config-printer utility.

You'd think that was good news, but we've been unable to find any way to 
make the queue for this "driverless" instance of the printer function 
properly.

The only way we can print with this printer is to do what we were doing 
before the new "driverless" instance of the printer showed up. We add a 
printer to the system via system-config-printer or the CUPS Web browser 
dialog and deliberately select the Brother MFC-9320CW Foomatic or 
Brother Script-3 driver. (That's not a typo. I'm deliberately choosing a 
different model.) Both of those PPDs work. I have to provide a 
deliberately altered name for this instance so users can tell it from 
the one that doesn't work.

The particularly annoying thing about this situation is that I cannot 
delete the "driverless" instance of the printer from CUPS / 
system-config-printer. The instant it is deleted, it is automatically 
re-detected and added back to the printer list. But anyone who chooses 
to print to it is going to get a distorted or garbled printout.

I was able to set a policy in the instance so that only root can print 
to it, so a regular user isn't going to waste time and paper. Still, it 
would be nicer if I could turn off the advertisement that the printer 
and the operating system is providing for the "driverless" instance.

I've found nothing in the printer's menu system or in its Web interface 
that would seem to pertain.

Ideas, anyone?

Thanks,
JP

[toc] | [next] | [standalone]

#184628

On Thu 03 Aug 2017 at 21:39:43 -0400, Jape Person wrote:

> A few weeks ago a CUPS upgrade to our Debian testing systems started showing
> a new driver for our Brother MFC-9340CDW in print dialogs and in the CUPS
> printer list and in the system-config-printer utility.
> 
> You'd think that was good news, but we've been unable to find any way to
> make the queue for this "driverless" instance of the printer function
> properly.

It *is* good news. The printer was set up automatically, something
people have been asking for for years. No non-free drives, either.
A pity about the printout. That shouldn't happen, The cause would
need to be looked at. Maybe the printer is non-conforming to IPP
Everywhere.
 
> The only way we can print with this printer is to do what we were doing
> before the new "driverless" instance of the printer showed up. We add a
> printer to the system via system-config-printer or the CUPS Web browser
> dialog and deliberately select the Brother MFC-9320CW Foomatic or Brother
> Script-3 driver. (That's not a typo. I'm deliberately choosing a different
> model.) Both of those PPDs work. I have to provide a deliberately altered
> name for this instance so users can tell it from the one that doesn't work.

Brother provides software for this printer.

 http://support.brother.com/g/b/downloadlist.aspx?c=gb&lang=en \
 &prod=mfc9340cdw_all \
 &_ga=2.149781630.955111390.1501838613-23812213.1497304959&os=128

(URL line broken for readability).

> The particularly annoying thing about this situation is that I cannot delete
> the "driverless" instance of the printer from CUPS / system-config-printer.
> The instant it is deleted, it is automatically re-detected and added back to
> the printer list. But anyone who chooses to print to it is going to get a
> distorted or garbled printout.
> 
> I was able to set a policy in the instance so that only root can print to
> it, so a regular user isn't going to waste time and paper. Still, it would
> be nicer if I could turn off the advertisement that the printer and the
> operating system is providing for the "driverless" instance.

"CreateIPPPrinterQueues No" in cups-browsed.conf. Or switch off Bonjour
broadcasting (AirPrint) on the printer.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184645

On 08/04/2017 06:37 AM, Brian wrote:
> On Thu 03 Aug 2017 at 21:39:43 -0400, Jape Person wrote:
> 
>> A few weeks ago a CUPS upgrade to our Debian testing systems
>> started showing a new driver for our Brother MFC-9340CDW in print
>> dialogs and in the CUPS printer list and in the
>> system-config-printer utility.
>> 
>> You'd think that was good news, but we've been unable to find any
>> way to make the queue for this "driverless" instance of the printer
>> function properly.
> 
> It *is* good news. The printer was set up automatically, something 
> people have been asking for for years. No non-free drives, either. A
> pity about the printout. That shouldn't happen, The cause would need
> to be looked at. Maybe the printer is non-conforming to IPP 
> Everywhere.

Well, it *would* be good news if it actually produced usable output. As 
things stand right now, it's merely a way to waste time, paper, and toner.

I'll admit I was tickled when I saw that there was a driver specifically 
for this printer, and then not tickled when it didn't work but wouldn't 
go away.

> 
>> The only way we can print with this printer is to do what we were
>> doing before the new "driverless" instance of the printer showed
>> up. We add a printer to the system via system-config-printer or the
>> CUPS Web browser dialog and deliberately select the Brother
>> MFC-9320CW Foomatic or Brother Script-3 driver. (That's not a typo.
>> I'm deliberately choosing a different model.) Both of those PPDs
>> work. I have to provide a deliberately altered name for this
>> instance so users can tell it from the one that doesn't work.
> 
> Brother provides software for this printer.
> 
> http://support.brother.com/g/b/downloadlist.aspx?c=gb&lang=en \ 
> &prod=mfc9340cdw_all \ 
> &_ga=2.149781630.955111390.1501838613-23812213.1497304959&os=128
> 
> (URL line broken for readability).
> 

When I first got the printer I updated its firmware. This isn't as easy 
as you might think. You have to have a Windows or Mac computer to 
perform the update, and I didn't own one. I purchased a little Windows 
10 gizmo from SimplyNUC so that I could do this update, and so that I 
could perform firmware updates on a couple of GPS devices.

I also tried the proprietary software, just for grins. I never intended 
to use anything other than what's in the official repos on my Debian 
systems. The helter-skelter way the driver installation directions were 
written and the absolutely hilarious hodge-podge of license notices and 
balky scripts was kind of horrifying. But I'll admit that everything 
worked, once I weeded out the inappropriate directions and fixed the 
installation. And I appreciated that all was installed in a manner that 
made it easy to remove.

The functionality of the proprietary printer driver was no better than 
that of the MFC-9320CW driver from CUPS, other than it included the 
ability to monitor toner levels. But all of that sort of stuff is 
readily available via the Web interface of the printer.

Since I have workaround, I can't bring myself to re-install the 
proprietary driver. I do have to use the Web interface to see the 
maintenance information, and I have to get scans via my wife's Android 
tablet. But I just found the proprietary drivers to be icky.

>> The particularly annoying thing about this situation is that I
>> cannot delete the "driverless" instance of the printer from CUPS /
>> system-config-printer. The instant it is deleted, it is
>> automatically re-detected and added back to the printer list. But
>> anyone who chooses to print to it is going to get a distorted or
>> garbled printout.
>> 
>> I was able to set a policy in the instance so that only root can
>> print to it, so a regular user isn't going to waste time and paper.
>> Still, it would be nicer if I could turn off the advertisement that
>> the printer and the operating system is providing for the
>> "driverless" instance.
> 
> "CreateIPPPrinterQueues No" in cups-browsed.conf. Or switch off
> Bonjour broadcasting (AirPrint) on the printer.
> 

Hmmm. I turned off AirPrint through the Web interface right from the 
beginning. I just checked it again, and the interface indicates that 
AirPrint is turned off.

I'll go further down this path if other tactics don't work.

Thank you so much for your time and effort. I didn't think of looking in 
cups-browsed.conf because I thought turning off AirPrint should have 
done the job.

[toc] | [prev] | [next] | [standalone]

#184649

On Fri 04 Aug 2017 at 14:09:25 -0400, Jape Person wrote:

> On 08/04/2017 06:37 AM, Brian wrote:
> >On Thu 03 Aug 2017 at 21:39:43 -0400, Jape Person wrote:
> >
> >>A few weeks ago a CUPS upgrade to our Debian testing systems
> >>started showing a new driver for our Brother MFC-9340CDW in print
> >>dialogs and in the CUPS printer list and in the
> >>system-config-printer utility.
> >>
> >>You'd think that was good news, but we've been unable to find any
> >>way to make the queue for this "driverless" instance of the printer
> >>function properly.
> >
> >It *is* good news. The printer was set up automatically, something people
> >have been asking for for years. No non-free drives, either. A
> >pity about the printout. That shouldn't happen, The cause would need
> >to be looked at. Maybe the printer is non-conforming to IPP Everywhere.
> 
> Well, it *would* be good news if it actually produced usable output. As
> things stand right now, it's merely a way to waste time, paper, and toner.

I thought you would say that, and it is very reasonable to express such
sentiments. But where is your ire aimed at? Not at Brother, as far as I
can see. What do they say? Somebody there must have some knowledge about
IPP specifications. Maybe they are not aware that one of their printers
sets resolution to 600x2 dpi. Have you told them?

(I am assumimg you are seeing fallout from #868360 and this is the cause
of your frustration).

> I'll admit I was tickled when I saw that there was a driver specifically for
> this printer, and then not tickled when it didn't work but wouldn't go away.

cups-browsed detects printers or print queues. Its job is to keep them
visible; why else should it exist? You control visibility from its conf
file. If you try to delete a printer or print queue cups-browsed  gets
upset and reinstates it. Perfectly normal if you think about it.

> >>The only way we can print with this printer is to do what we were
> >>doing before the new "driverless" instance of the printer showed
> >>up. We add a printer to the system via system-config-printer or the
> >>CUPS Web browser dialog and deliberately select the Brother
> >>MFC-9320CW Foomatic or Brother Script-3 driver. (That's not a typo.
> >>I'm deliberately choosing a different model.) Both of those PPDs
> >>work. I have to provide a deliberately altered name for this
> >>instance so users can tell it from the one that doesn't work.
> >
> >Brother provides software for this printer.
> >
> >http://support.brother.com/g/b/downloadlist.aspx?c=gb&lang=en \
> >&prod=mfc9340cdw_all \
> >&_ga=2.149781630.955111390.1501838613-23812213.1497304959&os=128
> >
> >(URL line broken for readability).
> >
> 
> When I first got the printer I updated its firmware. This isn't as easy as
> you might think. You have to have a Windows or Mac computer to perform the
> update, and I didn't own one. I purchased a little Windows 10 gizmo from
> SimplyNUC so that I could do this update, and so that I could perform
> firmware updates on a couple of GPS devices.

I have never thought updating printer firmware was easy or even possible
from Linux. No Windows or Mac here either. I'll look at SimplyNUC.
Thanks.
 
> I also tried the proprietary software, just for grins. I never intended to
> use anything other than what's in the official repos on my Debian systems.
> The helter-skelter way the driver installation directions were written and
> the absolutely hilarious hodge-podge of license notices and balky scripts
> was kind of horrifying. But I'll admit that everything worked, once I weeded
> out the inappropriate directions and fixed the installation. And I
> appreciated that all was installed in a manner that made it easy to remove.
> 
> The functionality of the proprietary printer driver was no better than that
> of the MFC-9320CW driver from CUPS, other than it included the ability to
> monitor toner levels. But all of that sort of stuff is readily available via
> the Web interface of the printer.
> 
> Since I have workaround, I can't bring myself to re-install the proprietary
> driver. I do have to use the Web interface to see the maintenance
> information, and I have to get scans via my wife's Android tablet. But I
> just found the proprietary drivers to be icky.

I mentioned the Brother software merely to inform that it exists, not to
recommend it. Driverless printing is the way to go and the future (give
or take printer bugs).
 
> >>The particularly annoying thing about this situation is that I
> >>cannot delete the "driverless" instance of the printer from CUPS /
> >>system-config-printer. The instant it is deleted, it is
> >>automatically re-detected and added back to the printer list. But
> >>anyone who chooses to print to it is going to get a distorted or
> >>garbled printout.
> >>
> >>I was able to set a policy in the instance so that only root can
> >>print to it, so a regular user isn't going to waste time and paper.
> >>Still, it would be nicer if I could turn off the advertisement that
> >>the printer and the operating system is providing for the
> >>"driverless" instance.
> >
> >"CreateIPPPrinterQueues No" in cups-browsed.conf. Or switch off
> >Bonjour broadcasting (AirPrint) on the printer.
> >
> 
> Hmmm. I turned off AirPrint through the Web interface right from the
> beginning. I just checked it again, and the interface indicates that
> AirPrint is turned off.
> 
> I'll go further down this path if other tactics don't work.

Without AirPrint enabled (and maybe IPP) cups-browsed is unable to
detect the printer. (Is this another printer bug? :) )
 
> Thank you so much for your time and effort. I didn't think of looking in
> cups-browsed.conf because I thought turning off AirPrint should have done
> the job.

So "CreateIPPPrinterQueues No" makes the ptinter invisible?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184652

On 08/04/2017 06:39 PM, Brian wrote:
> On Fri 04 Aug 2017 at 14:09:25 -0400, Jape Person wrote:
> 
>> On 08/04/2017 06:37 AM, Brian wrote:
>>> On Thu 03 Aug 2017 at 21:39:43 -0400, Jape Person wrote:
>>>
>>>> A few weeks ago a CUPS upgrade to our Debian testing systems
>>>> started showing a new driver for our Brother MFC-9340CDW in print
>>>> dialogs and in the CUPS printer list and in the
>>>> system-config-printer utility.
>>>>
>>>> You'd think that was good news, but we've been unable to find any
>>>> way to make the queue for this "driverless" instance of the printer
>>>> function properly.
>>>
>>> It *is* good news. The printer was set up automatically, something people
>>> have been asking for for years. No non-free drives, either. A
>>> pity about the printout. That shouldn't happen, The cause would need
>>> to be looked at. Maybe the printer is non-conforming to IPP Everywhere.
>>
>> Well, it *would* be good news if it actually produced usable output. As
>> things stand right now, it's merely a way to waste time, paper, and toner.
> 
> I thought you would say that, and it is very reasonable to express such
> sentiments. But where is your ire aimed at? Not at Brother, as far as I
> can see. What do they say? Somebody there must have some knowledge about
> IPP specifications. Maybe they are not aware that one of their printers
> sets resolution to 600x2 dpi. Have you told them?
> 
> (I am assumimg you are seeing fallout from #868360 and this is the cause
> of your frustration).
> 

Was my tone more testy than I thought? I wasn't intending to express ire 
at either Debian or Brother. I was just annoyed that there was no 
obvious way to tell the system that I didn't want to see a queue that 
was non-functional.

With all of the provisions for other settings it just seemed odd to me 
that neither CUPS nor config-system-printer had a clue in their user 
interfaces as to how a user might indicate that s/he didn't want to see 
the driverless printer. This was my first experience seeing one in 
GNU/Linux, after all.

>> I'll admit I was tickled when I saw that there was a driver specifically for
>> this printer, and then not tickled when it didn't work but wouldn't go away.
> 
> cups-browsed detects printers or print queues. Its job is to keep them
> visible; why else should it exist? You control visibility from its conf
> file. If you try to delete a printer or print queue cups-browsed  gets
> upset and reinstates it. Perfectly normal if you think about it.
> 

Hence, why I whined online -- in the hope that someone would tell me how 
to do this the non-gui way. After all, the man pages I read indicated 
that it could be done, but didn't seem to tell me how to do it. But you did!

8-)

>>>> The only way we can print with this printer is to do what we were
>>>> doing before the new "driverless" instance of the printer showed
>>>> up. We add a printer to the system via system-config-printer or the
>>>> CUPS Web browser dialog and deliberately select the Brother
>>>> MFC-9320CW Foomatic or Brother Script-3 driver. (That's not a typo.
>>>> I'm deliberately choosing a different model.) Both of those PPDs
>>>> work. I have to provide a deliberately altered name for this
>>>> instance so users can tell it from the one that doesn't work.
>>>
>>> Brother provides software for this printer.
>>>
>>> http://support.brother.com/g/b/downloadlist.aspx?c=gb&lang=en \
>>> &prod=mfc9340cdw_all \
>>> &_ga=2.149781630.955111390.1501838613-23812213.1497304959&os=128
>>>
>>> (URL line broken for readability).
>>>
>>
>> When I first got the printer I updated its firmware. This isn't as easy as
>> you might think. You have to have a Windows or Mac computer to perform the
>> update, and I didn't own one. I purchased a little Windows 10 gizmo from
>> SimplyNUC so that I could do this update, and so that I could perform
>> firmware updates on a couple of GPS devices.
> 
> I have never thought updating printer firmware was easy or even possible
> from Linux. No Windows or Mac here either. I'll look at SimplyNUC.
> Thanks.
>   

It's sad, isn't it? There must be enough Linux / Unix folks using 
brother printers to make it worth Brother's trouble to provide a utility 
for this. I guess most environments have either Windows or Mac 
available, but mine didn't until I got the little NUC. $300 so I can do 
firmware upgrades.

Making lemonade, I'll probably try to play some old games on the little 
box. There's always a silver lining.

>> I also tried the proprietary software, just for grins. I never intended to
>> use anything other than what's in the official repos on my Debian systems.
>> The helter-skelter way the driver installation directions were written and
>> the absolutely hilarious hodge-podge of license notices and balky scripts
>> was kind of horrifying. But I'll admit that everything worked, once I weeded
>> out the inappropriate directions and fixed the installation. And I
>> appreciated that all was installed in a manner that made it easy to remove.
>>
>> The functionality of the proprietary printer driver was no better than that
>> of the MFC-9320CW driver from CUPS, other than it included the ability to
>> monitor toner levels. But all of that sort of stuff is readily available via
>> the Web interface of the printer.
>>
>> Since I have workaround, I can't bring myself to re-install the proprietary
>> driver. I do have to use the Web interface to see the maintenance
>> information, and I have to get scans via my wife's Android tablet. But I
>> just found the proprietary drivers to be icky.
> 
> I mentioned the Brother software merely to inform that it exists, not to
> recommend it. Driverless printing is the way to go and the future (give
> or take printer bugs).
>   

I think you're right. Too bad Brother isn't saying whether or not the 
latest firmware upgrade actually fixes this problem. Since my last 
firmware upgrade resulted in me getting a version which isn't even 
listed in their update history any more, I'm loathe to be a first adapter.

>>>> The particularly annoying thing about this situation is that I
>>>> cannot delete the "driverless" instance of the printer from CUPS /
>>>> system-config-printer. The instant it is deleted, it is
>>>> automatically re-detected and added back to the printer list. But
>>>> anyone who chooses to print to it is going to get a distorted or
>>>> garbled printout.
>>>>
>>>> I was able to set a policy in the instance so that only root can
>>>> print to it, so a regular user isn't going to waste time and paper.
>>>> Still, it would be nicer if I could turn off the advertisement that
>>>> the printer and the operating system is providing for the
>>>> "driverless" instance.
>>>
>>> "CreateIPPPrinterQueues No" in cups-browsed.conf. Or switch off
>>> Bonjour broadcasting (AirPrint) on the printer.
>>>
>>
>> Hmmm. I turned off AirPrint through the Web interface right from the
>> beginning. I just checked it again, and the interface indicates that
>> AirPrint is turned off.
>>
>> I'll go further down this path if other tactics don't work.
> 
> Without AirPrint enabled (and maybe IPP) cups-browsed is unable to
> detect the printer. (Is this another printer bug? :) )
>   
>> Thank you so much for your time and effort. I didn't think of looking in
>> cups-browsed.conf because I thought turning off AirPrint should have done
>> the job.
> 
> So "CreateIPPPrinterQueues No" makes the ptinter invisible?
> 

As it turned out, I didn't have to edit the config file. Turning off 
WiFi Direct made the driverless printer invisible. Is it possible that 
Brother is using "WiFi Direct" as a synonym for Bonjour?

I'm unschooled on this stuff, so forgive if the question is dumb!

Thanks again, Brian!

[toc] | [prev] | [next] | [standalone]

#184677

On Fri 04 Aug 2017 at 20:19:33 -0400, Jape Person wrote:

> On 08/04/2017 06:39 PM, Brian wrote:
> 
> It's sad, isn't it? There must be enough Linux / Unix folks using brother
> printers to make it worth Brother's trouble to provide a utility for this. I
> guess most environments have either Windows or Mac available, but mine
> didn't until I got the little NUC. $300 so I can do firmware upgrades.
> 
> Making lemonade, I'll probably try to play some old games on the little box.
> There's always a silver lining.

I wonder whether wine would help (with installing the firmware, I mean).
 
> >So "CreateIPPPrinterQueues No" makes the ptinter invisible?
> 
> As it turned out, I didn't have to edit the config file. Turning off WiFi
> Direct made the driverless printer invisible. Is it possible that Brother is
> using "WiFi Direct" as a synonym for Bonjour?
> 
> I'm unschooled on this stuff, so forgive if the question is dumb!

Bonjour works on cabled and wireless networks, WiFi Direct is wireless
only. I also thought WiFi Direct did not use Bonjour. Mystifying.

You could try activating and de-activating Bonjour on the printer and
looking for the printer in the output of 'avahi-browse -art', You'll
need the avahi-utils package.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184683

On 08/05/2017 08:52 AM, Brian wrote:
> On Fri 04 Aug 2017 at 20:19:33 -0400, Jape Person wrote:
> 
>> On 08/04/2017 06:39 PM, Brian wrote:
>>
>> It's sad, isn't it? There must be enough Linux / Unix folks using brother
>> printers to make it worth Brother's trouble to provide a utility for this. I
>> guess most environments have either Windows or Mac available, but mine
>> didn't until I got the little NUC. $300 so I can do firmware upgrades.
>>
>> Making lemonade, I'll probably try to play some old games on the little box.
>> There's always a silver lining.
> 
> I wonder whether wine would help (with installing the firmware, I mean).
>   

I had that idea back before I purchased the little Windows system. A 
little alarm is flashing in the back of my mind which is telling me to 
not even try it.

I know that a publisher I worked for after my retirement from medicine 
fired an IT guy for doing a BIOS upgrade on a manager's laptop via WINE. 
The attempt bricked the laptop. In that case, of course, the fellow 
could have just burned a bootable BIOS update disc and done it the right 
way. But he insisted that the Windows executable BIOS updater should 
work through WINE. Since this was the *second* time he had done this, 
his boss showed him the door and how to use it.

>>> So "CreateIPPPrinterQueues No" makes the ptinter invisible?
>>
>> As it turned out, I didn't have to edit the config file. Turning off WiFi
>> Direct made the driverless printer invisible. Is it possible that Brother is
>> using "WiFi Direct" as a synonym for Bonjour?
>>
>> I'm unschooled on this stuff, so forgive if the question is dumb!
> 
> Bonjour works on cabled and wireless networks, WiFi Direct is wireless
> only. I also thought WiFi Direct did not use Bonjour. Mystifying.
> 
> You could try activating and de-activating Bonjour on the printer and
> looking for the printer in the output of 'avahi-browse -art', You'll
> need the avahi-utils package.
> 

I'm saving this information and will hope to get a chance to experiment 
at some point. I'd like to know more about the features and capabilities 
of CUPS (and this printer), but I'm a little low on energy and time due 
to some health issues.

I was pretty tired when I experimented with the AirPrint and WiFi Direct 
settings. I'm wondering now if I might have failed to restart the 
printer after I changed the AirPrint setting. Then, later on, turning 
WiFi Direct off and restarting the printer might have properly instated 
the change in the AirPrint setting.

Thank you for the additional information.

[toc] | [prev] | [next] | [standalone]

#184684

On 2017-08-05, Brian <ad44@cityscape.co.uk> wrote:
> On Fri 04 Aug 2017 at 20:19:33 -0400, Jape Person wrote:
>
>> On 08/04/2017 06:39 PM, Brian wrote:
>> 
>> It's sad, isn't it? There must be enough Linux / Unix folks using brother
>> printers to make it worth Brother's trouble to provide a utility for this. I
>> guess most environments have either Windows or Mac available, but mine
>> didn't until I got the little NUC. $300 so I can do firmware upgrades.
>> 
>> Making lemonade, I'll probably try to play some old games on the little box.
>> There's always a silver lining.
>
> I wonder whether wine would help (with installing the firmware, I mean).
>  

I was wondering whether a native utility like flashrom could be used for
this. However when I looked at the Brother firmware executable to see
whether the firmware part could be extracted, I found that in fact the
exe file doesn't contain the firmware at all, but rather downloads the
latter from a Brother internet server somewhere in the cloud and then
installs into the printer. 

Frankly I would be leery of going through the procedure without a lot of
wine for fear of bricking my device.

-- 
“Certitude is not the test of certainty.”
--Oliver Wendell Holmes, Jr.

[toc] | [prev] | [next] | [standalone]

#184687

On 08/05/2017 12:44 PM, Curt wrote:
> On 2017-08-05, Brian <ad44@cityscape.co.uk> wrote:
>> On Fri 04 Aug 2017 at 20:19:33 -0400, Jape Person wrote:
>>
>>> On 08/04/2017 06:39 PM, Brian wrote:
>>>
>>> It's sad, isn't it? There must be enough Linux / Unix folks using brother
>>> printers to make it worth Brother's trouble to provide a utility for this. I
>>> guess most environments have either Windows or Mac available, but mine
>>> didn't until I got the little NUC. $300 so I can do firmware upgrades.
>>>
>>> Making lemonade, I'll probably try to play some old games on the little box.
>>> There's always a silver lining.
>>
>> I wonder whether wine would help (with installing the firmware, I mean).
>>   
> 
> I was wondering whether a native utility like flashrom could be used for
> this. However when I looked at the Brother firmware executable to see
> whether the firmware part could be extracted, I found that in fact the
> exe file doesn't contain the firmware at all, but rather downloads the
> latter from a Brother internet server somewhere in the cloud and then
> installs into the printer.
> 

I should have mentioned that. I was aware that the firmware updater 
connected to a server in order to grab and install the new firmware.

It's all a little patchier than I'd like. The unreliable installation 
instructions, the fact that a recommended firmware upgrade I got from 
Brother and installed is no longer even listed in the update history on 
their site, and the odd documented bug in the firmware that evidently 
provides bad information to CUPS is enough to make me want to avoid 
another firmware update altogether. If I do decide to update the 
firmware again, I'm going to be leery of workarounds. I'll just do it 
via Windows.

> Frankly I would be leery of going through the procedure without a lot of
> wine for fear of bricking my device.
> 

A lot of wine is almost always good.

;-)

[toc] | [prev] | [next] | [standalone]

#184689

On Sat 05 Aug 2017 at 13:12:40 -0400, Jape Person wrote:

> On 08/05/2017 12:44 PM, Curt wrote:

[A bit of snipping for poetical reasons].

> >Frankly I would be leery of going through the procedure without a lot of
> >wine for fear of bricking my device.
> 
> A lot of wine is almost always good.

You have forgotten the other two essential ingredients:

 A Jug of Wine, a Loaf of Bread — and Thou

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184690

On 08/05/2017 02:28 PM, Brian wrote:
> On Sat 05 Aug 2017 at 13:12:40 -0400, Jape Person wrote:
> 
>> On 08/05/2017 12:44 PM, Curt wrote:
> 
> [A bit of snipping for poetical reasons].
> 
>>> Frankly I would be leery of going through the procedure without a lot of
>>> wine for fear of bricking my device.
>>
>> A lot of wine is almost always good.
> 
> You have forgotten the other two essential ingredients:
> 
>   A Jug of Wine, a Loaf of Bread — and Thou
> 
It's getting a little cheesy in here. I fear that someone will be along 
at any moment to smack our hands with a ruler.

<pepper pot> And no spam! I hate spam! </pepper pot>

[toc] | [prev] | [next] | [standalone]

#184693

On Sat 05 Aug 2017 at 14:44:46 -0400, Jape Person wrote:

> On 08/05/2017 02:28 PM, Brian wrote:
> >On Sat 05 Aug 2017 at 13:12:40 -0400, Jape Person wrote:
> >
> >>On 08/05/2017 12:44 PM, Curt wrote:
> >
> >[A bit of snipping for poetical reasons].
> >
> >>>Frankly I would be leery of going through the procedure without a lot of
> >>>wine for fear of bricking my device.
> >>
> >>A lot of wine is almost always good.
> >
> >You have forgotten the other two essential ingredients:
> >
> >  A Jug of Wine, a Loaf of Bread — and Thou
> >
> It's getting a little cheesy in here. I fear that someone will be along at
> any moment to smack our hands with a ruler.

You have in mind that nonentity who wrote

  A Jug of Wine, a Chunk of Cheddar — and Thou

and who didn't understand scanning. Don't worry about it. Most people
here are fans of Edward FitzGerald.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184698

On 08/05/2017 03:12 PM, Brian wrote:
> On Sat 05 Aug 2017 at 14:44:46 -0400, Jape Person wrote:
> 
>> On 08/05/2017 02:28 PM, Brian wrote:
>>> On Sat 05 Aug 2017 at 13:12:40 -0400, Jape Person wrote:
>>>
>>>> On 08/05/2017 12:44 PM, Curt wrote:
>>>
>>> [A bit of snipping for poetical reasons].
>>>
>>>>> Frankly I would be leery of going through the procedure without a lot of
>>>>> wine for fear of bricking my device.
>>>>
>>>> A lot of wine is almost always good.
>>>
>>> You have forgotten the other two essential ingredients:
>>>
>>>   A Jug of Wine, a Loaf of Bread — and Thou
>>>
>> It's getting a little cheesy in here. I fear that someone will be along at
>> any moment to smack our hands with a ruler.
> 
> You have in mind that nonentity who wrote
> 
>    A Jug of Wine, a Chunk of Cheddar — and Thou
> 
> and who didn't understand scanning. Don't worry about it. Most people
> here are fans of Edward FitzGerald.
> 

I might have been thinking of my wife.

She's always asking if I want some cheese to go with my whine.

[toc] | [prev] | [next] | [standalone]

#184629

On 2017-08-04, Jape Person <japers@comcast.net> wrote:
> A few weeks ago a CUPS upgrade to our Debian testing systems started 
> showing a new driver for our Brother MFC-9340CDW in print dialogs and in 
> the CUPS printer list and in the system-config-printer utility.
>
> You'd think that was good news, but we've been unable to find any way to 
> make the queue for this "driverless" instance of the printer function 
> properly.
>

Just very quickly found this bug that seems to be relevant to your case,
Jape. As you didn't describe the "garbled" condition of your printouts
with the "driverless" driver I can't be sure but it seems a fair guess.

Apparently a resolution dpi error (reported as 600x2dpi--firmware
bug?--and set that way by cups in the PPD.  Workaroundable by modifying
the PPD manually as explained in the thread).

BTW at the Brother site I think they're recommending updating the
firmware for this printer (maybe not for the reasons explicited here).

HTH.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868360



-- 
“Certitude is not the test of certainty.”
--Oliver Wendell Holmes, Jr.

[toc] | [prev] | [next] | [standalone]

#184630

On Fri 04 Aug 2017 at 12:25:51 +0000, Curt wrote:

> On 2017-08-04, Jape Person <japers@comcast.net> wrote:
> > A few weeks ago a CUPS upgrade to our Debian testing systems started 
> > showing a new driver for our Brother MFC-9340CDW in print dialogs and in 
> > the CUPS printer list and in the system-config-printer utility.
> >
> > You'd think that was good news, but we've been unable to find any way to 
> > make the queue for this "driverless" instance of the printer function 
> > properly.
> >
> 
> Just very quickly found this bug that seems to be relevant to your case,
> Jape. As you didn't describe the "garbled" condition of your printouts
> with the "driverless" driver I can't be sure but it seems a fair guess.
> 
> Apparently a resolution dpi error (reported as 600x2dpi--firmware
> bug?--and set that way by cups in the PPD.  Workaroundable by modifying
> the PPD manually as explained in the thread).

Definitely a firmware bug; the printer is non-conforming. cups-browsed
puts the incorrect information in the PPD because it queries the printer
and that is what it is told.
 
> BTW at the Brother site I think they're recommending updating the
> firmware for this printer (maybe not for the reasons explicited here).
> 
> HTH.
> 
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868360

If the OP has his testing systems up-to-date, he should not be seeing
this bug.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184646

On 08/04/2017 08:58 AM, Brian wrote:
> On Fri 04 Aug 2017 at 12:25:51 +0000, Curt wrote:
> 
>> On 2017-08-04, Jape Person <japers@comcast.net> wrote:
>>> A few weeks ago a CUPS upgrade to our Debian testing systems started
>>> showing a new driver for our Brother MFC-9340CDW in print dialogs and in
>>> the CUPS printer list and in the system-config-printer utility.
>>>
>>> You'd think that was good news, but we've been unable to find any way to
>>> make the queue for this "driverless" instance of the printer function
>>> properly.
>>>
>>
>> Just very quickly found this bug that seems to be relevant to your case,
>> Jape. As you didn't describe the "garbled" condition of your printouts
>> with the "driverless" driver I can't be sure but it seems a fair guess.
>>
>> Apparently a resolution dpi error (reported as 600x2dpi--firmware
>> bug?--and set that way by cups in the PPD.  Workaroundable by modifying
>> the PPD manually as explained in the thread).
> 
> Definitely a firmware bug; the printer is non-conforming. cups-browsed
> puts the incorrect information in the PPD because it queries the printer
> and that is what it is told.
>   

Seems like this must be the case. Too bad. Updating firmware on this 
thing requires trundling it out of the den, down the hall and to the 
living room so I can attach it to a Windows box.

I'll look into this and get back to you and Curt to let you know whether 
or not the printer is already running the latest firmware.

>> BTW at the Brother site I think they're recommending updating the
>> firmware for this printer (maybe not for the reasons explicited here).
>>
>> HTH.
>>
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868360
> 
> If the OP has his testing systems up-to-date, he should not be seeing
> this bug.
> 

All three testing systems are upgraded daily, so I'll check into it and 
get back to you.

Again, many thanks to you and Curt.

[toc] | [prev] | [next] | [standalone]

#184648

On 08/04/2017 08:58 AM, Brian wrote:
> On Fri 04 Aug 2017 at 12:25:51 +0000, Curt wrote:
> 
>> On 2017-08-04, Jape Person <japers@comcast.net> wrote:
>>> A few weeks ago a CUPS upgrade to our Debian testing systems
>>> started showing a new driver for our Brother MFC-9340CDW in print
>>> dialogs and in the CUPS printer list and in the
>>> system-config-printer utility.
>>> 
>>> You'd think that was good news, but we've been unable to find any
>>> way to make the queue for this "driverless" instance of the
>>> printer function properly.
>>> 
>> 
>> Just very quickly found this bug that seems to be relevant to your
>> case, Jape. As you didn't describe the "garbled" condition of your
>> printouts with the "driverless" driver I can't be sure but it seems
>> a fair guess.
>> 
>> Apparently a resolution dpi error (reported as 600x2dpi--firmware 
>> bug?--and set that way by cups in the PPD.  Workaroundable by
>> modifying the PPD manually as explained in the thread).
> 
> Definitely a firmware bug; the printer is non-conforming.
> cups-browsed puts the incorrect information in the PPD because it
> queries the printer and that is what it is told.
> 
>> BTW at the Brother site I think they're recommending updating the 
>> firmware for this printer (maybe not for the reasons explicited
>> here).
>> 
>> HTH.
>> 
>> 
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868360
> 
> If the OP has his testing systems up-to-date, he should not be
> seeing this bug.
> 

Hi, Brian.

My Debian testing systems are definitely up-to-date, but it appears that 
I am still seeing the bug. Eyes are too tired for me to be able to go 
through the suggested PPD edit and other testing. When the world is this 
bleary I just can't count on getting dependable results.

The workable solution for me right now is to use the MFC-9320CW driver. 
It actually works quite well and gives me access to control of all 
printer functions that I need.

Turning off AirPrint didn't remove the advertised driverless print 
option in CUPS / system-config-printer / print dialogs. Oddly enough, 
turning off WiFi Direct did eliminate it. I know I'm being 
simple-minded, but the printer's wireless adapter isn't being used. It's 
connected to the router via Ethernet. Why do wireless settings affect 
what I see of this printer on the network?

At least now we don't have to select between one queue that does work 
and one that doesn't. Your suggestion about AirPrint / Bonjour in the 
other message prompted me to look through all of the wireless settings. 
I'm delighted not to have to look at the queue that doesn't work.

;-)

I'll eventually update the firmware when my attitude improves. The 
physical process in our particular location is a little tough for me. 
Right now I'm wondering why the version 1.08 firmware on my printer is 
not listed in the Brother support site's update history. Their list 
jumps from 1.07 (which came with the printer) to 1.09. They give no 
useful information about the purpose of the update (or any of the 
previous ones). Looks like someone there is just going through the motions.

Best regards,
JP

[toc] | [prev] | [next] | [standalone]

#184651

On Fri 04 Aug 2017 at 16:10:13 -0400, Jape Person wrote:

> On 08/04/2017 08:58 AM, Brian wrote:
> >On Fri 04 Aug 2017 at 12:25:51 +0000, Curt wrote:
> >
> >>On 2017-08-04, Jape Person <japers@comcast.net> wrote:
> >>>A few weeks ago a CUPS upgrade to our Debian testing systems
> >>>started showing a new driver for our Brother MFC-9340CDW in print
> >>>dialogs and in the CUPS printer list and in the
> >>>system-config-printer utility.
> >>>
> >>>You'd think that was good news, but we've been unable to find any
> >>>way to make the queue for this "driverless" instance of the
> >>>printer function properly.
> >>>
> >>
> >>Just very quickly found this bug that seems to be relevant to your
> >>case, Jape. As you didn't describe the "garbled" condition of your
> >>printouts with the "driverless" driver I can't be sure but it seems
> >>a fair guess.
> >>
> >>Apparently a resolution dpi error (reported as 600x2dpi--firmware
> >>bug?--and set that way by cups in the PPD.  Workaroundable by
> >>modifying the PPD manually as explained in the thread).
> >
> >Definitely a firmware bug; the printer is non-conforming.
> >cups-browsed puts the incorrect information in the PPD because it
> >queries the printer and that is what it is told.
> >
> >>BTW at the Brother site I think they're recommending updating the
> >>firmware for this printer (maybe not for the reasons explicited
> >>here).
> >>
> >>HTH.
> >>
> >>
> >>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868360
> >
> >If the OP has his testing systems up-to-date, he should not be
> >seeing this bug.
> >
> 
> Hi, Brian.
> 
> My Debian testing systems are definitely up-to-date, but it appears that I
> am still seeing the bug. Eyes are too tired for me to be able to go through
> the suggested PPD edit and other testing. When the world is this bleary I
> just can't count on getting dependable results.

Understandable. Sometimes it is better to leave it to another day and
look it with fresh eyes. TBH, that is also the way I feel now when it
comes to your switching off AirPrint not doing what is expected.
 
> The workable solution for me right now is to use the MFC-9320CW driver. It
> actually works quite well and gives me access to control of all printer
> functions that I need.
> 
> Turning off AirPrint didn't remove the advertised driverless print option in
> CUPS / system-config-printer / print dialogs. Oddly enough, turning off WiFi
> Direct did eliminate it. I know I'm being simple-minded, but the printer's
> wireless adapter isn't being used. It's connected to the router via
> Ethernet. Why do wireless settings affect what I see of this printer on the
> network?

Nothing immediately springs to mind. Something to think about, even
though your desire not to see the printer has been sorted. No wireless
capability anywhere on the network?
 
> At least now we don't have to select between one queue that does work and
> one that doesn't. Your suggestion about AirPrint / Bonjour in the other
> message prompted me to look through all of the wireless settings. I'm
> delighted not to have to look at the queue that doesn't work.
> 
> ;-)
> 
> I'll eventually update the firmware when my attitude improves. The physical
> process in our particular location is a little tough for me. Right now I'm
> wondering why the version 1.08 firmware on my printer is not listed in the
> Brother support site's update history. Their list jumps from 1.07 (which
> came with the printer) to 1.09. They give no useful information about the
> purpose of the update (or any of the previous ones). Looks like someone
> there is just going through the motions.

I wouldn't want to point the finger at Brother. Other printer vendors
are not all that great with changelog recording,

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#184653

On 08/04/2017 07:02 PM, Brian wrote:
> On Fri 04 Aug 2017 at 16:10:13 -0400, Jape Person wrote:
> 
>> On 08/04/2017 08:58 AM, Brian wrote:
>>> On Fri 04 Aug 2017 at 12:25:51 +0000, Curt wrote:
>>>
>>>> On 2017-08-04, Jape Person <japers@comcast.net> wrote:
>>>>> A few weeks ago a CUPS upgrade to our Debian testing systems
>>>>> started showing a new driver for our Brother MFC-9340CDW in print
>>>>> dialogs and in the CUPS printer list and in the
>>>>> system-config-printer utility.
>>>>>
>>>>> You'd think that was good news, but we've been unable to find any
>>>>> way to make the queue for this "driverless" instance of the
>>>>> printer function properly.
>>>>>
>>>>
>>>> Just very quickly found this bug that seems to be relevant to your
>>>> case, Jape. As you didn't describe the "garbled" condition of your
>>>> printouts with the "driverless" driver I can't be sure but it seems
>>>> a fair guess.
>>>>
>>>> Apparently a resolution dpi error (reported as 600x2dpi--firmware
>>>> bug?--and set that way by cups in the PPD.  Workaroundable by
>>>> modifying the PPD manually as explained in the thread).
>>>
>>> Definitely a firmware bug; the printer is non-conforming.
>>> cups-browsed puts the incorrect information in the PPD because it
>>> queries the printer and that is what it is told.
>>>
>>>> BTW at the Brother site I think they're recommending updating the
>>>> firmware for this printer (maybe not for the reasons explicited
>>>> here).
>>>>
>>>> HTH.
>>>>
>>>>
>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868360
>>>
>>> If the OP has his testing systems up-to-date, he should not be
>>> seeing this bug.
>>>
>>
>> Hi, Brian.
>>
>> My Debian testing systems are definitely up-to-date, but it appears that I
>> am still seeing the bug. Eyes are too tired for me to be able to go through
>> the suggested PPD edit and other testing. When the world is this bleary I
>> just can't count on getting dependable results.
> 
> Understandable. Sometimes it is better to leave it to another day and
> look it with fresh eyes. TBH, that is also the way I feel now when it
> comes to your switching off AirPrint not doing what is expected.
>   
>> The workable solution for me right now is to use the MFC-9320CW driver. It
>> actually works quite well and gives me access to control of all printer
>> functions that I need.
>>
>> Turning off AirPrint didn't remove the advertised driverless print option in
>> CUPS / system-config-printer / print dialogs. Oddly enough, turning off WiFi
>> Direct did eliminate it. I know I'm being simple-minded, but the printer's
>> wireless adapter isn't being used. It's connected to the router via
>> Ethernet. Why do wireless settings affect what I see of this printer on the
>> network?
> 
> Nothing immediately springs to mind. Something to think about, even
> though your desire not to see the printer has been sorted. No wireless
> capability anywhere on the network?
>   

Printer is connected to the network only via CAT6 to the router. All 
computers are connected via wireless. But none of them has ever been 
given permission to connect directly to the printer.

>> At least now we don't have to select between one queue that does work and
>> one that doesn't. Your suggestion about AirPrint / Bonjour in the other
>> message prompted me to look through all of the wireless settings. I'm
>> delighted not to have to look at the queue that doesn't work.
>>
>> ;-)
>>
>> I'll eventually update the firmware when my attitude improves. The physical
>> process in our particular location is a little tough for me. Right now I'm
>> wondering why the version 1.08 firmware on my printer is not listed in the
>> Brother support site's update history. Their list jumps from 1.07 (which
>> came with the printer) to 1.09. They give no useful information about the
>> purpose of the update (or any of the previous ones). Looks like someone
>> there is just going through the motions.
> 
> I wouldn't want to point the finger at Brother. Other printer vendors
> are not all that great with changelog recording,
> 

Oh, I know. A support group is given lots of "motions" to go through, 
and probably precious little time for the going. But that certainly 
results in frustrations for end users who need information. When you're 
using an OS other than Windows or MacOS you're going to feel short-changed.

I remember how annoyed I was once just after WinXP was released that my 
wife connected a new HP printer to her system and just stuck the 
included software CD in the optical drive. The software that got 
installed was bigger than the OS. No foolin'. Memory may be failing me, 
but I swear that at least a half-dozen services were installed without 
so much as a by-your-leave.

Maybe I'd actually rather be short-changed, come to think of it.

[toc] | [prev] | [next] | [standalone]

#184644

On 08/04/2017 08:25 AM, Curt wrote:
> On 2017-08-04, Jape Person <japers@comcast.net> wrote:
>> A few weeks ago a CUPS upgrade to our Debian testing systems
>> started showing a new driver for our Brother MFC-9340CDW in print
>> dialogs and in the CUPS printer list and in the
>> system-config-printer utility.
>> 
>> You'd think that was good news, but we've been unable to find any
>> way to make the queue for this "driverless" instance of the printer
>> function properly.
>> 
> 
> Just very quickly found this bug that seems to be relevant to your
> case, Jape. As you didn't describe the "garbled" condition of your
> printouts with the "driverless" driver I can't be sure but it seems a
> fair guess.

I should have been more careful in describing the output. Eyes are old, 
and thought the was garbling, but closer exam with magnifying glass 
reveals that it's all just distorted -- as in compressed vertically.
> 
> Apparently a resolution dpi error (reported as 600x2dpi--firmware 
> bug?--and set that way by cups in the PPD.  Workaroundable by
> modifying the PPD manually as explained in the thread).
> 
> BTW at the Brother site I think they're recommending updating the 
> firmware for this printer (maybe not for the reasons explicited
> here).
> 
> HTH. >
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868360
> 

Mercy! Why didn't I look in bug reports? Sheesh! The brain is really 
just kind of occupying space between the ears these days!

I'll check the firmware. I already updated it once on this printer, and 
it was a pain. (Required buying a Windows computer.)

I'll also go through the thread to see what I can learn.

Many thanks to you, Curt!

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web