CrazyCreator Posted March 21, 2017 Share #1 Posted March 21, 2017 Hello all, I think it's better if we open an extra thread, for Jun's v1.02a/v1.02a2 Loader. The loader can be downloaded here: https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!5kcjyJ7R I do not know if the developer likes it, but I think it is important for all testers to know what is currently not working and of course what works. ################################################################################################## I have currently the DS3615xs in use, on a HP ProLiant Microserver Gen8 ... Without problems. The DS3617xs works without Problems too, but the DS916 is not functional (in my case) ... I see the Grub Bootloader and can select a entry. But no matter what entry I choose I get no connection via webbrowser and see in my router also no IP address which would be assigned to the HP ProLiant. ########################### Update from 01.05.2017 ################################################# On 5/1/2017 at 9:03 PM, Polanskiman said: I have compiled a few more network modules and firmwares. This is for loader v1.02a (3615xs only) (see below for details). Compilation was done with DSM 6.1 source code and tool chain. Simply replace the default extra.lzma ramdisk in the loader with this one. I left all modules that were compiled by Jun as is. I am not sure if all the modules that I compiled are working fine since I do not have the corresponding hardware. Give it a shot. 3c59x.ko (3Com 3c59x/3c9xx ethernet driver) 8139cp.ko (RealTek RTL-8139C+ series 10/100 PCI Ethernet driver) 8139too.ko (RealTek RTL-8139 Fast Ethernet driver) e100.ko (Intel(R) PRO/100 Network Driver) forcedeth.ko (Nvidia nForce Ethernet) r6040.ko (RDC R6040 NAPI PCI FastEthernet driver) typhoon.ko (3Com Typhoon Family - 3C990, 3CR990, and variants) via-rhine.ko (VIA Rhine PCI Fast Ethernet driver) w5100.ko (WIZnet W5100 Ethernet driver) w5300.ko (WIZnet W5300 Ethernet driver ) /bnx2/bnx2-mips-09-6.2.1a.fw /bnx2/bnx2-mips-06-6.2.1.fw /e100/d101m_ucode.bin /e100/d101s_ucode.bin /e100/d102e_ucode.bin /3com/typhoon.bin In fact I did compile a few others but I am getting some unknown symbols and I do not have time to debug. In case some might want to look into it here is the list of modules which failed to compile properly and the dmesg log: Failed modules 3c574_cs.ko 3c589_cs.ko acenic.ko at91_ether.ko atl2.ko b44.ko bna.ko cxgb.ko cxgb3.ko cxgb4.ko cxgb4vf.ko ixgb.ko macb.ko mvmdio.ko sis190.ko sis900.ko xgmac.ko Hide dmesg log [ 34.447355] 3c574_cs: Unknown symbol pcmcia_disable_device (err 0) [ 34.447369] 3c574_cs: Unknown symbol pcmcia_unregister_driver (err 0) [ 34.447394] 3c574_cs: Unknown symbol pcmcia_request_io (err 0) [ 34.447403] 3c574_cs: Unknown symbol pcmcia_get_tuple (err 0) [ 34.447412] 3c574_cs: Unknown symbol pcmcia_register_driver (err 0) [ 34.447421] 3c574_cs: Unknown symbol pcmcia_enable_device (err 0) [ 34.447430] 3c574_cs: Unknown symbol pcmcia_request_irq (err 0) [ 34.447438] 3c574_cs: Unknown symbol pcmcia_dev_present (err 0) [ 34.450980] 3c589_cs: Unknown symbol pcmcia_disable_device (err 0) [ 34.450994] 3c589_cs: Unknown symbol pcmcia_unregister_driver (err 0) [ 34.451012] 3c589_cs: Unknown symbol pcmcia_request_io (err 0) [ 34.451020] 3c589_cs: Unknown symbol pcmcia_get_tuple (err 0) [ 34.451028] 3c589_cs: Unknown symbol pcmcia_register_driver (err 0) [ 34.451036] 3c589_cs: Unknown symbol pcmcia_enable_device (err 0) [ 34.451044] 3c589_cs: Unknown symbol pcmcia_request_irq (err 0) [ 34.451052] 3c589_cs: Unknown symbol pcmcia_dev_present (err 0) [ 34.463293] acenic: Unknown symbol kmalloc_order_trace (err 0) [ 34.466522] at91_ether: Unknown symbol macb_set_hwaddr (err 0) [ 34.466595] at91_ether: Unknown symbol macb_mii_init (err 0) [ 34.466606] at91_ether: Unknown symbol macb_ethtool_ops (err 0) [ 34.466620] at91_ether: Unknown symbol macb_ioctl (err 0) [ 34.466629] at91_ether: Unknown symbol macb_set_rx_mode (err 0) [ 34.466639] at91_ether: Unknown symbol macb_get_hwaddr (err 0) [ 34.466647] at91_ether: Unknown symbol macb_get_stats (err 0) [ 34.470514] atl2: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.476136] b44: Unknown symbol ssb_device_is_enabled (err 0) [ 34.476148] b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable (err 0) [ 34.476158] b44: Unknown symbol ssb_bus_may_powerdown (err 0) [ 34.476175] b44: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.476185] b44: Unknown symbol ssb_pcihost_register (err 0) [ 34.476194] b44: Unknown symbol ssb_device_disable (err 0) [ 34.476208] b44: Unknown symbol ssb_device_enable (err 0) [ 34.476219] b44: Unknown symbol ssb_driver_unregister (err 0) [ 34.476231] b44: Unknown symbol __ssb_driver_register (err 0) [ 34.476241] b44: Unknown symbol ssb_bus_powerup (err 0) [ 34.476256] b44: Unknown symbol ssb_clockspeed (err 0) [ 34.476265] b44: Unknown symbol ssb_dma_translation (err 0) [ 34.482344] bna: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.482393] bna: Unknown symbol alloc_pages_current (err 0) [ 34.485495] cxgb: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.488837] cxgb3: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.488858] cxgb3: Unknown symbol kmalloc_order_trace (err 0) [ 34.488926] cxgb3: Unknown symbol alloc_pages_current (err 0) [ 34.492549] cxgb4: Unknown symbol __kmalloc_node (err 0) [ 34.492642] cxgb4: Unknown symbol kmalloc_order_trace (err 0) [ 34.492658] cxgb4: Unknown symbol numa_node (err 0) [ 34.492701] cxgb4: Unknown symbol node_data (err 0) [ 34.492718] cxgb4: Unknown symbol alloc_pages_current (err 0) [ 34.496453] cxgb4vf: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.496470] cxgb4vf: Unknown symbol numa_node (err 0) [ 34.496500] cxgb4vf: Unknown symbol node_data (err 0) [ 34.496517] cxgb4vf: Unknown symbol alloc_pages_current (err 0) [ 34.511972] ixgb: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.516467] macb: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.520072] mvmdio: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.527891] sis190: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.532269] sis900: Unknown symbol kmem_cache_alloc_trace (err 0) [ 34.551610] xgmac: Unknown symbol kmem_cache_alloc_trace (err 0) Hide Link to comment Share on other sites More sharing options...
CrazyCreator Posted March 21, 2017 Author Share #2 Posted March 21, 2017 Has anyone brought the DS916p to run? Link to comment Share on other sites More sharing options...
raceboy Posted March 22, 2017 Share #3 Posted March 22, 2017 ...whats the difference between ...15xs, ...17xs, and 916? Link to comment Share on other sites More sharing options...
CrazyCreator Posted March 22, 2017 Author Share #4 Posted March 22, 2017 I know the 916p support SHR ... but the difference between DS3615xs and DS3617xs I don't know. In real we can find on Synology page, but in the loader? Link to comment Share on other sites More sharing options...
sze Posted March 22, 2017 Share #5 Posted March 22, 2017 Read somewhere here that 17xs works a little bit better with xeon, but don't find the post again. Link to comment Share on other sites More sharing options...
raceboy Posted March 22, 2017 Share #6 Posted March 22, 2017 ...i have jun 1.02a bootloader on ESXi 6 and HP Microserver gen8 both with dsm 6.1 (DS3615xs). on both works BTRFS and both works great. Link to comment Share on other sites More sharing options...
Sonnyboy666 Posted March 22, 2017 Share #7 Posted March 22, 2017 Running DSM 6.1 Update 1 on a HP ProLiant MicroServer Gen8, baremetal Installation, using Juns Loader 1.02a DS3615xs. Its running for a few weeks without any problems. I have three 3GB HDDs installed with ext4 running SHR. I have updated from DSM 5.2 To 6.0 And then To 6.1. The SHR group is working since 5.2. I think i have to do a clean install To use RAID and btfrs. Link to comment Share on other sites More sharing options...
CrazyCreator Posted March 22, 2017 Author Share #8 Posted March 22, 2017 Running DSM 6.1 Update 1 on a HP ProLiant MicroServer Gen8, baremetal Installation, using Juns Loader 1.02a DS3615xs.Its running for a few weeks without any problems. I have three 3GB HDDs installed with ext4 running SHR. I have updated from DSM 5.2 To 6.0 And then To 6.1. The SHR group is working since 5.2. I think i have to do a clean install To use RAID and btfrs. But with a new clean install you can't use SHR again. Only the DS916p (from the 3 Loaders I mean) support this. Link to comment Share on other sites More sharing options...
463nt0ran63 Posted March 22, 2017 Share #9 Posted March 22, 2017 ...i have jun 1.02a bootloader on ESXi 6 and HP Microserver gen8 both with dsm 6.1 (DS3615xs). on both works BTRFS and both works great. Did you do a fresh install or migration? If last I would be interested in how you did it Gesendet von meinem ONE A2003 mit Tapatalk Link to comment Share on other sites More sharing options...
raceboy Posted March 23, 2017 Share #10 Posted March 23, 2017 ...i have jun 1.02a bootloader on ESXi 6 and HP Microserver gen8 both with dsm 6.1 (DS3615xs). on both works BTRFS and both works great. Did you do a fresh install or migration? If last I would be interested in how you did it Gesendet von meinem ONE A2003 mit Tapatalk ...i did fresh. I have to re-format hdd's for btrfs support. Only in HP Proliant i have to put manual ip configuration. DHCP don't work so good. Link to comment Share on other sites More sharing options...
463nt0ran63 Posted March 23, 2017 Share #11 Posted March 23, 2017 ...i have jun 1.02a bootloader on ESXi 6 and HP Microserver gen8 both with dsm 6.1 (DS3615xs). on both works BTRFS and both works great. Did you do a fresh install or migration? If last I would be interested in how you did it Gesendet von meinem ONE A2003 mit Tapatalk ...i did fresh. I have to re-format hdd's for btrfs support. Only in HP Proliant i have to put manual ip configuration. DHCP don't work so good. Damn still searching for somebody who managed to get a migration done on esxi 6.5 Gesendet von meinem ONE A2003 mit Tapatalk Link to comment Share on other sites More sharing options...
colrojo Posted March 23, 2017 Share #12 Posted March 23, 2017 Running DSM 6.1 Update 1 on a HP ProLiant MicroServer Gen8, baremetal Installation, using Juns Loader 1.02a DS3615xs.Its running for a few weeks without any problems. I have three 3GB HDDs installed with ext4 running SHR. I have updated from DSM 5.2 To 6.0 And then To 6.1. The SHR group is working since 5.2. I think i have to do a clean install To use RAID and btfrs. But with a new clean install you can't use SHR again. Only the DS916p (from the 3 Loaders I mean) support this. Also in the 916 the CPU arquitecture is brasswell. Ideal for 3050 , 3060.... But i tried it on asrock n3150-itx And can't run. I think for the network chip. (rtl8111gr) Link to comment Share on other sites More sharing options...
463nt0ran63 Posted March 23, 2017 Share #13 Posted March 23, 2017 ...i have jun 1.02a bootloader on ESXi 6 and HP Microserver gen8 both with dsm 6.1 (DS3615xs). on both works BTRFS and both works great. Did you do a fresh install or migration? If last I would be interested in how you did it Gesendet von meinem ONE A2003 mit Tapatalk ...i did fresh. I have to re-format hdd's for btrfs support. Only in HP Proliant i have to put manual ip configuration. DHCP don't work so good. Could one readd the drives after a fresh install? What would happen? Loss of data? Gesendet von meinem ONE A2003 mit Tapatalk Link to comment Share on other sites More sharing options...
Sonnyboy666 Posted March 23, 2017 Share #14 Posted March 23, 2017 Running DSM 6.1 Update 1 on a HP ProLiant MicroServer Gen8, baremetal Installation, using Juns Loader 1.02a DS3615xs.Its running for a few weeks without any problems. I have three 3GB HDDs installed with ext4 running SHR. I have updated from DSM 5.2 To 6.0 And then To 6.1. The SHR group is working since 5.2. I think i have to do a clean install To use RAID and btfrs. But with a new clean install you can't use SHR again. Only the DS916p (from the 3 Loaders I mean) support this. Yes, but is SHR so much better then a "normal" Raid? Link to comment Share on other sites More sharing options...
CrazyCreator Posted March 23, 2017 Author Share #15 Posted March 23, 2017 Better? I don't know ... But you have in many cases more space ^^ Link to comment Share on other sites More sharing options...
Aigor Posted March 23, 2017 Share #16 Posted March 23, 2017 Off Topic Hi, are you the same CrazyCreator on Insanelymac? Link to comment Share on other sites More sharing options...
fonix232 Posted March 23, 2017 Share #17 Posted March 23, 2017 Running DSM 6.1 Update 1 on a HP ProLiant MicroServer Gen8, baremetal Installation, using Juns Loader 1.02a DS3615xs.Its running for a few weeks without any problems. I have three 3GB HDDs installed with ext4 running SHR. I have updated from DSM 5.2 To 6.0 And then To 6.1. The SHR group is working since 5.2. I think i have to do a clean install To use RAID and btfrs. But with a new clean install you can't use SHR again. Only the DS916p (from the 3 Loaders I mean) support this. Also in the 916 the CPU arquitecture is brasswell. Ideal for 3050 , 3060.... But i tried it on asrock n3150-itx And can't run. I think for the network chip. (rtl8111gr) It does not matter. The thing is, all loaders use a single kernel version (I think either Avoton or x64, on 5.2 I remember most devs used Bromolow), with multi-platform support enabled. Unless Synology made optimizations in HAL, I doubt there's an actual difference between loader builds (apart from the indicated CPU string). Link to comment Share on other sites More sharing options...
lewis666 Posted March 23, 2017 Share #18 Posted March 23, 2017 Running DSM 6.1 Update 1 on a HP ProLiant MicroServer Gen8, baremetal Installation, using Juns Loader 1.02a DS3615xs.Its running for a few weeks without any problems. I have three 3GB HDDs installed with ext4 running SHR. I have updated from DSM 5.2 To 6.0 And then To 6.1. The SHR group is working since 5.2. I think i have to do a clean install To use RAID and btfrs. But with a new clean install you can't use SHR again. Only the DS916p (from the 3 Loaders I mean) support this. Yes, but is SHR so much better then a "normal" Raid? Hi Sonnyboy666, to get SHR again on DSM 6.1 you need to modify the Syno's config : - edit synoinfo.conf located in /etc.defaults/synoinfo. conf - comment out / delete - support raid group = "yes" - then add - support_syno_hybrid_raid = "yes" reboot your NAS and create your volume with the SHR option. regardless lewis666 Link to comment Share on other sites More sharing options...
lewis666 Posted March 23, 2017 Share #19 Posted March 23, 2017 Running DSM 6.1 Update 1 on a HP ProLiant MicroServer Gen8, baremetal Installation, using Juns Loader 1.02a DS3615xs.Its running for a few weeks without any problems. I have three 3GB HDDs installed with ext4 running SHR. I have updated from DSM 5.2 To 6.0 And then To 6.1. The SHR group is working since 5.2. I think i have to do a clean install To use RAID and btfrs. But with a new clean install you can't use SHR again. Only the DS916p (from the 3 Loaders I mean) support this. Yes, but is SHR so much better then a "normal" Raid? Hi Sonnyboy666, to get SHR again on DSM 6.1 you need to modify the Syno's config : - edit synoinfo.conf located in /etc.defaults/synoinfo. conf - comment out / delete - support raid group = "yes" - then add - support_syno_hybrid_raid = "yes" reboot your NAS and create your volume with the SHR option. regardless lewis666 Link to comment Share on other sites More sharing options...
chrisund123 Posted March 23, 2017 Share #20 Posted March 23, 2017 I upgraded to 6.1 on Jun's alpha loader. I'm on a bare metal hp ML10 gen 9. Haven't found any problems with it. Link to comment Share on other sites More sharing options...
CrazyCreator Posted March 23, 2017 Author Share #21 Posted March 23, 2017 to get SHR again on DSM 6.1 you need to modify the Syno's config : - edit synoinfo.conf located in /etc.defaults/synoinfo. conf - comment out / delete - support raid group = "yes" - then add - support_syno_hybrid_raid = "yes" reboot your NAS and create your volume with the SHR option. regardless lewis666 If I try, then I get after the restart no IP address more. Link to comment Share on other sites More sharing options...
Salah Posted March 23, 2017 Share #22 Posted March 23, 2017 I am not seeing any issues with the x15 Alpha loader so far on my beta box(old dell 1u). I did do bare metal install. What seems to be the issue with what settings/hardware? Link to comment Share on other sites More sharing options...
wer Posted March 24, 2017 Share #23 Posted March 24, 2017 (edited) Thank you for the loader. Works fine so far with a MSI B150M ECO. Just tried it with a new Seagate IronWolf. New diagnostic tab appears in DSM 6.1, nice! As I need an additional DVB driver I also compiled new modules for supporting power button shutdown. Want to share it: [deleted] I made a new package. See: http://xpenology.com/forum/viewtopic.php?f=2&t=32773 Edited April 27, 2017 by Guest Link to comment Share on other sites More sharing options...
whatisk Posted March 24, 2017 Share #24 Posted March 24, 2017 Tried Jun's Mod V1.02 Alpha on N40L (AMD). Guessing it doesn't work as no AMD option in boot menu. Tried 'regular' option but Synology Assistant never found the unit. Link to comment Share on other sites More sharing options...
Sonnyboy666 Posted March 24, 2017 Share #25 Posted March 24, 2017 Upgraded this morning To DSM 6.1-15047 Update 2. (Yes, i am brave;-) Everything seems To work till now. Link to comment Share on other sites More sharing options...
Recommended Posts