I had a similar problem lately. I had a defective mobo replaced, and after
that the soundblaster didn't work. After switching the soundblaster and the
NIC from their respective slots, the NIC didn't work...
Then I put the NIC in a different PCI-slot, assuming the previous slot must
have been broken. Then it appeared to work, linux detected the NIC, the
modules loaded OK, everything went cool, untill I actually tried to use the
network.
Further testing revealed that the replacement mobo had 2 total dead and 1
cripple PCI-slot. After sending it back, and getting 2 more mobos (next
replacement came with defective PS/2 connections... Djees!) it finally
works.
Bottom line: screw open the case, and try putting the NIC in a different
PCI slot, and see if it helps. If it does, either the mobo is defective, or
you got one of them PCI incompatibility things that occurs on the last (or
is it first) slot of a PCI-system... Which is completely normal, btw...
On 2001.03.07 00:19 Carl Lafferty wrote:
> I have an Intel pro 100+ Network card (that's what windows idents it as)
> and since I upgraded my mobo from an asus p5ab to a p3b-f I can't get it
> to
> work in linux at all any more. everything APPEARS to work fine however.
> it is apparently detected and it did work prior to the mobo change.. ..
> I even did a complete reinstall of linux mandrake 7.2 and no go.
>
> I used the dmesg command to obtain some info:
>
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V.
> Savochkin <[EMAIL PROTECTED]> and others
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:7E:19:75, I/O at
> 0xd000,
> IRQ 0.
> Receiver lock-up bug exists -- enabling work-around.
> Board assembly 727095-007, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0x04f4518b).
>
>
>
> I am unsure why it is showing the card as having IRQ 0. Windows says
> it is on irq 9..
>
>
>
> this is important since when I want to do things in linux at home
> my wife still has to be able to get out to the net thru internet
> connection sharing.
>
> Any help is appreciated.
>
> --
> Carl Lafferty
> System Administrator, Floyd County Public Library
> Registered Linux User #201131
>
>
--
Rial Juan <http://nighty.ulyssis.org>
e-mail: [EMAIL PROTECTED]
ICQ: 20135549
Belgium tel: ++3289856533
cellular: ++32496737018
ulyssis system admininstrator <http://www.ulyssis.org>
1010011010 : Binary of the Beast
