Fedora Linux Support Community & Resources Center
  #1  
Old 10th May 2012, 07:29 PM
DBelton Offline
Administrator
 
Join Date: Aug 2009
Posts: 7,320
linuxfirefox
Interesting ethernet naming in F17

I just installed F17 from the TC3 dvd a few days ago, and I noticed something odd in the ethernet adapter naming in F17.

This was a fresh install, completely wiping the drive before installing, etc... But it had F16 on it prior and F16 named the ethernet adapter em1

After install F17, I noticed that it now names the ethernet adapter em13

I thought that the new naming was supposed have consistent naming. There were absolutely no hardware changes between the F16 install and the F17 install, so what happened?
Reply With Quote
  #2  
Old 11th May 2012, 12:35 AM
sonoran Offline
Registered User
 
Join Date: May 2005
Location: Sonoran Desert
Posts: 2,313
linuxfirefox
Re: Interesting ethernet naming in F17

I'll go you 3 better - my device name was "em16" for a week or so. Thinking to bypass that I added "biosdevname=0" to GRUB_CMDLINE_LINUX in /etc/default/grub and ran grub2-mkconfig, which produced some interesting effects:

1) eth0 is back as my connection name, the intended result, but also...

2) my grub2 menu was completely redesigned, new font, new layout. Okay, but...

3) I now get a "file not found" error message, "press any key to continue" which disappears of its own volition after about 5 seconds, and the gdm login appears. Except when it doesn't and the machine reboots.

And there are now 3 penguin icons in a row across the top of the screen. Cool.

I vaguely recall that disabling biosdevname also requires changing something in the network startup scripts, which could account for the error message. But I've decided to leave things as they are for the moment, making this a sort of game: will Fedora boot, or will it refuse and spit me back out to the grub legacy menu? Maybe this is a new feature - a Fedora locus poenitentiae?
Reply With Quote
  #3  
Old 11th May 2012, 08:32 AM
DBelton Offline
Administrator
 
Join Date: Aug 2009
Posts: 7,320
linuxfirefox
Re: Interesting ethernet naming in F17

Quote:
Originally Posted by sonoran View Post
I'll go you 3 better - my device name was "em16" for a week or so. Thinking to bypass that I added "biosdevname=0" to GRUB_CMDLINE_LINUX in /etc/default/grub and ran grub2-mkconfig, which produced some interesting effects:

1) eth0 is back as my connection name, the intended result, but also...

2) my grub2 menu was completely redesigned, new font, new layout. Okay, but...

3) I now get a "file not found" error message, "press any key to continue" which disappears of its own volition after about 5 seconds, and the gdm login appears. Except when it doesn't and the machine reboots.

And there are now 3 penguin icons in a row across the top of the screen. Cool.

I vaguely recall that disabling biosdevname also requires changing something in the network startup scripts, which could account for the error message. But I've decided to leave things as they are for the moment, making this a sort of game: will Fedora boot, or will it refuse and spit me back out to the grub legacy menu? Maybe this is a new feature - a Fedora locus poenitentiae?

Yea.. The updated grub2 is supposed to have a nice theme, but it doesn't work on my machine here. No theme, and It just sets the video mode to one my monitor doesn't support and I get a nice "Input not supported" message on my monitor until the video driver resets the mode.

I had to go in and force it to a mode that my monitor supports. But I do get those cool penguins as well
Reply With Quote
  #4  
Old 11th May 2012, 03:04 AM
nonamedotc Offline
Community Manager
 
Join Date: Mar 2011
Location: USA
Posts: 3,752
linuxfirefox
Re: Interesting ethernet naming in F17

That's quite interesting. In my laptop, it shows up as eth0. I have not changed anything. This was installed using TC2 and updated regularly. Here are the relevant portions

Code:
 ifconfig 
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xfc000000-fc020000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 109  bytes 21159 (20.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 109  bytes 21159 (20.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.24  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::226:c6ff:fe4b:6cc4  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 897  bytes 594273 (580.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 754  bytes 116547 (113.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
When I was running F16, it was eth0 as well. However, in my other laptop, F16 shows em1. I have not yet installed F17 on that. Are there any configuration entries that affect these? What causes them to be different in different hardware?

Last edited by nonamedotc; 11th May 2012 at 03:07 AM.
Reply With Quote
  #5  
Old 11th May 2012, 03:59 AM
Mister B Offline
Registered User
 
Join Date: May 2008
Posts: 48
windows_xp_2003ie
Re: Interesting ethernet naming in F17

I think this is due to Fedora moving to Consistent Network Device Naming. It looks like it was a feature of F15, but maybe it's part of a wider rollout now.
__________________
--Matt Broekemeier
Reply With Quote
Reply

Tags
ethernet, f17, interesting, naming

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora 16 ethernet port naming "secrets" p1* to eth* scott9harvey0l Servers & Networking 5 27th July 2012 08:40 PM
F16 iptables with new eth naming ScottFavor Security and Privacy 1 21st November 2011 03:45 PM
F16 Naming ask4nutz Wibble 4 24th April 2011 08:24 PM
Ethernet cards naming issue. flux Servers & Networking 1 27th January 2010 03:08 PM
naming ftp address mohtasham1983 Servers & Networking 6 25th December 2005 06:28 PM


Current GMT-time: 12:39 (Wednesday, 20-08-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat