Jump to content
XPEnology Community

whatever000

Transition Member
  • Posts

    14
  • Joined

  • Last visited

Posts posted by whatever000

  1. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.2.2 (DS918+)

    - DSM version AFTER update: DSM 7.2.1 69057 (DS3622xs+)

    - Loader version and model: arpl-i18n v23.10.4

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - X10SDV-4C-TLN2F (Xeon D1521)

     

  2. @mervincm I got this figured out. Just want to report back my findings in case someone has a supermicro board. It turns out there is a BIOS setting in Supermicro "Power button behaviour". You can choose between "instant off" or "4 sec override". The correct setting for the power button to work is "instant off"

     

    Here is the details log

     

    edwin@jarvis:/$ dmesg | grep Button
    [   21.328442] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
    [   21.328447] ACPI: Power Button [PWRB]
    [   21.328497] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
    [   21.328499] ACPI: Power Button [PWRF]
    edwin@jarvis:/$ dmesg | grep button
    [   35.696225] button: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
    edwin@jarvis:/$ ls /dev/input/
    event0  event1  event2  event3  event4  event5
    edwin@jarvis:/$ ls -l /dev/input/
    total 0
    crw------- 1 root root 13, 64 Feb 29 23:33 event0
    crw------- 1 root root 13, 65 Feb 29 23:33 event1
    crw------- 1 root root 13, 66 Feb 29 23:33 event2
    crw------- 1 root root 13, 67 Feb 29 23:33 event3
    crw------- 1 root root 13, 68 Feb 29 23:33 event4
    crw------- 1 root root 13, 69 Feb 29 23:33 event5
    edwin@jarvis:/$ ls -l /sys/class/input/
    total 0
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 event0 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 event1 -> ../../devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 event2 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:0B38:0010.0001/input/input2/event2
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 event3 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:0B38:0010.0002/input/input3/event3
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 event4 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.0/0003:0557:2419.0003/input/input4/event4
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 event5 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.1/0003:0557:2419.0004/input/input5/event5
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 input0 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 input1 -> ../../devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 input2 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:0B38:0010.0001/input/input2
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 input3 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:0B38:0010.0002/input/input3
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 input4 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.0/0003:0557:2419.0003/input/input4
    lrwxrwxrwx 1 root root 0 Feb 29 23:39 input5 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.1/0003:0557:2419.0004/input/input5
    edwin@jarvis:/$
     

  3. @mervincm, I followed your instruction but it doesn't seem to work for me. is there anyway to debug this? I am using Jun 1.04b loader for ds918+ 6.2.2 24922 (https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS918+_24922.pat) with 0.8_recovery ds918+ (http://s000.tinyupload.com/?file_id=02568989419278984390) from IG-88 and POWERBUTTON_6.2-0002.SPK. I am using Supermicro x10sdv-4c-tln2f. I can shutdown properly using the web interface. Here is my step to install:

    1. uninstalled the mentioned.spk

    2. reinstalled the mentioned .spk

    3. extracted button.ko and evdev.ko from 0.8_recovery ds918+

    4. overwrite the two ko in /usr/lib/modules/update with the extracted one.

    5. restart

    I see the following

    =======

    edwin@jarvis:/$ ls -l /dev/input/
    total 0
    crw------- 1 root root 13, 64 Feb 29 22:01 event0
    crw------- 1 root root 13, 65 Feb 29 22:01 event1
    crw------- 1 root root 13, 66 Feb 29 22:01 event2
    crw------- 1 root root 13, 67 Feb 29 22:01 event3
    crw------- 1 root root 13, 68 Feb 29 22:01 event4

    =======

    edwin@jarvis:/$ ll /sys/class/input/
    total 0
    drwxr-xr-x  2 root root 0 Feb 29 22:01 .
    drwxr-xr-x 59 root root 0 Feb 29 22:01 ..
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 event0 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 event1 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:0B38:0010.0001/input/input1/event1
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 event2 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:0B38:0010.0002/input/input2/event2
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 event3 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.0/0003:0557:2419.0003/input/input3/event3
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 event4 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.1/0003:0557:2419.0004/input/input4/event4
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 input0 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 input1 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:0B38:0010.0001/input/input1
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 input2 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:0B38:0010.0002/input/input2
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 input3 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.0/0003:0557:2419.0003/input/input3
    lrwxrwxrwx  1 root root 0 Feb 29 22:12 input4 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.1/0003:0557:2419.0004/input/input4

    =======

    edwin@jarvis:/$ dmesg | grep Button
    [   21.134670] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
    [   21.134675] ACPI: Power Button [PWRB]

    =======

    dmesg gave me the following

    [   34.766347] evdev: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '
    [   34.803902] button: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '

  4. I tried to install powerbutton_6.1-0005.spk on 6.2.2 24922 with driver extension 0.8 on 1.04b 918+ loader. But it said the DSM version is not supported. How do I install it? @IG-88would it be possible to include the power button stuff in the driver extension release? Thanks. 

  5. ic, when I look at the different between the cpu used in 918+ (apollolake) and ds3617xs (broardwell). It seems that apollolake has some new SHA instructions. everything else stays the same. Not sure how likely those instruction will be used. I guess I should be safe. And knowing that I can switch between the two is good. Thanks once again. @IG-88. You have been a great help!!

  6. I guess what I concerned about is if i use a DSM version designed for a CPU newer than what I have, there may be chance that the system will crash due to unsupported instructions. I don't know if it makes sense. Just want to make my system will be stable for daily usage. And avoid stuff that has high risk. Thanks in advance. 

  7. So @IG-88 I am a little embarrass to say this. But I think the problem is between the keyboard and the chair. It turns out I plugged xpenology into an old switch which I didn't own. It didn't support 1Gbps AND X557 didn't seem to support 100MBps. So once I fixed that. I was able to boot up and install 918+ without any problem.

     

    So about picking which DS3617xs vs DS918+ loader and the potential implication. which one should I really pick? It seems like from your comment and also the table in

     

     I wouldn't have transcode either way. So what is the advantage picking one over the other? is UEFI important?

     

    I am going to see if I have a chance to install ds3617xs and see if it work and reported back. Thank you @IG-88 for your help

    • Like 1
  8. @IG-88 so I have tried 918+ with your extra.lzma and extra2.lzma, but no luck. I think the best thing is to get serial cable and see what happen. It could have been my bios setting. So one more question. If I use ds3617xs 1.03b would I still be able to do trancoding? As it was mentioned, in your extra.lzma post, if I use 918+ recovery, I wouldn't be able to transcode, just curious if ds3617xs will still let me do it. Thanks a lot

  9. thanks @IG-88. In my first attempt on the 1.03b loader, I didn't. I just use whatever the loader has. On my 2nd attempt, when I tried the test 0.5 extra.lzma, I did copy rd.gz and zImage from https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat into the 2nd partition as given in 

     

     

    In terms of boot device, it only has the legacy ones. I am going to 1.04b 918+ with the extra/extra2 and will report back. BTW, since 918+ use a newer cpu than the one I have on my board, would that cause me trouble? And when?

     

    Does xpenlogy support USB serial? Really want to see what's going on in the console

  10. thanks and sorry @bearcat

     

    2 hours ago, bearcat said:

    Hi, and welcome :-)

    1 - When talking about bootloaders, it is important to specify *what* bootloader you are talking about ;-)

     

    Jun loader 1.03b for ds3617xs 

     

    2 hours ago, bearcat said:

    2 - As above, it is important to specify exact what version/build of DSM you are trying to get working..

     

    I am trying to use DSM 6.2.2. More specifically, https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat. I tried also tried ds3617xs extra.lzma from this thread 

     

     

    2 hours ago, bearcat said:

    3 - By the symtoms you describe, you are most likely not having a valid driver for you nic, with the tested combo of 1 and 2.

     

    What would be a reasonable/working combo? I think the nic are X557-AT2

     

    2 hours ago, bearcat said:

    4 - Identify the dual 10GbE nic, and you might find the needed combo of 1,2 and drivers.

     

    2 hours ago, bearcat said:

     

    btw: you might want to stay with the 3615, as the 3617 has been known to cause problems.

     

     

    I have also tried 3615, same thing. Does 3615 loader have ixgbe?

     

    Edwin

  11. HI guys,

     

    I received a Supermicro x10sdv-4c-tln2f for free and would like to use Xpenology on it. I am using ds3617xs loader because both use similar CPU (D1521 vs D1527). But once the bootloader printed the "... find.synology.com ... " I wasn't able to find it on the network. What should I do? I know people has success with the board using ESXi, but I rather run bare metal. I did the following 

    1. update pid/vid, sn, mac1 and mac2 in grub.cfg

    2. change in BIOS to Legacy boot

    Serial-over-Lan show me nothing regard the console output. I also use the same procedure and tried ds3615xs. same thing. Please let me know how I should proceed. Thanks

×
×
  • Create New...