RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

2 hours ago, Kaneske said:

Am I too stupid or foolish...

 

Why does the Built say:

 

[!] Failed to copy /home/xxx/Desktop/redpill-load-master/ext/rp-lkm/redpill-linux-v3.10.108.ko to /home/koljawenske/Desktop/redpill-load-master/build/1629220385/rd-ds3615xs_41222-unpacked/usr/lib/modules/rp.ko

/usr/bin/cp: cannot stat '/home/xxx/Desktop/redpill-load-master/ext/rp-lkm/redpill-linux-v3.10.108.ko': No such file or directory

*** Process will exit ***
 

Did you do step #2 form the redpill-load instructions?

https://github.com/jumkey/redpill-load:

Quote

Compile RedPill LKM and place it in ext/rp-lkm/redpill-linux-<VERSION>.ko (see platform config for details)

 

  • Like 1
Link to post
Share on other sites

@gadreel@scoobdriver@cwiggs@loomes Regarding that mystery bug with execve() shim causing kernel panic - can you check again with the newest version? We may have possibly found a solution.

 

6 hours ago, ilovepancakes said:

 

No, output in Grub seems normal, despite reverting to USB option each time I boot. See below. For what it's worth, after installing DSM, using the USB boot entry does indeed boot DSM, with the only side effect being the loader VMDK shows up in Storage Manager as Disk 1. If I use SATA boot option, loader doesn't show up in DSM at all and the first data VMDK shows up as Disk 2 in Storage Manager.

 

5 hours ago, scoobdriver said:

(The Sata boot option was not remembered when the machine rebooted after uploading the .pat file)

In the previous versions we've missed save call for 3615 (whoops!) but the newest release should save it. Can you confirm it's still not working?

 

  • Thanks 1
Link to post
Share on other sites
Spoiler

Aug 17 22:17:26 synocodesign: BLAKE2b-256 (ha_dummy_ocf/PromoteBegin) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Aug 17 22:17:26 synocodesign: ha_dummy_ocf/PromoteBegin: OK
Aug 17 22:17:26 synocodesign: BLAKE2b-256 (synohamessaged-update) = ce9ca8d7e0fc492f73218a297ad0f6769acd7bdc597e5568644df55927d347b9
Aug 17 22:17:26 synocodesign: synohamessaged-update: OK
Aug 17 22:17:26 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat...
Aug 17 22:17:26 install.cgi: Verify checksum of [/tmpData/upd@te]...
Aug 17 22:17:27 install.cgi: Pass checksum of /tmpData/upd@te...
Aug 17 22:17:27 updater: updater.c:6751 Start of the updater...
Aug 17 22:17:27 updater: updater.c:3211 orgBuildNumber = 41890, newBuildNumber=41890
Aug 17 22:17:27 updater: util/updater_util.cpp:86 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Aug 17 22:17:27 updater: updater.c:7029 ==== Start flash update ====
Aug 17 22:17:27 updater: updater.c:7033 This is X86 platform
Aug 17 22:17:27 kernel: [  162.861105] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 kernel: [  162.864426] synoboot2 unmounted, process=updater
Aug 17 22:17:27 kernel: [  162.873126] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 kernel: [  162.875378] synoboot2 unmounted, process=updater
Aug 17 22:17:27 kernel: [  162.885159] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 kernel: [  162.888309] synoboot2 unmounted, process=updater
Aug 17 22:17:27 updater: updater.c:7049 The SynoBoot partitions exist.
Aug 17 22:17:27 updater: updater.c:4056 SYNORedBootUpdCheckAndApply(4056): Skip bootloader update, no uboot_do_upd.sh exists
Aug 17 22:17:27 kernel: [  162.897682] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 updater: updater.c:539 fail to backup images. cp -f /tmp/bootmnt/zImage /tmpData/synob@ckup
Aug 17 22:17:27 updater: updater.c:607 checksum generated by [/bin/grep -i zImage checksum.syno >> /tmp/checksum.syno.tmp]
Aug 17 22:17:27 updater: updater.c:636 file [zImage] is being copied to [/tmp/bootmnt]
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/zImage] process done.
Aug 17 22:17:27 updater: updater.c:607 checksum generated by [/bin/grep -i rd.gz checksum.syno >> /tmp/checksum.syno.tmp]
Aug 17 22:17:27 updater: updater.c:636 file [rd.gz] is being copied to [/tmp/bootmnt]
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/rd.gz] process done.
Aug 17 22:17:27 updater: updater.c:607 checksum generated by [/bin/grep -i grub_cksum.syno checksum.syno >> /tmp/checksum.syno.tmp]
Aug 17 22:17:27 updater: updater.c:636 file [grub_cksum.syno] is being copied to [/tmp/bootmnt]
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/grub_cksum.syno] process done.
Aug 17 22:17:27 updater: updater.c:627 file [/tmp/bootmnt/hda1.tgz] is being removed
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/hda1.tgz] process done.
Aug 17 22:17:27 updater: updater.c:627 file [/tmp/bootmnt/updater] is being removed
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/updater] process done.
Aug 17 22:17:27 updater: updater.c:627 file [/tmp/bootmnt/VERSION] is being removed
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/VERSION] process done.
Aug 17 22:17:27 updater: updater.c:654 checksum file updated by [/bin/cp -f /tmp/checksum.syno.tmp /tmp/bootmnt/checksum.syno]
Aug 17 22:17:27 kernel: [  163.326742] synoboot2 unmounted, process=updater
Aug 17 22:17:32 kernel: [  168.338105] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:33 kernel: [  168.389988] synoboot2 unmounted, process=updater
Aug 17 22:17:33 kernel: [  168.400498] ext2: synoboot1 mounted, process=updater
Aug 17 22:17:33 kernel: [  168.401868] vfat: synoboot1 mounted, process=updater
Aug 17 22:17:33 updater: updater.c:913 open /tmp/bootmnt/EFI/boot//SynoBootLoader.conf failed
Aug 17 22:17:33 updater: updater.c:968 This model does not contain KPTI config and skip conversion
Aug 17 22:17:33 updater: updater.c:1177 Failed to update KPTI config
Aug 17 22:17:33 updater: updater.c:6557 failed to update factory partition, retry 0

@ThorGroup

I do not see the error anymore. Your fix did work for me but during installation it does not post any message that it failed. It will stuck at 99% with the error log I am posting that opening SynoBootLoader.conf failed and failed to update KPTI config. (Apollolake 7.0)

 

EDIT2:

I tried with Apollolake 6.2.4 and it was a success.

 

EDIT3:

I tried with Bromolow 7.0.41222, it was a success.

Edited by gadreel
Tried with Apollolake 6.2.4-25556
Link to post
Share on other sites
5 hours ago, gadreel said:
  ApolloLake 7.0 Error Log (Reveal hidden contents)

Aug 17 22:17:26 synocodesign: BLAKE2b-256 (ha_dummy_ocf/PromoteBegin) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Aug 17 22:17:26 synocodesign: ha_dummy_ocf/PromoteBegin: OK
Aug 17 22:17:26 synocodesign: BLAKE2b-256 (synohamessaged-update) = ce9ca8d7e0fc492f73218a297ad0f6769acd7bdc597e5568644df55927d347b9
Aug 17 22:17:26 synocodesign: synohamessaged-update: OK
Aug 17 22:17:26 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat...
Aug 17 22:17:26 install.cgi: Verify checksum of [/tmpData/upd@te]...
Aug 17 22:17:27 install.cgi: Pass checksum of /tmpData/upd@te...
Aug 17 22:17:27 updater: updater.c:6751 Start of the updater...
Aug 17 22:17:27 updater: updater.c:3211 orgBuildNumber = 41890, newBuildNumber=41890
Aug 17 22:17:27 updater: util/updater_util.cpp:86 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Aug 17 22:17:27 updater: updater.c:7029 ==== Start flash update ====
Aug 17 22:17:27 updater: updater.c:7033 This is X86 platform
Aug 17 22:17:27 kernel: [  162.861105] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 kernel: [  162.864426] synoboot2 unmounted, process=updater
Aug 17 22:17:27 kernel: [  162.873126] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 kernel: [  162.875378] synoboot2 unmounted, process=updater
Aug 17 22:17:27 kernel: [  162.885159] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 kernel: [  162.888309] synoboot2 unmounted, process=updater
Aug 17 22:17:27 updater: updater.c:7049 The SynoBoot partitions exist.
Aug 17 22:17:27 updater: updater.c:4056 SYNORedBootUpdCheckAndApply(4056): Skip bootloader update, no uboot_do_upd.sh exists
Aug 17 22:17:27 kernel: [  162.897682] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:27 updater: updater.c:539 fail to backup images. cp -f /tmp/bootmnt/zImage /tmpData/synob@ckup
Aug 17 22:17:27 updater: updater.c:607 checksum generated by [/bin/grep -i zImage checksum.syno >> /tmp/checksum.syno.tmp]
Aug 17 22:17:27 updater: updater.c:636 file [zImage] is being copied to [/tmp/bootmnt]
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/zImage] process done.
Aug 17 22:17:27 updater: updater.c:607 checksum generated by [/bin/grep -i rd.gz checksum.syno >> /tmp/checksum.syno.tmp]
Aug 17 22:17:27 updater: updater.c:636 file [rd.gz] is being copied to [/tmp/bootmnt]
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/rd.gz] process done.
Aug 17 22:17:27 updater: updater.c:607 checksum generated by [/bin/grep -i grub_cksum.syno checksum.syno >> /tmp/checksum.syno.tmp]
Aug 17 22:17:27 updater: updater.c:636 file [grub_cksum.syno] is being copied to [/tmp/bootmnt]
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/grub_cksum.syno] process done.
Aug 17 22:17:27 updater: updater.c:627 file [/tmp/bootmnt/hda1.tgz] is being removed
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/hda1.tgz] process done.
Aug 17 22:17:27 updater: updater.c:627 file [/tmp/bootmnt/updater] is being removed
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/updater] process done.
Aug 17 22:17:27 updater: updater.c:627 file [/tmp/bootmnt/VERSION] is being removed
Aug 17 22:17:27 updater: updater.c:644 file [/tmp/bootmnt/VERSION] process done.
Aug 17 22:17:27 updater: updater.c:654 checksum file updated by [/bin/cp -f /tmp/checksum.syno.tmp /tmp/bootmnt/checksum.syno]
Aug 17 22:17:27 kernel: [  163.326742] synoboot2 unmounted, process=updater
Aug 17 22:17:32 kernel: [  168.338105] ext2: synoboot2 mounted, process=updater
Aug 17 22:17:33 kernel: [  168.389988] synoboot2 unmounted, process=updater
Aug 17 22:17:33 kernel: [  168.400498] ext2: synoboot1 mounted, process=updater
Aug 17 22:17:33 kernel: [  168.401868] vfat: synoboot1 mounted, process=updater
Aug 17 22:17:33 updater: updater.c:913 open /tmp/bootmnt/EFI/boot//SynoBootLoader.conf failed
Aug 17 22:17:33 updater: updater.c:968 This model does not contain KPTI config and skip conversion
Aug 17 22:17:33 updater: updater.c:1177 Failed to update KPTI config
Aug 17 22:17:33 updater: updater.c:6557 failed to update factory partition, retry 0

@ThorGroup

I do not see the error anymore. Your fix did work for me but during installation it does not post any message that it failed. It will stuck at 99% with the error log I am posting that opening SynoBootLoader.conf failed and failed to update KPTI config. (Apollolake 7.0)

 

EDIT2:

I tried with Apollolake 6.2.4 and it was a success.

 

EDIT3:

I tried with Bromolow 7.0.41222, it was a success.

i tried this boot in phycis machine ,using j1900 cpu ,it can success booting ,but i can't find ip address ! my motherborde Gigabit Ethernet is intel i211,i think this boot can't drive my drive,how to add drivers to this booting img?

  • Confused 1
Link to post
Share on other sites
1 hour ago, Julio0825 said:

i tried this boot in phycis machine ,using j1900 cpu ,it can success booting ,but i can't find ip address ! my motherborde Gigabit Ethernet is intel i211,i think this boot can't drive my drive,how to add drivers to this booting img?

 

Right now the redpill loader is not ready for baremetal and is still under development. Their are people that successfully installed it on Baremetal configuration but, ThorGroup has to implement/support more drivers for your i211 to work like Jun's Loader... You have to wait for the time being. :

Link to post
Share on other sites

I think barematel is not the best option for xpenology.

virtualization is very mature and safe enough to be used in production environment.  And it will create a lot less trouble when further development is required to support later version of DSM.  Yet the perfomance loss is very little.

 

Link to post
Share on other sites
7 hours ago, scoobdriver said:

I’m seeing the same issue still I’m afraid.  Esxi 6.7 ds3615xs 


apologies. My mistake. (Reused a cp command , and copied wrong .img) commit dffcf01 has resolved the boot issue with my esxi 6.7 

great work !

To note: it does not let me create a storage pool/volume , 

the boot loader does not remember sata boot option after the machine has built. 

 

Link to post
Share on other sites

Hello together!

 

I have never read such a good thread ever before!! Absolutely awesome!

Thanks to @ThorGroup, @haydibe, @flyride, @mcdull and all other I forgot for the very good information!

 

I am very busy at work so I can't work much in here but I read a lot.

 

I have spin up an Ubuntu 20.04 VM via Vagrant under VMware Workstation (under Windows) and was able to build with the help of the docker from @haydibe in a few minutes the loader (Apollolake, 6.2.4 and 7.0). (Testing of the loaders are note done yet due to lack of time).

 

If anyone is interested in a "Vagrant how to", leave a short note: I have documented everything and can post it here. :-)

 

 

  • Like 1
  • Thanks 1
Link to post
Share on other sites
1 hour ago, mcdull said:

I think barematel is not the best option for xpenology.

virtualization is very mature and safe enough to be used in production environment.  And it will create a lot less trouble when further development is required to support later version of DSM.  Yet the perfomance loss is very little.

 

I'm using barematel for plex hardware transcoding. Is this possible using virtualization?

Link to post
Share on other sites
19 minutes ago, BlaBla1973 said:

I'm using barematel for plex hardware transcoding. Is this possible using virtualization?

i guess yes.

 

For example, I'm using Unraid with i915 driver, so I can easily pass /dev/dri./card128 device to the VM.

  • Thanks 1
Link to post
Share on other sites
24 minutes ago, BlaBla1973 said:

I'm using barematel for plex hardware transcoding. Is this possible using virtualization?

yes. in any case you can passthorugh the GPU to the vm, even signle GPU environment is fine.

Although it is much easier if you have an extra display adaptor to share to the VM.

 

Intel may also support GPU sharing under some cirumstances.  But these setting may cost you weeks of time to set up the host.

For simple passthrough under proxmox or ESXi with compatible hardware, it should not be much difficult than running loader in this thread. 

  • Thanks 2
Link to post
Share on other sites
11 minutes ago, mcdull said:

yes. in any case you can passthorugh the GPU to the vm, even signle GPU environment is fine.


tbh, for normal home user appliance...i dont see the added value of esx. 
i have now baremetal with WOL and a safenet shutdown time in case i forget to power it off.

 

nvidia shield is fully capable to decode whatever is throw at it so i like the keep it simple approach :-)

Link to post
Share on other sites

use right  3615 sn bug get errors

synocodectool: G1Licence.cpp:79 Licence not Success,error msg "SN format is wrong."

synocodectool: SYNOCodecPatentG1.cpp:236 ValidateG1Licence failed

Failed to convert video [/volume1/photo/test/IMG_4444.MOV] to h.264 mp4

failed to use photo codecs

Link to post
Share on other sites
1 hour ago, renyi said:

use right  3615 sn bug get errors

synocodectool: G1Licence.cpp:79 Licence not Success,error msg "SN format is wrong."

synocodectool: SYNOCodecPatentG1.cpp:236 ValidateG1Licence failed

Failed to convert video [/volume1/photo/test/IMG_4444.MOV] to h.264 mp4

failed to use photo codecs

It seems your SN was wrong.
As far i remember 3615 doesn't have hardware transcoding capabilities 

Link to post
Share on other sites
2 minutes ago, mcdull said:

@haydibe where should  I put my custom user_config.json ?

Thanks.

redpill-tool-chain_x86_64_v0.5.3/docker/user_config.json.template

it will be pushed to the docker when doing the build if i am not mistaken. at least, it seems that it is reflected into my *.img after doing the build_all

Link to post
Share on other sites

interesting, I managed to run fine after reinstall the docker-ce.  But after I changed the json and do it again, I hit error again.

Even I removed the json and run again, its still the same.

 

oo... https://github.com/jumkey/redpill-load.git -b 7.0-41890  This is really missing from source. 

 

 => ERROR [stage-1 3/9] RUN git clone https://github.com/RedPill-TTG/redpill-lkm.git  -b master  /opt/redpill-lkm &&     git clone https://github.com/jumk  2.9s
------
 > [stage-1 3/9] RUN git clone https://github.com/RedPill-TTG/redpill-lkm.git  -b master  /opt/redpill-lkm &&     git clone https://github.com/jumkey/redpill-load.git -b 7.0-41890 /opt/redpill-load:
#6 0.551 Cloning into '/opt/redpill-lkm'...
#6 1.755 Cloning into '/opt/redpill-load'...
#6 2.594 fatal: Remote branch 7.0-41890 not found in upstream origin
------
executor failed running [/bin/sh -c git clone ${REDPILL_LKM_REPO}  -b ${REDPILL_LKM_BRANCH}  ${REDPILL_LKM_SRC} &&     git clone ${REDPILL_LOAD_REPO} -b ${REDPILL_LOAD_BRANCH} ${REDPILL_LOAD_SRC}]: exit code: 128

 

Edited by mcdull
Link to post
Share on other sites
11 hours ago, Julio0825 said:

i tried this boot in phycis machine ,using j1900 cpu ,it can success booting ,but i can't find ip address ! my motherborde Gigabit Ethernet is intel i211,i think this boot can't drive my drive,how to add drivers to this booting img?

Thinks answer me,i understand ,i will continue noticing this porjet

Link to post
Share on other sites
3 minutes ago, hoangminh88 said:

Can you create a tutorial for J1900 nas?

i want it to,i have try the physic booting in my j1900,the network card can't be drive,but some model of network card can be drive,if you want to install in physic machine,you must try by yourself.if you use the pve,the author's bootloader can successful install dsm and most of the function are working normaly.  if you want to install in physic machine ,there are some issue known.so just waiting for some time,the author and the group are Improving.

  • Like 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.