Jump to content
XPEnology Community

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


IG-88

Recommended Posts

On 4/17/2021 at 12:45 PM, SnowDrifter said:

Looking to get this going so I can get my second ethernet port working. If someone wouldn’t mind sanity checking before I dive into this

Hardware:

ASrock Rack C246 WSI - 2 x RJ45 GLAN by Intel® i210+Intel® i219LM
Intel I3-9100
DMS 6.2.2-23739 – jun 1.04b – 918+

Install:

SSH w/ root
rm -rf /usr/lib/modules/update/*
rm -rf /usr/lib/firmware/i915/*

Shut down the system

Chuck the usb into my computer, mount w/ osfmount, replace the original files in the partition with the updated lzma

done?

Threw together a test install w/ a new drive and different USB.

Network doesn't seem to wake up once any of the updated lzmas are applied. find.synology.com not finding anything. Viewing router shows nothing

Link to comment
Share on other sites

7 hours ago, SnowDrifter said:

Threw together a test install w/ a new drive and different USB.

Network doesn't seem to wake up once any of the updated lzmas are applied. find.synology.com not finding anything. Viewing router shows nothing

Decided to try a thing

Did a test update to dsm 6.2.3, then installed update 3 (which is interesting because I never could get it to install...)

Loaded up the corresponding driver pack from there, and everything works flawlessly

Did once again on working machine, and same result. All settled

Link to comment
Share on other sites

14 hours ago, SnowDrifter said:

Did a test update to dsm 6.2.3, then installed update 3 (which is interesting because I never could get it to install...)
Loaded up the corresponding driver pack from there, and everything works flawlessly
Did once again on working machine, and same result. All settled

from my point of view there is no reason to keep 6.2.2

6.2.3 works better and is again driver compatible to the original 6.2.0 the loader was made with

only downside is the non working i915 with jun's original extra/extra2 but thats fixed with my extra/extra2

Link to comment
Share on other sites

  • 1 month later...

Hi,

Thanks for your great work.

I have a old configuration (i3 Haswell and an ethernet chipset RTL81111DL + DSM6.1). I would like to update my configuration to DSM6.2.2. But I have some problems with the original Jun.1.04. It seems that my network chipset is not detected. 

Could you add the RTL8111DL driver to your extra. lzma ?

Thanks

 

Link to comment
Share on other sites

hi,

i have currently an P8H77-I which has a Realtek® RTL8111F.

 

i am facing some issue...

 

so far, i manage to have the whole thing working with the 6.1.7 version but as soon as i go to 6.2.3 then i am stuck with network not reachable (not cool for a nas).

i have read several post so i decided to include the extra drivers in the *.img on the 30mb partition but so far...no luck...

 

so i took: synoboot(_ds3615_6.2).img and added the file at the beginning of the topic: extra3615_v0.11_test.zip

 

did i miss something?

thank you in advance for your help :-)

Link to comment
Share on other sites

On 5/23/2021 at 12:52 AM, titoum said:

hi,

i have currently an P8H77-I which has a Realtek® RTL8111F.

 

i am facing some issue...

 

so far, i manage to have the whole thing working with the 6.1.7 version but as soon as i go to 6.2.3 then i am stuck with network not reachable (not cool for a nas).

i have read several post so i decided to include the extra drivers in the *.img on the 30mb partition but so far...no luck...

 

so i took: synoboot(_ds3615_6.2).img and added the file at the beginning of the topic: extra3615_v0.11_test.zip

 

did i miss something?

thank you in advance for your help :-)

nvm i went for a E1G42ETBLK so i dont face any problem in the futur.

Link to comment
Share on other sites

  • 2 months later...

after update / clean install to 6.2.3. package center stopped working. 'connection failed bla..bla.'. i have manually entered my dns to 8.8.8.8 even in the router has the same dns. delete /.xpenoboot and then reboot the package center show no package at all. is this has to do with the bootloader that not properly patch the system. 

on dsm 5.2 i have no trouble at all seeing my package available. please any help would be appreciated

Link to comment
Share on other sites

  • 1 month later...

I am trying to install 6.2.3 as a clean install and followed guides however cannot get N54L to be seen on network to apply corresponding .pat file.

I have tried internal NIC as it is supposed to be working on 6.2.3 and Realtek RTL8111E card i have installed in it too. Added VID and PID and mac address's and s/n, I am going crazy as i have 4 similar servers working just fine. Using 'Jun's Loader v1.03b DS3615xs'.

 

Any suggestions will be appreciated

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...

Hi All

I'm testing some hardware before updating my 'prod' systems

 

J3455 itx board and Intel add on nic
1 drive attached to mobo onboard sata 1
DS918+ boot loader created/installed DSM6.2.3-25426 and U3 to the mobo drive - all working fine
Replaced extra.lzma and extra2.lzma with @IG88's driver extension v.0.13.3 files to boot loader partition

 

Added Supermicro Marvell 98SE6x sas controller with 2 (sata) drives attached

 

Booting system the 2 drives are visible in the Marvell bios

 

DSM Storage Manager only shows the 1 drive attached to the onboard sata

 

Putty connection to the system and running various commands;

 

lspci lists;

class 0104: Device 11ab:6485 - The 98SE controller
class 0000: Device 1b4b:9215 - The onboard Marvell 9215 controller

 

dmesg output for the Marvell mvsas module;

 

[   26.873356] drivers/scsi/mvsas/mv_sas.c 1079:phy 0 attach dev info is 0
[   26.873366] drivers/scsi/mvsas/mv_sas.c 1081:phy 0 attach sas addr is 0
[   26.974352] drivers/scsi/mvsas/mv_sas.c 1079:phy 1 attach dev info is 0
[   26.974357] drivers/scsi/mvsas/mv_sas.c 1081:phy 1 attach sas addr is 0
[   27.075349] drivers/scsi/mvsas/mv_sas.c 1079:phy 2 attach dev info is 0
[   27.075354] drivers/scsi/mvsas/mv_sas.c 1081:phy 2 attach sas addr is 0
[   27.176346] drivers/scsi/mvsas/mv_sas.c 1079:phy 3 attach dev info is 0
[   27.176351] drivers/scsi/mvsas/mv_sas.c 1081:phy 3 attach sas addr is 0
[   27.277344] drivers/scsi/mvsas/mv_sas.c 1079:phy 4 attach dev info is 0
[   27.277350] drivers/scsi/mvsas/mv_sas.c 1081:phy 4 attach sas addr is 0
[   27.378341] drivers/scsi/mvsas/mv_sas.c 1079:phy 5 attach dev info is 0
[   27.378346] drivers/scsi/mvsas/mv_sas.c 1081:phy 5 attach sas addr is 0
[   27.579363] drivers/scsi/mvsas/mv_sas.c 1079:phy 6 attach dev info is 0
[   27.579365] drivers/scsi/mvsas/mv_sas.c 1081:phy 6 attach sas addr is 6
[   27.780359] drivers/scsi/mvsas/mv_sas.c 1079:phy 7 attach dev info is 0
[   27.780361] drivers/scsi/mvsas/mv_sas.c 1081:phy 7 attach sas addr is 7
[   27.780371] scsi host3: mvsas
[   27.784221] drivers/scsi/mvsas/mv_sas.c 277:phy 6 byte dmaded.
[   27.784227] drivers/scsi/mvsas/mv_sas.c 277:phy 7 byte dmaded.
[   27.784379] sas: phy-3:6 added to port-3:0, phy_mask:0x40 ( 600000000000000)
[   27.784428] sas: phy-3:7 added to port-3:1, phy_mask:0x80 ( 700000000000000)
[   27.784450] sas: DOING DISCOVERY on port 0, pid:29
[   27.784452] sas: ATA device seen but CONFIG_SCSI_SAS_ATA=N so cannot attach
[   27.784453] sas: unhandled device 5
[   27.784460] sas: DONE DISCOVERY on port 0, pid:29, result:-6
[   27.784465] sas: DOING DISCOVERY on port 1, pid:29
[   27.784466] sas: ATA device seen but CONFIG_SCSI_SAS_ATA=N so cannot attach
[   27.784467] sas: unhandled device 5
[   27.784471] sas: DONE DISCOVERY on port 1, pid:29, result:-6

 

Seems that the mvsas module is loading ok and finding the drives, but not connecting due to the CONFIG_SCSI_SAS_ATA=N status

 

In an old forum thread from 2018 (https://xpenology.com/forum/topic/12679-progress-of-62-loader/page/13/) @IG88 had recompiled the mvsas and libsas with CONFIG_SCSI_SAS_ATA=Y which seemed to resolve the issue

 

Does anyone have this Marvell or mvsas based card working with 6.2.3 and the v.0.13.3 driver extensions?


If IG88 sees this - does your 0.13.3 extension include the recompiled CONFIG...=Y modules
Have I missed something with my setup ?

Link to comment
Share on other sites

On 10/23/2021 at 11:52 PM, sbv3000 said:

Hi All

I'm testing some hardware before updating my 'prod' systems

 

J3455 itx board and Intel add on nic
1 drive attached to mobo onboard sata 1
DS918+ boot loader created/installed DSM6.2.3-25426 and U3 to the mobo drive - all working fine
Replaced extra.lzma and extra2.lzma with @IG88's driver extension v.0.13.3 files to boot loader partition

 

Added Supermicro Marvell 98SE6x sas controller with 2 (sata) drives attached

 

Booting system the 2 drives are visible in the Marvell bios

 

DSM Storage Manager only shows the 1 drive attached to the onboard sata

 

Putty connection to the system and running various commands;

 

lspci lists;

class 0104: Device 11ab:6485 - The 98SE controller
class 0000: Device 1b4b:9215 - The onboard Marvell 9215 controller

 

dmesg output for the Marvell mvsas module;

 

[   26.873356] drivers/scsi/mvsas/mv_sas.c 1079:phy 0 attach dev info is 0
[   26.873366] drivers/scsi/mvsas/mv_sas.c 1081:phy 0 attach sas addr is 0
[   26.974352] drivers/scsi/mvsas/mv_sas.c 1079:phy 1 attach dev info is 0
[   26.974357] drivers/scsi/mvsas/mv_sas.c 1081:phy 1 attach sas addr is 0
[   27.075349] drivers/scsi/mvsas/mv_sas.c 1079:phy 2 attach dev info is 0
[   27.075354] drivers/scsi/mvsas/mv_sas.c 1081:phy 2 attach sas addr is 0
[   27.176346] drivers/scsi/mvsas/mv_sas.c 1079:phy 3 attach dev info is 0
[   27.176351] drivers/scsi/mvsas/mv_sas.c 1081:phy 3 attach sas addr is 0
[   27.277344] drivers/scsi/mvsas/mv_sas.c 1079:phy 4 attach dev info is 0
[   27.277350] drivers/scsi/mvsas/mv_sas.c 1081:phy 4 attach sas addr is 0
[   27.378341] drivers/scsi/mvsas/mv_sas.c 1079:phy 5 attach dev info is 0
[   27.378346] drivers/scsi/mvsas/mv_sas.c 1081:phy 5 attach sas addr is 0
[   27.579363] drivers/scsi/mvsas/mv_sas.c 1079:phy 6 attach dev info is 0
[   27.579365] drivers/scsi/mvsas/mv_sas.c 1081:phy 6 attach sas addr is 6
[   27.780359] drivers/scsi/mvsas/mv_sas.c 1079:phy 7 attach dev info is 0
[   27.780361] drivers/scsi/mvsas/mv_sas.c 1081:phy 7 attach sas addr is 7
[   27.780371] scsi host3: mvsas
[   27.784221] drivers/scsi/mvsas/mv_sas.c 277:phy 6 byte dmaded.
[   27.784227] drivers/scsi/mvsas/mv_sas.c 277:phy 7 byte dmaded.
[   27.784379] sas: phy-3:6 added to port-3:0, phy_mask:0x40 ( 600000000000000)
[   27.784428] sas: phy-3:7 added to port-3:1, phy_mask:0x80 ( 700000000000000)
[   27.784450] sas: DOING DISCOVERY on port 0, pid:29
[   27.784452] sas: ATA device seen but CONFIG_SCSI_SAS_ATA=N so cannot attach
[   27.784453] sas: unhandled device 5
[   27.784460] sas: DONE DISCOVERY on port 0, pid:29, result:-6
[   27.784465] sas: DOING DISCOVERY on port 1, pid:29
[   27.784466] sas: ATA device seen but CONFIG_SCSI_SAS_ATA=N so cannot attach
[   27.784467] sas: unhandled device 5
[   27.784471] sas: DONE DISCOVERY on port 1, pid:29, result:-6

 

Seems that the mvsas module is loading ok and finding the drives, but not connecting due to the CONFIG_SCSI_SAS_ATA=N status

 

In an old forum thread from 2018 (https://xpenology.com/forum/topic/12679-progress-of-62-loader/page/13/) @IG88 had recompiled the mvsas and libsas with CONFIG_SCSI_SAS_ATA=Y which seemed to resolve the issue

 

Does anyone have this Marvell or mvsas based card working with 6.2.3 and the v.0.13.3 driver extensions?


If IG88 sees this - does your 0.13.3 extension include the recompiled CONFIG...=Y modules
Have I missed something with my setup ?

Just as a follow up to this I connected an old 137GB SAS drive to the controller and it shows up ok in Storage Manager and the demsg output is;

[   19.258492] drivers/scsi/mvsas/mv_sas.c 1079:phy 3 attach dev info is 80001
[   19.258494] drivers/scsi/mvsas/mv_sas.c 1081:phy 3 attach sas addr is f90ad50e00c50050
[   19.662485] scsi host4: mvsas
[   20.762159] drivers/scsi/mvsas/mv_sas.c 277:phy 3 byte dmaded.
[   20.762268] sas: phy-4:3 added to port-4:0, phy_mask:0x8 (5000c5000ed50af9)
[   20.762275] drivers/scsi/mvsas/mv_sas.c 1116:set wide port phy map 8
[   20.812335] sas: DOING DISCOVERY on port 0, pid:29
[   20.812341] sas: DONE DISCOVERY on port 0, pid:29, result:0
[   20.818290] scsi 4:0:0:0: Direct-Access     HP       DG146BB976               HPDC PQ: 0 ANSI: 5
[   20.822575] sd 4:0:0:0: [sde] 286749488 512-byte logical blocks: (147 GB/137 GiB)
[   20.824551] sd 4:0:0:0: [sde] Write Protect is off
[   20.824559] sd 4:0:0:0: [sde] Mode Sense: db 00 10 08
[   20.826472] sd 4:0:0:0: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[   20.839796]  sde: sde1 sde2 sde3
[   20.846383] sd 4:0:0:0: [sde] Attached SCSI disk

 

 

 

Link to comment
Share on other sites

  • 3 weeks later...
1 hour ago, Kamele0N said:

Even links in 6.2.3 topic? 

the 6.2.3 where renewed this week, the other might get new links next weekend (if i have time)

imho the <6.2.3 versions are obsolete, maybe the 6.1 versions have some roome as they can be easyer to handle because of supporting uefi and bios/csm (1.03b only supports bios/csm)

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

  • 1 month later...
On 1/8/2020 at 10:29 PM, IG-88 said:

manual says

"supports Lan 10/100 Fast ethernet by Realtek 8105e"

thats not the "nornal" 10/100/1000 realtek that some ancient thing and with just 100Mbit (= 10MByte/s) you will not have anything usefull even it it works

there are a few 100Mbit nic drivers in the package but im not going to invest any time to add more as its pointless when using a nas now days

put in a 1Gbit nic

 

edit: i check in the old thread with the driver list and the driver would be r8101 for this is in the 3615/17 with the latest version, maybe something else is the problem

 

simply use 1.02b. no additional driver

Link to comment
Share on other sites

  • 1 month later...
On 12/19/2021 at 8:47 PM, IG-88 said:

links renewed

 

14 hours ago, arnoz said:

the dead links have returned !

 

thks again !

 

Confirmed links are dead for all but the DS3615 file.

 

New mirror links below.  Please consult the OP for any additional info needed!

 

0.8_syno ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_syno
Original: https://gofile.io/d/mVBHGi
Filename: extra918plus_v0.8_syno.zip
SHA256: 21B0CCC8BE24A71311D3CC6D7241D8D8887BE367C800AC97CE2CCB84B48D869A
Mirrors: Clicknupload, Dailyuploads, usersdrive, Zippyshare

 

0.8_std ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_std
Original: https://gofile.io/d/y8neID
Filename: extra918plus_v0.8_std.zip
SHA256: F611BCA5457A74AE65ABC4596F1D0E6B36A2749B16A827087D97C1CAF3FEA89A
Mirrors: Clicknupload, Dailyuploads, usersdrive, Zippyshare

 

0.8_recovery ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_recovery
Original: https://gofile.io/d/4K3WPE
Filename: extra918plus_v0.8_recovery.zip
SHA256: 5236CC6235FB7B5BB303460FC0281730EEA64852D210DA636E472299C07DE5E5
Mirrors: Clicknupload, Dailyuploads, usersdrive, Zippyshare

 

DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test
Original: https://gofile.io/d/iQuInV
Filename: extra3615_v0.5_test.zip
SHA256: BAA019C55B0D4366864DE67E29D45A2F624877726552DA2AD64E4057143DBAF0
Mirrors: Clicknupload, Dailyuploads, usersdrive, Zippyshare

 

DS3617: extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test
Original: https://gofile.io/d/blXT9f
Filename: extra3617_v0.5_test
SHA256: 4A2922F5181B3DB604262236CE70BA7B1927A829B9C67F53B613F40C85DA9209
Mirrors: Clicknupload, Dailyuploads, usersdrive, Zippyshare

Edited by rcached
Link to comment
Share on other sites

  • 1 month later...

 

13 hours ago, Xpenilogy10700 said:

I have 10700 with 1.04b + DSM 6.2.3 up3

used 9BC5 with 2 lzma files

it was working fine with no HW transcoding

 

because its pci id is not in the driver, the device will be ignored

 

On 4/20/2020 at 2:56 AM, IG-88 said:

-> one user negative feedback for a i9-10900 (8086:9BC5) system does not boot anymore - seems to be a solid hands off?

 

that one is from the 1st post, so we already knew about that for 0x9bc5

 

 

13 hours ago, Xpenilogy10700 said:

now it won’t boot

 

did you fix that? are you capable of dealing with this of your own? if yes we could go forward and try to shift the pci id to other i915 devices

there are GT1/GT3/GT3 and also different hardware gen's in the driver, with the "old" patch we used to handle it like "8086:3E92 => iGPU UHD 630, Low End Desktop 9 Series"

 

 

Quote

really hope we could have the working 9BC5 patch, but looks like I have to move to 10400 which is the most cost effective atm.

 

that depends how much time you are willing to invest into testing more driver variations

i was looking for the kernel source and pocopico pointed me into the right direction, so i did a patch and new binary driver for 7.0 where its much easier to switch the position on how the drier should handle a certain pci id (not patching the original driver, really adding devices)

it would take only a few minutes to create some new i915.ko drivers each handling your pci id differently, you would have to swap the i915 and depending on the state (like not booting) it might be a little more work to do that as you might need to boot a recovery linux

i had a "recovery" loader for 6.2.2 to remove a non working i915 driver from the system  (different location as we would need it now) but i could use that to create a recovery loader for 6.2.3 that removes the file in question (or its more like a recovery extra/extra2, the loader would still be the same)

 

in the end we could can use the information for 7.0 too

"downside" might be that in about one year its not needed anymore if synology releases a new hardware needing a new i915 driver in the synology kernel and if that one it for elkardt or jasper lake we would have kernel module wich much newer code that can deal with 10th/11th  gen cpu's

 

beside this there is also the possibility to ventre deeper into nvidia support and ignore qsv and videostation and use jellyfinn (free) oder plex or emby

Edited by IG-88
Link to comment
Share on other sites

  • 4 weeks later...
On 4/3/2022 at 10:54 AM, mydownload said:

i've tried to install 6.2.2 on my prolian ML 350 G6 with HP smart array P410i. Disks are seen but in have an error during format. I'm using V1.03b loader.

 

My disks are on raid0. Any idea why i cannot format (error 35), not found similar on forum.

as i could not test myself and the feedback for external source hpsa driver was negative we kept the original driver from kernel 3.10

in most cases with hpsa people use a hypervisor to handle raid and disks properly and use dsm as a vm

apart from hypervisor/vm there is also redpill loader and dsm 7.0 if you use 3617 or 3622 you would have kernel 4.4 as base, maybe the 4.4 kernel default driver works better (driver version 2.0.2 vs 3.4.16)

you can read this for a start

https://xpenology.club/install-dsm-7-on-baremetal-or-vm/

but keep in mind its still in the developer section of the forum, dont expect everything polished and wit a lot of support

(and the link to a external howto is also a hint that its not yet "supported" as the general solution here)

 

ps: its also possible to "replace" the hpsa controller with a lsi sas in it-mode (hba mode), you would be able to use the sas backplane of the server and have a better supported solution (lsi sas comes with native drivers from synology, you would need a "older" controller but thats the cheaper one anyway, 9211-8i with the chip sas2008 is the most used one, has a ton of oem versions that can are crossflashed and in IT mode)

https://www.servethehome.com/lsi-sas-2008-raid-controller-hba-information/

Link to comment
Share on other sites

21 hours ago, IG-88 said:

as i could not test myself and the feedback for external source hpsa driver was negative we kept the original driver from kernel 3.10

in most cases with hpsa people use a hypervisor to handle raid and disks properly and use dsm as a vm

apart from hypervisor/vm there is also redpill loader and dsm 7.0 if you use 3617 or 3622 you would have kernel 4.4 as base, maybe the 4.4 kernel default driver works better (driver version 2.0.2 vs 3.4.16)

you can read this for a start

https://xpenology.club/install-dsm-7-on-baremetal-or-vm/

but keep in mind its still in the developer section of the forum, dont expect everything polished and wit a lot of support

(and the link to a external howto is also a hint that its not yet "supported" as the general solution here)

 

ps: its also possible to "replace" the hpsa controller with a lsi sas in it-mode (hba mode), you would be able to use the sas backplane of the server and have a better supported solution (lsi sas comes with native drivers from synology, you would need a "older" controller but thats the cheaper one anyway, 9211-8i with the chip sas2008 is the most used one, has a ton of oem versions that can are crossflashed and in IT mode)

https://www.servethehome.com/lsi-sas-2008-raid-controller-hba-information/

Hi,

 

thanks for your reply. I've just tried with Repill (lastest release). Worst issue than wih Jun's loader, no disk seen. test with Broadwell and bromolow.

 

i've also delete all partitions on all disks (live ubuntu).

 

any other idea ?

 

thanks,

Link to comment
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.

×
×
  • Create New...