Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

1 Follower

About nc88keyz

  • Rank

Recent Profile Visitors

685 profile views
  1. nc88keyz

    DSM 6.1.x Loader

    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 "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
  2. nc88keyz

    DSM 6.1.x Loader

    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
  3. nc88keyz

    DSM 6.1.x Loader

    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 t
  4. correction: R8169 vs, R8168, My apologies
  5. 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.
  6. nc88keyz

    DSM 6.1.x Loader

    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.....
  7. 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 a
  8. 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 i
  9. nc88keyz

    DSM 6.1.x Loader

    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 q