Jump to content
XPEnology Community

jun

Developer
  • Posts

    64
  • Joined

  • Last visited

  • Days Won

    32

Posts posted by jun

  1. 5 hours ago, Benoire said:

    @jun if using the SASIDXmAP command, will this order the disks according to their connected positions instead of which one is detected first at boot up?  By this I mean, presently disk 1 may be in slot 1 of the enclosure with an LSI 9211-8i (IT) HBA but in DSM it could be disk 6... Does this fix that and I insert a disk in to slot 8, it will show it even if its the only disk? 

    yes, that is what I means by "stable SAS disk name"

  2. 1 hour ago, autohintbot said:

      

    Thanks for the info!  I still haven't been able to get my setup to enumerate disks starting at 1 (in the GUI, /dev/sda viewed from command line).  Specs: 

     

    My grub.cfg line:

     

     

    I changed sata_pcislot as an experiment, because I noticed the PCI slot number changed between my 6.1.x VMs (EFI Boot) and this VM (BIOS boot). 

     

    6.1.x VM is showing:

     

    While this VM is showing:

     

    The setup is the same, so my best guess is this is just how VMWare has set up their DSDT/whatever tables between the two firmware options.  Maybe the order of adding devices when I made the VM originally altered things, though.  Either way, I didn't notice a difference from sata_pcislot=5 to sata_pcislot=3. 

     

    I had to increase internalprtcfg in synoinfo.conf to see all the disks.  You can see the 8-disk gap in the UI: 

     

    691277189_ScreenShot2018-08-04at5_45_34PM.thumb.png.308c5f7dee836a80eae528cd5688124e.png

     

    Or in the shell:

     

    The VM is pretty minimally configured:

     

    1790841821_ScreenShot2018-08-04at5_48_00PM.thumb.png.a97cd09f2f4e6d6e57d9f58038bf943e.png

     

    I don't see anything glaringly obvious in dmesg or early boot from the serial port.  Happy to paste those your way if you want to take a peek, though!  At this point I'm at the limits of my (admittedly poor) XPE knowledge, so just kind of hoping the EFI-fixed version makes my 6.1 VMs behave the same with a 6.2 install... 

    since you are using a external sas enclosure, that is a setup I've never experimented before,  here is my educated guess:

    You issue is caused by my implementation of stable Sas disk naming, the disk name is simply derived from sas remote phy id plus SasIdxMap as start position.

    I think ports directly connected to hba card are 0-7, and external expansion cards inside your enclosure will start from 8

    You can try to set SasIdxMap=0xfffffff8, that is -8 to move start position to 0

    if that does not work, simple remove SasIdxMap option, then sas disk names should occupy unused slots as before.

     

    • Like 1
  3. 22 hours ago, autohintbot said:

    I spent some time experimenting tonight, and I still can't get my disks starting at 1 with the 6.2 loader, either 3615 or 3617, with an LSI passed through in an ESXi 6.5u2 VM.

     

    I noticed SasIdxMap=0 from grub.cfg doesn't actually come through on /proc/cmdline, which seems like it's trying to start enumeration at 0 for an SAS controller:

    
    sh-4.3# cat /proc/cmdline
    syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi quiet root=/dev/md0 sn=XXXXXXXXXXXXX mac1=XXXXXXXXXXXX netif_num=1 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1

    But, it doesn't come through on my 6.1.x VM with the same card either, and that correctly enumerates disks starting with /dev/sda.  Not sure what else to try.  I increased internalportcfg for now, but that's just a landmine on the next big update (I guess it's possible to include that in the jun.patch in extra.lzma though).

     

     

    Hi, options not available in vanilla DSM are hidden in /proc/cmdline
    here is a example of disk order related options: SasIdxMap=0 DiskIdxMap=080C SataPortMap=4
    it should works like this:   DiskIdxMap make first sata controller start from disk 8, second from disk 12 etc,
    SataPortMap limit the number of disks a sata controller can have(vmware's virtual sata controller have 32 ports!)
    then SasIdxMap make SAS controller start from disk 0, as a plus, this option should give you a stable SAS disk name

    • Like 1
  4. hi,
     
    good news for better/more drivers
    there is new source now for DSM 6.1.3
    https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/15152branch/
     
    this weekend or the one after this weekend i will update my systems/vm's to 6.1.3 and will try to compile a new driver set and provide a new extra.lzma
    hopefully all the drivers that failed with unknown symbols will work with that source and DSM 6.1.3
     
    synology stripe comments and replace ifdefs to meaningless myabc in the kernel source,i believe that is the cause of the incompatibility
    • Like 1
  5. Another thing I've just noticed.. I've just upgraded from DSM 6.0 to 6.1 and every time the VM boots it's status is set as "Recoverable". It's able to repair it every time, but I have no idea why this should happen. Never encountered this on earlier versions of XPenology. 
    because the loader packs a earlier kernel & ramdisk with it, and they are expected to be upgraded to latest version during install or upgrade process. that is how the loader is able to support multiple dsm version, and allows you to apply latest security fix, if kernel version code does not change.
  6. 5 hours ago, fitman said:

    @jun, is it 1.02b? It seem it cannot boot up for ds3617 in baremetal, always said migratable. Even, I use it for new install, it still got the same issue.

     

    Use back 1.02a2, no problem on clean installation, 6.11 or 6.12

    Sorry, fixed

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

    its an old script bug due to my oversight, I am uploading a new version to fix it, hopefully without introduce new bugs :smile:
    • Like 8
  8. DS916 is added for hardware transcoding support, and its kernel is optimized for intel's braswell family processors. For desktop/mobile processors, 4th Gen Core processor or later is required to provide necessary instruction features.

    for example, i7-4700mq works, but e3-1230v2 complains about undefined instructions.

     

    Trying to understand the current situation here. Does the undefined instructions complain affect machines running e3-1230 v2 with esxi being the underlay OS?

    ds916p is for braswell family processors (j3160 n3710 etc), there seems no much point to run it on e3 except debugging the loader.

  9. Polanskiman said:
    jun said:
    Polanskiman said:

    @jun

     

    I tested both D3617xs and DS916+ with loader v1.02a2. There seems to be an issue with the DS916+. This was done under VirtualBox. Below the logs:

     

    
    
    
    GNU GRUB  version 2.02~beta2-36ubuntu3.9
    
         DS916+ 6.1 Baremetal with Jun's Mod v1.02-alpha                            
         DS916+ 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall                  
         DS916xs 6.1 VMWare/ESXI with Jun's Mod v1.02-alpha
    
    	Use the ^ and v keys to select which entry is highlighted.          
    	Press enter to boot the selected OS, `e' to edit the commands       
    	before booting or `c' for a command-line.
    	The highlighted entry will be executed automatically in 5s.
    
    [    0.423566] Modules linked in:
    [    0.436016] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.10.102 #15047
    [    0.467738] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
    [    0.502364] task: ffff88007c4a3510 ti: ffff88007c4a4000 task.ti: ffff88007c4a4000
    [    0.537344] RIP: 0010:[]  [] sha_transform+0x2e/0x12e0
    [    0.578929] RSP: 0000:ffff88007c4a7d60  EFLAGS: 00010092
    [    0.602867] RAX: ffffffff819c2a80 RBX: 0000000010325476 RCX: 00000000e8a4602c
    [    0.636074] RDX: ffff88007c4a7db0 RSI: ffffffff819c2a80 RDI: ffff88007c4a7d98
    [    0.671161] RBP: 00000000c3d2e1f0 R08: 00000000efcdab89 R09: 0000000010325476
    [    0.706130] R10: 0000000067452301 R11: 0000000098badcfe R12: 00000000f33d5697
    [    0.740213] R13: ffff88007c4a7e66 R14: 0000000000000286 R15: 0000000000000004
    [    0.775799] FS:  0000000000000000(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
    [    0.816173] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    [    0.843490] CR2: 0000000000000000 CR3: 000000000180d000 CR4: 00000000000406e0
    [    0.878398] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [    0.916584] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    [    0.953482] Stack:
    [    0.961549]  0000000000000010 ffffffff81842cc0 ffffffff81842ce4 ffff88007c4a7e66
    [    0.995757]  0000000000000286 0000000000000004 ffffffff812fa652 efcdab8967452301
    [    1.026519]  1032547698badcfe 00000000c3d2e1f0 ffffffff81842e10 0000000000000246
    [    1.059921] Call Trace:
    [    1.069624]  [] ? extract_buf+0x62/0x140
    [    1.097915]  [] ? __wake_up+0x35/0x50
    [    1.120773]  [] ? account+0x104/0x290
    [    1.145425]  [] ? extract_entropy+0x5c/0x170
    [    1.167743]  [] ? proc_register+0x67/0x140
    [    1.195936]  [] ? neigh_hash_alloc+0x7b/0xb0
    [    1.220055]  [] ? neigh_table_init+0x86/0x2b0
    [    1.249181]  [] ? arp_init+0xc/0x47
    [    1.269220]  [] ? inet_init+0x18e/0x27a
    [    1.286156]  [] ? ipv4_offload_init+0x63/0x63
    [    1.307237]  [] ? do_one_initcall+0xea/0x140
    [    1.327047]  [] ? kernel_init_freeable+0x13a/0x1bb
    [    1.354132]  [] ? rest_init+0x70/0x70
    [    1.374793]  [] ? kernel_init+0x5/0x180
    [    1.396170]  [] ? ret_from_fork+0x58/0x90
    [    1.418521]  [] ? rest_init+0x70/0x70
    [    1.441242] Code: 8b 5f 08 44 8b 17 41 56 44 8b 47 04 44 89 d1 41 55 c1 c1 05 41 54 45 8d 23 55 8b 6f 10 41 81 c4 99 79 82 5a 53 8b 5f 0c 41 89 d9 <0f> 38 f0 06 45 31 d9 89 02 45 21 c1 41 c1 c8 02 41 31 d9 41 01 
    [    1.485888] RIP  [] sha_transform+0x2e/0x12e0
    [    1.505453]  RSP 
    
     

    DS916 is added for hardware transcoding support, and its kernel is optimized for intel's braswell family processors. For desktop/mobile processors, 4th Gen Core processor or later is required to provide necessary instruction features.

    for example, i7-4700mq works, but e3-1230v2 complains about undefined instructions.

     

    Ok then I guess someone with the required hardware should test it.

     

    By the way, what did you add/fix on v1.02a2?

    I enabled mcu emulation for ds916p/ds3617 to deal with "time bomb" problem, plus as you notice, standalone patcher is provided for interested guys, though I think peoples want to recompile the loader should be able to extract it from the img.

    These models (in fact, I believe all new models) expect some kind of challenge/response through serial port with on board mcu. I solve this by emulate a serial port to response this kind messages in kernel.

  10. On 4/11/2017 at 4:01 PM, Polanskiman said:

    @jun

     

    I tested both D3617xs and DS916+ with loader v1.02a2. There seems to be an issue with the DS916+. This was done under VirtualBox. Below the logs:

     

    
    GNU GRUB  version 2.02~beta2-36ubuntu3.9
    
         DS916+ 6.1 Baremetal with Jun's Mod v1.02-alpha                            
         DS916+ 6.1 Baremetal with Jun's Mod v1.02-alpha Reinstall                  
         DS916xs 6.1 VMWare/ESXI with Jun's Mod v1.02-alpha
    
    	Use the ^ and v keys to select which entry is highlighted.          
    	Press enter to boot the selected OS, `e' to edit the commands       
    	before booting or `c' for a command-line.
    	The highlighted entry will be executed automatically in 5s.
    
    [    0.423566] Modules linked in:
    [    0.436016] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.10.102 #15047
    [    0.467738] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
    [    0.502364] task: ffff88007c4a3510 ti: ffff88007c4a4000 task.ti: ffff88007c4a4000
    [    0.537344] RIP: 0010:[]  [] sha_transform+0x2e/0x12e0
    [    0.578929] RSP: 0000:ffff88007c4a7d60  EFLAGS: 00010092
    [    0.602867] RAX: ffffffff819c2a80 RBX: 0000000010325476 RCX: 00000000e8a4602c
    [    0.636074] RDX: ffff88007c4a7db0 RSI: ffffffff819c2a80 RDI: ffff88007c4a7d98
    [    0.671161] RBP: 00000000c3d2e1f0 R08: 00000000efcdab89 R09: 0000000010325476
    [    0.706130] R10: 0000000067452301 R11: 0000000098badcfe R12: 00000000f33d5697
    [    0.740213] R13: ffff88007c4a7e66 R14: 0000000000000286 R15: 0000000000000004
    [    0.775799] FS:  0000000000000000(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
    [    0.816173] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    [    0.843490] CR2: 0000000000000000 CR3: 000000000180d000 CR4: 00000000000406e0
    [    0.878398] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [    0.916584] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    [    0.953482] Stack:
    [    0.961549]  0000000000000010 ffffffff81842cc0 ffffffff81842ce4 ffff88007c4a7e66
    [    0.995757]  0000000000000286 0000000000000004 ffffffff812fa652 efcdab8967452301
    [    1.026519]  1032547698badcfe 00000000c3d2e1f0 ffffffff81842e10 0000000000000246
    [    1.059921] Call Trace:
    [    1.069624]  [] ? extract_buf+0x62/0x140
    [    1.097915]  [] ? __wake_up+0x35/0x50
    [    1.120773]  [] ? account+0x104/0x290
    [    1.145425]  [] ? extract_entropy+0x5c/0x170
    [    1.167743]  [] ? proc_register+0x67/0x140
    [    1.195936]  [] ? neigh_hash_alloc+0x7b/0xb0
    [    1.220055]  [] ? neigh_table_init+0x86/0x2b0
    [    1.249181]  [] ? arp_init+0xc/0x47
    [    1.269220]  [] ? inet_init+0x18e/0x27a
    [    1.286156]  [] ? ipv4_offload_init+0x63/0x63
    [    1.307237]  [] ? do_one_initcall+0xea/0x140
    [    1.327047]  [] ? kernel_init_freeable+0x13a/0x1bb
    [    1.354132]  [] ? rest_init+0x70/0x70
    [    1.374793]  [] ? kernel_init+0x5/0x180
    [    1.396170]  [] ? ret_from_fork+0x58/0x90
    [    1.418521]  [] ? rest_init+0x70/0x70
    [    1.441242] Code: 8b 5f 08 44 8b 17 41 56 44 8b 47 04 44 89 d1 41 55 c1 c1 05 41 54 45 8d 23 55 8b 6f 10 41 81 c4 99 79 82 5a 53 8b 5f 0c 41 89 d9 <0f> 38 f0 06 45 31 d9 89 02 45 21 c1 41 c1 c8 02 41 31 d9 41 01 
    [    1.485888] RIP  [] sha_transform+0x2e/0x12e0
    [    1.505453]  RSP 
    
     

    DS916 is added for hardware transcoding support, and its kernel is optimized for intel's braswell family processors. For desktop/mobile processors, 4th Gen Core processor or later is required to provide necessary instruction features.

    for example, i7-4700mq works, but e3-1230v2 complains about undefined instructions.

  11. Think I've spotted a potential little bug in the grub.cfg file (or in how it's applied)..

     

    set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet'
    
    set sata_args='sata_uid=1 sata_pcislot=1 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=2 SasIdxMap=0'

     

    If I leave SataPortMap=2 (I have 2 disks in my test box, so =2) in the set sata_args line, it doesnt work.. I get the old reported issues 'we've detected errors on disks 3,4,5 etc.

    However, If I move the command up into the common_args line.......

     

    set common_args_3615='syno_hdd_powerup_seq=0 SataPortMap=2 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet'
    
    set sata_args='sata_uid=1 sata_pcislot=1 synoboot_satadom=1 DiskIdxMap=0C SasIdxMap=0'

     

    ...It works! :grin::grin::grin:

     

    It boots fine and I get the 'Install' prompt - rather than a load of reported disk errors..

    After applying the 6.1 PAT file and restarting, disks are fine, data is fine, it's now on 6.1.. :grin:

    DSM61_zpsatcdqb2z.jpg~original

    DSM61-2_zpsws2p4dgh.jpg~original

     

    So........ Might there be an issue with applying the sata_args?

     

    Cheers,

     

    #Hostilian

    sata and usb here refers to the boot device of the DSM, usb for baremetal and sata for VM

  12. I got the dreaded 'Sorry, the page you are looking for is not found' after 6.1 upgrade.

     

    Digging around, looks like synoscgi upstart job fails to run and it's due to libsynoshare.so.6 (error while loading shared libraries: /lib/libsynoshare.so.6: invalid ELF header). Few other commands I tried (synoupgrade) failed for the same reason.

     

    Typically, ELF header issues are due to mixing 32 and 64 bit dependencies (between executable and shared object libs). Hopefully, one of you with more experience with syno stuff can think of workarounds or things that can be tried.

    some DSM models has extra checks after running around a few hours, if this check is not passed, a few .so will be deliberately corrupted,

    the code to deal with this is not enabled for the model if you see "device not supported" in the kernel log

  13. I tried with force install and it worked, but now, every time my machine boots, this error comes up...

     

    jtdUCAS.jpg

     

    Any ideas?

     

    Same error over here too after each reboot. As a matter of fact, found that on the 6.0.2 the SSD (500GB) 200 of used space after upgrading to 6.1 it shows that 254GB used space - seems like 54Gb puff gone :ugeek:

    Is that the case on your Nas too ?

     

    Not really. All my pre existing volumes maintained the same used/free space ratio, and my SSD that I use as cache it's working properly and with the correct size/space available.

     

    Anyone has any tips on debugging this issue?

     

    If you have a look at grub.cfg, notice that "Force Install" entry has a extra argument "syno_port_thaw=1", that is the option to prevent kernel complaining disk disabled problems, you may want to add this option to normal boot menu entry to see if it helps.

  14. Clean OP, add link to Pokanskiman's tutorial and add download mirror.

     

    DMS 6.1 uses updated kernel (3.10.102).

    The kernel sources for 6.0.2 (3.10.77) has not been released yet so don't hope anything from Syno before months.

     

    Like before no sources = no loader

     

    jun's v1.01 loader CAN'T support DSM 6.1 so DO NOT UPGRADE !

     

    I've rebased the vendor changes on 3.10.77 to 3.10.102, seems still works.

     

    jun your are the MAN :mrgreen:

     

    Next step is I think to troubleshoot the network issue on some system that "prevent" network driver to load at boot.

    How can I (or the community) help you to debug ?

    How do you display/access the early boot stage without serial console ?

     

    Based on my unintentionally migration from ds3615xs to ds3617sx, and feedbacks from this forum, I guess some drivers are not correctly updated in the rootfs, thus caused network failure, a clean installation does not suffer from this problem.

     

    I use VM to do preliminary test, does not have the luxury to test on baremetals.

     

    As before, I do not have much time to build and test drivers, if developers and users can help in these area, then more hardware will be supported.

  15. I can see in the grub.cfg file the AMD loader is commented out, does this mean that those using Gen7 HP Microservers have to wait a little longer? Just wanted to make sure before trying to use this.

     

    Yes, AMD loader need some extra work.

  16. Clean OP, add link to Pokanskiman's tutorial and add download mirror.

     

    DMS 6.1 uses updated kernel (3.10.102).

    The kernel sources for 6.0.2 (3.10.77) has not been released yet so don't hope anything from Syno before months.

     

    Like before no sources = no loader

     

    jun's v1.01 loader CAN'T support DSM 6.1 so DO NOT UPGRADE !

     

    I've rebased the vendor changes on 3.10.77 to 3.10.102, seems still works.

  17. I worked it out (sort of).

    After trying all your tips, the reader still did not work in any way.

    Almost ready to throw it out of the window, I tried to insert an old USB 2 Hub between de HP microserver and smartreader.

    Immediately, the reader started working, exactly as before on 5.2.

    I tried to remove the hub and immediately it stopped working again. I also tried different BIOS settings regarding USB, bot none worked.

    Lsusb only shows the device when connected through the hub.

    So the only way to get the smargo working for now is to use the old (Sweex) USB 2.0 Hub. I am okay with that for now, but if possible I would like to connect the reader directly.

     

    look at my smargo info inside chroot:

    oscam manualy compiled using smargo in libusb

    instaled all dependencies and libusb-dev 1.0 i think.

     

    root@nas:/usr/src/oscam-svn/Distribution# ./list_smargo-1.20-unstable_svn11279-x86_64-linux-gnu-libusb
    libudev: udev_has_devtmpfs: name_to_handle_at on /dev: Function not implemented
    Looking for smartreader compatible devices...
    bus 002, device 005 : 0403:6001 Smartreader2 plus (type=SRv2, in_ep=02, out_ep=81; insert in oscam.server 'device = SRv2;Serial:CCCCCCCC')
    

     

    dmesg after unplug it and plug it again:

     

    [36342.567036] usb 2-1.4: USB disconnect, device number 4
    [36344.801652] usb 2-1.4: new full-speed USB device number 5 using ehci-pci
    

     

    again, if you guys are using oscam, dont use FTDI drivers, reconfigure your driver to use smartreader protocol, its alot beter

     

    [reader]
    
    protocol                      = smartreader
    device                        = SRv2;Serial:CCCCCCCC
    detect                        = cd

    work 100%

     

    This version of loader (and synology's version) does not have driver for ohci usb controller, a host controller for usb 1.x.

    Why it is not included in the loader?

    Because I did not notice it was not included.

    Why not for synology?

    My understanding is that, Intel invent UHCI for usb 1.x, so normally, intel chipsets will never have OHCI controllers,

    nowdays even UHCI's are uncommon, lots of usb 2.x/3.x controller seems include builtin hubs to do the translation for usb 1.x devices.

     

    In your use case, the external hub simply acts as a usb 1.x to usb 2.x translator, that is a viable workaround for the moment.

     

    I will make sure this driver is availble when next release is out, developers can also compile ohci-hcd yourself.

  18. Some Info for N54L users (AMD based)

    I burned the newest 1.01 Image on my USB Stick, adjusted PID, VID, SNR and MAC but still ran into "Booting the Kernel" without finding the NAS in my network.

     

    After i adjusted the timeout to '5' i had the chance to see the grub menu, where i could choose the AMD entry, which did the trick :smile:

     

    Thanks for the hard work :smile:

     

    I thought one second is enough :grin:

     

    Next update maybe change the timeout= parameter to default to 3 or 4 seconds. :cool: Should be plenty enough

    Press up/down key before the menu is shown, the same way as you enter BIOS setup screen

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

     

     

    The new kernel will not in effect, unless manually copy it to the right place.

    Since Intel machines are in fact using unmodified synology kernel, I am considering restructure the boot partition's to closely match synology's, so that new kernel will take effect automatically, but this has the potential risk of a small upgrade may break a working system.

  20. @Jun Can you share the steps to recompile your patched kernel zImage? I can recompile the kernel with Hyper-V support, but it seems still not work, so I guess I missed the proper patch for DSM6.0.2?

    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.

    Thanks for the reply, jun! I am trying to make hv_balloon.ko, hv_utils.ko, hv_vmbus.ko, hv_netvsc.ko, hv_storvsc.ko load correctly as kernel module, but I get unknown symbol error, by checking dmesg output, there are many unknown symbols, for example:

    [436076.774681] hv_vmbus: Unknown symbol hv_register_vmbus_handler (err 0)      
    [436076.774985] hv_vmbus: Unknown symbol x86_hyper_ms_hyperv (err 0)            
    [436076.775042] hv_vmbus: Unknown symbol pv_cpu_ops (err 0)                     
    [436076.775055] hv_vmbus: Unknown symbol x86_hyper (err 0)                      
    [440432.878847] hv_vmbus: Unknown symbol hv_register_vmbus_handler (err 0)      
    [440432.878871] hv_vmbus: Unknown symbol x86_hyper_ms_hyperv (err 0)            
    [440432.878885] hv_vmbus: Unknown symbol pv_cpu_ops (err 0)                     
    [440432.878914] hv_vmbus: Unknown symbol x86_hyper (err 0)                      
    [440463.877528] hv_utils: Unknown symbol vmbus_driver_unregister (err 0)        
    [440463.877545] hv_utils: Unknown symbol vmbus_sendpacket (err 0)               
    [440463.877556] hv_utils: Unknown symbol vmbus_prep_negotiate_resp (err 0)      
    [440463.877568] hv_utils: Unknown symbol vmbus_close (err 0)                    
    [440463.877578] hv_utils: Unknown symbol vmbus_recvpacket (err 0)               
    [440463.877600] hv_utils: Unknown symbol cn_netlink_send (err 0)                
    [440463.877611] hv_utils: Unknown symbol vmbus_open (err 0)                     
    [440463.877625] hv_utils: Unknown symbol cn_del_callback (err 0)                
    [440463.877700] hv_utils: Unknown symbol __vmbus_driver_register (err 0)        
    [440463.877717] hv_utils: Unknown symbol cn_add_callback (err 0)                
    [440706.396491] hv_vmbus: Unknown symbol hv_register_vmbus_handler (err 0)      
    [440706.396518] hv_vmbus: Unknown symbol x86_hyper_ms_hyperv (err 0)            
    [440706.396532] hv_vmbus: Unknown symbol pv_cpu_ops (err 0)                     
    [440706.396545] hv_vmbus: Unknown symbol x86_hyper (err 0)  

     

    Then maybe let's start with pv_cpu_ops, I checked the reference and dependency of this symbol in below link:

    c

     

    Any suggestions on how to make such symbol loadable as a kernel module based on above link's information?

    not possible unless you've managed to

    compile the missing code as module, as you may notice, these code are normally compiled as part of the kernel(and for a good reason), so you need hacking the code to make it work, that's the hardest part.

     

    EDIT:

    I've been a bit careless reading your question, you clear know most of the above info.

×
×
  • Create New...