sunnyqeen 6 Posted January 30 Share Posted January 30 Hi All, I modified jun's loader to work with DSM-6.2.4, for safe reason, I removed all the kmods from the extra.lzma but kept rtc_cmos.ko The loader is created with DSM-6.2.4 update 2 Tested working well with vmware, you will need change .vmx file to use e1000e as it's built-in. ethernet0.virtualDev = "e1000e" It should work with main boards that have r8168, igb like J3455-ITX, etc here is the step to create the loader. 1. prepare patched kernel zImage RedPill team already have that well explained, so just use their tool to generate one. 2. prepare patched ramdisk make the extra.cpio that contains modified files from jun's 1.0.4 loader, mainly the jun.patch to match the new files inside rd.gz you could add more kmods for network cards and storage cards to load, as there is a lot of them for RedPill loader already extract the rd.gz to rd.cpio lzma -dc < rd.gz > rd.cpio the kernel support multi-cpio booting, so just copy the 2 files to one cat rd.cpio extra.cpio > rd_extra.cpio make new rd.gz that accepted by the kernel. original rd.gz has 64bytes sig, as the patched kernel already bypass the sig check, so we just need to add a fake sig to end of file. create a padding.bin which is 64bytes. lzma -9 rd_extra.cpio cat rd_extra.cpio.lzma padding.bin > rd_extra.lzma 3. modify grub.cfg to boot with the new zImage and rd_extra.lzma copy the patched zImage to first EFI partition of the synoboot.img and replace bzImage copy the rd_extra.lzma to the second partition enable the initrd loading initrd /rd_extra.lzma if all the steps are done you should have bootable 6.2.4 loader. The modified files are attached. you should unpack the extra.cpio to see what are changed. And you could try the made loader from here https://ufile.io/hrdlt20r UsedFiles.rar 2 1 Quote Link to post Share on other sites
flyride 750 Posted January 31 Share Posted January 31 Interesting, will have to play with this a bit. Can you explain this further? Is your modification causing kernel panics? 17 hours ago, sunnyqeen said: for safe reason, I removed all the kmods from the extra.lzma 17 hours ago, sunnyqeen said: It should work with main boards that have r8168, igb like J3455-ITX, etc This is because the native DS918+ has this NIC. Quote Link to post Share on other sites
IG-88 1,034 Posted January 31 Share Posted January 31 (edited) 2 hours ago, flyride said: This is because the native DS918+ has this NIC. no realtek in 918+, its intel (afair the realtek in the 918+ *.pat comes from another unit that is build on the same cpu architecture and uses the same base kernel config including drivers) https://xpenology.com/forum/topic/14127-guide-to-native-drivers-dsm-621-on-ds918/ On 2/4/2019 at 12:46 AM, flyride said: designed. Refer to the example below for DS918: DS918 Reference Hardware: CPU: Intel J3455 (Apollo Lake) GPU: Intel HD Graphics 500/505 Chipset: Intel SOC 2x1Gb Ethernet: Intel i211 SATA: 88SE9215 PCIe SATA 6.0 Gb/s controller Edited January 31 by IG-88 Quote Link to post Share on other sites
sunnyqeen 6 Posted January 31 Author Share Posted January 31 @flyride There are no kernel panics in VMware. The boot log looks good, and also the dmesg. I removed the kernel mods because they were built for 6.2.3 I am not sure if they are still working for 6.2.4 or not. you could add them back if you like to try any. Quote Link to post Share on other sites
flyride 750 Posted January 31 Share Posted January 31 3 hours ago, IG-88 said: no realtek in 918+, its intel (afair the realtek in the 918+ *.pat comes from another unit that is build on the same cpu architecture and uses the same base kernel config including drivers) https://xpenology.com/forum/topic/14127-guide-to-native-drivers-dsm-621-on-ds918/ As always, nothing gets by you man! And using my own post to refute. My point was that the realtek driver was part of the base image without Jun's add. But I didn't phrase it that way, did I? 26 minutes ago, sunnyqeen said: I removed the kernel mods because they were built for 6.2.3 I am not sure if they are still working for 6.2.4 or not. Technically they were built for 6.2.x as 6.2.3 did not exist when they were released. And honestly, I've never checked to see if they are identical to the mods embedded in 1.02b (6.1.x) version of Jun's loader. I don't think there would be much harm in leaving them in there if they did not cause a panic. Thank you for clarifying your reasoning. Quote Link to post Share on other sites
Nemesis 3 Posted February 1 Share Posted February 1 Thanks! Will this boot my 6.2.3 so I can upgrade to 6.2.4 through DSM? 1 Quote Link to post Share on other sites
sunnyqeen 6 Posted February 3 Author Share Posted February 3 @Nemesis you should make your own loader based on the post. most important, add your own net and storage drivers. I tried my pc and VMware, both working fine. because there is kernel update with 6.2.4 update 2 you will need to create 2 loader, 1 for orig 6.2.4, another for update 2. install using the first one and after update using the second one. if the loader and installation package do not match, you will see dsm recovery page. if you have serial port enabled, you will see the log message of mismatch. 1 Quote Link to post Share on other sites
Dvalin21 26 Posted February 5 Share Posted February 5 On 2/3/2022 at 2:38 PM, sunnyqeen said: @Nemesis you should make your own loader based on the post. most important, add your own net and storage drivers. I tried my pc and VMware, both working fine. because there is kernel update with 6.2.4 update 2 you will need to create 2 loader, 1 for orig 6.2.4, another for update 2. install using the first one and after update using the second one. if the loader and installation package do not match, you will see dsm recovery page. if you have serial port enabled, you will see the log message of mismatch. How do you enable serial port and get the logs? Quote Link to post Share on other sites
ed_co 14 Posted February 7 Share Posted February 7 (edited) @sunnyqeen any chance to do something similar for DSM7? LOL Edited February 7 by ed_co Quote Link to post Share on other sites
sunnyqeen 6 Posted February 8 Author Share Posted February 8 11 hours ago, ed_co said: @sunnyqeen any chance to do something similar for DSM7? LOL No possible, different kernel version. Jun's kmod will not be loaded. Quote Link to post Share on other sites
tintun2022 0 Posted February 28 Share Posted February 28 I tried it, but always bootup at recover screen Quote Link to post Share on other sites
sunnyqeen 6 Posted March 1 Author Share Posted March 1 (edited) 23 hours ago, tintun2022 said: I tried it, but always bootup at recover screen Try the new loader, I removed some version check. So it should work for 6.2.4 with/without update. And also attached new extra.cpio with the jun.patch update --- a/usr/syno/sbin/check_root_junior_match.sh +++ b/usr/syno/sbin/check_root_junior_match.sh @@ -43,9 +43,4 @@ if [ "$UniqueRD" != "kvmx64" -a "$UniqueRD" != "nextkvmx64" -a "$UniqueRD" != "kvmcloud" ]; then AssertDirectory "${RootMnt}.syno/patch/" AssertFileKeyValueEqual "/${VERSION_DEF}" "${RootMnt}${VERSION_UPDATER}" buildnumber - AssertFileKeyValueEqual "/${VERSION_DEF}" "${RootMnt}${VERSION_UPDATER}" smallfixnumber - if [ ! -f ${RootMnt}.SkipCheckPackingMatch ]; then - AssertFileKeyValueEqual "/${VERSION_DEF}" "${RootMnt}${VERSION_UPDATER}" packing - AssertFileKeyValueEqual "/${VERSION_DEF}" "${RootMnt}${VERSION_UPDATER}" packing_id - fi fi https://ufile.io/az21xwu0 extra.cpio Edited March 1 by sunnyqeen update content 1 Quote Link to post Share on other sites
foxbat 4 Posted March 15 Share Posted March 15 I confirm.The latest version it's working! installed and updated to the latest 6.2.update ( 5, if I remenmber) Thank you Quote Link to post Share on other sites
MajkelP 12 Posted March 17 Share Posted March 17 On 1/31/2022 at 12:59 AM, sunnyqeen said: Hi All, I modified jun's loader to work with DSM-6.2.4, for safe reason, I removed all the kmods from the extra.lzma but kept rtc_cmos.ko The loader is created with DSM-6.2.4 update 2 Tested working well with vmware, you will need change .vmx file to use e1000e as it's built-in. ethernet0.virtualDev = "e1000e" It should work with main boards that have r8168, igb like J3455-ITX, etc here is the step to create the loader. 1. prepare patched kernel zImage RedPill team already have that well explained, so just use their tool to generate one. 2. prepare patched ramdisk make the extra.cpio that contains modified files from jun's 1.0.4 loader, mainly the jun.patch to match the new files inside rd.gz you could add more kmods for network cards and storage cards to load, as there is a lot of them for RedPill loader already extract the rd.gz to rd.cpio lzma -dc < rd.gz > rd.cpio the kernel support multi-cpio booting, so just copy the 2 files to one cat rd.cpio extra.cpio > rd_extra.cpio make new rd.gz that accepted by the kernel. original rd.gz has 64bytes sig, as the patched kernel already bypass the sig check, so we just need to add a fake sig to end of file. create a padding.bin which is 64bytes. lzma -9 rd_extra.cpio cat rd_extra.cpio.lzma padding.bin > rd_extra.lzma 3. modify grub.cfg to boot with the new zImage and rd_extra.lzma copy the patched zImage to first EFI partition of the synoboot.img and replace bzImage copy the rd_extra.lzma to the second partition enable the initrd loading initrd /rd_extra.lzma if all the steps are done you should have bootable 6.2.4 loader. The modified files are attached. you should unpack the extra.cpio to see what are changed. And you could try the made loader from here https://ufile.io/hrdlt20r UsedFiles.rar 84.22 kB · 52 downloads Hi, I was wondering if this could be used for DS3617xs for 6.2.4-25556 and what has to be changed? Quote Link to post Share on other sites
gericb 13 Posted May 9 Share Posted May 9 On 1/30/2022 at 5:59 PM, sunnyqeen said: Hi All, I modified jun's loader to work with DSM-6.2.4, for safe reason, I removed all the kmods from the extra.lzma but kept rtc_cmos.ko The loader is created with DSM-6.2.4 update 2 Tested working well with vmware, you will need change .vmx file to use e1000e as it's built-in. ethernet0.virtualDev = "e1000e" It should work with main boards that have r8168, igb like J3455-ITX, etc here is the step to create the loader. 1. prepare patched kernel zImage RedPill team already have that well explained, so just use their tool to generate one. 2. prepare patched ramdisk make the extra.cpio that contains modified files from jun's 1.0.4 loader, mainly the jun.patch to match the new files inside rd.gz you could add more kmods for network cards and storage cards to load, as there is a lot of them for RedPill loader already extract the rd.gz to rd.cpio lzma -dc < rd.gz > rd.cpio the kernel support multi-cpio booting, so just copy the 2 files to one cat rd.cpio extra.cpio > rd_extra.cpio make new rd.gz that accepted by the kernel. original rd.gz has 64bytes sig, as the patched kernel already bypass the sig check, so we just need to add a fake sig to end of file. create a padding.bin which is 64bytes. lzma -9 rd_extra.cpio cat rd_extra.cpio.lzma padding.bin > rd_extra.lzma 3. modify grub.cfg to boot with the new zImage and rd_extra.lzma copy the patched zImage to first EFI partition of the synoboot.img and replace bzImage copy the rd_extra.lzma to the second partition enable the initrd loading initrd /rd_extra.lzma if all the steps are done you should have bootable 6.2.4 loader. The modified files are attached. you should unpack the extra.cpio to see what are changed. And you could try the made loader from here https://ufile.io/hrdlt20r UsedFiles.rar 84.22 kB · 64 downloads Can you re-upload your loader again, maybe to Google Drive, MEGA, Amazon Drive...curious to try it out. Just tried to download https://ufile.io/hrdlt20r and informed "The hosting period for this file has now expired, only paid users can download it. To download this file, you must first subscribe to a paid plan" Thanks Quote Link to post Share on other sites
sunnyqeen 6 Posted May 11 Author Share Posted May 11 Hi @gericb here is the new link to the file. https://ufile.io/b43l2wy4 Welcome making mirror. Regards! 1 Quote Link to post Share on other sites
gericb 13 Posted May 11 Share Posted May 11 38 minutes ago, sunnyqeen said: Hi @gericb here is the new link to the file. https://ufile.io/b43l2wy4 Welcome making mirror. Regards! Thank You! Quote Link to post Share on other sites
ratanapoll 0 Posted Monday at 11:18 AM Share Posted Monday at 11:18 AM On 5/11/2022 at 8:10 PM, sunnyqeen said: Hi @gericb here is the new link to the file. https://ufile.io/b43l2wy4 Welcome making mirror. Regards! Thank you ,It work . Quote Link to post Share on other sites
uaus 4 Posted Tuesday at 12:30 AM Share Posted Tuesday at 12:30 AM (edited) @sunnyqeen Is there a change to create or deliver this also for the "pure metal" operation of the HP microserver Gen7 (N36L/40L/54L (also Gen 8?)) (that would be: Bromollow 3.10.105 (DSM6) module): i.e. --> Jun's Loader v1.03b DS3615xs modified for DSM-6.2.4? Background: I have set up several Gen7/Gen8 HP microserver at friends of mine for several years as their data storage and backup. None of their HP microserver is additionally equipped with SATA extensions or additional NICs/PC-Cards, all "pure metal" of the original HP server. So driver support is enough for me/us, which was present in the wonderful original "Jun's Loader v1.03b DS3615xs". I will probably not switch to DSM-7.x soon, I don't see any advantages for me/us at the moment, but I would always like to get the security updates from Synology, until DSM-6.x is no longer supported by Synology. No question, redpill is the future for DSM-7.x support and also for additional SATA/PC cards or other mainboards, but for about the next two years, DSM-6.2.4 (with Jun's Loader v1.03b DS3615xs...) is probably enough for me/us with my limited hardware. I could imagine, that many other owners of HP Gen7/Gen8 servers feel the same way, who would like to get the security updates of the DSM-6.x. ... Edited Tuesday at 12:54 AM by uaus Quote Link to post Share on other sites
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.