On Sat, Jul 08, 2006 at 07:00:01PM -0400, Garry T. Williams wrote:
> On Saturday 08 July 2006 16:14, Todd Zullinger wrote:
> > Charles Curley wrote:
> > > I don't see anything obvious. Here's a wierd one:
> > >
> > > Deactivating device dev3514.
> > >
> > > I see other more reasonable device names like eth0 and eth1, but
> > > that's another mutant device name.
> >
> > So the devXXXXX numbers change frequently too? If you grep the logs
> > for one of those, are there any other entries for them which might
> > give a clue as to when or why they're being created?
>
> You want to install the initscripts update. It should eliminate the
> devXXXX interfaces.
I did so, and rebooted. The system came up and ran the network
initscript. I got a connection on eth0. I did not check to see if eth1
was set up correctly.
I then turn on NM. It broke my connection. eth1 had been replaced with
a mutant device name:
dev1804289383 Link encap:Ethernet HWaddr 00:10:C6:C0:AA:26
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 00:13:CE:70:53:C8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1055 errors:6 dropped:6 overruns:0 frame:0
TX packets:419 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:45025 (43.9 KiB) TX bytes:37217 (36.3 KiB)
Interrupt:11 Base address:0x8000 Memory:c0204000-c0204fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:329 errors:0 dropped:0 overruns:0 frame:0
TX packets:329 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:29622 (28.9 KiB) TX bytes:29622 (28.9 KiB)
eth0 is the wireless device. NM still failed to authenticate on it.
[root@dragon ~]# pre initscripts networkmanager| sort
initscripts-8.31.5-1
NetworkManager-0.6.3-1.fc5
NetworkManager-glib-0.6.3-1.fc5
NetworkManager-gnome-0.6.3-1.fc5
I then rebooted, and am using a connection established by the network
init script. Without having run NM, I see:
[root@dragon ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:CE:70:53:C8
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe70:53c8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6679 errors:0 dropped:0 overruns:0 frame:0
TX packets:6652 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2115735 (2.0 MiB) TX bytes:916352 (894.8 KiB)
Interrupt:11 Memory:c0204000-c0204fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:354 errors:0 dropped:0 overruns:0 frame:0
TX packets:354 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:30600 (29.8 KiB) TX bytes:30600 (29.8 KiB)
[root@dragon ~]# ifconfig eth1
eth1: error fetching interface information: Device not found
Just for the halibut, I plugged a cable into eth1. ifconfig reports
the same. There is no link light on the computer. The link and high
speed lights on the switch are now on. The driver for it is installed:
[root@dragon ~]# lsmod | grep e100
e100 35909 0
mii 5697 1 e100
The initscripts update did not eliminate the mutant device names. It
did, however, eliminate my ethernet device. Imagine my ecstasy.
--
Charles Curley /"\ ASCII Ribbon Campaign
Looking for fine software \ / Respect for open standards
and/or writing? X No HTML/RTF in email
http://www.charlescurley.com / \ No M$ Word docs in email
Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Attachment:
pgpHxtaYVk0zI.pgp
Description: PGP signature
