Official Realtek Driver Binary 1.95 For 2.4.4 Release
Just an update for anyone reading this old thread for older releases, there are much simpler instructions that worked for me on the 2.5.1 release, I now recommend avoiding any messy compilation and upload of drivers and just using the instructions here:
cooljimy84 last edited by
same here, pkg remove and then install
tho i had to add the following to /boot/loader.conf
Version 1.96.04 for FreeBSD 13, if needed.
I'm running into this issue on PFSense 2.6. Does anyone have a working driver?
pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/realtek-re-kmod-197.00.pkg
echo 'if_re_load="YES"' >> /boot/loader.conf.local echo 'if_re_name="/boot/modules/if_re.ko"' >> /boot/loader.conf.local
Then reboot. Make sure it reports the new driver in the boot log.
A Former User last edited by A Former User
Loading and installing over the Webgui
Console or log in via SSH
pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/latest/All/realtek-re-kmod-197.00.pkg pkg install -f -y realtek-re-kmod-197.00.pkg
loader.conf.local and entries must be created by yourself
You only need the 'pkg add' command to install it.
You don't need to do anything with the existing module if you have specified the path to the alternative module in the _name variable.
Thanks all! :)
Oxyacetylene last edited by Oxyacetylene
I am having this same issue, but the repository listed above is giving me a 403 forbidden error. I am on pfSense 2.6 and just set up a new Zimaboard to use for a firewall. My WAN internet connection has dropped multiple times over the last 24 hours.
EDIT: I used
pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/realtek-re-kmod-197.00.pkg
2nd Edit: Once I installed this package the firewall behaved even worse. I went back in after a reboot and unchecked the option to disable hardware checksum offload. Rebooted again. Watching now to see if things are stable. I had checked this option to disable the offload as an attempt to fix the problem, before loading the driver.
3rd Update: The driver didn't fix the problem. The WAN connection went down again in less than 24 hours. The LAN would still ping, but the web GUI would not load. I have pulled the Zimaboard out of service for now. The next attempt will be with a PCIe dual Intel NIC on the Zimaboard. This isn't really ideal but I am going to give it a shot.
Was it showing watchdog timeouts from the Realtek driver in the logs?
Are you sure the alternative driver was actually loading?
@stephenw10 I definitely had the watchdog timeouts in the log. As far as the driver loading, I need to verify that. When I ran the pkg add command, in the output I saw the relevant lines indicating to load the driver, but to your point I need to actually look to see if the driver is loading. I'll try to do that soon and report back. Would I verify by just looking at the kernel modules? I work from home and the drops were causing me a big headache so I just pulled it for now, but I will try to set it up soon on the bench and see what's what.
Check the boot logs. The alternative driver shows the driver version on each NIC it attaches to like:
re0: <Realtek PCIe GbE Family Controller> port 0x1000-0x10ff mem 0xf7a00000-0xf7a00fff,0xf7900000-0xf7903fff irq 16 at device 0.0 on pci1 re0: Using Memory Mapping! re0: Using 1 MSI-X message re0: ASPM disabled re0: version:1.97.00 re0: Ethernet address: 00:0d:b9:37:30:10
gregeeh last edited by gregeeh
I had manually installed Realtek Drivers on versions prior to 2.6 and assumed they just carried over to 2.6.
I have no /boot/loader/conf.local file and my /boot/loader.conf is:
[2.6.0-RELEASE][admin@pfSense.localdomain]/boot: cat loader.conf kern.cam.boot_delay=10000 kern.ipc.nmbclusters="1000000" kern.ipc.nmbjumbop="524288" kern.ipc.nmbjumbo9="524288" opensolaris_load="YES" zfs_load="YES" kern.geom.label.gptid.enable="0" kern.geom.label.disk_ident.enable="0" autoboot_delay="3" hw.hn.vf_transparent="0" hw.hn.use_if_start="1" net.link.ifqmaxlen="128" [2.6.0-RELEASE][admin@pfSense.localdomain]/boot:
So it appears the latest Realtek Driver is not installed.
Should I install it?
Id Refs Address Size Name 1 25 0xffffffff80200000 3aed878 kernel 3 1 0xffffffff84089000 9860 opensolaris.ko 4 1 0xffffffff84311000 1000 cpuctl.ko 5 1 0xffffffff84312000 1400 wmt.ko 6 1 0xffffffff84314000 8e10 aesni.ko 7 1 0xffffffff8431d000 bf8 coretemp.ko 8 1 0xffffffff8431e000 11aa8 dummynet.ko
@gregeeh said in Official Realtek Driver Binary 1.95 For 2.4.4 Release:
Should I install it?
Only if you're seeing a problem with the in-kernel driver.
If you do decide to add it the loader line should be added to /boot/loader.conf.local
gregeeh last edited by
@stephenw10 Thanks for your reply. Where is the best place to look for problems?
You won't have to look. When it fails it usually stops passing traffic entirely. But you can looks for log entries in the main system log showing watchdog timeouts from the re(4) driver.
@stephenw10 I booted it up on the bench and sure enough, the new driver was not loading. I had thought that the message I saw during the package install meant that the needed lines were being added to the boot config, but that is not the case. I have now manually added the lines to /boot/loader.conf.local and verified the new driver module is loading at boot. I am going to put it back in service soon and will report back.
@stephenw10 It has now been over 24 hours and no stability issues that I have noticed. I believe the issue was resolved with the driver. Thanks!
Still stable with no discernible drops over the last few days. I think the issue is resolved with the driver! Many thanks to those who posted the info!