hpoj-devel — HPOJ development/support list

Re: [hpoj-devel] (Unofficial patch) 2nd patch to hpoj for 2.4

[DG <dg...@um...>]

From: Burkhard Kohl <bu...@bu...>
>DG
>> >BTW, there is still another problem with the kernel drivers which causes
>> >more-or-less random lockups of the client process, for example, when
doing
>> >a large scan.  If you're able to do anything about that or even just
have
>> >any ideas on what could be causing it, it would be much appreciated too.
>> :-)
>>
>> I've spent a little time reaquainting myself with the code, and I think I
>> can take a shot at this.  Fortunately (maybe), it hangs reliably with
>> debugging turned on, suggesting a timing issue (interrupt scheduling
>> conflicts maybe?).
>Are we talking about the driver compiled under 2.2 or 2.4?
>I know we have a timing issue under 2.4 and I hope it is related
>to changes in the underlying parport layer.

Compiled under 2.2.17 to be exact.  I haven't tried other kernels.

>Under 2.4 the driver becomes somehow  sluggish without debugging
>turned on (sic!) - which means that the overall reaction becomes
>faster if some loops slow down.

--
Burkhard Kohl			buk at/auf buks.ipn.de
_______________________________________________
hpoj-devel mailing list
hpo...@li...
http://lists.sourceforge.net/mailman/listinfo/hpoj-devel

--
Daniel
ZZZ-dgun-ZZZ-@-ZZZ-umpire.com-ZZZ
(Remove the Z-'s to reply)
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup

Re: [hpoj-devel] Re:[Patch v2] hpoj now running with 2.4 kernel

[damcha <da...@cy...>]

Hello,

On lun, 02 oct 2000 16:42:44 Alexander Zimmermann wrote:
> 3) 2.4.0-SMP
>    kernel modules compile, but there're unresolved symbols when loading
>    them and I don't know which module to install instead of
>    parport_probe.


Could you list the symbols which are not resolved ?

Damcha
-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+) s: a-- C++ UL+++ P+>++ L+++ E(+) W++ N+ o? K- w-- O? M V?
PS++ PE- Y+ PGP t+ 5 X++ R(+) tv-(+) b+ DI D++ G e+++ h--- r++ y+++*
------END GEEK CODE BLOCK------
					 See http://www.geekcode.com

[hpoj-devel] Re:[Patch v2] hpoj now running with 2.4 kernel

[Alexander Z. <Ale...@fm...>]

Hello,

On 25 Sep, damcha wrote:
> Here is the patch which includes both Burkhard's and mine.
> It now compile on 2.4.0-test9. Please report comments in the ML.
> 

I applied this patch to hpoj-0.6, but still have problems:

1) 2.2.16-UP
   works fine (but only on one CPU).

2) 2.2.16-SMP
   kernel still crashes during  hpo devid  .

3) 2.4.0-SMP
   kernel modules compile, but there're unresolved symbols when loading
   them and I don't know which module to install instead of
   parport_probe.

Any help wellcome!

Of course I'm able and willing to make some tests if someone tells me
what and how.
-- 
Ale...@fm... / Seize the day, put no trust in 
http://www.fmi.uni-passau.de/~zimmerma/ the morrow!   -- Quintus
for PGP public key finger            / Horatius Flaccus (Horace) 
zim...@yo...     / 

Re: [hpoj-devel] Stuck...

[Tom <trh...@su...>]

My Bad,

After I straced the call, I realized I hadn't done the insmod steps
(thinking they were performed automagically after the first time).

Scanning works!   Yeah.   Me happy, me go sleep now!

Tom

Re: [hpoj-devel] Stuck...

[<pa...@rc...>]

trh...@su... said:
> Any ideas?  I'm running on a Mondrake system (~RedHat) kernel
> 2.2.14-15mdk, the HPOJ is hooked up to the parallel port (BTE is there
> anything special needed to use the USB?), printing works fine. 

Sorry, I forgot to address this paragraph.  That's strange that printing
works but scanning doesn't.  Are you sure you aren't printing through
/dev/lp0 instead of ieee12844_print (or ptal-print)?

USB isn't supported at the moment, but I'm looking into it.

David

Re: [hpoj-devel] Stuck...

[<pa...@rc...>]

> I did try to faithfully follow the SCAN_HOWTO, and things make just
> fine.  However, when I try scanimage --test I get:
> 
> % scanimage --test
> ptalMlcChannelOpen(chan=0x08052C48): error creating socket!
> ptalChannelOpen(chan=0x08052C48): provider failed open!
> scanimage: no SANE devices found

Hi, Tom.  Did you remember to insmod parport, parport_pc, parport_probe,
ieee12844.o ieee12844pp.o?  Use the "lsmod" command to be sure.  See the
"INSTALL" file for more details.

David

[hpoj-devel] Stuck...

[Tom <trh...@su...>]

Hi there,

I finally got my (clunky) OfficeJet G85!

I did try to faithfully follow the SCAN_HOWTO, and things make just
fine.  However, when I try scanimage --test I get:

% scanimage --test
ptalMlcChannelOpen(chan=0x08052C48): error creating socket!
ptalChannelOpen(chan=0x08052C48): provider failed open!
scanimage: no SANE devices found

% scanimage -d hp:mlc:mlcpp0 --test
ptalMlcChannelOpen(chan=0x08052C48): error creating socket!
ptalChannelOpen(chan=0x08052C48): provider failed open!
ptalMlcChannelOpen(chan=0x08052C48): error creating socket!
ptalChannelOpen(chan=0x08052C48): provider failed open!
scanimage: open of device hp:mlc:mlcpp0 failed: Error during device I/O

And with debugging turned on:
% scanimage -d hp:mlc:mlcpp0 --test
[sanei_debug] Setting debug level of hp to 128.
[hp] sane_init called
ptalInit(): debug level set to 2.
ptalInit()
ptalDeviceProbe: dev=<mlc:mlcpp0>.
ptalDeviceAdd(provider=<mlc>,name=<mlcpp0>): dev=0x0804EB40.
ptalDeviceProbe: dev=<mlc:mlcpp1>.
ptalDeviceAdd(provider=<mlc>,name=<mlcpp1>): dev=0x0804EB78.
[hp] sane_init will finish with Success
[hp] sane_open called
[hp] hp_read_config: hp backend v0.91 starts reading config file
[hp] hp_read_config: processing line <mlc:mlcpp0>
[hp] hp_read_config: processing line <option connect-ptal>
[hp] hp_read_config: attach mlc:mlcpp0
[hp] hp_get_dev: New device mlc:mlcpp0, connect-ptal, scsi-request=0
ptalMlcDeviceOpen(name=<mlcpp0>): found matching dev=0x0804EB40.
ptalChannelAllocate(dev=0x0804EB40): chan=0x08052C48.
ptalChannelSetRemoteService(chan=0x08052C48,serviceType=2,socketID=0,serviceName=<>)

[hp] scsi_flush: writing 2 bytes:
[hp]  0x0000  1B 45                                            .E
ptalMlcChannelOpen(chan=0x08052C48): error creating socket!
ptalChannelOpen(chan=0x08052C48): provider failed open!
[hp] hp_nonscsi_device_new: SCL reset failed
[hp] scsi_close: closing fd -1
ptalChannelClose(chan=0x08052C48)
ptalChannelClose(chan=0x08052C48): not open!
[hp] hp_get_dev: New device mlc:mlcpp0, connect-ptal, scsi-request=0
ptalMlcDeviceOpen(name=<mlcpp0>): found matching dev=0x0804EB40.
[hp] scsi_flush: writing 2 bytes:
[hp]  0x0000  1B 45                                            .E
ptalMlcChannelOpen(chan=0x08052C48): error creating socket!
ptalChannelOpen(chan=0x08052C48): provider failed open!
[hp] hp_nonscsi_device_new: SCL reset failed
[hp] scsi_close: closing fd -1
ptalChannelClose(chan=0x08052C48)
ptalChannelClose(chan=0x08052C48): not open!
scanimage: open of device hp:mlc:mlcpp0 failed: Error during device I/O
[hp] sane_exit called
[hp] sane_exit will finish

Any ideas?  I'm running on a Mondrake system (~RedHat) kernel
2.2.14-15mdk, the HPOJ is hooked up to the parallel port (BTE is there
anything special needed to use the USB?), printing works fine.

Tom

[hpoj-devel] Re: Problem

[B. H. R. <bh...@ma...>]

I have done a little more research on the problem and when I trace through 
the source of ptal-connect using the options mlc:mlcpp0 -scan my computer 
locks up on line 174  of ptal-mlc.c.  Hope this helps.

Thanks,
Heath Robinson

On Thu, 28 Sep 2000, I wrote:
> I am having trouble with connecting to my PSC 500.  When I run any of the
> apps or sane, my computer freezes.  the modules load fine, and report the
> correct information when I do hpoj devid, but if I do anything else I can
> do nothing else, but press the reset button.
>
> BTW, thanks a lot for your work on this driver.  My Win2K doesn't work with
> this now either.  I figured I'd come closer to having support with it, but
> I guessed wrong.

Re: [hpoj-devel] (Unofficial patch) 2nd patch to hpoj for 2.4

[Burkhard K. <bu...@bu...>]

DG
> >BTW, there is still another problem with the kernel drivers which causes
> >more-or-less random lockups of the client process, for example, when doing
> >a large scan.  If you're able to do anything about that or even just have
> >any ideas on what could be causing it, it would be much appreciated too. 
> :-)
> 
> I've spent a little time reaquainting myself with the code, and I think I
> can take a shot at this.  Fortunately (maybe), it hangs reliably with
> debugging turned on, suggesting a timing issue (interrupt scheduling
> conflicts maybe?).
Are we talking about the driver compiled under 2.2 or 2.4?
I know we have a timing issue under 2.4 and I hope it is related 
to changes in the underlying parport layer. 

Under 2.4 the driver becomes somehow  sluggish without debugging 
turned on (sic!) - which means that the overall reaction becomes
faster if some loops slow down.

-- 
Burkhard Kohl			buk at/auf buks.ipn.de

Re: [hpoj-devel] (Unofficial patch) 2nd patch to hpoj for 2.4

[DG <dg...@um...>]

From: pa...@rc... (David Paschal)
> > I want to start with a small scan like maybe 'scanimage --test', but I
don't
> > know how the protocol works.  How can I find out what the data exchange
> > should look like between the driver and scanner during a scan? 
Something
> > like a step-by-step explanation would be best.  A dump of the incoming
and
> > outgoing data would also help.  Then I can compare what I'm getting with
> > what I should be getting and hopefully find out where the error is
creeping
> > in.
>
> Hi, Daniel.  There is a little section at the end of SCAN-HOWTO telling
how
> to turn on debug output for the SANE HP backend and for PTAL:
> >        export SANE_DEBUG_HP=128
> >        export PTAL_DEBUG=2
> You'll probably want to have HP's SCL documentation handy (available from
> http://www.hp-developer-solutions.com, free registration required).  If
you
> want you can e-mail the output to me (pa...@rc..., not the mailing
> list) and I'll take a look at it too.
>
> After I wrote that last paragraph I re-read your question and realized I
> didn't answer it.  :-)  It sounds like you're wanting debug output from
> some successful runs.  "scanimage --test" may work OK for you (try it and
> let me know if even that gives you trouble).  Let me know exactly what
> operations you want debug output for and I'll send it to you.

Yes, that's what I want.  Rather than 'scanimage --test', I'll start with
something simpler.  Using the 'ptal-connect -scan' command, what are the PCL
commands to scan a single line?  I'll start there and then move up to
'scanimage --test' when I (hopefully) figure out how the ptal commands are
handled by the ieee12844 modules.

--
Daniel
ZZZ-dgun-ZZZ-@-ZZZ-umpire.com-ZZZ
(Remove the Z-'s to reply)
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup

Re: [hpoj-devel] Printing in RedHat Was: (no subject)

[Joe P. <joe...@sn...>]

I'm reposting this because it didn't make it onto the
list for some reason. My apologies if it appears twice.
Joe
--------

On Tue, 26 Sep 2000, Erik Hendrix wrote:

> My understanding was that I needed apsfilter and a2ps to be able to make 
> this work. This is the only reason why I installed it.
> 

> I'm running Red Hat 6.2 and currently nothing is modified of that version. 
> My printer deamon is up and running.
> 

Erik:

I've only done some testing on the driver and haven't used it regularly. I'm
working on a potential GUI for the project, but that is different from the
inner workings of the driver. Chances are, a much better coder will need to
take over the GUI development later anyway.

Today I tested the driver some more on my RedHat 6.1 desktop system. It seems
to work the way I have it set up, but since I've done minimal testing, I could
be wrong.

From what the developers have said, it seems that the purpose of the driver is
only to add increased functionality and controllability to the officejet, while
simply throughputting the ghostscript-generated print data.

The driver is undergoing active development, and is improving steadily, but it
isn't yet finished.

Here is how my RH 6.1 system is set up, if you want to try copying it:

Basically, I'm not using apsfilter or a2ps, just a regular ghostscript driver
with "wrapfilter" in its spool directory. I had an earlier driver setup that
did  not involve using the hpoj driver. I still have that, plus a new, similar
driver setup for use with the hpoj driver. 

In printtool, I set up a regular ghostscript color print driver, with gamma
correction added via "gamma.ps" because the printing was too dark using only
the gs driver. This should be tested to see if it works as expected. The hpoj
driver is not involved in this first "driver" setup. The printcap entry is
below, as added by printtool.

Note: restart lpd after changes to printtool or printcap entries.

##PRINTTOOL3## LOCAL cdj550 300x300 letter {} DeskJet550 32 1
HPofficejet|officejet|ojet|oj:\
 :sd=/var/spool/lpd/HPofficejet:\
 :mx#0:\
 :lp=/dev/lp0:\
 :if=/var/spool/lpd/HPofficejet/filter:\
 :sh:                            

I then made a copy of the same "driver" with printtool, but with different
printer name(s), and a different spool directory. It's necessary to have a
separate spool dir for each printtool driver entry. The default spool dir is
usually "lp0" but that should be changed to be more descriptive of the driver
being used. In printtool, I called that "HPOJ_DRVR". This should also be tested
to see if it works the same as the other driver.

I later (carefully) hand edited  /etc/printcap to change the :if= line to
change 'filter' to 'wrapfilter'.

##PRINTTOOL3## LOCAL
HPOJ_DRVR:\
 :sd=/var/spool/lpd/HPOJ_DRVR:\
 :mx#0:\
 :lp=/dev/lp0:\
 :if=/var/spool/lpd/HPOJ_DRVR/wrapfilter:\
 :sh:                                    


In the /var/spool/lpd directory there is now a subdir named HPOJ_DRVR where the
necessary files for the ghostscript print driver are kept. This is where I added
the wrapfilter. I had to change the QUEDIR line in wrapfilter to correspond to
the new spool directory. 

#!/bin/sh
# filename: /var/spool/lpd/HPOJ_DRVR/wrapfilter
#
QUEUEDIR=/var/spool/lpd/HPOJ_DRVR
IEEE12844DIR=/usr/local/bin
#
${QUEUEDIR}/filter "$@" | ${IEEE12844DIR}/ieee12844_print
#

I'm able to print color and text web pages with this in Netscape.

All of the necessary kernel modules have to be insmodded for this to work.

-----
Joe  

RE: [hpoj-devel] Problem

[PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...>]

Hi, Heath.  What kernel version are you running, and what kind of machine
are you running this on?  There are known bugs with kernel 2.3/2.4 and with
SMP machines, which are being worked on.

There is another bug that in some cases causes an individual process (for
example, SANE) to lock up, but not the whole computer, so that may not be
what's happening to you.  Some people have reported an easier time
reproducing this problem than others.

Hang in there; we're working on it.  :-)  In the meantime, if you happen to
have a JetDirect 70X, 170X, 300X, or 500X handy you could put your PSC 500
on that, because that connection method bypasses the kernel-mode drivers
that have the above-mentioned bugs.

David

> -----Original Message-----
> From: B. Heath Robinson [mailto:bh...@ma...]
> Sent: Thursday, September 28, 2000 10:07 AM
> To: hpo...@li...
> Subject: [hpoj-devel] Problem
> 
> 
> I am having trouble with connecting to my PSC 500.  When I 
> run any of the 
> apps or sane, my computer freezes.  the modules load fine, 
> and report the 
> correct information when I do hpoj devid, but if I do 
> anything else I can do 
> nothing else, but press the reset button.
> 
> BTW, thanks a lot for your work on this driver.  My Win2K 
> doesn't work with 
> this now either.  I figured I'd come closer to having support 
> with it, but I 
> guessed wrong.

[hpoj-devel] Problem

[B. H. R. <bh...@ma...>]

I am having trouble with connecting to my PSC 500.  When I run any of the 
apps or sane, my computer freezes.  the modules load fine, and report the 
correct information when I do hpoj devid, but if I do anything else I can do 
nothing else, but press the reset button.

BTW, thanks a lot for your work on this driver.  My Win2K doesn't work with 
this now either.  I figured I'd come closer to having support with it, but I 
guessed wrong.

Re: [hpoj-devel] 2.4.0 kernel issues

[Burkhard K. <bu...@bu...>]

David Paschal
> Hi, Burkhard.
> 
> > BTW: in ieee12844/Makefile.in the "cp" expression to move kernel
> > modules to the appropriate location was commented out. Was this
> > done for any particular purpose? I am asking because it meant
> > that the modules had to be installed by hand.
> That part is left over from the previous maintainers.  The new
> "make install" I added to the top-level directory doesn't even invoke
> makefiles in subdirectories.  By default, it installs the modules under
> /usr/local/lib, which doesn't help make it accessible to modprobe.
> Based on John Chmielewski's message from September 13, it sounds like it
> could be moved to (or possibly symlinked in) /lib/modules/misc, but there's
> still the problem that modprobe doesn't detect that ieee12844pp.o depends
> on parport_probe, not just parport and parport_pc.  My idea was to add a
> dummy function in ieee12844pp.c which never got called but which made a
> reference to a function in parport_probe (for example, parport_probe()).
> Since you're working on this code at the moment could you try this out and
> let me know if it fixes the problem (or I can try it myself later).
parport_probe no longer exist in the 2.4 kernel, so there it will 
be some other candidate. This issue should be resolved with the use 
of the new parport_driver_register interface. So it will be a mixed
(kernel version dependant) solution.

Burkhard
-- 
Burkhard Kohl			bu...@bu...

Re: [hpoj-devel] (no subject)

[Joe P. <joe...@sn...>]

On Tue, 26 Sep 2000, Erik Hendrix wrote:

> My understanding was that I needed apsfilter and a2ps to be able to make 
> this work. This is the only reason why I installed it.
> 

> I'm running Red Hat 6.2 and currently nothing is modified of that version. 
> My printer deamon is up and running.
> 

Erik:

I've only done some testing on the driver and haven't used it regularly. I'm
working on a potential GUI for the project, but that is different from the
inner workings of the driver. Chances are, a much better coder will need to
take over the GUI development later anyway.

Today I tested the driver some more on my RedHat 6.1 desktop system. It seems
to work, but since I've done minimal testing, I could be wrong.

From what the developers have said, it seems that the purpose of the driver is
only to add increased functionality and controllability to the officejet, while
simply throughputting the ghostscript-generated print data. The driver is
undergoing active development, so you need to decide whether you should
make it available for general use.

Here is how my system is set up, if you want to try copying it:

Basically, I'm not using apsfilter or a2ps, just a regular ghostscript driver
with "wrapfilter" in its spool directory. I had an earlier driver setup that
did  not involve using the hpoj driver. I still have that, plus a new, similar
driver setup for use with the hpoj driver. 

In printtool, I set up a regular ghostscript color print driver, with gamma
correction added via "gamma.ps" because the printing was too dark using only
the gs driver. This should be tested to see if it works as expected. The hpoj
driver is not involved in this first "driver" setup.

##PRINTTOOL3## LOCAL cdj550 300x300 letter {} DeskJet550 32 1
HPofficejet|officejet|ojet|oj:\
        :sd=/var/spool/lpd/HPofficejet:\
        :mx#0:\
        :lp=/dev/lp0:\
        :if=/var/spool/lpd/HPofficejet/filter:\
        :sh:                            

I then made a copy of the same "driver" with printtool, but with different
printer names, and a different spool directory. It's necessary to have a
separate spool dir for each printtool driver entry. The default spool dir is
usually "lp0" but that should be changed to be more descriptive of the driver
being used. In printtool, I called that "HPOJ_DRVR".

##PRINTTOOL3## LOCAL
HPOJ_DRVR:\
        :sd=/var/spool/lpd/HPOJ_DRVR:\
        :mx#0:\
        :lp=/dev/lp0:\
        :if=/var/spool/lpd/HPOJ_DRVR/wrapfilter:\
        :sh:                                    


In the /var/spool/lpd directory there is now a subdir named HPOJ_DRVR where the
necessary files for the hpoj print driver are kept. This is where I added the
wrapfilter. I had to change the QUEDIR line in wrapfilter because of the new
spool directory.

 #!/bin/sh
# filename: /var/spool/lpd/HPOJ_DRVR/wrapfilter
 
QUEUEDIR=/var/spool/lpd/HPOJ_DRVR
IEEE12844DIR=/usr/local/bin
#
 ${QUEUEDIR}/filter "$@" | ${IEEE12844DIR}/ieee12844_print

I'm able to print color and text web pages with this in Netscape.

All of the necessary kernel modules have to be insmodded for this to work.

-----
Joe  

Re: [hpoj-devel] (no subject)

[Joe P. <joe...@sn...>]

On Tue, 26 Sep 2000, Erik Hendrix wrote:

> My understanding was that I needed apsfilter and a2ps to be able to make 
> this work. This is the only reason why I installed it.
> 

> I'm running Red Hat 6.2 and currently nothing is modified of that version. 
> My printer deamon is up and running.
> 

Erik:

I've only done some testing on the driver and haven't used it regularly. I'm
working on a potential GUI for the project, but that is different from the
inner workings of the driver. Chances are, a much better coder will need to
take over the GUI development later anyway.

Today I tested the driver some more on my RedHat 6.1 desktop system. It seems
to work the way I have it set up, but since I've done minimal testing, I could
be wrong.

From what the developers have said, it seems that the purpose of the driver is
only to add increased functionality and controllability to the officejet, while
simply throughputting the ghostscript-generated print data.

The driver is undergoing active development, and is improving steadily, but it
isn't yet finished.

Here is how my RH 6.1 system is set up, if you want to try copying it:

Basically, I'm not using apsfilter or a2ps, just a regular ghostscript driver
with "wrapfilter" in its spool directory. I had an earlier driver setup that
did  not involve using the hpoj driver. I still have that, plus a new, similar
driver setup for use with the hpoj driver. 

In printtool, I set up a regular ghostscript color print driver, with gamma
correction added via "gamma.ps" because the printing was too dark using only
the gs driver. This should be tested to see if it works as expected. The hpoj
driver is not involved in this first "driver" setup. The printcap entry is
below, as added by printtool.

Note: restart lpd after changes to printtool or printcap entries.

##PRINTTOOL3## LOCAL cdj550 300x300 letter {} DeskJet550 32 1
HPofficejet|officejet|ojet|oj:\
	:sd=/var/spool/lpd/HPofficejet:\
	:mx#0:\
	:lp=/dev/lp0:\
	:if=/var/spool/lpd/HPofficejet/filter:\
	:sh:                            

I then made a copy of the same "driver" with printtool, but with different
printer name(s), and a different spool directory. It's necessary to have a
separate spool dir for each printtool driver entry. The default spool dir is
usually "lp0" but that should be changed to be more descriptive of the driver
being used. In printtool, I called that "HPOJ_DRVR". This should also be tested
to see if it works the same as the other driver.

I later (carefully) hand edited  /etc/printcap to change the :if= line to
change 'filter' to 'wrapfilter'.

##PRINTTOOL3## LOCAL
HPOJ_DRVR:\
	:sd=/var/spool/lpd/HPOJ_DRVR:\
	:mx#0:\
	:lp=/dev/lp0:\
	:if=/var/spool/lpd/HPOJ_DRVR/wrapfilter:\
	:sh:                                    


In the /var/spool/lpd directory there is now a subdir named HPOJ_DRVR where the
necessary files for the ghostscript print driver are kept. This is where I added
the wrapfilter. I had to change the QUEDIR line in wrapfilter to correspond to
the new spool directory. 

#!/bin/sh
# filename: /var/spool/lpd/HPOJ_DRVR/wrapfilter
#
QUEUEDIR=/var/spool/lpd/HPOJ_DRVR
IEEE12844DIR=/usr/local/bin
#
${QUEUEDIR}/filter "$@" | ${IEEE12844DIR}/ieee12844_print
#

I'm able to print color and text web pages with this in Netscape.

All of the necessary kernel modules have to be insmodded for this to work.

-----
Joe  

Re: [hpoj-devel] 2.4.0 kernel issues

[damcha <da...@cy...>]

Hello, 

> could be moved to (or possibly symlinked in) /lib/modules/misc, but there's

Btw, the path for the modules in 2.4 would be
/lib/modules/2.4.0-test8/kernel/drivers/parport/ I suppose (misc doesn't exist any more).

Damcha

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+) s: a-- C++ UL+++ P+>++ L+++ E(+) W++ N+ o? K- w-- O? M V?
PS++ PE- Y+ PGP t+ 5 X++ R(+) tv-(+) b+ DI D++ G e+++ h--- r++ y+++*
------END GEEK CODE BLOCK------
					 See http://www.geekcode.com

Re: [hpoj-devel] 2.4.0 kernel issues

[John L. C. <jl...@cf...>]

On Tue, Sep 26, 2000 at 12:12:29AM -0700, David Paschal wrote:

<snip><snip><snip>

> That part is left over from the previous maintainers.  The new
> "make install" I added to the top-level directory doesn't even invoke
> makefiles in subdirectories.  By default, it installs the modules under
> /usr/local/lib, which doesn't help make it accessible to modprobe.
> Based on John Chmielewski's message from September 13, it sounds like it
> could be moved to (or possibly symlinked in) /lib/modules/misc, but there's
> still the problem that modprobe doesn't detect that ieee12844pp.o depends
> on parport_probe, not just parport and parport_pc.  My idea was to add a
> dummy function in ieee12844pp.c which never got called but which made a
> reference to a function in parport_probe (for example, parport_probe()).
> Since you're working on this code at the moment could you try this out and
> let me know if it fixes the problem (or I can try it myself later).

If you do a modprobe -c, you will see the directories that are searched
for modules.  Besides directories under specific kernel versions, modprobe
will also search specific directories under /lib/modules, if they exist.
So I created /lib/modules/misc and moved the ieee12844 modules there.  I
would like to see the modules installed there instead of /usr/local/lib.

Burkhard Kohl sent a message to this list explaining how to set up
conf.modules, as a workaround, so the modules load.  I modified it
into two lines:
	above parport parport_pc
	below ieee12844 parport_probe


John Chmielewski

Re: [hpoj-devel] (Unofficial patch) 2nd patch to hpoj for 2.4

[<pa...@rc...>]

> >BTW, there is still another problem with the kernel drivers which causes
> >more-or-less random lockups of the client process, for example, when doing
> >a large scan.  If you're able to do anything about that or even just have
> >any ideas on what could be causing it, it would be much appreciated too. 
> :-)
> 
> I've spent a little time reaquainting myself with the code, and I think I
> can take a shot at this.  Fortunately (maybe), it hangs reliably with
> debugging turned on, suggesting a timing issue (interrupt scheduling
> conflicts maybe?).
> 
> I want to start with a small scan like maybe 'scanimage --test', but I don't
> know how the protocol works.  How can I find out what the data exchange
> should look like between the driver and scanner during a scan?  Something
> like a step-by-step explanation would be best.  A dump of the incoming and
> outgoing data would also help.  Then I can compare what I'm getting with
> what I should be getting and hopefully find out where the error is creeping
> in.

Hi, Daniel.  There is a little section at the end of SCAN-HOWTO telling how
to turn on debug output for the SANE HP backend and for PTAL:
>        export SANE_DEBUG_HP=128
>        export PTAL_DEBUG=2
You'll probably want to have HP's SCL documentation handy (available from
http://www.hp-developer-solutions.com, free registration required).  If you
want you can e-mail the output to me (pa...@rc..., not the mailing
list) and I'll take a look at it too.

After I wrote that last paragraph I re-read your question and realized I
didn't answer it.  :-)  It sounds like you're wanting debug output from
some successful runs.  "scanimage --test" may work OK for you (try it and
let me know if even that gives you trouble).  Let me know exactly what
operations you want debug output for and I'll send it to you.

David

[hpoj-devel] Re: HPOJ (fwd)

[David P. <pa...@rc...>]

I meant to copy this to the list.  Has anybody had any experience with the
OfficeJet LX?

David

------- Forwarded Message

To: ott...@t-... (Klaus Degenhardt)
Cc: pa...@rc...
Subject: Re: HPOJ 
From: pa...@rc... (David Paschal)
Reply-To: pa...@rc...
Date: Tue, 26 Sep 2000 00:00:31 -0700

> For interest I read the list of supported devices. 
>  (http://hpoj.sourceforge.net/suplist.shtml)
> Do you plan to support the HP OfficeJet LX for the future or does one of
> the listed devices supports the LX too?
> 
>  With kind regards
> 
>  Klaus Degenhardt

Hi, Klaus.  I'm copying this to the hpoj-devel mailing list in case anybody
else knows more about this model than I do.

I have no experience with the OfficeJet LX, so I don't know for sure whether
it can be supported.  Several months ago I exchanged e-mails with somebody
else who asked the same question, and after he performed some diagnostics
I suggested, it looked like it wouldn't work.  Try the following suggestion
from the FAQ page (which I need to improve):

> On Linux Kernel 2.2.x, type
>	$ cat /proc/parport/0/autoprobe
> On Linux Kernel 2.3.x, type
>	$ cat /proc/sys/dev/parport/parport0/autoprobe
> If the output contains the
> string MLC (probably in the "COMMAND SET" or "CMD" field), then it is
> likely that your printer is supported by our driver.

This retrieves a somewhat "cooked" version of the device ID string of the
peripheral.  Alternatively, you could try Tim Waugh's "deviceid" program
available at "ftp://people.redhat.com/twaugh/parport/deviceid-0.3.tar.gz".
Let me know what output you get.

David

------- End of Forwarded Message

Re: [hpoj-devel] 2.4.0 kernel issues

[<pa...@rc...>]

Hi, Burkhard.

> I see a lot of "already open" messages from the ptal layer - maybe
> we have other problems as well, but "scanimage --test" runs on my 
> box now successfully.
That's normal, due to the somewhat underhanded method I had to use to
make the SANE HP backend work with PTAL.

> BTW: in ieee12844/Makefile.in the "cp" expression to move kernel
> modules to the appropriate location was commented out. Was this
> done for any particular purpose? I am asking because it meant
> that the modules had to be installed by hand.
That part is left over from the previous maintainers.  The new
"make install" I added to the top-level directory doesn't even invoke
makefiles in subdirectories.  By default, it installs the modules under
/usr/local/lib, which doesn't help make it accessible to modprobe.
Based on John Chmielewski's message from September 13, it sounds like it
could be moved to (or possibly symlinked in) /lib/modules/misc, but there's
still the problem that modprobe doesn't detect that ieee12844pp.o depends
on parport_probe, not just parport and parport_pc.  My idea was to add a
dummy function in ieee12844pp.c which never got called but which made a
reference to a function in parport_probe (for example, parport_probe()).
Since you're working on this code at the moment could you try this out and
let me know if it fixes the problem (or I can try it myself later).

David

Re: [hpoj-devel] (Unofficial patch) 2nd patch to hpoj for 2.4

[DG <dg...@um...>]

>BTW, there is still another problem with the kernel drivers which causes
>more-or-less random lockups of the client process, for example, when doing
>a large scan.  If you're able to do anything about that or even just have
>any ideas on what could be causing it, it would be much appreciated too. 
:-)

I've spent a little time reaquainting myself with the code, and I think I
can take a shot at this.  Fortunately (maybe), it hangs reliably with
debugging turned on, suggesting a timing issue (interrupt scheduling
conflicts maybe?).

I want to start with a small scan like maybe 'scanimage --test', but I don't
know how the protocol works.  How can I find out what the data exchange
should look like between the driver and scanner during a scan?  Something
like a step-by-step explanation would be best.  A dump of the incoming and
outgoing data would also help.  Then I can compare what I'm getting with
what I should be getting and hopefully find out where the error is creeping
in.

ZZZ-dgun-ZZZ-@-ZZZ-umpire.com-ZZZ
(Remove the Z-'s to reply)
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup

Re: [hpoj-devel] (no subject)

[Erik H. <hen...@ho...>]

Hey Joe,

>I have no experience with apsfilter or a2ps, but maybe someone here >who 
>does could help you.
My understanding was that I needed apsfilter and a2ps to be able to make 
this work. This is the only reason why I installed it.

>It would be helpful if you could post back giving some extra >information 
>such as
>your operating system type and version, and whether or not your >printer 
>daemon
>is running.
>
I'm running Red Hat 6.2 and currently nothing is modified of that version. 
My printer deamon is up and running.

>Do you see any error messages at boot? If so, write them down >exactly.
No error messages at boot. I checked the boot.log file and the messages 
file.

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

Re: [hpoj-devel] (no subject)

[Erik H. <hen...@ho...>]

Hey Joe,

For the moment that is correct. I'm currently running under ROOT since I 
just started setting everything up and I do not want to constantly switch.
And I'm just trying it out. I know that afterwards I'll need to move it or 
reinstall it to get it to the correct place so that all users can use it.


>From: Joe Piolunek <joe...@sn...>
>Reply-To: hpo...@li...
>To: hpo...@li...
>Subject: Re: [hpoj-devel] (no subject)
>Date: Mon, 25 Sep 2000 20:55:18 -0400
>
>On Mon, 25 Sep 2000, Erik Hendrix wrote:
>
><edited for size>
> >
> > I installed :
> >    APSFILTER
> >    A2PS
> >    Ghostscript
> >    and offcourse the 0.6 HPOJ driver
> >
> >    The driver seems to be working fine since I can get the status of
> >    my printer.
> >    But when I try to print something nothing happens.
>
>
><...>
>
> >           # APS_BASEDIR:/root/linux/rpms/apsfilter
>
> > :if=/root/linux/rpms/apsfilter/filter/aps1-deskjet--auto-default:
>
> >               :if=/root/linux/rpms/apsfilter/filter/aps2-deskjet--raw:
>
><...>
>
> >   As far as I can see everything is allright. But it isn`t since I
> >   can`t print. The big question for me now is what did I do wrong?
> >
> >   Any help is REALLY appreciated.
> >
> > Thank you.
> >
>
>
>Erik:
>
>Check to see if apsfilter has been installed in the correct place. It seems
>unusual to me for new software to be installed under /root. If it doesn't
>belong there,  your trouble could be a permissions problem.
>
>--
>Joe Piolunek
>_______________________________________________
>hpoj-devel mailing list
>hpo...@li...
>http://lists.sourceforge.net/mailman/listinfo/hpoj-devel

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

Re: [hpoj-devel] (no subject)

[Joe P. <joe...@sn...>]

On Mon, 25 Sep 2000, Erik Hendrix wrote:

<edited for size>
>
> I installed :
>    APSFILTER
>    A2PS
>    Ghostscript
>    and offcourse the 0.6 HPOJ driver
> 
>    The driver seems to be working fine since I can get the status of
>    my printer.
>    But when I try to print something nothing happens.


<...>

>           # APS_BASEDIR:/root/linux/rpms/apsfilter
         
> :if=/root/linux/rpms/apsfilter/filter/aps1-deskjet--auto-default:

>               :if=/root/linux/rpms/apsfilter/filter/aps2-deskjet--raw:

<...>
 
>   As far as I can see everything is allright. But it isn`t since I
>   can`t print. The big question for me now is what did I do wrong?
> 
>   Any help is REALLY appreciated.
> 
> Thank you.
> 


Erik:

Check to see if apsfilter has been installed in the correct place. It seems
unusual to me for new software to be installed under /root. If it doesn't
belong there,  your trouble could be a permissions problem.

--
Joe Piolunek