hpoj-devel — HPOJ development/support list

Re: [hpoj-devel] OfficeJet 4100 - can't get this printer to work with HPOJ 0.91

[Richard J. <ri...@an...>]

Following the advice here:

http://hpoj.sourceforge.net/_todo-0.90.shtml

I upgraded to libusb 0.8.1 and the latest CVS version of hpoj, and the
OfficeJet 4100 printer *still* doesn't work.  Now the device cannot
even be found by ptal-init setup, even though the kernel can see it
quite happily.

Rich.

-- 
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
"One serious obstacle to the adoption of good programming languages is
the notion that everything has to be sacrificed for speed. In computer
languages as in life, speed kills." -- Mike Vanier

[hpoj-devel] OfficeJet 4100 - can't get this printer to work with HPOJ 0.91

[Richard J. <ri...@an...>]

Probe for USB-connected devices ([y]/n)?  y

Probing "/dev/usb/lp0"...  
    *** Found "officejet 4100 series" but failed to communicate with it!
    *** Elapsed time for this attempt was 6 second(s).
    *** Check syslog file for ptal-mlcd error messages.
    *** See hpoj documentation for troubleshooting information.

In /var/log/syslog I see:

Mar 20 10:37:28 aomori ptal-mlcd: SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=31144, e=2, t=1079779048         ptal-mlcd successfully initialized. 
Mar 20 10:37:28 aomori ptal-mlcd: SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=31151, e=111, t=1079779048         ptal-mlcd successfully initialized. 
Mar 20 10:37:28 aomori ptal-mlcd: ERROR at ExMgr.cpp:4063, dev=<mlc:usb:probe@/dev/usb/lp0>, pid=31151, e=22, t=1079779048         libusbFindDevice: Couldn't find device! 
Mar 20 10:37:33 aomori ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:251, dev=<mlc:usb:probe@/dev/usb/lp0>, pid=31151, e=22, t=1079779053         Command reply timeout on port=0, count=1, lastRequest=0x00! 
Mar 20 10:37:33 aomori ptal-mlcd: ERROR at ExMgr.cpp:871, dev=<mlc:usb:probe@/dev/usb/lp0>, pid=31151, e=22, t=1079779053         exClose(reason=0x3002) 
Mar 20 10:37:34 aomori ptal-mlcd: SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=31161, e=111, t=1079779054         ptal-mlcd successfully initialized. 
Mar 20 10:37:34 aomori ptal-mlcd: ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe@/dev/usb/lp1>, pid=31161, e=19, t=1079779054         Couldn't find device! 
Mar 20 10:37:34 aomori ptal-mlcd: SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=31170, e=111, t=1079779054         ptal-mlcd successfully initialized. 
Mar 20 10:37:34 aomori ptal-mlcd: ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe@/dev/usb/lp10>, pid=31170, e=19, t=1079779054         Couldn't find device! 
Mar 20 10:37:34 aomori ptal-mlcd: SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=31179, e=111, t=1079779054         ptal-mlcd successfully initialized. 

[Last two messages repeated several more times]

In dmesg there doesn't seem to be anything particularly unusual:

usb.c: ignoring set_interface for dev 2, iface 1, alt 0
usb.c: registered new driver usblp
usb.c: ignoring set_interface for dev 2, iface 1, alt 0
printer.c: usblp0: USB Bidirectional printer dev 2 if 1 alt 0
printer.c: v0.8:USB Printer Device Class driver

I had another HP OfficeJet (45) working on the same USB port until we
bought this printer to replace it, so I'm reasonably sure the hardware
is OK.

Ideas?

Rich.

-- 
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
PTHRLIB is a library for writing small, efficient and fast servers in C.
HTTP, CGI, DBI, lightweight threads: http://www.annexia.org/freeware/pthrlib/

[hpoj-devel] HP PSC2210 is not available for scanning

[Till K. <til...@gm...>]

Here is a report on the bug tracking system for Mandrakelinux:

http://qa.mandrakesoft.com/show_bug.cgi?id=8763

The device did not cause any errors on "ptal-init setup" and it prints 
correctly. Problem is that it does not scan. There is also a debug log 
of SANE attached to the report. I am not sure whether HPOJ (0.91), the 
kernel (between 2.6.3 and 2.6.4), or even SANE (1.0.13) is the culprit.

    Till

Re: [hpoj-devel] Not printing after upgrading from kernel 2.6.2 to 2.6.4

[Woojin L. <wl...@ca...>]

Same thing happens with Mandrake 10 which uses kernel 2.6.3.
I have HP officejet 4110.  I was told that kernel 2.6.3 and up has problem 
with HP usb printers for now...

Woojin

On Thursday 18 March 2004 07:30 am, Saulo Calixto Bonfim wrote:
> Greetings from Brazil,
>
> after upgrading my kernel from 2.6.2 to 2.6.4 my HP PSC 1210 USB printer
> does not work anymore. I mean, it pulls the paper but doesn't print
> anything, so it keeps pulling paper continuously.
> When I switch back to kernel 2.6.2, it prints normally.
>
> hopj from cvs
> hpijs-1.5
>
> Any help would be appreciated.
>
> TIA,

[hpoj-devel] Not printing after upgrading from kernel 2.6.2 to 2.6.4

[Saulo C. B. <cu...@sa...>]

Greetings from Brazil,

after upgrading my kernel from 2.6.2 to 2.6.4 my HP PSC 1210 USB printer 
does not work anymore. I mean, it pulls the paper but doesn't print 
anything, so it keeps pulling paper continuously.
When I switch back to kernel 2.6.2, it prints normally.

hopj from cvs
hpijs-1.5

Any help would be appreciated.

TIA,


-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Saulo Calixto Bonfim      -       sa...@sa...
Chave PGP: http://www.saulo.eti.br/saulo-pgp.key
Powered by Conectiva Linux 9 - Kernel 2.6.2
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The Power Rangers use Linux. Shouldn't you?

[hpoj-devel] HP PSC 1210 - hpoj-0.91 - linux-2.6.4 - fedora core 1

[Alexandre T. R. <th...@pp...>]

The print is ok after this alteration from :

http://www.ussg.iu.edu/hypermail/linux/kernel/0403.0/1190.html

( not all patch )

===

 --- drivers/usb/class/usblp.c.orig 2004-03-05 17:09:00.412189056 +0000
 +++ drivers/usb/class/usblp.c 2004-03-05 17:10:30.121551160 +0000
  <at>  <at>  -609,8 +609,10  <at>  <at>  static ssize_t usblp_write(struct file *
 while (writecount < count) {
 if (!usblp->wcomplete) {
 barrier();
 - if (file->f_flags & O_NONBLOCK)
 + if (file->f_flags & O_NONBLOCK) {
 + writecount += transfer_length;
 return writecount ? writecount : -EAGAIN;
 + }

 timeout = USBLP_WRITE_TIMEOUT;
 add_wait_queue(&usblp->wait, &wait);
===

now, HP PSC 1210 work fine !!!

[hpoj-devel] Re: Kernel bug: 2.6.3-3mdk allows printing on PSC 1210, 2.6.3.4mdk not

[thieme <th...@te...>]

HP PSC 1210 with fedora core 1 and kernel 2.6.4 also do not work -
could=
 only print blank sheets (with kernel 2.6.3 HP PSC 1210 work fine) 

Re: [hpoj-devel] Fixed in 0.91 or not?

[Jarl F. <ja...@so...>]

Jarl Friis <ja...@so...> writes:

> Hi.
>
> I just bought a *PSC2175* and installed it to a linux (*SuSE 9.0*) box for
> a friend. The HPOJ software with SuSE-9.0 is hpoj 0.9. I experience
> the scanning offset problem which seem to be well described on=20
> http://hpoj.sourceforge.net/_todo-0.90.shtml=20
> as a known problem with hpoj-0.9
> ------------------------------
> When scanning on some models (especially the PSC 2xxx and OfficeJet
> 61xx series), the bottom and/or right margin may be cut off, and/or
> selected scan areas may be offset to the right. Fixed as much as
> possible in CVS; any remaining cutoffs are probably the fault of
> either the device or frontend application.
> ------------------------------
> The page states that this has been fixed in CVS (but with no date).
>
> Can one of you tell me if the problem is fixed in hpoj-0.91?

In hope it will benefit others I will answer my question then :-)=20

Version 0.91 does contain a fix for the above mentioned problem.

I have created a SuSE-9.0 package of hpoj-0.91 (based on the SRPM
shiped with SuSE-9.0). The packages can be found on
http://www.softace.dk/personal/jarl/hpoj/SuSE-9.0/

Be aware that the configuration file format have change from hpoj-0.90
to hpoj-0.91, so you must run 'ptal-init setup' once again.

Jarl

--=20
Jarl Friis
Softace
Om=F8gade 8, 2.sal
2100 K=F8benhavn =D8.
Denmark
Phone:  +45 26 13 20 90
E-mail: ja...@so...

[hpoj-devel] Re: Kernel bug: 2.6.3-3mdk allows printing on PSC 1210, 2.6.3.4mdk not

[Urmas <urm...@pp...>]

Printing started to work with 2.6.3-4mdk kernel after applying following 
usblp.c patch from 
http://www.ussg.iu.edu/hypermail/linux/kernel/0403.0/1190.html

===
 --- drivers/usb/class/usblp.c.orig 2004-03-05 17:09:00.412189056 +0000
 +++ drivers/usb/class/usblp.c 2004-03-05 17:10:30.121551160 +0000
 @@ -609,8 +609,10 @@ static ssize_t usblp_write(struct file *
 while (writecount < count) {
 if (!usblp->wcomplete) {
 barrier();
 - if (file->f_flags & O_NONBLOCK)
 + if (file->f_flags & O_NONBLOCK) {
 + writecount += transfer_length;
 return writecount ? writecount : -EAGAIN;
 + }
 
 timeout = USBLP_WRITE_TIMEOUT;
 add_wait_queue(&usblp->wait, &wait);
 @@ -670,7 +672,8 @@ static ssize_t usblp_write(struct file *
 
 usblp->writeurb->transfer_buffer_length = transfer_length;
 
 - if (copy_from_user(usblp->writeurb->transfer_buffer, buffer + writecount, 
transfer_length)) {
 + if (copy_from_user(usblp->writeurb->transfer_buffer, 
 + buffer + writecount, transfer_length)) {
 up(&usblp->sem);
 return writecount ? writecount : -EFAULT;
 }
 ====

[hpoj-devel] Re: Kernel bug: 2.6.3-3mdk allows printing on PSC 1210, 2.6.3.4mdk not

[Nicolas P. <np...@ma...> <Hi...@ka...>]

Could you use lastest cooker initscripts (initscripts-7.06-44mdk.i586.rpm) or
# umount /proc/bus/usb ; mount -t usbdevfs none /proc/bus/usb
Regards,
Date: Mon, 15 Mar 2004 15:17:41 +0100
In-Reply-To: <405...@gm...> (Till Kamppeter's message of "Mon,
 15 Mar 2004 10:07:17 +0000")
Message-ID: <m2z...@ka...>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit

Till Kamppeter <til...@gm...> writes:

> Oi,
>
> attached are two postings from the HPOJ list which show that HP PSC
> 1xxx multi-function devices work with kernel 2.6.3-3mdk and not with
> kernel 2.6.3-4mdk.
>
>     Till
> From: Urmas Närep <urm...@pp...>
> Subject: Re: [hpoj-devel] PSC 1210 : blank sheets on Mdk 10.0
> To: hpo...@li...
> Date: Mon, 15 Mar 2004 08:56:51 +0200
>
> On Sunday 14 March 2004 23:31, Gérard Delafond wrote:
>>  but I don't need a computer to do that
>
> PSC printers don't work with mdk 10.0 kernel 2.6.3-4mdk. I have HP PSC 1350 
> and it crashed the kernel when I turned off the printer while it was printing 
> empty pages. I switched back to 2.6.3-3mdk, and printing works now fine.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
>
> _______________________________________________
> hpoj-devel mailing list
> hpo...@li...
> https://lists.sourceforge.net/lists/listinfo/hpoj-devel
>
>
> ----------
>
> From: Gérard Delafond <ge...@de...>
> Subject: [hpoj-devel] PSC 1210 : blank sheets on Mdk 10.0
> To: hpo...@li...
> Date: Sun, 14 Mar 2004 22:31:48 +0100
> Organization: Delafond
>
> Hi !
>
> I updated Mdk 9.2 into 10.0 (kernel 2.6.3), and my PSC 1210 could only print 
> blank sheets (hundreds of them).
> It's quite funny, but I don't need a computer to do that.
>
> After updating hpoj/gimprint, I could still not print.
>
> So I rebooted with 2.4 kernel, and I could print again with no special 
> setting.
>
> Is there a version of the driver which accepts working with 2.6 kernels ?
>
> Thanks
>
> Gerard
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>
> _______________________________________________
> hpoj-devel mailing list
> hpo...@li...
> https://lists.sourceforge.net/lists/listinfo/hpoj-devel
>
>
> ----------

Re: [hpoj-devel] HP any Photsmart Paper size limits

[Till K. <til...@gm...>]

Darragh Bailey wrote:
> 
> As I see it there are 3 areas where the problem could be
> 1) printer firmware

In this case one could try to hack the HPIJS driver somehow that on the 
end of the job the paper does not get ejected and the next job is 
directly printed at the end of the previous one.

> 2) printer driver limitation

Then one simply needs to modify HPIJS to accept any custom paper size. 
There is already an option for custom paper sizes. One should simply 
check whether HPIJS has limits and remove them.

> 3) configuration settings
> 

This you can simply try. Simply print with a custom paper size with a 
height bigger than 530 mm and see how much comes out. For the test use 
cheap dot matrix paper and a long plain text file (which CUPS converts 
to PostScript).

There are no paper size limitations in Foomatic and AFAIK also none in 
GhostScript (Foomatic and GhostScript is also used for Epson and there 
we know that it works.).

    Till

[hpoj-devel] HP any Photsmart Paper size limits

[Darragh B. <fe...@co...>]

Hi,

I've been hearing that there are some paper size limits with all HP Photosmart 
printers, basically you can't print large landscape photos on paper of about 
590mm length, the limit is about 530 if you use banner which is not the same 
and small again for. (its been confirmed by a friend that this problem exists 
when printing from windows)

I currently possess a PSC 2410, but I haven't managed to get my hands on 
suitable paper to try and test if there is a simple way around this problem 
under gnu/linux, or even if it exists with the gnu/linux drivers just yet. 
Since the gnu/linux driver is opensource ( and of course gnu/linux is my 
preference :) ) I thought I'd ask here if anyone had encountered this problem.

Documentation on this is non existant, it appears just to be one of those 
undocumented gotchas with the HP printers, as such my friend who does a lot of 
photography uses an epson printer for those Landscape photos that can't be 
printed via the HP one.


As I see it there are 3 areas where the problem could be
1) printer firmware
2) printer driver limitation
3) configuration settings


Obviously 3 requires only modification of settings, 2 requires alterations to 
the driver and should be a relatively minor adjustment with the opensource but 
1 would require HP to rewrite/update its printer firmware.


So:
a) has anyone tried printing on paper outside the specified supported sizes for 
HP Photosmart printers and had success or failure
b) is aware of the limitation and where it lies
c) has come across this problem during driver developement and knows where its 
encountered (actually what part of the driver handles media sizes?)
d) knows where the extent of the problem is documented, hp website and google 
aren't very helpful in this case or else I'm just blind.


Any information about the problem would be appreciated.

-- 
Darragh

"Nothing's foolproof to a sufficently talented fool"

Re: [hpoj-devel] PSC 1210 : blank sheets on Mdk 10.0

[Urmas <urm...@pp...>]

On Sunday 14 March 2004 23:31, G=E9rard Delafond wrote:
>  but I don't need a computer to do that

PSC printers don't work with mdk 10.0 kernel 2.6.3-4mdk. I have HP PSC 1350=
=20
and it crashed the kernel when I turned off the printer while it was printi=
ng=20
empty pages. I switched back to 2.6.3-3mdk, and printing works now fine.

[hpoj-devel] PSC 1210 : blank sheets on Mdk 10.0

[<ge...@de...>]

Hi !

I updated Mdk 9.2 into 10.0 (kernel 2.6.3), and my PSC 1210 could only print 
blank sheets (hundreds of them).
It's quite funny, but I don't need a computer to do that.

After updating hpoj/gimprint, I could still not print.

So I rebooted with 2.4 kernel, and I could print again with no special 
setting.

Is there a version of the driver which accepts working with 2.6 kernels ?

Thanks

Gerard

[hpoj-devel] PSC 1210 under Debian Woody

[Richard S. <ri...@al...>]

Hi all

I've been trying to get an HP PSC 1210 working under Linux.. the fact that
it was listed as working is why I allowed it to be bought.  So far I've
had lots of fun.  The system:

Debian Woody
Linux kernel 2.4.24
libusb 0.1.8 (also tried 0.1.7)

ptal-init setup appears to work OK and finds the printer
ptal-init start also seems to work fine, and produces this in syslog:

Mar 13 11:15:38 raphael ptal-mlcd: SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:psc_1200_series>, pid=9048, e=2, t=1079129738         ptal-mlcd successfully initialized.
Mar 13 11:15:38 raphael ptal-printd: ptal-printd(mlc:usb:psc_1200_series) successfully initialized using /var/run/ptal-printd/mlc_usb_psc_1200_series*.

ptal-devid comes up with this:

richard@raphael:~$ ptal-devid
MFG:Hewlett-Packard;MDL:psc 1200 series;CMD:LDL,MLC,PML,DYN;CLS:PRINTER;1284.4DL:4d,4e,1;SN:MY394F317F5H;S:0380008000820000002c1480060c2500062;

if I run it as root, though, I get an error message:

raphael:/home/richard# ptal-devid

ptal-mlcd: ERROR at ExMgr.cpp:4063, dev=<mlc:usb:psc_1200_series@/dev/usb/lp0>, pid=9048, e=20, t=1079129854libusbFindDevice: Couldn't find device!
MFG:Hewlett-Packard;MDL:psc 1200 series;CMD:LDL,MLC,PML,DYN;CLS:PRINTER;1284.4DL:4d,4e,1;SN:MY394F317F5H;S:0380008000820000002c1480060c2500062;


ptal-mlcd is linked with libusb:

richard@raphael:~$ ldd /usr/local/sbin/ptal-mlcd
        libusb-0.1.4 => /usr/local/lib/libusb-0.1.4 (0x4001e000)
        libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x40026000)
        libm.so.6 => /lib/libm.so.6 (0x40070000)
        libc.so.6 => /lib/libc.so.6 (0x40091000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)


I've been reading through the docs, and can't figure this out.  Can anyone
shed any light?

Thanks

Richard

[hpoj-devel] Looking for updates...

[kent e. <ken...@gr...>]

Hi to all ...

The HP1100a of ours is connected to a redhat linux as our print server,
now the issue with this printer is that we have to toggle on/off the
power switch for the printing to be pushed through .. Now there are some
users around doesn't know aboiut this and they kept on complaining
regarding this matter.. Good if im around but most of the time im not,
so they will transfer the printer to their workstations which I hate
people doing that...

Now, Just asking for any updates/inputs regarding this matter

TIA

- kent e -

[hpoj-devel] libusbDevice: Couldn't find device

[Darren C. <dc...@ws...>]

Hi all,

I have been having a lot of trouble with my OfficeJet 7110.  It 
sporadically functions but generally just hangs in processing jobs.  
The error message I keep getting is:

ptal-mlcd: ERROR at ExMgr.cpp:4063, 
dev=<mlc:usb:officejet_7100_series@/dev/usb/lp0>, pid=1115, e=22, 
t=1078773288
libusbFindDevice: Couldn't find device!

which happens every time I start cups.  This happens regardless of 
whether or not the printer is even in the cups configuration.  When I 
use the cups web interface, the ptal device is listed as "ptal device 
not found" although very occasionally comes up correctly and then the 
printer functions for a while and then stops seemingly of its own 
accord.

I have tried various forms of power on and off between the printer and 
the computer and tried starting the services (i.e. hpoj, cups, etc.) 
manually in every order I can think of.

Does anyone have any thoughts on what the problem might be?  I am using 
hpoj-0.91 on a debian stable distribution.

Thanks,
Darren

[hpoj-devel] hpoj causing printing to be scrambled..

[Draco N. <dra...@ly...>]

Hi,  I'm new to the list (and indeed hpoj having only just discovered it) and I'm having problems.

I'm running Fedora Core 1, and decided today to get my printer (a HP PSC 500) to work with it.  I ran the Fedora
print setup for cups and it all worked fine.  Then I decided that I wanted to get the scanner to work too, and
after some investigation discovered that the way to do this would be to install hpoj, which I went ahead and did.

Then comes the problems.  I tried to run 'ptal-init setup' and although it found the printer it then complained
that the printer "wasn't listening" (apologies but I haven't got a copy of exactly what it said).  I ran 'ptal-init
setup' again and this time it didn't even find the printer.  At this point I decided to give up with getting the
scanner to work (at least for the present), happy in the knowledge that I could at least print.

Then a few hours later and I tried to print something.  And all that came out were several pages with a line of
random characters across the top and nothing else.  I tried to print a test page and the same happened.

So figuring that hpoj had caused the problem I uninstalled it.  However the problem still happened.  I've removed
and then reinstalled everything relating to printing and it's still happening.

So I guess I want to ask two things.  Firstly, any idea why hpoj might have caused this problem, and are there any
config files that might have been left behind when I removed hpoj that could be the reason the problem is persisting.

Or alternatively (and I suppose preferably), does anyone have experience getting a HP PSC500 to work with hpoj, and
can I get some advice on how to get hpoj installed and noticing my printer properly.

Ideally I'd want hpoj working so that I can scan and print, but I'd be perfectly happy just removing whatever is
causing the screwy printing so that it will just print again properly.

Thanks for any help you can give me!

Fran.

Lycos EMail has 10 MB of storage space. http://mail.lycos.co.uk

RE: [hpoj-devel] Problem with hpoj /w SMP and USB?

[Crosland, J. <Jer...@21...>]

I had the same problem, only my printer is the multi-function GX85, also on=
 the USB port. I have a dual-CPU box where I installed SuSE 9.0 and have be=
en (so-far) unable to get printing to work. In reading the support pages fo=
r hpoj I found that I needed to install the 0.91 version of the package. I =
did that (manually, from source, because binaries for SuSE 9.0 were not yet=
 available) and the ptal setup ran fine this time. It noticed that I had th=
e printer module activated in the kernel, with a USB printer and SMP and it=
 offered to turn it off for me, which I told it to do. All tests from the c=
ommand line worked fine then. My problem came when I tried to go into Yast =
to configure the printer queue etc. and Yast could not find things. I poste=
d a message here, and recieved the following responses, which I have not ye=
t had a chance to test out:

From Laurence Keefe:

	When you installed version .91 of hpoj, where did things end up?  Are=20
ptal-init, ptal-mlcd, and ptal-printd all in /usr/sbin?  That is where SuSE=
 expects to find them, along with ptal-cups and ptal-photod.

	Does SuSE say that CUPS will not run with an SMP kernel?  If it does run t=
hen=20
you don't want to use YAST anyway to set up the printing, or so the hpoj=20
documentation says.  I successfully set up my OfficeJet V40 to print and sc=
an=20
using the CUPS web interface.

And from Cory Meisch:

Using YaST be sure that CUPS and HPOJ are setup up to start on runlevels
3 and 5. Then, use the web interface http://localhost:631 to setup your
device.

Cory
hp linux printing team

Jerel Crosland
Technical Specialist
 818/704-3187

Bug: Small living things that small living boys throw on small living girls.


-----Original Message-----
From: hpo...@li...
[mailto:hpo...@li...]On Behalf Of James B.
Hiller
Sent: Tuesday, March 02, 2004 3:07 PM
To: Dr. Andreas Schenk
Cc: hpo...@li...
Subject: Re: [hpoj-devel] Problem with hpoj /w SMP and USB?


Hi.

Thanks for all the detail.  I hope others will jump in, because I'm not
real familiar with a lot of the things that you have, and I'm not at
all familiar with the track record of hpoj with the types of printers
you're using.  (Implied:  maybe there could be some problems with
those types of printers - is hpoj known to and intended to work ok
with LaserJets?)

> My software: SuSE Linux 9.0 installed on the workstation. No other operat=
ing=20
> system besides that. Kernel: 2.4.21-99-smp4G. I guess the smp stands for=
 > symmetric multi-processor. I don't know exactely what it means, but I gu=
ess,=20
> it should work with a hyperthreading CPU.

Right.  SMP is Symmetric Multi Processing.  There's a very good, just a lit=
tle
old, SMP-HOWTO for linux that is well worth the read.  It explains a lot
about the capability in its different flavors, ways to make use of it,
and a lot more.  It also has links to the Linux Parallel Processing HOWTO
and a few other very good docs, all of which you would likely enjoy.

The canonical URL for the SMP HOWTO is:

http://www.tldp.org/HOWTO/SMP-HOWTO.html

Note that there is a link to the maintainer's site, and in fact there is
a slightly newer, better version there.

The SMP HOWTO briefly mentions hyperthreading, as well as general hardware
issues across a number of platforms, so you may gain some insight as to
whether you have other latent issues to contend with.  But again, the
document is 18 months old, so you'll probably get better general info on
hyperthreading from other sources.

> So I read the troubleshooting guide and found the problem "I have=20
> an SMP system, and I experience kernel OOPSes or complete system lockups =
when=20
> using USB".

According to the original hpoj maintainer, David Paschal, the linux SMP/USB
bug was in principle fixed with the linux 2.6 series (which implies somewhe=
re
in the 2.5 development series as well).  However, he didn't have the
opportunity to do comprehensive hpoj-related testing, so he couldn't attest
to the veracity of the fix or 2nd/3rd order regression.  Worth keeping
in mind.

He has also previously told me that there was never an issue with SMP and
parallel port hpoj, though on occasion someone would say, or imply, on
the list that they were having such troubles.  I know this myself to be
true, as I've been running hpoj/parallel port and an SMP box for a Very Long
Time (since before hpoj actually did anything) (both Intel and AMD flavors).
And also, though you didn't ask - the issue does not come up simply
because one has USB configured and running in an SMP kernel.  It's only when
you're attempting to use hpoj with USB that the problem manifests.  (I say
this because there has been traffic on the list from time to time asserting
otherwise, but those folks were misunderstanding the issue at the time).

Aside from all that - you'd probably benefit from upgrading the kernel if
you don't have other major dependencies on 2.4.21.  There might even be
some "improvement" in the SMP bug in the later 2.4-series kernels; I seem
to recall some assertions of that on this mailing list.  If I remember
right, it would be at least 2.4.23 to get to.  But I'll stress that I'm
not certain of the accuracy of this conjecture, so even better would be
to just go with latest (2.6.3, almost .4 now).

> I tried to reboot with the nosmp kermel option. This didn't work, the sys=
tem=20
> didn't boot with this option. (I wonder why). Then I disabled hyperthread=
ing=20
> in the BIOS setup. As a result, hpoj worked pretty fine. After I enabled=
 > hyperthreading again in the BIOS setup, the system locked up again. So I=
 > guess, I have the cited problem.

Seems like it.

> What can I do now (besides throwing away something)?

Rather than throwing anything away, you might consider just going with
parallel-port-only for the moment, either with the one parallel port
printer that you have, or even better, with that one and one borrowed
from a friend (and a $10 PCI parallel port card if you need one).
This way you could remove the USB issue from the mix and make sure you're
not having other problems not at all related to it (seems like you could
be).  Then you might be able to roll in hpoj with USB in a controlled
way and see what happens.

Hope some of this helps.

jbh


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick

_______________________________________________
hpoj-devel mailing list
hpo...@li...
https://lists.sourceforge.net/lists/listinfo/hpoj-devel


***********************************************************************
This e-mail and any files transmitted with it are intended=20
solely for the use of the addressee.  This e-mail may=20
contain confidential and/or legally privileged information. =20
Any review, transmission, disclosure, copying, or any action=20
taken or not taken, by other than the intended recipient, in=20
reliance on the information, is prohibited.  If you received=20
this e-mail in error, notify the sender and delete this e-mail=20
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century=20
Insurance Group reserves the right to monitor, access and=20
review all messages, data and images transmitted through=20
our electronic mail system. By using our e-mail system, you=20
consent to this monitoring.=20
***********************************************************************

Re: [hpoj-devel] Problem with hpoj /w SMP and USB?

[Bayard R. C. <n1...@co...>]

I am having similar problems, which I've been able to distill down 
somewhat...

My configuration info:
Asus A7M266-D, two AMD MP1800+ CPUs, 1GB PC2100, Adaptec 3960D SCSI 
controller,
2 SCSI hard drives plus Plextor PX-W1210S CDRW, Matrox G550 display card 
to an HP f70.
HP PSC2410xi on my USB *with* the duplexer (and it's an old one off of 
my 940c !).
No other USB devices usually, except an HP812 camera, which continues to 
work correctly.

SuSE 9.0 with all mandatory (YOU-sensed) updates, albeit not every 
non-security
related update, has been installed. This includes the new kernel:

Linux version 2.4.21-192-smp4G (ro...@i3...) (gcc version 3.3.1 
(SuSE Linux)) #1 SMP Wed Feb 18 19:27:48 UTC 2004

hpijs at version 1.5, hpoj at 0.91.

System is configured to use CUPS (rpm -q cups: cups-1.1.19-85) and two 
queues are
set up, one for plain, ordinary, everyday use (and as the default), the 
other to stipulate
1200dpi and photopaper. Kooka is used to access the scanner.

Symptoms:
Boot log shows:
<notice>start services (ptal-init)

Stopping the HP OfficeJet Linux driver.
Starting the HP OfficeJet Linux driver.
    mlc:usb:psc_2400_series

<notice>exit status of (ptal-init) is (0)
Then, a few lines later:

ptal-mlcd: ERROR at ExMgr.cpp:2525, 
dev=<mlc:usb:psc_2400_series@/dev/usblp3>, pid=725, e=19, t=1078338477

However, 'lpq' will typically show that the printer is ready. The CUPS 
web administrative
screen (http://localhost:631/printers) will show that the Printer State 
is idle. But,
queuing a print job typically will then trigger the Printer State to 
Stopped.

Current Workaround:

I previously invoked 'ptal-init setup' under a bash command line ad nauseum.
However, while this helped provide some useful configuration 
information. Specifically,
ptal eventually concocted a URI. However, it appears that CUPS 
won't/can't/doesn't
see it by itself and doesn't bother to remember it across boots.

So, for now, I boot the system, login as a regular user, but open a 
spare terminal window
with a bash shell in it. I go into the CUPS admin webpage, click on 
'modify printer'.
It shows "Name: hp_psc2400", "Location: USB printer on 
//hp0MDL:psc/2400%20series0CMD:MLC,PCL,PML,DW-PCL;CLS:PRINTER;1284.4DL:4d,4e,1;SN:MY3BCG239V6T;S:038000808400102
and Description: hp psc 2400 series".

I then click on 'Continue' and the 'Device for hp_psc2400' screen 
usually says:
Device: App Socket/HP JetDirect (which appears to be simply the first item
available on the menu list). I scroll down to 'ptal device not found' 
and select
it, and then proceed to the next screen, which gives me the (correct) 
name and URI,
which I then select (no other real choice, but it is correct and works 
nicely), and then
continue to the next two screens for 'Make: and "Model/Driver". I choose the
appropriate items (Hewlett-Packard and "HP PSC 2400 Foomatic/hpijs 
(recommended) (en)")
and 'continue'.

At this point, however, the printer still won't start printing. I simply 
threw together
a simple script, and, yes, I'm sure I could have used various HUP 
commands, but
this is straightforward enough for me for now until the problem is 
solved for real:

/etc/init.d/cups stop
/etc/init.d/ptal-init stop
/etc/init.d/ptal-init start
/etc/init.d/cups start

Once I do that, and then hit the CUPS admin web page to 'Start Printer', 
I'm in
business. However, I occasionally have to re-hit that web page button 
after each
print job to keep the printer rolling along - it appears that the queue 
stops. I haven't
thoroughly investigated this. I have not really looked at the code 
module (ExMgr.cpp)
as I'm not a C++ guy and the ptal stuff looks pretty complex to me.

One other interesting symptom is that there are LOT of complaints in my 
/var/log/messages
file(s) about a missing disk drive, which I *think* is the memory 
card/stick hardware
on the PSC 2410xi, which is normally empty:

Mar  3 13:28:01 linux kernel: sdc : READ CAPACITY failed.
Mar  3 13:28:01 linux kernel: sdc : status = 1, message = 00, host = 0, 
driver = 08
Mar  3 13:28:01 linux kernel: Current sd00:00: sense key Not Ready
Mar  3 13:28:01 linux kernel: Additional sense indicates Medium not present
Mar  3 13:28:01 linux kernel: sdc : block size assumed to be 512 bytes, 
disk size 1GB.
Mar  3 13:28:01 linux kernel: sdc: test WP failed, assume Write Enabled
Mar  3 13:28:01 linux kernel:  sdc: I/O error: dev 08:20, sector 0
Mar  3 13:28:01 linux kernel:  I/O error: dev 08:20, sector 0
Mar  3 13:28:01 linux kernel:  I/O error: dev 08:20, sector 2097144
Mar  3 13:28:01 linux kernel:  I/O error: dev 08:20, sector 2097144
Mar  3 13:28:01 linux kernel:  I/O error: dev 08:20, sector 0
Mar  3 13:28:01 linux kernel:  unable to read partition table
Mar  3 13:28:01 linux kernel:  I/O error: dev 08:20, sector 0

Although the quantity and length of these messages are annoying, they appear
to be benign, at least with respect to ordinary printing operations. 
Scanning appears
to work reasonably well, although a full-blown 1200dpi scan is very, 
very slow.

I apologize for the length of this treatise, but perhaps others will be 
able to compare
their signs and symptoms to mine and find some useful clues.

I have avoided trying a 2.6 kernel because of the SuSE 9.0 warranty and to
avoid complications with possible side-effects of the newer giblets on old
kernels and other components. (I've done a LOT of testing on previous 
systems,
all the way back to the 1.1 series, so I'm not shy about it :-).

Thanks, and 73,

Bayard R. Coolidge, N1HO  (n1...@co...)

Re: [hpoj-devel] Adaptation ofHPOJ to kernel 2.6.x

[Till K. <til...@gm...>]

I have updated my patch on

http://www.linuxprinting.org/till/tmp/hpoj-0.91-kernel26.patch.bz2

The first version was not working correctly. Please apply this one on a 
clean HPOJ 0.91 source package.

    Till

P. S.: On the upcoming Mandrake Linux 10.0 Community Edition (in a few 
days) HPOJ seems to work fine with kernel 2.6.x and all supported devices.

Till Kamppeter wrote:
> Oi,
> 
> kernel 2.6.x has the module "usblp" for USB printers and not "printer" 
> any more. To make the "ptal-init" script compatible to both 2.4.x and 
> 2.6.x kernels I have made a patch. You can get it on
> 
> http://www.linuxprinting.org/till/tmp/hpoj-0.91-kernel26.patch.bz2
> 
>    Till
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> 
> _______________________________________________
> hpoj-devel mailing list
> hpo...@li...
> https://lists.sourceforge.net/lists/listinfo/hpoj-devel
> 
> 

Re: [hpoj-devel] Problem with hpoj /w SMP and USB?

[James B. H. <jh...@vi...>]

Hi.

Thanks for all the detail.  I hope others will jump in, because I'm not
real familiar with a lot of the things that you have, and I'm not at
all familiar with the track record of hpoj with the types of printers
you're using.  (Implied:  maybe there could be some problems with
those types of printers - is hpoj known to and intended to work ok
with LaserJets?)

> My software: SuSE Linux 9.0 installed on the workstation. No other operating 
> system besides that. Kernel: 2.4.21-99-smp4G. I guess the smp stands for 
> symmetric multi-processor. I don't know exactely what it means, but I guess, 
> it should work with a hyperthreading CPU.

Right.  SMP is Symmetric Multi Processing.  There's a very good, just a little
old, SMP-HOWTO for linux that is well worth the read.  It explains a lot
about the capability in its different flavors, ways to make use of it,
and a lot more.  It also has links to the Linux Parallel Processing HOWTO
and a few other very good docs, all of which you would likely enjoy.

The canonical URL for the SMP HOWTO is:

http://www.tldp.org/HOWTO/SMP-HOWTO.html

Note that there is a link to the maintainer's site, and in fact there is
a slightly newer, better version there.

The SMP HOWTO briefly mentions hyperthreading, as well as general hardware
issues across a number of platforms, so you may gain some insight as to
whether you have other latent issues to contend with.  But again, the
document is 18 months old, so you'll probably get better general info on
hyperthreading from other sources.

> So I read the troubleshooting guide and found the problem "I have 
> an SMP system, and I experience kernel OOPSes or complete system lockups when 
> using USB".

According to the original hpoj maintainer, David Paschal, the linux SMP/USB
bug was in principle fixed with the linux 2.6 series (which implies somewhere
in the 2.5 development series as well).  However, he didn't have the
opportunity to do comprehensive hpoj-related testing, so he couldn't attest
to the veracity of the fix or 2nd/3rd order regression.  Worth keeping
in mind.

He has also previously told me that there was never an issue with SMP and
parallel port hpoj, though on occasion someone would say, or imply, on
the list that they were having such troubles.  I know this myself to be
true, as I've been running hpoj/parallel port and an SMP box for a Very Long
Time (since before hpoj actually did anything) (both Intel and AMD flavors).
And also, though you didn't ask - the issue does not come up simply
because one has USB configured and running in an SMP kernel.  It's only when
you're attempting to use hpoj with USB that the problem manifests.  (I say
this because there has been traffic on the list from time to time asserting
otherwise, but those folks were misunderstanding the issue at the time).

Aside from all that - you'd probably benefit from upgrading the kernel if
you don't have other major dependencies on 2.4.21.  There might even be
some "improvement" in the SMP bug in the later 2.4-series kernels; I seem
to recall some assertions of that on this mailing list.  If I remember
right, it would be at least 2.4.23 to get to.  But I'll stress that I'm
not certain of the accuracy of this conjecture, so even better would be
to just go with latest (2.6.3, almost .4 now).

> I tried to reboot with the nosmp kermel option. This didn't work, the system 
> didn't boot with this option. (I wonder why). Then I disabled hyperthreading 
> in the BIOS setup. As a result, hpoj worked pretty fine. After I enabled 
> hyperthreading again in the BIOS setup, the system locked up again. So I 
> guess, I have the cited problem.

Seems like it.

> What can I do now (besides throwing away something)?

Rather than throwing anything away, you might consider just going with
parallel-port-only for the moment, either with the one parallel port
printer that you have, or even better, with that one and one borrowed
from a friend (and a $10 PCI parallel port card if you need one).
This way you could remove the USB issue from the mix and make sure you're
not having other problems not at all related to it (seems like you could
be).  Then you might be able to roll in hpoj with USB in a controlled
way and see what happens.

Hope some of this helps.

jbh

[hpoj-devel] Problem with hpoj /w SMP and USB?

[Dr. A. S. <And...@Dr...>]

Hi,

please excuse my asking you for help, but I am only a Linux user, not a Linux 
developer...

Probably I have a well known problem, but I don't know how to fix it. 

My hardware: Pretty new workstation with Intel Pention 4 with hyperthreading, 
mainboard D1688 from Fujitsu-Siemens with four USB Ports, Intel Chipset 875P.

One USB device is an ISDN modem, Teledat X120 of the German telecom. Another 
USB device is an HP LaserJet 3330. I also have an HP LaserJet 5MP connected 
to the parallel port.

My software: SuSE Linux 9.0 installed on the workstation. No other operating 
system besides that. Kernel: 2.4.21-99-smp4G. I guess the smp stands for 
symmetric multi-processor. I don't know exactely what it means, but I guess, 
it should work with a hyperthreading CPU.

The ISDN modem works without problems. If I configure printing with Yast2, it 
works fine with both printers. If I -- on the other hand -- install hpoj and 
use it, it completely locks up my system. Only switching the power off helps. 
This has already damaged my reiserFS so much, that I couldn't repair it. I 
had to install Linux from scratch again.

So I read the troubleshooting guide and found the problem "I have 
an SMP system, and I experience kernel OOPSes or complete system lockups when 
using USB".

I tried to reboot with the nosmp kermel option. This didn't work, the system 
didn't boot with this option. (I wonder why). Then I disabled hyperthreading 
in the BIOS setup. As a result, hpoj worked pretty fine. After I enabled 
hyperthreading again in the BIOS setup, the system locked up again. So I 
guess, I have the cited problem.

At that point I begin to need help. I built hpoj again from the sources with 
libusb support -- at least I think so. It didn't help, the problem even seems 
to be worse. But I don't know, whether I did that last thing right. libusb is 
installed on my system. I ran ./configure with the options --prefix=/usr 
--with-usb. 

But how do I know, that hpoj was built with libusb in this case? And how do I 
know, whether ptal-init setup detected this situation and enabled a 
workaround, as described in the troubleshooting giude? (I built hpoj while 
hyperthreading was enabled.) After rebuilding and reinstalling hpoj 
the system always(!) locked during bootup. I tried it three times. Each time 
the lockup occured at a differend step but I always had 
to switch off power. The system only came up again, after I disabled 
hyperthreading in the BIOS setup again.  Before rebuilding, this only happend 
once. Then the system only locked up if I tried to use the scanner.

What can I do now (besides throwing away something)?

Thanks in advance for any help,

yours sincerely

Andreas Schenk

[hpoj-devel] Re:Adaptation ofHPOJ to kernel 2.6.x

[Jeff <j....@ve...>]

I'm having the same problems as listed above.
ptal-init setup works sometimes, usually I have to pwr the printer on & off a few times b4 it works, some sample output.
When it doesn't work:
Probing "/dev/lp0"...  
    *** Found "photosmart 7900 series" but failed to communicate with it!
    *** Elapsed time for this attempt was 5 second(s).
    *** Check syslog file for ptal-mlcd error messages.
    *** See hpoj documentation for troubleshooting information.

Mar  Mar  1 06:38:17 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20
414, e=111, t=1078141097_        ptal-mlcd successfully initialized._
Mar  1 06:38:17 [ptal-mlcd] ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe>, pid=20
414, e=11, t=1078141097_        Couldn't find device!_

When it does:
Probing "/dev/lp0"...  
    Found "photosmart 7900 series"
    with serial number "CN3BJ310G7N8".

    This device will be set up as "mlc:usb:photosmart_7900_series".
    Press <Enter> alone to continue or <Ctrl-D> to skip this device, or
    enter a different desired name suffix (without the "mlc:usb:" prefix)
    here ---> 

    Setting up as "mlc:usb:photosmart_7900_series".
    Enabling ptal-mlcd and ptal-printd.
    Enabling ptal-photod.
Mar  1 06:46:10 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20836, e=2, t=1078141570_        
ptal-mlcd successfully initialized._
Mar  1 06:46:10 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20843, e=111, t=1078141570_      
  ptal-mlcd successfully initialized._
Mar  1 06:46:11 [ptal-mlcd] SYSLOG at /var/tmp/portage/hpoj-0.91-r2/work/hpoj-0.91/mlcd/ExMgr.h:646, dev=<mlc:u
sb:probe@/dev/lp0>, pid=20843, e=11, t=1078141571_        ptal-mlcd successfully activated, mode=1284.4._
Mar  1 06:46:15 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20859, e=111, t=1078141575_      
  ptal-mlcd successfully initialized._
Mar  1 06:46:15 [ptal-mlcd] ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe>, pid=20859, e=11, t=1078141575_       
 Couldn't find device!_
Mar  1 06:46:15 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20868, e=111, t=1078141575_      
  ptal-mlcd successfully initialized._
Mar  1 06:46:15 [ptal-mlcd] ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe>, pid=20868, e=11, t=1078141575_       
 Couldn't find device!_
Mar  1 06:46:15 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20877, e=111, t=1078141575_      
  ptal-mlcd successfully initialized._
Mar  1 06:46:15 [ptal-mlcd] ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe>, pid=20877, e=11, t=1078141575_       
 Couldn't find device!_
Mar  1 06:46:15 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20886, e=111, t=1078141575_      
  ptal-mlcd successfully initialized._
Mar  1 06:46:15 [ptal-mlcd] ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe>, pid=20886, e=16, t=1078141575_       
 Couldn't find device!_
Mar  1 06:46:15 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20895, e=111, t=1078141575_      
  ptal-mlcd successfully initialized._
Mar  1 06:46:15 [ptal-mlcd] ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe>, pid=20895, e=11, t=1078141575_       
 Couldn't find device!_
Mar  1 06:46:15 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:probe>, pid=20904, e=111, t=1078141575_      
  ptal-mlcd successfully initialized._
Mar  1 06:46:15 [ptal-mlcd] ERROR at ExMgr.cpp:2525, dev=<mlc:usb:probe>, pid=20904, e=11, t=1078141575_       
 Couldn't find device!_
Mar  1 06:46:18 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:photosmart_7900_series>, pid=20919, e=2, t=10
78141578_        ptal-mlcd successfully initialized._
Mar  1 06:46:18 [ptal-printd] ptal-printd(mlc:usb:photosmart_7900_series) successfully initialized using /var/r
un/ptal-printd/mlc_usb_photosmart_7900_series*._
Mar  1 06:46:20 [ptal-photod] ptal-photod(mlc:usb:photosmart_7900_series) successfully initialized, listening o
n port 5703._

ptal-init start:
Mar  1 06:51:12 [ptal-mlcd] SYSLOG at ExMgr.cpp:652, dev=<mlc:usb:photosmart_7900_series>,
 pid=20955, e=2, t=1078141872_        ptal-mlcd successfully initialized._
Mar  1 06:51:12 [ptal-printd] ptal-printd(mlc:usb:photosmart_7900_series) successfully ini
tialized using /var/run/ptal-printd/mlc_usb_photosmart_7900_series*._
Mar  1 06:51:14 [ptal-photod] ptal-photod(mlc:usb:photosmart_7900_series) successfully ini
tialized, listening on port 5703._

cupsd start:
root@Genbox init.d # ./cupsd start
 * Starting cupsd...

ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:251, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142036
Command reply timeout on port=0, count=1, lastRequest=0x00!

ptal-mlcd: ERROR at ExMgr.cpp:871, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142036
exClose(reason=0x3002)

When trying to setup printer in cups in the device screen: PTAL device not found

Some other info:
root@Genbox everything # ptal-devid

ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:251, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142397
Command reply timeout on port=0, count=1, lastRequest=0x00!

ptal-mlcd: ERROR at ExMgr.cpp:871, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142397
exClose(reason=0x3002)
ptal-devid: Failed to retrieve device ID string for device "mlc:usb:photosmart_7900_series"!

root@Genbox everything # ptal-print </dev/null
ptal-print: connecting to device "mlc:usb:photosmart_7900_series"...  
ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:251, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142448
Command reply timeout on port=0, count=1, lastRequest=0x00!

ptal-mlcd: ERROR at ExMgr.cpp:871, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142448
exClose(reason=0x3002)

ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:251, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142453
Command reply timeout on port=0, count=1, lastRequest=0x00!

ptal-mlcd: ERROR at ExMgr.cpp:871, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142453
exClose(reason=0x3002)
failed!

root@Genbox everything # ptal-connect -service ECHO
ptal-connect: connecting to device "mlc:usb:photosmart_7900_series"...  
ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:251, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142518
Command reply timeout on port=0, count=1, lastRequest=0x00!

ptal-mlcd: ERROR at ExMgr.cpp:871, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142518
exClose(reason=0x3002)

ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:251, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142524
Command reply timeout on port=0, count=1, lastRequest=0x00!

ptal-mlcd: ERROR at ExMgr.cpp:871, dev=<mlc:usb:photosmart_7900_series@/dev/lp0>, pid=20955, e=2, t=1078142524
exClose(reason=0x3002)
failed!

root@Genbox everything # lsmod
Module                  Size  Used by
sd_mod                 11168  0 
hid                    22912  0 
usb_storage            26176  0 
scsi_mod               64172  2 sd_mod,usb_storage
usblp                  10880  0 
emu10k1_gp              2496  0 
gameport                3584  1 emu10k1_gp
ehci_hcd               22468  0 
ohci_hcd               15936  0 
evdev                   7680  0 
usbcore                94556  7 hid,usb_storage,usblp,ehci_hcd,ohci_hcd

root@Genbox everything # lsusb
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 002: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 005: ID 03f0:b602 Hewlett-Packard 
Bus 001 Device 003: ID 04cc:1122 Philips Semiconductors Hub
Bus 001 Device 001: ID 0000:0000

Dump:
ExMgr:
pid=20955
gDebugFlag=0
pBufferPool: available#=0, size=4102, requested#=390, allocated#=1
noFork=0
noDrain=0
forceMlcDot4=0
noDot4=0
noMlc=0
noPmlMultiplexing=0
initialized=1
fd=5: read=1, write=0
fd=8: read=1, write=0
fdCount=9
exContext=2
exState=0
exActivateCount=6
exCloseCount=6
exCloseReason=0x3002
tryDot4=1
tryMlc=1
transportMode=0=print-only
miser=0
argcOriginal=9
argvOriginal:  "mlc:usb:photosmart_7900_series" "-devidmatch" "MDL:photosmart 7900 series;" "-devidmatch" "SN:CN3BJ310G7N8;" "-device" "/dev/usb/lp[0-9]*" "/dev/usblp[0-9]*" "/dev/lp[0-9]*"
argc=0
fdNull=4
pFreeMsgPool: depth=1
pPendingMsgQueue: depth=0
pActiveTimerQueue: depth=0
pPeriodicTimerQueue: depth=0
select timeout: sec=0, usec=0, infinite=1
consoleAllowRemote=0
consoleOldStdin=6
consoleOldStdout=7
consoleIsRemote=0
socketSuffix=<usb:photosmart_7900_series>
socketName=</var/run/ptal-mlcd/usb:photosmart_7900_series>
socketFd=5
pmlTransportSession=8
pmlCurrentSession=-1
pmlLastSession=31
llioPossibleName[0]=</dev/usb/lp[0-9]*>
llioPossibleName[1]=</dev/usblp[0-9]*>
llioPossibleName[2]=</dev/lp[0-9]*>
llioPossibleNameCount=3
llioName=<>
llioGlobBuffer.gl_pathc=7
llioGlobBuffer.gl_offs=0
llioGlobFlags=32
llioMatchDeviceID[0]=<MDL:photosmart 7900 series;>
llioMatchDeviceID[1]=<SN:CN3BJ310G7N8;>
llioMatchDeviceIDCount=2
llioInterface[EX_INTERFACE_MLC].pForwardBdrQueue: depth=0
llioInterface[EX_INTERFACE_MLC].active=1
llioInterface[EX_INTERFACE_MLC].transportState=1
llioInterface[EX_INTERFACE_MLC].fdPipe.read=-1
llioInterface[EX_INTERFACE_MLC].fdPipe.write=-1
llioInterface[EX_INTERFACE_MLC].fdDevice=-1
llioInterface[EX_INTERFACE_MLC].overrideMaxForwardPacketSize=0
llioInterface[EX_INTERFACE_MLC].pid=-1
llioInterface[EX_INTERFACE_PRINT].pForwardBdrQueue: depth=0
llioInterface[EX_INTERFACE_PRINT].active=0
llioInterface[EX_INTERFACE_PRINT].transportState=0
llioInterface[EX_INTERFACE_PRINT].fdPipe.read=-1
llioInterface[EX_INTERFACE_PRINT].fdPipe.write=-1
llioInterface[EX_INTERFACE_PRINT].fdDevice=-1
llioInterface[EX_INTERFACE_PRINT].overrideMaxForwardPacketSize=0
llioInterface[EX_INTERFACE_PRINT].pid=-1
llioEnablePrintInterface=1
llioDeviceID=<>
llioSavedDeviceID=<MFG:hp;MDL:photosmart 7900 series;CMD:MLC,PCL,PML,DW-PCL,DESKJET,DYN;CLS:PRINTER;DES:7960;SN:CN3BJ310G7N8;S:0380088084001021003c148004dc250004ac3580053;J:                    ;Z:0102;>
llioMatchVendorID=0xFFFFFFFF
llioMatchProductID=0xFFFFFFFF
llioAllowComposite=1
llioGlobUsb=1
llioAllowChannelChangeRequest=1
llioBusAddress=1
llioDeviceAddress=5
llioVendorID=0x03F0
llioProductID=0xB602
llioSupportedProtocols=0x04
llioCurrentProtocol=2
llioDesiredProtocol=2

Passthrough transport:
this=0x08074338
port=0
pMgr=0x08071050
pPhysicalPort=0x08071050
forwardTransactionCounter: current=128, initial=128, low=128, high=128, max=128
channelCount=1
channelArray=0x08074418
channelArray[0]=0x08074428
overheadBufferCount=0
pNextTransport=0x00000000
pForwardDataTimer=0x080743D8 (count=0)
pForwardDataTimeoutMsg=0x080743A8
reverseDataBufferCount=0
reverseDataBufferSize=0
maxForwardBdrsPerTransaction=0
nextChannelToAllocate=0
absoluteMaxForwardDatalen=0
absoluteMaxReverseDatalen=0
nextBlockedChannel=-1
lookupQueue: depth=0, peek=0x00000000

MLC/1284.4 transport:
this=0x08071DF8
port=0
pMgr=0x08071050
pPhysicalPort=0x08071050
forwardTransactionCounter: current=128, initial=128, low=127, high=128, max=128
channelCount=17
channelArray=0x08071FF0
channelArray[0]=0x08072038
channelArray[1]=0x08072338
channelArray[2]=0x08072538
channelArray[3]=0x08072738
channelArray[4]=0x08072938
channelArray[5]=0x08072B38
channelArray[6]=0x08072D38
channelArray[7]=0x08072F38
channelArray[8]=0x08073138
channelArray[9]=0x08073338
channelArray[10]=0x08073538
channelArray[11]=0x08073738
channelArray[12]=0x08073938
channelArray[13]=0x08073B38
channelArray[14]=0x08073D38
channelArray[15]=0x08073F38
channelArray[16]=0x08074138
overheadBufferCount=0
pNextTransport=0x08074338
pForwardDataTimer=0x08071EC8 (count=0)
pForwardDataTimeoutMsg=0x08071E98
reverseDataBufferCount=340
reverseDataBufferSize=4102
maxForwardBdrsPerTransaction=4
nextChannelToAllocate=1
absoluteMaxForwardDatalen=-6
absoluteMaxReverseDatalen=-6
nextBlockedChannel=-1
lookupQueue: depth=0, peek=0x00000000
----------------
pForwardHeaderPool=0x08071F08
mlcChannelArray=0x08071FF0
pCommandChannel=0x08072038
grcState=0
reverseDataStopped=0
tryDot4=1
tryPreDot4=0
tryMlc=1
requestedRevision=0x20
revision=0xFFFF
maxRemoteSockets=32

Command channel:
this=0x08072038
port=0
channel=0
localSocket=0
pTransport=0x08071DF8
pMgr=0x08071050
pPhysicalPort=0x08071050
openingAnySetFlags=0x0010
closingAnySetFlags=0x0124
flags=0x0000
countOpen=0
countOpenFailure=0
pService=0x00000000
scd=0x00000000
forwardDataPriority=0
minBuffersRequired=0
benefitOfMoreBuffers=0
reverseDataBufferSize=4102
bufferCount=3
remoteSocket=0
maxForwardDatalen=58
maxReverseDatalen=58
countForwardData=1
countReverseData=0
countReverseBuffers=0
countReverseBufferReturns=0
lastReverseBuffer=0x00000000
currentForwardBuffer=0x00000000
currentGrabbedCredit=-1
currentGrabbedTransaction=-1
----------------
pMlcTransport=0x08071DF8
pCommandChannel=0x08072038
disableCreditCommands=1
pForwardCreditRequestTimer=0x080721D8
pForwardCreditRequestMsg=0x080721A8
pReverseCreditHeartbeatTimer=0x08072240
pReverseCreditHeartbeatMsg=0x08072210
musherFirstCreditRequestDelay=2
musherNextCreditRequestDelay=5
gusherFirstCreditRequestDelay=5
gusherNextCreditRequestDelay=10
miserFirstCreditRequestDelay=0
miserNextCreditRequestDelay=2
gusherPiggybackCreditCount=1
gusherCreditCount=2
miserCreditRequestCount=2
workaroundReverseCreditLoss=0
maxForwardPacketSize=64
maxReversePacketSize=64
forwardCreditRequest=16
forwardMaxOutstandingCredit=1
forwardCredit: current=0, initial=0, low=0, high=0, max=65535
lastCreditRequestGotUsNowhere=0
reverseMaxOutstandingCredit=1
reverseBuffersPerPacket=1
uncreditedBuffers=0
reverseCreditToGrant=2
reverseCredit: current=1, initial=1, low=1, high=1, max=65535
countSendPiggybackCredit=1
countHandlePiggybackCredit=0
countSendCredit=0
countHandleCredit=0
countHandleCreditAfterCreditRequest=0
countSendCreditRequest=0
countHandleCreditRequest=0
countSendEmptyCreditRequestReply=0
countHandleEmptyCreditRequestReply=0
isGusher=-1
----------------
pForwardCommandPool=0x08072278
pForwardNonconsumingQueue=0x08072298
pForwardReplyQueue=0x080722A8
pForwardRequestQueue=0x080722B8
forwardRequestCredit: current=0, initial=0, low=0, high=0, max=65535
pCommandReplyTimer=0x080722F8 (count=0)
pCommandReplyTimeoutMsg=0x080722C8
allowErrorPackets=1
lastRequest=0x00
lastPsid=-1
lastSsid=-1

Session 0: type=command
	state=1
	fd=8
	scdlink=-1
	pLookup=0x080718D0
	outstandingForwardBdrCount=1
	pReverseBdrQueue: depth=0
	tcd=0x00000000
	pCommandBdr=0x080766C0
	pmlTrapsRegistered=0
	bitbucketSocket=0

Sorry for the length of this, just trying to give someone all the info.
Have tried with 2.6.2-vanilla, 2.6.3-vanilla & 2.6.3-mm4 kernel sources.
HPOJ is 0.91 with libusb support and yes, I've tried the patch.
So right now I'm looking at an expensive paper weight.........

[hpoj-devel] OfficeJet T65 + Debian SID

[Erik <tra...@xs...>]

I'm having an incredible amount of trouble trying to get the OfficeJet
T65 to work in debian. I have intalled what I believe to be all the
neccessary files (hpoj, hpij, cupsys-client...) and can "see" the
printer via the ptal interface via either "ptal-init setup" or lpinfo
-v. The print does show up in CUPS and I have set it up using the ptal
interface and not the direct link to /dev/lp0. 

I feel as if the printer is hanging on every request because the scripts
such as HPIJS and ptal-printd remain open along with foomatic-bin. These
programs remain until I kill them. 

Any help at all would be of great help... The printer worked wonderful
in Redhat 9 and Fedora Core 1, but I grew increasingly tired of RH and
now I love all my debian systems dearly. Please do not make me revert
back!

Thanks in advance,
Erik