Oh dear what did I start!@!@! I'm sorry, I did not know this was a
machine brewing. Don't follow the mailing list all that often. I
updated 3 x86 machines with no problem but the 64 just took a crap...
I agree! Should have read the notes.
N.
On 4/6/13, Jörg Schaible <joerg.schai...@gmx.de> wrote:
> Volker Armin Hemmann wrote:
>
>> Am 06.04.2013 21:33, schrieb Mick:
>>> On Saturday 06 Apr 2013 20:03:15 Volker Armin Hemmann wrote:
>>>> Am 06.04.2013 17:57, schrieb Alan Mackenzie:
>>>>> Hi, Nick.
>>>>>
>>>>> On Sat, Apr 06, 2013 at 10:51:42AM -0400, Nick Khamis wrote:
>>>>>> After updating our systems we lost network connectivity to the
>>>>>> servers. When trying to start net.eth0 we got the following message:
>>>>>> /ib64/rc/net/wpa_supplicant.sh: line 68: _is wireless command not
>>>>>> found /etc/init.d/net.eth0: line 548: _exists command not found
>>>>>> Errror: Interface eth0 does not exist
>>>>>> Ensure that you have loaded the correct kernel modules for your
>>>>>> hardware
>>>>>> # lsmod
>>>>>> module used by
>>>>>> tg3 0
>>>>>> lbphy tg3
>>>>>> eth0
>>>>>> flags=4098<broadcast,multicast> mtu 1500
>>>>>> ....
>>>>>> interrupt=16
>>>>>>
>>>>>> lo
>>>>>> flags=73<UP,LOOPBACK,RUNNING> mtu 16436
>>>>>> inet 127.0.0.1 BROADCAST 255.255.255.0
>>>>>> inet6 ::1 prefixlen 128 scopeid 0x10 <host>
>>>>>>
>>>>>> Please excuse me, I am running back and forth from the servers and
>>>>>> typing the error message here. Did our configuration get switched to
>>>>>> IP6? These are our DB servers and why me!!! Why ME!!!!!
>>>>> No, it's not just you, it's happened to pretty much everybody.
>>>>> udev-200 now renames eth0, eth1, .... to something else, dependent
>>>>> upon
>>>>> complicated rules. In my case eth0 has become p6p1, though many
>>>>> people
>>>>> seem to have got longer names.
>>>>>
>>>>> Have a look in /sys/class/net and see if your new name is there. If
>>>>> so, edit all your config files containing eth0, switching to the new
>>>>> name.
>>>>>
>>>>> Once you got that done and things work again, take a deep breath and
>>>>> have a look at the most recent Gentoo news item ($ eselect news read)
>>>>> which
>>>>> explains it all, more or less. Then decide whether the above is a
>>>>> long
>>>>> term solution, and if not start reading docs about writing udev rules.
>>>>>
>>>>> Yes, it's a pain in the backside. But at least with Gentoo, you've a
>>>>> good chance of fixing things like this quickly.
>>>>>
>>>>>> Your help is greatly appreciated,
>>>>>> Nick
>>>> in my case it is still eth0:
>>>> ifconfig
>>>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>>>> inet 192.168.178.21 netmask 255.255.255.0 broadcast
>>>> 192.168.178.255
>>>> inet6 fe80::1e6f:65ff:fe87:6f6a prefixlen 64 scopeid
>>>> 0x20<link>
>>>> ether 1c:6f:65:87:6f:6a txqueuelen 1000 (Ethernet)
>>>> RX packets 4647305 bytes 6693078055 (6.2 GiB)
>>>> RX errors 0 dropped 0 overruns 0 frame 0
>>>> TX packets 2943816 bytes 226871998 (216.3 MiB)
>>>> TX errors 0 dropped 1 overruns 0 carrier 0 collisions 0
>>>>
>>>> sys-fs/udev
>>>> Available versions: (~)168-r2[1] [M]171-r10 197-r8^t{tbz2}
>>>> (~)198-r6^t{tbz2} (~)199-r1^t{tbz2} 200^t{tbz2} **9999^t {acl
>>>> action_modeswitch build debug doc edd extras +firmware-loader floppy
>>>> gudev hwdb introspection keymap +kmod +openrc +rule_generator selinux
>>>> static-libs test}
>>>> Installed versions: 200^t{tbz2}(18:30:31
>>>> 29.03.2013)(firmware-loader gudev hwdb keymap kmod openrc -acl -doc
>>>> -introspection -selinux -static-libs)
>>>>
>>>> I did keep net.eth0....
>>> Is your eth0 NIC a module (modprobed), or built in the kernel?
>> r8169 41918 0
>> module
>
> For me its built in.
>
> - Jörg
>
>
>
