Official Realtek Driver Binary 1.95 For 2.4.4 Release
-
@breakaway said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:
Unzip & Place "if_re.ko" file at "/boot/kernel"
Change ownership and permissions on the if_re.ko file
chown root:wheel if_re.ko
chmod 0555 if_re.koThen edit "/boot/loader.conf” to add this line:
if_re_load=“YES"
Reboot.
Then go to diagnostics > command prompt in the WebGUI
Run the command
kldstat
If you did everything properly you’ll see “if_re.ko” in the list that comes up. If not, the driver isn’t loaded.
Tip for anyone having a issue, If you copied and pasted the if_re_load=“YES" line fix the first “ and make it " yes there is a difference. /facedesk
Works like a charm, once I found that =P
Thanks for the updated driver and taking the time to compile, I have a ZOTAC ZBOX CI323 Nano with dual Realtek and a 2nd Generic system with a single Realtek (router on a Stick).
-
Odd - looks like the double quotes are messed up. You can thank my Phone for that! I’ll update it.
Always use kldstat to verify if the driver if_re.ko is loaded!
Shell Output - cat /boot/loader.conf
kern.cam.boot_delay=10000
kern.ipc.nmbclusters="1000000"
kern.ipc.nmbjumbop="524288"
kern.ipc.nmbjumbo9="524288"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
if_re_load=“YES”
autoboot_delay="3"
hw.usb.no_pf="1”Shell Output - kldstat
Id Refs Address Size Name
1 20 0xffffffff80200000 2d9a7d0 kernel
2 1 0xffffffff82f9c000 381f00 zfs.ko
3 2 0xffffffff8331e000 a3a0 opensolaris.ko
4 1 0xffffffff83329000 7d2c0 if_re.ko
5 1 0xffffffff83911000 10a0 cpuctl.ko
6 1 0xffffffff83913000 2ec0 cryptodev.ko
7 1 0xffffffff83916000 c80 coretemp.ko -
@breakaway upper case is fine, it is the left/backwards/upside down quotation mark that if copy pasted makes the loader throw a syntax error and not load the driver.
- about a month later
-
Could you post a guide on how to compile the driver? Would be nice to know what is needed from pfsense sources etc and if any configs is needed.
-
Here's a link of the guide. The files are a little bit old so use the newer version (Realtek driver v1.95 and FreeBSD 11.2), but the process is still the same.
https://gist.github.com/jovimon/524e116471f249626fd2ccd141f3fe05
-
Also, is there any way to “slipstream” the driver and the modification to the loader.conf so that it will automatically include this driver when installing from media?
-
would it be possible to put driver into a pfS package?
-
@love-it-again thanks a ton
-
It's very unlikely this could ever be added as an official package. Is it even using a license that would allow it?
The correct way to resolve this would be to fix the upstream FreeBSD driver. I've never looked to see what the differences are there.
Steve
- about a month later
-
Just got finished putting this driver on my Odroid H2. This SBC has been nice but the NIC's seem to drop connection about a once a day.
Is there something I can do to track the state of the NIC's and the drivers to see what's happening when they lock up? I'd be willing to revert to the stock drivers just to find out why a daily reboot has been necessary.
-
Not easily. You'd probably need to add debug messages to the driver for example. Maybe recompile it.
Are you (were you) seeing the watchdog timeouts?
Steve
-
@stephenw10 I hadn't been seeing the watchdog timeouts but I hadn't been looking for them either. What's the best way to look for them?
-
They would be in the system log if you are hitting that issue.
Steve
-
Also, at least in my experience using the driver built in to FreeBSD, the watchdog timeout is pretty easy to provoke by running iperf tests against the LAN interface. I see that the Odroid H2 has dual RTL8111Gs whereas I, and I believe most others using the official Realtek driver, have been running Zotac machines that I believe have RTL8111Es. Both of those use the same driver, but I think it's fair to say that the RTL8111G is less "battle tested" with this driver. Have you also confirmed that the driver is indeed being loaded and used by looking for it in the output of ldstat?
- 2 months later
-
I have made FreeBSD 12 package.
https://drive.google.com/file/d/1Ch4Z_w7gpbrpavQ4KhPUXUzYhRyzqnye/view?usp=sharing
I dont consider it my work - I have just packed it in one archive. It is stable for me on 12.0 p3 more than
"sed -i -e 's/TAILQ_FOREACH/CK_STAILQ_FOREACH/g' if_re.c" -
Will pfSense 2.5.0 / FreeBSD 12.0-RELEASE-p3 improve the built-in Realtek drivers situation at all?
-
stephenw10 Netgate Administratorlast edited by stephenw10 Mar 18, 2019, 6:11 PM Mar 18, 2019, 5:58 PM
I would guess no. Not much activity in the FreeBSD repo:
https://github.com/pfsense/FreeBSD-src/commits/RELENG_2_5/sys/dev/re - 8 days later
-
I've installed precomplied version of this driver for Nettop Gigabyte GB-BACE-3000 - working good with PFSence 2.4.4-RELEASE-p1. Uptime 31 days.
Thanks for the driver @TheNarc! -
I am currently using a Gigabyte GA-C1007UN-D
It has two realtek NICS either RTL8111E or RTL811F (online reviews conflict) I have never noticed this error, but would use this driver if it would increase stability. using the current 2.4.5 dev build.Any advice on specific iperf test that is known to kick off this problem? traffic to the rtr, from the router, do I need tons of simultaneous streams?
I would like to see it fail before I spent the time.
-
@mervincm In my experience, I didn't need to set any exotic iperf options. Just running a few iperf tests between a host on the LAN and the LAN port of the pfSense machine was enough to reproduce the error.