alirz1
-
Posts
195 -
Joined
-
Last visited
Posts posted by alirz1
-
-
27 minutes ago, Peter Suh said:
Didn't think you could use ipmi remotely so you couldn't see the monitor.
The my.sh command doesn't help.
After ssh connection, please execute ./menu.sh instead.well as i said im testing on a local VM right now anyways. But for my remote box i do have full display,keyboard and mouse control remotely.
So for running "my.sh". Whatever that script does, it did start the build process and successfully built dsm 7.2 for my vm. I can re-try using the menu.sh.
-
1
-
-
so i started of in tcrp. where the DSM 7.2 build failed.
I ran your curl command, it downloaded stuff and then rebooted. At the boot menu, i went to select "tiny core rebuild". That booted like regular tcrp and took me to the TCRP gui where there two consoles open. one sitting at the tc# prompt and the other that is displaying system info like, IP, cpu info etc.
No other windows popped up.
I connected via ssh and saw additional files from your download in the /home/tc folder. Where i ran the my.sh script. This was still all text based and no gui.
I know tcrp 0.9.4.9c, if i download from poccpico's github and burn that to a usb and boot off that. That one does have a web interface where your build via the gui. I assume thats not the same GUI you are talking about.
-
i actually did try your suggestion. i had to manually run my.sh after the reboot to build the loader.. It did work.
"Your offer" Sounds like a Mafia boss offering me something and if i dont accept, off with my head!
-
1
-
-
7 minutes ago, Peter Suh said:
Even now, if you can process the rploader.sh command through ipmi, you can switch from pocopico's TCRP to my M SHELL for TCRP.
Execute the following command.curl -kLO https://raw.githubusercontent.com/PeterSuh-Q3/tinycore-redpill/master/my.sh.gz; tar -zxvf my.sh.gz ; ./rploader.sh backup; sudo rebootAfter rebooting, if you enter the TCRP loader build again, A menu-driven loader build like ARPL will be provided.
right now im just testing in a vm environment not on my PROD remote system.
I relauze that during "tcrp fullgrade" it had given error:
"chmod: changing permissions of '/home/tc/redpill-load/custom/extensions/pocopico.e1000/ds918p_42962/check-e1000.sh': Operation not permitted
chmod: changing permissions of '/home/tc/redpill-load/custom/extensions/boot-wait/ds918p_42962/boot-wait.sh': Operation not permit "Could that be causing the error related to e1000 during the build process?
PS. Does tc 0.9.4.9 not have the GUI based buildinterface as 0.9.4.9C?
-
testing a VM 7.2 build with tcrp 0.9.4.9 but its failing with this error:
[#] Extension misc for ds918p_64570 platform is already up to date
[-] The extension pocopico.e1000 was found. However, the extension index has no recipe for ds918p_64570 platform. It may not be
[-] supported on that platform, or author didn't updated it for that platform yet. You can try running
[-] "ext-manager.sh update" to refresh indexes for all extensions manually. Below are the currently known information about
[-] the extension stored locally:
[#] ========================================== pocopico.e1000 ==========================================
i the .vmx file of the vm does have that ethernet listed as: ethernet0.virtualDev = "e1000"
-
21 hours ago, Peter Suh said:
If you can control the grub boot menu sequence with ipmi remote access and even control the TC linux kernel console,
it is recommended to rebuild the bootloader for DSM 7.2.
After rebooting, you will be asked to install the pat file for DSM 7.2.
Just proceed with the installation as requested.
one thing that confuses me that during build process, TC will download the selected DSM version e.g it'll download "7.1.1 DSM_DS918+ 42962.pat". But it wont say which build/update version is this PAT. So once the build is done and im at the DSM installation/migration GUI and have to select or download a dsm pat how do i know which UPDATE/BUILD of 7.1.1 i need to provide? i've been going at this for a and tried providing different pat files of the same 7.1.1 but my installation hangs at 99% everytime.
-
On 5/30/2023 at 6:40 PM, ed_co said:
TCRP difficult update procedure:
* Manually install 7.2
* reboot, wait for "synology is recoverable"
* Shutdown
* Rebuild usb key with TCRP 0.9.4.6 (I guess meaning of latest version)
* ./rploader.sh update now
* ./rploader.sh fullupgrade now
* ./rploader.sh serialgen DS918+ realmac
* ./rploader.sh identifyusb now
* ./rploader.sh satamap now
* ./rploader.sh backup
* ./rploader.sh build ds918p-7.2.0-64561 withfriend
* ./rploader.sh backup
* exitcheck.sh rebootBased on Ozef update comments here:
If someone has any comment, correction or whatever, please let me know.
Three more procedures to go (or just one if the easy update procedure is trivial).
Thankshow to do an in place upgrade of tcrp without having to flash the usb drive with a new tcrp.img file? is this possible?
I want to update my tcrp from 0.9.4.0 to the latest 0.9.4.9c but flashing the usb drive is not possible at the moment. thanks
-
how to do an in place upgrade of tcrp without having to flash the usb drive with a new tcrp.img file? is this possible?
I want to update my tcrp from 0.9.4.0 to the latest 0.9.4.9c
-
2 hours ago, Peter Suh said:
If you can control the grub boot menu sequence with ipmi remote access and even control the TC linux kernel console,
it is recommended to rebuild the bootloader for DSM 7.2.
After rebooting, you will be asked to install the pat file for DSM 7.2.
Just proceed with the installation as requested.
So I can update the bootloader via command line right? I don’t need to burn a new tcrp image to the usb flash drive that is connected to my bare metal?
that’s the only think I don’t how can do remotely but other than that yes I have full keyboard display from the xpenology box via a connected pikvm.
would loader rebuild and dsm install/migrate to 7.2 carry over my current dsm 7.1 configs and apps etc?
-
Currently on baremetal 7.1, using tcrp .9.4.0.
Now looking to update to dsm 7.2 and with that to the new tcrp. My xpenology box is remote and I have ipmi access to it. Anyway I can update the USB stick to the latest tcrp? Does the loader update command do that Or a new .img burn is required?
While doing this remotely is a bit risky I think with ipmi access I should be mostly ok. This time around I'm probably also going to use the "with friend" option which seems to be on by default on the latest tcrp, is that correct?
-
Delete
-
Short version: Is is possible to set display resolution when booting tinycore?
Long version: I have just got a Pikvm v4 connected to my xpenelogy for remote management etc. the kvm shows the video connection etc is all good however i dont get display int he kvm window. After some discussions with the pikvm folks, we think it could be display resolution related(The kvm windows shows me inacive display with a 640x480 resolution)Though that doesnt explain why i donte even see the POST display for the xpenology but anyways i would like to see if its its possible to set the display resolution for when TC boots up.
-
On 2/12/2023 at 4:03 AM, loveburn said:
success update to U4 from U3 !
Does TCRP support U4 or you simply update and just run the postupgrade for 42962?
-
Anyone here tried those sata port multipliers I,e those that plug into a nvme slot to give you regular 5-6 sata ports? I’m wondering how would it be detected by the tcrp loader?
-
3 hours ago, sbromulo said:
Hello guys.
I have a problem with the my.sh script.
The script goes OK with the build DSM3622-42962
I do a reboot and the base system boots ok.
The base system ask for the DSM 42962 pat file. I select the file and click next, but always I got the error below attached.
Anyone has a solution for that?
I tried another builds and i gave same error.
I believe this failure happens when your usb drive's PID/VID are not set correctly. Also verify sata and disk map values.
-
So M shell is a menu driven add on for tcrp or something like ARPL
-
1
-
-
On 3/4/2022 at 3:41 PM, ryancc said:
So I migrated my xpenology server from DS918+ model to DS3622xs, and the nvme cache no longer works since the model number no longer exist in libsynonvme.so.1. I dig into the libsynonvme.so.1 and found it might check your pcie location to have the nvme drive works properly. After inspect the file, I found it just checks /etc.defaults/.extensionPorts and we just need to modify that.
Here are the steps:
1. Check your nvme pci location(in my case it's 0000:00:01.0😞
udevadm info /dev/nvme0n1
P: /devices/pci0000:00/0000:00:01.0/0000:01:00.0/nvme/nvme0/nvme0n1
2. Modify /etc.defaults/.extensionPorts to have the port number match your nvme location.
cat /etc.defaults/extensionPorts
[pci]
pci1="0000:00:01.0"
3. I did not even restart and the nvme cache drive already appears. Hope this helps anyone who is looking to solve this.
Update:
If you worry a system update will revert this modification, just add a startup script with root:
sed -i 's/03.2/[your_pci_last_three_digs]/g' /etc.defaults/extensionPorts
In this way, no matter what version you goes, this will always stay.
Can you have a cache drive in DS918+?
-
19 hours ago, gericb said:
I'm still at a loss to understand why Plex software itself, if it can be install on a Synology/QNAP/Unraid etc. or with the aid of some add-on software, can't directly take advantage of the Intel QuickSync instruction set. Having a platform functionality deficient in this way, is astonishing and ludicrous, it should be platform agnostic. I'm sure there are folks that have more content, than a 918/920 can cost effectively hold, so something like a 3622 with HW transcoding would make total sense. Having said that, this would imply such a possibility given that the 3615/3617 aren't intended to HW transcode, but yet, this seems to makes it possible. Soooo, maybe it could work on 3622. 🤠
I had previously tried that synocodec tool with no luck for whatever reason. I think the issues related to HW transcoding are more from Synology rather than Plex itself.
-
18 hours ago, gericb said:
I have the exact same CPU. I'm sure that FOXBI's Info Center CPU modifier will show the correct Intel info, but yes, sadly, why I don't know...it does seem that Synology has a hard limit on Cores/Threads. Seems like a totally useless thing to do, never found a worthy explanation for it, but it is what it is. You can see the current reflected support with DSM 7:
So if DSM is hard limited, makes it kind of pointless to get extra beefy CPU, unless you are going to build a model that supports those Cores/Threads fully. Maybe future revisions will open these arbitrary limitations, to allow more horsepower to be used. Having said this, there are certainly additional benefits from many of the newer generation CPU's and just because all of the Cores/Threads aren't always being used, you'll have motherboards with faster chipsets, memory bandwidth, more SATA ports, NVMe storage options, etc. etc. so it's not all bad just because the CPU doesn't get utilized fully.
Yeh i was using a 3622xs built on the old processor. But switched ot ds918 for Plex's HW decoding but im realizing this cpu limit with the new processor. Cant even go back to ds3622 as that doesnt support HW decoding.
-
11 hours ago, FOXBI said:
I think it's probably a DS920+ or DS918+ that only supports up to 8 cores if your DSM is 7.x or higher.
as you know ch_cpuinfo simply displays information from /proc/cpuinfo.
Currently, it seems that only up to 8 cores are recognized.
If you want to show all the cores you have, you will have to build and use it with a DSM that supports 16 cores or more.
I think the link below will help.
Yeh i found that out that theres a hard limit in dsm for number of cores etc per synology model. Kind of sucks.
-
On 1/17/2023 at 9:29 AM, Kaneske said:
Just swap it and you’re good to go.
i just replaced the cpu in my DS918+ baremetal setup to an Intel i7-8700. Its supposed to be 6 cores/12 hreads. However /proc/cpuninfo shows me 8 cpus(0-7).
When i ran the your tool to update info in DSM. DSM shows me 6 Cores (1 CPU/6 Cores | 8 Threads)
I bought the cpu fom ebay and it is a i7-8700.
So now im wondering if the the CPU is bad, not all its cores are working? or is it simply a Snology OS/DSM thing that its not showing me the right # of cpu/threads even in /proc/cpuinfo?
I did simply just swap out my cpu. Do i need to rebuild from tcrp lader again perhaps to get the new cpu detected properly?
EDIT: so reading up more on this. Seems like this is an old issue from Jun loaders days and there is some hard limit on # of cpus in Synology's linux kernel
-
i just replaced the cpu in my baremetal setup to an Intel i7-8700. Its supposed to be 6 cores/12 hreads. However /proc/cpuninfo shows me 8 cpus(0-7).
When i ran the your tool to update info in DSM. DSM shows me 6 Cores (1 CPU/6 Cores | 8 Threads)
I bought the cpu fom ebay and it is a i7-8700.
So now im wondering if the the CPU is bad, not all its cores are working? or is it simply a Snology OS/DSM thing that its not showing me the right # of cpu/threads even in /proc/cpuinfo?
I did simply just swap out my cpu. Do i need to rebuild from tcrp lader again perhaps to get the new cpu detected properly?
-
ds918, 7.1.1 42661 U1. Looking to update to 7.1.1 42962 U3.
I manually updated the DSM via GUI. Rebooted into tcrp 0.9.4. Ran full upgrade and post update command but it says version available is 42962 U2? Reluctantly i let it proceed with that. After my box seems to boot correctly. DSM info shows im at DSM 7.1.1-42962 Update 3
Should i be concerned that i ran tcrp and let its do it post update stuff for U2?
-
12 hours ago, Kaneske said:
Just swap it and you’re good to go.
Thanks
TinyCore RedPill Loader (TCRP)
in Loaders
Posted · Edited by alirz1
How come menu_m.sh, shows no values for sata map or disk ID? Does it detect it automatically? Does it need to be manually entered?
Also i notice that after the build, when i have to reboot, the default menu option is set to tinycore USB, even though im installing in a VM and would need to use the tiny core SATA boot option.
EDIT: This doesnt make any sense to me unfortunately. After the dsm 7.2 build was successful. After reboot, im back at my original dsm 7.1.1. No prompt by DSM to migrate/install etc... I think the problem is due to the fact it thinks im installing on a usb stick and a vm disk!
I think ill stick to the regular TCRP. It hasnt really failed me yet and this whole menu driven stuff is not really working for me. I rather configure everything manually so i know whats going on.
Heres the log if you want to see it. Thanks.