sunnyqeen
-
Posts
6 -
Joined
-
Last visited
Posts posted by sunnyqeen
-
-
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
- 1
-
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.
-
@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
-
@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.
-
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
- 2
- 1
Jun's ds918+ loader modified for DSM-6.2.4
in Developer Discussion Room
Posted
Hi @gericb
here is the new link to the file.
https://ufile.io/b43l2wy4
Welcome making mirror.
Regards!