Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+


Recommended Posts

9 часов назад, IG-88 сказал:

я не писал так, но имел в виду, что вы также должны использовать extra.lzma для загрузчика 1.02b / DSM 6.1 отсюда, чтобы получить лучший / более новый драйвер Intel для DSM 6.1

https://xpenology.com/forum/topic/9508-driver-extension-jun-102bdsm61x-for-3615xs-3617xs-916/

Intel Failure.

Link to post
Share on other sites

 

11 hours ago, IG-88 said:

 

don't connect a monitor, as long as there are no boot problems there is no need for a monitor

dsm is designed as a headless system

 

I tried to boot without connecting the monitor as you gave me the guide with the bootloader with the 0.8 patch I mentioned above.
But again, it doesn't find Ethernet.
The 1.04b original bootloader also does not find Ethernet.
Reconnecting the monitor line does not change the phenomenon.
The models on the main board differ cautiously, but many other users in Korea say the same thing.
It won't be easy to solve this problem, will it?

Link to post
Share on other sites
13 hours ago, pcVirus said:

Intel Failure.

 

how do you know, do you have a serial console connected or do you have a dmesg log?

 

6 hours ago, Peter Suh said:

The 1.04b original bootloader also does not find Ethernet.

then it different from what you wrote above, that was ethernet lost when monitor disconnected, so it should work with the monitor connected or its just a erratic failure and there might be a diffrent cause you have not found out

can you oot a live linux and do a

lspci -k | grep 'Kernel driver'

we should see the device id of that intel hardware if a driver gets loaded

also as in the case above you might try the 1.02b loader with dsm 6.1 and the additinal extra.lzma with its newer drivers

Link to post
Share on other sites

 

7 hours ago, IG-88 said:

then it different from what you wrote above, that was ethernet lost when monitor disconnected, so it should work with the monitor connected or its just a erratic failure and there might be a diffrent cause you have not found out

can you oot a live linux and do a


lspci -k | grep 'Kernel driver'

we should see the device id of that intel hardware if a driver gets loaded

also as in the case above you might try the 1.02b loader with dsm 6.1 and the additinal extra.lzma with its newer drivers

 

This is the result of accessing the DSM with SSH.
-----------------------------------------------------------
admin@NAS4:/$ lspci -k | grep 'Kernel Driver'
Kernel driver in us: hsw_uncore
Kernel driver in us: i915
Kernel driver in us: xhci_hcd
Kernel driver in us: serial
Kernel driver in us: e1000e
Kernel Driver in Us: Ehci-pci
Kernel driver in us: pcieport
Kernel driver in us: pcieport
Kernel Driver in Us: Ehci-pci
Kernel driver in us: lpc_ich
Kernel driver in us: ahci
Kernel driver in us: i801_smbus
-------------------------------------------------------
Will this information help?

The same original 1.04b bootloader as mine and DS918+ DSM 6.2.2 have the same symptoms as the same person who has experienced the same symptoms of not being able to find Ethernet.
I heard that he has solved the problem by downgrading to DS918+ DSM 6.2.1.

First of all, I will try the DSM downgrade before using the 1.02b bootloader.

 

Thanks.

Link to post
Share on other sites

Hi guys,

 

I have Asrock J3160DC-ITX mobo (J3160 CPU, ahci storage driver) with Intel 82574L Gigabit ethernet card (use e1000e driver) in minipcie. I am currently on DS3615xs DSM 6.1.7-15284 Update 3 and I am thinking on update to DSM 6.2.2. Which model/loader could I use for this mobo? Which is more stable?

 

As I understood, the 918+ loader will work only with "recovery" extra. Both DS3615xs and DS3617xs loaders should work too. Transcoding support is not priority for me.

Link to post
Share on other sites
9 minutes ago, Arcao said:

Hi guys,

 

I have Asrock J3160DC-ITX mobo (J3160 CPU, ahci storage driver) with Intel 82574L Gigabit ethernet card (use e1000e driver) in minipcie. I am currently on DS3615xs DSM 6.1.7-15284 Update 3 and I am thinking on update to DSM 6.2.2. Which model/loader could I use for this mobo? Which is more stable?

 

As I understood, the 918+ loader will work only with "recovery" extra. Both DS3615xs and DS3617xs loaders should work too. Transcoding support is not priority for me.

 

Hi Arco,

 

You might want to have a look at this. This will tell you what you can and cannot use.

 

Link to post
Share on other sites

Hi IG,

today I found time to test some configurations on my J4105 ITX.

 

I booted with extra standard and system loops, then changed the extra with recovery and it boots.

 

dmesg show me only the current boot so I had a look on kern.log

 

Quote

2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080482] Call Trace:
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080491]  [<ffffffffa093ccf0>] ? drm_clflush_sg+0x50/0x90 [drm]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080539]  [<ffffffffa0a231f4>] __i915_do_clflush+0x14/0x30 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080571]  [<ffffffffa0a23369>] i915_gem_clflush_object+0x39/0x1e0 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080604]  [<ffffffffa0a32813>] flush_write_domain+0x33/0xe0 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080639]  [<ffffffffa0a3506c>] i915_gem_object_set_to_gtt_domain+0x8c/0x120 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080676]  [<ffffffffa0a466dd>] execlists_context_pin+0x14d/0x4e0 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080709]  [<ffffffffa0a424c7>] intel_engine_init_common+0x27/0x380 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080741]  [<ffffffffa0a47ad2>] logical_ring_init+0x12/0xc0 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080773]  [<ffffffffa0a47c62>] logical_render_ring_init+0xe2/0x340 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080804]  [<ffffffffa0a45e50>] ? gen9_init_render_ring+0x30/0x30 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080835]  [<ffffffffa0a42187>] intel_engines_init+0x47/0xb0 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080869]  [<ffffffffa0a37577>] i915_gem_init+0xf7/0x4a0 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080901]  [<ffffffffa09f0cde>] i915_driver_load+0xa1e/0xe00 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080932]  [<ffffffffa09fb797>] i915_pci_probe+0x27/0x40 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080938]  [<ffffffff812ffb8c>] pci_device_probe+0x8c/0x100
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080942]  [<ffffffff81387641>] driver_probe_device+0x1f1/0x310
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080944]  [<ffffffff813877e2>] __driver_attach+0x82/0x90
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080946]  [<ffffffff81387760>] ? driver_probe_device+0x310/0x310
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080950]  [<ffffffff813856d1>] bus_for_each_dev+0x61/0xa0
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080951]  [<ffffffff813870d9>] driver_attach+0x19/0x20
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080954]  [<ffffffff81386d03>] bus_add_driver+0x1b3/0x230
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080956]  [<ffffffffa0b2c000>] ? 0xffffffffa0b2c000
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080959]  [<ffffffff81387feb>] driver_register+0x5b/0xe0
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080961]  [<ffffffff812fe667>] __pci_register_driver+0x47/0x50
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080990]  [<ffffffffa0b2c03e>] i915_init+0x3e/0x45 [i915]
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.080996]  [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.081001]  [<ffffffff810e1b48>] do_init_module+0x56/0x1be
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.081005]  [<ffffffff810b7d8d>] load_module+0x1dfd/0x2080
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.081007]  [<ffffffff810b51f0>] ? __symbol_put+0x50/0x50
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.081010]  [<ffffffff810b8199>] SYSC_finit_module+0x79/0x80
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.081012]  [<ffffffff810b81b9>] SyS_finit_module+0x9/0x10
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.081017]  [<ffffffff8156a58a>] entry_SYSCALL_64_fastpath+0x1e/0x92
2020-02-22T13:20:23+01:00 xpewd6 kernel: [   60.081018] Code: 00 16 00 00 48 8d 37 48 01 c6 48 b8 00 00 00 00 00 88 ff ff 48 c1 fe 06 31 d2 48 c1 e6 0c 48 01 c6 8d 02 48 8d 04 30 66 0f ae 38 <8d> 14 0a 81 fa ff 0f 00 00 76 eb 55 48 89 e5 65 48 8b 04 25 c0 

 

at this point the system makes the loop.

 

 

I tried fresh install from 6.2.2 with extra from std with extra2 from recovery -> dosn´t work NMI watchdog: BUG: soft lockup

 

 

I wasn´t able to deactivate the watchdog

 

I tried:

sudo sh -c "echo '0' > /proc/sys/kernel/nmi_watchdog"

which dosn´t give an error

 

and I modified grub.cfg with put in the line

GRUB_CMDLINE_LINUX_DEFAULT="quiet nmi_watchdog=0"

 

both dosn´t deactivate the watchdog and the system loops.

Link to post
Share on other sites
В 05.11.2019 в 09:26, sunshine сказал:

Thanks for your quick answer.

 

It seems its too difficult for me and I wait.

Use OSFmount and mount sinoboot.img for 918+. Then choose partition1, not 0, as usual - the then you can handle it as a liocal disk with file explorer. Try, it is very simple

Link to post
Share on other sites

Hi, before starting I want to thank everyone for their efforts.

I used xpenology on my old Asrock J2900-based NAS for at least 5 years, but now I'm struggling with my new(ish) system.

 

My CPU is a 4460T (35w TDP, Haswell refresh) and it has got an integrated HD 4600 GPU.

Network works fine since it's Realtek r8111 based.

 

I need a beefier CPU (so I bought the i5 instead of the Celeron J3455) since I have a ton of dockers on the NAS.

But I really would like to get hw transcoding working, since I have a lot of HEVC content.

I have a couple of problems, the main one is that it reboot when I try to see a video in Video Station on my browser with HW acceleration enabled.

Video starts and encoding works very well, but I can't touch the slider: as soon as i stop the movie or move the slider my system instantaneosly reboot.

 

Nothing in logs, no sign of kernel crash or memory errors, it just reboots.

 

My conditions:

  • real mac / serial combo, took from a dead unit, I even have synology.me working
  • jun's loader 1.04b, version for ds918+
  • /dev/dri is populated:
root@DS918:~# ls -la /dev/dri/
total 0
drwxr-xr-x  2 root root       100 Feb 25 09:49 .
drwxr-xr-x 11 root root     18880 Feb 25 09:49 ..
crw-rw----  1 root video 226,   0 Feb 25 09:50 card0
crw-rw----  1 root video 226,  64 Feb 25 09:50 controlD64
crw-rw----  1 root video 226, 128 Feb 25 09:50 renderD128
cat /usr/syno/etc/codec/activation.conf  
{"success":true,"activated_codec":["h264_dec","h264_enc","mpeg4part2_dec","aac_dec","aac_enc","hevc_dec","vc1_dec","vc1_enc","ac3_dec","mpeg4part2_enc"],"token":"d686df0830fa070505494ed7d9787fa2"}

 

Other problems:

 

- my system will not boot without HDMI connected

 

How can I solve it? I tried the slimmed down driver extension (1.5mb) from another thread but it seems to did nothing.

I tried your driver extension (extra918plus_v0.8_syno.zip). Same issue, just reboots.

I even tried to chmod 777 /dev/dri content.

Which version would you suggest to an Haswell user?

 

root@DS918:~# tail -f /var/log/dmesg
[Tue Feb 25 09:49:34 2020] usbserial: USB Serial support registered for cp210x
[Tue Feb 25 09:49:34 2020] usbcore: registered new interface driver pl2303
[Tue Feb 25 09:49:34 2020] usbserial: USB Serial support registered for pl2303
[Tue Feb 25 09:49:34 2020] pl2303 1-8.2:1.0: pl2303 converter detected
[Tue Feb 25 09:49:34 2020] usb 1-8.2: pl2303 converter now attached to ttyUSB0
[Tue Feb 25 09:49:34 2020] usbcore: registered new interface driver ch341
[Tue Feb 25 09:49:34 2020] usbserial: USB Serial support registered for ch341-uart
[Tue Feb 25 09:49:34 2020] usbcore: registered new interface driver ti_usb_3410_5052
[Tue Feb 25 09:49:34 2020] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
[Tue Feb 25 09:49:34 2020] usbserial: USB Serial support registered for TI USB 5052 2 port adapter

root@DS918:~# tail -f /var/log/messages
2020-02-25T10:08:10+01:00 DS918 ddnsd: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:08:24+01:00 DS918 ddnsd: SYSTEM:  Last message 'proxy_internal_lib_c' repeated 1 times, suppressed by syslog-ng on DS918
2020-02-25T10:08:24+01:00 DS918 synoscgi_SYNO.Core.Package.Server_2_list[10172]: pkgcurltool.cpp:474 http://packages.synocommunity.com/, Failed to request packages, httpResponseCode=502
2020-02-25T10:08:24+01:00 DS918 synoscgi_SYNO.Core.Package.Server_2_list[10172]: pkgcurltool.cpp:474 http://packages.synocommunity.com/, Failed to request packages, httpResponseCode=502
2020-02-25T10:08:25+01:00 DS918 synoscgi_SYNO.Core.Package.Server_2_list: SYSTEM:       Last message 'pkgcurltool.cpp:474 ' repeated 1 times, suppressed by syslog-ng on DS918
2020-02-25T10:08:25+01:00 DS918 ore.Package.Server_1_check: pkgcurltool.cpp:474 http://packages.synocommunity.com/, Failed to request packages, httpResponseCode=502
2020-02-25T10:08:25+01:00 DS918 ore.Package.Server_1_check: pkgcurltool.cpp:474 http://packages.synocommunity.com/, Failed to request packages, httpResponseCode=502
2020-02-25T10:23:45+01:00 DS918 kernel: [ 2084.925651] Bluetooth: Failed to add device to auto conn whitelist: status 0x0c
2020-02-25T10:54:45+01:00 DS918 ddnsd: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:54:45+01:00 DS918 ddnsd: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:57:28+01:00 DS918 synoscgi_SYNO.VideoStation2.Controller.Device_1_list[9595]: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:57:30+01:00 DS918 synoscgi_SYNO.VideoStation2.Streaming_2_open[9669]: json_utils.cpp:147 Failed to parse json file [/tmp/VideoStation/enabled]
2020-02-25T10:58:32+01:00 DS918 ddnsd: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:58:32+01:00 DS918 ddnsd: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:58:33+01:00 DS918 ddnsd: SYSTEM:  Last message 'proxy_internal_lib_c' repeated 1 times, suppressed by syslog-ng on DS918
2020-02-25T10:58:33+01:00 DS918 ore.Package.Server_1_check: pkgcurltool.cpp:474 http://packages.synocommunity.com/, Failed to request packages, httpResponseCode=502
2020-02-25T10:58:33+01:00 DS918 ore.Package.Server_1_check: pkgcurltool.cpp:474 http://packages.synocommunity.com/, Failed to request packages, httpResponseCode=502
2020-02-25T10:58:45+01:00 DS918 ore.Package.Server_1_check: SYSTEM:     Last message 'pkgcurltool.cpp:474 ' repeated 1 times, suppressed by syslog-ng on DS918
2020-02-25T10:58:45+01:00 DS918 ddnsd: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:58:46+01:00 DS918 ddnsd: proxy_internal_lib_conf.c:106 Create file or directory failed
2020-02-25T10:58:53+01:00 DS918 ddnsd: SYSTEM:  Last message 'proxy_internal_lib_c' repeated 1 times, suppressed by syslog-ng on DS918
2020-02-25T10:58:53+01:00 DS918 synoscgi_SYNO.VideoStation2.Controller.Device_1_list[11850]: proxy_internal_lib_conf.c:106 Create file or directory failed

 

Edited by gatsu_1981
Link to post
Share on other sites
On ‎2‎/‎21‎/‎2020 at 12:27 PM, Peter Suh said:

This is the result of accessing the DSM with SSH.
-----------------------------------------------------------
admin@NAS4:/$ lspci -k | grep 'Kernel Driver'
Kernel driver in us: hsw_uncore
Kernel driver in us: i915
Kernel driver in us: xhci_hcd
Kernel driver in us: serial
Kernel driver in us: e1000e
Kernel Driver in Us: Ehci-pci
Kernel driver in us: pcieport
Kernel driver in us: pcieport
Kernel Driver in Us: Ehci-pci
Kernel driver in us: lpc_ich
Kernel driver in us: ahci
Kernel driver in us: i801_smbus
-------------------------------------------------------
Will this information help?

The same original 1.04b bootloader as mine and DS918+ DSM 6.2.2 have the same symptoms as the same person who has experienced the same symptoms of not being able to find Ethernet.
I heard that he has solved the problem by downgrading to DS918+ DSM 6.2.1.

First of all, I will try the DSM downgrade before using the 1.02b bootloader.

 

Thanks.

 

I answer the last question myself.

 

Downgrading to DS918+ DSM VERSION 6.2.1.

 

However, if I unplug the HDMI CABLE, the Ethernet disappears.

 

So, I bought and installed the HDMI DUMMY PLUG.

 

In this case, Ethernet does not disappear and the connection persists.

 

Perhaps, even the latest version of DS918+ DSM VERSION 6.2.2 DUMMY PLUG would have been helpful.

 

Thanks.

Link to post
Share on other sites

Thanks  for your hard work. But I found your boot did not load i915 drivers.
I got one boot img, but cannot get the i915 driver's version. Compared with Jun's 1.04b loader, only  the i915 drivers update (3 files only, drm, drm-help, i915) in the extra.lmz, no others changed from Jun 1.04b.

I just verified in my  computer and works well with 6.2.2-24922 new installation, which CPU is intel J1900 and Ethernet card is intel i211.

also has /dev/dri. but the hardware decoder not tested.

This driver works well, I would like to share with you.

The img link: https://share.weiyun.com/56iapul, the document name is 6.2.1, but this is work only for 6.2.2, not working for 6.2.1(I tested, IP connection lost).

Link to post
Share on other sites
On 2/16/2020 at 6:18 PM, premiero said:

Asrock J5005 ITX.

extra918plus_v0.8_syno

Baremetal fresh install: Success

Update from 6.2 (DSM_DS918+_23739.pat): Success

Comments: Shutdown and reboot works good. No errors at dmesg. No dev/dri. Next updated to DSM 6.2.2-24922 Update 5 - still works good.

 

extra918plus_v0.8_std

Baremetal fresh install: Failed

Update from 6.2 (DSM_DS918+_23739.pat): Failed

Comments: Lot of errors at dmesg. I was able to finish install with extra918plus_v0.8_recovery, but still lot of errors, no dev/dri, shutdown and reboot not working.

The same to you!

Link to post
Share on other sites

Hello, with this drivers, i could boot my Xpenology with onboard NIC, and a dual Intel e1000e, but my old controller LSI SAS1068E that was working on DSM 6.2 stopping working after the upgrade, is there a way to make it works again?? How? Thanks.

 

ash-4.3# lspci -k
0000:00:00.0 Class 0600: Device 8086:d130 (rev 11)
        Subsystem: Device 1028:02a6
0000:00:03.0 Class 0604: Device 8086:d138 (rev 11)
        Kernel driver in use: pcieport
0000:00:05.0 Class 0604: Device 8086:d13a (rev 11)
        Kernel driver in use: pcieport
0000:00:08.0 Class 0880: Device 8086:d155 (rev 11)
0000:00:08.1 Class 0880: Device 8086:d156 (rev 11)
0000:00:08.2 Class 0880: Device 8086:d157 (rev 11)
0000:00:08.3 Class 0880: Device 8086:d158 (rev 11)
0000:00:10.0 Class 0880: Device 8086:d150 (rev 11)
0000:00:10.1 Class 0880: Device 8086:d151 (rev 11)
0000:00:1a.0 Class 0c03: Device 8086:3b3c (rev 05)
        Subsystem: Device 1028:02a6
        Kernel driver in use: ehci-pci
0000:00:1c.0 Class 0604: Device 8086:3b42 (rev 05)
        Kernel driver in use: pcieport
0000:00:1c.4 Class 0604: Device 8086:3b4a (rev 05)
        Kernel driver in use: pcieport
0000:00:1c.5 Class 0604: Device 8086:3b4c (rev 05)
        Kernel driver in use: pcieport
0000:00:1d.0 Class 0c03: Device 8086:3b34 (rev 05)
        Subsystem: Device 1028:02a6
        Kernel driver in use: ehci-pci
0000:00:1e.0 Class 0604: Device 8086:244e (rev a5)
0000:00:1f.0 Class 0601: Device 8086:3b14 (rev 05)
        Subsystem: Device 1028:02a6
        Kernel driver in use: lpc_ich
0000:00:1f.2 Class 0106: Device 8086:3b22 (rev 05)
        Subsystem: Device 1028:02a6
        Kernel driver in use: ahci
0000:02:00.0 Class 0100: Device 1000:0058 (rev 08)
        Subsystem: Device 1028:1f0e
0000:03:00.0 Class 0200: Device 8086:105e (rev 06)
        Subsystem: Device 103c:7044
        Kernel driver in use: e1000e
0000:03:00.1 Class 0200: Device 8086:105e (rev 06)
        Subsystem: Device 103c:7044
        Kernel driver in use: e1000e
0000:04:00.0 Class 0200: Device 14e4:165a
        Subsystem: Device 1028:02a6
        Kernel driver in use: tg3
0000:06:03.0 Class 0300: Device 102b:0532 (rev 0a)
        Subsystem: Device 1028:02a6
0000:ff:00.0 Class 0600: Device 8086:2c50 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:00.1 Class 0600: Device 8086:2c81 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:02.0 Class 0600: Device 8086:2c90 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:02.1 Class 0600: Device 8086:2c91 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:03.0 Class 0600: Device 8086:2c98 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:03.1 Class 0600: Device 8086:2c99 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:03.2 Class 0600: Device 8086:2c9a (rev 04)
        Subsystem: Device 8086:8086
0000:ff:03.4 Class 0600: Device 8086:2c9c (rev 04)
        Subsystem: Device 8086:8086
0000:ff:04.0 Class 0600: Device 8086:2ca0 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:04.1 Class 0600: Device 8086:2ca1 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:04.2 Class 0600: Device 8086:2ca2 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:04.3 Class 0600: Device 8086:2ca3 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:05.0 Class 0600: Device 8086:2ca8 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:05.1 Class 0600: Device 8086:2ca9 (rev 04)
        Subsystem: Device 8086:8086
0000:ff:05.2 Class 0600: Device 8086:2caa (rev 04)
        Subsystem: Device 8086:8086
0000:ff:05.3 Class 0600: Device 8086:2cab (rev 04)
        Subsystem: Device 8086:8086
0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff)

and the lsmod

ash-4.3# lsmod
Module                  Size  Used by
cifs                  368749  0
udf                    79080  0
isofs                  32127  0
loop                   16655  0
tcm_loop               16708  1
iscsi_target_mod      298219  1
target_core_ep         46817  2
target_core_multi_file    29253  1
target_core_file       44308  1
target_core_iblock     21489  1
target_core_mod       990769  18 target_core_iblock,target_core_multi_file,iscsi_target_mod,target_core_ep,target_core_file,tcm_loop
syno_extent_pool     1291887  0
rodsp_ep               74563  3 target_core_multi_file,syno_extent_pool,target_core_file
hid_generic             1121  0
usbhid                 26311  0
hid                    82284  2 hid_generic,usbhid
usblp                  12146  0
bromolow_synobios      47238  0
xgmac                  16325  0
s2io                   75339  0
rtl8150                 9799  0
r8152                 122229  0
plusb                   1667  0
pegasus                18902  0
mcs7830                 6404  0
i40evf                 86590  0
et131x                 29775  0
cx82310_eth             3814  0
asix                   27314  0
aqc111                 15882  0
vxge                   94832  0
bna                   118832  0
cxgb4                 115227  0
cxgb3                 131376  0
cxgb                   55300  0
forcedeth              54967  0
ixgb                   44507  0
e100                   28637  0
atl2                   23204  0
evdev                   8888  0
button                  4448  0
ax88179_178a           12020  0
usbnet                 23677  6 asix,plusb,mcs7830,aqc111,ax88179_178a,cx82310_eth
tg3                   171910  0
r8169                  32596  0
r8125                 109310  0
r8101                 193604  0
ixgbevf                57430  0
igbvf                  34823  0
bnx2                   73577  0
vmxnet3                38413  0
pcnet32                30594  0
e1000                 123303  0
sfc                   187579  0
netxen_nic             96532  0
qlge                   77298  0
qlcnic                227672  0
qla3xxx                36553  0
pch_gbe                48315  0
ptp_pch                 5718  1 pch_gbe
sky2                   47062  0
skge                   29539  0
jme                    34049  0
ipg                    15781  0
uio                     7600  0
alx                    26137  0
atl1c                  35540  0
atl1e                  29486  0
atl1                   31726  0
libphy                 18261  2 asix,et131x
mii                     3771  11 ipg,jme,e100,asix,atl1,mcs7830,usbnet,pch_gbe,pcnet32,pegasus,ax88179_178a
exfat                 116630  0
btrfs                 909167  2
synoacl_vfs            17190  2
zlib_deflate           20444  1 btrfs
hfsplus                91458  0
md4                     3561  0
hmac                    2697  0
bnx2x                 642848  0
libcrc32c                906  1 bnx2x
mdio                    3301  5 alx,sfc,cxgb,bnx2x,cxgb3
mlx5_core             517396  0
mlx4_en               110920  0
mlx4_core             287935  1 mlx4_en
mlx_compat              6312  3 mlx4_en,mlx4_core,mlx5_core
compat                  4337  4 mlx_compat,mlx4_en,mlx4_core,mlx5_core
qede                  115450  0
qed                   796207  1 qede
atlantic               65622  0
r8168                 557739  0
tn40xx               1088472  0
i40e                  304063  0
ixgbe                 277642  0
be2net                 82933  0
igb                   181654  0
i2c_algo_bit            5128  1 sfc
e1000e                208376  0
dca                     4512  2 igb,ixgbe
vxlan                  17808  0
fuse                   76026  0
vfat                   10151  0
fat                    50511  1 vfat
crc32c_intel           13865  2
glue_helper             4001  0
lrw                     3277  0
gf128mul                5346  1 lrw
ablk_helper             1684  0
arc4                    1840  0
cryptd                  6964  1 ablk_helper
ecryptfs               79019  1 btrfs
sha256_generic          9628  0
sha1_generic            2206  0
ecb                     1849  0
aes_x86_64              7303  0
authenc                 6180  0
des_generic            15851  0
ansi_cprng              3740  0
cts                     3936  0
md5                     2249  0
cbc                     2512  0
cpufreq_conservative     6240  0
cpufreq_powersave       1118  0
cpufreq_performance     1186  0
cpufreq_ondemand        8021  0
mperf                   1075  0
processor              26468  0
thermal_sys            17969  1 processor
cpufreq_stats           3369  0
freq_table              4556  2 cpufreq_stats,cpufreq_ondemand
dm_snapshot            26058  0
crc_itu_t               1267  1 udf
crc_ccitt               1267  0
quota_v2                3719  0
quota_tree              7458  1 quota_v2
psnap                   1653  0
p8022                    979  0
llc                     3505  2 p8022,psnap
sit                    14746  0
tunnel4                 2061  1 sit
ip_tunnel              11456  2 sit,vxlan
ipv6                  306113  52 sit,rodsp_ep
zram                    8145  4
sg                     25382  0
etxhci_hcd            135424  0
nvme                   37347  0
hpsa                   59748  0
isci                  113726  0
arcmsr                 27544  0
mvsas                  53005  0
mvumi                  28900  0
3w_xxxx                23911  0
3w_sas                 20250  0
3w_9xxx                32453  0
aic94xx                71507  0
aacraid                79328  0
sx8                    13021  0
mpt2sas               239426  0
megaraid_sas           72686  0
megaraid               37746  0
megaraid_mbox          27691  0
megaraid_mm             7568  1 megaraid_mbox
BusLogic               21185  0
usb_storage            49280  0
xhci_hcd               86244  0
uhci_hcd               24347  0
ohci_hcd               25680  0
ehci_pci                3928  0
ehci_hcd               46953  1 ehci_pci
usbcore               206504  21 asix,etxhci_hcd,r8152,plusb,usblp,uhci_hcd,rtl8150,mcs7830,usb_storage,aqc111,ohci_hcd,ehci_hcd,ehci_pci,usbhid,usbnet,pegasus,ax88179_178a,xhci_hcd,cx82310_eth
usb_common              1552  1 usbcore
cepsw                  17708  0

 

Edited by Gccarvalho
Link to post
Share on other sites

@IG-88 i think the error was in the kernel compiled, because when i try to run the command "insmod /lib/modules/update/mptsas.ko" i got the message "insmod: ERROR: could not insert module /lib/modules/update/mptsas.ko: Unknown symbol in module", how can i fix that???

 

Thanks

Link to post
Share on other sites
11 hours ago, Gccarvalho said:

Hello, with this drivers, i could boot my Xpenology with onboard NIC, and a dual Intel e1000e, but my old controller LSI SAS1068E that was working on DSM 6.2 stopping working after the upgrade, is there a way to make it works again?? How? Thanks.

 

please read agin in the 1st post in this thread the RED an BOLD (and below) in the 3615/17 section

mptsas is not working with 6.2.2, i was explicit about that, i tested it with virtualblox (lsi scsi and lsi sas virtual hardware)

 

2 hours ago, Gccarvalho said:

i think the error was in the kernel compiled,

the kernel is original from synology and we only have a 2.5 year old beta kernel to compile drivers - i repeat myself here, read the 1st post and the FAQ

reason for you error when loading the module might be when mixing old drivers from 6.2.0 and kernel 6.2.2 as there where changes in the kernel config used for 6.2.2

but even it it loads (for 6.2.2. compiled module) it will crash when the hardware is present (loaded without errors without the hardware present)

it would need someone to debug that crash and find out what might be different in the actual kernel synology uses for 6.2.2 and the old kernel we have to compile for the drivers

details the different kernel config in 6.2.2 are documented here

https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/?do=findComment&comment=122631

 

 

Link to post
Share on other sites
On 2/26/2020 at 12:11 PM, dlutwang said:

The img link: https://share.weiyun.com/56iapul, the document name is 6.2.1, but this is work only for 6.2.2, not working for 6.2.1(I tested, IP connection lost).

 

i'd like to have a look but you need a account to download and its all chinese (there might be a billion people being able to read this but most here will not

maybe you can upload it to a hoster where it can be downloaded free (without opening a account) or extract the extra.lzma/extra2.lzma and upload it here (both files are below 10MB so you could PM them to me in two messages)

 

On 2/26/2020 at 12:11 PM, dlutwang said:

I got one boot img, but cannot get the i915 driver's version

there are three veriaty's of the extra/extra2 the image (*.img) can onyl contain one so you might have used the wrong extra/extra2, reread the 1st post and the tutorial on how to modify the image/loader (can be done directly on the usb or with osfmount and the image file)

i had at least one positive report with J1800 and 0.8_syno ds918+

Link to post
Share on other sites
On 2/21/2020 at 7:11 AM, Arcao said:

I have Asrock J3160DC-ITX mobo (J3160 CPU, ahci storage driver) with Intel 82574L Gigabit ethernet card (use e1000e driver) in minipcie. I am currently on DS3615xs DSM 6.1.7-15284 Update 3 and I am thinking on update to DSM 6.2.2. Which model/loader could I use for this mobo? Which is more stable?

 

all three should work, when using 6.2. it needs the new drivers because of the changes in the kernel

On 2/21/2020 at 7:11 AM, Arcao said:

As I understood, the 918+ loader will work only with "recovery" extra. Both DS3615xs and DS3617xs loaders should work too. Transcoding support is not priority for me.

 

recover would be the safe bet that can be used after trying the other two, syno would be 1st, might work as your hardware is only slightly older then the original J3455 f the 9188+

if things go south (like does not boot anymore) then recovery can overwrite the i915 driver and firmware with 0-byte files on boot

even if it boots you should check for crashing drives in the log this can prevent reboot and shutdown

it safer to make dry run with a fresh loader and one empty disk before trying to update the running 6.1 system

Link to post
Share on other sites
On 2/25/2020 at 11:34 AM, Peter Suh said:

Downgrading to DS918+ DSM VERSION 6.2.1.

However, if I unplug the HDMI CABLE, the Ethernet disappears.

So, I bought and installed the HDMI DUMMY PLUG.

In this case, Ethernet does not disappear and the connection persists.

Perhaps, even the latest version of DS918+ DSM VERSION 6.2.2 DUMMY PLUG would have been helpful.

 

that kind of very specific to some boards or vendors and might even be seen with other linux systems too

(at least i remember reading about hdmi dummy plugs needed for some systems elsewhere)

and if it needs some kernel tweaking its clear we can't do it as the kernel comes fix from synology with dsm and also we dont have the source from the backported i915 driver (jun has not made this one public, he just used it for creating its loader modules)

Link to post
Share on other sites
7 hours ago, IG-88 said:

 

i'd like to have a look but you need a account to download and its all chinese (there might be a billion people being able to read this but most here will not

maybe you can upload it to a hoster where it can be downloaded free (without opening a account) or extract the extra.lzma/extra2.lzma and upload it here (both files are below 10MB so you could PM them to me in two messages)

 

there are three veriaty's of the extra/extra2 the image (*.img) can onyl contain one so you might have used the wrong extra/extra2, reread the 1st post and the tutorial on how to modify the image/loader (can be done directly on the usb or with osfmount and the image file)

i had at least one positive report with J1800 and 0.8_syno ds918+

Sorry, please check the link https://easyupload.io/eeup5p.

 

For "syno", J1900 can boot without any problem, but once the decoder working,  will reboot.

Link to post
Share on other sites
On 2/25/2020 at 10:49 AM, gatsu_1981 said:

Hi, before starting I want to thank everyone for their efforts.

I used xpenology on my old Asrock J2900-based NAS for at least 5 years, but now I'm struggling with my new(ish) system.

 

My CPU is a 4460T (35w TDP, Haswell refresh) and it has got an integrated HD 4600 GPU.

Network works fine since it's Realtek r8111 based.

 

I need a beefier CPU (so I bought the i5 instead of the Celeron J3455) since I have a ton of dockers on the NAS.

But I really would like to get hw transcoding working, since I have a lot of HEVC content.

I have a couple of problems, the main one is that it reboot when I try to see a video in Video Station on my browser with HW acceleration enabled.

Video starts and encoding works very well, but I can't touch the slider: as soon as i stop the movie or move the slider my system instantaneosly reboot.

 

Nothing in logs, no sign of kernel crash or memory errors, it just reboots.

 

My conditions:

  • real mac / serial combo, took from a dead unit, I even have synology.me working
  • jun's loader 1.04b, version for ds918+
  • /dev/dri is populated:

cat /usr/syno/etc/codec/activation.conf  
{"success":true,"activated_codec":["h264_dec","h264_enc","mpeg4part2_dec","aac_dec","aac_enc","hevc_dec","vc1_dec","vc1_enc","ac3_dec","mpeg4part2_enc"],"token":"d686df0830fa070505494ed7d9787fa2"}

 

Other problems:

 

- my system will not boot without HDMI connected

 

How can I solve it? I tried the slimmed down driver extension (1.5mb) from another thread but it seems to did nothing.

I tried your driver extension (extra918plus_v0.8_syno.zip). Same issue, just reboots.

I even tried to chmod 777 /dev/dri content.

Which version would you suggest to an Haswell user?

-SNIP-

 

 

9 hours ago, IG-88 said:

 

that kind of very specific to some boards or vendors and might even be seen with other linux systems too

(at least i remember reading about hdmi dummy plugs needed for some systems elsewhere)

and if it needs some kernel tweaking its clear we can't do it as the kernel comes fix from synology with dsm and also we dont have the source from the backported i915 driver (jun has not made this one public, he just used it for creating its loader modules)

 

Hi @IG-88 what do you think of my problem? syno works, STD crash on boot (diskstation becomes unreachable), recovery obviously works but no hw acceleration.

On my config I don't have error in logs, just keeps rebooting when skipping videos while using HW transcoding in video station.

Edited by gatsu_1981
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.