Jump to content
XPEnology Community

wer

Member
  • Posts

    23
  • Joined

  • Last visited

  • Days Won

    2

wer last won the day on March 2 2018

wer had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

wer's Achievements

Junior Member

Junior Member (2/7)

20

Reputation

  1. Finally I could make r8125 driver working at DSM 6.1. Found my four years old Debian VM with DSM 6.1 build environment and obviously there was a difference.
  2. The r8125 works for me at DSM 6.2.3, however I can't get the hard disks to spin down, no matter what I try (using tmpfs for several mounts, disabling logs and all possible services). I was happy with DSM 6.1-15101 Update 4 for several years and it was the last version that I had no problems with hard disk spinning down after selected time of no activity. I was able to compile r8125.ko for DSM 6.1-15101, however it doesn't load (error: "region #1 not an MMIO resource", reported for other realtek adapters and different systems too). @IG-88 What driver source did you use for r8125?
  3. Second NIC even works without MAC in grub.cfg with fresh install. I don't know what went wrong, what crashed whole config. There was no other way than fresh install. I tried switching to 918 but no matter what (vid & pid in grub.cfg), I always got error 13 while installing pat. After complete cleaning 3615 is now running again and backup is restoring.
  4. Thank you, including driver worked that way. However just bringing up the second NIC crashed the settings completely! It's no longer possible to use the network configuration at the web login, I get operation fails. Connection by SSH fails too, works again after removing second NIC. Settings aren't possible anymore. /var/log/messages is floated by synoscgi_SYNO.Core,.Network error messages.
  5. I can manually load it. However it's not loaded when adding it in rc.modules like the other modules (like r8169). I might add it myself to extra.lzma the same way? I'm just not sure how to compress/pack it again.
  6. Problem with extra.lzma v0.11.2_test Configuration: Host: ESXi 7 Virtual E1000e NIC AHCI Controller Passthrough Loader 1.03b DS3615xs DSM 6.2.3-25426 Update 3 With default extra.lzma everything works fine. Now I want to add a second NIC with RTL8125 (Passthrough). At the serial console output I get: :: Loading module ata_piix BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 After that no further modules are loaded. Starting doesn't finish. No "Starting /usr/syno/bin/synocfgen". Hard disks at the AHCI controller are obviously not present. Is there another way just to add support for RTL8125 (not at boot time)?
  7. Sorry haven't been around for a while - and as I'm running DSM on ESXi not using powerbutton anymore myself. I added braswell to INFO: powerbutton_6.1-0005.spk
  8. Spin down is not logged. You can place a tick mark at the energy settings for logging the wakeups - however it's always logged in /etc/var/scemd.log So I can't see the spin down but hear it.
  9. Finally I found a working combination: ESXi 6.5 Build 5969303 DSM 6.1-15101 (till Update 4) Iso boot image that issues booting from USB stick (with Jun's 1.02)
  10. Hi, for quite a while I'm trying to find out why hard disks do not spin down after the set time with DSM 6.x and ESXi Hypervisor (6.0 or 6.5) using Jun's loader. Hard disks are connected to a passthrough SATA Controller (onboard, also tried PCIe). Exactly one and the same setup is working bare metal, also with DSM 5.2 on ESXi. I even tried using a boot iso (as with DSM 5.2) that uses the passthrough USB boot stick (like with bare metal) instead of synoboot.vmdk/synoboot.img combination. No spindown, hdparm -y does a spindown, however disks wake up at once again. I can't see any differences in the logs between running bare metal or on ESXi. Would appreciate any further ideas.
  11. I'm just doing my first trials with ESXi. I intend to physically pass through complete hard drives but SMART doesn't seem to work this way. But that's a different problem. One idea would be not to enlarge the already existing drive (e.g. by 50 GB) but to add an additional disk (with 50 GB) later and use this additional drive for expanding the existing one using JBOD.
  12. wer

    DSM 6.1.2-15132

    powerbutton_6.1-0004.spk still works. You might have to install it again.
  13. No. I just did a clean new install. Really quite strange...
  14. Just tried my package on an AMD system with DSM 5.2-5644 Update 5. Works without any problems.
  15. So there is obviously a problem when the needed kernel modules should be unloaded - and when the power button ACPI event "power button pushed" occurs. I'm not sure if this is an AMD issue. There is a seperate power off thread but I haven't found something there. You might follow the orignal instruction and install manually just to see if problem remains the same.
×
×
  • Create New...