Poly-poly man wrote:
> 3. With the SMC card, if I load tulip, dmesg says :
>
> Linux Tulip driver version 1.1.14-NAPI (May 11, 2002)
> PCI: cache line size of 128 is not supported by device 0000:02:0a.0
> 0000:02:0a.0: tulip_stop_rxtx() failed
> tulip0: MII transceiver #3 config 1000 status 7809 advertising 01e1.
> eth2: Digital DS21140 Tulip rev 32 at MMIO 0xfea00000, EEPROM not present,
> 00:4C:69:6E:75:79, IRQ 22.

Good. The card seems to be working.

> Unfortunately, there's no eth2 (eth2 makes sense because there is a ghost
> eth0 that only pops up at boot, leaving my builtin card to get eth1).

What do you mean "there's no eth2"? Did you check with 'ifconfig -a'
and/or setup the interface with ifconfig? Without the "-a" flag,
ifconfig will show interfaces that are up, which your new one won't be
unless you've already used ifconfig to set it up.

John-Paul Stewart wrote:

> Poly-poly man wrote:
>> 3. With the SMC card, if I load tulip, dmesg says :
>>
>> Linux Tulip driver version 1.1.14-NAPI (May 11, 2002)
>> PCI: cache line size of 128 is not supported by device 0000:02:0a.0
>> 0000:02:0a.0: tulip_stop_rxtx() failed
>> tulip0: MII transceiver #3 config 1000 status 7809 advertising 01e1.
>> eth2: Digital DS21140 Tulip rev 32 at MMIO 0xfea00000, EEPROM not
>> present, 00:4C:69:6E:75:79, IRQ 22.
>
> Good. The card seems to be working.
>
>> Unfortunately, there's no eth2 (eth2 makes sense because there is a ghost
>> eth0 that only pops up at boot, leaving my builtin card to get eth1).
>
> What do you mean "there's no eth2"? Did you check with 'ifconfig -a'
> and/or setup the interface with ifconfig? Without the "-a" flag,
> ifconfig will show interfaces that are up, which your new one won't be
> unless you've already used ifconfig to set it up.

There is indeed, after an ifconfig -a, an eth3 (don't ask), unfortunately,
when hooked up to my router, a dhclient returns no responses. Giving it a
static address doesn't allow it to ping the router either.

I tried Knoppix (5.1.1 DVD), but the same pretty much happened (builtin
worked, SMC didn't, there's that damn ghost eth0 again). With the 3c905b
card in, lspci cannot find it. Anymore. WTF?

The 8139d card seems the best way to go, if I can figure out how to keep it
from halting.

poly-p man

Major ops: for the ifconfig -a
--
There's no place like ~

Poly-poly man wrote:

> John-Paul Stewart wrote:
>
>> Poly-poly man wrote:
>>> 3. With the SMC card, if I load tulip, dmesg says :
>>>
>>> Linux Tulip driver version 1.1.14-NAPI (May 11, 2002)
>>> PCI: cache line size of 128 is not supported by device 0000:02:0a.0
>>> 0000:02:0a.0: tulip_stop_rxtx() failed
>>> tulip0: MII transceiver #3 config 1000 status 7809 advertising 01e1.
>>> eth2: Digital DS21140 Tulip rev 32 at MMIO 0xfea00000, EEPROM not
>>> present, 00:4C:69:6E:75:79, IRQ 22.
>>
>> Good. The card seems to be working.
>>
>>> Unfortunately, there's no eth2 (eth2 makes sense because there is a
>>> ghost eth0 that only pops up at boot, leaving my builtin card to get
>>> eth1).
>>
>> What do you mean "there's no eth2"? Did you check with 'ifconfig -a'
>> and/or setup the interface with ifconfig? Without the "-a" flag,
>> ifconfig will show interfaces that are up, which your new one won't be
>> unless you've already used ifconfig to set it up.
>
> There is indeed, after an ifconfig -a, an eth3 (don't ask), unfortunately,
> when hooked up to my router, a dhclient returns no responses. Giving it a
> static address doesn't allow it to ping the router either.
>
> I tried Knoppix (5.1.1 DVD), but the same pretty much happened (builtin
> worked, SMC didn't, there's that damn ghost eth0 again). With the 3c905b
> card in, lspci cannot find it. Anymore. WTF?
>
> The 8139d card seems the best way to go, if I can figure out how to keep
> it from halting.
>
> poly-p man
>
> Major ops: for the ifconfig -a

I appear to have fixed it.

After playing around in Knoppix, Gentoo decided to cooperate with the two
interfaces at the same time. I still have to worry about the phantom eth0,
but that's for another time.

thanx,
poly-p man
--
There's no place like ~
Gentoo RULES!!!
Live life on the bleeding edge - kernel 2.6.19-rc6!
export ACCEPT_KEYWORDS=~x86

On Sun, 21 Jan 2007, in the Usenet newsgroup comp.os.linux.hardware, in article
, Poly-poly man wrote:

>1. With the rtl8139D card in my system, the computer doesn't even boot
>(probably the 8139too module locking up).

What distribution / release / kernel?

>2. With the 3c905b card, nothing happens when I load 3c59x. This card is (at
>least as far as lspci is concerned) 002c:0200

Does the boot messages show a MAC address?

>3. With the SMC card, if I load tulip, dmesg says :
>
>Linux Tulip driver version 1.1.14-NAPI (May 11, 2002)
>PCI: cache line size of 128 is not supported by device 0000:02:0a.0
>0000:02:0a.0: tulip_stop_rxtx() failed
>tulip0: MII transceiver #3 config 1000 status 7809 advertising 01e1.
>eth2: Digital DS21140 Tulip rev 32 at MMIO 0xfea00000, EEPROM not present,
>00:4C:69:6E:75:79, IRQ 22.

Just went through this in a thread "FA511/tulip cardbus card fails (no
EEPROM) on reboot from WinXP" in comp.os.linux.networking last Wednesday.
You may want to google for that MAC address - yes it's a well known
problem, no - I don't remember what the fix is... my notes say:

--------
In c.o.l.n (Message-ID: <1143424641.153132.176950@i39g2000cwa.googlegroups. com>
on 3/27/06, a report that the tulip _driver_ chooses 00:4C:69:6E:75:79 (Linux
in hex) as the MAC if it can't see the EEPROM. Article title was "MAC
00:4C:69:6E:75:79" posted from Oz by "sergerivest@yahoo.com"
--------

even through that is incorrect (Linux would be 4C:69:6E:75:78, not 79). Are
you also running windoze on this box?

Old guy