Frederic Lepied wrote:

"J.A. Magallon" <[EMAIL PROTECTED]> writes:


On 2003.01.16 Frederic Lepied wrote:

"J.A. Magallon" <[EMAIL PROTECTED]> writes:


On 2003.01.16 J.A. Magallon wrote:

Hi...

Latest initscripts fail to init my dhcp connection (I had to call dhclient
by hand...)


It works for other cards...

(lspci+ifstatus -v)

At home if fails all methods:
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
eth0:
SIOCETHTOOL failed (Operation not supported)
SIOGGMIIPHY failed (Operation not supported)
SIOCDEVPRIVATE failed (Operation not supported)

Can you send me the pci id of the card please ? That way we will be
able to make exceptions by putting MII_NOT_SUPPORTED in the ifcfg-eth?
file.

Here's the info:
lspci -v:
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Flags: medium devsel, IRQ 11
I/O ports at ef20 [size=32]

lspci -n
00:10.0 Class 0200: 10ec:8029

But I do not think it is the way to go... There can be tons of exceptions, old
cards and new cards which have a driver but it still does not support mii.
Filling a list with exceptions is so error prone...
Wouldn't it be better to skip the ifplug-ging if ONBOOT = yes, and force ifcfg ?
And some way to test if mii work, and fall back to 'traditional-slow-but-safe'
method ?

Yes you are right. I'm going to modify ifplugd to launch ifup if the
detection failed.

I've got a number of Ethernet controllers:

This one works fine with ifplugd:
00:0c.0 Class 0200: 10b7:9055 (rev 30)
00:0c.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)
Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
Flags: bus master, medium devsel, latency 32, IRQ 12
I/O ports at ac00 [size=128]
Memory at da021000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: <available only to root>

This one doesn't want to come up. It's got a static IP-address and the interface is brought up after booting. With ifplugd no IP-address is assigned to the interface.
00:0d.0 Class 0200: 10b7:9050
00:0d.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at b000 [size=64]
Expansion ROM at <unassigned> [disabled] [size=64K]

This one doesn't want to come up. It's got a dynamic (DHCP) IP-address and the interface is brought up after booting. With ifplugd no IP-address is assigned to the interface:

# ifup eth0
Determining IP information for eth0... failed; no link present. Check cable?

After running dhcpcd by hand all is well.

00:0e.0 Class 0200: 1011:0002 (rev 24)
00:0e.0 Ethernet controller: Digital Equipment Corporation DECchip 21040 [Tulip] (rev 24)
Flags: bus master, medium devsel, latency 96, IRQ 10
I/O ports at b400 [size=128]
Memory at da020000 (32-bit, non-prefetchable) [size=128]

The VMware machine I've got running presents the same issues as the Tulip card above:

00:11.0 Class 0200: 1022:2000 (rev 10)
00:11.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)

with kind regards,

Stefan

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to