🚀 go-pugleaf

David James Spillett wrote:
> 
> In article <F11Bu8.Dx@dangl.demon.co.uk>, Dan Glover
> <news@dangl.demon.co.uk> writes
> >>From the Windows settings, I expect the parallel port to appear at
> >>addresses 0378-037a, but it's not detected.  There's no relevant
> >>message in dmesg, but there never was even when it was working.
> >
> >I'm currently running kernel 2.1.126-pre2, with a modular parallel port
> >driver.  parport0 only appears in /proc/ioports while the module is
> >loaded.  Are you sure that you're not in a situation where your parallel
> >port driver is failing to load when required?  (I'm not sure whether the
> >latest way of handling parport stuff was in 2.0.27.)
> 
> Not as such [it isn't in my 2.0.35] but the lp modules _does_ auto-load
> on my system [when ppa isn't loaded] so this could indeed be the
> problem. Try doing an 'insmod lp' before trying to print and see what
> happens.
> 
> A believe the 2.1 kernels [and the nearly-here 2.2 ones, of course] use
> a different methodology when it comes to parallel ports.
> 
> --
> David James Spillett              Ageing is compulsory
> DJSpillett@bigfoot.com                      Maturing is optional...
> http://www.djspillett.demon.co.uk (home of WholeSite v1.51,
> the one-click web-site updater. Oh, and some strange humour...)


Ahah, that did the trick.  When I was recompiling the kernel I must have
blown away the /lib/modules/2.0.27 directory.  Restoring it fixed
the problem.

Thanks very much to both of you for your help.


Rod Tye.
rdtye@iee.org