Re: Printer problem

[Brian]

On Sat 14 Dec 2013 at 20:37:09 +0100, Siard wrote:

> Gábor Hársfalvi wrote off-list:

If his reply to my post was off-list it will never be seen by me (I only
receive and respond to on-list mail) or (obviously) anyone else. If
Gábor is looking for a response he should check whether any mail was
sent to debian-user.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/14122013202748.abc3ba1a7...@desktop.copernicus.demon.co.uk

Re: Printer problem

[Siard]

Gábor Hársfalvi wrote off-list:
> Thanks.
>
> So we could tell the driver to use only the black ink for black
> texts/images?

No.  A document containing composite black text is simply not suitable
for printing.  You should try to get a better document.

Of course, you can tell the driver to print only black & white.
But then everything is in grayscale.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131214203709.3346de84.shiems...@kpnplanet.nl

Re: Printer problem

[Siard]

Gábor Hársfalvi wrote:
> We have got a HP Inkjet f2180 printer and we need use pure black ink
> instead of composite black every time.
> 
> How to do this?

The document to be printed should contain pure black, that is,
CMYK values C=0% M=0% Y=0% K=100%.
Printing offices also require this if you have your document printed
there.

As far as I can see, LibreOffice produces pure black.
PDF's produced by Scribus certainly comply with the standards.
I've often seen documents made with Word, converted to a PDF with a
third party program, that do _not_ have pure black. Don't know what the
latest state of affairs w.r.t. this is though.

In the case of a PDF, if it does not contain pure black, I know that
the latest Adobe Acrobat can do a conversion to repair this.
But of course, that is not a free program, and needs MacOSX or Windows.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131214191533.80474e72.shiems...@kpnplanet.nl

Re: Printer problem

[Brian]

On Sat 14 Dec 2013 at 11:22:08 +0100, Gábor Hársfalvi wrote:

> We have got a HP Inkjet f2180 printer and we need use pure black ink
> instead of composite black every time.
> 
> How to do this?

What driver package and PPD are you using?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/14122013125105.e5ccfb936...@desktop.copernicus.demon.co.uk

Printer problem

[Gábor Hársfalvi]

Hi,

We have got a HP Inkjet f2180 printer and we need use pure black ink
instead of composite black every time.

How to do this?

Re: Suggestion for buying/repairing print (was: "Chicken-egg" printer problem)

[Lisi]

On Wednesday 20 October 2010 12:13:15 Rodolfo Medina wrote:
> Rodolfo Medina  writes:
> >> However, I have now another problem: after cleaning the heads, the print
> >> quality remains bad.  They told me it may depend on the heads dried or
> >> maybe broken.  In any case, they told that the printer needs being taken
> >> to an assistence centre.
> >>
> >> Any suggestion about that?
> >
> > It seems that I need a new printer: where can I find a list of all the
> > printers that are known to be compatible with Debian Lenny?
>
> Thanks to all for the suggestions.
>
> Rodolfo

There have been several recommendations, deservedly, for HP.  But I have a 
cheap Samsung, the ML1510.  It was reduced to half price because it was end 
of line, and was cheap in the first place.  It runs marvellously with various 
distros.  Initially I had to find and install drivers.  Now I just install 
splix (same idea as HPLIP).

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201010311034.40384.lisi.re...@gmail.com

Re: Suggestion for buying/repairing print (was: "Chicken-egg" printer problem)

[Rodolfo Medina]

Rodolfo Medina  writes:

>> However, I have now another problem: after cleaning the heads, the print
>> quality remains bad.  They told me it may depend on the heads dried or maybe
>> broken.  In any case, they told that the printer needs being taken to an
>> assistence centre.
>>
>> Any suggestion about that?
>
>
> It seems that I need a new printer: where can I find a list of all the
> printers that are known to be compatible with Debian Lenny?



Thanks to all for the suggestions.

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87fww1p16c.fsf...@gmail.com

Re: [solved] Re: "Chicken-egg" printer problem

[Jörg-Volker Peetz]

Since you are about to scrap the printer, you could try some harder
methods. Searching for "epson print head cleaning" you can find advices,
how to try to clean a dried print head without disassembling the
printer, e.g., http://www.2manuals.com/head_clean.php
Instead of a syringe I used a Q-tip (cotton-wool tip) and was able to
revive my Epson inkjet printer.
-- 
Best regards,
Jörg-Volker.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/i9ma8d$bm...@dough.gmane.org

Re: [solved] Re: "Chicken-egg" printer problem

[Doug]

On 10/19/2010 07:31 AM, Rodolfo Medina wrote:

Camaleón  writes:

   

So, in brief:

1/ There is still a small quantity of ink in cartridges
2/ But the printer does not print because its cleaning heads are
obturated or dirty.
3/ You cannot perform a maintenance task because there is not enough ink
4/ The printer does not respond to a cartridge replacement even once you
have pressed the required buttons
5/ Therefore, you are completely stuck

In this situation, I would just contact Epson and tell about this. They
know the printer and could suggest you the right steps.

I (for my self) just would try to manually ("force") the cartridges to
put into the "replace" position but doing this can break the printer, so
dunno... if you cannot afford another printer, be careful or ask Epson
first :-/
 



I spoke with a customer care telephone number and they suggested the solution:
keeping the maintenance button (the right one) pressed for a long time (say 5
seconds), we force the substitution: the heads move to the replacement position
and the cartridge can be replaced before they're completely empty.  The
chicken-egg problem is so overcome.

However, I have now another problem: after cleaning the heads, the print
quality remains bad.  They told me it may depend on the heads dried or maybe
broken.  In any case, they told that the printer needs being taken to an
assistence centre.

Any suggestion about that?

Thanks for anyone's help!

Rodolfo


   
I don't know where you live, but in the US, the price any repair place 
would charge

would certainly buy you a new printer, or darned near it.

--doug

--
Blessed are the peacemakers...for they shall be shot at from both sides. --A. 
M. Greeley


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4cbe479a.9060...@optonline.net

Re: [solved] Re: "Chicken-egg" printer problem

[Eduardo M KALINOWSKI]

 On 10/19/2010 09:31 AM, Rodolfo Medina wrote:

However, I have now another problem: after cleaning the heads, the print
quality remains bad.  They told me it may depend on the heads dried or maybe
broken.  In any case, they told that the printer needs being taken to an
assistence centre.

Any suggestion about that?


Yeah, forget about crappy inkjet printers and buy a laser one. Initial 
cost is higher, but the actual cost per page is less, and they tend to 
last for a much longer time, especially if they're not the cheapest 
ones. But even the cheapest lasers are probably more durable than an 
average inkjet.




--
Hell is empty and all the devils are here.
-- Wm. Shakespeare, "The Tempest"

Eduardo M KALINOWSKI
edua...@kalinowski.com.br


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4cbe005b.3020...@kalinowski.com.br

Re: [solved] Re: "Chicken-egg" printer problem

[Gilbert Sullivan]

On 10/19/2010 11:40 AM, Klistvud wrote:


The "printer and cartridges" business model has been a thorn in the side
of conscientious consumers for years.



You can say that again! Although I might characterize the position of 
the pain as being more toward the posterior than the side.


;-)


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4cbdc3ed.80...@comcast.net

Re: [solved] Re: "Chicken-egg" printer problem

[Klistvud]

Dne, 19. 10. 2010 15:05:21 je Gilbert Sullivan napisal(a):


In addition to considering the compatibility of a printer with your  
OS you might want to consider its design compatibility with your  
printing needs.


The issue you ran into with your Epson not being able to clear its  
print heads effectively is one I've run into before. If you use an  
inkjet printer only sporadically you may be best served by buying an  
inkjet printer design which replaces the print heads along with the  
Ink cartridges. This makes the replacement cartridges much more  
expensive, but it means you get new print heads when you replace the  
cartridges.


If your needs can be handled by a b&w or color laser printer, that's  
even better. Laser printers cost more up front, but mine have more  
than paid for the cost differential with inkjet printers in the lower  
long-range cost of operation. (Laser printer cartridges cost a lot,  
but the last much, much longer than inkjet cartridges.)


Excellent advice. Couldn't agree more. In addition, depending on your  
situation and location, you may consider additional options, such as:


-- are your printing needs sporadic enough to warrant the services of a  
printing shop? Many printing shops accept files on USB sticks, CDs etc.  
and then print the files for you at affordable prices -- and you  
generally get state-of-the art printout quality;
-- is your neighborhood (or condo, or household) large and friendly  
enough to warrant the purchase of a quality newtorked laser  
printer/copier in common, for all the members to use (and to place in  
the lobby or something)?


The "printer and cartridges" business model has been a thorn in the  
side of conscientious consumers for years.


--
Regards,

Klistvud
Certifiable Loonix User #481801
http://bufferoverflow.tiddlyspot.com

Please reply to the list, not to me.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1287502807.2611...@compax

Re: [solved] Re: "Chicken-egg" printer problem

[Camaleón]

On Tue, 19 Oct 2010 13:59:36 +0200, Rodolfo Medina wrote:

> Rodolfo Medina writes:
> 
>> However, I have now another problem: after cleaning the heads, the
>> print quality remains bad.  They told me it may depend on the heads
>> dried or maybe broken.  In any case, they told that the printer needs
>> being taken to an assistence centre.
>>
>> Any suggestion about that?

No, sorry ;-(

It's years since I've not played with inkjet printers (my last one was an 
Epson Stylus Photo 1290).
 
> It seems that I need a new printer: where can I find a list of all the
> printers that are known to be compatible with Debian Lenny?

If you can buy it, I'd suggest a laser printer that plays fine with linux 
(HP have some nice and quite affordable models).

Another option (and for casual/non intensive usage), would be those 
called all-in-one devices, where, again, HP has some good and linux 
compatible models.

As for the compatibilty list, just select one model you like and then 
perform the search. For example, HP linux compatible (and all-in-one)
printers can be looked up here:

http://hplipopensource.com/hplip-web/supported_devices/index.html

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.10.19.13.34...@gmail.com

Re: [solved] Re: "Chicken-egg" printer problem

[Gilbert Sullivan]

On 10/19/2010 07:59 AM, Rodolfo Medina wrote:

Rodolfo Medina  writes:


However, I have now another problem: after cleaning the heads, the print
quality remains bad.  They told me it may depend on the heads dried or maybe
broken.  In any case, they told that the printer needs being taken to an
assistence centre.

Any suggestion about that?



It seems that I need a new printer: where can I find a list of all the printers
that are known to be compatible with Debian Lenny?

Bye
Rodolfo



Hi, Rodolfo.

In addition to considering the compatibility of a printer with your OS 
you might want to consider its design compatibility with your printing 
needs.


The issue you ran into with your Epson not being able to clear its print 
heads effectively is one I've run into before. If you use an inkjet 
printer only sporadically you may be best served by buying an inkjet 
printer design which replaces the print heads along with the Ink 
cartridges. This makes the replacement cartridges much more expensive, 
but it means you get new print heads when you replace the cartridges.


If your needs can be handled by a b&w or color laser printer, that's 
even better. Laser printers cost more up front, but mine have more than 
paid for the cost differential with inkjet printers in the lower 
long-range cost of operation. (Laser printer cartridges cost a lot, but 
the last much, much longer than inkjet cartridges.)


All of this is generally speaking, of course. And I haven't even 
mentioned print quality. Each brand has its adherents. I'm happy as long 
as I can read the print, and I'm delighted if it actually looks pretty.


I think that you'll find that HP printers of various kinds are generally 
better supported in GNU/Linux.


Good luck!


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4cbd9791.5050...@comcast.net

Re: [solved] Re: "Chicken-egg" printer problem

[Paul Cartwright]

On Tue October 19 2010, Rodolfo Medina wrote:
> It seems that I need a new printer: where can I find a list of all the
> printers that are known to be compatible with Debian Lenny?

http://www.linuxprinting.org/


-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201010190822.36481.deb...@pcartwright.com

Re: [solved] Re: "Chicken-egg" printer problem

[Rodolfo Medina]

Rodolfo Medina  writes:

> However, I have now another problem: after cleaning the heads, the print
> quality remains bad.  They told me it may depend on the heads dried or maybe
> broken.  In any case, they told that the printer needs being taken to an
> assistence centre.
>
> Any suggestion about that?


It seems that I need a new printer: where can I find a list of all the printers
that are known to be compatible with Debian Lenny?

Bye
Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87aama8kbb@gmail.com

[solved] Re: "Chicken-egg" printer problem

[Rodolfo Medina]

Camaleón  writes:

> So, in brief:
>
> 1/ There is still a small quantity of ink in cartridges
> 2/ But the printer does not print because its cleaning heads are 
> obturated or dirty.
> 3/ You cannot perform a maintenance task because there is not enough ink
> 4/ The printer does not respond to a cartridge replacement even once you 
> have pressed the required buttons
> 5/ Therefore, you are completely stuck
>
> In this situation, I would just contact Epson and tell about this. They 
> know the printer and could suggest you the right steps.
>
> I (for my self) just would try to manually ("force") the cartridges to 
> put into the "replace" position but doing this can break the printer, so 
> dunno... if you cannot afford another printer, be careful or ask Epson 
> first :-/



I spoke with a customer care telephone number and they suggested the solution:
keeping the maintenance button (the right one) pressed for a long time (say 5
seconds), we force the substitution: the heads move to the replacement position
and the cartridge can be replaced before they're completely empty.  The
chicken-egg problem is so overcome.

However, I have now another problem: after cleaning the heads, the print
quality remains bad.  They told me it may depend on the heads dried or maybe
broken.  In any case, they told that the printer needs being taken to an
assistence centre.

Any suggestion about that?

Thanks for anyone's help!

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87sk028llg.fsf...@gmail.com

Re: "Chicken-egg" printer problem

[Camaleón]

On Tue, 19 Oct 2010 11:23:24 +0200, Rodolfo Medina wrote:

(...)

>> Then try with these steps:
>>
>> http://support.epson-europe.com/onlineguides/en/sc20/ref_g/ink_1.htm
> 
> 
> Those steps require the cartridges to be completely empty, otherwise the
> heads won't reach the replacement position:
> 
>   "Do not move the print head by hand, as this may damage the
>printer. Always press the  maintenance button to move it."

So, in brief:

1/ There is still a small quantity of ink in cartridges
2/ But the printer does not print because its cleaning heads are 
obturated or dirty.
3/ You cannot perform a maintenance task because there is not enough ink
4/ The printer does not respond to a cartridge replacement even once you 
have pressed the required buttons
5/ Therefore, you are completely stuck

In this situation, I would just contact Epson and tell about this. They 
know the printer and could suggest you the right steps.

I (for my self) just would try to manually ("force") the cartridges to 
put into the "replace" position but doing this can break the printer, so 
dunno... if you cannot afford another printer, be careful or ask Epson 
first :-/

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.10.19.10.12...@gmail.com

Re: "Chicken-egg" printer problem

[Rodolfo Medina]

Rodolfo Medina  writes:

> I'm facing the following odd problem:
>
> when I do: `escputil -c' to clean the printer's heads, the output looks good:
>
> $ escputil -c -r /dev/usb/lp0
> Escputil version 5.0.2, Copyright (C) 2000-2006 Robert Krawitz
> Escputil comes with ABSOLUTELY NO WARRANTY; for details type 'escputil -l'
> This is free software, and you are welcome to redistribute it
> under certain conditions; type 'escputil -l' for details.
>
> Cleaning heads...
>
>
> , but then nothing happens and the heads are not cleaned.  I suspect this
> happens because the ink is short and the system is waiting for it to finish
> completely.  But then I have the following problem:
>
> 1) until the ink is not finished, I can't clean heads;
>
> 2) until the heads are not cleaned, the paper is left blank and so the ink is
>not used up and cannot finish.
>
> What to do in this case?  From cups mailing list I got no indications.



Camaleón  writes:

> If your ink levels are so low that cleaning is not possible, replace the 
> ink cartridges. I suppose you can force a "replacement" :-?



Rodolfo Medina  writes:

>> I don't know how: until the ink is completely finished, the cartridges
>> won't reach the replacement position.  :(


Camaleón  writes:

> If you have no way to force a replacement, just print 100 copies of a 
> multi-colored image to empty the cartridges :-P



On 10/18/2010 05:33 PM, Rodolfo Medina wrote:

>> But it's just this the problem: as I said, the paper is left blank because
>> the
>> heads are dirty, both black and coloured print.


Eduardo M KALINOWSKI  writes:

> Maybe the ink has dried, then there's not much you can do.
>
> Regardless of the cause, can't you just replace the cartidge?


Camaleón  writes:

> You don't get "any" colour? Neither black or greyish? Nada? :-?

No, nothing.



> Then try with these steps:
>
> http://support.epson-europe.com/onlineguides/en/sc20/ref_g/ink_1.htm


Those steps require the cartridges to be completely empty, otherwise the heads
won't reach the replacement position:

  "Do not move the print head by hand, as this may damage the
   printer. Always press the  maintenance button to move it."

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87d3r6bkoj@gmail.com

Re: Odd printer problem

[Camaleón]

On Mon, 18 Oct 2010 21:33:05 +0200, Rodolfo Medina wrote:

> Rodolfo Medina writes:
> 
>>> I don't know how: until the ink is completely finished, the cartridges
>>> won't reach the replacement position.  :(
> 
> 
> Camaleón writes:
> 
>> If you have no way to force a replacement, just print 100 copies of a
>> multi-colored image to empty the cartridges :-P
> 
> 
> 
> But it's just this the problem: as I said, the paper is left blank
> because the heads are dirty, both black and coloured print.

You don't get "any" colour? Neither black or greyish? Nada? :-?

Then try with these steps:

http://support.epson-europe.com/onlineguides/en/sc20/ref_g/ink_1.htm

If you are still unsuccessful, contact Epson and ask for feedback (this 
"chicken-egg" situation can happen also in Windows).

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.10.18.20.02...@gmail.com

Re: Odd printer problem

[Eduardo M KALINOWSKI]

 On 10/18/2010 05:33 PM, Rodolfo Medina wrote:
But it's just this the problem: as I said, the paper is left blank 
because the

heads are dirty, both black and coloured print.


Maybe the ink has dried, then there's not much you can do.

Regardless of the cause, can't you just replace the cartidge?


--
Here I am at the flea market but nobody is buying my urine sample bottles ...

Eduardo M KALINOWSKI
edua...@kalinowski.com.br


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4cbca5fd.9090...@kalinowski.com.br

Re: Odd printer problem

[Rodolfo Medina]

Rodolfo Medina  writes:

> I'm facing the following odd problem:
>
> when I do: `escputil -c' to clean the printer's heads, the output looks good:
>
> $ escputil -c -r /dev/usb/lp0
> Escputil version 5.0.2, Copyright (C) 2000-2006 Robert Krawitz
> Escputil comes with ABSOLUTELY NO WARRANTY; for details type 'escputil -l'
> This is free software, and you are welcome to redistribute it
> under certain conditions; type 'escputil -l' for details.
>
> Cleaning heads...
>
>
> , but then nothing happens and the heads are not cleaned.  I suspect this
> happens because the ink is short and the system is waiting for it to finish
> completely.  But then I have the following problem:
>
> 1) until the ink is not finished, I can't clean heads;
>
> 2) until the heads are not cleaned, the paper is left blank and so the ink is
>not used up and cannot finish.
>
> What to do in this case?  From cups mailing list I got no indications.



Camaleón  writes:

> If your ink levels are so low that cleaning is not possible, replace the 
> ink cartridges. I suppose you can force a "replacement" :-?



Rodolfo Medina  writes:

>> I don't know how: until the ink is completely finished, the cartridges
>> won't reach the replacement position.  :(


Camaleón  writes:

> If you have no way to force a replacement, just print 100 copies of a 
> multi-colored image to empty the cartridges :-P



But it's just this the problem: as I said, the paper is left blank because the
heads are dirty, both black and coloured print.

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87aambjnym@gmail.com

Re: Odd printer problem

[Camaleón]

On Mon, 18 Oct 2010 18:36:24 +0200, Rodolfo Medina wrote:

> Rodolfo Medina  writes:

>> What to do in this case?  From cups mailing list I got no indications.
> 
> 
> 
> Camaleón writes:
> 
>> If your ink levels are so low that cleaning is not possible, replace
>> the ink cartridges. I suppose you can force a "replacement" :-?
> 
> 
> 
> Rodolfo Medina writes:
> 
>>> I don't know how: until the ink is completely finished, the cartridges
>>> won't reach the replacement position.  :(
> 
> 
> 
> Lisi writes:
> 
>> Which printer is this?
> 
> 
> Old Epson Stylus C20UX.

If you have no way to force a replacement, just print 100 copies of a 
multi-colored image to empty the cartridges :-P

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.10.18.16.49...@gmail.com

Re: Odd printer problem

[Rodolfo Medina]

Rodolfo Medina  writes:

> I'm facing the following odd problem:
>
> when I do: `escputil -c' to clean the printer's heads, the output looks good:
>
> $ escputil -c -r /dev/usb/lp0
> Escputil version 5.0.2, Copyright (C) 2000-2006 Robert Krawitz
> Escputil comes with ABSOLUTELY NO WARRANTY; for details type 'escputil -l'
> This is free software, and you are welcome to redistribute it
> under certain conditions; type 'escputil -l' for details.
>
> Cleaning heads...
>
>
> , but then nothing happens and the heads are not cleaned.  I suspect this
> happens because the ink is short and the system is waiting for it to finish
> completely.  But then I have the following problem:
>
> 1) until the ink is not finished, I can't clean heads;
>
> 2) until the heads are not cleaned, the paper is left blank and so the ink is
>not used up and cannot finish.
>
> What to do in this case?  From cups mailing list I got no indications.



Camaleón  writes:

> If your ink levels are so low that cleaning is not possible, replace the 
> ink cartridges. I suppose you can force a "replacement" :-?



Rodolfo Medina  writes:

>> I don't know how: until the ink is completely finished, the cartridges
>> won't reach the replacement position.  :(



Lisi  writes:

> Which printer is this?


Old Epson Stylus C20UX.

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87hbgje9vb@gmail.com

Re: Odd printer problem

[Lisi]

On Monday 18 October 2010 13:39:50 Rodolfo Medina wrote:
> Rodolfo Medina  writes:
> > I'm facing the following odd problem:
[snip]
> > when I do: `escputil -c' to clean the printer's heads, the output looks
> > good:
[snip]
> > , but then nothing happens and the heads are not cleaned. 
[snip]

> Camaleón  writes:
> > If your ink levels are so low that cleaning is not possible, replace the
> > ink cartridges. I suppose you can force a "replacement" :-?

> I don't know how: until the ink is completely finished, the cartridges
> won't reach the replacement position.  :(

Which printer is this?

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201010181443.18382.lisi.re...@gmail.com

Re: Odd printer problem

[Rodolfo Medina]

Rodolfo Medina  writes:

> I'm facing the following odd problem:
>
> when I do: `escputil -c' to clean the printer's heads, the output looks good:
>
> $ escputil -c -r /dev/usb/lp0
> Escputil version 5.0.2, Copyright (C) 2000-2006 Robert Krawitz
> Escputil comes with ABSOLUTELY NO WARRANTY; for details type 'escputil -l'
> This is free software, and you are welcome to redistribute it
> under certain conditions; type 'escputil -l' for details.
>
> Cleaning heads...
>
>
> , but then nothing happens and the heads are not cleaned.  I suspect this
> happens because the ink is short and the system is waiting for it to finish
> completely.  But then I have the following problem:
>
> 1) until the ink is not finished, I can't clean heads;
>
> 2) until the heads are not cleaned, the paper is left blank and so the ink is
>not used up and cannot finish.
>
> What to do in this case?  From cups mailing list I got no indications.



Camaleón  writes:

> If your ink levels are so low that cleaning is not possible, replace the 
> ink cartridges. I suppose you can force a "replacement" :-?



I don't know how: until the ink is completely finished, the cartridges won't
reach the replacement position.  :(

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87hbgj1xpl@gmail.com

Re: Odd printer problem

[Camaleón]

On Sun, 17 Oct 2010 11:34:07 +0200, Rodolfo Medina wrote:

(...)

> , but then nothing happens and the heads are not cleaned.  I suspect
> this happens because the ink is short and the system is waiting for it
> to finish completely.  But then I have the following problem:
> 
> 1) until the ink is not finished, I can't clean heads;

Printer head cleaning needs ink to perform the task.

> 2) until the heads are not cleaned, the paper is left blank and so the
> ink is
>not used up and cannot finish.
> 
> What to do in this case?  From cups mailing list I got no indications.

If your ink levels are so low that cleaning is not possible, replace the 
ink cartridges. I suppose you can force a "replacement" :-?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.10.17.13.40...@gmail.com

Odd printer problem

[Rodolfo Medina]

I'm facing the following odd problem:

when I do: `escputil -c' to clean the printer's heads, the output looks good:

$ escputil -c -r /dev/usb/lp0
Escputil version 5.0.2, Copyright (C) 2000-2006 Robert Krawitz
Escputil comes with ABSOLUTELY NO WARRANTY; for details type 'escputil -l'
This is free software, and you are welcome to redistribute it
under certain conditions; type 'escputil -l' for details.

Cleaning heads...


, but then nothing happens and the heads are not cleaned.  I suspect this
happens because the ink is short and the system is waiting for it to finish
completely.  But then I have the following problem:

1) until the ink is not finished, I can't clean heads;

2) until the heads are not cleaned, the paper is left blank and so the ink is
   not used up and cannot finish.

What to do in this case?  From cups mailing list I got no indications.

Thanks for any help.

Rodolfo


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874ocl6u40@gmail.com

Re: panasonic printer problem

[Ron Johnson]

On 2009-07-25 12:57, Jude DaShiell wrote:
This is getting interesting now and I have some good news.  I hooked the 
printer up to a real dos box that never had any other operating system 
on it and used a file manager to print a file.  This time, the file came 
out legible with no garbage.  So, I'm thinking printing with this kind 
of printer using Linux will probably work only using cat filename 
 >/dev/lp0 and not using any of the other printing facilities.  I could 
be wrong about that but don't think so.  I'll try later and get some 
assistance finding out what happened.


It being a line printer, that would not surprise me.  Besides, 
dot-matrix graphics???  Eeew.


And *noisy*. 45 minutes of "zt zt zt zt zt 
zt zt zt zt zt zt zt zt zt 
zt zt zt zt zt zt zt zt zt 
zt zt zt" has been ruled "torture" by the Internation 
Court of Human Rights.


--
Scooty Puff, Sr
The Doom-Bringer


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

re: panasonic printer problem

[Jude DaShiell]

This is getting interesting now and I have some good news.  I hooked the 
printer up to a real dos box that never had any other operating system on 
it and used a file manager to print a file.  This time, the file came out 
legible with no garbage.  So, I'm thinking printing with this kind of 
printer using Linux will probably work only using cat filename >/dev/lp0 
and not using any of the other printing facilities.  I could be wrong 
about that but don't think so.  I'll try later and get some assistance 
finding out what happened.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: panasonic printer problem

[Ron Johnson]

On 2009-07-25 01:35, Jude DaShiell wrote:
Was there a firmware update released for the KXP-1123 during its 
history? It could be the ppd file that's available for that printer 
needs that firmware update installed if such exists.


Do those old printers even have the capability to flash their 
EEPROMS?  Do they even *have* EEPROMS?


--
Scooty Puff, Sr
The Doom-Bringer


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

panasonic printer problem

[Jude DaShiell]

Was there a firmware update released for the KXP-1123 during its history? 
It could be the ppd file that's available for that printer needs that 
firmware update installed if such exists.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

update: Can't config cups printer, problem gone

[T o n g]

On Thu, 16 Oct 2008 04:14:35 +, T o n g wrote:

> I can't config my cups printer in my newly installed lenny system. 

Somehow, the command

 /usr/lib/cups/backend/usb

now returns my printer info. 

I turn off and on the printer before running the command, both when 
posting the OP, and now. The only different might be that I restarted the 
cups services this time.

Thanks everyone for your help. BTW, the initial problem when I can't add 
my printer is that, in my newly installed lenny system root password is 
different from what I used to have and I've forgot about that because I 
always use sudo su -- A fool's mistake will baffle a thousand wise guys. 

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

printer problem (prints postscript source, not document)

[Miles Bader]

My work has a combo copy-machine/fax/printer that works great with
windows (and seems really fast), but I can't seem to get it working
properly with debian/cups.

The printer model is:  "Canon iR C4580F"

I managed to locate it on the net, and configured it with cups'
webpage-configuration stuff, and even found a .ppd file for it on
Canon's website (no easy task, as naturally they distribute everything
as windows installable archives...).

The printer seems to use the "IPP" protocol, with a URL of
"ipp://dhypr434:631/ipp" (I've attached the /etc/cups/printers.conf
entry to this message).

The problem is that when I print to this printer, while it _does_ print
something, it prints the _postscript souce code_ for whatever I'm trying
to print!  This seems to happen no matter what input I feed cups
(postscript file, pdf file, ...) or what frontend I use (lpr command
from .ps file, mozilla print command, evince print command etc).

So, for instance, a very simple 1 page postscript file (see "test.ps"
attached to this message) results in the printer printing about 8 pages
of postscript source code.

Upon examining the postscript source code thus printed, I see two
things:

   (1) It's obviously the same postscript I fed it, but has been
   "augmented" by some filter along the way, fleshing out the various magic
   comments and adding some setup code etc.  I assume cups does this, but I
   don't think it's the problem.

   (2) The source code is "stair-stepped", with newlines only moving
   vertically.  This suggests that whoever converted the postscript into
   text for printing was expecting a windows line-ending convention.

I suppose (2) could be part of the problem, if somebody along the way is
expecting postscript using windows line-endings, and gets confused
because it gets only unix-style newlines.

If anybody has read this far, do you have any suggestions on where I
could look for the problem?

[Using wireshark, I can see lots of negotiation between cups and the
printer when I print something, but I'm not really sure what's correct
and what's not...]

Thanks,

-Miles


test.ps:



test.ps
Description: test.ps


cups printer.conf entry:



dhypr434.xml
Description: cups printers.conf for dhypr434


-- 
The secret to creativity is knowing how to hide your sources.
  --Albert Einstein

Re: usb/cups printer problem after etch upgrade

[Florian Kulzer]

On Sat, May 12, 2007 at 08:18:10 -0700, Nick Jacobs wrote:
> 
> 
> Florian Kulzer-3 wrote:
> > 
> > As far as I understand udev, it should always use the lowest free lpX
> > node for a new printer.
> > 
> That's just the problem, it doesn't always. If it did that consistently,
> nobody would have had a problem when upgrading from devfs/hotplug. It looks
> to me as though we have "upgraded" from something that was stable and worked
> (despite having some theoretical deficiencies) to something that is
> bug-ridden and unsuitable for general use (despite being theoretically
> wonderful).

I think there are two slightly different issues:

1) Removable devices, such as printers or external storage drives, which
   are not always present and which can be plugged in or switched on in
   changing order. I am not sure if devfs can ensure reserving the same
   device node for each specific device in that case. (I have to admit
   that I hardly know devfs; I started with Linux only after udev was
   the "norm".) Udev provides mechanisms to address this problem by
   generating device symlinks from properties such as volume labels and
   it allows you to specify your own rules on top of that. This is
   complemented by changes in other systems, e.g. CUPS now lets you
   specify the DeviceURI of printers by maker, model and serial number,
   which is independent of the actual lpX or usb/lpX device node.
   Partitions on storage devices can be addressed by labels or UUIDs in
   all important places (e.g. /etc/fstab or GRUB).

2) "Permanent" devices changing device nodes, e.g. different network
   cards in the same computer can alternate between eth0 and eth1. As
   far as I understand it, this is inherent in the new kernels which can
   exhibit changes in the order of loading modules. Udev has
   "persistent" rules which should take care of that by using e.g. the
   MAC address to assign a given ethX node always to the same ethernet
   card. If this automatic mechanism fails it is time to submit a bug
   report. Also, there are enough people on this list who can help you
   with fixing the rules yourself in case of trouble. A special problem
   arises if your system partitions change device nodes, for example due
   to a change in the driver (hdX -> sdY). Using volume labels or UUIDs
   for your bootloader and in fstab can save the day in that case, too.

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[Andrew Sackville-West]

On Sat, May 12, 2007 at 08:18:10AM -0700, Nick Jacobs wrote:
> 
> 
> Florian Kulzer-3 wrote:
> > 
> > As far as I understand udev, it should always use the lowest free lpX
> > node for a new printer.
> > 
> That's just the problem, it doesn't always. If it did that consistently,
> nobody would have had a problem when upgrading from devfs/hotplug. It looks
> to me as though we have "upgraded" from something that was stable and worked
> (despite having some theoretical deficiencies) to something that is
> bug-ridden and unsuitable for general use (despite being theoretically
> wonderful).

just .02, and not trying to deny or put down anyone's problems with
udev. And I'm sure you ()and many) are very frustrated.

I've had exactly 0 (zero) trouble with udev from day one on my 5 real
and 3 virtual debian machines. I suspect that is the case in most
applications. I think that the issue is that when it does go wrong, it
can go horribly wrong. But I also think it is plenty ready for general
usage.

cheers

A


signature.asc
Description: Digital signature

Re: usb/cups printer problem after etch upgrade

[Nick Jacobs]

Florian Kulzer-3 wrote:
> 
> As far as I understand udev, it should always use the lowest free lpX
> node for a new printer.
> 
That's just the problem, it doesn't always. If it did that consistently,
nobody would have had a problem when upgrading from devfs/hotplug. It looks
to me as though we have "upgraded" from something that was stable and worked
(despite having some theoretical deficiencies) to something that is
bug-ridden and unsuitable for general use (despite being theoretically
wonderful).
-- 
View this message in context: 
http://www.nabble.com/usb-cups-printer-problem-after-etch-upgrade-tf3651961.html#a10446799
Sent from the Debian User mailing list archive at Nabble.com.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[Florian Kulzer]

On Sat, May 05, 2007 at 07:34:30 -0700, Nick Jacobs wrote:
> Graham Seaman wrote:
> > 
> > After upgrading the server to etch (without any major problems) cups no 
> > longer sees the printer. Cups is running ok, and knows about the 
> > printer, but the web interface always displays the message:
> > 
> > " HL5040 (Default Printer) "Printer not connected; will retry in 30 
> > seconds..."
> > 
> > lsusb shows that the printer is there, and visible over wireless:
> > 
> > snoopy: lsusb
> > Bus 003 Device 002: ID 13fd:0540
> > Bus 003 Device 001: ID :
> > Bus 002 Device 001: ID :
> > Bus 001 Device 028: ID 04f9:0016 Brother Industries, Ltd
> > Bus 001 Device 001: ID :
> > 
> I had a similar problem and found that what happens is that Etch can assign
> a different lp device number to the printer every time it's turned on. So if
> your CUPS printer is set up as /dev/usb/lp0, CUPS won't see anything on lp0.
> lsusb tells you what the device number is. In your case, it seems to be 28
> (from above). So if you had reconfigured the printer as /dev/usb/lp28, it
> would have worked. This means you have to reconfigure the printer every time
> you turn it on and off again, which sucks. But at least you will be able to
> print.

We had addressed possible udev problems already, see here:

http://lists.debian.org/debian-user/2007/04/msg04804.html

Udev had created /dev/usb/lp0 with the correct permissions (as far as we
could tell). Nevertheless CUPS did not recognize the printer, not via
usb:/dev/usb/lp0 and not via usb://?serial=
either. Strangely enough, /usr/lib/cups/backend/usb did list the printer
correctly as "Brother HL-5040 series".

As far as I understand udev, it should always use the lowest free lpX
node for a new printer. That can still cause problems if you have
several printers that are plugged in or switched on in random order, but
you should only ever get "lp28" if there are really 28 other (USB)
printers connected already to occupy lp0 to lp27. The maker/model/serial
method of specifying the DeviceURI was introduced to avoid the problem
of changing lpX numbers. (You can also write your own udev rule to give
each printer an additional symlink in /dev/ as an unambiguous
identifier; see Andrew's earlier mail.)

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem

[slvr00gt]

I have exactly the same problem.  I tried your suggestion and changed lp0 to 
lp2 ( in my case printer is attached to device number 2).

It didn't help at all.  Same "printer not connected" message.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[Andrew Sackville-West]

On Sat, May 05, 2007 at 07:34:30AM -0700, Nick Jacobs wrote:
> 
> 
> Graham Seaman wrote:
> > 
> > After upgrading the server to etch (without any major problems) cups no 
> > longer sees the printer. Cups is running ok, and knows about the 
> > printer, but the web interface always displays the message:
> > 
> > " HL5040 (Default Printer) "Printer not connected; will retry in 30 
> > seconds..."
> > 
> > lsusb shows that the printer is there, and visible over wireless:
> > 
> > snoopy: lsusb
> > Bus 003 Device 002: ID 13fd:0540
> > Bus 003 Device 001: ID :
> > Bus 002 Device 001: ID :
> > Bus 001 Device 028: ID 04f9:0016 Brother Industries, Ltd
> > Bus 001 Device 001: ID :
> > 
> I had a similar problem and found that what happens is that Etch can assign
> a different lp device number to the printer every time it's turned on. So if
> your CUPS printer is set up as /dev/usb/lp0, CUPS won't see anything on lp0.
> lsusb tells you what the device number is. In your case, it seems to be 28
> (from above). So if you had reconfigured the printer as /dev/usb/lp28, it
> would have worked. This means you have to reconfigure the printer every time
> you turn it on and off again, which sucks. But at least you will be able to
> print.

you can write a custom udev rule to correct this problem, if that is
indeed the problem. google on "writing udev rules" and you'll get the
how-to in the first couple hits

A


signature.asc
Description: Digital signature

Re: usb/cups printer problem after etch upgrade

[Nick Jacobs]

Graham Seaman wrote:
> 
> After upgrading the server to etch (without any major problems) cups no 
> longer sees the printer. Cups is running ok, and knows about the 
> printer, but the web interface always displays the message:
> 
> " HL5040 (Default Printer) "Printer not connected; will retry in 30 
> seconds..."
> 
> lsusb shows that the printer is there, and visible over wireless:
> 
> snoopy: lsusb
> Bus 003 Device 002: ID 13fd:0540
> Bus 003 Device 001: ID :
> Bus 002 Device 001: ID :
> Bus 001 Device 028: ID 04f9:0016 Brother Industries, Ltd
> Bus 001 Device 001: ID :
> 
I had a similar problem and found that what happens is that Etch can assign
a different lp device number to the printer every time it's turned on. So if
your CUPS printer is set up as /dev/usb/lp0, CUPS won't see anything on lp0.
lsusb tells you what the device number is. In your case, it seems to be 28
(from above). So if you had reconfigured the printer as /dev/usb/lp28, it
would have worked. This means you have to reconfigure the printer every time
you turn it on and off again, which sucks. But at least you will be able to
print.

-- 
View this message in context: 
http://www.nabble.com/usb-cups-printer-problem-after-etch-upgrade-tf3651961.html#a10337018
Sent from the Debian User mailing list archive at Nabble.com.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[graham]

Hi Florian,

Unfortunately, I ran out of time to work on this. So I have abandoned my 
 print server and temporarily moved to using the printer as a local 
printer attached to the parallel port on my workstation. When it gets 
sufficiently annoying not to be able to print from other machines I will 
try stripping out cups and starting again.


Thanks for all your time

Graham

Florian Kulzer wrote:

On Mon, Apr 30, 2007 at 00:56:24 +0100, graham wrote:

Florian Kulzer wrote:


[...]


Compare a directory listing before and after you plug in the printer if
necessary. You can use something like
find /dev/ | sort > before.txt
< plug in the printer >
find /dev/ | sort > after.txt
diff -u before.txt after.txt

snoopy> diff -u before.txt after.txt


[ snip: I only kept the new device nodes below ]


+/dev/bus/usb/001/110
+/dev/.udev/db/[EMAIL PROTECTED]@usbdev1.110
+/dev/.udev/db/[EMAIL PROTECTED]@lp0
+/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL PROTECTED]@[EMAIL 
PROTECTED]:[EMAIL PROTECTED]/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL 
PROTECTED]:00:[EMAIL PROTECTED]@[EMAIL PROTECTED]:[EMAIL 
PROTECTED]/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
PROTECTED]@[EMAIL PROTECTED]
+/dev/usb
+/dev/usbdev1.110_ep00
+/dev/usbdev1.110_ep03
+/dev/usbdev1.110_ep82
+/dev/usb/lp0


[...]


snoopy>ls -al /dev/usb/lp0
crw-rw 1 root lp 180, 0 2007-04-30 00:34 /dev/usb/lp0


That all looks fine to me. For real bout of paranoia you can quickly
check if you are still a member of the "lp" group.


snoopy> udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0)


[...]


  looking at device '/class/usb/lp0':
KERNEL=="lp0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{dev}=="180:0"

  looking at parent device 
'/devices/pci:00/:00:03.0/usb1/1-1/1-1:1.0':

KERNELS=="1-1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usblp"
ATTRS{modalias}=="usb:v04F9p0016d0100dc00dsc00dp00ic07isc01ip02"
ATTRS{bInterfaceProtocol}=="02"
ATTRS{bInterfaceSubClass}=="01"
ATTRS{bInterfaceClass}=="07"
ATTRS{bNumEndpoints}=="02"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
ATTRS{ieee1284_id}=="MFG:Brother_CMD:PJL,PCL,PCLXL_MDL:HL-5040 
series_CLS:PRINTER_"


  looking at parent device '/devices/pci:00/:00:03.0/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{serial}=="L3J497500"
ATTRS{product}=="HL-5040"
ATTRS{manufacturer}=="Brother"
ATTRS{maxchild}=="0"
ATTRS{version}==" 1.10"
ATTRS{devnum}=="125"
ATTRS{speed}=="12"
ATTRS{bMaxPacketSize0}=="16"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="00"
ATTRS{bcdDevice}=="0100"
ATTRS{idProduct}=="0016"
ATTRS{idVendor}=="04f9"
ATTRS{bMaxPower}=="100mA"
ATTRS{bmAttributes}=="c0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"


[...]

I think we can now safely assume that udev works properly and that the
problem is with CUPS. (It is good to have these tests now in the archive
for other people to find.)

[...]


You could also try to find a serial number like this:
udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0)  | grep -i serial

ATTRS{serial}=="L3J497500"
ATTRS{serial}==":00:03.0"

I have tried setting:

DeviceURI usb://dev/usb/lp0?serial=L3J497500

and

DeviceURI usb://dev/usb/lp0?serial=:00:03.0

with no results.


Just for the sake of completeness I would also try:

DeviceURI usb://Brother/HL-5040%20series?serial=L3J497500

and

DeviceURI usb://Brother/HL-5040?serial=L3J497500

(":00:03.0" is the serial number of the OHCI Host Controller and
 should not be relevant for CUPS.)


Another thing that might be important is how you handled the cupsys
configuration files during the upgrade. Did you keep your old ones or
did you replace them with the maintainer's new versions?
I kept the original version of cupsd.conf, the only file the installer 
asked about.
When it didn't work I tried using the new cupsd.conf.dpkg-dist, with no 
more success


Just to be sure: Did you restart cupsys after making the change?


Also:

After I changed DeviceURI to /dev/usb/lp0, the cups admin panel immediately 
showed 'new printer found'. I added this new printer, then looked at the 
rewritten printers.conf. The line it had added was the same as the original 
version:


DeviceURI usb://Brother/HL-5040%20series

The name cups auto-assigned to the new printer is 
Brother_HL-5040_series_USB_1


However, this 'newly discovered' printer also displays 'printer not 
connected' when attempting to print to it.


Thanks for your extreme patience!


I am afraid that I am slowly running out of ideas how to tackle this. I use Sid
and I remember at least two CUPS upgrades in the last 1.5 years which required
me to reinstall the printers (new PPD-files) and to overwrite the configuration
files. My feeling is therefore that there is a pr

Re: usb/cups printer problem after etch upgrade

[Florian Kulzer]

On Mon, Apr 30, 2007 at 00:56:24 +0100, graham wrote:
> Florian Kulzer wrote:

[...]

>> Compare a directory listing before and after you plug in the printer if
>> necessary. You can use something like
>> find /dev/ | sort > before.txt
>> < plug in the printer >
>> find /dev/ | sort > after.txt
>> diff -u before.txt after.txt
>
> snoopy> diff -u before.txt after.txt

[ snip: I only kept the new device nodes below ]

> +/dev/bus/usb/001/110
> +/dev/.udev/db/[EMAIL PROTECTED]@usbdev1.110
> +/dev/.udev/db/[EMAIL PROTECTED]@lp0
> +/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
> PROTECTED]@[EMAIL PROTECTED]:[EMAIL PROTECTED]/dev/.udev/db/[EMAIL 
> PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL PROTECTED]@[EMAIL PROTECTED]:[EMAIL 
> PROTECTED]/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
> PROTECTED]@[EMAIL PROTECTED]
> +/dev/usb
> +/dev/usbdev1.110_ep00
> +/dev/usbdev1.110_ep03
> +/dev/usbdev1.110_ep82
> +/dev/usb/lp0

[...]

> snoopy>ls -al /dev/usb/lp0
> crw-rw 1 root lp 180, 0 2007-04-30 00:34 /dev/usb/lp0

That all looks fine to me. For real bout of paranoia you can quickly
check if you are still a member of the "lp" group.

> snoopy> udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0)

[...]

>   looking at device '/class/usb/lp0':
> KERNEL=="lp0"
> SUBSYSTEM=="usb"
> DRIVER==""
> ATTR{dev}=="180:0"
>
>   looking at parent device 
> '/devices/pci:00/:00:03.0/usb1/1-1/1-1:1.0':
> KERNELS=="1-1:1.0"
> SUBSYSTEMS=="usb"
> DRIVERS=="usblp"
> ATTRS{modalias}=="usb:v04F9p0016d0100dc00dsc00dp00ic07isc01ip02"
> ATTRS{bInterfaceProtocol}=="02"
> ATTRS{bInterfaceSubClass}=="01"
> ATTRS{bInterfaceClass}=="07"
> ATTRS{bNumEndpoints}=="02"
> ATTRS{bAlternateSetting}==" 0"
> ATTRS{bInterfaceNumber}=="00"
> ATTRS{ieee1284_id}=="MFG:Brother_CMD:PJL,PCL,PCLXL_MDL:HL-5040 
> series_CLS:PRINTER_"
>
>   looking at parent device '/devices/pci:00/:00:03.0/usb1/1-1':
> KERNELS=="1-1"
> SUBSYSTEMS=="usb"
> DRIVERS=="usb"
> ATTRS{configuration}==""
> ATTRS{serial}=="L3J497500"
> ATTRS{product}=="HL-5040"
> ATTRS{manufacturer}=="Brother"
> ATTRS{maxchild}=="0"
> ATTRS{version}==" 1.10"
> ATTRS{devnum}=="125"
> ATTRS{speed}=="12"
> ATTRS{bMaxPacketSize0}=="16"
> ATTRS{bNumConfigurations}=="1"
> ATTRS{bDeviceProtocol}=="00"
> ATTRS{bDeviceSubClass}=="00"
> ATTRS{bDeviceClass}=="00"
> ATTRS{bcdDevice}=="0100"
> ATTRS{idProduct}=="0016"
> ATTRS{idVendor}=="04f9"
> ATTRS{bMaxPower}=="100mA"
> ATTRS{bmAttributes}=="c0"
> ATTRS{bConfigurationValue}=="1"
> ATTRS{bNumInterfaces}==" 1"

[...]

I think we can now safely assume that udev works properly and that the
problem is with CUPS. (It is good to have these tests now in the archive
for other people to find.)

[...]

>> You could also try to find a serial number like this:
>> udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0)  | grep -i serial
>
> ATTRS{serial}=="L3J497500"
> ATTRS{serial}==":00:03.0"
>
> I have tried setting:
>
> DeviceURI usb://dev/usb/lp0?serial=L3J497500
>
> and
>
> DeviceURI usb://dev/usb/lp0?serial=:00:03.0
>
> with no results.

Just for the sake of completeness I would also try:

DeviceURI usb://Brother/HL-5040%20series?serial=L3J497500

and

DeviceURI usb://Brother/HL-5040?serial=L3J497500

(":00:03.0" is the serial number of the OHCI Host Controller and
 should not be relevant for CUPS.)

>> Another thing that might be important is how you handled the cupsys
>> configuration files during the upgrade. Did you keep your old ones or
>> did you replace them with the maintainer's new versions?
>
> I kept the original version of cupsd.conf, the only file the installer 
> asked about.
> When it didn't work I tried using the new cupsd.conf.dpkg-dist, with no 
> more success

Just to be sure: Did you restart cupsys after making the change?

> Also:
>
> After I changed DeviceURI to /dev/usb/lp0, the cups admin panel immediately 
> showed 'new printer found'. I added this new printer, then looked at the 
> rewritten printers.conf. The line it had added was the same as the original 
> version:
>   
> DeviceURI usb://Brother/HL-5040%20series
>
> The name cups auto-assigned to the new printer is 
> Brother_HL-5040_series_USB_1
>
> However, this 'newly discovered' printer also displays 'printer not 
> connected' when attempting to print to it.
>
> Thanks for your extreme patience!

I am afraid that I am slowly running out of ideas how to tackle this. I use Sid
and I remember at least two CUPS upgrades in the last 1.5 years which required
me to reinstall the printers (new PPD-files) and to overwrite the configuration
files. My feeling is therefore that there is a problem somewhere in the
configuration files of your CUPS. I am starting to lean towards the brute-force
approach:

1) Back up /etc/cups/ (for our old friend Mr Justin Case).

2) Purge CUPS from your system:
   
   

Re: usb/cups printer problem after etch upgrade

[graham]

Florian Kulzer wrote:

On Sun, Apr 29, 2007 at 20:32:59 +0100, graham wrote:

Florian Kulzer wrote:


find /dev/ -name usblp0 -exec ls -l {} \;

   ^
I'd still like to see the output of the above command just to be sure.

Oops, sorry thought I'd checked this but I hadn't.
/dev/usblp0 does not exist. There is a /dev/usb/lp0, however. Here are all 
the usb devices:


snoopy> find /dev/ -name "usb*" -exec ls -l {} \;


[...]


crw-rw 1 root lp180,   0 2005-02-26 06:43 lp0
crw-rw 1 root lp180,   1 2005-02-26 06:43 lp1


[ snip: and so on ]

I think these are all from /dev/.static/dev/. You have to find out which
device node is created for the printer in /dev/ outside of .static.


There is both a /dev/.static/dev/usb/lp0 and a /dev/usb/lp0 (see below - 
the non-static one is created when I plug in the printer)



Compare a directory listing before and after you plug in the printer if
necessary. You can use something like

find /dev/ | sort > before.txt

< plug in the printer >

find /dev/ | sort > after.txt

diff -u before.txt after.txt


snoopy> diff -u before.txt after.txt
--- before.txt  2007-04-30 00:16:28.0 +0100
+++ after.txt   2007-04-30 00:14:39.0 +0100
@@ -6,6 +6,7 @@
 /dev/bus/usb
 /dev/bus/usb/001
 /dev/bus/usb/001/001
+/dev/bus/usb/001/110
 /dev/bus/usb/002
 /dev/bus/usb/002/001
 /dev/bus/usb/003
@@ -5774,9 +5775,11 @@
 /dev/.udev/db/[EMAIL PROTECTED]@ttyS2
 /dev/.udev/db/[EMAIL PROTECTED]@ttyS3
 /dev/.udev/db/[EMAIL PROTECTED]@usbdev1.1
+/dev/.udev/db/[EMAIL PROTECTED]@usbdev1.110
 /dev/.udev/db/[EMAIL PROTECTED]@usbdev2.1
 /dev/.udev/db/[EMAIL PROTECTED]@usbdev3.1
 /dev/.udev/db/[EMAIL PROTECTED]@usbdev3.2
+/dev/.udev/db/[EMAIL PROTECTED]@lp0
 /dev/.udev/db/[EMAIL PROTECTED]@vcs
 /dev/.udev/db/[EMAIL PROTECTED]@vcs1
 /dev/.udev/db/[EMAIL PROTECTED]@vcs2
@@ -5792,6 +5795,9 @@
 /dev/.udev/db/[EMAIL PROTECTED]@vcsa5
 /dev/.udev/db/[EMAIL PROTECTED]@vcsa6
 /dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
PROTECTED]@1-0:[EMAIL PROTECTED]
+/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL PROTECTED]@[EMAIL 
PROTECTED]:[EMAIL PROTECTED]/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL 
PROTECTED]:00:[EMAIL PROTECTED]@[EMAIL PROTECTED]:[EMAIL 
PROTECTED]/dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
PROTECTED]@[EMAIL PROTECTED]
 /dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
PROTECTED]@usbdev1.1_ep00
 /dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
PROTECTED]@2-0:[EMAIL PROTECTED]
 /dev/.udev/db/[EMAIL PROTECTED]:[EMAIL PROTECTED]:00:[EMAIL 
PROTECTED]@usbdev2.1_ep00
@@ -5809,6 +5815,10 @@
 /dev/.udev/failed/[EMAIL PROTECTED]@00:05
 /dev/.udev/uevent_seqnum
 /dev/urandom
+/dev/usb
+/dev/usbdev1.110_ep00
+/dev/usbdev1.110_ep03
+/dev/usbdev1.110_ep82
 /dev/usbdev1.1_ep00
 /dev/usbdev1.1_ep81
 /dev/usbdev2.1_ep00
@@ -5818,6 +5828,7 @@
 /dev/usbdev3.2_ep00
 /dev/usbdev3.2_ep02
 /dev/usbdev3.2_ep81
+/dev/usb/lp0
 /dev/vcs
 /dev/vcs1
 /dev/vcs2




I need to see the properties of the newly-created device node (and only
of this one). Make sure it is really /dev/usb/lp0.


snoopy>ls -al /dev/usb/lp0
crw-rw 1 root lp 180, 0 2007-04-30 00:34 /dev/usb/lp0

snoopy> udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0)

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/class/usb/lp0':
KERNEL=="lp0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{dev}=="180:0"

  looking at parent device 
'/devices/pci:00/:00:03.0/usb1/1-1/1-1:1.0':

KERNELS=="1-1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usblp"
ATTRS{modalias}=="usb:v04F9p0016d0100dc00dsc00dp00ic07isc01ip02"
ATTRS{bInterfaceProtocol}=="02"
ATTRS{bInterfaceSubClass}=="01"
ATTRS{bInterfaceClass}=="07"
ATTRS{bNumEndpoints}=="02"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
ATTRS{ieee1284_id}=="MFG:Brother_CMD:PJL,PCL,PCLXL_MDL:HL-5040 
series_CLS:PRINTER_"


  looking at parent device '/devices/pci:00/:00:03.0/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{serial}=="L3J497500"
ATTRS{product}=="HL-5040"
ATTRS{manufacturer}=="Brother"
ATTRS{maxchild}=="0"
ATTRS{version}==" 1.10"
ATTRS{devnum}=="125"
ATTRS{speed}=="12"
ATTRS{bMaxPacketSize0}=="16"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="00"
ATTRS{bcdDevice}=="0100"
ATTRS{idProduct}=="0016"
ATTRS{idVendor}=="04f9"
ATTRS{bMaxPower}=="100mA"
ATTRS{bmAttributes}=="c0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"

  looking at parent device '/dev

Re: usb/cups printer problem after etch upgrade

[Florian Kulzer]

On Sun, Apr 29, 2007 at 20:32:59 +0100, graham wrote:
> Florian Kulzer wrote:
>
 find /dev/ -name usblp0 -exec ls -l {} \;
>>^
>> I'd still like to see the output of the above command just to be sure.
>
> Oops, sorry thought I'd checked this but I hadn't.
> /dev/usblp0 does not exist. There is a /dev/usb/lp0, however. Here are all 
> the usb devices:
>
> snoopy> find /dev/ -name "usb*" -exec ls -l {} \;

[...]

> crw-rw 1 root lp180,   0 2005-02-26 06:43 lp0
> crw-rw 1 root lp180,   1 2005-02-26 06:43 lp1

[ snip: and so on ]

I think these are all from /dev/.static/dev/. You have to find out which
device node is created for the printer in /dev/ outside of .static.
Compare a directory listing before and after you plug in the printer if
necessary. You can use something like

find /dev/ | sort > before.txt

< plug in the printer >

find /dev/ | sort > after.txt

diff -u before.txt after.txt

I need to see the properties of the newly-created device node (and only
of this one). Make sure it is really /dev/usb/lp0.

[...]

> snoopy>/usr/lib/cups/backend/usb
> direct usb://Brother/HL-5040%20series "Brother HL-5040 series" "Brother 
> HL-5040 series USB #1" "MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-5040 
> series;CLS:PRINTER;"
 So far, so good. Now let's see how the printer is defined for CUPS. Post
 the output of
 grep DeviceURI /etc/cups/printers.conf
>>> DeviceURI usb://Brother/HL-5040%20series
>>>
>>> Looks identical to the /dev name to me.
>> Most USB DeviceURIs that I find on the web have "?serial=..." appended
>> after the  string. Maybe the problem is that in your case no
>> serial number is found by the USB backend of CUPS. (I am speculating
>> here; I never used CUPS with a USB printer.)
>
> Now he tells me ;-)
> Seems a little unlikely though as this setup all worked fine with sarge
>
>> You could try:
>> DeviceURI usb:/dev/...
>> or
>> DeviceURI USB #1
>
> I've tried
> DeviceURI usb:/dev/lp0
>
> which didn't change anything

What about "usb:/dev/usb/lp0"?

You could also try to find a serial number like this:

udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0)  | grep -i serial

Another thing that might be important is how you handled the cupsys
configuration files during the upgrade. Did you keep your old ones or
did you replace them with the maintainer's new versions?

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[graham]

Florian Kulzer wrote:


find /dev/ -name usblp0 -exec ls -l {} \;

   ^
I'd still like to see the output of the above command just to be sure.



Oops, sorry thought I'd checked this but I hadn't.
/dev/usblp0 does not exist. There is a /dev/usb/lp0, however. Here are 
all the usb devices:


snoopy> find /dev/ -name "usb*" -exec ls -l {} \;
crw-rw 1 root root 442, 4097 2007-04-29 15:23 /dev/usbdev3.2_ep81
crw-rw 1 root root 442, 4097 2007-04-29 15:23 /dev/usbdev3.2_ep02
crw-rw 1 root root 442, 4097 2007-04-29 15:23 /dev/usbdev3.2_ep00
total 0
crw-rw 1 root audio 180,  66 2005-02-26 06:43 cpad0
crw-rw 1 root root  180,  32 2005-02-26 06:43 ez0
crw-rw 1 root root  180,  33 2005-02-26 06:43 ez1
crw-rw 1 root root  180,  42 2005-02-26 06:43 ez10
crw-rw 1 root root  180,  43 2005-02-26 06:43 ez11
crw-rw 1 root root  180,  44 2005-02-26 06:43 ez12
crw-rw 1 root root  180,  45 2005-02-26 06:43 ez13
crw-rw 1 root root  180,  46 2005-02-26 06:43 ez14
crw-rw 1 root root  180,  47 2005-02-26 06:43 ez15
crw-rw 1 root root  180,  34 2005-02-26 06:43 ez2
crw-rw 1 root root  180,  35 2005-02-26 06:43 ez3
crw-rw 1 root root  180,  36 2005-02-26 06:43 ez4
crw-rw 1 root root  180,  37 2005-02-26 06:43 ez5
crw-rw 1 root root  180,  38 2005-02-26 06:43 ez6
crw-rw 1 root root  180,  39 2005-02-26 06:43 ez7
crw-rw 1 root root  180,  40 2005-02-26 06:43 ez8
crw-rw 1 root root  180,  41 2005-02-26 06:43 ez9
crw-rw 1 root root  180,  96 2005-02-26 06:43 hiddev0
crw-rw 1 root root  180,  97 2005-02-26 06:43 hiddev1
crw-rw 1 root root  180, 106 2005-02-26 06:43 hiddev10
crw-rw 1 root root  180, 107 2005-02-26 06:43 hiddev11
crw-rw 1 root root  180, 108 2005-02-26 06:43 hiddev12
crw-rw 1 root root  180, 109 2005-02-26 06:43 hiddev13
crw-rw 1 root root  180, 110 2005-02-26 06:43 hiddev14
crw-rw 1 root root  180, 111 2005-02-26 06:43 hiddev15
crw-rw 1 root root  180,  98 2005-02-26 06:43 hiddev2
crw-rw 1 root root  180,  99 2005-02-26 06:43 hiddev3
crw-rw 1 root root  180, 100 2005-02-26 06:43 hiddev4
crw-rw 1 root root  180, 101 2005-02-26 06:43 hiddev5
crw-rw 1 root root  180, 102 2005-02-26 06:43 hiddev6
crw-rw 1 root root  180, 103 2005-02-26 06:43 hiddev7
crw-rw 1 root root  180, 104 2005-02-26 06:43 hiddev8
crw-rw 1 root root  180, 105 2005-02-26 06:43 hiddev9
crw-rw 1 root lp180,   0 2005-02-26 06:43 lp0
crw-rw 1 root lp180,   1 2005-02-26 06:43 lp1
crw-rw 1 root lp180,  10 2005-02-26 06:43 lp10
crw-rw 1 root lp180,  11 2005-02-26 06:43 lp11
crw-rw 1 root lp180,  12 2005-02-26 06:43 lp12
crw-rw 1 root lp180,  13 2005-02-26 06:43 lp13
crw-rw 1 root lp180,  14 2005-02-26 06:43 lp14
crw-rw 1 root lp180,  15 2005-02-26 06:43 lp15
crw-rw 1 root lp180,   2 2005-02-26 06:43 lp2
crw-rw 1 root lp180,   3 2005-02-26 06:43 lp3
crw-rw 1 root lp180,   4 2005-02-26 06:43 lp4
crw-rw 1 root lp180,   5 2005-02-26 06:43 lp5
crw-rw 1 root lp180,   6 2005-02-26 06:43 lp6
crw-rw 1 root lp180,   7 2005-02-26 06:43 lp7
crw-rw 1 root lp180,   8 2005-02-26 06:43 lp8
crw-rw 1 root lp180,   9 2005-02-26 06:43 lp9
crw-rw 1 root root  180,  16 2005-02-26 06:43 mouse0
crw-rw 1 root root  180,  17 2005-02-26 06:43 mouse1
crw-rw 1 root root  180,  26 2005-02-26 06:43 mouse10
crw-rw 1 root root  180,  27 2005-02-26 06:43 mouse11
crw-rw 1 root root  180,  28 2005-02-26 06:43 mouse12
crw-rw 1 root root  180,  29 2005-02-26 06:43 mouse13
crw-rw 1 root root  180,  30 2005-02-26 06:43 mouse14
crw-rw 1 root root  180,  31 2005-02-26 06:43 mouse15
crw-rw 1 root root  180,  18 2005-02-26 06:43 mouse2
crw-rw 1 root root  180,  19 2005-02-26 06:43 mouse3
crw-rw 1 root root  180,  20 2005-02-26 06:43 mouse4
crw-rw 1 root root  180,  21 2005-02-26 06:43 mouse5
crw-rw 1 root root  180,  22 2005-02-26 06:43 mouse6
crw-rw 1 root root  180,  23 2005-02-26 06:43 mouse7
crw-rw 1 root root  180,  24 2005-02-26 06:43 mouse8
crw-rw 1 root root  180,  25 2005-02-26 06:43 mouse9
crw-rw 1 root audio 180,  64 2005-02-26 06:43 rio500
crw-rw-rw- 1 root root  180,  48 2005-02-26 06:43 scanner0
crw-rw-rw- 1 root root  180,  49 2005-02-26 06:43 scanner1
crw-rw-rw- 1 root root  180,  58 2005-02-26 06:43 scanner10
crw-rw-rw- 1 root root  180,  59 2005-02-26 06:43 scanner11
crw-rw-rw- 1 root root  180,  60 2005-02-26 06:43 scanner12
crw-rw-rw- 1 root root  180,  61 2005-02-26 06:43 scanner13
crw-rw-rw- 1 root root  180,  62 2005-02-26 06:43 scanner14
crw-rw-rw- 1 root root  180,  63 2005-02-26 06:43 scanner15
crw-rw-rw- 1 root root  180,  50 2005-02-26 06:43 scanner2
crw-rw-rw- 1 root root  180,  51 2005-02-26 06:43 scanner3
crw-rw-rw- 1 root root  180,  52 2005-02-26 06:43 scanner4
crw-rw-rw- 1 root root  180,  53 2005-

Re: usb/cups printer problem after etch upgrade

[Florian Kulzer]

On Sun, Apr 29, 2007 at 14:31:24 +0100, graham wrote:
> Florian Kulzer wrote:
>> On Sat, Apr 28, 2007 at 23:08:39 +0100, graham wrote:
>
>> Just to be sure: Run
>> apt-get --purge remove hotplug
>> (Plain "remove" leaves configuration files on the system; "--purge" gets
>>  rid of them.)
>
> OK, done.
>
> Following which I power cycled the printer and rebooted the server. No 
> change.
>
>> find /dev/ -name usblp0 -exec ls -l {} \;
   ^
I'd still like to see the output of the above command just to be sure.

>> [...]
>>> snoopy>/usr/lib/cups/backend/usb
>>> direct usb://Brother/HL-5040%20series "Brother HL-5040 series" "Brother 
>>> HL-5040 series USB #1" "MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-5040 
>>> series;CLS:PRINTER;"
>> So far, so good. Now let's see how the printer is defined for CUPS. Post
>> the output of
>> grep DeviceURI /etc/cups/printers.conf
>
> DeviceURI usb://Brother/HL-5040%20series
>
> Looks identical to the /dev name to me.

Most USB DeviceURIs that I find on the web have "?serial=..." appended
after the  string. Maybe the problem is that in your case no
serial number is found by the USB backend of CUPS. (I am speculating
here; I never used CUPS with a USB printer.)

You could try:

DeviceURI usb:/dev/...

or

DeviceURI USB #1

instead. (Replace "..." with the exact path to the device node. Run
"invoke-rc.d cupsys restart" or "/etc/init.d/cupsys restart" after
editing printers.conf.)

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[graham]

Florian Kulzer wrote:

On Sat, Apr 28, 2007 at 23:08:39 +0100, graham wrote:




Just to be sure: Run

apt-get --purge remove hotplug

(Plain "remove" leaves configuration files on the system; "--purge" gets
 rid of them.)



OK, done.

Following which I power cycled the printer and rebooted the server. No 
change.




find /dev/ -name usblp0 -exec ls -l {} \;

[...]


snoopy>/usr/lib/cups/backend/usb
direct usb://Brother/HL-5040%20series "Brother HL-5040 series" "Brother 
HL-5040 series USB #1" "MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-5040 
series;CLS:PRINTER;"


So far, so good. Now let's see how the printer is defined for CUPS. Post
the output of

grep DeviceURI /etc/cups/printers.conf


DeviceURI usb://Brother/HL-5040%20series

Looks identical to the /dev name to me.

Graham



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[Florian Kulzer]

On Sat, Apr 28, 2007 at 23:08:39 +0100, graham wrote:
> Hi Florian,
>
> Thanks for the response! Answers inline below: basically everything seems 
> to be right - but cups still thinks the printer is paused...
>
> Florian Kulzer wrote:
>> On Thu, Apr 26, 2007 at 15:18:52 +0100, graham wrote:
>>> Hi,
>>>
>>> I have a server running cups, with a wireless usb connector connected to 
>>> a remote Brother 5040 laser printer. It's always worked fine, modulo a 
>>> little crackle on the television when printing ;-)
>>>
>>> After upgrading the server to etch (without any major problems) cups no 
>>> longer sees the printer. Cups is running ok, and knows about the printer, 
>>> but the web interface always displays the message:
>>>
>>> " HL5040 (Default Printer) "Printer not connected; will retry in 30 
>>> seconds..."

[...]

>>> I guess this is yet another strangeness with changes to udev?
>> That is possible, but it could also be due to the changes between CUPS
>> 1.1 and 1.2. AFAIK, some ways of specifying the DeviceURI have become
>> obsolete for the new version.
>
> Seems likely, though I haven't spotted the new way in the docs. There's 
> another etch user on the cups mailing list with a similar-sounding problem 
> (but no answers).
>
>> The obligatory checklist for the udev transition is:
>> Did you purge hotplug?
>
> apt-get remove hotplug
> Reading package lists... Done
> Building dependency tree... Done
> Package hotplug is not installed, so not removed

Just to be sure: Run

apt-get --purge remove hotplug

(Plain "remove" leaves configuration files on the system; "--purge" gets
 rid of them.)

[ snip: kernel 2.6.18-4-486 is OK ]

>> tail -fn0 /var/log/syslog | sed 's/.*kernel: //'
>
> ohci_hcd :00:03.0: wakeup
> usb 1-1: new full speed USB device using ohci_hcd and address 83
> usb 1-1: configuration #1 chosen from 1 choice
> drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 83 if 0 
> alt 0 proto 2 vid 0x04F9 pid 0x0016

Looks like udev is working, but maybe we should check the properties of
the created device node. What is the output of

find /dev/ -name usblp0 -exec ls -l {} \;

[...]

> snoopy>/usr/lib/cups/backend/usb
> direct usb://Brother/HL-5040%20series "Brother HL-5040 series" "Brother 
> HL-5040 series USB #1" "MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-5040 
> series;CLS:PRINTER;"

So far, so good. Now let's see how the printer is defined for CUPS. Post
the output of

grep DeviceURI /etc/cups/printers.conf

Printers.conf can contain passwords in clear text, therefore it is only
readable by root. Make sure to remove confidential information before
posting here. (This is probably not the case for your USB printer, but
better safe than sorry.)

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[graham]

Hi Florian,

Thanks for the response! Answers inline below: basically everything 
seems to be right - but cups still thinks the printer is paused...


Florian Kulzer wrote:

On Thu, Apr 26, 2007 at 15:18:52 +0100, graham wrote:

Hi,

I have a server running cups, with a wireless usb connector connected to a 
remote Brother 5040 laser printer. It's always worked fine, modulo a little 
crackle on the television when printing ;-)


After upgrading the server to etch (without any major problems) cups no 
longer sees the printer. Cups is running ok, and knows about the printer, 
but the web interface always displays the message:


" HL5040 (Default Printer) "Printer not connected; will retry in 30 
seconds..."


lsusb shows that the printer is there, and visible over wireless:

snoopy: lsusb
Bus 003 Device 002: ID 13fd:0540
Bus 003 Device 001: ID :
Bus 002 Device 001: ID :
Bus 001 Device 028: ID 04f9:0016 Brother Industries, Ltd
Bus 001 Device 001: ID :

lsmod shows I have the usb modules:

snoopy: lsmod

ehci_hcd   27144  0
ohci_hcd   17540  0
sis900 21120  0
mii 5376  1 sis900
usbcore   109444  5 usblp,usb_storage,ehci_hcd,ohci_hcd


I guess this is yet another strangeness with changes to udev?


That is possible, but it could also be due to the changes between CUPS
1.1 and 1.2. AFAIK, some ways of specifying the DeviceURI have become
obsolete for the new version.


Seems likely, though I haven't spotted the new way in the docs. There's 
another etch user on the cups mailing list with a similar-sounding 
problem (but no answers).




The obligatory checklist for the udev transition is:
Did you purge hotplug?


apt-get remove hotplug
Reading package lists... Done
Building dependency tree... Done
Package hotplug is not installed, so not removed


Did you upgrade to the 2.6.18 kernel?


uname -r
2.6.18-4-486



You can run

tail -fn0 /var/log/syslog | sed 's/.*kernel: //'


ohci_hcd :00:03.0: wakeup
usb 1-1: new full speed USB device using ohci_hcd and address 83
usb 1-1: configuration #1 chosen from 1 choice
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 83 if 0 
alt 0 proto 2 vid 0x04F9 pid 0x0016





and check if udev creates a device node when the printer is switched on
or when you plug in the usb connector. (Press CTRL+C to return to the
shell prompt.)


Has anyone else run into the same problem, or found a solution?


Post the output that you get when you run

/usr/lib/cups/backend/usb


snoopy>/usr/lib/cups/backend/usb
direct usb://Brother/HL-5040%20series "Brother HL-5040 series" "Brother 
HL-5040 series USB #1" "MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-5040 
series;CLS:PRINTER;"


Thanks again
Graham


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: usb/cups printer problem after etch upgrade

[Florian Kulzer]

On Thu, Apr 26, 2007 at 15:18:52 +0100, graham wrote:
> Hi,
>
> I have a server running cups, with a wireless usb connector connected to a 
> remote Brother 5040 laser printer. It's always worked fine, modulo a little 
> crackle on the television when printing ;-)
>
> After upgrading the server to etch (without any major problems) cups no 
> longer sees the printer. Cups is running ok, and knows about the printer, 
> but the web interface always displays the message:
>
> " HL5040 (Default Printer) "Printer not connected; will retry in 30 
> seconds..."
>
> lsusb shows that the printer is there, and visible over wireless:
>
> snoopy: lsusb
> Bus 003 Device 002: ID 13fd:0540
> Bus 003 Device 001: ID :
> Bus 002 Device 001: ID :
> Bus 001 Device 028: ID 04f9:0016 Brother Industries, Ltd
> Bus 001 Device 001: ID :
>
> lsmod shows I have the usb modules:
>
> snoopy: lsmod
> 
> ehci_hcd   27144  0
> ohci_hcd   17540  0
> sis900 21120  0
> mii 5376  1 sis900
> usbcore   109444  5 usblp,usb_storage,ehci_hcd,ohci_hcd
>
>
> I guess this is yet another strangeness with changes to udev?

That is possible, but it could also be due to the changes between CUPS
1.1 and 1.2. AFAIK, some ways of specifying the DeviceURI have become
obsolete for the new version.

The obligatory checklist for the udev transition is:
Did you purge hotplug?
Did you upgrade to the 2.6.18 kernel?

You can run

tail -fn0 /var/log/syslog | sed 's/.*kernel: //'

and check if udev creates a device node when the printer is switched on
or when you plug in the usb connector. (Press CTRL+C to return to the
shell prompt.)

> Has anyone else run into the same problem, or found a solution?

Post the output that you get when you run

/usr/lib/cups/backend/usb

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

usb/cups printer problem after etch upgrade

[graham]

Hi,

I have a server running cups, with a wireless usb connector connected to 
a remote Brother 5040 laser printer. It's always worked fine, modulo a 
little crackle on the television when printing ;-)


After upgrading the server to etch (without any major problems) cups no 
longer sees the printer. Cups is running ok, and knows about the 
printer, but the web interface always displays the message:


" HL5040 (Default Printer) "Printer not connected; will retry in 30 
seconds..."


lsusb shows that the printer is there, and visible over wireless:

snoopy: lsusb
Bus 003 Device 002: ID 13fd:0540
Bus 003 Device 001: ID :
Bus 002 Device 001: ID :
Bus 001 Device 028: ID 04f9:0016 Brother Industries, Ltd
Bus 001 Device 001: ID :

lsmod shows I have the usb modules:

snoopy: lsmod

ehci_hcd   27144  0
ohci_hcd   17540  0
sis900 21120  0
mii 5376  1 sis900
usbcore   109444  5 usblp,usb_storage,ehci_hcd,ohci_hcd


I guess this is yet another strangeness with changes to udev? Has anyone 
else run into the same problem, or found a solution?


Thanks
Graham


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Strange Printer Problem

[CoolFox]

Leonid Grinberg a magnifiquement tapoté sur son clavier avec ses gros 
doigts boudinés:

Hello,

This happened two weeks ago, and I ccan't seem to figure out why:

I was trying to print a document from my printer, and it printed fine.
Everything worked perfectly, and the paper came out great. Next, I
opened another document that needed printing, but this time it
wouldn't print! When I went to the Gnome printer administration tool,
I saw that the printer was paused with the job still in the list.
Trying to print some more, kept making jobs appear. At the moment,
there are 16 jobs in the list!

The printer is an HP Deskjet 6540. It is connected via USB to my
Debian machine, kernel 2.6.

The status message shown is:

Paused: Unable to open USB device "usb://6540?serial=": No such device

Does anybody have any ideas?

--
Leonid Grinberg
[EMAIL PROTECTED]


try lsusb to check if your device is accepted by the system

--
La vie c'est comme un concombre...
des fois tu l'as dans la main...
des fois tu l'as dans l'cul !

Paul Presbois (Poète avant-gardiste)



signature.asc
Description: OpenPGP digital signature

Strange Printer Problem

[Leonid Grinberg]

Hello,

This happened two weeks ago, and I ccan't seem to figure out why:

I was trying to print a document from my printer, and it printed fine.
Everything worked perfectly, and the paper came out great. Next, I
opened another document that needed printing, but this time it
wouldn't print! When I went to the Gnome printer administration tool,
I saw that the printer was paused with the job still in the list.
Trying to print some more, kept making jobs appear. At the moment,
there are 16 jobs in the list!

The printer is an HP Deskjet 6540. It is connected via USB to my
Debian machine, kernel 2.6.

The status message shown is:

Paused: Unable to open USB device "usb://6540?serial=": No such device

Does anybody have any ideas?

--
Leonid Grinberg
[EMAIL PROTECTED]

Re: HP Deskjet 6840 Printer Problem

[Stephen Allen]

Michael Kerwin wrote:
> I am trying to get an HP Deskjet 6840 inkjet Printer to work with my
> Debian 3.1 Sarge stable system.
> 
> I am trying to get it to work with lpr

Use CUPS instead, and check out this article;



It supposedly works fine with CUPS.

-- 
(On going to war over religion:) "You're basically killing each other
to see who's got the better imaginary friend."   -- Rich Jeni
__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

HP Deskjet 6840 Printer Problem

[Michael Kerwin]

I am trying to get an HP Deskjet 6840 inkjet Printer to work with my 
Debian 3.1 Sarge stable system.


I am trying to get it to work with lpr

The name of the printer I am calling is the same name as its host name 
which is hp7efdfb, its local address is 200.0.0.117 I have it using port 
9100 which is the same port as my HP Laserjet which does work.


The printcap file is

laser4v:\
   :sd=/var/spool/lpd/lp/laserjet:\
   :mx#0:\
   :sh:\
   :af=/var/spool/lpd/lp/laserjet/acct:\
   :lf=/var/spool/lpd/lp/laserjet/log:\
   :if=/usr/local/bin/filter.pcl:\
   :rm=200.0.0.7:\
   :rp=:

hp7efdfb:\
   :sd=/var/spool/lpd/lp/dj6840:\
   :mx#0:\
   :sh:\
   :af=/var/spool/lpd/lp/dj6840/acct:\
   :lf=/var/spool/lpd/lp/dj6840/log:\
   :af=/usr/local/bin/HP-Deskjet_6840-hpijs.ppd\
   :if=/usr/bin/foomatic-rip:\
   :rm=200.0.0.117:\
   :rp=:


In /var/spool/lpd/lp/dj6840 the status file says


If I do  the following command
lpadmin -p hp7efdfb -E -v socket://200.0.0.117:9100 -P 
/usr/local/bin/HP-Deskjet_6840-hpijs.ppd


debian says
lpadmin: add-printer (set model) failed: client-error-not-found


My lpstat -t says

scheduler is running
system default destination: laser4v
device for hp7efdfb: socket://200.0.0.117
device for laser4v: socket://200.0.0.7:9100

hp7efdfb accepting requests since Jan 01 00:00
laser4v accepting requests since Jan 01 00:00
printer hp7efdfb is idle.  enabled since Jan 01 00:00
printer laser4v is idle.  enabled since Jan 01 00:00


When I try to print is doesn't print anything and I can see the files 
build up in the queue for the printer.


Windows will print to the printer using the HP Driver that came with it 
but it doesn't have a linux driver on the disc.


Does anyone have any idea on how I can get this printer to work or what 
I am doing wrong? I would appreciate any help you can give me.


Michael Kerwin
~


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Diagnosing a printer problem

[Kevin Mark]

On Mon, May 30, 2005 at 12:06:58PM -0700, David E. Fox wrote:
> 
> I'm on a modified Mepis system, and my apt.preferences are sitting now
> at "experimental", probably a bad idea, but I did that so I could get
> kde 3.4 installed. I just didn't set it back, and the other day I ran
> an apt-get update && apt-get upgrade, and it upgraded a couple hundred
> packages in the pocess.
> 
> In the process, printing no longer works. Jobs get spooled, gs starts
Hi David,
Experimental is not a distrabution or release. If your other 
packages are mostly testing or unstable, that is what apt and its ilk will
try to use as a referense. If you do not 'hold' the experimental
packages, apt and its ilk will try to 'fix' all those packages by
upgrading them to the 'distribution' you are using (testing, unstable).
This can lead to mixed results as you have found. Experimental packages
are put in a special place for testing cutting edge ideas they may break
other things. If the idea works out, it will most likley be move into
unstable. There it will not break things.
cheers,
kev
-- 
counter.li.org #238656 -- goto counter.li.org and be counted!
  `$' $' 
   $  $  _
 ,d$$$g$  ,d$$$b. $,d$$$b`$' g$b $,d$$b
,$P'  `$ ,$P' `Y$ $$'  `$ $  "'   `$ $$' `$
$$ $ $$g$ $ $ $ ,$P""  $ $$
`$g. ,$$ `$$._ _. $ _,g$P $ `$b. ,$$ $$
 `Y$$P'$. `YP $$$P"' ,$. `Y$$P'$ $.  ,$.


signature.asc
Description: Digital signature

Diagnosing a printer problem

[David E. Fox]

I'm on a modified Mepis system, and my apt.preferences are sitting now
at "experimental", probably a bad idea, but I did that so I could get
kde 3.4 installed. I just didn't set it back, and the other day I ran
an apt-get update && apt-get upgrade, and it upgraded a couple hundred
packages in the pocess.

In the process, printing no longer works. Jobs get spooled, gs starts
up, but nothing comes out of the printer.  I have to remove the print
job and kill the stuck gs process. In diagnosing the problem, I find
that "strace -p ' is writing a large amount of zero
bytes through a broken pipe. That implies there's nothing on the other
end, or whatever is supposed to be on the other end is not responding.
I noticed also that while previously there used to be some processes
"parralel" and "cat" that get started, but these are not there now.  I
then attempted to backport to the "unstable" cups but that does not
help.

I'm a bit confused and not sure whether I got all the bits and pieces
of the stuff that's relevant to printing at the right versions (or ones
that work).


-- 

David E. Fox  Thanks for letting me
[EMAIL PROTECTED]change magnetic patterns
[EMAIL PROTECTED]   on your hard disk.
---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

CUPS usb printer problem

[Tom Allison]

I run into this maybe once a month.
(installation details are at the bottom)
my kyocera laser printer (usb) cuts out and won't respond.
Restarting cups takes a very long time and the CUPS web pages don't show 
any problems with the cups system.

The only messages in my syslog are:
Dec  7 05:19:55 localhost last message repeated 2 times
Dec  7 05:20:00 localhost kernel: usb 1-1: control timeout on ep0in
Dec  7 05:20:26 localhost last message repeated 5 times
Dec  7 05:20:31 localhost kernel: usb 1-2: control timeout on ep0in
Dec  7 05:20:56 localhost last message repeated 5 times
Dec  7 05:21:01 localhost kernel: usb 1-1: control timeout on ep0in
Dec  7 05:21:27 localhost last message repeated 5 times
Dec  7 05:21:32 localhost kernel: usb 1-2: control timeout on ep0in
Dec  7 05:21:57 localhost last message repeated 5 times
Dec  7 05:22:03 localhost kernel: usb 1-1: control timeout on ep0in
Dec  7 05:22:28 localhost last message repeated 5 times
Dec  7 05:22:33 localhost kernel: usb 1-2: control timeout on ep0in
Dec  7 05:22:59 localhost last message repeated 5 times
Dec  7 05:23:04 localhost kernel: usb 1-1: control timeout on ep0in
Dec  7 05:23:29 localhost last message repeated 5 times
Dec  7 05:23:34 localhost kernel: usb 1-2: control timeout on ep0in
Dec  7 05:24:00 localhost last message repeated 5 times
Power cycling the printer doesn't seem to help much...
Dec  7 05:25:25 localhost kernel: usb 1-2: control timeout on ep0in
Dec  7 05:26:27 localhost last message repeated 6 times
Dec  7 05:27:07 localhost last message repeated 4 times
Dec  7 05:27:15 localhost kernel: usb 1-2: USB disconnect, address 3
Dec  7 05:27:16 localhost kernel: drivers/usb/class/usblp.c: usblp1: removed
Dec  7 05:27:28 localhost kernel: usb 1-2: new full speed USB device 
using address 4
Dec  7 05:27:33 localhost kernel: usb 1-2: control timeout on ep0out
Dec  7 05:27:38 localhost kernel: usb 1-2: control timeout on ep0out
Dec  7 05:27:38 localhost kernel: usb 1-2: device not accepting address 
4, error -110
Dec  7 05:27:38 localhost kernel: usb 1-2: new full speed USB device 
using address 5
Dec  7 05:27:43 localhost kernel: usb 1-2: control timeout on ep0out

So I'll try rebooting the entire cups print server.
Not the solution I had hoped for.
But rebooting the system works.
At this point I'll make the accusation that there is more of a problem 
with USB devices than with CUPS.  But I never can tell with these things.

Any suggestions would be appreciated.
clang:~# uname -a
Linux clang 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux
clang:~# dpkg -l | grep cups
ii  cupsys 1.1.20final+rc Common UNIX Printing System(tm) - server
ii  cupsys-bsd 1.1.20final+rc Common UNIX Printing System(tm) - BSD 
comman
ii  cupsys-client  1.1.20final+rc Common UNIX Printing System(tm) - 
client pro
ii  cupsys-driver- 4.2.7-4Gimp-Print printer drivers for CUPS
ii  cupsys-driver- 4.2.7-4Gimp-Print printer drivers for CUPS
ii  libcupsimage2  1.1.20final+rc Common UNIX Printing System(tm) - 
image libs
rc  libcupsys2 1.1.20final+cv Common UNIX Printing System(tm) - libs
ii  libcupsys2-gnu 1.1.20final+rc Common UNIX Printing System(tm) - libs

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: parport printer problem under kernel 2.6 with asus mainboard

[Promocao NetBotanic]

Try to load the modules:
 
ppdev and lp, my lsmod is following:
 
Module  
Size  Used 
byppdev   
8544  
0lp 
11852  
0parport_pc 
38880  
1parport    
41672  3 
ppdev,lp,parport_pcautofs4    
16320  
0e100   
31744  
0mii 
5120  1 
e100microcode   
7392  0
 
Pedro Alves
Moebius Tecnologia em Informatica 
Ltda

Re: Openoffice printer problem - A Bug?

[Thomas H. George]

On Tue, Nov 23, 2004 at 10:43:45PM -0500, Adam Aube wrote:
> Thomas H. George wrote:
> 
> > Since the local printer is installed and is working correctly I hesitate
> > to delete and reinstall it.  It would seem best to remove the printer
> > from Openoffice and reinstall it there but I don't see how to do this.
> 
> Have you looked under OpenOffice.org Printer Administration
> (/usr/bin/oopadmin)?
> 
> Adam
> 
I ran oopadmin and successfully printed a test page.  Further
experimenting showed that Openoffice could print earlier documents on
the local printer but not any newly created documents!

If an earlier document is printed it shows up on the CUPS completed job
list.  If a newly created document is sent to the printer nothing
happens, it is as if it were sent to /dev/null, it is never reported by
CUPS on either the print que or the completed jobs list.

I have also lost the ability to print the newly created document on
another printer connected to a different system on the LAN.  Yesterday
this worked.  Today anything sent to the other printer is lost.

Tom George
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Openoffice printer problem

[Adam Aube]

Thomas H. George wrote:

> Since the local printer is installed and is working correctly I hesitate
> to delete and reinstall it.  It would seem best to remove the printer
> from Openoffice and reinstall it there but I don't see how to do this.

Have you looked under OpenOffice.org Printer Administration
(/usr/bin/oopadmin)?

Adam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Openoffice printer problem

[Thomas H. George]

Until the most recent dist-upgrade Openoffice had no trouble printing 
with the local printer, an HP 940C installed with Cups.  The printer 
installation is correct.  Lynx localhost:631 shows in as the default 
printer, available and accepting jobs.  The test page prints perfectly 
and a simple text file can be printed from the console with the lp 
command.  When the attempt is made to print a document from Openoffice 
it appears to work but nothing is printed, nothing appears in the print 
que and nothing appears in the jobs completed list.

Openoffice knows that there is a second printer on the LAN and can print 
the document to this printer with no difficulty.

Since the local printer is installed and is working correctly I hesitate 
to delete and reinstall it.  It would seem best to remove the printer 
from Openoffice and reinstall it there but I don't see how to do this.

I would appreciate any suggestions,
Tom George
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

USB printer problem

[David Hugh-Jones]

Hi

I have a problem using my printer. It's a canon S100. I am using CUPS
and Debian Sarge (same problem with kernels 2.6.7, 2.6.8 and 2.4.27).
When I try and print a test page (from the admin interface at
localhost:631) I get either the message "Printer fault" or the message
"USB port busy; will retry in 30 seconds..."

Can anyone help me with this? It was working originally, but then I
did a dist-upgrade.

My printer device: /dev/usb/lp0. 

Thanks a lot,

Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: parport printer problem under kernel 2.6 with asus mainboard

[Christian Riedel]

Hi Hendrik,
On 30.07.2004 15:04, Hendrik Fuß wrote:
are there known problems with parport on asus mainboards or is it just
my fault? /dev/lp0 behaves like /dev/null, everything I print just
disappears, no error or log messages. Even echo "hello world" > /dev/lp0
doesn't do anything.
Under 2.4 kernels everything works as expected.
I had similar problems, when I switched to 2.6 ... although the modules 
are loaded printing does not work.

As a workaround - that worked for me:
- unload lp and parport_pc manually and reload them
Then printing worked ...
It seems taht 2.6 has problems with correctly recognizing the parport. 
If you look at your boot messages you will probably see, that neither 
ecp or epp is detected, but that your parport is set to polling or 
something similar although the bios setting say other.

When I manually loaded the modules ECP was detected as it should be and 
printing worked.

HTH
Christian
--
To reply to this posting directly use the following address and
remove the 'NO-SPAM' part: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

parport printer problem under kernel 2.6 with asus mainboard

[Hendrik Fuß]

Hi,

are there known problems with parport on asus mainboards or is it just
my fault? /dev/lp0 behaves like /dev/null, everything I print just
disappears, no error or log messages. Even echo "hello world" > /dev/lp0
doesn't do anything.

Under 2.4 kernels everything works as expected.


mainboard: asus a7v133
distribution: unstable (sid)
kernel: kernel-image 2.6.5-1-k7


$ lsmod | grep lp 

> lp 11268  0
> parport41672  2 parport_pc,lp



-- 
Hendrik Fuß <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New Cups printer problem

[Thomas H. George]

On Sat, Mar 01, 2003 at 03:15:55PM -0600, Donald Spoon wrote:
> Thomas H. George,,, wrote:
> >Printer is an HP DeckJet 940C
> >Driver is Foomatic-hpijs downloaded from www.linuxprinting.org
> >
> >A print test from localhost:631 or from kde prints nothing.
> >
> >cat printtest.txt > /dev/lp0 prints the simple text file though it must 
> >be manually ejected.
> >
> >less /var/log/cups/error_log ends in multiple lines of 
> >"get-printer-attrs: resource name '/printers/Mail PDF' no good!"
> >
> >Background:  System is Woody with 2.4.18 kernel.
> >dpkg -l |grep cups and dpkg -l |grep foomatic show  the following 
> >packages installed (ii):
> >
> >   cupsomatic-ppd
> >   cupsys
> >   cupsys-bsd
> >   cupsys-client
> >   cupsys-pstoraster
> >   kdelibs3-cups
> >   libcupsys2
> >   libcupsys2-dev
> >   foomatic-bin
> >   foomatic-db
> >
> >As usual, I seem to have overlooked something, but what?
> >
> >Tom George
> >
> >
> 
> Stupid question I know, but do you have the "hpijs" package installed? 
> I think it is required with that PPD...  You also need GS, but that will 
> automatically be pulled in if you have the hpijs file installed.
> 
> -Don Spoon-
> 
Details, details, details.  It is always the details that kill you.  I
must have once know that the hpijs package is required as the printer
was working before a hard drive crash made it necessary to re-install
everything.  At any rate, I installed it and the printer is working
perfectly.  Thank you,

Tom George
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact 
> [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New Cups printer problem

[Donald Spoon]

Thomas H. George,,, wrote:
Printer is an HP DeckJet 940C
Driver is Foomatic-hpijs downloaded from www.linuxprinting.org
A print test from localhost:631 or from kde prints nothing.

cat printtest.txt > /dev/lp0 prints the simple text file though it must 
be manually ejected.

less /var/log/cups/error_log ends in multiple lines of 
"get-printer-attrs: resource name '/printers/Mail PDF' no good!"

Background:  System is Woody with 2.4.18 kernel.
dpkg -l |grep cups and dpkg -l |grep foomatic show  the following 
packages installed (ii):

   cupsomatic-ppd
   cupsys
   cupsys-bsd
   cupsys-client
   cupsys-pstoraster
   kdelibs3-cups
   libcupsys2
   libcupsys2-dev
   foomatic-bin
   foomatic-db
As usual, I seem to have overlooked something, but what?

Tom George


Stupid question I know, but do you have the "hpijs" package installed? 
I think it is required with that PPD...  You also need GS, but that will 
automatically be pulled in if you have the hpijs file installed.

-Don Spoon-

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

New Cups printer problem

[Thomas H. George,,,]

Printer is an HP DeckJet 940C
Driver is Foomatic-hpijs downloaded from www.linuxprinting.org
A print test from localhost:631 or from kde prints nothing.

cat printtest.txt > /dev/lp0 prints the simple text file though it must 
be manually ejected.

less /var/log/cups/error_log ends in multiple lines of 
"get-printer-attrs: resource name '/printers/Mail PDF' no good!"

Background:  System is Woody with 2.4.18 kernel.
dpkg -l |grep cups and dpkg -l |grep foomatic show  the following 
packages installed (ii):

   cupsomatic-ppd
   cupsys
   cupsys-bsd
   cupsys-client
   cupsys-pstoraster
   kdelibs3-cups
   libcupsys2
   libcupsys2-dev
   foomatic-bin
   foomatic-db
As usual, I seem to have overlooked something, but what?

Tom George

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Printer Problem - An Insane Solution

[Gary Turner]

Glenn English wrote:

>On Mon, 2003-02-10 at 10:03, Thomas H. George,,, wrote:
>
>> PS.  I was going to call this a cock-a-manie (sp?) solution but I can't 
>> find the word in any of our dictionaries.  Anyone know a correct 
>> spelling and dictionary entry?
>
>Not at all sure, but I think it's "cockamamie" - it's a term my
>grandparents used to use, so I suspect it came out of the 1920's.
>It ought to be in the Dictionary of American Slang.

FYI

gt@koko:~$ dict cockamamie
1 definition found

>From WordNet (r) 1.7 [wn]:

  cockamamie
   adj : (informal terms) "gave me a cockamamie reason for not
 going"; "wore a goofy hat"; "a silly idea"; "some wacky
 plan for selling more books" [syn: {cockamamy}, {fool(a)},
  {goofy}, {sappy}, {silly}, {wacky}, {zany},
{unreasonable}]
gt@koko:~$



--
gt  [EMAIL PROTECTED]
 If someone tells you---
 "I have a sense of humor, but that's not funny." 
  ---they don't.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Printer Problem - An Insane Solution

[Glenn English]

On Mon, 2003-02-10 at 10:03, Thomas H. George,,, wrote:

> PS.  I was going to call this a cock-a-manie (sp?) solution but I can't 
> find the word in any of our dictionaries.  Anyone know a correct 
> spelling and dictionary entry?

Not at all sure, but I think it's "cockamamie" - it's a term my
grandparents used to use, so I suspect it came out of the 1920's.
It ought to be in the Dictionary of American Slang.

-- 
Glenn English
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Printer Problem - An Insane Solution

[Thomas H. George,,,]

Problem: Epson Stylus Color 860 on usb to work with kde using cupsys and 
kdelibs3-cups and also to work from a terminal.  If web intstallation is 
used (localhost:631) and the recommended driver from linuxprinting 
(Stylus_Color_860-gimp-print-cups.ppd) the printer works beautifully 
from kde BUT - the printer does NOT WORK from a termial.

Solution:  Install the printer under a differnet name from the terminal 
- e.g.

   lpadmin -p ep -E -v usb:/dev/usblp0 -m 
Stylus_Color_860-gimp-print-cups.ppd

then run escputil -i -u -r /dev/usblp0  and lpadmin -d ep

Result:  Checked with the web installer, the new printer appears a Local 
Raw Printer.  It will print from a terminal command - e.g. lp printtest 
whre printtest is a simply ASCII file and, since I have defined it as 
the default printer, it will print from mutt.

The other printer definition created from the Web interface continues to 
exist and can be used to print documents from kde.

This will not be a happy solution if I ever succeed in getting this 
computer connected to our in-house wireless network but so far I have 
had little success with that.

PS.  I was going to call this a cock-a-manie (sp?) solution but I can't 
find the word in any of our dictionaries.  Anyone know a correct 
spelling and dictionary entry?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: USB Printer Problem - Partial Fix

[Thomas H. George]

On Fri, Jan 24, 2003 at 10:53:56AM -0500, Stephen Gran wrote:
> You'll want to use the gimp-print drivers for cups - they work very
> nicely with Epson printers.

Yes and No.  Installed gimp and gimpprint-doc.  Followed instructions
and printer worked perfectly printing a picture.

Installed cupsys-driver-gimpprint.  Test prints print the color hexagon
but no text. Where are the fonts?  apt-cache search gimp|grep font
doesn't find any.
> 
> -- 
>  --
> |  Stephen Gran  | Love is never asking why?   |
> |  [EMAIL PROTECTED] | |
> |  http://www.lobefin.net/~steve | |
>  --



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: USB Printer Problem

[Stephen Gran]

This one time, at band camp, Thomas H. George,,, said:
> I have an Epson Stylus Color 860 attached to a USB port.  I am using 
> CUPS and  cupsomatic-ppd.  localhost:631/printers shows Foomatic + 
> stp-4.0 and usb:/dev/usblp0.  When I try Print Test Page nothing is 
> printed and the /var/log/cups/error_log lists
> 
>GNU Ghostscript 7.05: Unrecoverable error, exit code 1
> 
> There are some earlier complaints that plain paper is not a valid 
> parameter of type media type and 360 is not a valid parameter of type 
> resolution.
> 
> The system is Debian Testing with kernel 2.4.20
> 
> This printer previously worked perfectly with CUPS installed from the CD 
> accompanying Michael Sweet's book.  I installed the debian cupsys and 
> cupsomatic packages as I want to use it with kde.  I downloaded the 860 
> drivers from linuxprinting.org.

You'll want to use the gimp-print drivers for cups - they work very
nicely with Epson printers.

-- 
 --
|  Stephen Gran  | Love is never asking why?   |
|  [EMAIL PROTECTED] | |
|  http://www.lobefin.net/~steve | |
 --



msg25956/pgp0.pgp
Description: PGP signature

USB Printer Problem

[Thomas H. George,,,]

I have an Epson Stylus Color 860 attached to a USB port.  I am using 
CUPS and  cupsomatic-ppd.  localhost:631/printers shows Foomatic + 
stp-4.0 and usb:/dev/usblp0.  When I try Print Test Page nothing is 
printed and the /var/log/cups/error_log lists

   GNU Ghostscript 7.05: Unrecoverable error, exit code 1

There are some earlier complaints that plain paper is not a valid 
parameter of type media type and 360 is not a valid parameter of type 
resolution.

The system is Debian Testing with kernel 2.4.20

This printer previously worked perfectly with CUPS installed from the CD 
accompanying Michael Sweet's book.  I installed the debian cupsys and 
cupsomatic packages as I want to use it with kde.  I downloaded the 860 
drivers from linuxprinting.org.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Printer problem

[root]

I can print with pr  |lpr. I have downloaded the browsers, 
Netscape 6 and Opera 5, as well as Star Office. On none of these can I 
print using the printer button. It seems unlikely that all are flawed so 
I must assume that something is wrong with my configuration. If somebody 
knows how to get my programs to print, I can replace Windows 98 with 
Debian as my primary operating system. Thank you.

re: printer problem

[Thomas H. George]

I have discovered that apsfilterconfig writes three filters for my 
Brother HL-730 laser printer (which can simulate an HP LJIIP).  In the 
printcap file it generates I find


  ascii|jet2p-letter-ascii-mono|jet2p

  lp|jet2p-letter-auto-mono|jet2p

  raw|jet2p-letter-raw|jet2p

The command lpr -Praw testtest  will print a simple text file written 
with vi.


In Abiword the print instruction with lpr -Plp will print test but not 
dingbats but the font is wrong - font 12 prints as font 30.


I have not discovered a use for the ascii filter.

I pass this along for whatever its worth

Re: printer problem

[Steve Gran]

On Wed, 23 May 2001, Wayne Topa wrote:

> 
> 
> Subject: printer problem
> Date: Tue, May 22, 2001 at 07:23:54PM -0500
> 
> In reply to:Thomas H. George
> 
> Quoting Thomas H. George([EMAIL PROTECTED]):
> > Trying to make printer (brother HL-730 on parallel port) work from 
> > debian linux 2.2.19:
> > 
> > lp testtxt
> > 
> > and from Abiword in ximian gnome desk top.  Compiled the kernel with 
> > parallel printer support and autoprobe.
> > 
> 
> Look at the past months mail archive for discussion on this.
> 
> I have a Brother HL-10V worling fine using magicfilter.  Could only
> get a great test page out of apsfilter. :(
> 
> Works for every program I have tried.
> 
> One other thought.  Have you compiled the kernel correctly?  A lot of
> parport options there.  Also have you included the parport options in
> the appends= in lilo.conf?  ie:
> append  = "lp=parport0 parport=0x378,none"
> 
> ( 'none' means don't ise an IRQ, which isn't required for the printer)

I think  you want to try lpr foo.txt instead of lp foo.txt - it may just be 
that it doesn't recognize the command you're trying to give it.  If you can cat 
text to the printer, don't mess with you're base settings (IRQ, DMA, etc.) 
because the information is getting to the right port.  It's something either in 
what you're telling it (i.e., wrong command) or in the configuration (i.e., 
/etc/printcap is misconfigured).  Try man printcap for a description of what 
you should be seeing in the file, and compare irt to what you actually see.
Good luck,
Steve

Re: printer problem

[Wayne Topa]

Subject: printer problem
Date: Tue, May 22, 2001 at 07:23:54PM -0500

In reply to:Thomas H. George

Quoting Thomas H. George([EMAIL PROTECTED]):
> Trying to make printer (brother HL-730 on parallel port) work from 
> debian linux 2.2.19:
> 
> lp testtxt
> 
> and from Abiword in ximian gnome desk top.  Compiled the kernel with 
> parallel printer support and autoprobe.
> 

Look at the past months mail archive for discussion on this.

I have a Brother HL-10V worling fine using magicfilter.  Could only
get a great test page out of apsfilter. :(

Works for every program I have tried.

One other thought.  Have you compiled the kernel correctly?  A lot of
parport options there.  Also have you included the parport options in
the appends= in lilo.conf?  ie:
append  = "lp=parport0 parport=0x378,none"

( 'none' means don't ise an IRQ, which isn't required for the printer)

:-) HTH, YMMV, HAND :-)

-- 
There can never be a computer language in which you cannot write a
bad program.
___

printer problem

[Thomas H. George]

Trying to make printer (brother HL-730 on parallel port) work from 
debian linux 2.2.19:


lp testtxt

and from Abiword in ximian gnome desk top.  Compiled the kernel with 
parallel printer support and autoprobe.


cat testtxt > /dev/lp0

works.  On advice from ximian gnome chat group ran

apt-get install apsfilter

which replaced magicfilter and ran apsfilterconfig.  Printed marvelous 
test page but


lp testtxt

still does not work.  lpq reports nothing printable in que and aborts job.

Abiword does nothing, probably because the font path is incorrect - I 
haven't found out how to fix this yet.  I do have gs and gsfonts installed.


Any suggestions as to what to try next?

usb printer problem

[Thomas H. George]

I successfully built a 2.2.19 kernel with usb support.  cat 
/proc/bus/usb/drivers shows drivers loaded, cat /proc/bus/usb/devices 
shows only pci.  I have


none/proc/bus/usbusbdevfsdefaults00

in fstab.  After booting up dmesg reports

  parport_probe: failed
  parport0: no IEEE-1284 device present

and then later in the listing

  lp0: using parport0 (polling)

Therefore when I try to print lpq reports lp0: no such device.

I could rebuild the kernel with no parport support (only a Visioneer One 
Touch 7600 scanner is attached to the parallel port and I don't believe 
there is any way to use this with linux) but sometime I might have 
something usable on the parallel port and still want to use the usb printer.


Is there something I have omitted which prevents lp0 from being assigned 
to the usb port?

Re: Printer Problem Solved..sorta..

[Dale Morris]

Doing some investigation, I find the problem lies more with StarOffice 5.2
than it does with my printer configuration. I changed lpd to lprng and have
configured it. ABI word prints fine, I can print from mutt, netscape, lyx,
etc.. but nothing happens with StarOffice, the printer just keeps spitting
out blank pages. On an email thread, I saw there were some changes that had
to be made to the printcap file having to do with *levels*? but I've decided
to remove StarOffice. It's so slow loading that I never use it anyhow. 





> The problem is when I try to print from StarOffice. The printer starts but
> nothing is printed to the page. Anyone else have this problem or know the
> solution? I'm using apsfilter, lpd, and an epson stylus color 600 printer.

Printer Problem

[Dale Morris]

Having just done another debian 2.2 reinstall, I'm having some printer
problems. I have installed the apsfilter package and it works fine printing
from netscape and printing text files, etc.. 
The problem is when I try to print from StarOffice. The printer starts but
nothing is printed to the page. Anyone else have this problem or know the
solution? I'm using apsfilter, lpd, and an epson stylus color 600 printer.

thanks

printer problem, sending problem

[Stephan Kulka]

My printer is only printing numbers, always the same. I did a strace lpr
file and I don't understand the messages, but I think that there is a
problem with printing.
My other problem is that I am writing this mail from my computer at the
university and I don't manage to transfer the file with the strace output
from my local computer to this computer. I did put foo, but I got the
message that foo doesn't exist (but I am sure about that). Is there a
possibility to use ssh for this file transfer??

TIA

Stephan

Re: Printer Problem

[kmself]

on Sun, Mar 18, 2001 at 07:59:35PM +0100, Stephan Kulka ([EMAIL PROTECTED]) 
wrote:
> When I try to print out a file , I get the following message:
> 
> >[EMAIL PROTECTED] - cannot open connection Connection refused
> >Make sure LPD server is running on the system.
> 
> I am quite confused, because the lpd daemon is started at startup (I even
> rebooted to be sure).
> What is this LPD?? My network is working, I never changed the
> configuration files for the network,so the local network should be ok as
> well.

Have you configured a printer?  I'm not particularly handy at this, but
tend to stumple through printtool, a graphical utility, with some
success.

-- 
Karsten M. Self http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?   There is no K5 cabal
  http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org


pgpT6pTwgZbVO.pgp
Description: PGP signature

Printer Problem

[Stephan Kulka]

When I try to print out a file , I get the following message:

>[EMAIL PROTECTED] - cannot open connection Connection refused
>Make sure LPD server is running on the system.

I am quite confused, because the lpd daemon is started at startup (I even
rebooted to be sure).
What is this LPD?? My network is working, I never changed the
configuration files for the network,so the local network should be ok as
well.

Any help appreciated

Stephan

Re: Printer Problem

[ktb]

On Fri, Feb 02, 2001 at 03:03:31PM -0500, Thomas H. George,,,610-444-2626 wrote:
> I was surprised!  After running dmesg I found my printer working again.  
> I don't understand why this is so but, as I had done nothing else (I 
> send these messages from another computer), dmseg must have corrected 
> the problem.
> 
> Thanks again for the help.
> 

H, dmesg just shows the output of boot.  I'm glad it is working now
though:)
kent

-- 
I'd really love ta wana help ya Flanders but... Homer Simpson

Re: Printer Problem

[Thomas H. George,,,610-444-2626]

I was surprised!  After running dmesg I found my printer working again.  
I don't understand why this is so but, as I had done nothing else (I 
send these messages from another computer), dmseg must have corrected 
the problem.


Thanks again for the help.

Tom George

Thomas H. George,,,610-444-2626 wrote:

Thanks for the suggestion.  I had not learned about dmesg.  
Unfortunately it reported everything in order - i.e. parport0 using 
0378 and irq 7.  I must look elsewhere for the problem.


Tom George

ktb wrote:


On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:

My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


   cat lptest > /dev/lp0  where lptest is a small text file

and

   lp lptest

responds normally but nothing is printed and nothing is in the print que.

   cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


   cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is !

directed to lp0.

Where is the missing link?



What does dmesg say about parport?
kent

Re: Printer Problem

[Thomas H. George,,,610-444-2626]

Thanks for the suggestion; I had not yet learned about dmesg.  
Unfortunately, dmesg reported all in order with parport - i.e. using 
0378 and irq 7.  I must look elsewhere for my problem.


Tom George

ktb wrote:


On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:

My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


   cat lptest > /dev/lp0  where lptest is a small text file

and

   lp lptest

responds normally but nothing is printed and nothing is in the print que.

   cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


   cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is directed to lp0.


Where is the missing link?



What does dmesg say about parport?
kent

Re: Printer Problem

[Thomas H. George,,,610-444-2626]

Thanks for the suggestion.  I had not learned about
dmesg.  Unfortunately it reported everything in order - i.e. parport0 using
0378 and irq 7.  I must look elsewhere for the problem.

Tom George

ktb wrote:
On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:
  My printer was working perfectly.  I rebuilt the kernel allowing autoprobe.  Printer no longer responds even to   cat lptest > /dev/lp0  where lptest is a small text fileand   lp lptestresponds normally but nothing is printed and nothing is in the print que.   cat /proc/ioports  shows the correct value (0378-037f) for parport0   cat /proc/parport/0/irq  reports none (should be irq 7 but is this needed?)Documentation/parport indicates that a lilo command parport=0x378,7 should work but /sbin/lilo rejects this line placed anywhere in lilo.conf.  The documentation also implies that the irq value reported by cat/proc/parport/0/irq can be changed but I don't understand how.It seems to me that everything is working normally but the printer is not receiving the transmission.  The printcap file is unaltered and lp is !
directed to lp0.Where is the missing link?
What does dmesg say about parport?kent

Re: Printer Problem

[ktb]

On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:
> My printer was working perfectly.  I rebuilt the kernel allowing 
> autoprobe.  Printer no longer responds even to
> 
>cat lptest > /dev/lp0  where lptest is a small text file
> 
> and
> 
>lp lptest
> 
> responds normally but nothing is printed and nothing is in the print que.
> 
>cat /proc/ioports  shows the correct value (0378-037f) for 
> parport0
> 
>cat /proc/parport/0/irq  reports none (should be irq 7 but is 
> this needed?)
> 
> Documentation/parport indicates that a lilo command parport=0x378,7 
> should work but /sbin/lilo rejects this line placed anywhere in 
> lilo.conf.  The documentation also implies that the irq value reported 
> by cat/proc/parport/0/irq can be changed but I don't understand how.
> 
> It seems to me that everything is working normally but the printer is 
> not receiving the transmission.  The printcap file is unaltered and lp 
> is directed to lp0.
> 
> Where is the missing link?
> 

What does dmesg say about parport?
kent

-- 
I'd really love ta wana help ya Flanders but... Homer Simpson

Printer Problem

[Thomas H. George,,,610-444-2626]

My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


  cat lptest > /dev/lp0  where lptest is a small text file

and

  lp lptest

responds normally but nothing is printed and nothing is in the print que.

  cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


  cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is directed to lp0.


Where is the missing link?

Tom George

Printer problem

[Micha Feigin]

I tried to set up my printer using apsfilter.
I have a hp 815 (I think that its a variation on the 810 with extra
language support)
I tried using the cdjcolor driver (It was the only one apropriate that was
found, aps filter tried to add a sufix to hpdj which made it not work, and
the driver for the 850,855 and 890 weren't there).
The test page printed out fine, but when I later tried to print to that
printer using lpr, the first call just hangs, it doesn't return from the
lpr call.
When I later try to run either lpr or lprm or lpq, either in paralel aor
after killing the lpr call with C-c I get a message that connection is
refused.
Any idea's?
Thanx
[EMAIL PROTECTED]

Re: Printer problem

[Alisdair McDiarmid]

On Thu, Nov 04, 1999 at 09:55:30AM +1030, John Pearson wrote:
> On Tue, Nov 02, 1999 at 10:57:59PM +, Alisdair McDiarmid wrote
> > 
> > i've got a printer set up on skinny, which prints locally fine.
> > the printcap on letdown is:
> > 
> > lp|hplj|HP Laserjet 1100:\
> > :lp=/dev/null:sd=/var/spool/lpd/hplj:rm=skinny.wasters:rp=lp:\
> > :sh:pw#80:pl#72:px#1440:mx#0:\
> > :if=/etc/magicfilter/ljet4l-filter:\
> > :af=/var/log/lp-acct:lf=/var/log/lp-errs:
> 
> My printcap, that works for remote printing, looks like this:
[snip]
> Maybe specifying 'lp=/dev/null' is getting your work thrown away before
> lpd notices you've specified a remote printer?

That appears to be the problem - it works perfectly now. Thanks,
John!

Re: Printer problem

[John Pearson]

On Wed, Nov 03, 1999 at 12:23:06AM +, Brian Schramm wrote
> I am sorry.  I did not give a good explanation for the problem.  I am 
> talking security.  I have the printer setup in the printcap file but 
> it is not working because it cannot connect to it.  The machine at the 
> other end says it cannot allow the connection.  I use to create a 
> hosts.lpd file and that would work but I know that this version has 
> some other file to edit.
> 
> Brian
> 

Slink includes two separate print spoolers - lpr and lprng - which use
different configuration files.  Which are you using?


John P. 
-- 
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark

Re: Printer problem

[John Pearson]

On Tue, Nov 02, 1999 at 10:57:59PM +, Alisdair McDiarmid wrote
> On Tue, Nov 02, 1999 at 06:43:00PM +0100, SGaerner wrote:
> > You have to edit your local /etc/printcap.
> > Add a line
> > rm=YOUR_SERVER_IP:\
> > rp=lp:\
> > 
> > But I think that you only have to uncomment und modify some lines in your 
> > standard
> > Debian /etc/printcap.
> 
> i'm currently having the same problem.
> 
> i've got a printer set up on skinny, which prints locally fine.
> the printcap is:
> 
> lp|hplj|HP Laserjet 1100:\
> :lp=/dev/lp0:sd=/var/spool/lpd/hplj:\
> :sh:pw#80:pl#72:px#1440:mx#0:\
> :if=/etc/magicfilter/ljet4l-filter:\
> :af=/var/log/lp-acct:lf=/var/log/lp-errs:
> 
> the printcap on letdown is:
> 
> lp|hplj|HP Laserjet 1100:\
>   :lp=/dev/null:sd=/var/spool/lpd/hplj:rm=skinny.wasters:rp=lp:\
>   :sh:pw#80:pl#72:px#1440:mx#0:\
>   :if=/etc/magicfilter/ljet4l-filter:\
>   :af=/var/log/lp-acct:lf=/var/log/lp-errs:
> 

My printcap, that works for remote printing, looks like this:

lp|huiac|lj|HP Laserjet 6MP:\
:lp=:\
:rm=huiac:\
:sd=/var/spool/lpd/lp:\
:af=/var/log/lp-acct:\
:lf=/var/log/lp-errs:\
:pl#70:\
:pw#80:\
:pc#150:\
:mx#0:\
:sh:

Maybe specifying 'lp=/dev/null' is getting your work thrown away before
lpd notices you've specified a remote printer?


John P.
-- 
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark

Re: Printer problem

[Brian Schramm]

I am sorry.  I did not give a good explanation for the problem.  I am 
talking security.  I have the printer setup in the printcap file but 
it is not working because it cannot connect to it.  The machine at the 
other end says it cannot allow the connection.  I use to create a 
hosts.lpd file and that would work but I know that this version has 
some other file to edit.

Brian

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 11/2/99, 10:07:03 AM, Ethan Benson <[EMAIL PROTECTED]> wrote 
regarding Re: Printer problem:


> On 2/11/99 Brian Schramm wrote:

> >I hope this gets to the list.  I never saw my question post the last
> >time.
> >
> >I am running Debian slink and I need to share my printers with my
> >networked Debian slink workstations.  I know that there is a file I
> >need to modify in order to give permission to each computer to do
> >this.  I just forgot which one and what to put in it.
> >
> >Can someone please help me on this?

> /etc/printcap  man printcap



> Best Regards,
> Ethan Benson
> To obtain my PGP key: http://www.alaska.net/~erbenson/pgp/

Re: Printer problem

[Alisdair McDiarmid]

On Tue, Nov 02, 1999 at 06:43:00PM +0100, SGaerner wrote:
> You have to edit your local /etc/printcap.
> Add a line
> rm=YOUR_SERVER_IP:\
> rp=lp:\
> 
> But I think that you only have to uncomment und modify some lines in your 
> standard
> Debian /etc/printcap.

i'm currently having the same problem.

i've got a printer set up on skinny, which prints locally fine.
the printcap is:

lp|hplj|HP Laserjet 1100:\
:lp=/dev/lp0:sd=/var/spool/lpd/hplj:\
:sh:pw#80:pl#72:px#1440:mx#0:\
:if=/etc/magicfilter/ljet4l-filter:\
:af=/var/log/lp-acct:lf=/var/log/lp-errs:

the printcap on letdown is:

lp|hplj|HP Laserjet 1100:\
:lp=/dev/null:sd=/var/spool/lpd/hplj:rm=skinny.wasters:rp=lp:\
:sh:pw#80:pl#72:px#1440:mx#0:\
:if=/etc/magicfilter/ljet4l-filter:\
:af=/var/log/lp-acct:lf=/var/log/lp-errs:

printing on letdown does nothing: lpq says "no printable jobs in
queue", but skinny doesn't appear to even get anything. there are
no logs or output from lpd on either machine to suggest that
anything happened. i think i've set up /etc/lpd.perms to allow
access, but i can't be sure (the only line is DEFAULT ACCEPT).

what could it possibly be? (i have RTFM and FAQ and HOWTO and they
don't help).

thanks,
-- 
alisdair mcdiarmid[EMAIL PROTECTED]
[everything that matters has gone http://wasters.org/]

Re: Printer problem

[SGaerner]

You have to edit your local /etc/printcap.
Add a line
rm=YOUR_SERVER_IP:\
rp=lp:\

But I think that you only have to uncomment und modify some lines in your 
standard
Debian /etc/printcap.


Brian Schramm wrote:

> I hope this gets to the list.  I never saw my question post the last
> time.
>
> I am running Debian slink and I need to share my printers with my
> networked Debian slink workstations.  I know that there is a file I
> need to modify in order to give permission to each computer to do
> this.  I just forgot which one and what to put in it.
>
> Can someone please help me on this?
>
> Thanks.
>
> Brian Schramm
> [EMAIL PROTECTED]
>
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Printer problem

[Brian Schramm]

I hope this gets to the list.  I never saw my question post the last 
time.

I am running Debian slink and I need to share my printers with my 
networked Debian slink workstations.  I know that there is a file I 
need to modify in order to give permission to each computer to do 
this.  I just forgot which one and what to put in it.

Can someone please help me on this?

Thanks.

Brian Schramm
[EMAIL PROTECTED]