Re: [PARPORT] Upgrade 2.4.4 to 2.4.18 lost parallel port

From: Andreas Nowatzyk (Andreas_Nowatzyk@onsis.sp.ri.cmu.edu)
Date: Sun Jul 14 2002 - 14:24:33 EDT

  • Next message: Charles Lepple: "Re: [PARPORT] Upgrade 2.4.4 to 2.4.18 lost parallel port"

    twaugh@redhat.com said:
    >> On Sun, Jul 14, 2002 at 03:41:10AM -0400, Andreas Nowatzyk wrote:
    >> After the "upgrade" I get:
    >>
    >> Jul 7 15:32:11 timesink kernel: parport 0x378 (WARNING): CTR: wrote 0x0c,
    read 0xff
    >> Jul 7 15:32:11 timesink kernel: parport 0x378 (WARNING): DATA: wrote 0xaa,
     read 0xff
    >> Jul 7 15:32:11 timesink kernel: parport 0x378: You gave this address, but
     there is probably no parallel port there!
    >> Jul 7 15:32:11 timesink kernel: parport0: PC-style at 0x378
    [PCSPP,TRISTATE]
    >
    > There really is no port at 0x378. Try leaving out all of the options
    > to parport_pc.
    >
    > Tim.
    > */

    I guess so, but it used to be there and it still is under window. Without
    options to parport_pc I get:

    /lib/modules/2.4.18-4GB/kernel/drivers/parport/parport_pc.o: init_module:
    Device or resource busy
    Hint: insmod errors can be caused by incorrect module parameters, including
    invalid IO or IRQ parameters

    and parport_pc does not load. I tried this with all variations of parport_pc
    and the result is always this.

      Kind regards,
      -- A. Nowatzyk

    -- 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 : Sun Jul 14 2002 - 14:28:03 EDT