hpoj-devel

RE: [Hpoj-devel] newbie question

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

(That's annoying -- sourceforge's mailing lists don't add a Reply-To line to
the header.  Anyway...)

Hi, Erick.  I see from the lsmod output you sent that you have properly
loaded parport, parport_pc, and parport_probe.  What Linux distribution and
version are you running?  What peripheral are you using?  Make sure it's on
the list of supported devices at http://hpoj.sourceforge.net/suplist.shtml.
In particular, the LaserJet 3100 and 3150 aren't supported.  Next, make sure
it's connected and powered on before you insmod ieee12844pp.o.  (Again, I
will clarify this in the documentation next time.)  Let me know if you're
still having trouble, and we'll take it from there.

David


> -----Original Message-----
> From: Erick Calder [mailto:ec...@ar...]
> Sent: Tuesday, August 29, 2000 12:48 PM
> To: PASCHAL,DAVID (HP-Roseville,ex1)
> Subject: RE: [Hpoj-devel] newbie question
> 
> 
> Thank you David, I've gotten a little further this time.  
> "insmod ieee12844.o" returned no response but lsmod shows 
> him, however,
> "insmod ieee12844pp.o" squeals:
> 
> 	ieee12844pp.o: init_module: Device or resource busy
> 
> uhh.... what next?
> 
> Thx - e
> 
> -----Original Message-----
> From: PASCHAL,DAVID (HP-Roseville,ex1) [mailto:dav...@hp...]
> Sent: Tuesday, August 29, 2000 11:23 AM
> To: 'Erick Calder'
> Subject: RE: [Hpoj-devel] newbie question
> 
> Hi, Erick.
> 
> > I'm sorry to post to the "devel" list but I tried to
> > subscribe to the "owners" list and got message that it had
> > been moved to this
> > list.
> >
> > I sent the message below but I don't know whether anyone 
> received it.
> >
> > any response would be greatly appreciated.  btw, is there a
> > newsgroup that replicates this mailing list?
> 
> Not that I know of, but now that we're on sourceforge, there 
> are archives of
> the mailing lists.  Please see 
> http://sourceforge.net/projects/hpoj, click
> on "Lists", and 
> then select the mailing list you want.
> 
> > I've just dowloaded the 0.5 version of the drivers and have a
> > little problem.  the INSTALL file says I should:
> >
> >       insmod ieee12844
> >
> > but insmod complains:
> >
> >       insmod: ieee12844: no module by that name found
> >
> > if I run make inside of the ieee12844 dir is says:
> >
> >       make: Nothing to be done for `release'.
> >
> > here's a dire listing:
> >
> > drwxr-xr-x    2 ekkis    500          4096 Aug 28 11:28 ./
> > drwxr-xr-x    8 ekkis    500          4096 Aug 28 11:31 ../
> > -rw-r--r--    1 root     root         1181 Aug 28 11:27 Makefile
> > -rw-r--r--    1 ekkis    500          1085 Jul  9 00:16 Makefile.in
> > -rw-r--r--    1 ekkis    500         37938 Jul  8 22:21 ieee12844.c
> > -rw-r--r--    1 root     root        21156 Aug 28 11:28 ieee12844.o
> > -rw-r--r--    1 root     root          172 Aug 28 11:28 
> ieee12844.ver
> > -rw-r--r--    1 ekkis    500         26219 Jul  8 22:22 
> ieee12844pp.c
> > -rw-r--r--    1 root     root        11344 Aug 28 11:28 
> ieee12844pp.o
> 
> I'm sorry about the confusion here.  You actually need to cd into the
> ieee12844 directory and run "insmod ieee12844.o" (with the 
> ".o" extension),
> and likewise for ieee12844pp.o.  I'll fix this in the 
> documentation on the
> next release.
> 
> David
> 

RE: [Hpoj-devel] newbie question

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

Hi, Erick.

> > (That's annoying -- sourceforge's mailing lists don't add a
> > Reply-To line to the header.  Anyway...)
> 
> I hit reply to the digest I* received today so I hope that's the right
> thing to do.  yesterday I replied directly to you since you wrote me
> directly.
When I originally replied I didn't notice that it was going to you directly
instead of to the list until after I had sent it.  I'll see if the
sourceforge folks can do anything about this.  In the meantime I'll just use
"reply to all" to make sure that it goes to the list.  I much prefer getting
mail through the list rather than directly, because then it also goes to my
personal (home) e-mail account and reduces the chance that it gets lost in
my inbox at work.  :-)

> ok. I connected the printer and tried again with the same failure.
> 
> 	root@beowulf:/root/hpoj-0.5/ieee12844 # insmod ieee12844pp.o
> 	ieee12844pp.o: init_module: Device or resource busy
> 
> I tried turning the printer off and back on and tried it again but
> still same message.  what next?
Bummer.  Those were the easy solutions.  :-)

I looked at your lsmod output again to see if there were other drivers (like
lp) hogging the parallel port, and I didn't see any.

Try this, and give me the output:
	cat /proc/parport/0/autoprobe
If your peripheral doesn't show up, then see what other port numbers (1, 2,
etc.) are in the parport directory, and try substituting those one by one
for "0".

Is your peripheral by any chance connected to a switchbox or other
"pass-through" device, such as a Zip drive?  It probably won't work in these
situations.

Is the parallel port enabled in your BIOS/CMOS setup?  Ideally it should be
set to "ECP" or "bidirectional", although the drivers currently don't use
the enhanced functionality.

Are you able to print just by dumping text or PCL data to /dev/lp0 (or lp1,
etc.), without loading ieee12844pp.o?  If your computer dual-boots with DOS
or Windows, can you print there?

What is the output from:
	cat /proc/ioports
	cat /proc/interrupts
This is to see if there's an I/O port or IRQ conflict with something else in
your system.

David

RE: [Hpoj-devel] newbie question

[Erick C. <ec...@ar...>]

ok, I looked up your response on the website since the mailing list is
REALLY slow and I have yet to receive it.

here's some stuff you requested:

> cat /proc/parport/0/autoprobe

MODEL:Unknown device;
MANUFACTURER:Unknown vendor;

... which seems obviously wrong but I don't know what valid values
might be...

> see what other port numbers (1, 2, etc.) are in the parport
directory

there is only 0

> Is your peripheral by any chance connected to a switchbox
> or other "pass-through" device, such as a Zip drive?

no, it's connected directly to the printer

> Is the parallel port enabled in your BIOS/CMOS setup?

I will have to check next time I can access the box but I'm pretty
sure (it's enabled by default and I haven't c changed it).

> Ideally it should be set to "ECP" or "bidirectional", although the
drivers
> currently don`t use the enhanced functionality.

I will set it that way when next I have a chance.

> Are you able to print just by dumping text or PCL
> data to /dev/lp0 (or lp1, etc.), without loading ieee12844pp.o?

yes.  I did "cat .kshrc > /dev/lp0" and it printed it.  funky, but it
printed.

> If your computer dual-boots with DOS
> or Windows, can you print there?

not a dual-boot.  linux only.

> cat /proc/ioports

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0220-022f : soundblaster
02e8-02ef : serial(auto)
0330-0333 : MPU-401 UART
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
e800-e8ff : eth0
ec00-ecff : eth1
ffa0-ffa7 : ide0
ffa8-ffaf : ide1

> cat /proc/interrupts

           CPU0
  0:   95883318          XT-PIC  timer
  1:       2468          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:       9432          XT-PIC  serial
  5:    3914313          XT-PIC  soundblaster
  8:          1          XT-PIC  rtc
  9:    3699914          XT-PIC  eth0
 11:     349853          XT-PIC  eth1
 13:          1          XT-PIC  fpu
 14:   10210692          XT-PIC  ide0
 15:        610          XT-PIC  ide1
NMI:          0

hope this stuff helps... would be great to get this to work.

- e

-----Original Message-----
From: PASCHAL,DAVID (HP-Roseville,ex1) [mailto:dav...@hp...]
Sent: Thursday, August 31, 2000 4:10 PM
To: 'Erick Calder'
Cc: 'pa...@rc...'
Subject: RE: [Hpoj-devel] newbie question


Sorry I didn't get to it yesterday.  I send a reply at 2:24 PM
(Pacific
time) today, but the mailing list seems to be rather slow.  I just got
it a
few minutes ago (4:06 PM).

David

> -----Original Message-----
> From: Erick Calder [mailto:ec...@ar...]
> Sent: Thursday, August 31, 2000 3:58 PM
> To: PASCHAL,DAVID (HP-Roseville,ex1)
> Subject: RE: [Hpoj-devel] newbie question
>
>
> David,
>
> I replied to you yesterday at the list address but didn't hear back
> from you.  was that the right thing to do or should I write you
> directly as I'm doing now?
>
> thx - e
>
> Just in case you didn't receive it, I'm including that message
below:
>
> -------------------------------------
> Message: 1
> Date: Wed, 30 Aug 2000 13:42:44 -0700
> From: Erick Calder <ec...@ar...>
> To: hpo...@li...
> Subject: [Hpoj-devel] RE: Hpoj-devel digest, Vol 1 #2 - 3 msgs
>
> David,
>
> > (That's annoying -- sourceforge's mailing lists don't add a
> > Reply-To line to the header.  Anyway...)
>
> I hit reply to the digest I* received today so I hope that's the
right
> thing to do.  yesterday I replied directly to you since you wrote me
> directly.
>
> > I see from the lsmod output you sent that you have properly
> > loaded parport, parport_pc, and parport_probe.  What Linux
> distribution
> > and version are you running?
>
> # uname -a
> Linux beowulf 2.2.14-5.0 #1 Tue Mar 7 20:53:41 EST 2000 i586 unknown
>
> > What peripheral are you using?
>
> an OfficeJet 700 (which is supported)
>
> > Next, make sure it's connected and powered on before you insmod
> > ieee12844pp.o.  (Again, I will clarify this in the documentation
> next
> > time.)  Let me know if you're still having trouble, and we'll take
> it
> > from there.
>
> ok. I connected the printer and tried again with the same failure.
>
> 	root@beowulf:/root/hpoj-0.5/ieee12844 # insmod ieee12844pp.o
> 	ieee12844pp.o: init_module: Device or resource busy
>
> I tried turning the printer off and back on and tried it again but
> still same message.  what next?
>
> thx - e
>
>

Re: [Hpoj-devel] newbie question

[Tim W. <tw...@re...>]

On Fri, Sep 01, 2000 at 10:07:21AM -0700, Erick Calder wrote:

> MODEL:Unknown device;
> MANUFACTURER:Unknown vendor;
>=20
> ... which seems obviously wrong but I don't know what valid values
> might be...

You can use
<URL:ftp://people.redhat.com/twaugh/parport/deviceid-0.3.tar.gz> to
find out what the device ID really is.

Not that it probably helps you..

Tim.
*/

RE: [Hpoj-devel] newbie question

[Erick C. <ec...@ar...>]

Tim,

I compiled the program but the docs are a bit spartan and I'm at a
loss for what value to pass for "deviceid" (required first parameter).

I tried the command below with the following results:

root@beowulf:/root/deviceid # deviceid /dev/lp0
deviceid: cannot set transfer mode

help! - e

-----Original Message-----
From: Tim Waugh [mailto:tw...@re...]
Sent: Friday, September 01, 2000 3:11 PM
To: Erick Calder
Cc: PASCHAL,DAVID (HP-Roseville,ex1); pa...@rc...;
hpo...@li...
Subject: Re: [Hpoj-devel] newbie question


On Fri, Sep 01, 2000 at 10:07:21AM -0700, Erick Calder wrote:

> MODEL:Unknown device;
> MANUFACTURER:Unknown vendor;
>
> ... which seems obviously wrong but I don't know what valid values
> might be...

You can use
<URL:ftp://people.redhat.com/twaugh/parport/deviceid-0.3.tar.gz> to
find out what the device ID really is.

Not that it probably helps you..

Tim.
*/

Re: [Hpoj-devel] newbie question

[Tim W. <tw...@re...>]

On Fri, Sep 01, 2000 at 05:54:49PM -0700, Erick Calder wrote:

> I compiled the program but the docs are a bit spartan and I'm at a
> loss for what value to pass for "deviceid" (required first parameter).

Do something like: 'deviceid --base 0x378'.

Tim.
*/

RE: [Hpoj-devel] newbie question

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

> > cat /proc/parport/0/autoprobe
> 
> MODEL:Unknown device;
> MANUFACTURER:Unknown vendor;
> 
> ... which seems obviously wrong but I don't know what valid values
> might be...
It should report something like "Hewlett-Packard" (possibly all uppercased)
and "OfficeJet Series 700" for the manufacturer and model fields.

> > see what other port numbers (1, 2, etc.) are in the parport
> directory
> 
> there is only 0
OK, so we know there's really only one port.

> > Are you able to print just by dumping text or PCL
> > data to /dev/lp0 (or lp1, etc.), without loading ieee12844pp.o?
> 
> yes.  I did "cat .kshrc > /dev/lp0" and it printed it.  funky, but it
> printed.
By "funky", do mean that it exhibited the "staircase" effect?  That's to be
expected unless the Unix-style newlines (LF only) are converted to DOS-style
(CR and LF).

> > cat /proc/ioports
> 
> 0000-001f : dma1
> 0020-003f : pic1
> 0040-005f : timer
> 0060-006f : keyboard
> 0070-007f : rtc
> 0080-008f : dma page reg
> 00a0-00bf : pic2
> 00c0-00df : dma2
> 00f0-00ff : fpu
> 0170-0177 : ide1
> 01f0-01f7 : ide0
> 0220-022f : soundblaster
> 02e8-02ef : serial(auto)
> 0330-0333 : MPU-401 UART
> 0376-0376 : ide1
> 03c0-03df : vga+
> 03f6-03f6 : ide0
> 03f8-03ff : serial(auto)
> e800-e8ff : eth0
> ec00-ecff : eth1
> ffa0-ffa7 : ide0
> ffa8-ffaf : ide1
Strange.  Did you do this while the parport, parport_pc, and parport_probe
modules were loaded?  I would have expected to see lines like:
	0378-037a : parport0
	0778-077a : parport0

I'm really starting to run out of ideas here.  Your peripheral is connected
directly to the parallel port without any pass-through devices, which is
good, and the parallel port is enabled in the BIOS, obviously since you can
print by cating stuff to /dev/lp0.  The only thing I can think of is that
maybe you have a bad parallel port or cable.  Perhaps there's a line that's
stuck low or high, such that it permits the basic signaling that happens
when using /dev/lp0 but breaks the extra signaling that happens with
ieee12844pp.o.  You wouldn't happen to have a logic analyzer and DB25
breakout board handy, would you?  :-)  At the very least, I would suggest
trying a different parallel cable (a high-quality cable that is "IEEE1284
compliant").  If possible, you could also try a different printer on your PC
or try your printer in a different PC (running Linux, so you can run the
same tests).  Or you could even try adding a second parallel port, but that
could open another can of worms.

What brand/model of computer are you using?

I was going to ask if you were running VMWare (which tends to take over the
parallel port), but I didn't see anything related to it in your lsmod
output.

David

RE: [Hpoj-devel] newbie question

[Erick C. <ec...@ar...>]

> > > cat /proc/parport/0/autoprobe
> >
> > MODEL:Unknown device;
> > MANUFACTURER:Unknown vendor;
>
> > ... which seems obviously wrong but I don't know what valid values
> > might be...
>
> It should report something like "Hewlett-Packard" (possibly all
> uppercased) and "OfficeJet Series 700" for the manufacturer and
> model fields.

forgive my ignorance on the subject but how would such information get
to these files?  is there some package or something I have to
install/run before I try to install your sofware?  I have the lpr
package installed... is there anything else I need?

> Strange.  Did you do this while the parport, parport_pc, and
parport_probe
> modules were loaded?  I would have expected to see lines like:
>	0378-037a : parport0
>	0778-077a : parport0

yes, I did.  I can see the 3 modules loaded.....

> I'm really starting to run out of ideas here.

no! no! :)  this can't be that difficult!

> The only thing I can think of is that
> maybe you have a bad parallel port or cable.

I use this printer to print from my laptop so I know the printer's
good and so is the cable.

> What brand/model of computer are you using?

it's an old brandless P90 with Phoenix BIOS and a 20G drive. but I
know his parallel port is good because before I installed Linux on it
I could print from it on Win98.

> I was going to ask if you were running VMWare (which tends to take
> over the parallel port), but I didn't see anything related to it in
> your lsmod output.

nope.  no VMWare.  just pure Linux...  is there anything I can
de-install and re-install...? where can we go from here?

1k thx - e

RE: [Hpoj-devel] newbie question

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

> > It should report something like "Hewlett-Packard" (possibly all
> > uppercased) and "OfficeJet Series 700" for the manufacturer and
> > model fields.
> 
> forgive my ignorance on the subject but how would such information get
> to these files?  is there some package or something I have to
> install/run before I try to install your sofware?  I have the lpr
> package installed... is there anything else I need?

The "files" in /proc are not actually stored on disk anywhere.  They are
generated by the kernel (in this case, the parport drivers) on-the-fly when
they are accessed.  Normally when the parport drivers are loaded, they do
their own probe of the parallel port(s) to attempt to retrieve a device ID
string from any attached peripherals, and a somewhat abridged version of the
device ID string is available as /proc/parport/0/autoprobe (for port 0).
ieee12844pp.o does its own probe to get to the actual (unabridged) device ID
string from any attached peripherals.  It appears that in both cases, the
device ID string cannot be read.

> > Strange.  Did you do this while the parport, parport_pc, and
> parport_probe
> > modules were loaded?  I would have expected to see lines like:
> >	0378-037a : parport0
> >	0778-077a : parport0
> 
> yes, I did.  I can see the 3 modules loaded.....

Try "cat /proc/ioports" again after insmoding "lp".  Maybe you need an
actual parallel port client driver (not just the parport helpers) for it to
show up.  I am concerned that your parallel port isn't showing up in the
list.

> > I'm really starting to run out of ideas here.
> 
> no! no! :)  this can't be that difficult!
I'm trying my best here.  :-)

> > The only thing I can think of is that
> > maybe you have a bad parallel port or cable.
> 
> I use this printer to print from my laptop so I know the printer's
> good and so is the cable.
> 
> > What brand/model of computer are you using?
> 
> it's an old brandless P90 with Phoenix BIOS and a 20G drive. but I
> know his parallel port is good because before I installed Linux on it
> I could print from it on Win98.

What are you running on the laptop?  Linux or Windows?

When you first set up this peripheral on Windows 98 (whether on the P90
before Linux or on the laptop if that's what you're running there), was
Windows able to detect the device in a "plug and play" fashion?  In other
words, when you booted or otherwise made it probe for new hardware, did it
pop up a "New hardware found wizard" and indicate that the found device was
an HP OfficeJet 700 and automatically pick the right driver, or did you have
to tell it what driver to use yourself?

Or on the other hand, did you use the Windows-based software that came with
the OfficeJet?  That type of software tends to be pretty picky about
insisting that you use it only with the right model, so if it was happy then
it must have been able to probe the device.  Did you try scanning or faxing
(to/from the PC, not standalone) under Windows?

David

RE: [Hpoj-devel] newbie question

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

> > I'm really starting to run out of ideas here.
> 
> no! no! :)  this can't be that difficult!

I know we've already been through the question of connecting the peripheral
before loading ieee12844pp.o, but I just discovered a little subtlety with
this that you should be aware of, and maybe if we're lucky it was causing
the problem all along.  Try unloading all of the parport and hpoj kernel
modules (ieee12844, parport_probe, parport_pc, and parport).  Run "lsmod"
just to be sure.  Now make sure the peripheral is connected and powered on
and in a ready state.  *Now* try loading the kernel modules (parport,
parport_pc, parport_probe, ieee12844.o, ieee12844pp.o).  Does it work now?

In any case, I discovered that the peripheral has to be connected before
loading parport_probe, not ieee12844pp.o.  It turns out that ieee12844pp
doesn't re-probe the peripheral, but instead asks parport_probe for the
device ID string (if any) it had probed when it (parport_probe) originally
got loaded.  So if parport_probe didn't find a peripheral originally, then
you can insmod ieee12844pp.o till you're blue in the face and it won't
recognize a peripheral that was connected after parport_probe was loaded.

I shall cross my fingers and hope this finally solves the problem.  :-)

David

RE: [Hpoj-devel] newbie question

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

> I shall cross my fingers and hope this finally solves the 
> problem.  :-)

One other thing -- if it doesn't solve the problem, please look in syslog
(/var/log/messages) and forward me any messages related to the parport* or
ieee12844*.o modules.

David

RE: [Hpoj-devel] newbie question

[Erick C. <ec...@ar...>]

David,

you hit the nail right on the head with this message.  I followed your
directions and it worked just fine.  In retrospect I now realise that at the
time I loaded parport the printer was not connected and that caused the
problem.

Thank you so very much for your efforts.  it's sooooo cool to be able to
print from that box!

what you're doing (donating your time for others' benefit in the spirit of
the free software community) is very cool.  it makes me wish I were more
than a simple user and that I could  in some way contribute too.  If I can
in any way add value to your process, please do not hesitate to contact me.

Again, thank you so very much.

- erick

-----Original Message-----
From: PASCHAL,DAVID (HP-Roseville,ex1) [mailto:dav...@hp...]
Sent: Saturday, September 02, 2000 1:13 AM
To: 'Erick Calder'
Cc: pa...@rc...; hpo...@li...
Subject: RE: [Hpoj-devel] newbie question


> > I'm really starting to run out of ideas here.
>
> no! no! :)  this can't be that difficult!

I know we've already been through the question of connecting the peripheral
before loading ieee12844pp.o, but I just discovered a little subtlety with
this that you should be aware of, and maybe if we're lucky it was causing
the problem all along.  Try unloading all of the parport and hpoj kernel
modules (ieee12844, parport_probe, parport_pc, and parport).  Run "lsmod"
just to be sure.  Now make sure the peripheral is connected and powered on
and in a ready state.  *Now* try loading the kernel modules (parport,
parport_pc, parport_probe, ieee12844.o, ieee12844pp.o).  Does it work now?

In any case, I discovered that the peripheral has to be connected before
loading parport_probe, not ieee12844pp.o.  It turns out that ieee12844pp
doesn't re-probe the peripheral, but instead asks parport_probe for the
device ID string (if any) it had probed when it (parport_probe) originally
got loaded.  So if parport_probe didn't find a peripheral originally, then
you can insmod ieee12844pp.o till you're blue in the face and it won't
recognize a peripheral that was connected after parport_probe was loaded.

I shall cross my fingers and hope this finally solves the problem.  :-)

David

RE: [Hpoj-devel] newbie question

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

> you hit the nail right on the head with this message.  I followed your
> directions and it worked just fine.  In retrospect I now 
> realise that at the
> time I loaded parport the printer was not connected and that 
> caused the
> problem.
> 
> Thank you so very much for your efforts.  it's sooooo cool to 
> be able to
> print from that box!

Hi, Erick.  I'm glad it's working now.  Sorry I gave you the run-around on
this problem; I learned a thing or two about this software myself.  When I
update the documentation to prepare for the next release I will add all the
troubleshooting steps we went through, starting with the most recent one.
:-)

> what you're doing (donating your time for others' benefit in 
> the spirit of
> the free software community) is very cool.  it makes me wish 
> I were more
> than a simple user and that I could  in some way contribute 
> too.  If I can
> in any way add value to your process, please do not hesitate 
> to contact me.
I'm glad that my work is useful.  If nothing else, it is very helpful to
receive feedback so I know what areas of the software and documentation need
improvement.  If you find something that's broken or you have a suggestion
of how to make something work better or make it easier to use, then let me
know.  I may not be able to get to it right away, but at least it'll go on
my list of things to look into later.

David