Bug 1081362
| Summary: | RHEL 7.0 unable to identify network card Realtek 8211 series - which was ok in RHEL6 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Prosun Prodhan <linuxprosun> | ||||||||
| Component: | kernel | Assignee: | John Greene <jogreene> | ||||||||
| kernel sub component: | NIC Drivers | QA Contact: | Yulong Pei <ypei> | ||||||||
| Status: | CLOSED INSUFFICIENT_DATA | Docs Contact: | |||||||||
| Severity: | high | ||||||||||
| Priority: | unspecified | CC: | ajb, dcbw, jfeeney, linuxprosun, toracat | ||||||||
| Version: | 7.0 | ||||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-03-13 19:03:12 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Please attach the output of the 'lspci' and 'dmesg' commands, thanks! Created attachment 880123 [details]
dmesg of RHEL7b
Created attachment 880125 [details]
lspci output
lspci output. The problem is related to on-board (ASUS M4N68T series) ethernet chip. Now I am searching for any extra (PCI slot) ethernet card having the same (RTL8111) series chip, to find if works or not. Till date not able to find the card.
Also informed ASUS tech team - regarding the fact. They just replied that they have escalated to proper channel. But if RHEL7final released without solving the bug, then our around 30 PC will not be able to accept RHEL7.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. lspci shows this ethernet: 00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2) It will help if you show us the output of 'lspci -nn' because that includes the device IP pairings. I suspect the device in question uses the forcedeth driver (but this needs confirmation with the IDs). If so, this is one of the many drivers that are now disabled in RHEL 7 [1]. One temporary solution will be to use the kmod-forcedeth package from ELRepo [2]. [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Migration_Planning_Guide/sect-Red_Hat_Enterprise_Linux-Migration_Planning_Guide-Removed_Packages.html#sect-Red_Hat_Enterprise_Linux-Migration_Planning_Guide-Removed_Packages-Removed_Drivers [2] http://elrepo.org/tiki/kmod-forcedeth We do need that lspci -nn to insure the below is accurate, but assuming it is for the the forcedeth.ko module. I checked rhel6 and rhel7 trees. The .config in RHEL6 does indeed enable that device by default: CONFIG_FORCEDETH=m CONFIG_FORCEDETH_NAPI=y But it's, BY DEFAULT, disabled in RHEL7. The driver does still exist in the rhel7 source tree and you can pretty easily build a kernel with it enabled if you wish. The driver source in the RHEL7 tree is located in drivers/net/ethernet/nvidia/ The Kconfig in that directory tell you what to do to change the .config for a kernel build to include it. But, sent us the lspci -nn output to be sure! (In reply to John Greene from comment #7) > But it's, BY DEFAULT, disabled in RHEL7. The driver does still exist in the > rhel7 source tree and you can pretty easily build a kernel with it enabled > if you wish. Yes, but you do not need to build the whole kernel. You can build just the forcedeth kernel module. That's exactly what ELRepo did to produce the kmod-forcedeth package. As a bonus, because it is kABI-tracking, it survives kernel updates transparently. I think this is the best/easiest solution at this moment. By the way a kernel with forcedeth enabled will be available from CentOS as the "centosplus" kernel [1] if anyone prefers that way as an interim solution. [1] http://bugs.centos.org/view.php?id=7359 (In reply to John Greene from comment #7) > We do need that lspci -nn to insure the below is accurate, but assuming it > is for the the forcedeth.ko module. > But, sent us the lspci -nn output to be sure! I'm not aware of any change in soon to be available 7.1 RHEL for this but I'd give it a try. Since I haven't seen anything in the way of the requested lspci -nnv to help you I'm closing this due to age. Please reopen if you have further information that would help us help you. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Created attachment 879299 [details] output of lsmod Description of problem: While installing RHEL7.0beta to M4N68T-M LE V2 systems, the onboard ethernet controller (RTL 8211 series) wont work. But it working fine with RHEL6.0. Version-Release number of selected component (if applicable): RTL 8211 How reproducible: Just install RHEL7.0b on using this mobo, and it will not be able to find the NIC Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: