Software decode will drive up the CPU usage and increase temps so get a decent passive cooling case (flirc case is highly recommended). The RPi4 SoC is designed to run much hotter than you're seeing .. it's not some fragile thing that must run at 40ºC.
Posts by chewitt
-
-
Do you really need a VPN? .. Or would SSH key-only auth be sufficient? (which is a one-click toggle in the GUI once you've deployed keys). You can change the sshd_config to move the exposed port to something non-standard; doesn't improve security but does reduce the number of bots that will find the port and attempt to exploit it.
-
VP9 .webm isn't the easiest thing to play.
There is no hardware decode support for VP9 on the RPi4 (only H264/HEVC) so it would be software decoded. I'd expect 1080p media to be okay but no ARM board will handle 4K in software.
-
Perhaps try connecting to another HDMI port on the TV?
-
Enable SSH and use PuTTY (Windows) or the native SSH clients on Linux/macOS to connect
-
1. No idea, it should just work. Latest LE11 nightlies have fixes for some situations where blank screens might be seen. Again, I suggest you try the latest nightly on a clean SD card with no attempts to pre-fix problems.
2. RPi websites should have authoritative documentation. The main point of the switch to the Linux kernel DRM framework is that most of the old config.txt hacks available in the older downstream vendor kernel should not be needed now. Users assume reduced documentation on config.txt means something is missing, but that's not correct. You can capture the EDID data from HDMI and force detection of the TV; run 'getedid create' with a working HDMI connection.
3. Nope. Never seen it reported (never seen it myself). You can force output modes (as previously hinted) but you cannot force colourspace.
Current Kodi skins are 1080p resolution so either Kodi or the TV has to do upscaling to 4K and generally keeping Kodi on 1080p and allowing the TV to do the upscale results in lower load on the RPi (so faster RPi) and equivalent or better results on-screen as the TV has dedicating scaling hardware. So far that that guidance seem to be true for the majority but I guess the results are ultimately subjective.
-
Let the bikeshedding commence
-
You need to update the paths in the sqlite database file to match the new path.
https://gist.github.com/magnetikonline…ca948595ed3f137 has some hints; the sqlite3 binary is in the OS already.
-
Once it appears in the repo (within the next 24h prob.) and once their repo cache expires (usually within 24h) it will see/download/update the add-on to the new version.
-
Most hdmi_ settings in config.txt will be ignored after LE9.2 as we use the kernel DRM framework, e.g. "video=HDMI-A-1:1920x1080M@60" can be added to boot params in cmdline.txt (not config.txt) to force 1080p output for GUI. You should also be using the HDMI-0 port (nearest the power connector) not the HDMI-1 port. I'll also comment there is very little real-world need for 4K60 since practically all 4K content is 4K24 or 4K23.976 format, and you do not want to run the GUI at 4K unless you want a slow GUI - use 1080p and whitelist/adjust-refresh to switch to 4K modes when needed.
I'd suggest starting over with a clean SD card with no extra config applied and the latest LE11 nightly.
-
Add "video=HDMI-A-1:1920x1080M@60" to the APPEND line (boot params) in syslinux.cfg and it should force 1080p on HDMI-A-1. If the box has more than one output (DP/HDMI/etc.) you might need to adjust the connector name.
-
TV at 1080p 60hz
Does the TV have 23.976/24/50/59.94 modes? .. what happens if you enable "adjust refresh" with whitelist entries for those modes and support for rate doubling (to handle deinterlaced content)?
I'm asking because I only see the pink line with a shitty 10" LCD that I use for testing sometimes which only has 1080p 50/60Hz modes. If using the normal house TV with more modes and adjust-refresh I don't see the line. It would be nice to confirm it's only present with 60Hz.
-
Pick a different HDMI cable. Pick a different HDMI port?
You already proved the issue is not the NUC or LE by connecting the monitor so next call is Samsung support.
-
So WOL is no longer supported on LE 20 ?
I replied to the "Any suggestions or alternatives?" .. because regardless of whether LE supports WOL (don't know, never used it) it is a method that always seems to result in frustrated users moaning about how flaky/difficult it is to get working right on their hardware or the app being used (or some other issue) in forums. So I suggested something low-tech that will work.
-
@chewitt: did you forget to remove the patch 'amlogic-0091-FIXUP-add-adc-gpio-keys-and-led-s-to-dreambox.patch' before merging nigthly? This only causes trouble, because the exit dialog opens with almost every keystroke on the infrared remote control
There are multiple additions in that Fixup! commit so it would be good if you can experiement and tell me which bits work or not. The formula for the adc-keys values can be found in the vendor dts so perhaps validate my maths as it would be good to have the keys working.
-
There are some users who claim 4.3 is broken and terrible and 4.2 is the only TVH to use. There are also users who claim that 4.2 is old and broken and terrible and 4.3 is the only TVH to use. So ..
-
dootsie5times USB rtw88 drivers were merged in 6.2 and were backported to 6.1 in LE, so they are present in current LE11 nightly images.
Probably not for all hardware (e.g. I haven't picked all those changes for AMLGX) and I'm not sure they're present for RPi images either.
-
Known issue. We need to backport the LE11 fix to LE10 and then build a replacement add-on. That should happen in the next 24-48h.
