limetech Posted January 12, 2013 Share Posted January 12, 2013 Download | Release Notes There are a couple critical bug fixes in here and everyone is encouraged to upgrade to this release. Please note: if you are upgrading from 4.7 or lower, please run the "New Permissions" utility available on the Utils page. This is necessary in order for the 5.0 security model to work correctly. If necessary, you will be able to downgrade back to 4.7 with no ill effects from this. If you are upgrading from an earlier 5.0-beta or 5.0-rc release, you will also need to run the "New Permissions" utility again unless you upgraded to 5.0-rc9 or -9a and did so yesterday. Also, if you have a Realtek NIC of any type, please post here whether it works with this release or not. I think I have the history of Realtek NIC drivers under linux sorted out: It turns out for GigEthernet that Realtek actually provides two drivers for linux: r8168: for newer NIC's (RTL8111B/RTL8168B/RTL8111/RTL8168 RTL8111C/RTL8111CP/RTL8111D(L) RTL8168C/RTL8111DP/RTL8111E RTL8168E/RTL8111F/RTL8411 r8169: for older NIC's (RTL8110SC(L) (RTL8110S/RTL8110SB(L)/RTL8169SB(L)/RTL8169S(L)/RTL8169) The Realtek 'r8169' driver is different from the "built-in" linux Realtek NIC kernel driver also called "r8169". The fact that the linux driver is named the same as a Realtek vendor driver has produced all kinds of confusion and is very unfortunate. I guess the guys that originally created the linux driver probably started with Realtek's r8169, but the two code bases are very different these days. So it appears that if you want to support the entire range of Realtek GigE NIC chips using the Realtek supplied drivers, you have to use both 'r8169' supplied by Realtek as well as 'r8168' supplied by Realtek. If you want to use the single stock linux driver to support all the Realtek GigE NIC's then you could just use 'r8169' included in the kernel sources. Except for one thing: the version of linux r8169 in the kernel unRaid is using (3.4.x) does not include support for a couple of the newer Reaktek NIC's. This support is in later kernels, e.g., 3.7.x but I'm not prepared to upgrade to this kernel just yet. Confusing? Try sorting this all out to being with Bottom line is this: I really really don't want to have to produce two downloads for each release, one with Realtek-supplied drivers and one with kernel-supplied drivers. This would make my life much more complicated and this I don't need. So I'm hoping the inclusion of both Realtek r8169 and r8168 drivers will solve this issue. There is much more I can write about my opinion of Realtek's linux support. Let me just say that I no longer have any motherboards around with Realtek NIC's and we will probably never again offer any motherboards with Realtek NIC's in any new server product moving forward, 'nuff said. Quote Link to comment
TheDragon Posted January 12, 2013 Share Posted January 12, 2013 Sounds like a real headache! Thanks for the update though, will give it a test drive ASAP Sent from my Samsung Galaxy S2 using Tapatalk 2 Quote Link to comment
S80_UK Posted January 12, 2013 Share Posted January 12, 2013 Thanks again, Tom. I have RTL8111E on my Asrock H67M-ITX. With the -RC10 build I get a stable 1 gigabit/sec connection (was OK with -RC9A and all previous RC builds as well in my case). Writes and reads to / from the server with large files (e.g. blu-ray rips) appear fine. More testing tomorrow. Quote Link to comment
dalben Posted January 12, 2013 Share Posted January 12, 2013 Installed and everything so far seems ok. Quote Link to comment
limetech Posted January 12, 2013 Author Share Posted January 12, 2013 Installed and everything so far seems ok. Realtek NIC? Quote Link to comment
lainie Posted January 12, 2013 Share Posted January 12, 2013 Is rc10 using the same 3.4.24 kernel that rc9 did? Quote Link to comment
limetech Posted January 12, 2013 Author Share Posted January 12, 2013 Is rc10 using the same 3.4.24 kernel that rc9 did? Yes. Quote Link to comment
dalben Posted January 12, 2013 Share Posted January 12, 2013 Installed and everything so far seems ok. Realtek NIC? Yep Jan 12 11:14:35 tdm kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded (System) Jan 12 11:14:35 tdm kernel: r8168 0000:03:00.0: irq 51 for MSI/MSI-X Jan 12 11:14:35 tdm kernel: eth%%d: RTL8168E/8111E at 0xf841e000, f4:6d:04:70:09:44, IRQ 51 Jan 12 11:14:35 tdm logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.10 broadcast 192.168.1.255 netmask 255.255.255.0 (Network) Jan 12 11:14:35 tdm kernel: r8168: eth0: link down (Network) Jan 12 11:14:35 tdm logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1 (Network) Jan 12 11:14:38 tdm kernel: r8168: eth0: link up (Network) Jan 12 11:14:39 tdm kernel: r8168: eth0: link up (Network) Quote Link to comment
sureguy Posted January 12, 2013 Share Posted January 12, 2013 Thanks for the release. It was released as I was rebooting my unRAID box after updating to 9a. I grinned while grumbling about my poor timing. I'll run an overnight parity check for the fun of it. Quote Link to comment
jumperalex Posted January 12, 2013 Share Posted January 12, 2013 Let me just say that I no longer have any motherboards around with Realtek NIC's and we will probably never again offer any motherboards with Realtek NIC's in any new server product moving forward, 'nuff said. Seems like you should have some around for testing [shrug]. I am tempted though to just install my netgear pci nic [shrug] Quote Link to comment
jumperalex Posted January 12, 2013 Share Posted January 12, 2013 Realtek 8112L, seems to be working. In fact it booted right to 1000mbit/s. often with RC8 and just now with RC9a it would boot to 100mib/s and i would have to unplug/plug the network cable. Read from array share: 40mb/s write to cache: 48mb/s Quote Link to comment
mikejp Posted January 12, 2013 Share Posted January 12, 2013 8111D working fine with a stable 1 gigabit/sec connection Quote Link to comment
luca Posted January 12, 2013 Share Posted January 12, 2013 I think that at the top in this rc10 thread there should be a mention of needing to run the new permission util. Assuming that this is still necessary in rc10 (I'm moving from rc8). Quote Link to comment
jbartlett Posted January 12, 2013 Share Posted January 12, 2013 RTL8168E/8111E working like a champ. Jan 11 20:22:06 NAS kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded (System) Jan 11 20:22:06 NAS kernel: r8168 0000:07:00.0: irq 50 for MSI/MSI-X Jan 11 20:22:06 NAS kernel: eth%%d: RTL8168E/8111E at 0xf8516000, 20:cf:30:f5:5a:c4, IRQ 50 Quote Link to comment
jinjorge Posted January 12, 2013 Share Posted January 12, 2013 finally up and running. had to reboot the server 3-4 times because the first time I rebooted after upgrading to rc10, the array was reporting as full, all drives were reporting 0 free disk space. Didn't capture a log while this was all happening..... Quote Link to comment
limetech Posted January 12, 2013 Author Share Posted January 12, 2013 I think that at the top in this rc10 thread there should be a mention of needing to run the new permission util. Assuming that this is still necessary in rc10 (I'm moving from rc8). Good idea. First post modified, thanks. Quote Link to comment
Mikee Posted January 12, 2013 Share Posted January 12, 2013 Sucessful upgrade from rc6 here, with realtek NIC. Jan 12 15:18:01 Tower kernel: eth0: Identified chip type is 'RTL8168C/8111C'. (Network) Jan 12 15:18:04 Tower dhcpcd[923]: eth0: carrier acquired (Network) Jan 12 15:18:04 Tower kernel: r8168: eth0: link up (Network) Quote Link to comment
limetech Posted January 12, 2013 Author Share Posted January 12, 2013 Sucessful upgrade from rc6 here, with realtek NIC. Remember to run 'New Permissions' script at some point. Quote Link to comment
Joe L. Posted January 12, 2013 Share Posted January 12, 2013 It works for me too on SuperMicro C2SEE motherboard: Jan 12 00:08:41 Tower kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded Jan 12 00:08:41 Tower kernel: r8168 0000:04:00.0: irq 45 for MSI/MSI-X Jan 12 00:08:41 Tower kernel: eth%%d: RTL8168C/8111C at 0xf8522000, 00:30:48:b0:06:00, IRQ 45 Jan 12 00:08:41 Tower kernel: r8168: This product is covered by one or more of the following patents: US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and US6,327,625. Jan 12 00:08:41 Tower kernel: eth0: Identified chip type is 'RTL8168C/8111C'. Jan 12 00:08:41 Tower kernel: r8168 Copyright © 2012 Realtek NIC software team <[email protected]> Joe L. Quote Link to comment
bonienl Posted January 12, 2013 Share Posted January 12, 2013 It is working for me too Jan 12 05:39:06 vesta kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded Jan 12 05:39:06 vesta kernel: r8168 0000:04:00.0: irq 43 for MSI/MSI-X Jan 12 05:39:06 vesta kernel: eth%%d: RTL8168D/8111D at 0xf8524000, 48:5b:39:50:fa:6b, IRQ 43 Jan 12 05:39:06 vesta kernel: eth0: Identified chip type is 'RTL8168D/8111D'. Jan 12 05:39:06 vesta kernel: r8168 Copyright © 2012 Realtek NIC software team Jan 12 05:39:06 vesta kernel: This program comes with ABSOLUTELY NO WARRANTY; for details, please see . Jan 12 05:39:06 vesta kernel: This is free software, and you are welcome to redistribute it under certain conditions; see . Quote Link to comment
cyrnel Posted January 12, 2013 Share Posted January 12, 2013 Very nice, Tom. This is acting somewhat faster than rc8. 5GB test file. Single test each, so FWIW. Copied locally via shell: -protected array drive -> cache drive 97MB/s -cache drive -> protected array drive 42MB/s SMB client: -protected array drive -> Win7 Pro SSD 105MB/s -Win7 Pro SSD -> protected array drive 49MB/s Thanks! Quote Link to comment
crazytony Posted January 12, 2013 Share Posted January 12, 2013 Download | Release Notes There is much more I can write about my opinion of Realtek's linux support. Let me just say that I no longer have any motherboards around with Realtek NIC's and we will probably never again offer any motherboards with Realtek NIC's in any new server product moving forward, 'nuff said. Capital A Awesome! I can't wait for final. It's going to be hard to find cost-effective non-realtek solutions in the general market. I tried when building my latest system (in December) due to the realtek issues but all the boards I could find had a Realtek chipset. Quote Link to comment
peter_sm Posted January 12, 2013 Share Posted January 12, 2013 This is my log, but I never had any issue at all on previous releases. Jan 12 07:52:05 tower kernel: r8168: This product is covered by one or more of the following patents: US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and US6,327,625. Jan 12 07:52:05 tower kernel: eth0: Identified chip type is 'RTL8168C/8111C'. (Network) Jan 12 07:52:05 tower kernel: r8168 Copyright (C) 2012 Realtek NIC software team <[email protected]> Jan 12 07:52:05 tower kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded (System) Jan 12 07:52:05 tower kernel: r8168 0000:03:00.0: irq 40 for MSI/MSI-X Jan 12 07:52:05 tower kernel: eth%%d: RTL8168C/8111C at 0xf84da000, 00:24:1d:83:b5:1c, IRQ 40 Quote Link to comment
opentoe Posted January 12, 2013 Share Posted January 12, 2013 I'm running RC8 now and going to upgrade to this one. I change my GO file to update to the latest samba, using 3.6.8. The release notes in this version says it is version 3.6.10. This may sound like a weird question, but what version is newer? Does that 3.6.10 mean a "10" at the end, or a "1"? Which then of course it would be newer. But, who knows. Hence why I'm asking. Thanks. Quote Link to comment
warhead Posted January 12, 2013 Share Posted January 12, 2013 I'm running RC8 now and going to upgrade to this one. I change my GO file to update to the latest samba, using 3.6.8. The release notes in this version says it is version 3.6.10. This may sound like a weird question, but what version is newer? Does that 3.6.10 mean a "10" at the end, or a "1"? Which then of course it would be newer. But, who knows. Hence why I'm asking. Thanks. Yes it's meant to be read as a '10' and thus is newer than '8' Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.