Bug 117659
| Summary: | 3c59x device eth0 does not seem to be present | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard Ayer III <rwa7> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | kishlaya.b |
| 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: | 2004-03-08 19:54:12 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: | |||
Well, I just went hunting to try to find the problem again. It seems that removing the specification of the IRQ as one of the options when the system loads the module, fixes the problem. Although, I know that the specified IRQ was correct. So I guess this is still a bug that needs to be fixed, but there is a workaround. There is no need to specify IRQs for PCI cards. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Description of problem: As of about a week ago, every time I boot up, I see a message '3c59x device eth0 does not seem to be present' when the system attempts bring up eth0. Once I log in, I have to insmod the 3c59x module, but it loads immediately and DHCP configures properly. I have a 3Com 3C905B-TX PCI NIC card. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. boot the system 2. 3. Actual Results: have to insmod 3c59x after system is booted Expected Results: module should be loaded during boot up Additional info: