Salah Posted April 29, 2017 Share #2701 Posted April 29, 2017 3617xs works fine for me. Please elaborate Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted April 29, 2017 Share #2702 Posted April 29, 2017 3617xs works fine for me. Please elaborate Nothing much to elaborate. Most people using v1.02a2 are able to run dsm 6.1 with 3617xs. There is nothing wrong with the patch. Quote Link to comment Share on other sites More sharing options...
mouse Posted April 29, 2017 Share #2703 Posted April 29, 2017 3617xs works fine for me. Please elaborate Nothing much to elaborate. Most people using v1.02a2 are able to run dsm 6.1 with 3617xs. There is nothing wrong with the patch. Agree working like a charm into a esxi 6.5 I previously cannot find it cause I've to plug the correct Ethernet cable[emoji1] Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted April 29, 2017 Share #2704 Posted April 29, 2017 Was that for 3617 1.02a2 or 3615 .2a?1.02a2 3617 the nic's are up and running. find syno worked initially. Loading DSM not so much. Looking at logs to see whats up when I have time. Yes that was for v1.02a2. The model (3615 or 3617) is irrelevant. In retrospect I just realised I made an erroneous statement. The version IS actually relevant since both models have different architectures. DS3615xs is bromolow based while DS3617xs is broadwell based. Sorry about that. Quote Link to comment Share on other sites More sharing options...
trublu Posted April 29, 2017 Share #2705 Posted April 29, 2017 Please send logs when all above is corrected. I put logs up but gave up on v1.02a2 ds3617xs. I dont think juns patch for it is working just yet. Rolled back to 1.02a ds3615xs with injected broadcom 3617xs works fine for me. What DSM version? Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted April 30, 2017 Share #2706 Posted April 30, 2017 I put logs up but gave up on v1.02a2 ds3617xs. I dont think juns patch for it is working just yet. Rolled back to 1.02a ds3615xs with injected broadcom 3617xs works fine for me. What DSM version? A quick search would have answered that question; DSM 6.1 Quote Link to comment Share on other sites More sharing options...
dedligamer Posted April 30, 2017 Share #2707 Posted April 30, 2017 Hi, installation from DSM 5.2 to 6.1 (using Jun Loader v1.02a2) went fine with my setup (see signature). I have one problem, everytime I boot my NAS, the CMOS Date is not valid anymore, so I have to change it in BIOS or skip it by pressing F1. Is there a workaround to cover this little bug? Thanks. Quote Link to comment Share on other sites More sharing options...
sze Posted April 30, 2017 Share #2708 Posted April 30, 2017 Yes, change your mainboard battery. Thats typical for an empty one. Quote Link to comment Share on other sites More sharing options...
JMG1 Posted April 30, 2017 Share #2709 Posted April 30, 2017 If you are on v1.01, replace the extra.lzma with this one https://mega.nz/#!KUxmhY7R!FYOSzesxdUjPlynO4YDvSu4LKfFkFk9eBvkUD9AGS04. I included the forcedeth module. Let me know if it works. I repeat. This is only for v1.01 NOT v.1.02a. Hoooo ... thanks I work on my computer. But only for version 6.0. It is not possible for version 6.1 ???, with this system or another, in my system extra.lzma is necessary. Thank you. Quote Link to comment Share on other sites More sharing options...
Qoo Posted April 30, 2017 Share #2710 Posted April 30, 2017 DSM 6.1-15047 Update 2 with Jun Loader v1.02a2 is working fine on Baremetal Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 30, 2017 Share #2711 Posted April 30, 2017 DSM 6.1-15047 Update 2 with Jun Loader v1.02a2 is working fine on Baremetal we already know that it works in general on baremetal, the interesing part is what hardware is working for you? Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 30, 2017 Share #2712 Posted April 30, 2017 If you are on v1.01, replace the extra.lzma with this one https://mega.nz/#!KUxmhY7R!FYOSzesxdUjPlynO4YDvSu4LKfFkFk9eBvkUD9AGS04. I included the forcedeth module. Let me know if it works. I repeat. This is only for v1.01 NOT v.1.02a. Hoooo ... thanks I work on my computer. But only for version 6.0. It is not possible for version 6.1 ???, with this system or another, in my system extra.lzma is necessary. Thank you. "This is only for v1.01 NOT v.1.02a." - it rwaly means that it is not for 1.02a aka dsm 6.1 dsm 6.1 is using a differnt kernel so kernel modules for 6.0 (loader 1.01) will not work on 6.1 , with this system or another, in my system extra.lzma is necessary. i don't know what you mean or wanted to know by that Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 30, 2017 Share #2713 Posted April 30, 2017 hello, i just setup a bare metal system using JUN's loader 1.0.1 with DSM 6.0.2 update 8. I've setup my volumes and everything. The problem is that i do not see any Synology packages/apps available under package center for install. Is this normal?. All pages are blank and simply say "All packages have been installed" I was looking to install Synology's Hyper backup package. Image: https://www.dropbox.com/s/cwg8zx9tt3jdxmk/synoapps.GIF?dl=0 Quote Link to comment Share on other sites More sharing options...
mgrobins Posted May 1, 2017 Share #2714 Posted May 1, 2017 I did a fresh install using the 1.0.a2 loader with DS3617xs config on Bare-metal. I used the online install of the latest version of DSM and then updated to Update 2 online. All worked fine. *I do not select any of the connections to synology such as feedback or QC so cannot comment on them. My hardware is in my sig. Note this is a Xeon-D Board I am using which is what is in the 3617xs so I would anticipate good compatibility. NIC is integrated into the CPU SOC on my board (some variants have the i350 chip as well for 1GBe NIC which may be different). I can see packages, have installed the power-off package so manual install is functional and package updates are working. I'll edit and post more here as I examine other deeper features but so far from the last 2 weeks of playing around and rebuilding this a couple of times tweaking stuff I am confident this is a stable build at least on bare metal and generic hardware like I have. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted May 1, 2017 Share #2715 Posted May 1, 2017 I'm still wondering why I cannot see any packages at all in the package center. I'm talking about the standar packages offered by synology? Could it be because I just made up a random serial number and MAC address to use? And perhaps it's not matching the 3615xs hardware and thus synology is not showing me any packages? Quote Link to comment Share on other sites More sharing options...
sliders Posted May 1, 2017 Share #2716 Posted May 1, 2017 helo mgrobins Your USB port works ???? USB 2.0 or USB 3.0 ??? I have installed DS3617xs not working USB For external hard drive Quote Link to comment Share on other sites More sharing options...
jorka57 Posted May 1, 2017 Share #2717 Posted May 1, 2017 Has there been a fix for the APC UPC not being detected in DSM 6.0.1 UPDATE 1 or 11 pugged in either front or back. It was working fine in 5.2 with a HP N54L, plugged in the back usb ports. UPDATE - Back-UPS ES 500 and Back-UPS ES 350 are on the Syno compatibility list, however Back-UPS ES 700 is not Yes there is a fix. The issue is down to the current build not having USB 1.1 Compatibility (APC USB for mine is 1.1 probably the same for all early ones, mines a Smart UPS 750). The fix is to install a USB 3.0 card in the N54L, that acts as a hub and lets DSM see it correctly. Got mine from Amazon.co.uk here: https://www.amazon.co.uk/gp/product/B01C86K4IG/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 DSM 6 now sees it correctly. Hi, I've the same issue ! Why the onboard USB doesn't work and an extra USB card work ? Isn't a parameters in BIOS ? So, this will fix in future release like DSM 6.1 loader ? or I must buy this type of USB card ? Thanks Quote Link to comment Share on other sites More sharing options...
chege Posted May 1, 2017 Share #2718 Posted May 1, 2017 Has there been a fix for the APC UPC not being detected in DSM 6.0.1 UPDATE 1 or 11 pugged in either front or back. It was working fine in 5.2 with a HP N54L, plugged in the back usb ports. UPDATE - Back-UPS ES 500 and Back-UPS ES 350 are on the Syno compatibility list, however Back-UPS ES 700 is not Yes there is a fix. The issue is down to the current build not having USB 1.1 Compatibility (APC USB for mine is 1.1 probably the same for all early ones, mines a Smart UPS 750). The fix is to install a USB 3.0 card in the N54L, that acts as a hub and lets DSM see it correctly. Got mine from Amazon.co.uk here: https://www.amazon.co.uk/gp/product/B01C86K4IG/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 DSM 6 now sees it correctly. Hi, I've the same issue ! Why the onboard USB doesn't work and an extra USB card work ? Isn't a parameters in BIOS ? So, this will fix in future release like DSM 6.1 loader ? or I must buy this type of USB card ? Thanks DSM 6.x does not have USB 1.1 drivers and loaders does not have it yet. You can use cheap USB 2.0 hub, it should fix that issue. Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted May 1, 2017 Share #2719 Posted May 1, 2017 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 Quote Link to comment Share on other sites More sharing options...
alirz1 Posted May 1, 2017 Share #2720 Posted May 1, 2017 I'm still wondering why I cannot see any packages at all in the package center. I'm talking about the standar packages offered by synology?Could it be because I just made up a random serial number and MAC address to use? And perhaps it's not matching the 3615xs hardware and thus synology is not showing me any packages? I have gone and updated the serial number to be a valid one for the 3615xs model. however i still dont see ANY packages for installation in the package center. Could someone please give me an idea what could be preventing the synology packages from showing up? Im running bare metal, jun loader 1.0.1, DSM 6.0.2 update 8. The box has a good internet connection with DNS and everything working. If i add the syno community repo, those packages show up fine. However im looking for the default synology packages to show up in my package center. Quote Link to comment Share on other sites More sharing options...
chege Posted May 1, 2017 Share #2721 Posted May 1, 2017 Do you have installed proper certificate from synology? Try to ping global.download.synology.com to see if you can access it. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted May 1, 2017 Share #2722 Posted May 1, 2017 Do you have installed proper certificate from synology? Try to ping global.download.synology.com to see if you can access it. That address pings fine from the xpenology box. i only have the default cert that DSM has installed and comes with. Quote Link to comment Share on other sites More sharing options...
chege Posted May 1, 2017 Share #2723 Posted May 1, 2017 Do you have installed proper certificate from synology? Try to ping global.download.synology.com to see if you can access it. That address pings fine from the xpenology box. i only have the default cert that DSM has installed and comes with. Yeah, thats the one cert. I have no idea why you dont see synology packages, but you can do 2 things and both are not satisfied. 1. download from synology site and install manually packages you want, 2. try to do hard reset from settings Quote Link to comment Share on other sites More sharing options...
Salah Posted May 2, 2017 Share #2724 Posted May 2, 2017 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. 3com is most excellent choice Quote Link to comment Share on other sites More sharing options...
spyrule Posted May 2, 2017 Share #2725 Posted May 2, 2017 Can someone link a 6.1 Pat file that worked for 1.02a2 loader? I've tried a few and none seem to work on my baremetal setup (Dell DCS C6005) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.