DSM 6.1.x Loader


Recommended Posts

Edit: p.s. I've tried both the UEFI image and the UEFI/BIOS image. My board is in true UEFI mode. Testing with a SSD attached to the intel controller. Disks attached to my 9211-i8 don't show up (at this stage?)

 

Most LSI cards will NOT work without a patched kernel. Until a patched kernel is produced, you'll have to wait.

 

 

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.

 

SAS2008 (Falcon) is the LSI 9211/IBM M1015.

Just because a module is added with support, does not make the Synology OEM kernel work. The kernel must be patched in order to make drives available for use.

 

Sent from my SM-N920T using Tapatalk

Link to post
Share on other sites

 

Arco, would you mind posting a full hybrid uefi/bios loader so we can use it as is instead of having to replace the ramdisk. That would be great if you could do that. Thanks.

 

OK, here are: :roll:

 

 

Edit:

Files moved to mega.nz from my webhosting...

 

Thank you Arcao. Greatly appreciated. I was going to do it myself but I though it would be better coming from you who already had repacked the ramdisk with all additional drivers. I will link your loader in the tutorial I made for the French section.

Edited by Guest
Link to post
Share on other sites
Hi,

 

I tried to install on bare-metal MSI N3150I ECO ITX board (celeron N3150), but installer always fails at 58% with error "Failed to install the file. The file is probably corrupted. (13)". On same setup i have installed latest 5.2 XPEnoboot without any problems. Any insights on this problem ?

 

maybe you did not change the vid/pid, so the installation process can not find the synoboot partitions.

 

I should make it clear that you need to change vid/pid BEFORE installation.

 

PS: DS716/916 should have better compatibility with your hardware, I'll release a DS916 version later when I can test it properly.

 

 

A newbie here, thanks Jun and thanks all of you pay effort that made this awesome things happened!!

 

I was wonder if there is any possible to port this loader for DS716 version?

 

Since I have a bare machine with N3150 chips, and would be so great if I can have hardware encoding option :smile:

Link to post
Share on other sites
Hi,

 

I tried to install on bare-metal MSI N3150I ECO ITX board (celeron N3150), but installer always fails at 58% with error "Failed to install the file. The file is probably corrupted. (13)". On same setup i have installed latest 5.2 XPEnoboot without any problems. Any insights on this problem ?

 

maybe you did not change the vid/pid, so the installation process can not find the synoboot partitions.

 

I should make it clear that you need to change vid/pid BEFORE installation.

 

PS: DS716/916 should have better compatibility with your hardware, I'll release a DS916 version later when I can test it properly.

 

 

A newbie here, thanks Jun and thanks all of you pay effort that made this awesome things happened!!

 

I was wonder if there is any possible to port this loader for DS716 version?

 

Since I have a bare machine with N3150 chips, and would be so great if I can have hardware encoding option :smile:

 

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

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.

 

 

Awesome work, Arcao! Would be better you can share how this is compiled and how this ramdisk is repacked, so more people with linux experience would help to test more drivers.

It would really perfect if you can help to compile and repack Hyper-V related drivers in ramdisk, something like in kernel configuration menu:

Device Drivers --> Network device support -->

Device Drivers --> Microsoft Hyper-V guest support -->

Device Drivers --> HID Support --> Special HID Drivers -->

A lot of people like me will be happy to test your work in Hyper-V. Thanks!

Link to post
Share on other sites

Hi viumden,

 

As I wrote earlier I use quicknick 3.10.77-7274 kernel source from https://github.com/quiknick/7274-kernel (newer is not available).

 

Compilation kernel modules is easy (I found it how to do it in http://setsunakawa.ddns.net/synology/dsm6/developer-guide.pdf):

cp synoconfigs/bromolow .config
make ARCH="x86_64" oldconfig
make ARCH="x86_64" menuconfig
make ARCH="x86_64" modules

 

To extract ramdisk.lzma I use this bash script:

#!/bin/bash
rm -r ramdisk
mkdir ramdisk
cd ramdisk
unlzma  -c ../ramdisk.lzma | cpio -im
cd ..

 

And for repack:

#!/bin/bash
cd ramdisk
find . | cpio -o -H newc | lzma > ../ramdisk_new.lzma
cd ..

 

Kernel modules are loaded in order as they are defined in /etc.defaults/rc.modules:

EXTRA_MODULES="mii mdio libphy usbnet atl1 atl1e atl1c alx cnic bnx2 bnx2x uio tg3 ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc igb ixgbe e1000 e1000e pcnet32 r8101 r8169 r8168 vmxnet3 ax88179_178a button evdev"
DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid megaraid_sas scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl mpt2sas"
EXTRA_FIRMWARES="bnx2/bnx2-mips-06-5.0.0.j3.fw bnx2/bnx2-mips-06-6.2.1.fw bnx2/bnx2-mips-06-6.2.3.fw bnx2/bnx2-mips-09-5.0.0.j3.fw bnx2/bnx2-mips-09-6.2.1a.fw bnx2/bnx2-mips-09-6.2.1b.fw bnx2/bnx2-rv2p-06-5.0.0.j3.fw bnx2/bnx2-rv2p-06-6.0.15.fw bnx2/bnx2-rv2p-09-5.0.0.j3.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw bnx2/bnx2-rv2p-09ax-6.0.17.fw tigon/tg357766.bin tigon/tg3.bin tigon/tg3_tso.bin tigon/tg3_tso5.bin bnx2x/bnx2x-e1-7.0.29.0.fw bnx2x/bnx2x-e1-7.8.17.0.fw bnx2x/bnx2x-e1-7.8.19.0.fw bnx2x/bnx2x-e1h-7.0.29.0.fw bnx2x/bnx2x-e1h-7.8.17.0.fw bnx2x/bnx2x-e1h-7.8.19.0.fw bnx2x/bnx2x-e2-7.0.29.0.fw bnx2x/bnx2x-e2-7.8.17.0.fw bnx2x/bnx2x-e2-7.8.19.0.fw bnx2x-e1-5.0.21.0.fw bnx2x-e1h-5.0.21.0.fw" 

 

DISK_MODULES are loaded in Jun's customized /linuxrc.syno (line 83):

. /etc.defaults/rc.modules
SYNOLoadModules $DISK_MODULES

 

And EXTRA_MODULES are added to KERNEL_MODULES with Jun's customized /etc.default/rc (line 166):

. /etc.defaults/rc.modules
KERNEL_MODULES="${KERNEL_MODULES} ${EXTRA_MODULES}"

 

Finally EXTRA_MODULES, DISK_MODULES and EXTRA_FIRMWARES are copied to hdd in Jun's customized /sbin/init.post.

 

For compiling modules from external sources i created symlink from kernel source root to /lib/modules/3.10.77/build. Then most of Makefiles will work without any change.

 

As a build machine I use my nas with installed debian-chroot package. There I just installed build-essential, ncurses-dev and bc packages:

sudo apt-get update
sudo apt-get install build-essential ncurses-dev bc

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.

Link to post
Share on other sites

Any help with this?

 

Thanks a lot!

 

Hi all!

 

Anybody can help me with this?

 

Scenario:

ESXi 6 on Gen8

DSM6 image from ESXi from first post

 

Ok, all is running properly, but when I add another net card, the system crash. BUT the first time when I added the net card all work properly, only get a kernel panic after change the IP of the second net card. I tried deleting and generating the ifcfg-eth* files of the path /etc/sysconfig/network-scripts/ and many other test, but the system only work again when I delete de second net card.

 

Here ir the output from the terminal, all the help are welcome and thank's all:

 

  Booting `Synology DS3615xs'

error: no suitable video mode found.
Booting in blind mode
early console in decompress_kernel

Decompressing Linux... Parsing ELF... done.
Booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.77 (root@build1) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #8451 SMP Wed Aug 17 05:12:41 CST 2016
[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt1)/grub/../image/DS3615xs/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=1 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 vid=0x0781 pid=0x5581 console=uart,io,0x3f8,115200n8 sn=C7LWN09761 mac1=0011322CA785 withefi elevator=your_magic_elevator quiet SataPortMap=4 synoboot_satadom=1 sata_uid=1 sata_pcislot=5
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000] Disabled fast string operations
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000000001000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fb25fff] usable
[    0.000000] BIOS-e820: [mem 0x000000003fb26000-0x000000003fb45fff] type 20
[    0.000000] BIOS-e820: [mem 0x000000003fb46000-0x000000003fb95fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000003fb96000-0x000000003fbb1fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000003fbb2000-0x000000003fbb5fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000003fbb6000-0x000000003fffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffc17fff] reserved
[    0.000000] Early serial console at I/O port 0x3f8 (options '115200n')
[    0.000000] bootconsole [uart0] enabled
START /linuxrc.syno
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module uhci-hcd ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module etxhci-hcd ... [  OK  ]
:: Loading module BusLogic ... [  OK  ]
:: Loading module vmw_pvscsi ... [  OK  ]
:: Loading module megaraid_mm ... [  OK  ]
:: Loading module megaraid_mbox ... [  OK  ]
:: Loading module megaraid ... [  OK  ]
:: Loading module megaraid_sas ... [  OK  ]
:: Loading module scsi_transport_spi ... [  OK  ]
:: Loading module mptbase ... [  OK  ]
:: Loading module mptscsih ... [  OK  ]
:: Loading module mptspi ... [  OK  ]
:: Loading module mptsas ... [  OK  ]
:: Loading module mptctl ... [  OK  ]
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
[    5.159217] md: invalid raid superblock magic on sde5
[    5.174367] md: invalid raid superblock magic on sdf5
[    5.190398] md: invalid raid superblock magic on sdg5
[    5.206278] md: invalid raid superblock magic on sdh5
                                                                                                                                                                                                                                                                                                                                       [    9.006325] md: invalid raid superblock magic on sdi3
                                                                                                                                                                                                                                                                                                                                       Partition Version=8
/sbin/e2fsck exists, checking /dev/md0...
1.42.6-5644: recovering journal






      29742 inodes used (19.11%, out of 155648)
         98 non-contiguous files (0.3%)
         12 non-contiguous directories (0.0%)
            # of inodes with ind/dind/tind blocks: 0/0/0
            Extent depth histogram: 26978/41
     259577 blocks used (41.70%, out of 622544)
          0 bad blocks
          1 large file

      23596 regular files
       3094 directories
          2 character device files
          0 block device files
          0 fifos
       1315 links
       3041 symbolic links (2713 fast symbolic links)
          0 sockets
------------
      31048 files
/sbin/e2fsck returns 1
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
No upgrade file exists
End upgrade procedure
============upgrade
Wait 2 seconds for synology manufactory device
Thr Oct 13 21:27:12 UTC 2016
/dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
none /dev devtmpfs rw,relatime,size=506736k,nr_inodes=126684,mode=755 0 0
proc /proc proc rw,relatime 0 0
linuxrc.syno executed successfully.
Post init
==================== start udevd ====================
===== trigger device plug event =====
[  190.859178] ------------[ cut here ]------------
[  190.859954] kernel BUG at /linux/synology/linux-stable/drivers/net/vmxnet3/vmxnet3_drv.c:1314!
[  190.861274] invalid opcode: 0000 [#1] SMP
[  190.861954] Modules linked in: bromolow_synobios(PO) adt7475 i2c_i801 vmxnet3 r8169 pcnet32 e1000 sfc netxen_nic qlge qlcnic qla3xxx pch_gbe ptp_pch sky2 skge jme ipg tg3 cnic uio bnx2 alx atl1c atl1e atl1 libphy mii btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit e1000e(O) dca fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg mptctl mptsas mptspi mptscsih mptbase scsi_transport_spi megaraid_sas megaraid megaraid_mbox megaraid_mm vmw_pvscsi BusLogic etxhci_hcd xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common el000(O) [last unloaded: i2c_i801]
[  190.879265] CPU: 1 PID: 9498 Comm: avahi-daemon Tainted: P         C O 3.10.77 #8451
[  190.880496] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.0.B64.1506250318 06/25/2015
[  190.882314] task: ffff88003f1b40c0 ti: ffff88003e954000 task.ti: ffff88003e954000
[  190.883530] RIP: 0010:[]  [] vmxnet3_rq_rx_complete+0x500/0x870 [vmxnet3]
[  190.885112] RSP: 0000:ffff88003d283e30  EFLAGS: 00010246
[  190.885964] RAX: 0000000000000000 RBX: ffff8800370b72c0 RCX: ffff880031db4010
[  190.887099] RDX: 0000000000000120 RSI: 0000000000000002 RDI: 000000000000011e
[  190.888218] RBP: ffff8800370b72c0 R08: 0000000000000000 R09: 0000000000000001
[  190.889350] R10: ffff8800370b6700 R11: 0000000000000040 R12: ffff880031dbc000
[  190.890472] R13: ffff880031e89180 R14: ffff880031c04000 R15: 0000000000000000
[  190.891588] FS:  00007fd40bb8c700(0000) GS:ffff88003d280000(0000) knlGS:0000000000000000
[  190.892851] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  190.893758] CR2: 0000000000648048 CR3: 000000003f198000 CR4: 00000000001407e0
[  190.894888] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  190.896029] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  190.897184] Stack:
[  190.897526]  000088003ac48bc0 0000004000000000 ffff8800370b72e0 ffff8800370b6700
[  190.898784]  ffff8800370b6700 ffff8800370b6700 ffff8800370b72e0 0000000000000040
[  190.900056]  ffff8800370b72c0 00000000fffe545a ffff88003d2910d0 ffffffffa096abb0
[  190.901346] Call Trace:
[  190.901746]  
[  190.902066]  [] ? vmxnet3_poll_rx_only+0x30/0xa0 [vmxnet3]
[  190.903237]  [] ? __netif_receive_skb_core+0x422/0x5e0
[  190.904277]  [] ? net_rx_action+0xf9/0x160
[  190.905164]  [] ? __do_softirq+0xc6/0x1a0
[  190.906061]  [] ? call_softirq+0x1c/0x30
[  190.906934]  [] ? do_softirq+0x35/0x70
[  190.907772]  [] ? irq_exit+0x95/0xa0
[  190.908562]  [] ? do_IRQ+0x49/0xb0
[  190.909336]  [] ? common_interrupt+0x6a/0x6a
[  190.910227]  
[  190.910562]  [] ? system_call_fastpath+0x16/0x1b
[  190.911542] Code: 00 00 48 8b 7c 24 10 4c 89 ee e8 fc e6 a7 e0 4c 8b 54 24 18 48 c7 85 d0 00 00 00 00 00 00 00 45 31 c0 e9 2d fc ff ff 0f 1f 40 00 <0f> 0b 66 0f 1f 44 00 00 0f 0b 66 0f 1f 44 00 00 3b 85 e4 00 00
[  190.915894] RIP  [] vmxnet3_rq_rx_complete+0x500/0x870 [vmxnet3]
[  190.917097]  RSP 
[  190.917658] ---[ end trace 87837954e5d25554 ]---
[  190.918342] Kernel panic - not syncing: Fatal exception in interrupt
[  190.919399] Rebooting in 3 seconds..

Link to post
Share on other sites

Dear all, I tried to read as much as I can from this thread! :smile:

I'm going to upgrade my bare metal nas with Q1900-itx, I hope everything will be fine but I'm doing a an external backup for sure.

 

I didn't understand if I need the .pat file as per the previous release or it will download automatically when I choose to install or upgrade?

 

Thanks

Link to post
Share on other sites
Hi viumden,

 

As I wrote earlier I use quicknick 3.10.77-7274 kernel source from https://github.com/quiknick/7274-kernel (newer is not available).

 

Compilation kernel modules is easy (I found it how to do it in http://setsunakawa.ddns.net/synology/dsm6/developer-guide.pdf):

cp synoconfigs/bromolow .config
make ARCH="x86_64" oldconfig
make ARCH="x86_64" menuconfig
make ARCH="x86_64" modules

 

To extract ramdisk.lzma I use this bash script:

#!/bin/bash
rm -r ramdisk
mkdir ramdisk
cd ramdisk
unlzma  -c ../ramdisk.lzma | cpio -im
cd ..

 

And for repack:

#!/bin/bash
cd ramdisk
find . | cpio -o -H newc | lzma > ../ramdisk_new.lzma
cd ..

 

Kernel modules are loaded in order as they are defined in /etc.defaults/rc.modules:

EXTRA_MODULES="mii mdio libphy usbnet atl1 atl1e atl1c alx cnic bnx2 bnx2x uio tg3 ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc igb ixgbe e1000 e1000e pcnet32 r8101 r8169 r8168 vmxnet3 ax88179_178a button evdev"
DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid megaraid_sas scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl mpt2sas"
EXTRA_FIRMWARES="bnx2/bnx2-mips-06-5.0.0.j3.fw bnx2/bnx2-mips-06-6.2.1.fw bnx2/bnx2-mips-06-6.2.3.fw bnx2/bnx2-mips-09-5.0.0.j3.fw bnx2/bnx2-mips-09-6.2.1a.fw bnx2/bnx2-mips-09-6.2.1b.fw bnx2/bnx2-rv2p-06-5.0.0.j3.fw bnx2/bnx2-rv2p-06-6.0.15.fw bnx2/bnx2-rv2p-09-5.0.0.j3.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw bnx2/bnx2-rv2p-09ax-6.0.17.fw tigon/tg357766.bin tigon/tg3.bin tigon/tg3_tso.bin tigon/tg3_tso5.bin bnx2x/bnx2x-e1-7.0.29.0.fw bnx2x/bnx2x-e1-7.8.17.0.fw bnx2x/bnx2x-e1-7.8.19.0.fw bnx2x/bnx2x-e1h-7.0.29.0.fw bnx2x/bnx2x-e1h-7.8.17.0.fw bnx2x/bnx2x-e1h-7.8.19.0.fw bnx2x/bnx2x-e2-7.0.29.0.fw bnx2x/bnx2x-e2-7.8.17.0.fw bnx2x/bnx2x-e2-7.8.19.0.fw bnx2x-e1-5.0.21.0.fw bnx2x-e1h-5.0.21.0.fw" 

 

DISK_MODULES are loaded in Jun's customized /linuxrc.syno (line 83):

. /etc.defaults/rc.modules
SYNOLoadModules $DISK_MODULES

 

And EXTRA_MODULES are added to KERNEL_MODULES with Jun's customized /etc.default/rc (line 166):

. /etc.defaults/rc.modules
KERNEL_MODULES="${KERNEL_MODULES} ${EXTRA_MODULES}"

 

Finally EXTRA_MODULES, DISK_MODULES and EXTRA_FIRMWARES are copied to hdd in Jun's customized /sbin/init.post.

 

For compiling modules from external sources i created symlink from kernel source root to /lib/modules/3.10.77/build. Then most of Makefiles will work without any change.

 

As a build machine I use my nas with installed debian-chroot package. There I just installed build-essential, ncurses-dev and bc packages:

sudo apt-get update
sudo apt-get install build-essential ncurses-dev bc

 

Really thanks for the detailed instructions!

I tried to download the source code and compile hyper-v related kernel modules, and managed to get the hv_balloon.ko, hv_utils.ko, hv_vmbus.ko, hv_netvsc.ko, hv_storvsc.ko and hyperv_fb.ko available, then modified /etc.defaults/rc.modules like below:

EXTRA_MODULES="hyperv_fb mii mdio libphy usbnet atl1 atl1e atl1c alx cnic bnx2 bnx2x uio tg3 ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc igb ixgbe e1000 e1000e hv_utils hv_balloon hv_netvsc pcnet32 r8101 r8169 r8168 vmxnet3 ax88179_178a button evdev"
DISK_MODULES="BusLogic hv_vmbus hv_storvsc vmw_pvscsi megaraid_mm megaraid_mbox megaraid megaraid_sas scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl mpt2sas"
EXTRA_FIRMWARES="bnx2/bnx2-mips-06-5.0.0.j3.fw bnx2/bnx2-mips-06-6.2.1.fw bnx2/bnx2-mips-06-6.2.3.fw bnx2/bnx2-mips-09-5.0.0.j3.fw bnx2/bnx2-mips-09-6.2.1a.fw bnx2/bnx2-mips-09-6.2.1b.fw bnx2/bnx2-rv2p-06-5.0.0.j3.fw bnx2/bnx2-rv2p-06-6.0.15.fw bnx2/bnx2-rv2p-09-5.0.0.j3.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw bnx2/bnx2-rv2p-09ax-6.0.17.fw tigon/tg357766.bin tigon/tg3.bin tigon/tg3_tso.bin tigon/tg3_tso5.bin bnx2x/bnx2x-e1-7.0.29.0.fw bnx2x/bnx2x-e1-7.8.17.0.fw bnx2x/bnx2x-e1-7.8.19.0.fw bnx2x/bnx2x-e1h-7.0.29.0.fw bnx2x/bnx2x-e1h-7.8.17.0.fw bnx2x/bnx2x-e1h-7.8.19.0.fw bnx2x/bnx2x-e2-7.0.29.0.fw bnx2x/bnx2x-e2-7.8.17.0.fw bnx2x/bnx2x-e2-7.8.19.0.fw bnx2x-e1-5.0.21.0.fw bnx2x-e1h-5.0.21.0.fw"

Then repack the ramdisk, make it into bootable ISO (isolinux), the ramdisk loads successfully in hyper-v:

Loading ../zImage... ok
Loading ../ramdisk_new.lzma... ok
early console in decompressing_kernel

Decompressing Linux... Parsing ELF... done.
Booting the kernel.

Then nothing happened, I still cannot see the DSM IP available in my router DHCP lease list, seems network is still not up properly, not sure whether there are other things to be done to make everything work in Hyper-V. It seems further work in kernel patching/configuration is needed to hyper-v work? Whether there are still Xpenology developer to share what has been done in the official release which makes hyper-v work like a charm?

Link to post
Share on other sites

my dsm is stuck in loopback. can i use a old bootloader instead of this?. i always change the mac and sn but this for some reason wont let me login as root nothing plugged in no disks it still is stuck in loopback and i cannot login as root to do ifconfig or see what the hell is going on. :sad: this really sucks i also caught a few glimpses of megaraid sas [failed] when loading files. maybe the file i got was bad? i downloaded it from the xpenology.xyz domain. does anyone else have a working bootloader they can upload?

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.

 

Unfortunately Synology kernel doesn't have support for textmode graphic output, debugging over com port is only supported. Could you tell me your HW?

Link to post
Share on other sites
Nice job Arcao, works even fine for me and my GA-170N-WIFI Board without a serial port. But I can only use one port, can you bring in the Intel i219 Ethernet port driver. This would be nice. After that, I can go to production system with DSM 6 :grin:

 

The source code used in this this loader came from DSM6 beta2. I wouldn't trust my "production" data on a beta source code.

Link to post
Share on other sites
got it, big thanks guys!

 

PS: interesting, why did they removed it?

 

Someone on the forum (probably in this thread) mentioned an expansion limit exists using SHR and that's why it's being phased out of the high end devices. Seems a bit daft to me because there will be lots of users who will never reach the limit and SHR would be far more useful. Besides if Synology are concerned about the limit all they needed to do was to put a warning comment next to the option, and then the user could decide which is best for them based on their real world use case. It's a big and unique selling point they're giving up on those devices for no good reason imho.

Edited by Guest
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.

 

Unfortunately Synology kernel doesn't have support for textmode graphic output, debugging over com port is only supported. Could you tell me your HW?

 

 

howdy! im running a hp ex490. its got an intel q8500 cpu with 2GB of ddr2 doesn't have graphics but i have a ttl cable which i can see bios and everything else. intel nic i believe. this server works fine with 5597 bootloader, do you know if is there anything different?. I noticed this is a efi bootloader and the other is not. But the furthest I got was booting kernel using hybrid, the other img file would not let me view the usb key its as if it does not get assigned a drive letter although the contents are on the usb key in directories and the utility i use is not letting me edit the file on the non hybrid version of the img file. :-| I was hoping maybe that one would work but Im out of usb keys at the moment to test.

Edited by Guest
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?

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.