jun

DSM 6.x.x Loader

Recommended Posts

trying juns version and its stuck at booting kernel with nothing else displaying after parsing elf. :-|:-| well 1 server totally fucked :-|:-| going to wait till something else pops up.

 

This is expected. You wont see anything else. Just go to http://find.synology.com to find your machine on the local network.

 

no I think my issue is with this version It hangs after parsing elf. server is up using the old bootloader 5597. How long do we wait after booting kernel? so should I just let it sit at booting kernel and see if it responds find.synology.com? or.......... when it says booting kernel its doing something?. despite no text output? haha im so tired i misread your message okay so ill let it do its thing,. After the 5967 runs a parity check. currently 8.67% so i will have to wait many hours before I attempt this loader again.

 

okay also I was going to say what version of DSM are you running I have the same exact board on my other server which is running 5644. Where is everyone downloading dsm 6 from and up to what version or revision is it safe before things get unstable?

Share this post


Link to post
Share on other sites

Works good with my config :


  • - MC : ASUS P8H77-I
    - CPU Intel Core i3-3220T
    - HDD : 6x WD 2 & 6To

Share this post


Link to post
Share on other sites
trying juns version and its stuck at booting kernel with nothing else displaying after parsing elf. :-|:-| well 1 server totally fucked :-|:-| going to wait till something else pops up.

 

This is expected. You wont see anything else. Just go to http://find.synology.com to find your machine on the local network.

 

no I think my issue is with this version It hangs after parsing elf. server is up using the old bootloader 5597. How long do we wait after booting kernel? so should I just let it sit at booting kernel and see if it responds find.synology.com? or.......... when it says booting kernel its doing something?. despite no text output? haha im so tired i misread your message okay so ill let it do its thing,. After the 5967 runs a parity check. currently 8.67% so i will have to wait many hours before I attempt this loader again.

 

okay also I was going to say what version of DSM are you running I have the same exact board on my other server which is running 5644. Where is everyone downloading dsm 6 from and up to what version or revision is it safe before things get unstable?

 

Yes let it finish the parity check then try again.

 

You don't have to wait after you see parsing elf. Simply go to http://find.synology.com and you should see your NAS.

 

You need to download the latest DSM 6.0.2 from Synology's servers, here. It works up to the latest update which is update 2.

Share this post


Link to post
Share on other sites

I used modified DS916+ on a J3160 board, hw transcoding seems work.

 

Hi jun, can you share this image so can I test it with my GA-N3150N-D3V ?

Thanks!

 

Ciao

ema

Share this post


Link to post
Share on other sites

e1000e: 82578DC/82578DM/Gigabit CT Desktop Adapter/PRO/1000 PT/PF/I217-LM/V/I218-V/LM/I219 LM/V

 

Hello Arcao,

 

Any reason why a GigaByte B150M-D3H MB with an e1000e (i219V) is not recognised? I see it's included among the modules you repacked. Would the kernel need to be patched for this NIC to work?

Edited by Guest

Share this post


Link to post
Share on other sites
During my test with updated network modules, I have tried to add sata driver including ata_piix (needed for my old ICH7 mobo).

When trying to insmod these sata modules it complain about unknow syno_libata_get_index or something like that.

This function should be included in the kernel (function declared in libata-core) but it doesn't.

 

I even try building these module with vanilla 3.10.77 kernel.

sata_sil, sata_via, sata_amd .... load ok but ata_piix module is stuck during insmod.

Of course using vanilla is not great idea and probably will cause disk naming conflict and other bugs.

 

I tried to set CONFIG_SYNO_FIXED_DISK_NAME=n (in menuconfig: Synology Enhancement Features -> Device Drivers -> SATA -> Use Fixed Disk Name) and compile ata_piix kernel module. Now it's successfully loaded with insmod, but hard to say how it will work without Use Fixed Disk Name.

 

Use Fixed Disk Name

Make internal SATA disk use fixed device name. For example, the first channel is sda, the second is sdb, etc. All USB disk would start from sdq.

 

I have seen a report where the drives of a P5KPL-AM Asus motherboard with an Intel® G31/ICH7 chipset could not be found. Would the above be the reason?

Share this post


Link to post
Share on other sites
Hi guys,

 

Here is my updated ramdisk.lzma: https://mega.nz/#!KBFRxZiY!m_w2uCnUvTyH2leI6hKn1GMDbGRV6MeOLmUFrzHc4R0

 

Backup your existing ramdisk.lzma (for sure) from image/DS3615xs/ on your usb boot drive and replace it with the ramdisk.lzma from archive.

 

Or download complete img file:

 

 

 

Change log:

Added below kernel modules:

 

r8101: RTL8100E/RTL8101E/RTL8102E-GR/RTL8103E(L) RTL8102E(L)/RTL8101E/RTL8103T RTL8401/RTL8401P/RTL8105E RTL8402/RTL8106E/RTL8106EUS

r8168: RTL8111B/RTL8168B/RTL8111/RTL8168 RTL8111C/RTL8111CP/RTL8111D(L) RTL8168C/RTL8111DP/RTL8111E

r8168: RTL8168E/RTL8111F/RTL8411 RTL8111G/RTL8111GUS/RTL8411B(N) RTL8118AS

* Note: r8169 from Trantor archive doesn't work with my on-board Realtek RTL8111GR. So I kept the existing which is also much bigger.

 

e1000e: 82573L/82572EI/82571EB/82573E/82573V/82567/82574L/82566MM/82566MC

e1000e: 82566DM/82566DC/82563EB/82574IT/82583V/82579LM/82579V/82577LC/82577LM

e1000e: 82578DC/82578DM/Gigabit CT Desktop Adapter/PRO/1000 PT/PF/I217-LM/V/I218-V/LM/I219 LM/V

 

bnx2: Broadcom NetXtremeII BCM5706/BCM5708/5709/5716

bnx2x: Broadcom NetXtremeII 10Gb BCM57710/BCM57711/BCM57711E/BCM57712

tg3: Broadcom Tigon3 BCM5705/BCM5703/BCM5702/BCM5701/BCM5700/BCM5721/BCM5751/BCM5788/BCM5704/BCM5752/BCM5789

tg3 : BCM5723/BCM5761/BCM5787/BCM5755/BCM5722/BCM5754/BCM57781/BCM57785/BCM5718BCM57765/BCM57761

tg3: BCM5719/BCM5725/BCM5762/BCM5720/BCM57790/BCM57795/BCM57766/BCM57780

* Note: Existing modules updated with version from Trantor archive. I also added missing firmware files.

 

ax88179_178a : ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet

 

mpt2sas: LSI SAS 6Gb/s Host Adapters SAS2004, SAS2008, SAS2108, SAS2116, SAS2208, SAS2308 and SSS6200

* Note: It's already included in existing ramdisk but not loaded. By dmesg it's started correctly.

 

evdev, button: for acpid

 

Compiling any disk adapter modules is not possible at the moment due to unexported syno_libata_get_index function (declared in libata-core). So only way to fix it is recompile kernel (we don't have latest kernel sources to do that) or somehow modify drive adapter sources to not depends on syno_libata_get_index function.

 

Edit:

Files moved to mega.nz from my webhosting.

 

Thank you very much for this release. Is it possible that for the next release include support also for ata_piix module. On my bare metal (old IBM Server) the Hard disks are not recognized.

Share this post


Link to post
Share on other sites

Wow!!!! how to do that?

 

Is the method all the same as 3615xs just replace the 3615xs.pat by DS916+.pat from synology?

 

Or any details I need to know , great thanks for reply me!!

Share this post


Link to post
Share on other sites
so I have a bare metal with 8 drives and a M1015/SAS2008 none are recognized, is this module loaded into the kernel?

 

thanks

 

The mpt2sas driver is not loaded. This is a known issues since the first couple pages of this post. I believe user "quicknick" is working on a kernel to include support for LSI 2008 based firmware. There are many of us waiting to get our LSI 92118i (in IT mode) cards to work.

Share this post


Link to post
Share on other sites

Hello ,

I installed XPEnoboot 5.2-5967.1 everything works stable

img installed on usb trying to make the migration but at 52% shows an error file my motherboard is

 

http://www.jetwaycomputer.com/NP93.html

 

Model No. NP93-2930 | NP93-2807

Part No. JNP93-2930 | JNP93-2807

Jetway NP93 Pico-ITX Motherboard Specification

Processor Fanless INTEL® Bay Trail-M Celeron N2930 1.83GHz Processor SoC, Quad-Core, 7.5W

Fanless INTEL® Bay Trail-M Celeron N2807 SoC Processor 1.58GHz, Dual-Core, 4.3W

* Low-profile heatsink Installed for Basic Bench Testing

Onboard Memory 2GB DDR3L-1333 non-expandable

Graphics Intel® HD Graphics

Audio Realtek ALC662 Audio

LAN 1 x Realtek Gigabit Ethernet RTL8111G

Storage 1 x full size mSATA slot

 

 

1 x SATA2 3Gb / s Connector

Super IO FINTEK F81803U

Form Factor Pico-ITX Form Factor (100mm X 72mm)

Edited by Guest

Share this post


Link to post
Share on other sites
During my test with updated network modules, I have tried to add sata driver including ata_piix (needed for my old ICH7 mobo).

When trying to insmod these sata modules it complain about unknow syno_libata_get_index or something like that.

This function should be included in the kernel (function declared in libata-core) but it doesn't.

 

I even try building these module with vanilla 3.10.77 kernel.

sata_sil, sata_via, sata_amd .... load ok but ata_piix module is stuck during insmod.

Of course using vanilla is not great idea and probably will cause disk naming conflict and other bugs.

 

I tried to set CONFIG_SYNO_FIXED_DISK_NAME=n (in menuconfig: Synology Enhancement Features -> Device Drivers -> SATA -> Use Fixed Disk Name) and compile ata_piix kernel module. Now it's successfully loaded with insmod, but hard to say how it will work without Use Fixed Disk Name.

 

Use Fixed Disk Name

Make internal SATA disk use fixed device name. For example, the first channel is sda, the second is sdb, etc. All USB disk would start from sdq.

 

Interesting...

If syno_libata_get_index is missing in the genuine syno kernel it means that it's disable, otherwise when we insmod module it shouldn't complain about missing function.

Can you repack this in a test ramdisk so I can test it with my mobo using ata_piix.

 

About your r8169 not working I think it's a crappy adapter that need firmware like my old dlink s*** ^^

r8169 from kernel is FULL of bugs for lot of adapters. This is why realtek create r8168 to split support in separate modules.

 

Edited OP with new links.

Share this post


Link to post
Share on other sites

Thanks for all the hard work on making it all possible. I have the Gigabyte H97N-WIFI (rev. 1.1) with two LAN cards (intel and realtek chipsets), how can i enable the intel lan ? When i upgraded tot DSM6 in the grub file i added the mac address of the realtek lan.

 

how can i enable the intel lan on the DSM, it is possible to add the mac of the intel lan in the grub ?

 

I want to enable both lan cards and create a BOND connection

Thank you !

Share this post


Link to post
Share on other sites

 

I used modified DS916+ on a J3160 board, hw transcoding seems work.

 

 

Wow!!!! how to do that?

 

Is the method all the same as 3615xs just replace the 3615xs.pat by DS916+.pat from synology?

 

Or any details I need to know , great thanks for reply me!!

Share this post


Link to post
Share on other sites

nope, it just not exported.

That is not a big problem, comment out any usage to make it compile, its only function is reordering disk numbers, and we can live without it.

The real problem is some kernel structures have extra fields in synology kernel, disble this option just cause more mismatches.

Share this post


Link to post
Share on other sites

e1000e: 82578DC/82578DM/Gigabit CT Desktop Adapter/PRO/1000 PT/PF/I217-LM/V/I218-V/LM/I219 LM/V

 

Hello Arcao,

 

Any reason why a Pentium G4400 with an e1000e (i219V) is not recognised? I see it's included among the modules you repacked. Would the kernel need to be patched for this NIC to work?

 

 

lspci -v result :

0000:00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
       Subsystem: Gigabyte Technology Co., Ltd Device e000
       Flags: bus master, fast devsel, latency 0, IRQ 10
       Memory at df100000 (32-bit, non-prefetchable) [size=128K]
       Capabilities: [c8] Power Management version 3
       Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
       Capabilities: [e0] PCI Advanced Features

0000:01:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5722 Gigabit Ethernet PCI Express
       Subsystem: Broadcom Limited NetXtreme BCM5722 Gigabit Ethernet PCI Express
       Flags: bus master, fast devsel, latency 0, IRQ 139
       Memory at df000000 (64-bit, non-prefetchable) [size=64K]
       Expansion ROM at  [disabled]
       Capabilities: [48] Power Management version 3
       Capabilities: [50] Vital Product Data
       Capabilities: [58] Vendor Specific Information: Len=78 <?>
       Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+
       Capabilities: [d0] Express Endpoint, MSI 00
       Capabilities: [100] Advanced Error Reporting
       Capabilities: [13c] Virtual Channel
       Capabilities: [160] Device Serial Number xx-xx-xx-xx-xx-xx-xx-xx
       Capabilities: [16c] Power Budgeting <?>
       Kernel driver in use: tg3

Something that i found in /var/log/messages

2016-10-27T16:00:09+02:00 SYNOLOGY synonetd: net_if_is_link.c:40 Cannot get link status: No such device
2016-10-27T16:00:09+02:00 SYNOLOGY synonetd: net_if_is_link.c:119 get link status failed on eth0
2016-10-27T16:00:09+02:00 SYNOLOGY synonetd: net_if_is_link.c:40 Cannot get link status: No such device
2016-10-27T16:00:09+02:00 SYNOLOGY synonetd: net_if_is_link.c:119 get link status failed on eth0
insmod: ERROR: could not insert module /lib/modules/cnic.ko: Unknown symbol in module
2016-10-27T16:00:10+02:00 SYNOLOGY kernel: [ 11.212398] cnic: Unknown symbol __uio_register_device (err 0)
2016-10-27T16:00:10+02:00 SYNOLOGY kernel: [ 11.212416] cnic: Unknown symbol uio_event_notify (err 0)
2016-10-27T16:00:10+02:00 SYNOLOGY kernel: [ 11.212432] cnic: Unknown symbol uio_unregister_device (err 0)

 

Mother board : Gigabyte B150M-D3H

 

if you have any clue :razz:

Share this post


Link to post
Share on other sites

I too am having issues with the Intel 219 NIC. Works for step one (finding the box and uploading the PAT) but doesn't seem to work after the reboot. Unfort. i don't have a serial connection so I can't debug stage 2.

Share this post


Link to post
Share on other sites

Yeah, there is feature/bug in loading kernel modules in Jun's modification. At first DISK_MODULES are loaded from ramdisk in /linuxrc.syno, that's ok. In /sbin/post.init are EXTRA_MODULES copied to hdd only when they are not exist and they are then loaded after chroot from hdd (in hdd's /etc.default/rc). So:

  • The installation step replace kernel modules (e.g. e1000e) with their version from pat file that cause not loading our updated kernel modules from ramdisk. Thus we have to replace these bad modules after reboot with version from ramdisk.
  • Also rc.modules file is not updated after first copy in the installation step. Thus when is updated from Jun's original ramdisk to my ramdisk v1, added kernel modules are not loaded. This explain why my network card didn't work with Trantor's r8169 module because the important r8168 wasn't loaded.

 

I will fix both in my v2 ramdisk.

Edited by Guest

Share this post


Link to post
Share on other sites
Yeah, there is bug in loading kernel modules in Jun's modification. At first DISK_MODULES are loaded from ramdisk in /linuxrc.syno, that's ok. In /sbin/post.init are EXTRA_MODULES copied to hdd only when they are not exist and they are then loaded after chroot from hdd (in hdd's /etc.default/rc). So:

  • The installation step replace kernel modules (e.g. e1000e) with their version from pat file that cause not loading our updated kernel modules from ramdisk. Thus we have to replace these bad modules after reboot with version from ramdisk.
  • Also rc.modules file is not updated after first copy in the installation step. Thus when is updated from Jun's original ramdisk to my ramdisk v1, added kernel modules are not loaded. This explain why my network card didn't work with Trantor's r8169 module because the important r8168 wasn't loaded.

 

I will fix both in my v2 ramdisk.

 

Beautiful. Thank you.

Share this post


Link to post
Share on other sites

Deprecated, see OP.

 

----------------------

Hi guys,

 

Here is my new v2 version with updated ramdisk.lzma:

 

 

When you will update ramdisk.lzma only, just backup your existing ramdisk.lzma (for sure) from image/DS3615xs/ on your usb boot drive and replace it with the ramdisk.lzma from archive.

 

Usage of these images is at your own risk. I don't recommend to use it on production environment without deeper testing.

 

Change log:

* Fixed loading modules after installation step and upgrading from previous ramdisk version

* Fixed order of loading kernel modules (cause not loading cnic)

 

--------------------------------------------------------------------------------

Recompiled kernel modules:

 

r8169: r8169-6.022.00 sources

* Note: Compiled by Trantor

 

igb: igb-5.3.5.4 sources

ixgbe: ixgbe-4.4.6 sources

* Note: Compiled from latest sources at intel.com

 

megaraid_sas: megaraid_sas-06.812.07.00 sources

mpt2sas: mpt2sas-20.00.04.00 sources

* Note: Compiled from latest sources at lsi.com/avagotech.com

 

--------------------------------------------------------------------------------

Added kernel modules:

 

mpt3sas: mpt3sas-14.00.00.00 sources

* Note: Compiled from latest sources at lsi.com/avagotech.com

 

ftdi_sio, cp210x, ch341, pl2303

* Note: ftdi_sio is compiled by Synology, others are compiled from 7274 kernel sources

 

My latest images are always placed here: https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w

 

Edit: Added AMD image, thanks to Jun.

Edited by Guest

Share this post


Link to post
Share on other sites
Hi guys,

 

Here is my new v2 version with updated ramdisk.lzma:

 

 

When you will update ramdisk.lzma only, just backup your existing ramdisk.lzma (for sure) from image/DS3615xs/ on your usb boot drive and replace it with the ramdisk.lzma from archive.

 

Change log:

* Fixed loading modules after installation step and upgrading from previous ramdisk version

* Fixed order of loading kernel modules (cause not loading cnic)

 

--------------------------------------------------------------------------------

Recompiled kernel modules:

 

r8169: r8169-6.022.00 sources

* Note: Compiled by Trantor

 

igb: igb-5.3.5.4 sources

ixgbe: ixgbe-4.4.6 sources

* Note: Compiled from latest sources at intel.com

 

megaraid_sas: megaraid_sas-06.812.07.00 sources

mpt2sas: mpt2sas-20.00.04.00 sources

* Note: Compiled from latest sources at lsi.com/avagotech.com

 

--------------------------------------------------------------------------------

Added kernel modules:

 

mpt3sas: mpt3sas-14.00.00.00 sources

* Note: Compiled from latest sources at lsi.com/avagotech.com

 

ftdi_sio, cp210x, ch341, pl2303

* Note: ftdi_sio is compiled by Synology, others are compiled from 7274 kernel sources

 

Thank you.

Share this post


Link to post
Share on other sites
Yeah, there is bug in loading kernel modules in Jun's modification. At first DISK_MODULES are loaded from ramdisk in /linuxrc.syno, that's ok. In /sbin/post.init are EXTRA_MODULES copied to hdd only when they are not exist and they are then loaded after chroot from hdd (in hdd's /etc.default/rc). So:

  • The installation step replace kernel modules (e.g. e1000e) with their version from pat file that cause not loading our updated kernel modules from ramdisk. Thus we have to replace these bad modules after reboot with version from ramdisk.
  • Also rc.modules file is not updated after first copy in the installation step. Thus when is updated from Jun's original ramdisk to my ramdisk v1, added kernel modules are not loaded. This explain why my network card didn't work with Trantor's r8169 module because the important r8168 wasn't loaded.

 

I will fix both in my v2 ramdisk.

I dont think this is a bug on my part, but your are welcome to make any change you see fit.

Share this post


Link to post
Share on other sites
Hi guys,

 

Here is my new v2 version with updated ramdisk.lzma:

 

 

When you will update ramdisk.lzma only, just backup your existing ramdisk.lzma (for sure) from image/DS3615xs/ on your usb boot drive and replace it with the ramdisk.lzma from archive.

 

Usage of these images is at your own risk. I don't recommend to use it on production environment without deeper testing.

 

Change log:

* Fixed loading modules after installation step and upgrading from previous ramdisk version

* Fixed order of loading kernel modules (cause not loading cnic)

 

--------------------------------------------------------------------------------

Recompiled kernel modules:

 

r8169: r8169-6.022.00 sources

* Note: Compiled by Trantor

 

igb: igb-5.3.5.4 sources

ixgbe: ixgbe-4.4.6 sources

* Note: Compiled from latest sources at intel.com

 

megaraid_sas: megaraid_sas-06.812.07.00 sources

mpt2sas: mpt2sas-20.00.04.00 sources

* Note: Compiled from latest sources at lsi.com/avagotech.com

 

--------------------------------------------------------------------------------

Added kernel modules:

 

mpt3sas: mpt3sas-14.00.00.00 sources

* Note: Compiled from latest sources at lsi.com/avagotech.com

 

ftdi_sio, cp210x, ch341, pl2303

* Note: ftdi_sio is compiled by Synology, others are compiled from 7274 kernel sources

 

My latest images are always placed here: https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w

Would I be right to assume that this still isn't compatible with the Gen7 HP Microserver as it is an AMD CPU not Intel?

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Supporting AMD CPUs require complete kernel recompilation. Kernel sources for DSM 6.0.2-8451 Update 2 are not available, only DSM 6 beta 7274. So no way at the moment. You can try to write Synology to release latest kernel sources as they have to by GPL license, but I think they will f*** you. :sad:

Edited by Guest

Share this post


Link to post
Share on other sites
Supporting AMD CPUs require complete kernel recompilation. Kernel sources for DSM 6.0.2-8451 Update 2 is not available, only DSM 6 beta 7274.

Thanks :smile: , that's what I suspected.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.