Jump to content
XPEnology Community

jun

Developer
  • Posts

    64
  • Joined

  • Last visited

  • Days Won

    32

Everything posted by jun

  1. jun

    DSM 6.1.x Loader

    Since there are considerable difference between beta source and the release version, I write and compile kernel modules instead, even the AMD kernel is a combination of the original kernel and the AMD support code compiled as module (sort of). I compile beta src kernel only to aid debugging, itself does not work properly, lacking required symbol etc, and I do not bother to fix it. can you provide a quick writeup on how you added LSI support as an example so that some of us can work on doing the same for other drivers? most drivers has nothing special, and for special drivers, better to wait for proper kernel source. For LSI hba, I use existing driver, patch the kernel to make it has proper device name, from sas* to sd*
  2. jun

    DSM 6.1.x Loader

    Since there are considerable difference between beta source and the release version, I write and compile kernel modules instead, even the AMD kernel is a combination of the original kernel and the AMD support code compiled as module (sort of). I compile beta src kernel only to aid debugging, itself does not work properly, lacking required symbol etc, and I do not bother to fix it.
  3. jun

    DSM 6.1.x Loader

    I thought one second is enough
  4. jun

    DSM 6.1.x Loader

    you can try to attach the img as a sata disk, you can also use a already installed disk image to skip installation step.
  5. jun

    DSM 6.1.x Loader

    oops, so it is indeed better to not replace existing files, maybe I should provide a bugfix v1.01 to fix it The security issue was already reported to me on the French section and it was with Arcao's v.2 hybrid uefi/bios loader. normally this message can be ignored, since this just means some drivers are updated, but it's a bit annoying, so I will fix it when I have time
  6. I have no idea at the moment, any additonal info, logs? And any other AMD user could help? Maybe compile a kernel with graphic console will aid debugging
  7. jun

    DSM 6.1.x Loader

    oops, good news is ata_piix works, bad news is seems not everyone loves it =) yeap. so is it possible to disable ata_piix? PS Thanks a lot for your work you can't at the memoent. if you intention is to move the ide drives out of the way, then DiskIdxMap boot paramenter will help, excerpt from source code comment /** * Modify disk name sequence. Each two characters define the start disk * index of the sata host. This argument is a hex string. * * Detail information: * http://synowiki.synology.com/MediaWiki/ ... _DiskIdMap * * For example, use DiskIdxMap=030600 will get the following result. * Disks of the 1st host: sdd, sde, sdf * Disks of the 2nd host: sdg, sdh, sdi * Disks of the 3rd host: sda, sdb, sdc */ If in addition you do not want ide disk to be show up anywhere, there is a libata.force boot parameter to disable it. this option works on sata disks too, but it still occupies the corresponding /dev/sdx name, so should be used with above option together for example, if you have a boot log like this, and you want disable ata2 & ata3, boot parameter should be libata.force=2:disable,3:disable [ 2.886833] ata2: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x2110 irq 14 [ 2.886836] ata3: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x2118 irq 15
  8. jun

    DSM 6.1.x Loader

    oops, so it is indeed better to not replace existing files, maybe I should provide a bugfix v1.01 to fix it
  9. jun

    DSM 6.1.x Loader

    this version try to detect boot partition automatically, so manually built vm can work without change some magic numbers, but this feature is not fully tested
  10. jun

    DSM 6.1.x Loader

    Sorry, I dont test ovf import, only try on VMware. What I think maybe go wrong is the file name and extension, try this first make sure you did not throw away synoboot.img, it is the real content, synoboot.vmdk is just a description file, if you did, put it back and try again. otherwise rename synoboot.img to synoboot-flat.vmdk open synoboot.vmdk with a text editor, make the same change to the line contains synoboot.img then try again
  11. jun

    DSM 6.1.x Loader

    Could there be any conflict if one would use the command line once thus editing /grub/grubenv and then edit the grub.cfg file manually with different data? Normally grub.cfg stores default configurations, and customization through grub command line interface will take precedence.
  12. jun

    DSM 6.1.x Loader

    Jun, Does configuring grub (vid/pid, SataPortMAp=) through command line apply changes to grub.cfg file permanently? It is saved in /grub/grubenv file, so it is permanent, but in a seperate file, this is the grub's way.
  13. jun

    DSM 6.1.x Loader

    oops, good news is ata_piix works, bad news is seems not everyone loves it
  14. jun

    DSM 6.1.x Loader

    Do you have a valid MAC-SN combination in your grub.cfg (matching with your real MAC)? I think MAC and SN are not used during installation, in fact, I am not aware that MAC/SN has any particular relationship between each other.
  15. Thanks Jun. Was going to mention that but you were faster! I am waiting for volunteers . BTW, good tutorial, this would help many people.
  16. I've uploaded a patched kernel for AMD users on the original post, but its not tested at the moment, you could have a try if you are brave enough
  17. jun

    DSM 6.1.x Loader

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

    DSM 6.1.x Loader

    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.
  19. jun

    DSM 6.1.x Loader

    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 I used modified DS916+ on a J3160 board, hw transcoding seems work.
  20. jun

    DSM 6.1.x Loader

    I used Jun's bare metal UEFI DSM 6 bootloader from OP (opening post) and updated grub.cfg: serial --port=0x3F8 --speed=115200 terminal_input serial terminal_output serial set default='0' set timeout='1' set fallback='0' insmod part_msdos insmod part_gpt set locale_dir=$prefix/locale set lang=en_US menuentry 'Synology DS3615xs' --class os { insmod fat set img=$prefix/../image/DS3615xs linux $img/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=0x5583 console=ttyS0,115200n8 sn=xxxxxxx mac1=xxxxxxx withefi elevator=your_magic_elevator quiet initrd $img/ramdisk.lzma } Replace VID, PID, sn and mac1 with yours. Make sure you have enabled COM port in UEFI BIOS, also switch to UEFI boot. Then boot up and open browser to find.synology.com. There click on Install latest DSM button (no need to select any pat, it will download correct one automatically). After restart you will have NAS updated to DSM 6.0.2-8451. Don't forget to perform update to DSM 6.0.2-8451 Update 2 via Control panel. Thanks for response. I've made everything as you described, but it's not working. I have ASRock J3160TIX. updated UFI to v1.3 Made a clear CMOS, Enabled(by default) COM Port to address 3F8h/IRQ4 advanced\USB Support\ Switched to UEFI setup only Tried to change HDD to new one. Booted from 1st efi partition, and the second UEFI and had the same result - > Failed to install the file. The file is probably corrupted (13) Could you write all uefi settings that you have? Do you use PCIe sata or using ASMedia sata3? J3160ITX is one of my test boards, so it is expected to work out of box, if you set VID/PID to match your usb drive. Edit: [spoiler=]one thing I forget to mention, you'd better plug your usb stick in a USB2 port, usb3 port has some issue duration installation if I recall correctly. It turn out that my impression was wrong, please ignore this.
  21. jun

    DSM 6.1.x Loader

    In hyper-V it boots and I can see VM screen: Then nothing else, and find.synology.me cannot connect in browser. Anyone can help and figure out the reason? Is that so the kernel and ramdisk has to be booted using EFI way? I dont know anything specific about Hyper-V, but in general, is is not possible to install this version with ISO only, but use ISO to load an installed version should be fine. The reason is DSM installer expect writable synoboot1/synoboot2 partitions, and I dont attemp to change this part of logic.
  22. jun

    DSM 6.1.x Loader

    To my surprise, I've seen report that AMD E-350 box works.
  23. jun

    DSM 6.1.x Loader

    Prints a couple lines like: then freezes The synology kernel do not have AMD CPU support compiled in, so it is expected that AMD box can not run properly. Adding support requires a full recompilation from source or some non-trivial patch to the synology kernel, both solution has its own difficulties. I personally does not have the hardware, so It may be a long wait before something positive happens.
  24. jun

    DSM 6.1.x Loader

    winscp is fine, but it maybe not easily be connected as root user. so you need change the above mount line as something like this, to give non-root use full access to the boot partition. mount -o umask=0 /dev/synoboot1 /mnt there are a few possible reasons cause it not got saved: 1. your boot disk is set to non-persistence 2. you did not properly umount the disk after editing. 3. vi is not really beginner friendly.
  25. jun

    DSM 6.1.x Loader

    if you are comfortable with shell, just ssh into DSM, type echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt /mnt/grub/grub.cfg umount /mnt
×
×
  • Create New...