IG-88

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

Recommended Posts

Posted (edited)

edit 14.05.2020: 6.2.3 is back online as v25426, for newer coffeelake cpu's with problems using hardware transcoding (dev/dri present after boot) there is a new videostation that fixes the problem

https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/?do=findComment&comment=144918

 

edit2 02.06.2020: as @richv31 pointed out here

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/?do=findComment&comment=148564

there seems to be a serious problem with 918+ and scsi/scs drivers, at least with mpt2sas/mpt3sas, not just with 6.2.2/6.2.3 it also happens with jun's original loader 1.04b and dsm 6.2.0 (23824), breaking raid sets after not properly waking up from hdd hibernation means potential data loss

i had a two disk raid1 set on a lsi 9211-8i and after disks spinning down only one came up and i saw some really worrying messages on the serial console, i was not able to log in to the system, not on the web gui, even not on the serial console, the whole system was in lock down and only switching off seemed to work

Spoiler

[ 1790.685552] blk_update_request: I/O error, dev sdg, sector in range 4980736 + 0-2(12)
[ 1790.694162] blk_update_request: I/O error, dev sdh, sector 4982400
[ 1790.700960] blk_update_request: I/O error, dev sdg, sector in range 9437184 + 0-2(12)
[ 1790.709540] blk_update_request: I/O error, dev sdh, sector 9437192
[ 1790.716337] blk_update_request: I/O error, dev sdg, sector in range 4980736 + 0-2(12)
[ 1790.724884] raid1: Disk failure on sdg1, disabling device.
[ 1790.724884]  Operation continuing on 1 devices
[ 1790.735845] blk_update_request: I/O error, dev sdh, sector 4982400
[ 1790.742638] blk_update_request: I/O error, dev sdh, sector 4982400
[ 1790.749436] blk_update_request: I/O error, dev sdh, sector in range 1798144 + 0-2(12)
[ 1790.758050] blk_update_request: I/O error, dev sdh, sector in range 1810432 + 0-2(12)
[ 1790.770432] blk_update_request: I/O error, dev sdh, sector in range 4980736 + 0-2(12)
[ 1790.779049] Buffer I/O error on device md0, logical block in range 225280 + 0-2(12)
[ 1790.780438] blk_update_request: I/O error, dev sdh, sector in range 839680 + 0-2(12)
[ 1790.780448] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1790.780479] blk_update_request: I/O error, dev sdh, sector 846608
[ 1790.781784] blk_update_request: I/O error, dev sdh, sector in range 1806336 + 0-2(12)
[ 1790.781793] blk_update_request: I/O error, dev sdh, sector in range 1810432 + 0-2(12)
[ 1790.828187] Buffer I/O error on device md0, logical block in range 225280 + 0-2(12)
[ 1790.836561] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.844964] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.853341] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.861702] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.870084] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.878455] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.886819] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.895172] Buffer I/O error on device md0, logical block in range 221184 + 0-2(12)
[ 1790.903662] Aborting journal on device md0-8.
[ 1790.908677] Buffer I/O error on dev md0, logical block in range 262144 + 0-2(12) , lost sync page write
[ 1790.918993] Buffer I/O error on dev md0, logical block in range 0 + 0-2(12) , lost sync page write
[ 1790.918996] JBD2: Error -5 detected when updating journal superblock for md0-8.
[ 1790.936811] EXT4-fs error (device md0): ext4_journal_check_start:56: write error, md0, sdh1 index [7], sector 2056 [raid1_end_write_request]
[ 1790.943717] Buffer I/O error on dev md0, logical block 0, lost sync page write
[ 1790.943722] EXT4-fs error (device md0): ext4_journal_check_start:56: Detected aborted journal
[ 1790.943723] EXT4-fs (md0): Remounting filesystem read-only
[ 1790.943727] EXT4-fs (md0): previous I/O error to superblock detected
[ 1790.950627] blk_update_request: I/O error, dev sdh, sector 2048
[ 1790.950780] Buffer I/O error on dev md0, logical block 0, lost sync page write
[ 1794.075615] blk_update_request: I/O error, dev sdh, sector 837504
[ 1794.082367] blk_update_request: I/O error, dev sdh, sector 837504
[ 1800.780803] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1810.789579] blk_update_request: I/O error, dev sdh, sector 846608
[ 1820.796568] blk_update_request: I/O error, dev sdh, sector 846608
[ 1822.044135] blk_update_request: I/O error, dev sdh, sector in range 774144 + 0-2(12)
[ 1822.052679] blk_update_request: I/O error, dev sdh, sector 776184
[ 1822.066628] blk_update_request: I/O error, dev sdh, sector in range 729088 + 0-2(12)
[ 1822.075149] blk_update_request: I/O error, dev sdh, sector 730800
[ 1830.934083] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1840.942853] blk_update_request: I/O error, dev sdh, sector 846608
[ 1850.949900] blk_update_request: I/O error, dev sdh, sector 846608
[ 1860.956826] blk_update_request: I/O error, dev sdh, sector 846608
[ 1870.963792] blk_update_request: I/O error, dev sdh, sector 846608
[ 1880.970764] blk_update_request: I/O error, dev sdh, sector 846608
[ 1890.977740] blk_update_request: I/O error, dev sdh, sector 846608
[ 1900.984686] blk_update_request: I/O error, dev sdh, sector 846608
[ 1910.991662] blk_update_request: I/O error, dev sdh, sector 846608
[ 1920.998651] blk_update_request: I/O error, dev sdh, sector 846608
[ 1926.606790] blk_update_request: I/O error, dev sdh, sector in range 774144 + 0-2(12)
[ 1926.623021] blk_update_request: I/O error, dev sdh, sector in range 729088 + 0-2(12)
[ 1931.005641] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1936.902021] blk_update_request: I/O error, dev sdh, sector in range 737280 + 0-2(12)
[ 1936.910568] blk_update_request: I/O error, dev sdh, sector 737800
[ 1941.014441] blk_update_request: I/O error, dev sdh, sector in range 843776 + 0-2(12)
[ 1943.976967] blk_update_request: I/O error, dev sdh, sector in range 450560 + 0-2(12)
[ 1943.985462] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1943.994054] blk_update_request: I/O error, dev sdh, sector in range 446464 + 0-2(12)
[ 1944.002551] blk_update_request: I/O error, dev sdh, sector in range 450560 + 0-2(12)
[ 1944.011056] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.019658] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.028247] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.036823] blk_update_request: I/O error, dev sdh, sector in range 1069056 + 0-2(12)
[ 1944.047345] blk_update_request: I/O error, dev sdh, sector 452360
[ 1944.056151] blk_update_request: I/O error, dev sdh, sector 347928
[ 1944.062956] blk_update_request: I/O error, dev sdh, sector 452064
[ 1944.069715] blk_update_request: I/O error, dev sdh, sector 349352
[ 1944.076507] blk_update_request: I/O error, dev sdh, sector 458760
[ 1944.083383] blk_update_request: I/O error, dev sdh, sector 456704
[ 1944.090223] blk_update_request: I/O error, dev sdh, sector 1576904
[ 1944.097147] blk_update_request: I/O error, dev sdh, sector 445736
[ 1944.103846] md/raid1:md2: sdg3: rescheduling sector 4525376
[ 1944.110073] raid1: Disk failure on sdg3, disabling device.
[ 1944.110073]  Operation continuing on 1 devices
[ 1944.121641] md/raid1:md2: redirecting sector 4525376 to other mirror: sdh3
[ 1944.137078] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0
[ 1944.146632] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.159127] blk_update_request: I/O error, dev sdh, sector 1742824
[ 1944.159458] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.159467] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.188028] blk_update_request: I/O error, dev sdh, sector 1742824
[ 1944.208072] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
[ 1944.217600] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 3, flush 0, corrupt 0, gen 0
[ 1944.217615] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.237971] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 4, flush 0, corrupt 0, gen 0
[ 1944.237980] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258357] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258418] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 5, flush 0, corrupt 0, gen 0
[ 1944.258424] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 6, flush 0, corrupt 0, gen 0
[ 1944.258471] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258483] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258511] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 7, flush 0, corrupt 0, gen 0
[ 1944.258516] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258527] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 8, flush 0, corrupt 0, gen 0
[ 1944.258534] md2: syno_self_heal_is_valid_md_stat(499): md's current state is not suitable for data correction
[ 1944.258551] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 9, flush 0, corrupt 0, gen 0
[ 1944.258564] BTRFS error (device md2): bdev /dev/md2 errs: wr 0, rd 10, flush 0, corrupt 0, gen 0
[ 1944.258821] BTRFS error (device md2): failed to repair data csum of ino 15266 off 0 (ran out of all copies)
[ 1944.258821]
[ 1944.258827] BTRFS error (device md2): failed to repair data csum of ino 15266 off 4096 (ran out of all copies)
[ 1944.258827]
[ 1944.395099] BTRFS error (device md2): failed to repair data csum of ino 15266 off 8192 (ran out of all copies)
[ 1944.395099]
[ 1944.557549] EXT4-fs error (device md0): ext4_find_entry:1624: inode #33349: comm synopkg: reading directory lblock 0
[ 1944.569078] EXT4-fs (md0): previous I/O error to superblock detected
[ 1944.576170] Buffer I/O error on dev md0, logical block 0, lost sync page write
[ 1944.793737] BTRFS: error (device md2) in btrfs_commit_transaction:2434: errno=-5 IO failure (Error while writing out transaction)
[ 1944.806642] BTRFS: error (device md2) in cleanup_transaction:2032: errno=-5 IO failure
[ 1951.515009] blk_update_request: I/O error, dev sdh, sector in range 69632 + 0-2(12)
[ 1951.539799] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.563740] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.586584] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.594097] blk_update_request: I/O error, dev sdh, sector 73472
[ 1951.601295] blk_update_request: I/O error, dev sdh, sector 73472

 

as of the problems with not getting s.m.a.r.t. values i used juns old original raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko to get the old state back (replacing my newly made ones from more recent synology kernel source 24922 ) in 0.11/0.12 - these version inherit the problem that seems to be present since the beginning with loader 1.04b

anyone using mpt2sas/mpt3sas and disk hibernation  on 918+ should disable it for now to not risk any data loss

the new 0.13 for 918+ will have the raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko from kernel source 24922, that version did work on testing on my system without breaking anything and without such alarming errors on wakeup of disks, there will be no smart data but at least it seems safer then disks not waking up properly

for "proper" lsi sas controller support i'd suggest using 3615 or 3617 as it is "native" in these units and should work better, maybe there are kernel options missing in the 918+ kernel and that cant be fixed, if anyone finds out more just add a comment (i might not have the time to dig into this)

the other alternative is to use sata/ahci instead of scsi/sas with 918+, that works without problems on my system using 918+ (12 disks), JMB585 based controller seem to be the best choice atm as they support pcie 3.0 and can have up to 2000 MByte/s for its 5 sata ports (the older marvell and asm chips use only pcie 2.0 limiting the data rate to 500 MB/s or 1000 MB/s, even 8 port controller with two of the older chips use a pcie bridge chip with just two lanes making them terrible choice for a high port count - might be ok with just one or two 1GBit nic's but will at least limit the rebuild speed and ssd's should be kept away from these controllers and place in internal sata ports)

 

 

for Instructions about installing or updating please read "Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+"
if i have time i will write more in this place
the new package is not well tested i just did some tests with hardware i have at hand (ahci, e1000e, r8168, igb, bnx2x, mpt2sas/mpt3sas) and tested update from 6.2.2 to 6.2.3


basically synology reverted the kernel config change made in 6.2.2 back to what was before so old drivers from original 1.04b loader (and older driver i made before  6.2.2) should work again - but as synology also introduced there own new i915 driver with 6.2.3 there will be a conflict when jun's i915 driver is loaded with 6.2.3


there are two positive new things, synology released a nearly recent kernel source code (24922) and 6.2.3 has a new i915 driver supporting as much gpu hardware as jun's backported i915 driver in loader 1.04b - so there is no need for jun's i915 driver anymore and in theory we should have good support for apollo lake, gemini lake and other newer hardware but it seems not all new UHD630 is supported as there is dev id "3E98" unsupported (i5-9400, i5-9600k, i7-9700t, i7-9700), ark.intel.com and wikichip.og are usually good sources to check the id

https://ark.intel.com/content/www/us/en/ark/products/134898/intel-core-i5-9400-processor-9m-cache-up-to-4-10-ghz.html

https://en.wikichip.org/wiki/intel/core_i5/i5-9400

there is also a good document from intel listing all coffeelake's

https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-cfl-vol01-configurations.pdf

coffeelake cup's without driver support (no hardware transcoding), SKU numbers should be listed when buying and can be checked on the box

i9 SKU S82
i7 SKU S82
i5 SKU S6f2

 

a new 10th gen i5-10500 / i3-10300 have device id's "9BC8" and there are no "9xxx" numbers in the driver we use so don't expect any newer gen10 cpu to work with hardware transcoding even when it "only" has UHD630 igpu

 

Spoiler

0042
0046
0102
0106
010A
0112
0116
0122
0126
0152
0155
0156
0157
015A
0162
0166
016A
016A
0402
0406
040A
040B
040E
0412
0416
041A
041B
041E
0422
0426
042A
042B
042E
0A02
0A06
0A0A
0A0B
0A0E
0A12
0A16
0A1A
0A1B
0A1E
0A22
0A26
0A2A
0A2B
0A2E
0A84
0C02
0C06
0C0A
0C0B
0C0E
0C12
0C16
0C1A
0C1B
0C1E
0C22
0C26
0C2A
0C2B
0C2E
0D02
0D06
0D0A
0D0B
0D0E
0D12
0D16
0D1A
0D1B
0D1E
0D22
0D26
0D2A
0D2B
0D2E
0F30
0F31
0F32
0F33
1602
1606
160A
160B
160D
160E
1612
1616
161A
161B
161D
161E
1622
1626
162A
162B
162D
162E
1632
1636
163A
163B
163D
163E
1902
1906
190A
190B
190E
1912
1916
191A
191B
191D
191E
1921
1923
1926
1927
192A
192B
192D
1932
193A
193B
193D
1A84
1A85
22B0
22B1
22B2
22B3
2562
2572
2582
258A
2592
2772
27A2
27AE
2972
2982
2992
29A2
29B2
29C2
29D2
2A02
2A12
2A42
2E02
2E12
2E22
2E32
2E42
2E92
3184
3185
3577
3582
358E
3E90
3E91
3E92
3E93
3E94
3E96
3E99
3E9A
3E9B
3EA0
3EA1
3EA2
3EA3
3EA4
3EA5
3EA6
3EA7
3EA8
3EA9
5902
5906
5908
590A
590B
590E
5912
5913
5915
5916
5917
591A
591B
591D
591E
5921
5923
5926
5927
593B
5A41
5A42
5A49
5A4A
5A51
5A52
5A59
5A5A
5A71
5A79
5A84
5A85
8990
A001
A011


i completely removed jun's i915 drivers from the extra/extra2 and changed/added the i915 firmware needed, also i took care of the "old" i915 drivers on the installed system in /usr/lib/modules/update/, they are now deleted on boot so if you come from 6.2.2 and used extra/extra2 std or recovery or you did already used juns original 1.04b extra/extra2, it should work as soon as you boot up (when drivers in "update" are not present then the default drivers from synology will be used and with the added i915 in place it will work on most intel gpu's up to coffee lake)
the driver versions are the same as in the 6.2.2 extra/extra2 but are newly compiled, as every driver from 6.2.2 is renewed all the old drivers are overwritten and there should be no crashing drivers on boot (which can prevent proper shutdown or reboot)
we now have one universal i915 driver (and not jun's and synologys) its back to one package for all cpu/gpu, if needed there will  be a recovery version too

i only did test a new created loader from 1.04b image file with zImage and rd.gz from "DSM_DS918+_25426.pat" and the new extra.extra2, it might work with the 6.2.0 kernel that is by default in the 1.04b image (i will test this)


if you accidentally updated 6.2.2 to 6.2.3 and now have problems like no network after boot, no proper shutdown/reboot or missing /dev/dri (hardware transcoding) then you just copy the new extra/extra2 to your already updated usb drive (the update to 6.2.3 already installed the new kernel on it)

with latest updates of win10 there is no drive letter anymore, its possible to still do it with the tools already used for creating the usb drive, read the usb to a imgae file with "Win32DiskImager 1.0" (activate "read only allocated partitions"), mount that image with osfmount (like in the tutorial section), overwrite old /extra/extra2.lzma and write the image back to usb with Win32DiskImager

 

extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13

scsi/sas disks will have no  s.m.a.r.t. infos (see edit2 above), newer atlantic.ko driver 2.3.4

http://s000.tinyupload.com/?file_id=07822334905920255474

 

extra.lzma for loader 1.03b ds3615 DSM 6.2.3 v0.11_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ...

http://s000.tinyupload.com/?file_id=04147311964729253115

 

extra.lzma for loader 1.03b ds3617 DSM 6.2.3 v0.11.2_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ... (0.11.2 because i forgot bnx2/bnx2x firmware and mpt2/mp3 driver problem when updating from 6.2.2 in 0.11)

http://s000.tinyupload.com/?file_id=00282289527307524672

 

Edited by IG-88
added iGPU device id's for checking for unsupported hardware like i5 9400
  • Like 5
  • Thanks 13

Share this post


Link to post
Share on other sites
Posted (edited)

fantastic, thank you man! trying this right now on a qnap-453be :)

...and it's all working, have /dev/dri, cheers 

Edited by richv31

Share this post


Link to post
Share on other sites

I already change but my network card not work

 

Intel 82583V Gigabyte Ethernet,

 

Best regards 

Share this post


Link to post
Share on other sites

Hi, I have updated the extras, although /dev/dri folder returned, the HW acceleration still does not work

Share this post


Link to post
Share on other sites
Posted (edited)

It's fantastic.

 

J4105  ,  RAM DDR4 16GB , 512 GB SSD x2  , RTL8111G dual  lan

 

image.png.c9fbc5d8c4aae5b5e8ad0429aefd278e.png

 

H/W transcoding works very well. 

Thank you very much.

 

 

Edited by dolbycat

Share this post


Link to post
Share on other sites
9 минут назад, dolbycat сказал:

It's fantastic.

 

J4105  ,  RAM DDR4 16GB , 512 GB SSD x2  , RTL8111G dual  lan

 

image.png.c9fbc5d8c4aae5b5e8ad0429aefd278e.png

 

H/W transcoding works very well. 

Thank you very much.

 

 

Did you check actual work of the HW Transcoding? For example, to upload a movie to an iPhone? This option does not work in mine as well as playback of dowgraded video files. Although all the codecs up like in yours

Share this post


Link to post
Share on other sites
Posted (edited)

This 6.2.3 extra driver also resolves the disappearance of the LAN without a monitor line or HDMI DUMMY PLUG.
Thank you. IG-88

Edited by Peter Suh

Share this post


Link to post
Share on other sites
26 minutes ago, lotusd said:

Did you check actual work of the HW Transcoding? For example, to upload a movie to an iPhone? This option does not work in mine as well as playback of dowgraded video files. Although all the codecs up like in yours

Yes.
H/W Transcoding works very well.
The video quality is set to medium.

 

 

Share this post


Link to post
Share on other sites
Posted (edited)
13 hours ago, IG-88 said:

the new package is not well tested i just did some tests with hardware i have at hand (ahci, e1000e, r8168, igb, bnx2x, mpt2sas/mpt3sas) and tested update from 6.2.2 to 6.2.3

Hi, could you check if the smart info is showing correctly? I updated from 6.22 24922 (ds918+) and swapped the new extra and extra2 files after installation. The mpt2sas driver seems to be working but no SMART info (the SMART info was there before update).

 

 Installation type: VM(unraid) - e3 1280 v3, on board lsi2308 passthrough, on board Intel NIC 

 

I didn't know if I should swap the rd.gz and zlmage file in the loader with those from the .pat file but I did it anyway. I also realized that /dev/dri folder is missing (I don't use hw transcoding at all but maybe that is related to the smart info missing problem?)

Edited by sarieri

Share this post


Link to post
Share on other sites
1 hour ago, neo82ita said:

zImage and rd.gz from the 6.2.3 or the original in jun 1.04b?

i've only tested with 6.2.3 (1st boot without dsm) but it should work with 6.2.0 too, but not for long, when you install 6.2.3 *.pat the kernel is overwritten with 6.2.3

"accidental" update also starts with 6.2.3 on usb

the path is the same as with 6.2.2, i suggest 1st creating the usb with 6.2.3, test it and the install the dsm pat file with a 6.2.3 booted loader (it will recognize tthe older version on disk and will offer to update/migrate)

 

 

2 hours ago, sarieri said:

I also realized that /dev/dri folder is missing (I don't use hw transcoding at all but maybe that is related to the smart info missing problem?)

no, not related and your xeon does not have a gpu like a desktop cpu, quick sync video is a gpu feature

 

 

5 hours ago, Peter Suh said:

This 6.2.3 extra driver also resolves the disappearance of the LAN without a monitor line or HDMI DUMMY PLUG.
Thank you. IG-88

nothing what i did, if its solved then its part of the i915 driver synology provided

 

 

11 hours ago, lotusd said:

Hi, I have updated the extras, although /dev/dri folder returned, the HW acceleration still does not work

you could try a fresh install on a single empty disk to test if there is a general problem with your i3-9100 cpu

i tested with a G5400 aka coffee lake S, UHD 610 gpu Gen 9.5 and your  i3 9100 is a coffee lake R with UHD 630 gpu gen 9.5

so there might be a difference (my own i3 9100 is still in its original package, but i will know soon if its working or not)

 

 

14 hours ago, tuanbombt said:

I already change but my network card not work

 

Intel 82583V Gigabyte Ethernet,

did you had 6.2.3 kernel with my new drivers on usb?

any log (serial console or from disk)?

i've tested igb and e1000e with additional nic's so i know it should work in egneral

 

 

 

 

 

Share this post


Link to post
Share on other sites

No /dev/dri/ for me on J4105. I am afraid all changes to synoboot.img don't save at all. Everytime I flash the usb drive I have to change vid, pid, sn, Mac in grub menu.

 

Can anyone create synoboot.img with the newest custom extra.lzma and upload here? I would change vid, pid, sn, mac in grub menu.

Share this post


Link to post
Share on other sites
10 минут назад, premikkoci сказал:

No /dev/dri/ for me on J4105. I am afraid all changes to synoboot.img don't save at all. Everytime I flash the usb drive I have to change vid, pid, sn, Mac in grub menu.

 

Can anyone create synoboot.img with the newest custom extra.lzma and upload here? I would change vid, pid, sn, mac in grub menu.

Do you uncheck the box read only in the OFS Mount when mounting your image?

Share this post


Link to post
Share on other sites
Posted (edited)
48 минут назад, IG-88 сказал:

1st creating the usb with 6.2.3, test it and the install the dsm pat file with a 6.2.3 booted loader (it will recognize tthe older version on disk and will offer to update/migrate)

It works great for me. Thank you!

New synoboot with your extra + files from 6.2.3 .pat. 

Asrock h370m-itx/ac (i219 + i211)

Edited by Cornelius_drebbel

Share this post


Link to post
Share on other sites

I have finally managed to create a proper usb bootloader and my j4105 works perfectly fine (dev/dri/ exists).

Share this post


Link to post
Share on other sites
5 minutes ago, premikkoci said:

I have finally managed to create a proper usb bootloader and my j4105 works perfectly fine (dev/dri/ exists).

why did it not work for you to create a working loader?

Share this post


Link to post
Share on other sites
Posted (edited)

All changes to synoboot didn't save with osfmount that is bundled with the  xpenology tool. So I tried a current version and it worked for some reason.

Edited by premikkoci

Share this post


Link to post
Share on other sites
5 часов назад, IG-88 сказал:

you could try a fresh install on a single empty disk to test if there is a general problem with your i3-9100 cpu

i tested with a G5400 aka coffee lake S, UHD 610 gpu Gen 9.5 and your  i3 9100 is a coffee lake R with UHD 630 gpu gen 9.5

so there might be a difference (my own i3 9100 is still in its original package, but i will know soon if its working or not)

 

I have tried a fresh install with the same outcome, unfortunately. /dev/dri exist, codecs activated. HW Acc doesn't work. Would be really greatful if you managed to solve this.

Share this post


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

no, not related and your xeon does not have a gpu like a desktop cpu, quick sync video is a gpu feature

I saw another person passing through a lsi card and has missing smart info as well. Is this a driver issue?

Share this post


Link to post
Share on other sites
4 hours ago, sarieri said:

I saw another person passing through a lsi card and has missing smart info as well. Is this a driver issue?

yes its on my list what to check and to do next

  • Like 1
  • Thanks 1

Share this post


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

yes its on my list what to check and to do next

Thank you so much. 

Share this post


Link to post
Share on other sites

I already check.

 

Fresh install, extra it work, but have problem with reboot (can't reboot), i will post log ASAP.

 

Share this post


Link to post
Share on other sites
Posted (edited)
В 20.04.2020 в 16:54, dolbycat сказал:

H/W Transcoding works very well.

Can confirm this, /dev/dri returns and H/W transcoding works well (G4620/Z170). Updated extra.lzma «in situ» (via temporary synoboot2 mount) after upgrading to 6.2.3.

Edited by The Chief

Share this post


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.