A W Young enscribed thusly:
> In article <[EMAIL PROTECTED]>, Michael H.
> Warfield <[EMAIL PROTECTED]> writes
:
: - snip to remove ongoing cruft...
:
> I'm not entirely sure, but I have the file vmlinuz-2.0.34-0.6 which I
> guess means version 2.0.34.
Correct... You can double check that its the version you have
loaded by typing "uname -a".
> >If it's a 2.0 kernel, it's
> >not a parport line you should have been looking for. How about an
> >lp line like this:
> >0378-037f : lp
> No. No mention of either lp or parport.
Ok! Now we're getting down to brass tacks. You don't have support
for lp in the kernel.
> > This is from my 2.0.36 system. The parport0 line in my earlier
> >message was from 2.2.1.
> > If you don't see an lp line in the ioports, try running the command
> >"insmod lp" and see what happens... See if your lpr ports work and see
> >if anything shows up in ioports then.
> Typed "insmod lp" and got
> insmod: lp: no module by that name found
> Then moved to /dev and tried "insmod lp" again and got:
No no... Don't do that...
The modules reside in /lib/modules/{version}/{category}
Where {category} would be things like "misc", "fs", "net",
etc, etc... For your kernel version, you should have had the file
"/lib/modules/2.0.34-*/misc/lp.o" for "insmod lp" to work. If lp
is not in your kernel and not loadable as a module, that's definitly
at the heart of your problem. Personally, I would rebuild a kernel,
2.0.36 is the latest in the 2.0 series and 2.2.1 is the latest in the
2.2 series, and include parallel port support or build it as a module.
You aren't getting anywhere till that lp support is in place.
> ./lp: error reading ELF header: Success
> --
> A. W. Young
> http://www.tylehurst.demon.co.uk/
Mike
--
Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
(The Mad Wizard) | (770) 925-8248 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
