January 12, 201313 yr Successfully upgraded from RC5 Jan 12 11:35:58 WinklerNAS kernel: r8169 Gigabit Ethernet driver 6.017.00-NAPI loaded Jan 12 11:35:58 WinklerNAS kernel: r8169: 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 11:35:58 WinklerNAS logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Jan 12 11:35:58 WinklerNAS kernel: eth0: RTL8169SC/8110SC at 0xf8492c00, 00:01:2e:3c:11:d8, IRQ 16
January 12, 201313 yr 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. Perhaps you missed it - As also discussed in the RC9 thread here http://lime-technology.com/forum/index.php?topic=25184.msg219229#msg219229
January 12, 201313 yr Does this release include the fix that was going to be part of RC9b ?? That was a potential version number for the Realtek fixes. RC10 is intended to be a "one size fits all" solution to that problem, hence Tom's request for users to test and report success or failure especially if they use a Realtek network chip in their server.
January 12, 201313 yr 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. 10 is a later version. I just commented out the lines that load 3.6.8 on the GO script and upgraded to RC10.
January 12, 201313 yr Upgraded to 9a then 10. All working A-ok here. Hopefully this can come GM and Tom can get on with sorting AFP, the Performance issues etc
January 12, 201313 yr Upgraded to RC10. Everything seems to be working correctly. I am using an intel PCI NIC. Conducting a parity check now.
January 12, 201313 yr Upgraded from rc9a, so far rc10 is running fine and stable on my server with Realtek 8111F (Asus P8H77-M), same network speed (~110MB/s on both directions, with client PC running W7, a bit less with XP) and same read/write speed on the protected array (120/30-35MB/s) as with rc8 and rc9a. Thanks. Jan 12 09:50:58 unRAID 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 09:50:58 unRAID kernel: eth0: Identified chip type is 'RTL8168F/8111F'. Jan 12 09:50:58 unRAID kernel: r8168 Copyright (C) 2012 Realtek NIC software team
January 12, 201313 yr all fine here new samba seems snappier Jan 12 15:23:51 P8H67 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 15:23:51 P8H67 kernel: eth0: Identified chip type is 'RTL8168E/8111E'. (Network) Jan 12 15:23:51 P8H67 kernel: r8168 Copyright (C) 2012 Realtek NIC software team <[email protected]> Jan 12 15:23:51 P8H67 kernel: This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. Jan 12 15:23:51 P8H67 kernel: This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>.
January 12, 201313 yr 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. Intel PCI-E NICs are pretty cheap
January 12, 201313 yr 2 servers with Realtek nics upgraded successfully : Jan 12 14:51:57 Tower kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded Jan 12 14:51:57 Tower kernel: r8168 0000:03:00.0: irq 42 for MSI/MSI-X Jan 12 14:51:57 Tower kernel: eth%%d: RTL8168F/8111F at 0xf845e000, 30:85:a9:40:44:e0, IRQ 42 Jan 12 14:51:57 Tower kernel: eth0: Identified chip type is 'RTL8168F/8111F'. Jan 12 14:51:57 Tower kernel: r8168 Copyright (C) 2012 Realtek NIC software team Jan 12 13:01:35 Tower2 kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded Jan 12 13:01:35 Tower2 kernel: r8168 0000:03:00.0: irq 45 for MSI/MSI-X Jan 12 13:01:35 Tower2 kernel: eth%%d: RTL8168E/8111E at 0xf8506000, bc:ae:c5:c2:cc:e4, IRQ 45 Jan 12 13:01:35 Tower2 kernel: eth0: Identified chip type is 'RTL8168E/8111E'. Jan 12 13:01:35 Tower2 kernel: r8168 Copyright (C) 2012 Realtek NIC software team 'New Permissions' still running on one of them.
January 12, 201313 yr 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. Intel PCI-E NICs are pretty cheap That's not the only consideration. Many small form-factor builds using Mini-ITX boards have Realtek LAN chips and the only available PCI or PCI-e slot is often used for additional SATA ports. I greatly sympathise with Tom's problem of trying to deal with Realtek support under Linux, but I don't think the problem will go away that easily.
January 12, 201313 yr Well despite earlier enthusiasm 10 will not boot. I can't provide a log because it doesn't get past the bootloader (the SYSLINUX...) Steps: 1. Working 8a stick 2. Power down 3. Transfer stick to PC 4. Copy BZROOT/BZIMAGE for rc10 5. Transfer stick back 6. Boot 7. Hang on bootloader (Syslinux copyright Peter Anvin... etc) 8. Power down 9. Transfer stick to PC 10. Load BZROOT/BZIMAGE for rc8a 11. Transfer stick back 12. Boot 13. Working rc8a unraid Same machine, same stick, same process (copy bzimage/bzroot): 8a works for me but 10 just won't boot. ASUS F1A75V-Pro/4GB ram/2x AOC-SAS2LP-MV8/10 3TB Seagates
January 12, 201313 yr Well despite earlier enthusiasm 10 will not boot. I can't provide a log because it doesn't get past the bootloader (the SYSLINUX...) Steps: 1. Working 8a stick 2. Power down 3. Transfer stick to PC 4. Copy BZROOT/BZIMAGE for rc10 5. Transfer stick back 6. Boot 7. Hang on bootloader (Syslinux copyright Peter Anvin... etc) 8. Power down 9. Transfer stick to PC 10. Load BZROOT/BZIMAGE for rc8a 11. Transfer stick back 12. Boot 13. Working rc8a unraid Same machine, same stick, same process (copy bzimage/bzroot): 8a works for me but 10 just won't boot. ASUS F1A75V-Pro/4GB ram/2x AOC-SAS2LP-MV8/10 3TB Seagates Sounds like a bad download..
January 12, 201313 yr This includes the fix that was going to be in RC9b as well doesn't it. Good times. So....this is it then. Assuming all goes well with this over the next week, this will become version 5 final. Exciting for the community.
January 12, 201313 yr Anyone try using a combination of C2SEE and AOC-SASLP-MV8? If so it might finally be time for me to jump on 5.0 bandwagon...
January 12, 201313 yr Well despite earlier enthusiasm 10 will not boot. I can't provide a log because it doesn't get past the bootloader (the SYSLINUX...) Steps: 1. Working 8a stick 2. Power down 3. Transfer stick to PC 4. Copy BZROOT/BZIMAGE for rc10 5. Transfer stick back 6. Boot 7. Hang on bootloader (Syslinux copyright Peter Anvin... etc) 8. Power down 9. Transfer stick to PC 10. Load BZROOT/BZIMAGE for rc8a 11. Transfer stick back 12. Boot 13. Working rc8a unraid Same machine, same stick, same process (copy bzimage/bzroot): 8a works for me but 10 just won't boot. ASUS F1A75V-Pro/4GB ram/2x AOC-SAS2LP-MV8/10 3TB Seagates I just: Stop the array Go to tower/flash on the network Rename bzroot and bzimage then copy the bzroot and bzimage from RC10 to tower/flash reboot the server and RC10 up and running No need to transfer stick to PC. Updating takes just a few minutes. You might try to download again or you didn't eject the stick properly fromthe PC after copying the files.
January 12, 201313 yr Sounds like a bad download.. ZIP utilizes a CRC to validate the files contained in the archive. The CRC should prevent incomplete archives from extracting properly. That being said, I re-downloaded the archive and went through the process again without any luck.
January 12, 201313 yr Sounds like a bad download.. ZIP utilizes a CRC to validate the files contained in the archive. The CRC should prevent incomplete archives from extracting properly. That being said, I re-downloaded the archive and went through the process again without any luck. Same happened to me so I ran the makebootable.bat one the flash drive and that fixed my problems. Please try.
January 12, 201313 yr OK so I'm bringing this up here because we're talking about realtek NIC's. So in testing my 8112L is detected as 579: Jan 12 11:01:07 Tower kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded 580: Jan 12 11:01:07 Tower kernel: r8168 0000:02:00.0: irq 41 for MSI/MSI-X 581: Jan 12 11:01:07 Tower kernel: eth%%d: RTL8168D/8111D at 0xf84c4000, f4:6d:04:22:6d:84, IRQ 41 589: Jan 12 11:01:07 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. 590: Jan 12 11:01:07 Tower kernel: eth0: Identified chip type is 'RTL8168D/8111D'. 591: Jan 12 11:01:07 Tower kernel: r8168 Copyright © 2012 Realtek NIC software team Win7 SSD => Unraid Cache WD 640 Black: 46mb/s (left side of network graph) Unraid Cache WD 640 Black: => Win7 SSD 50mb/s (right side of network graph) So while testing I also watched the windows task manager network tab (attached). Notice how when copying to the unraid cache i have much higher and more volatile network activity compared to when copying the same file back to my my Win7 from the unraid cache. Is there a normal reason for this? Or could it be related to my Realtek 8112L, or even that chipset being detected as an 8111D? And of course the real question is, why have i been so limited since 4.7? I know on 4.7 I was saturating my network when writing to the cache and when reading from the cache and array both. EDIT: so hopefully it is obvious that I'm running RC10. also my hardware is shown in my sig.
January 12, 201313 yr Same happened to me so I ran the makebootable.bat one the flash drive and that fixed my problems. Please try. That made it work. That's really strange. Maybe the boot parameters/size changed and that caused the boot loader to go wonky? Tomorrow I'm going to try 8a to see if it is the boot config. I just: Stop the array Go to tower/flash on the network Rename bzroot and bzimage then copy the bzroot and bzimage from RC10 to tower/flash reboot the server and RC10 up and running That's my normal procedure but when it didn't work I tried the more manual procedure.
January 12, 201313 yr The copying speed appears to have changed again... Copying used to start with huge speeds (some kind of buffering I guess), ending in copy speeds between 20 and 30 MB/s.. In this version copying seems to start real slow again, climbing up to around 10 MB/s .. I am running with sysctl vm.highmem_is_dirtyable=1 I took a chance and changed this to 0 again, immediatly back to the 300 KB/s speeds, so the parameter was active. Back to 1 and speeds climb up to 7 to 10 MB/s .. No plugins are doing something (they are loaded in the same configuration where I got speeds of 20 to 30 MB/s .. EDIT: Strike that... from another drive it is just 20MB/s ... More testing is needed... It might very well be something on my side.
Archived
This topic is now archived and is closed to further replies.