Bug 448040 - network device not activated on boot
network device not activated on boot
Product: Fedora
Classification: Fedora
Component: upstart (Show other bugs)
i686 Linux
low Severity high
: ---
: ---
Assigned To: Casey Dahlin
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-22 23:40 EDT by Syam
Modified: 2014-06-18 04:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-22 23:51:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Screenshot of network device configuration (49.84 KB, image/png)
2008-05-22 23:40 EDT, Syam
no flags Details
/etc/sysconfig/networking/devices/ifcfg-eth0 (282 bytes, text/plain)
2008-05-22 23:42 EDT, Syam
no flags Details

  None (edit)
Description Syam 2008-05-22 23:40:59 EDT
Description of problem:

Even though I've selected 'Activate device when computer starts' for my network
adaptor, it is not activated on boot.
After every boot, I've to manually go to Network configuration or Network device
control and activate the device.
Attached are the screenshots of my network settings and
/etc/sysconfig/networking/profiles/default/ifcfg-eth0 (which is same as

How reproducible:

Steps to Reproduce:
1. Configure Fedora 9 network adaptor
2. Select 'Activate on boot'
3. Reboot and find that the device is not activated
Actual results:
Device is not activated on boot.

Expected results:
Device is activated on boot.

Additional info:
NetworkManager service: Not enabled
IP: Static (no DHCP)
ipv6: disabled
Comment 1 Syam 2008-05-22 23:40:59 EDT
Created attachment 306443 [details]
Screenshot of network device configuration
Comment 2 Syam 2008-05-22 23:42:28 EDT
Created attachment 306444 [details]
Comment 3 Bill Nottingham 2008-05-22 23:51:55 EDT
Either set NM_CONTROLLED to 'yes' (the Controlled by NetworkManager checkbox) or
enable the 'network' service in the service control.

Note You need to log in before you can comment on or make changes to this bug.