Re: [PARPORT] printing with 2.2.18pre21 kernel

From: Tim Waugh (twaugh@redhat.com)
Date: Wed Nov 22 2000 - 09:25:25 EST

  • Next message: Eythan Weg: "Re: [PARPORT] printing with 2.2.18pre21 kernel"

    On Wed, Nov 22, 2000 at 09:14:33AM -0500, Eythan Weg wrote:

    > Neither 2.2.18pre21 nor 2.4.0-test11 behaves
    > properly. They both allow me to write to /dev/lp0
    > without error.

    What happens if you do:

    # insmod parport
    # insmod parport_pc
    # insmod lp reset=1

    ? Does the printer do anything?

    > For 2.2.18 it is as follow: parport, parport_pc,
    > pnp_parport, paride, and printer are set to
    > modules.

    You could even turn off CONFIG_PNP_PARPORT and CONFIG_PARIDE
    altogether.

    > Pnp and printer_readback are in the
    > kernel. This is compiled with gcc-2.7.2.3.

    And you don't need CONFIG_PRINTER_READBACK.

    > For 2.4.0-test11 it is as follows: parport,
    > parport_pc, printer are modules. parport_pc_fifo,
    > parport_1284, pnp, isapnp are in the kernel. This
    > is compiled with gcc-2.95.2. (I do not have easy
    > access to the recommended compiler.)

    You could turn off CONFIG_PARPORT_PC_FIFO and CONFIG_PARPORT_1284
    altogether. It seems unlikely that the only problem is a compiler
    bug, since the 2.2.x kernel is compiled with a kernel that's
    recommended for at least one kernel you've tried.

    My best guess at the moment is that it's a timing problem: perhaps the
    printer needs a longer strobe or something. You can use tunelp to
    adjust that (on 2.2.x only, it doesn't work with 2.4.x for the
    moment).

    Tim.
    */



    -- 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 : Wed Nov 22 2000 - 09:25:53 EST