Thanks for the quick reply!
I tried your suggestion. The rmmod commands both give me
"module is not loaded" messages. I ran the dmesg -c command,
then insmod parport. That succeeded. However, insmod parport_pc
gave me this:
init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
After running dmesg > messages, the messages file contained this:
WinBond Super-IO detection, now testing ports 3F0, 370, 250, 4E, 2E ...
SMSC Super-IO detection, now testing Ports 2F0, 370 ...
Can you tell what's going on from this output?
Eric
Tim Waugh wrote:
> On Sun, Aug 26, 2001 at 09:34:32PM -0400, Eric And Steff Runquist wrote:
>
> > I looked in /var/log/messages, and discovered the following
> > error:
> >
> > ...insmod: /lib...parport/parport_pc.o init_module: Device or resource
> > busy
>
> Do this:
>
> rmmod parport_pc
> rmmod parport
> dmesg -c > /dev/null (to clear the kernel message buffer)
> insmod parport
> insmod parport_pc
> dmesg > messages
>
> What's in the 'messages' file at that point?
>
> Tim.
> */
>
> ------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Thu Aug 30 2001 - 02:31:34 EDT