Bug 12974
| Summary: | network eth0 device fails to start after upgrade | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Chris Runge <crunge> |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | herrold, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-06-26 03:30:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I confirm this happens with both 3c509 (ISA), and the 3c59x drivers (PCI). Additionally, this occurs with the DHCP device setup as well. It's a failover problem from the bad upgrade logic causing the correct modutils to not be installed. |
upgraded from 6.2 to beta 2 during reboot I get an error during networking startup; after logging in ifconfig only shows the loopback device, not the eth0 device (which was working fine under 6.2) /etc/rc.d/init.d/network restart gives this eth0: error fetching interface information: Device not found Setting network parameters [OK] Bringing up interface lo [OK] Bringing up interface eth0 Delaying eth0 initialization. [FAILED] less /etc/sysconfig/network NETWORKING=yes HOSTNAME=crunge.runge FORWARD_IPV4=no GATEWAYDEV=eth0 GATEWAY=192.168.1.1 less /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO-static BROADCAST=192.168.1.255 IPADDR-192.168.1.2 NETMASK=255.255.255.0 NETWORK=192.168.1.0 ONBOOT=yes lsmod does not show the module for my 3Com networking card (in fact, it shows no modules loading--I wonder if this is related to bug 12972--yep, I think that's the problem (I just did a depmod -a ; /etc/rc.d/init.d/network restart and everything is fine)