Brian Wilson wrote:

> TSL 3.0 is the first time I have tried to set up CUPS.
> Until now I have used BSD variants including LPRng,
> so I figure my problems with cups are just me and
> the learning curve.
>
> Steven -- I did get past the first bump that perhaps you missed,
> my parallel port driver was not being loaded.
>
> On my system, I did 'modprobe parport_pc' to get it to load the 
> parallel port driver immediately.
> (Do 'dmesg' to see messages indicating it loaded.)
> I put parport_pc into /etc/modules so that it will
> be loaded after reboot.
>
> I deleted the old /etc/cupsd/printers.conf file and restarted (service
> cupsd restart) then I used the web interface to cupsd
> (http://myservername:631/) to configure the printer on the parallel
> port.
>
> Now for the strangeness: even though it lists my printer correctly by
> name (HP LaserJet 4ML/PS) (so it must be talking on parport) it lists
> the device as "Device URI: parallel:/dev/unknown-parallel0" and
> printing a test page fails. The status message it shows is
>
> "Printer not connected; will retry in 30 seconds..."
>
> I can queue print jobs and see them in the queue. I can remove them.
> But nothing goes to the printer. I tried manually editing the
> /etc/cupsd/printing.conf to force it to use /dev/lp0 as the device to
> no avail.
>
> Brian

Hi Brian,

Thanks for that I added the parport_pc via modprobe. I still have 
problems however. I have enabled debug mode in cupsd.conf and now I get

[29/Jul/2005:15:59:47 +1000] [Job 4] /usr/bin/gs: error while loading 
shared libraries: libXt.so.6: cannot open shared object file: No such 
file or directory

gs -l also produces ...

gs: error while loading shared libraries: libXt.so.6: cannot open shared 
object file: No such file or directory

Looks like a problem with ghostscript ...

I have hardcoded the printers.conf file

<DefaultPrinter HPLj3330>
Info My Printer
Location Back Room
DeviceURI parallel:/dev/lp0
State Idle
Accepting Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
</Printer>

Will advise further
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss

Reply via email to