Bug 126115
| Summary: | FC2 Fails to bring up eth0 (natsemi) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Thomas <byteenable> |
| Component: | kernel | Assignee: | Jeff Garzik <jgarzik> |
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2 | CC: | nhorman, peterm |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-12-07 18:52:40 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: | |||
Forgot, Via Apollo Pro266T North Bridge. Is there anything interesting in "dmesg" or /var/log/messages about the ethernet ? I have tested SUSE also, it will not bring up the nic either. I have installed the 2.6.6 kernel from kernel.org and it will not bring the nic up either. It seems that once I boot with 2.4.2X kernel, any 2.6 can boot thereafter. Nothing in dmesg. Just the deferred message during init. My guess is that it has to do with IRQ routing (BIOS & registers), the kernel and kudzu. My BIOS is old (2001). Byte My workaround is to install FC2 and reboot. Install FC1 2.4 kernel from CD and reboot. Let kudzu find new network device, make sure nic works. Reboot with 2.6 kernel, and everything is happy. Byte I can try doing a clean FC2 install here, but I've tried deleting my kudzu config several times now, and rebooting under varying kernels from pre FC2 releases, to the latest out of bitkeeper, and they all seem to run the card properly, I have no problems send or receiving traffic. When you see this problem occur, can you cat /proc/interrupts and see if the requisite interrupt counter increments while you try to send or receive traffic? If it doesn't then your most likely correct, in that this is a BIOS issue. I do not have this hardware anymore and cannot test. Sorry. Byte |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 Description of problem: I dont know if this is kudzu related or not, but this was the closest category I could think of. FC2 fails to bring up eth0 and obtain an IP address. I can manually start eth0 and transmit packets, but cannot receive any. It appears to be interrupt related (hunch). I can install the kernel from FC1, boot with that kernel and eth0 comes up and works. I can then boot with the FC2 kernel and eth0 works! I tried all combo's of acpi=off pci=noacpi apm=off. I also tried the chmod -x /sbin/mii-tool Hardware Dual Pentium III 1.13GHz/133 1 GigaByte DDR NVidia GeForce 5700 FX Sound Blaster Live! Hauppage WinTV DVD ROM Two IDE Hard Drives NetGear FA-XXX (natsemi driver) 00:0a.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller Subsystem: Netgear: Unknown device f312 Flags: bus master, medium devsel, latency 32, IRQ 129 I/O ports at d000 Memory at e3000000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install Fedora Core 2 2. Reboot 3. eth0 will not come up (natsemi) Actual Results: eth0 is deferred Expected Results: eth0 to come up and obtain an IP address. Additional info: