Re: Local priner problem - SOLVED

Radek Bursztynowski <[email protected]>
Newsgroups gmane.linux.redhat.k12osn
Message-ID <10987965.761362561908472.JavaMail.root@poczta.bursztynowski.waw.pl>
Hello All,

Many thanks to All who sent me advice. Owing to this I solved this problem.
For forcing my printer to cooperation I made:

lts.conf
    PRINTER_0_DEVICE         = /dev/usb/lp0
    PRINTER_0_PORT         = 9100
    PRINTER_TYPE         = S

and jetpipe process is started as follow:

/usr./sbin/jetpipe -f /dev/usb/lp0

My printer prints with original jetpipe included in thin client, and with p910nd package got from http://p910nd.sourceforge.net/

That's all.

Thanks again for any help.

Best regards,
Radek


----

    Debug of [..]/sbin/jetpipe revealed line 50: only '/dev/tty..' are
    serial, devicetype 'S'. Other names will be parralel devicetype 'P'.

    

    jetpipe:
    
           50         if devicename[:8] == '/dev/tty':    # This should catch regular serial and USB serial
    
    [..]
    
           59             self.devicetype = 'S'
           60         else:
           61             self.device = open(devicename, 'wb')
           62             self.devicetype = 'P'
    
    

    I 'eliminated' this error and useing '/dev/usb/lp0' jetpipe threw an
    exception:

    serial.serialutil.SerialException("Could not configure port:(25,
    'Inappropriate ioctl for device')

    

    The comment on line 307 (serialposix.py) might be your answer.

    
          305         try:
          306             iflag, oflag, cflag, lflag, ispeed, ospeed, cc = termios.tcgetattr(self.fd)
          307         except termios.error, msg:      # if a port is nonexistent but has a /dev file, it'll fail here
          308             raise SerialException("Could not configure port: %s" % msg)
    
    Why the prot would be nonexistent I do not know; /dev/usb/lp0 gets
    created when a printer is connected to a usb port.

    

    Jaap

    

    On 03/05/2013 02:11 PM, Radek Bursztynowski wrote:
    
      Thanks a lot for all help, but still nothing. Let me explain my today exercise.

The first I used Julius's advice:
       PRINTER_0_TYPE=S
        PRINTER_0_DEVICE="/dev/usb/lp0"  # /dev/usblp0 is symbolic link to /dev/usb/lp0
        PRINTER_0_WRITE_ONLY=Y

Nothing. 
telnet 192.168.1.10:9100 
connection refused.

So, I started on thin client (shell console) jetpipe manually. 

Now telnet 192.168.1.10 9100 
connects, but still I couldn't print.

So I added /usr/sbin/jetpipe to /etc/rc.d/rc.local. Now every time telnet 192.168.1.10 9100 connects, but the printer doesn't print.

I changed PRINTER_0_TYPE=S with "U", still nothing.

I installed using chroot python-daemon, still nothing.
ps aux | grep python*
shows that any python process isn't running.

But very interesting - when I added this printer connected to thin client using system-config-printer on my LTSP server and I try to print test page, I can read the messages that printer is connected, next - the file sent to the printer, next "waiting for finishing printing job", and next "ready to use". But my printer didn't print anything.

The advice with /dev/lp0 I tried too - still noting.



When I try to add this printer on Windows computer using TCP/IP port (192.168.1.10:9100) I can see the message, that the printer is not connected (still telnet 192.168.1.10 9100 connects).

Any other advice, please?

Best regards,
Radek


----- Original Message -----
From: "Santiago Mera" <[email protected]>
Sent: Mon, 3/4/2013 8:54pm
To: "Support list for open source software in schools." <[email protected]>
Subject: Re: [K12OSN] Local priner problem

Yes, that would usually be the case I think.What happened to us with parallel printers is that we see no device in the /dev directory that corresponds to the printer (no /dev/lp0 or similar). So no matter what you put in PRINTER_0_DEVICE, jetpipe will complain about not finding the device and dies.
We ended up not bothering about parallel printing and are now using serial or usb.
----
Ing. Santiago Mera
Droguería Uruguay S.A.
Tel: (+598) 2408 7505 int. 264

From: "Burke Almquist" <[email protected]>
To: "Support list for open source software in schools." <[email protected]>
Sent: Monday, March 4, 2013 5:30:55 PM
Subject: Re: [K12OSN] Local priner problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Mar 4, 2013, at 11:56 AM, Santiago Mera wrote:


      
        Hello Radek, 
I have the same server as yours. The first time I tried to print locally I had the similar problems (jetpipe wasn't running).

I solved this by installing the python-daemon package in the chroot.
I'm still unable to print to a printer connected to the thin client via the parallel port though.


      
      I think for parallel port printers you need to use
 PRINTER_0_DEVICE          = "/dev/lp0"                 instead of "/dev/usblp0"
    PRINTER_TYPE                  = P                                 instead of U or S


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlE09nAACgkQxWV7OPa/g5EwBwCfZfiH96eoLgxZSBiUzl3Wtxw5
wtQAniN2yp+lxDZ2Ysf8IowNYZYN9GvS
=rekW
-----END PGP SIGNATURE-----

_______________________________________________
K12OSN mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

_______________________________________________
K12OSN mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>;

_______________________________________________
K12OSN mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

    
  

_______________________________________________
K12OSN mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>;

_______________________________________________
K12OSN mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.