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