Joseph Bishay wrote:
> Hello,
>
> On Wed, Dec 24, 2008 at 9:40 AM, Peter Scheie <[email protected]>
> wrote:
>
>> This may be of no use to you, but on K12Linux (Fedora) we forgot to include
>> pyserial in the chroot, which jetpipe requires, resulting in symptoms
>> similar to
>> yours. Adding it fixed the problem.
>>
>> Peter
>>
>
> How do I add pyserial? I have a similar problem where I am able to
> get an HP LJ 1000 USB printer to work no problem at all when plugged
> into the server, but I can't get it at all to print when plugged into
> a client. I've followed the instructions here
> http://wiki.ltsp.org/twiki/bin/view/Ltsp/Printers and whenever I send
> a print job the system reports that it is processing, then that it is
> complete but nothing came out! I am using the CentOS 5 k12ltsp
> version.
>
> Thanks,
> Joseph
>
>
Joseph,
I would first recommend that you be sure if jetpipe is the issue. I mean
if it is actually not working because in my case there was nothing wrong
with jetpipe. However my environment was KIWI-LTSP and Ubuntu but YMMV
on K12.
You can do that check by logging into one of the shells on the
thin-client (Alt+F1) as root and then check for ps aux | grep jetpipe.
If jetpipe is there which was the case with most of my printer problems
then it may be a firmware issue if you are using one of the foo2???
drivers which may be resolved in this way -
"
Got a HP LJ P1007 working with this entry in lts.conf:
[default]
....
RCFILE_01=/etc/init.d/init_hp_P1007.sh
init_hp_1007.sh is a very amateur script which shall need some building
up and may upload custom firmware based on the printer detected via
lsusb. (Not that good at shell scripting ;-( )
$ cat /opt/ltsp/i386/etc/init.d/init_hp_P1007.sh
#! /bin/sh
# Note that this file resides inside the chroot
p=`lsusb | grep -c P1007`
if [ -c "/dev/usb/lp0" ] && [ $p -eq 1 ] ; then
echo "HP Laserhet P1007 detected, loading firmware ... "
cat /usr/share/foo2xqx/firmware/sihpP1005.dl > /dev/usblp0
echo "Firmware loaded successfully"
fi
This can be done the way I have done it or even with a robust and more
generic script if one is included in upstream then a new lts.conf
parameter PRINTER_n_FIRMWARE= <firmware file name> may be added as
increasingly more and more printers at least from HP and using the
foo2???/foomatic drivers need this.
Any thoughts?
Regards,
SB
--
Shrenik Bhura
IntelliAnt: Consulting and Development of Free / Open Source Software
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
