[SOLVED] eth0 won't start without NM in F16

Basher52 · 01-17-2012, 04:26 PM

These are my settings and works in F14.
Is there a bug in F16? no update are available as now right now.
or am I missing something else here.

ifconfig eth0

Quote:

eth0 Link encap:Ethernet HWaddr 0F:19

4:B7:85:1B
inet addr:192.168.67.92 Bcast:192.168.67.255 Mask:255.255.255.0
inet6 addr: fb80::211:d4fe:fec7:76eb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:141 errors:0 dropped:0 overruns:0 frame:0
TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14807 (14.4 KiB) TX bytes:24863 (24.2 KiB)
Interrupt:23

Quote:

ifcfg-eth0
HWADDR=0F:129:B7:85:1B
IPV6INIT=no
UUID="5fb16be0-1bf1-8dfb-15a2-ddedd6ffee13"
IPADDR0=192.168.67.92
DNS1=1.2.3.4
PREFIX0=24
DEFROUTE="yes"
IPV4_FAILURE_FATAL="yes"
NM_CONTROLLED=no
BOOTPROTO=none
GATEWAY0=192.168.67.250
DNS2=2.3.4.5
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
NAME="eth0"
NETMASK=255.255.255.0
USERCTL=no
PREFIX=24

I've tried everything I can think of and what I've found googling, but still I have to 'ifup' it after a restart.

Anyone else wanna take a crack at this cos I just can't find the "error"
I don't wanna use NM, but it does work with it.

kbp · 01-17-2012, 10:16 PM

I believe the device naming may have changed on you.. try 'emX'

Basher52 · 01-18-2012, 11:40 AM

emX instead of eth0? or am I just stupid here

It is called eth0 when I use NM
Was originally named 'System eth0' (I think) but removed that unnecessary 'System' thing

kbp · 01-18-2012, 03:31 PM

Yeah .. not sure on the details but mine has changed since F14. Did you upgrade or do a fresh install ?

Basher52 · 01-18-2012, 03:32 PM

Just found what you meant by this, from F15 this is done, but there is nothing else but eth0.

Quote:

ls /etc/sysconfig/networking/profiles/default/
hosts ifcfg-eth0 network resolv.conf

Quote:

ls /etc/sysconfig/networking/devices/
ifcfg-eth0

The only NIC I got after a start/restart is 'lo'
I can't ifup any emX but I can ifup this eth0

kbp · 01-18-2012, 03:49 PM

Do you have an eth0 alias in /etc/modprobe.conf ? .. I'm guessing you upgraded and it kept the old name.

Maybe try this:
- service NetworkManager stop (may be 'systemctl stop NetworkManager.service')
- service network stop
- remove any ethX references from /etc/modprobe.conf
- remove any /etc/sysconfig/network-scripts/ifcfg-ethX files
- remove /etc/udev/rules.d/70-persistent-net.rules
- chkconfig NetworkManager off
- reboot

Then just configure networking manually, find the discovered device, add an ifcfg-<dev> file:
DEVICE=<dev>
TYPE=Ethernet
BOOTPROTO=none
IPADDR=x.x.x.x
NETMASK=x.x.x.x
ONBOOT=yes
USERCTL=no
NM_CONTROLLED=no

Basher52 · 01-18-2012, 04:22 PM

I don't have a file called: /etc/modprobe.conf
The only modprobe-thing I got is this directory:

Quote:

ls /etc/modprobe.d/
anaconda.conf blacklist.conf dist-alsa.conf dist.conf dist-oss.conf udlfb.conf

This is a clean install of Fedora 16
I do that to test things before I do the upgrade of the other machines I got running F14 and even F13.

On the F14 machines I just stopped Network Manager, told the NIC to ONBOOT=yes, restarted the network or rebooted and it all worked.
The NIC is embedded so the name should be as you said, emX.

PS. When I installed this I did make a name change of the NIC from 'System eth0' to just 'eth0' if that might have changed something, but I doubt it since it should have been emX anyways, right?

kbp · 01-18-2012, 04:34 PM

So what do you get for 'grep eth /var/log/mesages' ?

Basher52 · 01-18-2012, 04:41 PM

grep eth /var/log/mesages

Quote:

Jan 18 23:35:53 dubb kernel: [ 9.123707] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
Jan 18 23:35:53 dubb kernel: [ 9.230135] forcedeth 0000:00:0a.0: PCI INT A -> Link[APCH] -> GSI 23 (level, low) -> IRQ 23
Jan 18 23:35:53 dubb kernel: [ 9.850465] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 0F:19

4:B7:85:1B
Jan 18 23:35:53 dubb kernel: [ 9.852905] forcedeth 0000:00:0a.0: highdma csum gbit lnktim desc-v3
Jan 18 23:36:16 dubb avahi-daemon[804]: Registering new address record for fb80::211:d4fe:fec7:76eb on eth0.*.
Jan 18 23:36:17 dubb avahi-daemon[804]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.67.92.
Jan 18 23:36:17 dubb avahi-daemon[804]: New relevant interface eth0.IPv4 for mDNS.
Jan 18 23:36:17 dubb avahi-daemon[804]: Registering new address record for 192.168.67.92 on eth0.IPv4.

kbp · 01-18-2012, 07:16 PM

Here's the relevant change info: http://fedoraproject.org/wiki/Featur...rkDeviceNaming

Can you try removing /etc/udev/rules.d/70-persistent-net.rules and rebooting ?

Basher52 · 01-19-2012, 01:19 PM

Got the same result

70-persistent-net.rules

Quote:

# PCI device 0x10de:0x0057 (forcedeth) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="0F:19

4:B7:85:1B", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

This is weird lol

Basher52 · 01-25-2012, 02:43 PM

I couldn't figure this one out so I'm gonna reinstall it again.

I'm gonna mark it solved, but as of now... it ain't