Bug 181703 - [re] [patch] Fix Realtek 8111G Ethernet controller not being detected
Summary: [re] [patch] Fix Realtek 8111G Ethernet controller not being detected
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-net (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-31 12:40 UTC by Neel Chauhan
Modified: 2016-06-05 15:33 UTC (History)
0 users

See Also:


Attachments
file.diff (815 bytes, patch)
2013-08-31 12:40 UTC, Neel Chauhan
no flags Details | Diff
file.diff (504 bytes, patch)
2013-08-31 12:40 UTC, Neel Chauhan
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Neel Chauhan freebsd_committer freebsd_triage 2013-08-31 12:40:00 UTC
When I boot FreeBSD 9.1 with the Realtek 8111G controller on an Asus H87M-E motherboard, it says "Unknown H/W revision".

dmesg snapshot:
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf3104000-0xf3104fff,0xf3100000-0xf3103fff irq 18 at device 0.0 on pci3
re0: Using 1 MSI-X message
re0: turning off MSI enable bit.
re0: Chip rev. 0x4c000000
re0: MAC rev. 0x00000000
re0: Unknown H/W revision: 0x4c000000

Fix: I did set up patches to support the ethernet controller. The patches are:

---and---
How-To-Repeat: 1. Load FreeBSD on a computer with a Realtek 8111G controller
2. See the dmesg output that says that the HW revision is unknown
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-09-01 05:33:24 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net


Over to maintainer(s).
Comment 2 Neel Chauhan freebsd_committer freebsd_triage 2013-09-11 00:26:23 UTC
Update: I tested the patch. It just makes the ethernet controller useless
until you unplug your computer.
Comment 3 Neel Chauhan freebsd_committer freebsd_triage 2016-06-05 15:33:16 UTC
Many years later, FreeBSD has gotten 8111G support. I'm closing this bug as it's irrelevant now. It was a failed attempt at kernel hacking (along with another attempt to put Haswell support, which also failed).