Lexmark z53: lprng versus cups on server:Resolved

[Joel Hammer]

Well, I did it. Just to pass on some gotchas.

I went with lprng on the lindows server and had the following experiences:

1. Lindows warehouse supplied lprng no problem.

2. Lindows warehouse didn't supply the z53 drivers. 

3. I got the z53 drivers from the lexmark page. In rpm format. Since lindows
is debian, I was very afraid. I downloaded rpm from the warehouse and rpm -i
the printing package. rpm complained of a missing file, Packages. Turns
out the whole rpm directory was missing. So I made the directory and the
Packages file, and voila, rpm worked. So, it looks like some post install
script in the debian rpm package didn't function and make these
directories and files for me.

4. Once rpm worked, it gave me about 10 missing dependencies with the
printing software. I used --nodeps and things installed and worked,
at which point:

5. I ran the configuration program, lexmarkz53. It complained there was no
queue. Sure enuf, the lprng package hadn't made a printcap file, neither had
the printing package. This is why I stick with what I know. I made the
queues, ran checkpc -f, started lprng, and the thing printed the test
page.

6. I then had to create a 2nd queue to handle documents that have to be
reformatted. (I suppose I could have used the same queue as the test page
used but I didn't think of it at the time. Basically it is the raw queue
versus the filter queue thing, but you could fiddle with the filter to
pass through binary files.)

7. Then, just to be fancy, I made several queues with different
configuration files (from the lexmark configuration program) so I
could print to draft, high quality, photo, etc, just by choosing the
print queue.

Network issues. Here is where things got interesting.

8. My windows laptop printed without trouble.

9. My other lindows box set up the printer very nicely, no complaints, but the
print jobs just hung in the queue. 

I then tried to set up printing from my old caldera box, with a bunch
of bounce queues, and they just hung. 

I finally realized that my print server name, hammer10, was resolving to
the internet ip of my gateway box, which has no real printing services
on it, just a bunch of queues which were going nowhere (really pointing
to my old dead caldera box). Since my local name server went dead,
every local address resolves to the ip of my gateway box. This is because
they all use the comcast name server, which thinks all names ending in
hammershome.com are the same thing.

SO,  I had to reinstall a local DNS for my home network, which went very
smoothly on a lindows box, and had to fiddle with lpd.perms on the print
server for my old caldera box to access it via port 515, and voila,
all things printing work again.

This suggests that linux uses IP addresses to find other computers
but windows doesn't. I thought that windows (XP pro) had gone over to
ip's, too.

Now, just gotta get the scanner up and going and I think I am back to
where I was before the crash.

Joel


On Sun, Nov 23, 2003 at 08:19:47AM -0800, Ian Stephen wrote:
> On Sun, 2003-11-23 at 06:03, Joel Hammer wrote:
> 
> >      3. Has anyone set up a lexmark z53 with cups? I would
> >      appreciate hearing about your experience.
> 
> I went to a big-box store and bought the only printer in the place with
> a penquin on the box, a Z53, for use with Red Hat 8.
> 
> That was followed by several days tinkering and Googling before I took
> the cursed thing back and got an Epson C82.  I love my Epson C82.
> 
> However, today I found this which may be helpful...
> http://www.linuxprinting.org/show_printer.cgi?recnum=Lexmark-Z53
> 
> Best of luck,
> IanS
> 
> _______________________________________________
> Linux-users mailing list
> Linux-users at smtp.linux-sxs.org
> Unsubscribe/Suspend/Etc -> http://smtp.linux-sxs.org/mailman/listinfo/linux-users
> 

--