Bug 324891
| Summary: | forcedeth device eth0 does not seem to be present | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Riku Seppala <riku.seppala> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | aabdulla, jonstanley, manfred, plinhardt | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2008-02-15 14:56:53 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Riku Seppala
2007-10-09 14:01:01 UTC
Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Closing per previous comment. If you can provide the requested information, please feel free to re-open this bug. Fedora 9 alpha, I still have this problem. Except now I have to manually setup network every time I log in. HP laptop + Linux = disaster Created attachment 294322 [details]
lspci -vvv
Created attachment 294323 [details]
dmesg
Please take a look at this, it's really getting annoying to set up network manually every time I boot. On dmesg I can see: udev: renamed network interface eth0 to eth2 Every boot it renames one higher, why is that? I noticed error on shutdown,something like: can't remove /etc/resolv.conf.predhclient.ethX X being the current number (changes on every boot) Looking in your dmesg this doesn't look too promising: forcedeth 0000:00:14.0: Invalid Mac address detected: 00:00:00:00:00:00 forcedeth 0000:00:14.0: Please complain to your hardware vendor. Switching to a random MAC. forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:00:6c:cc:3c:12 forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3 Not a lot that we can do about keeping things in the same order if the MAC address is changing with every boot. Shit. Ok the ethernet is broken, I'm sending it for repair. Maybe I get lucky and all the other bugs I've seen are hardware related and goes away when they switch the motherboard. :) OK, since the hsrdware is at fault, I'll close this NOTABUG. I think this evaluation of the situation is not correct. This is a bug, but the bug is in the hardware firmware. It is not that the hardware is broken, it's the NIC card doesn't reliably produce a consistent MAC address. If you do a Google search on "MAC address 00:00:6C", you'll find a lot of people dealing with this issue with this vendor. What would be useful information is specific steps in the Redhat environment in how to have the boot-chain spoof the correct MAC address. For instance, this article explains it on another flavor of linux platform, but because Redhat has different system files different steps are necessary: How to fix invalid MAC address on Nforce MCP network controller http://www.besy.co.uk/debian/how_to_fix_invalid_mac_address_on_nforce_mcp_network_controllers -paul |