[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Installing a NIC
>eexpress.c doesn't compile with the options given. Once compiled (with
>different options), it still couldn't find the card to set it up.
It is quite possible that the card had NO assigned address/IRQ at that
point, and thus NO system could have found it. We don't know (or you
haven't reported on) the prior history of this card, so it's hard to know
what was in PROM beforehand.
>After I booted with a DOS disk and ran Intel's setup program, it was able
>to find the card (as long as I told it what address to use) so I guess
>it's pretty much worthless.
Sounds like it's worthless in the case where you used it; the OEM setup
disk was clearly needed. Consider other cases, where one is testing a
card that was installed previously, so the card had an assigned address,
or some testing of the card was needed. This is (probably) the real value
of this program.
>I was able to get Linux to recognize the card with the command:
>root# ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
Right, 'cept this is configuring the INTERFACE, and binding it to the
card, not configuring the card itself. To see where/what was recognized,
issue: dmesg|less Look for mention of the ethernet card in that listing.
>but still no communication.
Between the Linux box and what else?
>The problem seems to be with the Windows protocol. I'm working on that
>tonight.
>(By the way, it took me about 15 minutes to get the card working in my
>Windows box.)
OK, that's fine. If there's "no communication", how do you know the
card is setup right in the 15 minutes it took you over in Windows?
Also, can you tell us how much time it took to actually get the card
working on your Linux machine? Don't count study time, software
acquisition time, time of experimentation, etc, but just the time to do
exactly what worked.
Keep us posted!
Regards,
---> RGB <---