• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Replacing realtek "re" driver

DoBoY

New Member


Messages: 6

#26
I'm been up for 18 days with my compiled driver so far. Performance is very good on a 120Mbit WAN link. I push it to the max for hours and still no more "watchdog timeout" errors anymore.
 

chrcol

Well-Known Member

Thanks: 15
Messages: 377

#27
guys I managed to purchase a jetway dual port intel i350 mini pcie card for my braswell N3150 NUC.

I did find it odd I only managed to find one retailer worldwide selling it and now its vanished of their website, very odd. It is listed on jetway's site but they dont sell direct.

For those who are looking tho and do have a mini pcie slot, then the model number is ADMPEIDLA and I see there is one on ebay albeit not cheap.

Mine was £50 for a 2 port card, the one on ebay is even more.

However it has been reliable and the shipped igb drivers are compatible.

minipc.de and mercateo have them also actually.
 

mmac

New Member

Thanks: 4
Messages: 8

#28
Hello everyone! Today i assembled my next DIY home server based on ASRock J4205-ITX running FBSD 11.0-RELEASE-p7. After the installation and initial configuration, i run some first (disappointing) tests on my new hardware. By the way, the machine is pretty good in its power consumption which is about 18 watts in active/idle with two spinning HDDs. The main purpose of the machine should be "headless file serving", therefore it has to feed several gigabytes of AVCHD-Files from my Handycam.

And here is the problem: the NIC is going to say goodbye (watchdog-messages in screen terminal) each time the network traffic goes up by copying large files.

The internal NIC is a:

Code:
re0@pci0:1:0:0:    class=0x020000 card=0x81681849 chip=0x816810ec rev=0x11 hdr=0x00
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device      = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class        = network
    subclass   = ethernet
And this is the Reason why i'm now here. I tried to compile the actual driver from Realtek according to the steps described in this thread without success. The point is that the driver version related to the description is v191 but i only found v192 on Realtek's page. Is there any chance that the built-in driver is going to be updated in future FBSD patches, or did i really have to compile the driver by myself? Imho FBSD is currently unusable with Realtek cards, and I dont want to add another (pci-)nic only because there is a software bug. :(

Thank you all! :)
 

mmac

New Member

Thanks: 4
Messages: 8

#30
I followed the instructions and build my own kernel with the latest realtek driver "if_re.ko" (v192) as a module. First load tests with some large files (+4 Gigabytes) shows no more watchdog interrupts. This workaround works very well.

Thank you all! :)
 

SpaceAdventureCobra

New Member


Messages: 3

#32
Hi. I have just finished building my pfsense firewall with 2x onboard NICs, and having some trouble with the firewall becoming non-responsive from time to time, I have come here to this forum post, because my logs says re0: watchdog timeout.

I googled before I bought my system and I read that Realtek 8168 NICs was stable. This is my motherboard; https://www.gigabyte.com/Motherboard/GA-J3455N-D3H-rev-10#ov - but it is not stable,, after putting VLANs etc on the LAN side of it and pushing heavy traffic it sometimes requires shutting it off and on due to NICs becoming unresponsive (it does answer ping requests though, but no routing..)

Anyways;

Reading this forum post, and this one - https://forums.freebsd.org/threads/55306/ I am thinking the solution will be to load the Realtek driver as a module. It has now updated to v1.94, http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false - and I am wondering if anyone has success with using that one? I cannot seem to find the other versions of this driver.

Running pfsense with a 2.4.2-RELEASE-p1 (amd64)
built on Tue Dec 12 13:45:26 CST 2017
FreeBSD 11.1-RELEASE-p6

Code:
[2.4.2-RELEASE][root@pfSense.localdomain]/root: pciconf -v -l
re0@pci0:3:0:0:   class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet
re1@pci0:4:0:0:   class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet
[2.4.2-RELEASE][root@pfSense.localdomain]/root:
 

SpaceAdventureCobra

New Member


Messages: 3

#33
Anyone else having trouble with this, I found some more information here: in comment #42 the user "franco" stated (...) Realtek released the FreeBSD driver version 1.93 with built-in support for FreeBSD 11.0. All the more reason to go forward (...)
https://forum.opnsense.org/index.php?topic=4183.30

And it seems to me that the existing Realtek driver from FreeBSD should have been replaced by version Opnsense 17.1.2,, and downloading it now Opnsense is version 17.7.5, so it should work "out of the box" without any fiddling.

Hm, already started to know my way around pfsense, such a shame to switch to Opnsense :)

Now if someone could just point to to the "doubleclick this" install_new_driver_realtek_setup.exe file to setup the new drivers :eek:
 

borjam

New Member


Messages: 3

#35
I have had similar problems with a NUC6AYH, with one of those hideous re GbE interfaces. Unfortunately it's not possible to replace it.

In my case it kinda worked, but I tried to do something a bit stupid (like running an Elasticsearch node on it, and, to make it worse, using a iSCSI volume as its storage) and the interface would die with a watchdog error after a minute or so.

I am running 11.1-STABLE from two or three weeks ago. I reproduced the problem several times and, interestingly, when forcing a reboot with the interface frozen I got this error:

Code:
<5>re0: link state changed to UP
re0: watchdog timeout
<5>re0: link state changed to DOWN
<5>re0: link state changed to UP
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop... g_vfs_done():da0[WRITE(offset=14498955264, length=131072)]error = 6
g_vfs_done():da0[WRITE(offset=14499086336, length=131072)]error = 6
g_vfs_done():da0[WRITE(offset=14499250176, length=131072)]error = 6
g_vfs_done():da0[WRITE(offset=21167616, length=1024)]error = 6
panic: cannot reassign paging buffer
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff806e5bb7 at kdb_backtrace+0x67
#1 0xffffffff8069fb26 at vpanic+0x186
#2 0xffffffff8069f993 at panic+0x43
#3 0xffffffff80762043 at reassignbuf+0x273
#4 0xffffffff8074336e at bdirty+0x2e
#5 0xffffffff807421ca at brelse+0x10a
#6 0xffffffff80744cc7 at bufdone+0x87
#7 0xffffffff805f26b2 at g_io_deliver+0x202
#8 0xffffffff805ef952 at g_disk_done+0x122
#9 0xffffffff802df933 at dadone+0x18a3
I have updated to the latest driver downloaded from here,

http://www.realtek.com/downloads/do...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

It was simple. Compiling a kernel without the re device, compiling this module and replacing the if_re.ko from the kernel directory with this new one.

It had a silly problem when compiling but it was trivial to fix. It failed to find one of its include files because it searched for a different path.

Other than that it's running solid for several hours now. It is losing a packet now and then (I am keeping a ping to check that), but nothing serious.
 

tingo

Daemon

Thanks: 320
Messages: 1,815

#36
Did you also create a bug report for the bug with the FreeBSD driver related to your hardware?
 

borjam

New Member


Messages: 3

#37
Not yet. Besides, it survived for several hours but the driver crashed this morning.

The machine is alive but the network interface is failing. So, something else to look at :/

I'll create a bug report if I can get more information. And unfortunately it's not possible to replace the bloody Ethernet interface. It's on the motherboard and there's no PCI slots to install a proper card. Sigh.
 
Top