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

From: Gunther Mayer (
Date: Wed Jul 17 2002 - 05:10:21 EDT

  • Next message: Moritz Barsnick: "Re: [PARPORT] CF reader with Shuttle/SMC EP1284-01"

    Andreas Nowatzyk wrote:
    > said:
    > > As a workaround follow instructions in "setsuperio-experts_only.c"
    > > from
    > Thanks so much for your patience!
    > After running your workaround (with slight modifications) I get:
    > lssuperio V0.67 (EXPERIMENTAL)
    > Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
    > SMSC Super-IO detection, now testing Ports 2F0, 370, 2E, 4E ...
    > SMSC chip at EFER=0x4e key=0x55 id=54 rev=04
    > oldid=0x00 oldrev=0x00
    > LDN 0( FDC): io=0x3f0, irq= 6, dma= 2
    > LDN 1(reserved): Disabled.
    > LDN 2(reserved): Disabled.
    > LDN 3( LPT): io=0x378, irq= 7, dma= 3

    > After this parport_pc load attempt, lssuperio still lists LPT as above: OK,
    > so it is not that case that part of the insmod-attempt disabled the LPT port.
    > However, I had to guess the address for the last outb:
    > outb(0xAA, efer+1); // magic seal

    Thats wrong, you set the parallel port pins to floppy disk mode
    by writing AA to the previously selected register F1
    (some laptops connected external floppy over the parallel port!)

    > I tried first "efer", which produced the outcome described above. Then
    > I tried "efer+1", whioutb(0xAA, eferch made the superio-chip to disappear from lssuperio
    > (but without any other effects: everything else is cool. I guess this is
    > the magic disappera from sight feature described in your comments).

    No, lssuperio does not work when config space is left open.

    > Unfortunately, parport_pc still does not find the port.

    Use outb(0xAA, efer) and retry.

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

    This archive was generated by hypermail 2b29 : Wed Jul 17 2002 - 05:12:41 EDT