Jump to content
XPEnology Community

archon

Rookie
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

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

archon's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. With valid serial number (registered on Syno's site) the AME will activate without any additional patch. I have similar setup (DS918+, v7.2.1-69057, ProxMox, valid SN) and it just works (only HEVC).
  2. I can confirm, that newest AME (only HEVC codec) is working with DS918+ when using valid SN without any system modifications. AME 1.1.0-01006 06.01.2024 using loader TCRP with M Shell (by PeterSuh-Q3) v1.0.1.0 DSM 7.2.1-69057 Update 3 VM on ProxMox You can check SN by registering it on Syno website. It it registers than it probably will work inside DSM.
  3. It may be possible. The toolkit and toolchain are available for 7.2-63134 https://archive.synology.com/download/ToolChain/ No kernel for 7.2 yet, only 7.1.1-42962 https://archive.synology.com/download/ToolChain/Synology NAS GPL Source With kernel and some time it may be possible to construct spk package. I did some modifications to package with virtualbox for 6.2, compiled newer version, but in 7.x there are new rules for packages, so a lot of reading is involved.
  4. Hi, Is anybody interested in using this package (vbox 6.1.16) compiled to apollolake platform? (DS918+) I have previously used 6.0.8 on bromolow, did hardware update (ASRock J5040) and was forced to change platform to DS918, so I compiled vbox myself (using seba's package). I am currently working on phpvirtualbox4dsm for this package.
  5. Hi, I was successfully running ds3615xs on ASRock Q1900-ITX and decided it's time for upgrade. The new hardware is ASRock J5040-ITX and this is where the fun starts. According to topic about loaders and platforms, 1.03b supports only BIOS/CSM, MBR. The new mainboards doesn't allow to set anything like 'legacy boot mode', but it seems that the booting process begins properly. Screen shows well known grub table with three options, and when I choose option number one it starts booting. Unfortunately HDD stops working almost immediately. After editing grub.cfg and enabling debug set extra_args_3615='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15' The result is as following [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.105 (root@build1) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #23739 SMP Sat May 19 03:07:32 CST 2018 [ 0.000000] Command line: disable_mtrr_trim syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator syno_port_thaw=1 root=/dev/md0 sn=12345678 mac1=12345678 netif_num=1 vid=0x0951 pid=0x1643 earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000100-0x000000000003dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000000003e000-0x000000000003ffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000040000-0x000000000009dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000000fffffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000010000000-0x0000000012150fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000012151000-0x0000000076d07fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000076d08000-0x00000000795b7fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000795b8000-0x00000000795f3fff] ACPI data [ 0.000000] BIOS-e820: [mem 0x00000000795f4000-0x0000000079653fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000079654000-0x0000000079ae0fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000079ae1000-0x000000007a4e3fff] usable [ 0.000000] BIOS-e820: [mem 0x000000007a4e4000-0x000000007a58ffff] reserved [ 0.000000] BIOS-e820: [mem 0x000000007a590000-0x000000007abfffff] usable [ 0.000000] BIOS-e820: [mem 0x000000007ac00000-0x000000007fffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000d0000000-0x00000000d0ffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000d3709000-0x00000000d3709fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fe042000-0x00000000fe044fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fe900000-0x00000000fe902fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000047fffffff] usable [ 0.000000] extended physical RAM map: [ 0.000000] reserve setup_data: [mem 0x0000000000000100-0x000000000003dfff] usable [ 0.000000] reserve setup_data: [mem 0x000000000003e000-0x000000000003ffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000040000-0x000000000009dfff] usable [ 0.000000] reserve setup_data: [mem 0x000000000009e000-0x00000000000fffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000000010006f] usable [ 0.000000] reserve setup_data: [mem 0x0000000000100070-0x000000000fffffff] usable [ 0.000000] reserve setup_data: [mem 0x0000000010000000-0x0000000012150fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000012151000-0x0000000076d07fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000076d08000-0x00000000795b7fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000795b8000-0x00000000795f3fff] ACPI data [ 0.000000] reserve setup_data: [mem 0x00000000795f4000-0x0000000079653fff] ACPI NVS [ 0.000000] reserve setup_data: [mem 0x0000000079654000-0x0000000079ae0fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000079ae1000-0x000000007a4e3fff] usable [ 0.000000] reserve setup_data: [mem 0x000000007a4e4000-0x000000007a58ffff] reserved [ 0.000000] reserve setup_data: [mem 0x000000007a590000-0x000000007abfffff] usable [ 0.000000] reserve setup_data: [mem 0x000000007ac00000-0x000000007fffffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000d0000000-0x00000000d0ffffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000d3709000-0x00000000d3709fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fe042000-0x00000000fe044fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fe900000-0x00000000fe902fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed01000-0x00000000fed01fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000047fffffff] usable [ 0.000000] Early serial console at I/O port 0x3f8 (options '115200n') [ 0.000000] bootconsole [uart0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.105 #23739 [ 0.000000] ffffffff814c0c1f ffffffff818831a1 0000000000000001 0000000000000001 [ 0.000000] 00000000364c6000 0000000001b3a000 0000000000000bff fffffffeec635000 [ 0.000000] 0000000100000000 0000000000000000 0000000000000000 000000000000000e [ 0.000000] Call Trace: [ 0.000000] [<ffffffff814c0c1f>] ? dump_stack+0xc/0x15 [ 0.000000] [<ffffffff818831a1>] ? early_idt_handler_common+0x81/0xa8 [ 0.000000] [<ffffffff818940b3>] ? efi_init+0x238/0x476 [ 0.000000] [<ffffffff818940a0>] ? efi_init+0x225/0x476 [ 0.000000] [<ffffffff81887091>] ? setup_arch+0x43d/0xc44 [ 0.000000] [<ffffffff814bff92>] ? printk+0x4a/0x52 [ 0.000000] [<ffffffff81883957>] ? start_kernel+0x7b/0x3b0 [ 0.000000] RIP 0xfffffffeec635000 Any ideas why the kernel instantly crashes? Of course the VID, PID, MAC, SERIAL are entered properly.
  6. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: Yes, v0.11 for 6.2.3, applied during reboot (previously using extra.lzma v0.5 for 6.2.2) - Installation type: BAREMETAL - ASRock Q1900-ITX + Intel PRO/1000 PCIe (8086:107d) - Additional comments: Update via DSM GUI. Reboot required.
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock Q1900B-ITX + Intel EXPI9400PT (Intel PRO/1000 PT) - Additional comment: reboot required
×
×
  • Create New...