Re: Gateway Solo's ethernet card

[Viktor Pavlenko <vp@example.com>]

Finally, I'm giving up... One of the reasons being that pcmcia network
card works fine.

>>>>> "CS" == Christopher Sekiya <wileyc@example.com> writes:

    CS> Assuming that the driver author isn't smoking crack, your
    CS> hardware has to be somewhat misconfigured.

I tried Becker's driver and 3Com's one. It really looks like hardware
is misconfigured (configured to work with windows). Built-in WinModem
and 3Com ethernet controller share the same IRQ 10. The drivers I
tried don't allow to change IRQ. Also winmodem and ethernet card have
the same IRQ 10 under win98 where the card does work!

    CS> Turn off _all_ power management (i.e., APM or APCI) and see
    CS> what happens.

Tried that. Also, somewhere at www.scyld.com I found the following:

    scyld> What if the card is detected with a ff:ff:ff:ff:ff:ff
    scyld> station address?

    scyld> There are three known causes of this problem.

    scyld> Warm-booting from Win95 OSR2.1 or Win98 (power-managed
    scyld> cards only)

    scyld> "PnP OS" is set in the PCI BIOS setup.

    scyld> Broken PCI BIOSes (reportedly version "AI78" is broken).


Turning "PnP OS" (another name for a MS system!) off, shutting down
the machine and removing battery -- nothing helped. The only thing I
can console myself with is that probably the PCI BIOS is broken.

But basically, it was fun :-----------)

Thanks for your responses.

Viktor

P.S. Forgot to tell you, I met a person who had had the same problems
with the same (or about the same) laptop model. He doesn't know the
solution either.