hendry

is this project still continue for the latest DSM version ?

@pocopico why the result of loader.img does not have custom.gz file ? in fact i add some custom extenstion before build the loader. MODEL="DS918+" PLATFORM="APOLLOLAKE" GRUB_PROJECT="grub-2.x" GRUB_VERSION="1" DSM_VERSION="42218" has custom.gz like this one but on MODEL="DS3622xs+" PLATFORM="BROADWELLNK" GRUB_PROJECT="grub-2.x" GRUB_VERSION="1" DSM_VERSION="42962" no custom.gz

hi @pocopico can you compile v9fs drivers for latest build 7.2 ?

hope you have a time to try installing docker xpenology as the instruction on the link i show u. i just think, the module (.ko) is missing in loader img which was need to load the syno os.

this can be a reference https://github.com/uxora-com/xpenology-docker

just like that.. actually, i run it under docker container on my NAS hardware. docker container on debian os running KVM to load xpenology. file system not known i think it's missing the driver to be loaded on the boot process.

i attach the result log when first boot.. maybe someone here can help me to solve this issue.. docker-xpe run fail.txt docker-xpe run.txt

why the file system not known at first boot ? it's on v7.2.0-64570 xpe1 | LoadingLoadin gLinux... Linux.. .pe1 | xpe1 | LoadingLoadin ginitramfs... initramfs.. .pe1 | xpe1 | error: unknown filesystem. error: unknown filesystemStarting. xpe1 | Startin gkernel kerne lwith wit hUSB US Bboot boo xpe1 | Press any key to continue...t xpe1 | xpe1 | Press any key to continue... [ 0.000000] Initializing cgroup subsys cpuset xpe1 | [ 0.000000] Initializing cgroup subsys cpu xpe1 | [ 0.000000] Initializing cgroup subsys cpuacct xpe1 | [ 0.000000] Linux version 4.4.302+ (root@build8) (gcc version 12.2.0 (GCC) ) #64570 SMP Sat Jun 3 00:10:35 C3 xpe1 | [ 0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3622xs+ console=ttyS0,115p xpe1 | [ 0.000000] KERNEL supported cpus: xpe1 | [ 0.000000] Intel GenuineIntel xpe1 | [ 0.000000] x86/fpu: Legacy x87 FPU detected. xpe1 | [ 0.000000] e820: BIOS-provided physical RAM map: xpe1 | [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable xpe1 | [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved xpe1 | [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved xpe1 | [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdbfff] usable xpe1 | [ 0.000000] BIOS-e820: [mem 0x000000003ffdc000-0x000000003fffffff] reserved xpe1 | [ 0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved xpe1 | [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved xpe1 | [ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved xpe1 | [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved xpe1 | [ 0.000000] earlycon: Early serial console at I/O port 0x3f8 (options '115200n8') xpe1 | [ 0.000000] bootconsole [uart0] enabled xpe1 | [ 0.000000] NX (Execute Disable) protection: active xpe1 | [ 0.000000] SMBIOS 2.8 present. xpe1 | [ 0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 xpe1 | [ 0.000000] Kernel/User page tables isolation: disabled xpe1 | [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved xpe1 | [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable xpe1 | [ 0.000000] e820: last_pfn = 0x3ffdc max_arch_pfn = 0x400000000 xpe1 | [ 0.000000] MTRR default type: write-back xpe1 | [ 0.000000] MTRR fixed ranges enabled: xpe1 | [ 0.000000] 00000-9FFFF write-back and ends up with kernel panic xpe1 | [ 0.592682] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 xpe1 | [ 0.592682] xpe1 | [ 0.593626] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 xpe1 | [ 0.593626] while on 7.1.0-42661 the boot process is okay.. xpe | xpe | Loadin gLinux... Linux.. .pe | xpe | LoadingLoadin ginitramfs... initramfs.. .pe | xpe | StartingStartin gkernel kerne lwith wit hUSB US Bboot boo [ 0.000000] Initializing cgroup subsys cpuset xpe | [ 0.000000] Initializing cgroup subsys cpu xpe | [ 0.000000] Initializing cgroup subsys cpuacct xpe | [ 0.000000] Linux version 3.10.108 (root@build13) (gcc version 8.5.0 (GCC) ) #42661 SMP Fri Apr 1 15:31:15 CS2 xpe | [ 0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3615xs console=ttyS0,115201 xpe | [ 0.000000] KERNEL supported cpus: xpe | [ 0.000000] Intel GenuineIntel xpe | [ 0.000000] e820: BIOS-provided physical RAM map: xpe | [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable xpe | [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved xpe | [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved xpe | [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdbfff] usable xpe | [ 0.000000] BIOS-e820: [mem 0x000000003ffdc000-0x000000003fffffff] reserved xpe | [ 0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved xpe | [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved xpe | [ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved xpe | [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved xpe | [ 0.000000] Early serial console at I/O port 0x3f8 (options '115200n') xpe | [ 0.000000] bootconsole [uart0] enabled

then what should i do next ? rebuild the loader again ? does the /mnt/sda3/grub72.cfg file has default grub boot option to SATA ? or do u mean, i need to edit the grub72.cfg file and change the default boot option ? sorry, i still not understand..

After tring to put inside docker vm script, the bootloader which was built by m-shell can start, but wrong choose default boot option. it should be SATA not USB as the default grub boot menu. It was an error unknown file system after that. How to change this ? @Peter Suh

how to try it ? download latest modified rploader.sh from your github then sftp to /home/tc ?

can i just remark part of rploader.sh which become something like this ? #if [ "$MAKEIMG" = "YES" ]; then echo "Stop creating loader and keep loader.img for 7.2" sudo cp -vf loader.img /mnt/${loaderdisk}3/loader72.img echo "Cleaning up files" removemodelexts sudo rm -rf /home/tc/cache/*pat /home/tc/redpill-load/loader.img exit 0 #fi

ok.. then no need to add 9p drivers on /home/tc rpext.json file.. will try it after this build success with loader72.img file.. zlastbuild.log

Hi, i tried build 7.1.1 loader, but still not found loader72.img file.. and about virtio 9p drivers, i tried to edit & add rpext json file from /home/tc with the content from your tcrp-addons/9p/rpext-index.json. does it means, the build process will include these driver ? @Peter Suhzlastbuild.log

yes i run this one.. but error no space left on device..