[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#716843: cups: CUPS doesn't properly initialize Lexmark E238



On July 14, 2013, Brian Potkin wrote:

> Hello Mark,

>

> Thank you for your detailed report.

>

> On Sat 13 Jul 2013 at 11:38:00 -0300, Mark Small wrote:

> > After upgrading my print server to Wheezy, I've had a lot of problems

> > printing on my Lexmark E238 laser printer.

> >

> > When printing from a linux client, it will

> >

> > sometimes print just the top corner zoomed to fill the whole page. This

> > happens roughly half of the time, and only on the first page of a multi

> > page print job. Otherwise it prints properly. I'm using the pcl5

> > driver. (Generic PCL 5 Printer Foomatic/ljet3).

>

> My first thought here was - why isn't the recommended pxlmono driver

> being used? It may not be important in the light of what is said later.

>

 

Okay, so I've done some more troubleshooting. I've changed the CUPS driver to the recommended PXLMONO driver. I've also reset the printer to factory defaults. I'm still in the sometimes works category, except that its a little worse.

 

From Windows, usign the E238 (MS) driver, when it fails, it spits out pages and pages of garbage, starting with some comments.

 

From Linux, when it fails it now spits out pages of PCL source code starting with

 

PJL ENTER LANGUAGE = PCLXL

 

 

> > If I print from a Windows box using direct/raw access (with the

> >

> > Lexmark driver specifically for this printer), I get page after page of

> > gobbledegook (probably PCL6 source code.)

>

> The E238 has a PCL interpreter, so this shouldn't happen. Right?

>

 

That's my understanding.

 

>

> How is the server connected to the printer?

>

 

It's connected by USB.

 

 

 

>

> Is testing using unstable a possibility for you?

>

> Regards,

>

> Brian.

 

 

That would be tricky, as this is a mission critical box for my small business. It runs my internal email server, web server, NFS, Samba, and a bunch of other stuff that I don't want to mess up.

 

After some more web searching, I've found some Ubuntu bugs that are similar (1184597, 872483). Both seem to resolved by playing with a usb-no-reattach option within lpadman. I'll try that and report back.

 

--

 


Reply to: