jj-lolo Posted March 24, 2022 Share #1 Posted March 24, 2022 I'm having issues with tinycore-redpill.v0.4.6 I've booted tiny core and ssh'd into the vm When I run /rploader.sh update now I see an update but get There is a newer version of the script on the repo should we use that ? [yY/nN]y OK, updating, please re-run after updating cp: cannot stat '/home/tc/latestrploader.sh': No such file or directory Updating tinycore loader with latest updates Backing up files to /mnt/sda3//mydata.tgz Done. I rerun it again and get the same error. I then continue with ./rploader.sh serialgen DS3615xs and ./rploader.sh satamap now and ./rploader.sh backup now but when I get to ./rploader.sh build bromolow-7.0.1-42218 I get the following tc@box:~$ ./rploader.sh build bromolow-7.0.1-42218 Loader source : https://github.com/jumkey/redpill-load.git Loader Branch : develop Redpill module source : https://github.com/RedPill-TTG/redpill-lkm.git : Redpill module branch : master Extensions : Extensions URL : TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download TOOLKIT_SHA : a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/bromolow-source/linux-3.10.x.txz/download SYNOKERNEL_SHA : 18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed COMPILE_METHOD : toolkit_dev TARGET_PLATFORM : bromolow TARGET_VERSION : 7.0.1 TARGET_REVISION : 42218 REDPILL_LKM_MAKE_TARGET : dev-v7 KERNEL_MAJOR : 3 MODULE_ALIAS_FILE= modules.alias.3.json Checking Internet Access -> OK Checking if a newer version exists on the repo -> gzip: modules.alias.3.json.gz: No such file or directory gzip: modules.alias.4.json.gz: No such file or directory sha256sum: latestrploader.sh: No such file or directory There is a newer version of the script on the repo should we use that ? [yY/nN]n Cloning into 'redpill-lkm'... fatal: unable to access 'https://github.com/RedPill-TTG/redpill-lkm.git/': SSL certificate problem: certificate is not yet valid Loader sources already downloaded, pulling latest fatal: not a git repository (or any of the parent directories): .git Using static compiled redpill extension Looking for redpill for : ds3615xs_42218 modinfo: module '/lib/modules/5.10.3-tinycore64/redpill.ko' not found cp: cannot stat '/home/tc/redpill.ko': No such file or directory Got redpill-linux-v.ko Testing modules.alias.3.json -> File OK ------------------------------------------------------------------------------------------------ It looks that you will need the following modules : Found IDE Controller : pciid 8086d00007111 Required Extension : No matching extension Found VGA Controller : pciid 15add00000405 Required Extension : No matching extension Found SATA Controller : pciid 15add000007e0 Required Extension : No matching extension Found SATA Controller : pciid 15add000007e0 Required Extension : No matching extension Found Ethernet Interface : pciid 8086d000010d3 Required Extension : e1000e.ko Searching for matching extension for e1000e.ko ------------------------------------------------------------------------------------------------ Starting loader creation Checking user_config.json : Done tar: /home/tc/bsdiff.txz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now mkdir: cannot create directory 'cache': Permission denied sudo: ./build-loader.sh: command not found FAILED : Loader creation failed check the output for any errors Any suggestions would be appreciated! Quote Link to comment Share on other sites More sharing options...
htanh034 Posted March 25, 2022 Share #2 Posted March 25, 2022 (edited) tc@box:~$ sudo su Did you run this command first ? Once you have successfully established an SSH connection, run the following commands: sudo su ./rploader.sh update now ./rploader.sh serialgen DS3615sx ./rploader.sh satamap bromolow-7.0.1-42218 ./rploader.sh backup now ./rploader.sh build bromolow-7.0.1-42218 auto poweroff Edited March 25, 2022 by htanh034 Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted May 13, 2022 Share #3 Posted May 13, 2022 run the date command in your ssh session and see what it's set to. my vm was set to 2015 for some reason so any https request would fail as the certificates aren't valid yet. i just ran ntpd -p north-america.pool.ntp.org -q to grab the correct time 1 Quote Link to comment Share on other sites More sharing options...
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.