From a thread in the 4.1 Topic area

 

The realtec drivers are a p.i.t.a.    The last time I tried building it got compile errors    I'll have to look to see of someone fixed this.

 

Did anything happen to change/fix the realtek driver problem?  Because of the weird drive allocation problem I experienced I didn't want to try a 4.0 to 4.2 update if nothing has changed in regard to realtek drivers between 4.1 & 4.2.

 

Thanks,

 

Mark.

Sorry I don't think so.  Please give it try though.  If you're worried about your drive assignments, just completely back up the contents of the 'config' directory (including super.dat).  If after booting 4.2 you see assignments moving around, you can restore.

Sorry I don't think so.  Please give it try though.  If you're worried about your drive assignments, just completely back up the contents of the 'config' directory (including super.dat).  If after booting 4.2 you see assignments moving around, you can restore.

 

Nope, still bad  :'(

 

21% Network Utilization on 4.0

An Unusable 0.06% under 4.2beta2

 

Edit:- Should I be thinking of buying a NIC to prevent this being an issue every update?

 

Mark.

Realtek recently released an update to their r8168 driver which compiles successfully against the latest linux kernel source.  This has been incorporated in 4.2-beta3, please give it a try.

 

Some background.

 

There are 2 "r8169" drivers:

1. created/supported by Realtek, let's call this "Realtek r8169"

2. the r8169 driver included with linux kernel source, let's call this "linux r8169".

 

Near as I can tell, the "linux r8169" driver started life as a snapshot of the "Realtek r8169" driver "many versions ago".  As each new linux kernel is released, "someone" in kernel development makes necessary changes to "linux r8169" driver to make sure it compiles and works.  This someone also makes updates from time to time.  But it seems like the "Realtek r8169" driver is more up-to-date as far as chip support goes, but not in terms of which kernel it will compile with.

 

There are also 2 other Realtek drivers:

3. created/supported by Realtek, let's call this "r8168".

4. created/supported by Realtek, let's call this "r1000".

 

The r1000 driver was the one created by Realtek to support their PCI-Express NIC chips, but this driver has not been updated in a long time; instead Realtek is now supporting their PCI-Express NIC chips with their r8168 driver, instead of r1000.

 

So... if you have a PCI-Express Realtek chip, you want r8168.

If you have a PCI Realtek chip, you want Realtek's r8169 driver.

 

Unfortunately, Realtek's r8169 driver has not been updated to compile with latest linux kernel source (but r8168 has).

 

What a mess, eh? 

What a mess these Realtek chipsets cause!

 

Unfortunately not fixed in that beta release, same 0.06% utilization .

 

Mobo: Asus P5LD2-SE R2.0 (RTL8111B PCI-E Gb LAN controller)

 

I have 3 of these and I didn't actually mean to order this Mobo, I meant to order the P5LD2-VM SE and I think I would have been ok then as that has an Intel chipset.

 

If this isn't resolveable then I guess the Realtek RTL8111B PCI-E chipset just isn't supported under unRAID.  If that is the case is there a specific GigLan NIC a UK user can recommend to get around this problem?

 

Thanks for all your efforts here,

 

Mark.

It could be a very simple problem that can be fixed using 'ethtool'.  But we don't have any motherboards at present with Realtek NIC's so I can't experiment with this.

Would the

 

Realtek RTL8111B/RTL8168B/RTL8111/RTL8168/RTL8111C Linux driver for kernel 2.6.x (Support x86 and x64)

Version: 8.003.00 Dated:- 2007/8/28

 

From the realtek site be a newer one than the one you tried?

 

Thanks,

 

Mark.

Yes, that's the driver included in the 4.2-beta builds.  I picked up a Asus P5RD2-VM motherboard which has a Realtek RTL8111B chip on it, so we'll try to figure out what's going on with that driver.

Yes, that's the driver included in the 4.2-beta builds.  I picked up a Asus P5RD2-VM motherboard which has a Realtek RTL8111B chip on it, so we'll try to figure out what's going on with that driver.

 

That's great, I'll hold out for a driver solution before buying new mobo's or Nics & Sata Cards (x3 )

 

Thanks,

 

Mark.

Just curious, what driver is it using now in 4.2?  I use 'ethtool -i eth0' to show the network driver and its version.

 

Just curious, what driver is it using now in 4.2?  I use 'ethtool -i eth0' to show the network driver and its version.

 

 

My system is being used right now under 4.0 so I can't go back to one of the beta's to tell you, but I'll do it tomorrow.

 

Thanks,

 

Mark.