wired ethernet disabled between reboots, was: when startup delays become bugs
awilliam at redhat.com
Tue May 21 16:40:00 UTC 2013
On Sun, 2013-05-19 at 09:59 -0400, Nico Kadel-Garcia wrote:
> On Fri, May 17, 2013 at 1:10 AM, Chris Murphy <lists at colorremedies.com> wrote:
> > On May 16, 2013, at 10:49 PM, Dan Williams <dcbw at redhat.com> wrote:
> >> On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
> >>> On May 16, 2013, at 3:36 PM, Chris Murphy <lists at colorremedies.com> wrote:
> >>>> Rebooted. I still have the problem. Wired connection is Off on each reboot. This happens even if I regress to the 3.9.0 kernel that's used on the Live media, which works on every boot. Flummoxed.
> >>> I found part of the problem:
> >>> [root at F19 network-scripts]# cat ifcfg-ens5
> >>> ….
> >>> ONBOOT=no
> >>> But why is it set to no? Once set to yes, system reboots with p5p1 enabled.
> >> Either it was set to "no" during installation, or something set it to
> >> "no" after the install. NetworkManager won't ever change that value by
> >> itself. Something else (like the GUI, or directly editing that file
> >> with VIM/emacs/etc) had to change it.
> > It was set to no during installation, user unaware of this.
> > The Gnome shell > Settings > Network > Wired > gear button > Identity > Connect automatically checkbox is what affects the ONBOOT= value. A similarly named checkbox is checked in anaconda on Fedora 18, but is unchecked if the cable is unplugged in anaconda on Fedora 19. So the resulting installation gets an ONBOOT=no and stays that way until the user finds, five layers deep, this weird Connect automatically checkbox.
> > But this bug has brought me to a plethora of buggy behavior in the Gnome Settings Network panel, so maybe the misery was worth it.
> *THIS*. *This* kind of thing is why NetworkManager remains unusable
> for production network configuratoin.
Hyperbole -> /dev/null.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
More information about the devel