Arcao
-
Posts
62 -
Joined
-
Last visited
Everything posted by Arcao
-
- Outcome of the update: SUCCESSFUL - DSM version prior update: Jun's Loader v1.04b DS918+, DSM 6.2.3-25426 Update 3 (DS918+) - Loader version and model: Redpill Tinycore V0.4.6, DSM 7.1-42661 (DS918+) - Using custom extra.lzma: NO - Installation type: Baremetal ASRock J3160DC-ITX, mini-pcie Intel 82574 (E1000e) ethernet card, 16 GB RAM, 4x SATA drives - Additional comments: Use official Synology .pat file. Added E1000e and r8168 ext.
-
Note: Marvel 88SE9215 also exists in M.2 M Key 2260 version: https://www.aliexpress.com/item/32814284199.html?spm=a2g0o.productlist.0.0.25b53c0ds9S1kJ&algo_pvid=e52cd22c-0354-472f-9c68-076f7c750c23&algo_expid=e52cd22c-0354-472f-9c68-076f7c750c23-6&btsid=0be3743615869391392268670eb250&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_ Or you can buy M.2 M key to PCIe 1x riser card similar to this: https://www.aliexpress.com/item/4000825543839.html?spm=a2g0o.productlist.0.0.377d17088YtFCl&algo_pvid=89c570e2-7219-41e7-8dcf-4ba32f7fdaa0&algo_expid=89c570e2-7219-41e7-8dcf-4ba32f7fdaa0-24&btsid=0ab6fa7b15869398135633409e5814&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_ -
I suggest to use Marvel 88SE9215 (4 port SATA 6Gbps PCIe x1) for best compatibility, because it's used in DS918+. This card is easily available at ebay (and other China shops) in the various form factors (PCIe / miniPCIe)
-
Success with AsRock J3160DC-ITX using DS918+ 1.04b loader with 0.8_syno ds918+ drivers patch. Notes: On first partition I updated grub config with correct USB stick VID/PID, valid SN and MACs (found on internet). On second partition I replaced kernel zImage and rd.gz with those from "DSM_DS918+_24922.pat" and replaced extra.lzma and extra2.lzma with those from "0.8_syno ds918+" package. First I used empty drive only to test if the loader works with clean installation using latest DSM 6.2.2-24922 Update 5 - selected automatic installation. Then I removed that test drive, attached existing drives and boot the system to start migration from DS3615xs DSM 6.1.7. Both network adapters works: onboard Realtek RTL8111GR and mini-pcie Intel 82574. HW transcoding not tested. I don't use it. Thanks @IG-88
-
Hi guys, I have Asrock J3160DC-ITX mobo (J3160 CPU, ahci storage driver) with Intel 82574L Gigabit ethernet card (use e1000e driver) in minipcie. I am currently on DS3615xs DSM 6.1.7-15284 Update 3 and I am thinking on update to DSM 6.2.2. Which model/loader could I use for this mobo? Which is more stable? As I understood, the 918+ loader will work only with "recovery" extra. Both DS3615xs and DS3617xs loaders should work too. Transcoding support is not priority for me.
-
Damn, I can't edit my previous post. Anyway, after copy kernel modules from extra.lzma to /lib/modules, it works again! So it looks like missing kernel modules detection is not present in a bootloader.
-
Hi guys, I tried to update my NAS (ds3617ds Jun's 1.02a2) from DSM 6.1.1-15101 Update 4 to DSM 6.1.2-15132 without luck, no lan. Fortunately I have serial cable connected to my router so I am able to debug it. Anyway the update removed all custom kernel drivers which was copied while initial installation. The modified rc and rc.modules are present, kernel modules and firmwares not. I tried also run reinstall bootloader choice, but it doesn't resolve missing kernel modules. Last chance is to copy missing kernel modules manually with second USB drive.
-
The same as Polanskiman wrote. Anyway for Quickconnect you need S/N and Network MAC Address valid pair.
-
Hello Guys, I week ago I migrated my nas from 3615xs DSM 6.0.2u11 with customized Jun v1.02a2 bootloader to 3617xs DSM 6.1.1u2. Unfortunately I had to do clean install because upgrading caused not loading network drivers. Maybe caused with a different kernel driver loader script. Fortunately I have serial cable connected to nas, so it was easy to modify /etc.default/VERSION file to change version and restart upgrade process again. So my suggestion is to do clean install if you decide to jump to this latest version from old one. @Jun: It would be good to have special bootloader choice to force reinstall Xpenology kernel modules and patches start scripts. I tried Install/Reinstall choice, but this didn't help me.
-
viewtopic.php?f=2&t=20216&p=75946#p75946
-
Here is differences between N3150 an J3160: http://www.anandtech.com/show/9806/intel-introduces-new-braswell-stepping-with-j3060-j3160-and-j3710. They are almost identical. J3160 has newer GPU and increased CPU Burst speed. Unfortunately both 5.2 and 6.0 bootloader doesn't support CPU Bursting. The CPU runs at 1.6GHz all the time. Beware on Apollo Lake CPUs, they needs patched kernel to work.
-
Hi Guys, I've just updated to DSM 6.0.2-8451 Update 5. All seems works. Change log here.
-
Damn. Kernel missing. :/ It looks like there are source code packages for helper apps.
-
The kernel image and ramdisk form Jun's 1.0 bootloader is identical to original 8451 version of synology_bromolow_3615xs pat file. In one earlier post Jun wrote that Intel image is not modified, only AMD image. In Update 4 they updated kernel but stayed on label 8451. Anyway the kernel image is binary different to the jun's 1.0 kernel image. In ramdisk they updated: /etc/VERSION (increased patch version number) /usr/sbin/raidtool Hard to say what happened. For better debugging you need serial cable.
-
ax88179_178a is already included in latest jun's bootloader, so it should work.
-
The first line decompress lzma archive and cpio command extract files to current directory. The second line pack all files and directories in current directory to cpio format and then apply lzma compression on it https://en.wikipedia.org/wiki/Cpio
-
If your bootloader works OK, it's not needed to touch on it. Just update to DSM 6.0.2 8451 Update3 only.
-
AFAIK, DSM 6.1 is a beta version which needs a new kernel image in bootloader, so not supported at the moment.
-
@Jun: Did you try to install DSM 6.0.2-8451 Update 3? It contains new kernel image in flashupdate_6.0-8451-s3_all.deb. I guess because of fix Dirty Cow CVE-2016-5195 vulnerability. Anyway here is change log: https://www.synology.com/cs-cz/releaseNote/DS3615xs Edit: I successfully updated to DSM 6.0.2-8451 Update 3.
-
OMG! Kernel modules from DSM 5.2 will never work on DSM 6.0.2 kernel!!! You can try to select force install DSM 6.0.2 in jun's 1.01 bootloader.
-
We 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 Our kernel modules are saved in extra.lzma. To extract extra.lzma I use this bash script: #!/bin/bash rm -r extra mkdir extra cd extra unlzma -c ../extra.lzma | cpio -im cd .. And for repack: #!/bin/bash cd extra find . | cpio -o -H newc | lzma > ../extra_new.lzma cd .. Kernel modules are loaded in order as they are defined in /etc/rc.modules: EXTRA_MODULES="mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x cnic e1000e igb ixgbe r8101 r8168 r8169 tg3 usbnet ax88179_178a button evdev" DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl ata_piix megaraid_sas mpt2sas mpt3sas" EXTRA_FIRMWARES="tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" 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
-
I guess that Beta needs Beta kernel image, which is not patched to work on our custom HW. Thus we need someone to patch Beta kernel first.
-
Dmesg should show you what symbols are missing. You can try to post result here.
-
Do you know what usb serial chip it is using? Because my v2 ramdisk/boot image contains drivers (kernel modules) for ftdi_sio, cp210x, ch341 and pl2303. I have tested usb serial adapters with FTDI an cp210x and both works OK. If yours is missing I can add it.
-
Hi guys, Here is prepared image with included AMD zImage: https://mega.nz/#!WVlWRKiR!ZYATz-ZuaoSF14I_V7tTkd1m0tAK04xs1IwsfAG2Afc (Amd img Hybrid UEFI/BIOS) Image prepared with OSFMount.
