What do you men test with KMS not FKMS.
distroconfig.txt contains
dtoverlay=vc4-kms-v3d,cma-512 but you replaced it with
dtoverlay=vc4-fkms-v3d,cma-512 in config.txt - that's the legacy video driver
so long,
Hias
Cannot get LE to run on Raspberry PI 4 4GB of RAM
-
jMooney -
June 21, 2021 at 4:34 PM -
Thread is Resolved
-
-
I started the PI with the stock configs and the cmdline.txt changes additions shown above. The PI gets an IP address but that seems to be about it. I can ping it but can't connect with ssh. The activity light is solid. All of the information provided thus far is from the Sony WEGA. I have not been able to get the PI to do anything when connected to the 2 SmartTVs.
-
I figured out my problem with getting ssh running. I corrected cmdline.txt and started the pi with fresh install and stock configs. Below are the results. The first one is from the tv that I was able to get LE working modifying the configs. The second one is from one of the other tvs I mentioned that I have tried it on and I have been unable to get it to be recognized by the tv.
Sony WEGA KDF-60XS955
LibreELEC (official): 9.95.4 (RPi4.arm)
LibreELEC:~ # pastekodi
LibreELEC:~ # modetest | pastebinit
LibreELEC:~ # vcdbg log msg 2>&1 | pastebinit
Sony Bravia KDL-55HX701
LibreELEC (official): 9.95.4 (RPi4.arm)
LibreELEC:~ # pastekodi
LibreELEC:~ # modetest | pastebinit
LibreELEC:~ # vcdbg log msg 2>&1 | pastebinit
-
Both vcdbg logs show that the firmware can't read the EDID of the TV, which is quite odd.
Can you test with some other (computer) monitor or TV and check if any of these work with stock RPiOS or LE (without config.txt changes)?
so long,
Hias
-
Hias
Thank for you help and patience with this. I purchased a micro hdmi adapter and removed the pi from the Argon One V2 case and now libreelec works fine on the TVs in question with a fresh install and no modifications whatsoever. I reached out to Argon40 to try to get assistance with getting the PI/libreelec working with their case.
Thanks
Ted
-
Oh, you could have saved yourself and us a lot of time if you had mentioned that you used an Argon case before - these cases seem to cause a lot of trouble... See eg this recent post: RE: LibreElec 9.95.4 on Raspberry Pi 4 with Argon One V2 case - HDMI problems
so long,
Hias
-
Hi HiassofT:
I'm struggeling quite for a long time with a pale picture on LE 9.95.x.
Before I'd set in config.txt
As you have wrote, this isn't working anymore in LE10. I can set in /flash/cmdline.txt
Codeboot=UUID=2311-4421 disk=UUID=4a7717ae-4e4f-431a-86cf-643c8bb8834a quiet drm.edid_firmware=HDMI-A-1:edid/edid-HDMI-A-1.bin video=HDMI-A-1:1920x1080M@60Dmodetest gives me a lot of output also regarding the supported colorspaces, e.g.:
Code37 Colorspace: flags: enum enums: Default=0 SMPTE_170M_YCC=1 BT709_YCC=2 XVYCC_601=3 XVYCC_709=4 SYCC_601=5 opYCC_601=6 opRGB=7 BT2020_CYCC=8 BT2020_RGB=9 BT 2020_YCC=10 DCI-P3_RGB_D65=11 DCI-P3_RGB_Theater=12 value: 0fbset gives me:
Codefbset -fb /dev/fb0 -s mode "1920x1080-0" # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz geometry 1920 1080 1920 1080 16 timings 0 0 0 0 0 0 0 accel true rgba 5/11,6/5,5/0,0/0 endmodeHow can I force the video parameter to use a specific colorspace?
-
It's not a colorspace issue, the problem is that your monitor doesn't seem to support limited range on CTA ("TV") modes. Forcung full range output isn't implemented in the driver yet, so there's currently no workaround for your monitor issue.
so long,
Hias
-
Thanks. I'm currently try to understand the edid data. I loaded the edid file in wxedid. But my understanding is quite limited yet.
Is here a way to extend the edid file by the missing modes?
-
- Best Answer
There's not much you can do with edid editing. Your monitor is probably properly announcing support for 1920x1080 etc modes (otherwise you would not be able to select those) but doesn't handle the limited range pixel data - I have an ancient monitor with the same issue here.
so long,
Hias
-
FYI, I received the new card for one of my Argon One cases and it works as expected on 2 of my TVs. On the third Sony WEGA (the older one) I had to set the resolution in cmdline.txt to 720p for it to work.
-
