• Content Count

  • Joined

  • Last visited

Everything posted by sancome

  1. the "open-vm-tools_bromolow-5.1_9.10.0-2476743-1.spk" has been released, you can download it from here: ... p4gaJAfiTa
  2. u can put the script file into the /usr/local/etc/rc.d/ directory. the filename like this ""
  3. i had build the shairport spk for dsm, u can try it. viewtopic.php?t=5294
  4. it's need to add files to both ramdisk and hdd, i will do this in the next release. thanks for you donate.
  5. i added this files to the img for you before, but you said it's not working.
  6. by using this spk, will display the DNS name and IP address in the vmware client, and reboot, shutdown and boot the virtual machine, rather than directly off the power. I recompiled it with the DSM 5.1 toolchain, if you encounter problems using the gnoboot's version(open-vm-tools-bromolow-9.4.0-1280544-50), you can try to replace. In the following environment test pass: VMWare Workstation 11.0 VMWare ESXi 5.5 update2 the latest vesion is "open-vm-tools_bromolow-5.1_9.4.6-1770165-3.spk" Download here: ... p4gaJAfiTa BTW: there is a "s
  7. you can download the latest release of Nanoboot-x86 from my website, i have fixed this pb.
  8. try to modify /etc/synoinfo.conf file, and change "supportraidgroup=no" to "yes", then report. If anyone want to test, please contact me, i will email the test img to you. sancome(AT)
  9. Nanoboot is for DSM 5.0-4528, no more drivers was added. So far, the DSM 5.1-5021 only test within the team, but will soon be released.
  10. With the same modification, works well on DS214play-4493, very strange. Maybe we really need the DS415play-4458.pat, but Synology does not release this file.
  11. Thanks @Vortex, but it still umount all volumes, i have replace the following files with DS214play-4458.pat(because there is no DS415play-4458.pat), maybe added new protection in DS415play-4493, can u help ? /usr/syno/synoman/webman/uistrings.cgi /usr/syno/synoman/webman/usersettings.cgi /usr/syno/synoman/webman/initdata.cgi /usr/syno/synoman/webman/modules/SystemInfoApp/LogViewer.cgi /usr/syno/synoman/webman/modules/PollingTask/polling.cgi /usr/syno/synoman/webman/modules/DSMNotify/dsmnotify.cgi /usr/syno/synoman/webman/modules/PkgManApp/PkgSynoMan.cgi /usr/syno/synoman/webman/modules/Pkg
  12. @Vortex, Can you help to create devices file for DS415play? I want to update Nanoboot-x86 by using DS415play. Thanks.
  13. The domain has been recovered, I don't know what happened, did not even received an e-mail. The new domain name is The Nanoboot just a small upadte. 1. update ar8171 driver, solve the problem does not show traffic. 2. add usb sound card drivers, you can now install and run the shairport.spk file. If you want to compile the kernel, there is the source, looking forward to your work.
  14. Installation instruction: ... -update-1/ Also I've placed the new Nanoboot boot image version here, I don't mind you available for download, but please Indicate the source
  15. How about AS-6XX_2.1.1.R3B2.img with kernel 3.7.9 ? i can't split it, it is different.
  16. Great work! I will try later,and report the progress at any time. Sent from my mi phone using Tapatalk
  17. We need to get initramfs first, only the kernel is not enough, look this: [ 1.433577] Please append a correct "root=" boot option; here are the available partitions: I boot the kernel on a physical machine, not virtualized environment.
  18. Hi, I am interested in this, and i have a question: How do you know to remove the header (261 bytes) of the file "AS-2XX_2.1.1.R3B2.img" ? Here is some debug info: debug info [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.7.9 (root@cross-builder) (gcc version 4.6.3 (x86 64-bit toolchain - ASUSTOR Inc.) ) #1 SMP Tue Mar 11 05:16:51 CST 2014 [ 0.000000] Command line: raid=noautodetect root=/dev/sda1 console=ttyS0,115200 BOOT_IMAGE=/zImage [
  19. The r8168 driver is already included. Sent from my mi phone using Tapatalk
  20. I also have a N40L, just enable "wol" in synoinfo.conf, it will be work normally.
  21. Try to add the following parameters: rmmod=r8168,r8169_new insmod=r8169
  22. Unexpectedly! x64 or x86 ? Does it work in ?