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 ?
AH, and I have also found this:
werewolf:~# ifstatus -v lo
lo:
SIOCETHTOOL failed (Operation not supported)
SIOGGMIIPHY failed (Operation not supported)
SIOCDEVPRIVATE failed (Operation not supported)
so loopback also gets uninitialized (active, but no 127.0.0.1 assigned, so
gnome takes an eon to log in).
TIA
--
J.A. Magallon <[EMAIL PROTECTED]> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.21-pre3-jam2 (gcc 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk))
