On Sun, Aug 26, 2001 at 01:51:20PM -0400, Eric Howard wrote: > > > Is parport.o for the same kernel as the one you are running > > (type uname -a to check)? > > Well, it's under 2.2.17 and my kernel is 2.4.9, but the /lib/modules/2.4.9 > directory doesn't seem to have the module in it, so I assumed that 2.2.17 > was up-to-date. If not, where do I go for a more recent copy of parport.o? >
Modules are always specific to the kernel version, sometimes even to the options selected when that kernel was compiled. Your 2.2.17 parport.o is a whole generation older than your 2.4.9 kernel. Its like trying to fit an old HP LaserJet 1 ink cartridge in a HP Color LaserJet 8000, it just won't fit. Technical background: In kernel 0.x.x the kernel was one big thing, everything was either compiled in or not there at all. To save memory and allow no-compile config changes during first time system install, current kernels (since 1.3.* I think) allow you to put some parts of kernel in modules to be loaded on request. But it is still one big kernel which should all be built as one big unit, bzImage, System.map, modules and all. I don't know much about kernel 2.4.x but perhaps parport is called something else in 2.4.x. But first check wherever you got your copy of 2.4.x to see if there is a file or package full of modules. Also make sure all kernel-related tools (e.g. insmod and other modutils) are 2.4.x compatible versions. Hope it helps Jakob -- This message is hastily written, please ignore any unpleasant wordings, do not consider it a binding commitment, even if its phrasing may indicate so. Its contents may be deliberately or accidentally untrue. Trademarks and other things belong to their owners, if any.
