Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

2 hours ago, Kaneske said:

Anyone updated a running instance of 7.0.1-42218-2 to new Version 7.0.1-42218-3 using the internal update process while running the System?

 

Thou outcome of this would be nice to know…

 

AM3 Athlon II 260u (1.8Ghz!) 3615xs system has updated from 7.0.1-42218-2 to -3 ok.

Gen7 microserver 3615xs has been operating 24/7 since September on 7.0.1 and also updated ok to -3.

* Both have NC360T nics installed and used as lan1 although tinycore installs appropriate drivers for the onboard nics, both are recognised in DSM and are usable.

* Both now using tinycore loader, Gen7 previously using the original thorgroup loader since August.

 

Installed 3622xs+ 7.0.1-42218 ok on the AM3 system to test but didn't update any further and reinstalled 3615xs, "all files and settings" option.

* The section under Control Panel/DSM Update/Status shows correctly on the 3615xs (your DSM version is up to date) but shows "unable to connect" on 3622xs+.

 

From the release notes for 7.1:

"For the following models, DSM 7.1 will be the last upgradable version: .....DS3615xs"

 

It will quarantine two of my real synos as well 😒

Link to comment
Share on other sites

33 minutes ago, altas said:

DSM Update seems to be broken, as i also get connection failed.. but i think is better to have it like this as DSM do an auto update and bricks.

 

Yes I don't mind this, I have set the update to manual anyway, I was just curious why this is coming up as connection error.

Link to comment
Share on other sites

On 1/29/2022 at 10:03 PM, scoobdriver said:

 

Just to update DS918+ build with full (GVTd rather than GVTg) IGD / IGPU passed through at pci slot 2 on Proxmox works and uses the gpu for Face recognition with a generated serial number . (don't need to use the patch to use CPU) 

 

I haven't been able to work out a way yet to to specify the slot the igpu is passed through on for ESXi , so the GPU is used for HW transcoding in things like plex , but not for face recognition .. 

 

(my integrated GPU is a 9th gen intel UHD 630 ) 

 

Hi, @scoobdriver!

I have just move from baremental to proxmox, i found the way to passthrough GVTg, but nowhere i can find GVTd. Help me please!

Edited by ducnhat1309
Link to comment
Share on other sites

11 hours ago, AbuMoosa said:

My internet connection is working, I have installed webstation and test website is also working, I can update my packages using package center, reverse proxies for subdomains are also working but why on the update check it says this??
image.thumb.png.bca948c5e1d5cf314e467c7baecddbfc.png
 

 

4 hours ago, altas said:

DSM Update seems to be broken, as i also get connection failed.. but i think is better to have it like this as DSM do an auto update and bricks.

 

 

DSM automatic update don´t work because redpill-load change/manipulate the urls and its good so.

You can see this in the config files:

"synoinfo": {
    ...
    "rss_server": "http://example.com/null.xml",
    "rss_server_ssl": "https://example.com/null.xml",
    "small_info_path": "https://example.com/null",
    "updateurl": "http://example.com/",
    "myds_region_api_base_url": "https://example.com"

 

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

1 hour ago, dodo-dk said:

 

 

DSM automatic update don´t work because redpill-load change/manipulate the urls and its good so.

You can see this in the config files:


"synoinfo": {
    ...
    "rss_server": "http://example.com/null.xml",
    "rss_server_ssl": "https://example.com/null.xml",
    "small_info_path": "https://example.com/null",
    "updateurl": "http://example.com/",
    "myds_region_api_base_url": "https://example.com"

 

 

ok thats good,

Link to comment
Share on other sites

On 3/1/2022 at 4:39 PM, synoxpe said:

OK so the serial port shows kernel panic before crashing and rebooting @IG-88 @Orphée @haydibe

I was running 0.4.4 DS918+ without any glitches since a week back. Then DSM started crashing spontaneously and now I see this:

Looks like you're running into the kernel panic issue we spent quite a while investigating last year:

https://github.com/RedPill-TTG/redpill-lkm/issues/21

 

The workaround I found was to boot with NMI watchdog disabled, then turn it on manually after booting.

  • Thanks 1
Link to comment
Share on other sites

On 2/22/2022 at 3:13 PM, Orphée said:

Hi All,

 

So I finally made the big jump.

 

I migrated my prod ESXi DS3615xs 6.2.3 jun's to ESXi DS3622xs+ 7.0.1 RP.

 

All went very smooth, all apps were migrated successfully, only those not available on DSM7 were "stopped/incompatible"

 

image.thumb.png.13925e7cd564cd21fd00219ddb1dd63b.png

 

All my shares are here, docker migrated without any manual action.

As I reminder i'm using a LSI HBA IT card to passthrough my 4x4Tb disks

 

image.png.86d38c6e7f8199c308458be0f01f1e28.png

All good exept disk starting in position 2 (strange behavior with LSI HBA passthrough)

 

All my SMART info are there :

image.thumb.png.06d3c4c993c996e33dd90a159a3f6874.png

 

Synology Moments migrated to Synology Photos and is currently indexing all photos.

 

A big thanks to @pocopico @yanjun @haydibe @IG-88 and all others I probably forget too.

 

tagging @scoobdriver for info ;)

Hey! I am trying to do something similar. Right now I took the vdmk and img file, created as an IDE drive but the VM doesn't start the boot loader. Are you able to explain how to attached the boot loader image to your VM?

Link to comment
Share on other sites

1 hour ago, WiteWulf said:

Looks like you're running into the kernel panic issue we spent quite a while investigating last year:

https://github.com/RedPill-TTG/redpill-lkm/issues/21

 

The workaround I found was to boot with NMI watchdog disabled, then turn it on manually after booting.

@WiteWulf thanks much for responding 🙏

I’m not using docker though but the issue linked above could be the cause. 
I just set ‘nmi_watchdog=0’ in user_config.json and rebuild? After booting ‘echo 1> /proc/sys/kernel/nmi_watchdog’?

 

Having said that, I upgraded to v0.4.5 builder and its running rock solid over the last 2 days with heavy data scrubbing and general use (even after the host Proxmox environment crashed after a few hours 😀)

has this issue been tackled in the latest version of the builder 0.4.5.x?

Link to comment
Share on other sites

I’ve ds918+ installed on Proxmox 7.1 running on 5 HDDs (as PCI pass through) with loader 0.4.5.
Due to frequent crashes in the Proxmox environment, mostly triggered by hardware related stuff (e.g plugging in a usb drive, NIC hardware hang etc) I want to move to ESXi.

Do I just rebuild the loader on ESXi 7 and  pass through the disks stated above? Or is there anything else that needs to be done?

Link to comment
Share on other sites

I would like ask about adding the extensions / drivers. 

 

example:

rploader.sh ext apollolake-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json

How I can add more "links with extension in one go" ?

I mean 

sudo ./rploader.sh build broadwellnk-7.0.1-42218 add https://github.com/pocopico/rp-ext/blob/main/e1000e/rpext-index.json AND https://github.com/pocopico/rp-ext/blob/main/e1000e/rpext-index.json

 

Please forgive my lack of knowledge, but I'm just getting started.

 

ok, I was able to install 3622xs on my VM. 

 

Edited by MajkelP
fixed one issue
Link to comment
Share on other sites

8 hours ago, ducnhat1309 said:

Hi, @scoobdriver!

I have just move from baremental to proxmox, i found the way to passthrough GVTg, but nowhere i can find GVTd. Help me please!


I’ll try and find my notes/old grub and configs . I have now moved to GVTg for now to split the gpu between 2 vms. (Redpill and windows) 

For gvtd I followed a guide , blacklisting i915 so the host did not use it , and adding some commands to the grub Cmd line of Proxmox 

I then followed this from @dreamtekcat to passthrough at 00:02

 

 

“In proxmox with a HD5xx or HD6xx IGPU passthrough,this question can be solved.
The problem is opengl(which syno used to accelerate the facedetect) only use a i915 device with addr 00:02,and the default addr of proxmox passthrogh is 00:10.
So you can manually edit it in args: -device vfio-pci,host=00:02.0,addr=0x02,x-igd-opregion=on in /etc/pve/qemu-server/10x.conf. And set the display hardware to none,avoiding the same 0x02 addr with i915.
Remenber the i915 driver blacklist in /etc/modprobe.d/blacklist.conf and vfio options in /etc/modprobe.d/vfio.conf must be done first.Or it will be a freeze on proxmox host,shutdown the autorun of DSM VM first before do above!”

 

I have since found I can pass through at 00:02 using gvtg using  -set device.hostpci0.addr=0x02 which allows we to split the igpu. 

 

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, Tibag said:

I see a bunch of you using Proxmox. As I am setting up a new machine I was going to go for esxi but is there any advantage to Proxmox vs esxi?

 

If you don't want to use linux command lines at all, go to ESXi. It is easier to manage disk / img upload and deployment with ESXi GUI.

If you don't fear command lines, ssh, etc... Proxmox VE is free and has a better serial port handling for our Xpenology needs. (Actually serial port from network/telnet access is not available without enterprise license on ESXi.)

 

Proxmox has some usefull features like Let's Encrypt certificates, MFA availability. I did not see it on ESXi.

 

It is my personnal experience with only one week of Proxmox usage.

Edited by Orphée
Link to comment
Share on other sites

6 hours ago, Orphée said:

 

If you don't want to use linux command lines at all, go to ESXi. It is easier to manage disk / img upload and deployment with ESXi GUI.

If you don't fear command lines, ssh, etc... Proxmox VE is free and has a better serial port handling for our Xpenology needs. (Actually serial port from network/telnet access is not available without enterprise license on ESXi.)

 

Proxmox has some usefull features like Let's Encrypt certificates, MFA availability. I did not see it on ESXi.

 

It is my personnal experience with only one week of Proxmox usage.


I don’t fear ssh at all and would love continuing to use Proxmox but its very unstable. Hence want to go to ESXi.
I also believe that the hardware pass through works better and more reliable there.

The serial port is just an output of dmesg right or am I missing something? If yes just a simple “dmesg -Tx —follow > $PATH/dmesg.log” should suffice in case the serial port isn’t available?

Link to comment
Share on other sites

9 hours ago, Amrit86 said:

I managed to downloaded the update from the Synology website and then did a manual DSM update and it took about 30 secs. On DSM 7.0.1-42218 Update 3 now. 

What did you do to go through and update to u3? It just reboots me to recover mode each time

Link to comment
Share on other sites

1 hour ago, Dvalin21 said:

What did you do to go through and update to u3? It just reboots me to recover mode each time

I didn’t do anything particularly special, just downloaded the update from the Synology website, clicked Manual DSM Update and uploaded the file. It warned me that it may take 20mins+ to install and then came back 30secs later. 
 

I should note that I’m using it on a bare metal install, a Dell OptiPlex 7040 SFF and I didn’t add any extra config, drivers or anything of the sort when I built v7.0.1 with RedPill. It just worked

  • Thanks 1
Link to comment
Share on other sites

@IG-88

Regarding transcoding in Plex, I've spent all day yesterday testing on three platforms.

DSM 7.01 u2 with automatically generated SN. DS918+.

Cpu Intel 8th gen. works oob.

Cpu Intel 10th gen not working.

Cpu Intel J5040  not working. (surprisingly  because is closest to 918+)

Same results with real SN.

All three platforms transcoding well on OMV.

On the only working platform (8th gen cpu) results are not good. While Video station was transcoding 4K HDR without problem, plex was struggling with the same file. Transcoding hw visible in dashboard of Plex. So, finally, the implementation of Quicksync  transcoding in Plex is not implemented very well. Comments on Plex forum are similar. The problem is on Plex side. One of the Plex employ comment that DSM is not exposing the subsystem for transcoding.

P.S. I've tried all the "tricks" known. Using docker run of PMS for using /dev/dri in native PMS. Adding VaapiDriver="i965" in preferences file etc. People are having problems on original synology after upgrade (depends on the model).

So the story on Plex transcoding hw doesn't give much hope for the moment.

 

  • Like 1
Link to comment
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.

×
×
  • Create New...