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
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 ?
-Is the problem eventually due to some incompatibilities with Kernel 2.2.5 ?
Best regards,
Pierre.
------------------------------------------------------------------------------
At 18:44 02.06.99 +0200, you wrote:
>On Wed, Jun 02, 1999 at 04:03:29PM +0200, Pierre Jung wrote:
>
>Hello Pierre,
>
>>
>> you proposed kindly for solving this detection problem. Somehow, it
does not
>> want to detect the drive on port 0x378, irq 7 which are set in the BIOS.
>> Interestingly,in /proc/interrupts, irq 7 DOES NOT APPEAR. However in
>> /proc/ioports, the unique parallel port appears as 0378-037a : parport
0. Is
> ^^^^^^^^^^
>parport claims ioports ftape wants to access as well.
>Several people have reported problems regarding the interaction between
>ftape and
>parport, parport_pc. So I would recommend unloading parport_pc and parport
>before
>trying to load ftape, zftape and bpck-fdc. If this unloading fails it may be
>necessary to remove lp as well:
>
> modprobe -r lp
> modprobe -r parport_pc
> modprobe -r parport
>
> and now ftape...
>
>
>> there something wrong for not mentionning irq 7 ? I have no prointer
>
>no, I wouldn't say so. Those irq lines are not always claimed the whole time.
>
>(...)
>> 22:04:13 : [010] 0 fdc-parport.h (ft_parport_claim) - Unable to grab
>> address 0x0378 for <NULL>.
>
>yes, a collision between ftape and parport. Parport has to removed, so that
>ftape/zftape/bpck-fdc can work correctly.
>
>Ok - let's see what the next problems are....
>
>
>Good luck,
>
>Juergen.
>
>--
>****************************************************************
>* Juergen Leising; email: [EMAIL PROTECTED] *
>* http://www.stud.uni-bayreuth.de/~a0037/ *
>****************************************************************
