Jump to content
XPEnology Community

alirz1

Member
  • Posts

    194
  • Joined

  • Last visited

Everything posted by alirz1

  1. 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.
  2. 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.
  3. 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!
  4. 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?
  5. 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"
  6. 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.
  7. 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 but flashing the usb drive is not possible at the moment. thanks
  8. 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
  9. 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?
  10. 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?
  11. 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.
  12. Does TCRP support U4 or you simply update and just run the postupgrade for 42962?
  13. 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?
  14. I believe this failure happens when your usb drive's PID/VID are not set correctly. Also verify sata and disk map values.
  15. So M shell is a menu driven add on for tcrp or something like ARPL
  16. 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.
  17. 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.
  18. Yeh i found that out that theres a hard limit in dsm for number of cores etc per synology model. Kind of sucks.
  19. 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
  20. 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?
  21. 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?
  22. can the cpu be upgraded without a rebuild? I’m just looking to change my cpu from Intel i3 8100 to i7 8700. Both are 8th gen cpus. Is a simple swap enough or a rebuild of loader etc will be needed?
×
×
  • Create New...