nc88keyz

5.2.5644 (ex495) > ethtool -i eth0 driver: r8168 version: 8.040.00-NAPI firmware-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no 6.1.3.15152 "Update 1" with 1.02b jun loader (ex495) ethtool -i eth0 driver: r8168 version: 8.044.02-NAPI firmware-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no

im using 1.02b loader and 6.1.3 with update 1 applies. has stabilized. mtu set at 4k.. it 5.2.5644 it is set at 9k or maximum setring. although i think from putty it shows 6400 with ethtool. i can verify that in a few. Sent from my SM-G935V using Tapatalk

Indeed the 510 datavault is the sibling to the consumer EX495. Are you still running parity check on your volume by chance. Mine has settled down and now the nic is no longer dropping off, Im not sure what that has to do with it unless its a resources issue. However, I have successfully transfered 1.4TB without a crash. I did do the update 1 pat file as well. I have MTU set to 4000. Not sure if i want to push it further as there are known issues with DSM 6.1.x I am currently on 6.1.3 with update 1 applied using 1.02b loader untouched. It is sustaining 90MB to 110MB transfers now. and 40MB over usb 2.0 on the EX495. There is hope.

correction: R8169 vs, R8168, My apologies

i am completely willing to do this. I need the real R8168 driver to work with my headless EX495. The R8169 in 1.02b crashes it hard on large file trasfers. This has been going on since 5.2 days!!! Would be most appreciative of some help with fixing this. I have a working unit up and working to test with, without data, and willing to crash it in trial and error.

does an extra.lzma exist for 1.02b jun loader??? one with the correct .ko file to identify my R8168. I wish there was a post that organized the extra.lzma by kernel. Its confusing for new people to 6.x. Even when dowloading an extra.lzma i have no idea how to tell what kernel those drivers were compiled for. Helpless. Have read so much now.....

is it possible to blacklist R8169 to make R8168 driver load on the loader 1.02 from jun. This seems to be my issue with a headless unit HP EX495 mediasmart box. I have two of these boxes that required loading this same driver direct from realtek to fix this issue. Issue: File starts blazing fast, 3 to 4 seconds later drops to 0 and crashes nic until a reboot is performed. I am almost positive this is the exact same issue with 5.2.5466. This is the only thing holding me up from a 6.1.2 install on a headless EX495. Any assistance appreciated.

working on this right now. Have it installed just fine, but the nic driver is broken. Loads RT8169 vs RT8168. Try to transfer a file and it will crash. Stock 1.02b loader from Jun will work just fine with latest pat manually or from web. Lets fix the nic driver please. Its the only thing messed up as far as I can see. This issue was present when 5.2 rolled as well. Does anyone know how to force the RT8168 vs RT8169 driver? In 5.2 you were able to manually install the driver from realtek with a script. That script doesnt work with 6.1.2 due to the kernel changes and path changes is my understanding. Is this as simple as commenting out the driver somewhere. to force RT8168 on the headless EX495, EX490? I have two of these units working fine in 5.2.5644

I have a real DS1812 plus 2 DX512 expansions. I also have 4-5 Mediasmart headless units. The three that are in question are all EX495s actually. I have not done any upgrading the xpenology on 2 of these units because, well they just work. and I try not to fix what is not broken, however when I attempted to do a bare bones install of the latest on a 3rd EX495 I cannot get the realtek network card to operate stable. on the previous two I had the same issue and I believe this stems from the driver in the kernel. I know enough about linux to be dangerous and thats about it. My questions are the following: I can get the system to load stable with 1.02b jun loader, and select latest from synology for pat file via web. Works every time As soon as a transfer a large file as a test, it crashes the NIC. This is because i believe according to grep command it has the RT8169 driver loaded for what is the RT8168 in the headless unit. I 'do have a debug cable" btw as I own many of these mediasmart units. Its my understanding this was fixed in 1.02b so it loads the correct driver. So why is it crashing now. Im not sure I know where to find the correct extra.lzma file for the version used. There are so many files out there and apparently they are kernel dependent OR pat file dependent on version , correct? I was able to replace drivers on 5.2.5644 - They run flawlessly and are untouched. ....almost makes me want to just set this up on the third one since it just works, but I try to stay current and would like get 6.1 working correctly. These are Core duo , 2gb ram, base machines from HP. It appears when i try to upgrade the extra.lzma it freezes upon boot, or worse, unmounts the volume and array, this would indicate wrong version i believe. Here is what I have done so far. Followed the guide to a T - I can mount image replace, extra-lzma file etc. Do I need to touch ramdisk.lzma, If so I have no idea where it is ? Built into the kernel? Is there a simple way just to replace the nic driver with the correct one from realtek on this build? The pat file cant have anything do do with it, because it freezes before booting the first time with the extra.lzma that i attempt , I assume you can either replace in .synoboot.img file or just copy and paste as once the drive is imaged with win32Diskimage, the 15mb and 30mb partitions are available to copy and paste too. I am always using notepad II to edit .cfg files by the way. Im not a complete idiot, just need this driver fixed. I have .ssh shell of course too to do any troubleshooting, It is set to gigabit on network driver as well. This is a known issue with the RT8168 nic, as the RT8169 driver is loaded by default by the loader. How to force the RT8168 driver for it? Help Please!!! Last question: If i cant figure this out, Is it feasable to image the USB drive from working expenology and reset so the drivers and everything are intact on 5.2.5644 for the nic card issue, and just set up my volumes to start a new xpenology with clean drives.??? ie. copy usb image to new usb drive for new nas. Then wipe and clear for fresh start and new volume. Sorry for long post, hoping get some help here. I know the extra.lzma was the answer to people having to compile their own drivers, I just cannot figure out what is broken about the process for my unit. Just to clarify, i know exactly how to boot these units with drives in all bays. I have several of them and experience. As soon as the network card blinks off on for about 3 seconds. (there are other windows as well) USB Drive needs to be in lowest slot on back of unit. slide the drive in bay 0 or the bay towards the bottom Meta # ex495,ex490,mediasmart, ex485, ex470, rt8168