Re: [Fwd: Re: [PARPORT] printing problem]

From: Lars-Göran Andersson (lars-goran.087775025@telia.com)
Date: Sun May 25 2003 - 05:34:13 EDT

  • Next message: Peter Asemann: "[PARPORT] More libieee questions"

    Tim Waugh wrote:

    >On Sat, May 24, 2003 at 09:14:40AM +0200, Lars-Göran Andersson wrote:
    >
    >
    >
    >>May 15 20:32:16 lasse kernel: parport 0x378: You gave this address, but
    >>there is probably no parallel port there!
    >>May 15 20:32:16 lasse kernel: parport0: PC-style at 0x378 [PCSPP(,...)]
    >>May 15 20:32:16 lasse kernel: lp0: using parport0 (polling).
    >>
    >>When I check /proc/..../parport0/base-addr I get '888 1912' in both
    >>cases so apperntly 0x378 seems to be the
    >>right place for the port.
    >>
    >>
    >
    >That isn't what that means - since your modules.conf specifies that
    >address, parport has to believe it (even though it protests). There
    >more than likely is no port there.
    >
    >Tim.
    >*/
    >
    >
    If I comment out the parport options line I get the following message in
    /var/log/messages.:

    May 25 11:08:37 lasse insmod:
    /lib/modules/2.4.19-4GB/kernel/drivers/parport/parport_pc.o:
    init_module: Device or resource busy
    May 25 11:08:37 lasse insmod: Hint: insmod errors can be caused by
    incorrect module parameters, including invalid IO or IRQ
    parameters. You may find more information in syslog or the output
    from dmesg
    May 25 11:08:37 lasse insmod:
    /lib/modules/2.4.19-4GB/kernel/drivers/parport/parport_pc.o: insmod
    parport_lowlevel failed
    May 25 11:08:37 lasse kernel: lp: driver loaded but no devices found

    What still confuses me is the fact that when running my 2.4.4 kernel
    and looking at /proc/dev/parport/parport0
    I can see that the only difference is the value of 'modes', which is
     PCSPP,EPP for my 2.4.4 system and
    only PCSPP for the 2.4.19 system. The options line is commented out for
    my 2.4.4 system as well so I assume
    parport is scanning for a port and is successful for the 2.4.4 system
    and unsuccessful for the 2.4.19 system.
    Since the /proc/..../parport0/base-addr value is 888 for my 2.4.4 system
    I assumed it had found a port at
    0x378.

    Regards, Lars-G

    -- 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 May 25 2003 - 05:43:11 EDT