Bug 43148
Summary: | BAD: Module doesn't work for the 21040 NIC | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Kim Futtrup Petersen <wintersilence> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WORKSFORME | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | pekkas |
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: | 2003-06-06 13:07:54 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: |
Description
Kim Futtrup Petersen
2001-06-01 12:21:01 UTC
This is related to drivers, changing to kernel component. This might also be a local configuration issue; check: 1) dmesg output when loading the driver 2) whether your switch is using autonegotiation (probably yes); if not, you need to tune /etc/modules.conf 3) 'lspci' output; which driver is used? 4) 'mii-tool -v'. Also, does the de4x5 driver work instead of the tulip driver work ? Closed: Inactive |