January 10, 201313 yr I get no network on rc8a or rc9a but im ok with rc5 I'm running a abit ip35 pro with the following nics: Onboard LAN 2 - Realtek RTL8110SC - PCI Gigabit Ethernet controller RC5 screen RC9a Screen Any help would be appreciated Cheers
January 10, 201313 yr Hi Marvel, ive got the same problem in RC9a, however another unRAID user has a solution that seems to work for me on RC8a http://lime-technology.com/forum/index.php?topic=22615.msg201529#msg201529 take a look, please let me know if this works for you, there appear to be differences in the driver that are causing issues FYI: I'm also running a Realtek RTL8110SC chipset and this seems to work great for me Cheers KYTON
January 10, 201313 yr Author Thanks for the heads up Kyton, I'll check it out. I might have to purchase an intel nic, I don't want to but I don't think this will get fixed
January 10, 201313 yr Bear in mind that I can not support any user-modified kernel. I am preparing 5.0-rc9b which will come in two flavors: 5.0-rc9b-r8169 (uses linux driver for Realtek chipsets) 5.0-rc9b-r8168 (uses Realtek vendor-supplied driver) If you don't have a Realtek NIC, then thank your lucky stars, and use the -r8169 version.
January 10, 201313 yr Bear in mind that I can not support any user-modified kernel. I am preparing 5.0-rc9b which will come in two flavors: 5.0-rc9b-r8169 (uses linux driver for Realtek chipsets) 5.0-rc9b-r8168 (uses Realtek vendor-supplied driver) If you don't have a Realtek NIC, then thank your lucky stars, and use the -r8169 version. to stop the confusion, can you name it a tad differently. The driver name only for the changed rc9. I use a realtek and I'm running rc9a fine, but don't ask me if its a 8168 or 8169. If you released it for the start with that naming convention I'd probably still be rooting around trying to work out which one I should use.
January 10, 201313 yr Bear in mind that I can not support any user-modified kernel. I am preparing 5.0-rc9b which will come in two flavors: 5.0-rc9b-r8169 (uses linux driver for Realtek chipsets) 5.0-rc9b-r8168 (uses Realtek vendor-supplied driver) If you don't have a Realtek NIC, then thank your lucky stars, and use the -r8169 version. to stop the confusion, can you name it a tad differently. The driver name only for the changed rc9. I use a realtek and I'm running rc9a fine, but don't ask me if its a 8168 or 8169. If you released it for the start with that naming convention I'd probably still be rooting around trying to work out which one I should use. Ok, how about this: 5.0-rc9b (for everyone) 5.0-rc9b-r8168 (for those that need the Realtek driver) I want everyone to be using the "normal" release, and if we get to a point where the -r8168 version is no longer necessary (like it was some time ago), then I will stop producing it.
January 10, 201313 yr Bear in mind that I can not support any user-modified kernel. I am preparing 5.0-rc9b which will come in two flavors: 5.0-rc9b-r8169 (uses linux driver for Realtek chipsets) 5.0-rc9b-r8168 (uses Realtek vendor-supplied driver) If you don't have a Realtek NIC, then thank your lucky stars, and use the -r8169 version. to stop the confusion, can you name it a tad differently. The driver name only for the changed rc9. I use a realtek and I'm running rc9a fine, but don't ask me if its a 8168 or 8169. If you released it for the start with that naming convention I'd probably still be rooting around trying to work out which one I should use. Ok, how about this: 5.0-rc9b (for everyone) 5.0-rc9b-r8168 (for those that need the Realtek driver) I want everyone to be using the "normal" release, and if we get to a point where the -r8168 version is no longer necessary (like it was some time ago), then I will stop producing it. That would make more sense for me.
January 10, 201313 yr Bear in mind that I can not support any user-modified kernel. I am preparing 5.0-rc9b which will come in two flavors: 5.0-rc9b-r8169 (uses linux driver for Realtek chipsets) 5.0-rc9b-r8168 (uses Realtek vendor-supplied driver) If you don't have a Realtek NIC, then thank your lucky stars, and use the -r8169 version. I understand completly, not expecting you to support mods, i was trying to confirm a hunch with the drivers Thanks for the effort your putting in with this Cheers KYTON
January 11, 201313 yr If you don't have a Realtek NIC, then thank your lucky stars, and use the -r8169 version. or alternatively if you have purchased a NIC recommended in http://lime-technology.com/wiki/index.php/Hardware_Compatibility - the DLink DGE528T. This NIC creates the same issues - so when will somebody remove it from the hardware compatibility list?
January 12, 201313 yr If you don't have a Realtek NIC, then thank your lucky stars, and use the -r8169 version. or alternatively if you have purchased a NIC recommended in http://lime-technology.com/wiki/index.php/Hardware_Compatibility - the DLink DGE528T. This NIC creates the same issues - so when will somebody remove it from the hardware compatibility list? Edit the WIKI and add a note that the card seems to be no longer compatible as of this version. If a second user can confirm then they can mark the card an not compatible.
January 12, 201313 yr Have you fellows tried ver 5.0-rc10 yet? It includes two Realtek driver files-- r8161 and r8169. Most the people who have reported success are using a r8186 driver. I am assuming that you folks need the drivers contained in the r-8169 file. (See the first post in the rc10 release post for more information.)
January 12, 201313 yr OK - will do Just tried RC10 and still no luck with this NIC - DLink DGE528T. Even though RC10 appears to have made some efforts in this direction (inclusion of Realtek version r8168-8.035.00 ethernet driver and Realtek version r8169-6.017.00 ethernet driver?) no joy!? Really disappointing. Will have to wind back to piotrasd's hacked rc8.... and think about buying a replacement card. Anyone suggest a card that works now (and fingers crossed .. in the future?)
January 12, 201313 yr intel. here's an example of one of their pci-e cards: http://www.ncix.com/products/?sku=37926&vpn=EXPI9301CTBLK&manufacture=Intel
January 12, 201313 yr Nice! Thank you. Based in the UK so will google Brit suppliers now. Thanks again. Got to get out of this Realtek loop
January 12, 201313 yr OK - will do Just tried RC10 and still no luck with this NIC - DLink DGE528T. Even though RC10 appears to have made some efforts in this direction (inclusion of Realtek version r8168-8.035.00 ethernet driver and Realtek version r8169-6.017.00 ethernet driver?) no joy!? Really disappointing. Will have to wind back to piotrasd's hacked rc8.... and think about buying a replacement card. Anyone suggest a card that works now (and fingers crossed .. in the future?) Researched the DGE528T and found out Dlink provides a driver for called 'r1000': http://askubuntu.com/questions/39172/how-do-i-install-the-driver-for-a-dlink-dge-528t However that thing won't compile on our kernel. This is another case of the "linux r8169" driver being more comprehensive; somewhere around 2.6.11 support for that chip was added in there: http://www.linuxquestions.org/questions/linux-hardware-18/ethernet-card-dge-528t-and-kernel-2-6-a-350564/ Unfortunately until the 3.4.x maintainer backports update linux r8169 driver that card won't be supported by unRaid. This would be the first time ever any h/w support got dropped after having been supported that I'm aware of. Wish I had a better answer for you.
January 13, 201313 yr Thanks for the detail/taking the situation so seriously - it is appreciated. Am going to root around in a computer graveyard for an old Intel gigabit NIC - but if that fails then plan to order a brand new one! Thanks again for taking it seriously - these are not expensive devices and I have probably spent far more time than I should installing/rolling back each new release since rc5. Intel NIC here I come
Archived
This topic is now archived and is closed to further replies.