On Fri, Jun 04, 1999 at 09:29:47AM +0200, Pierre Jung wrote:
> Hello J�rgen,
>
> Thanks again for your hints. Sorry to insist, but unfortunately, none of
> these modules is loaded. I compiled SuSE Kernel 2.2.5 with the parport,
> parport_pc support as modules, as well as for lp support. So, the 3 modules
this is certainly ok...
> do exist in /lib/modules/2.2.5/... and are loadable without any problems
> (lp + parport) if wished so. Am I missing something ? Two questions:
>
> -Is there any other way to get rid of this *%&? parport 0 in /proc/ioports if
> it has not been compiled into the kernel and the corresponding modules has
> never been loaded ?
Good question, in fact, I cannot imagine how parport 0 is able to
appear without parport and parport_pc having been loaded...(assuming they
are not linked statically with the kernel, i. e. didn't choose "Y"
while configuring your kernel) - perhaps parport_probe is still left...
Ok - a bit of struggling is necessary...
So one more time (to present us some information):
- try to remove parport and parport_pc and parport_probe and lp by
rmmod or by modprobe -r
- try to load these ftape modules by insmod or by modprobe
- show us please the output of cat /proc/ioports
- show us please the output of lsmod
- if lsmod didn't spit out "parport" nor "parport_pc" nor "lp": show us
please again the output of dmesg as long as ftape is concerned
>
> -Is the problem eventually due to some incompatibilities with Kernel 2.2.5 ?
>
Hm, haven't heard of any. Well, I myself would prefer to take a kernel that
is not modified by suse, but this should not be the reason in your case.
Has anybody else any further ideas?
Cheers, Juergen.
--
****************************************************************
* Juergen Leising; email: [EMAIL PROTECTED] *
* http://www.stud.uni-bayreuth.de/~a0037/ *
****************************************************************
