Discussion:
Local priner problem
Radek Bursztynowski
2013-03-04 15:21:19 UTC
Permalink
Hello All,

Today I try the first time to use local printer connected to thin client, and no effect.

My LTSP server is CentOS 6.3 x86_64.
My local printer connected to thin client via USB is Samsung ML-2165.
This printer connected to the server directly works very well.

The first I checked is thin client sees this printer.
Using Ctrl+F6 I switched to the shell and:
# tail -f /var/log/messages
I can see that printer is connected to /dev/usblt0
I checked jetpipe:
# ps aux | grep jetpipe

and I can see:
root 3463 0.0 0.0 760 pts/1 S+ 14:49 0:00 grep jetpipe

Thin client configuration in lts.conf:
[E0:69:95:65:A1:EB] # Nettop D510
LIKE = CentOS
PRINTER_0_DEVICE = "/dev/usblp0"
PRINTER_0_PORT = 9100
PRINTER_TYPE = U

Thin client receives from DHCP IP address 192.168.1.10
# Netbook D510
host d510 {
option host-name "d510";
hardware ethernet E0:69:95:65:A1:EB;
fixed-address 192.168.1.10;

### LTSP 5
option root-path "192.168.1.230:/opt/ltsp/i386";
next-server 192.168.1.230;
filename "/ltsp/i386/pxelinux.0";
### Koniec LTSP 5
}

Finally I added printer using system-config-printer:
socket://192.168.1.10:9100

And nothing.

I checked archives this issue and I found this post:
https://www.redhat.com/archives/k12osn/2012-September/msg00009.html

Follow this advice I deleted old jetpipe from thin client chroot and I renamed p910nd in jetpipe.

Still nothing. I can see the message that the printer could be not connected.

What should I to do to use local printer.
Any advice will be priceless.

Best regards,
Radek
j***@turtle.com
2013-03-04 16:07:06 UTC
Permalink
Radek, same server as yours,  this is what works for me like a charm:
 
        PRINTER_0_TYPE=S
        PRINTER_0_DEVICE="/dev/usb/lp0"
        PRINTER_0_WRITE_ONLY=Y

Check the /dev files. I use "Write only" because I don't want or need
the chatter. The printer type is really serial as in "Universal Serial
Bus".
 A good way to test for the properly created printer process is:
telnet 192.168.1.10 9100.
you should get:
Connected to 192.168.1.10.
Escape character is '^]'.

Julius

----- Original Message -----
From: "Support list for open source software in schools."
To:
Cc:
Sent:Mon, 4 Mar 2013 16:21:19 +0100
Subject:[K12OSN] Local priner problem

Hello All,

Today I try the first time to use local printer connected to thin
client, and no effect.

My LTSP server is CentOS 6.3 x86_64.
My local printer connected to thin client via USB is Samsung ML-2165.
This printer connected to the server directly works very well.

The first I checked is thin client sees this printer.
Using Ctrl+F6 I switched to the shell and:
# tail -f /var/log/messages
I can see that printer is connected to /dev/usblt0
I checked jetpipe:
# ps aux | grep jetpipe

and I can see:
root  3463  0.0   0.0   760  pts/1  S+  14:49  0:00  grep
jetpipe

Thin client configuration in lts.conf:
[E0:69:95:65:A1:EB]                # Nettop D510
   
LIKE                                  
= CentOS
    PRINTER_0_DEVICE          = "/dev/usblp0"
    PRINTER_0_PORT             = 9100
    PRINTER_TYPE                  = U

Thin client receives from DHCP IP address 192.168.1.10
# Netbook D510
  host d510 {
    option host-name "d510";
    hardware ethernet    E0:69:95:65:A1:EB;
    fixed-address 192.168.1.10;

    ### LTSP 5
    option root-path "192.168.1.230:/opt/ltsp/i386";
    next-server 192.168.1.230;
    filename        "/ltsp/i386/pxelinux.0";
    ### Koniec LTSP 5
  }

Finally I added printer using system-config-printer:
socket://192.168.1.10:9100

And nothing.

I checked archives this issue and I found this post:
https://www.redhat.com/archives/k12osn/2012-September/msg00009.html

Follow this advice I deleted old jetpipe from thin client chroot and
I renamed p910nd in jetpipe.

Still nothing. I can see the message that the printer could be not
connected.

What should I to do to use local printer.
Any advice will be priceless.

Best regards,
Radek This email is confidential and intended solely for the use of
the individual to whom it is addressed. Please note, any views or
opinions presented in this email are solely those of the author and
do not necessarily represent those of Turtle & Hughes, Inc.
Santiago Mera
2013-03-04 17:56:09 UTC
Permalink
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.

Hope this helps.

----
Ing. Santiago Mera
Droguería Uruguay S.A.
Tel: (+598) 2408 7505 int. 264


----- Original Message -----

From: "Radek Bursztynowski" <***@bursztynowski.waw.pl>
To: ***@redhat.com
Sent: Monday, March 4, 2013 1:21:19 PM
Subject: [K12OSN] Local priner problem

Hello All,

Today I try the first time to use local printer connected to thin client, and no effect.

My LTSP server is CentOS 6.3 x86_64.
My local printer connected to thin client via USB is Samsung ML-2165.
This printer connected to the server directly works very well.

The first I checked is thin client sees this printer.
Using Ctrl+F6 I switched to the shell and:
# tail -f /var/log/messages
I can see that printer is connected to /dev/usblt0
I checked jetpipe:
# ps aux | grep jetpipe

and I can see:
root 3463 0.0 0.0 760 pts/1 S+ 14:49 0:00 grep jetpipe

Thin client configuration in lts.conf:
[E0:69:95:65:A1:EB] # Nettop D510
LIKE = CentOS
PRINTER_0_DEVICE = "/dev/usblp0"
PRINTER_0_PORT = 9100
PRINTER_TYPE = U

Thin client receives from DHCP IP address 192.168.1.10
# Netbook D510
host d510 {
option host-name "d510";
hardware ethernet E0:69:95:65:A1:EB;
fixed-address 192.168.1.10;

### LTSP 5
option root-path "192.168.1.230:/opt/ltsp/i386";
next-server 192.168.1.230;
filename "/ltsp/i386/pxelinux.0";
### Koniec LTSP 5
}

Finally I added printer using system-config-printer:
socket://192.168.1.10:9100

And nothing.

I checked archives this issue and I found this post:
https://www.redhat.com/archives/k12osn/2012-September/msg00009.html

Follow this advice I deleted old jetpipe from thin client chroot and I renamed p910nd in jetpipe.

Still nothing. I can see the message that the printer could be not connected.

What should I to do to use local printer.
Any advice will be priceless.

Best regards,
Radek
_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Burke Almquist
2013-03-04 19:30:55 UTC
Permalink
Post by Santiago Mera
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
j***@turtle.com
2013-03-04 19:42:34 UTC
Permalink
Device depends on what is in the /dev directory. I have /dev/usb/lp0
In my experience the parallel printers just refused to work
julius

----- Original Message -----
From: "Support list for open source software in schools."
To:"Support list for open source software in schools."
Cc:
Sent:Mon, 4 Mar 2013 13:30:55 -0600
Subject:Re: [K12OSN] Local priner problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Santiago Mera
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).
Post by Santiago Mera
I solved this by installing the python-daemon package in the
chroot.
Post by Santiago Mera
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
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see
This email is confidential and intended solely for the use of the
individual to whom it is addressed. Please note, any views or
opinions presented in this email are solely those of the author and
do not necessarily represent those of Turtle & Hughes, Inc.
Santiago Mera
2013-03-04 19:54:17 UTC
Permalink
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


----- Original Message -----

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Santiago Mera
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
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Radek Bursztynowski
2013-03-04 18:55:29 UTC
Permalink
Hello,

Many thanks to Julius and Santiago. I will use your advice tomorrow at
the my lab and I report the results.

Best regards,
Radek
Post by Santiago Mera
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.
Hope this helps.
----
Ing. Santiago Mera
Droguería Uruguay S.A.
Tel: (+598) 2408 7505 int. 264
______________________________________________________________________
Sent: Monday, March 4, 2013 1:21:19 PM
Subject: [K12OSN] Local priner problem
Hello All,
Today I try the first time to use local printer connected to thin client, and no effect.
My LTSP server is CentOS 6.3 x86_64.
My local printer connected to thin client via USB is Samsung ML-2165.
This printer connected to the server directly works very well.
The first I checked is thin client sees this printer.
# tail -f /var/log/messages
I can see that printer is connected to /dev/usblt0
# ps aux | grep jetpipe
root 3463 0.0 0.0 760 pts/1 S+ 14:49 0:00 grep jetpipe
[E0:69:95:65:A1:EB] # Nettop D510
LIKE = CentOS
PRINTER_0_DEVICE = "/dev/usblp0"
PRINTER_0_PORT = 9100
PRINTER_TYPE = U
Thin client receives from DHCP IP address 192.168.1.10
# Netbook D510
host d510 {
option host-name "d510";
hardware ethernet E0:69:95:65:A1:EB;
fixed-address 192.168.1.10;
### LTSP 5
option root-path "192.168.1.230:/opt/ltsp/i386";
next-server 192.168.1.230;
filename "/ltsp/i386/pxelinux.0";
### Koniec LTSP 5
}
socket://192.168.1.10:9100
And nothing.
https://www.redhat.com/archives/k12osn/2012-September/msg00009.html
Follow this advice I deleted old jetpipe from thin client chroot and I
renamed p910nd in jetpipe.
Still nothing. I can see the message that the printer could be not connected.
What should I to do to use local printer.
Any advice will be priceless.
Best regards,
Radek
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Radek Bursztynowski
2013-03-05 13:11:25 UTC
Permalink
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" <***@dusa.com.uy>
Sent: Mon, 3/4/2013 8:54pm
To: "Support list for open source software in schools." <***@redhat.com>
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" <***@thealmquists.net>
To: "Support list for open source software in schools." <***@redhat.com>
Sent: Monday, March 4, 2013 5:30:55 PM
Subject: Re: [K12OSN] Local priner problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Santiago Mera
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
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>;
Santiago Mera
2013-03-05 14:58:58 UTC
Permalink
When starting jetpipe manually on the thin client shell, you could try the -d option (debug).
This may give you additional information as to why it's not printing...

----
Ing. Santiago Mera
Droguería Uruguay S.A.
Tel: (+598) 2408 7505 int. 264


----- Original Message -----

From: "Radek Bursztynowski" <***@bursztynowski.waw.pl>
To: "Support list for open source software in schools." <***@redhat.com>, "Support list for open source software in schools." <***@redhat.com>
Sent: Tuesday, March 5, 2013 11:11:25 AM
Subject: Re: [K12OSN] Local priner problem

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" <***@dusa.com.uy>
Sent: Mon, 3/4/2013 8:54pm
To: "Support list for open source software in schools." <***@redhat.com>
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" <***@thealmquists.net>
To: "Support list for open source software in schools." <***@redhat.com>
Sent: Monday, March 4, 2013 5:30:55 PM
Subject: Re: [K12OSN] Local priner problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Santiago Mera
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
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

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

_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Burke Almquist
2013-03-05 19:13:27 UTC
Permalink
It seems you were able to connect to port 9100, so the print server part must be working.
You said the printer is a Parallel Port one, correct? If that is the case, you need to make sure your client is loading the parallel port driver kernel module and the /dev/lp0 exists.
Radek Bursztynowski
2013-03-05 21:36:04 UTC
Permalink
The printer is connected to thin client via USB.

So, should I install cups package in the chroot and run cups service on
thin client?

Best regards,
Radek


--
Post by Burke Almquist
It seems you were able to connect to port 9100, so the print server part must be working.
You said the printer is a Parallel Port one, correct? If that is the case, you need to make sure your client is loading the parallel port driver kernel module and the /dev/lp0 exists.
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
j***@turtle.com
2013-03-05 23:44:15 UTC
Permalink
No, you don't need cups in the lts tree. The print services run on the
server.
Julius

----- Original Message -----
From: "Radek Bursztynowski" "Support list for open source software
in schools."
To:"Support list for open source software in schools."
Cc:
Sent:Tue, 5 Mar 2013 22:36:04 +0100
Subject:Re: [K12OSN] Local priner problem

The printer is connected to thin client via USB.

So, should I install cups package in the chroot and run cups service
on
thin client?

Best regards,
Radek

--
Post by Burke Almquist
It seems you were able to connect to port 9100, so the print
server part must be working.
Post by Burke Almquist
You said the printer is a Parallel Port one, correct? If that is
the case, you need to make sure your client is loading the parallel
port driver kernel module and the /dev/lp0 exists.
Post by Burke Almquist
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see
_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see
This email is confidential and intended solely for the use of the
individual to whom it is addressed. Please note, any views or
opinions presented in this email are solely those of the author and
do not necessarily represent those of Turtle & Hughes, Inc.
Jaap Bril
2013-03-06 09:05:16 UTC
Permalink
Debug of [..]/sbin/jetpipe revealed line 50: only '/dev/tty..' are
serial, devicetype 'S'. Other names will be parralel devicetype 'P'.
50 if devicename[:8] == '/dev/tty':*# This should catch regular serial and USB serial*
[..]
59 self.devicetype = 'S'
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.
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
Thanks a lot for all help, but still nothing. Let me explain my today exercise.
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 -----
Sent: Mon, 3/4/2013 8:54pm
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
Sent: Monday, March 4, 2013 5:30:55 PM
Subject: Re: [K12OSN] Local priner problem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Post by Santiago Mera
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
https://www.redhat.com/mailman/listinfo/k12osn
For more info see<http://www.k12os.org>
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see<http://www.k12os.org>;
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see<http://www.k12os.org>
b***@thealmquists.net
2013-03-05 22:18:55 UTC
Permalink
Dumb question, but did you reboot your thin client after you made the changes to the lts.conf file?
Post by Radek Bursztynowski
The printer is connected to thin client via USB.
So, should I install cups package in the chroot and run cups service on
thin client?
Best regards,
Radek
--
Post by Burke Almquist
It seems you were able to connect to port 9100, so the print server part must be working.
You said the printer is a Parallel Port one, correct? If that is the case, you need to make sure your client is loading the parallel port driver kernel module and the /dev/lp0 exists.
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
Loading...