Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

1 hour ago, scoobdriver said:

have you ensured Plex user has correct access to /dev/dri ,  ? 

@scoobdriver

on "ls -la /dev/dri" 


drw-rw-rw-  2 root root              80 Mar  4 20:24 .
drwxr-xr-x 13 root root           13800 Mar  4 20:24 ..
crw-------  1 root root        226,   0 Mar  4 20:24 card0
crw-rw----  1 root videodriver 226, 128 Mar  4 20:24 renderD128

 

So, obviously, no.

But, after: sudo chmod 666 /dev/dri I've got same response on ls -la /dev/dri

 

drw-rw-rw-  2 root root              80 Mar  4 20:24 .
drwxr-xr-x 13 root root           13800 Mar  4 20:24 ..
crw-------  1 root root        226,   0 Mar  4 20:24 card0
crw-rw----  1 root videodriver 226, 128 Mar  4 20:24 renderD128

 

No errors reproted on chmod... but with no changes.

 

Link to comment
Share on other sites

2 hours ago, IG-88 said:

from ark intel that 0x3184 ant thats already in the original driver, inmply's a firmware problem (check the dmesg log)

dmesg:

41.026353] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeo                      ut
[   41.134248] i915 0000:00:02.0: Failed to reset chip
 

Link to comment
Share on other sites

31 minutes ago, smilenkovski said:

dmesg:

41.026353] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeo                      ut
[   41.134248] i915 0000:00:02.0: Failed to reset chip
 

try the original synology i915.ko and add "glk_dmc_ver1_04.bin" to the firmware/i915

the pci id is in the original driver and is used in ds920+ where "glk_dmc_ver1_04.bin" is present

920+ uses 0x3185 (https://ark.intel.com/content/www/de/de/ark/products/197305/intel-celeron-processor-j4125-4m-cache-up-to-2-70-ghz.html)

and in the driver 0x3184 and 0x3185 are treated the same way as GLK_IDS

 

#define INTEL_BXT_IDS(info) \
	INTEL_VGA_DEVICE(0x0A84, info), \
	INTEL_VGA_DEVICE(0x1A84, info), \
	INTEL_VGA_DEVICE(0x1A85, info), \
	INTEL_VGA_DEVICE(0x5A84, info), /* APL HD Graphics 505 */ \
	INTEL_VGA_DEVICE(0x5A85, info)  /* APL HD Graphics 500 */

#define INTEL_GLK_IDS(info) \
	INTEL_VGA_DEVICE(0x3184, info), \
	INTEL_VGA_DEVICE(0x3185, info)

#define INTEL_KBL_ULT_GT1_IDS(info) \
	INTEL_VGA_DEVICE(0x5906, info), /* ULT GT1 */ \
	INTEL_VGA_DEVICE(0x5913, info)  /* ULT GT1.5 */

 

Link to comment
Share on other sites

3 minutes ago, IG-88 said:

try the original synology i915.ko and add "glk_dmc_ver1_04.bin" to the firmware/i915

I'm just a beginner in linux. Can you point me to the post where the procedure is explained. So, when You say add  "glk_dmc_ver1_04.bin" to the firmware/i915" I have no idea how to do that. If it is doable trough tinycore I can try to do that. By the way, you are wright, CPU encoding give better picture than QS, but i3 8th gen is on 98/99 % usage.

Link to comment
Share on other sites

1 hour ago, smilenkovski said:

@scoobdriver

on "ls -la /dev/dri" 


drw-rw-rw-  2 root root              80 Mar  4 20:24 .
drwxr-xr-x 13 root root           13800 Mar  4 20:24 ..
crw-------  1 root root        226,   0 Mar  4 20:24 card0
crw-rw----  1 root videodriver 226, 128 Mar  4 20:24 renderD128

 

So, obviously, no.

But, after: sudo chmod 666 /dev/dri I've got same response on ls -la /dev/dri

 

drw-rw-rw-  2 root root              80 Mar  4 20:24 .
drwxr-xr-x 13 root root           13800 Mar  4 20:24 ..
crw-------  1 root root        226,   0 Mar  4 20:24 card0
crw-rw----  1 root videodriver 226, 128 Mar  4 20:24 renderD128

 

No errors reproted on chmod... but with no changes.

 

Try sudo chmod 666 /dev/dri/* 

 

(I have this command in a script to run on startup ) 

Link to comment
Share on other sites

27 minutes ago, smilenkovski said:

I'm just a beginner in linux. Can you point me to the post where the procedure is explained. So, when You say add  "glk_dmc_ver1_04.bin" to the firmware/i915" I have no idea how to do that. If it is doable trough tinycore I can try to do that. By the way, you are wright, CPU encoding give better picture than QS, but i3 8th gen is on 98/99 % usage.

you can ssh into xpenology after boot and do 
 

cd /lib/firmware/i915 

 

sudo wget https://anduin.linuxfromscratch.org/sources/linux-firmware/i915/glk_dmc_ver1_04.bin 

 Then reboot 

 

 

Link to comment
Share on other sites

4 minutes ago, scoobdriver said:

Try sudo chmod 666 /dev/dri/* 

 

(I have this command in a script to run on startup ) 

Yeah, that changed the output of ls -la, now is like yours. It is transcoding hw (shown in dashboard) and buffering every 5-6 second. Something is wrong with all my setup. Maybe I'll reinstall everything, this is my spare  comp I have three movies 4k for testing purposes. And Thank You for helping.

Link to comment
Share on other sites

2 hours ago, smilenkovski said:

I'm just a beginner in linux. Can you point me to the post where the procedure is explained. So, when You say add  "glk_dmc_ver1_04.bin" to the firmware/i915" I have no idea how to do that.

If it is doable trough tinycore I can try to do that. By the way, you are wright, CPU encoding give better picture than QS, but i3 8th gen is on 98/99 % usage.

 

then what did you do with the i915_universal_918p_DSM7.zip file? it contained the i915.ko driver and the firmware, the folder structure in there was the guidance

folder modules contained the i915.ko (supposed to replace the original from synology) and firmware contained the i915 folder with all the needed firmware to use more then just apollo lake on the 918+

without the firmware you wont be able to use more then the original 918+

if a 4 core cpu is in high load for transcoding then you have no hardware transcoding active, you would need to active that in video station and thats only possible with a patch to circumvent the serial number check

 

its done apart from tinycore after installing dsm, you rename the original i915.ko (easier to go back that way then just overwriting it) copy then one in the same place and also copy the firmware (at least the "bxt_dmc_ver1_07.bin" is already there as its the one needed for apollo lake

 

Link to comment
Share on other sites

4 minutes ago, IG-88 said:

 

its done apart from tinycore after installing dsm, you rename the original i915.ko (easier to go back that way then just overwriting it) copy then one in the same place and also copy the firmware (at least the "bxt_dmc_ver1_07.bin" is already there as its the one needed for apollo lake

I've done that.  Scoobdriver user help me. Thank You IG-88 for your help. It is not the first You are helping me. thanx

Link to comment
Share on other sites

Just a test on a test box (Z370 i5 860K),   VirtualBox 6.132,  ssh as tc 

 

sudo ./rploader.sh build bromolow-7.0.1-42218

 

----------------
It looks that you will need the following modules :


Found VGA Controller : pciid 15add00000405  Required Extension :
No matching extension
Found Ethernet Interface : pciid 1af4d00001000 Required Extension :
No matching extension
Found SATA Controller : pciid 8086d00002829  Required Extension :
No matching extension

 

[!] Failed to unpack /home/tc/redpill-load/ext/boot-image-template.img.gz to loader.img

*** Process will exit ***

 

Any ideas?

Link to comment
Share on other sites

On 3/3/2022 at 5:47 PM, 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 where can I make the change? I'm running DSM virtualized on Proxmox using @pocopico tinycore loader.

Link to comment
Share on other sites

2 hours ago, synoxpe said:

where can I make the change?

@WiteWulf Something like this in user_config.json?

{
  "extra_cmdline": {
    "pid": "0x0001",
    "vid": "0x46f4",
    "sn": "xxx",
    "mac1": "xxx",
    "SataPortMap": "15",
    "DiskIdxMap": "0000”,
    “nmi_watchdog”: “0”
  },
  "synoinfo": {

          "internalportcfg" : "0xffff",
          "maxdisks" : "16"

},
  "ramdisk_copy": {

    
}

}

 

  • Like 1
Link to comment
Share on other sites

22 minutes ago, Orphée said:

Stop playing with random values...

DiskIdxMap 0000 make no sense at all...

 

Working for me perfectly. The first digit in SataPortMap is apparently incorrectly reported in a Proxmox environment where I'm running my stuff. So effectively the second controller starts from 0.

That's not my question here anyway. I just pasted the config to check if that's the way to disable the nmi_watchdog kernel parameter, which is crashing my DSM if enabled causing Kernel panic.

 

  • Thanks 1
Link to comment
Share on other sites

Just now, synoxpe said:

 

Working for me perfectly. The first digit in SataPortMap is apparently incorrectly reported in a Proxmox environment where I'm running my stuff. So effectively the second controller starts from 0.

That's not my question here anyway. I just pasted the config to check if that's the way to disable the nmi_watchdog kernel parameter, which is crashing my DSM if enabled causing Kernel panic.

 

I understand, but still, other will come and see your settings and will copy/paste it thinking it is how it works.

I know that on proxmox qc35 the first controller is not used at all, but ... for a correct mindset, you should not set 0000., better remove it or set it as 0A00

Link to comment
Share on other sites

39 minutes ago, Orphée said:

I understand, but still, other will come and see your settings and will copy/paste it thinking it is how it works.

I know that on proxmox qc35 the first controller is not used at all, but ... for a correct mindset, you should not set 0000., better remove it or set it as 0A00

Ack!

How about passing the nmi_watchdog parameter? Is this a correct way?

Link to comment
Share on other sites

44 minutes ago, synoxpe said:

to check if that's the way to disable the nmi_watchdog kernel parameter, which is crashing my DSM if enabled causing Kernel panic.

disabling at boot might be easy as kernel parameter

the generic's are here

http://redsymbol.net/linux-kernel-boot-parameters/4.4/

for syno's specifics you need to check syno's kernel and documentation (if available)

Edited by IG-88
Link to comment
Share on other sites

5 minutes ago, IG-88 said:

the generic's are here

http://redsymbol.net/linux-kernel-boot-parameters/4.4/

for syno's specifics you need to check syno's kernel and documentation (if available)

Thanks again!

My context is redpill tinycore loader's user_config.json. Is it possible to pass the parameter there as I've specified above?

For now I just used this from the DSM command prompt:

root@ds918p:~# echo 0 > /proc/sys/kernel/nmi_watchdog 
root@ds918p:~#

 

Edited by synoxpe
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...