NoFate Posted October 23, 2017 Share #26 Posted October 23, 2017 i had the same issues about the drops, look in this topic started from this reply : lowe i fixed on my asrock by lowering from 4 GB to 2 GB ram, on my hp gen 8 i created a workaround, Quote Link to comment Share on other sites More sharing options...
naasking Posted October 24, 2017 Author Share #27 Posted October 24, 2017 I've tried removing a memory module so I only have 2GB of physical memory, but it hasn't improved the situation. However, the BIOS reports 2GB but Synology's info center says the NAS has 4GB of physical memory. Perhaps it's displaying a cached value? Is there some way to refresh this information? Quote Link to comment Share on other sites More sharing options...
naasking Posted October 25, 2017 Author Share #28 Posted October 25, 2017 I also tried swapping the modules and the memory slots, still no dice. It's strange because the ethernet statistics (netstat -i) don't show any packet drops or errors, it just stops responding for a period of time, then starts up again. Some online posts on Windows with this same issue have disabled "energy efficient ethernet" to fix it, but "ethtool --set-eee eth0 eee off" fails as not supported. I wish I could simply install a new ethernet card, but the one slot I have available is taken by an SATA card I use for my storage. Looking into other embedded motherboards, they all seem to have RTL8111 chipsets of various editions (mostly H or G, I have RTL8111E), so just replacing the board might not actually fix this issue. I have no idea what to do now. Quote Link to comment Share on other sites More sharing options...
naasking Posted October 25, 2017 Author Share #29 Posted October 25, 2017 On 10/9/2017 at 9:53 PM, Decapix said: how about loading driver from IG-88? Machine boots fine, but network drops still occur. I have the same AuthenticAMD unknown vendor error: [ 0.000000] CPU: vendor_id 'AuthenticAMD' unknown, using generic init. CPU: Your system may be unstable. So perhaps it's all related to the spotty AMD support in Jun's current loader. Strange that everything mostly works though, and it's rock solid otherwise. Quote Link to comment Share on other sites More sharing options...
naasking Posted October 25, 2017 Author Share #30 Posted October 25, 2017 On 10/9/2017 at 9:53 PM, Decapix said: how about loading driver from IG-88? Machine boots fine, but network drops still occur. I have the same AuthenticAMD unknown vendor error: [ 0.000000] CPU: vendor_id 'AuthenticAMD' unknown, using generic init. CPU: Your system may be unstable. So perhaps it's all related to the spotty AMD support in Jun's current loader. Strange that everything mostly works though, and it's rock solid otherwise. Quote Link to comment Share on other sites More sharing options...
waspsoton Posted October 26, 2017 Share #31 Posted October 26, 2017 I might try putting dsm 5 on the server and see if its any better Quote Link to comment Share on other sites More sharing options...
naasking Posted October 26, 2017 Author Share #32 Posted October 26, 2017 DSM 5.2 was great for over a year. But I need DSM 6. Quote Link to comment Share on other sites More sharing options...
waspsoton Posted October 26, 2017 Share #33 Posted October 26, 2017 2 hours ago, naasking said: DSM 5.2 was great for over a year. But I need DSM 6. I would prefer dsm 6 but think I will try and see what happends Quote Link to comment Share on other sites More sharing options...
Hackerjac Posted November 3, 2017 Share #34 Posted November 3, 2017 On 25/10/2017 at 5:35 PM, naasking said: Machine boots fine, but network drops still occur. I have the same AuthenticAMD unknown vendor error: [ 0.000000] CPU: vendor_id 'AuthenticAMD' unknown, using generic init. CPU: Your system may be unstable. So perhaps it's all related to the spotty AMD support in Jun's current loader. Strange that everything mostly works though, and it's rock solid otherwise. Its not just related to the spotty AMD support, i have a ASUS AT5NM10T-I (Atom 1.8) also with Realtek 8111E and facing the same problem Quote Link to comment Share on other sites More sharing options...
naasking Posted November 4, 2017 Author Share #35 Posted November 4, 2017 On 11/3/2017 at 6:37 AM, Hackerjac said: Its not just related to the spotty AMD support, i have a ASUS AT5NM10T-I (Atom 1.8) also with Realtek 8111E and facing the same problem That's a bummer. I was seriously considering replacing the board with something like this, but it too has a Realtek 8111 chipset. It's the H revision though, ie. RTL8111H. I'm gunshy on the 8111 chipset now, but since this problem seems to only have been reported in the E revisions in this thread, maybe it's a hardware bug in that edition alone. Quote Link to comment Share on other sites More sharing options...
waspsoton Posted November 6, 2017 Share #36 Posted November 6, 2017 has anyone tired installing a intel network card?? Quote Link to comment Share on other sites More sharing options...
waspsoton Posted November 28, 2017 Share #37 Posted November 28, 2017 On 04/11/2017 at 5:23 PM, naasking said: That's a bummer. I was seriously considering replacing the board with something like this, but it too has a Realtek 8111 chipset. It's the H revision though, ie. RTL8111H. I'm gunshy on the 8111 chipset now, but since this problem seems to only have been reported in the E revisions in this thread, maybe it's a hardware bug in that edition alone. did u ever get it sorted Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted November 29, 2017 Share #38 Posted November 29, 2017 On 10/19/2017 at 12:09 PM, naasking said: The problem seems well-known in every Linux distro. My board has the Realtek 8111E chipset, and along with the 8168, these load the driver for the Realtek 8169. Unfortunately, this driver is known to produce unreliable ethernet connections on these chipsets. Not sure what I can do to remedy this, as all the recommended solutions that I can find suggest building the drivers Realtek provides from source, and I'm not setup to do that with the Synology images. Anyone have any ideas? Would that NIC be able to boot with r8168.ko? If yes you could try disabling r8169.ko by removing it from the rc.modules file contained within the ramdisk. Before doing that you also need to remove the file from DSM too as it's already been copied in the OS ans it's used to load the NIC at every boot. You need to remove it from: /usr/lib/modules/update Once you have removed the file, shutdown your machine and edit the rc.modules file in the loader's ramdisk as stated above. Then plug your usb back in and boot. See if that works. If not then you simply re-enable r8169.ko in the rc.modules and that will copy the module again to the above directory once you boot again. Quote Link to comment Share on other sites More sharing options...
naasking Posted December 5, 2017 Author Share #39 Posted December 5, 2017 So here's my partial solution: I noticed that the drops seemed related to burst traffic, so I used the DSM control panel's traffic shaping tab to limit the bandwidth of the problematic network card to less than 95MB/s (you may have to play around with this number). That seems to have eliminated the drops, but I'll keep you posted. Quote Link to comment Share on other sites More sharing options...
waspsoton Posted December 5, 2017 Share #40 Posted December 5, 2017 13 minutes ago, naasking said: So here's my partial solution: I noticed that the drops seemed related to burst traffic, so I used the DSM control panel's traffic shaping tab to limit the bandwidth of the problematic network card to less than 95MB/s (you may have to play around with this number). That seems to have eliminated the drops, but I'll keep you posted. cool I will try this tonight and let u know Quote Link to comment Share on other sites More sharing options...
Decapix Posted December 6, 2017 Share #41 Posted December 6, 2017 On 11/6/2017 at 4:37 PM, waspsoton said: has anyone tired installing a intel network card?? Yes, i tried with Intel card and the problem went away. quite sure it's the driver issue Quote Link to comment Share on other sites More sharing options...
waspsoton Posted December 6, 2017 Share #42 Posted December 6, 2017 1 hour ago, Decapix said: Yes, i tried with Intel card and the problem went away. quite sure it's the driver issue in that case I will buy new intel card Quote Link to comment Share on other sites More sharing options...
naasking Posted December 20, 2017 Author Share #43 Posted December 20, 2017 Just an update, the drops still happen but are much less frequent with the bandwidth limiter. Quote Link to comment Share on other sites More sharing options...
waspsoton Posted April 17, 2018 Share #44 Posted April 17, 2018 well I have finally got round to putting in a intel network card. I hope its fixes the issue now Quote Link to comment Share on other sites More sharing options...
waspsoton Posted April 18, 2018 Share #45 Posted April 18, 2018 well that didn't work for me. still getting network drop outs. cant work it out, I have changed the network card and a powerline adapters two. I am running out of ideas Quote Link to comment Share on other sites More sharing options...
flegarrec Posted May 22, 2020 Share #46 Posted May 22, 2020 Hello, i now have the same issue. On my Asus E35M1-M Pro i had an Intel NIC on PCIe, all working fine. I just removed it to put a SATA card, hence now using the onboard NIC. And the traffic drop now occurs. It blocks Windows Explorer and Kodi. I need to kill the smbd to get back the control, as the CPU becomes very high. Did you find a way to resolve it? Did you find a more recent driver? Help welcome before i have to put the Intel NIC back :( Quote Link to comment Share on other sites More sharing options...
naasking Posted June 25, 2020 Author Share #47 Posted June 25, 2020 No, never found a solution. Strange that it still seemed to work running ordinary Linux, just not under DSM. Quote Link to comment Share on other sites More sharing options...
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.