Re: [PARPORT] init_module: Device or resource busy

From: Nate (
Date: Tue Jun 04 2002 - 12:25:33 EDT

  • Next message: Max Vorobiev: "[PARPORT] Extension suggestions for libieee1284"

    Blaise suggested that both the first and second modules were already
    compiled into the kernel. I had thought that the parport module was, but I
    didn't think that the parport_pc module was. It turned out that Blaise was
    correct and it worked like a charm.

    Thank You,


    ----- Original Message -----
    From: "Nate" <>
    To: <>
    Sent: Monday, June 03, 2002 2:11 PM
    Subject: [PARPORT] init_module: Device or resource busy

    > Hello,
    > I am using Kernel 2.4.2-2, (Red Hat 7.1), on a system and the unit it able
    > to print from one program fine. I know the working program uses "lp".
    > However on a program I am trying to write, it fails to load the parport_pc
    > module.
    > My sequence I am simply invoking is the following commands:
    > #insmod parport
    > #insmod parport_pc
    > #insmod ppdev
    > The first and third appear successful as I can see them listed using
    > #lsmod... It reports back the following error: "... init_module: Device
    > resource busy ...", with a hint about the IRQ being the most common
    > after the second command (parport_pc).
    > ......................ok
    > When I boot up, I can read /proc/ioports as having 0x378 and 0x37b as
    > parport0 prior to loading parport module. At that point, if I do a
    > I see nothing. Then I can insert the module, #insmod parport, and see the
    > same thing in /proc/ioports but #lsmod shows the parport module inserted
    > now.
    > I have also tried it with full parameters, #insmod parport_pc io=0x378
    > Nothing seems to get it there.
    > What is the solution or next step? I have read Tim W.'s web pages. I
    > found lots of similar scenarios but no real resolutions in list archives
    > doing a google search... I just do not know what I could do to check
    > Thank You,
    > Nate
    > (I would rather not recompile a kernel if possible)
    > -- To unsubscribe, send mail to: --
    > -- with the single word "unsubscribe" in the body of the message. --

    -- To unsubscribe, send mail to: --
    -- with the single word "unsubscribe" in the body of the message. --

    This archive was generated by hypermail 2b29 : Tue Jun 04 2002 - 12:30:24 EDT