Re: [PARPORT] parport_pc: Device or resource busy

From: Eric And Steff Runquist (
Date: Wed Sep 05 2001 - 00:11:24 EDT

  • Next message: Tim Waugh: "Re: [PARPORT] parport_pc: Device or resource busy"

    After running insmod parport_pc with my parallel port's base IO address,
    I get this from dmesg:

    parport 0x378 (WARNING): CTR: wrote 0x0c, read 0xff
    parport 0x378 (WARNING): DATA: wrote 0xaa, read 0xff
    parport 0x378: You gave this address, but there is probably no parallel port
    parport0: PC-style at 0x378 [PCSPP,TRISTATE]
    parport0: cpp_daisy: aa5500ff87(b8)
    parport0: assign_addrs: aa5500ff87(b8)
    parport0: cpp_daisy: aa5500ff87(b8)
    parport0: assign_addrs: aa5500ff87(b8)

    I tried running printconf, to set up a printer, and things go ok
    until I try to print to it. The print job shows the following status
    for a few seconds, then goes away:

    IF filter 'mf_wrapper' filter msg - 'gs PID2=1157' at ...

    I guess setting up the printer drivers was kind of pointless if the
    parallel port isn't right. Any more thoughts?


    Tim Waugh wrote:

    > On Tue, Sep 04, 2001 at 08:15:54AM -0400, Eric And Steff Runquist wrote:
    > > What are your rule-outs for this? Hardware problem? Configuration problem?
    > > User problem ;-)?
    > I guess parport_pc or the hardware is at fault here.
    > What happens if you do 'insmod parport_pc io=0x378' (or whatever base
    > address your port has)?
    > Tim.
    > */
    > ------------------------------------------------------------------------
    > Part 1.2Type: application/pgp-signature

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

    This archive was generated by hypermail 2b29 : Wed Sep 05 2001 - 02:44:09 EDT