[x86-64] GMKtec NucBox G10 Resolution Change Issue

    Hi.

    A newbie here although a very long time happy user (but not very techie).

    I have a new GMKtec NucBox G10 (AMD Ryzen 5 3500U) on which I've installed Libreelec 12.2.0 (seemed the most stable at the time but......!). Outputting to an LG TV.

    I have an issue trying to reduce the display resolution from 3840x2160p to 1920x1080p. I'm trying to do this because playback is suffering (e.g. audio only) at the higher resolution. But if I do this and then reboot the Libreelec splash screen appears, freezes, and then a small window with Libreelec in it appears in the top left of the screen.

    Hours of AI (not) assisted (not) help has found no resolution. The best I can get SSH to do is reboot without the error but then the display resolution changes back to 3840x2160p.

    Am I correct to be trying to reduce the resolution to improve playback performance? If so, how can I do it? Would a more up to date Libreelec version help (there was some issue doing this which I've forgotten given the day I've had!)? Is this an issue with this hardware (I've always used Intel before)?

    I tried a forum search but it's hard to come up with a good search term.

    Cheers

    If the current HDMI cables and/or internal firmware (most NUC like devices use an internal DP to HDMI adapter and this has some firmware) have issues with 4K60 but the Kodi GUI (desktop) defaults to 4K60 and "adjust refresh" is not used and/or 1080p modes are not whitelisted, Kodi will upscale everything to 4K60 to compound the problem. It's also possible to have bandwidth issues with uncertified HDMI cables. Have a read of https://wiki.libreelec.tv/configuration/4k-hdr for explanations of recommended config.

    To force 1080p desktop, run tail /sys/class/drm/*/status to understand what connector type/number is in active use. Assuming HDMI-A-1, then add video=HDMI-A-1:1920x1080M@60D to kernel boot params; which will be either the syslinux.cfg file in the root folder of the USB (legacy boot) or EFI/BOOT/grub.cfg on the USB (EFI boot). If the active connector is not HDMI-A-1 adjust the video= command accordingly. This forces the initial kernel DRM state to 1080p@60 and not 4K where it probably defaults to 4K60.

    NB: Some users solve 4K60 issues by using an external DP to HDMI adaptor instead of the HDMI ports on the box. This is not always a guarantee of success as most adaptors are cheap and can also have rubbish firmware; but unlike the internal one soldered to the motherboard, you can order a bunch from Amazon and experiment until you find one that plays nice.

    Quote from chewitt

    If the current HDMI cables and/or internal firmware (most NUC like devices use an internal DP to HDMI adapter and this has some firmware) have issues with 4K60 but the Kodi GUI (desktop) defaults to 4K60 and "adjust refresh" is not used and/or 1080p modes are not whitelisted, Kodi will upscale everything to 4K60 to compound the problem. It's also possible to have bandwidth issues with uncertified HDMI cables. Have a read of https://wiki.libreelec.tv/configuration/4k-hdr for explanations of recommended config.

    To force 1080p desktop, run tail /sys/class/drm/*/status to understand what connector type/number is in active use. Assuming HDMI-A-1, then add video=HDMI-A-1:1920x1080M@60D to kernel boot params; which will be either the syslinux.cfg file in the root folder of the USB (legacy boot) or EFI/BOOT/grub.cfg on the USB (EFI boot). If the active connector is not HDMI-A-1 adjust the video= command accordingly. This forces the initial kernel DRM state to 1080p@60 and not 4K where it probably defaults to 4K60.

    NB: Some users solve 4K60 issues by using an external DP to HDMI adaptor instead of the HDMI ports on the box. This is not always a guarantee of success as most adaptors are cheap and can also have rubbish firmware; but unlike the internal one soldered to the motherboard, you can order a bunch from Amazon and experiment until you find one that plays nice.

    Many thanks for that.

    I've certainly learnt a lot about the Libreelec display/player settings yesterday which is all good stuff! I have, amongst other things (but mainly), set "adjust refresh" to "on start/stop" and whitelisted most 1080p modes. Presumably that just leaves the display (the Libreelec GUI) in 3840 resolution which does not seem to be a problem. Maybe that's enough?

    Sorry but I'm not techie in this regard to know what to do with your suggested commands. I only just "mastered" SSH yesterday! I could try asking my AI but I don't have another day to spend with it for it to eventually admit it's been guessing and lying to me!

    Quote from User100

    Many thanks for that.

    I've certainly learnt a lot about the Libreelec display/player settings yesterday which is all good stuff! I have, amongst other things (but mainly), set "adjust refresh" to "on start/stop" and whitelisted most 1080p modes. Presumably that just leaves the display (the Libreelec GUI) in 3840 resolution which does not seem to be a problem. Maybe that's enough?

    Sorry but I'm not techie in this regard to know what to do with your suggested commands. I only just "mastered" SSH yesterday! I could try asking my AI but I don't have another day to spend with it for it to eventually admit it's been guessing and lying to me!

    OK, I couldn't help myself so asked AI to explain your suggestion and it said something I think I understand......

    "This instruction adapts the generic Linux kernel method to force 1080p boot resolution on your LibreELEC AMD NUC setup, overriding the default 4K detection from your display.

    Identify Connector

    Boot into LibreELEC, enable SSH (Settings > Services), connect via SSH as root. Run tail /sys/class/drm/*/status to find the active HDMI connector (e.g., HDMI-A-1 shows "connected"). AMD APUs use the same DRM naming.github

    Boot Files on Installed LibreELEC

    Unlike USB, files are on the read-only /flash partition (internal storage). Remount writable: mount -o remount,rw /flash. Edit /flash/syslinux.cfg (BIOS/legacy boot) or /flash/EFI/BOOT/syslinux.cfg (UEFI)—not grub.cfg; LibreELEC generic x86 uses Syslinux/extlinux. Use ls /flash to confirm.libreelec+1

    Add Kernel Parameter

    In the APPEND or linux line, append video=HDMI-A-1:1920x1080M@60D (replace HDMI-A-1 with your connector). Example: APPEND boot=UUID=... quiet video=HDMI-A-1:1920x1080M@60D. Save with nano, remount read-only (mount -o remount,ro /flash), reboot. Forces kernel framebuffer to 1080p@60Hz on AMD DRM before Kodi loads.reddit+1

    Why It Works on AMD NUC

    LibreELEC generic x86 supportsThis instruction adapts the generic Linux kernel trick to force a 1080p boot framebuffer on your LibreELEC-installed AMD NUC, overriding the default 4K detection that lags the GUI.

    Identify Connector

    Boot LibreELEC, enable SSH (Settings > Services), connect as root. Run tail /sys/class/drm/*/status to spot the active HDMI (likely HDMI-A-1 on AMD APUs). Note it exactly.wiki.libreelec

    Edit Boot Config

    Remount flash writable: mount -o remount,rw /flash. Check ls /flash—edit /flash/syslinux.cfg (legacy BIOS) or /flash/EFI/BOOT/syslinux.cfg (EFI, common on NUCs; not grub.cfg). Use nano to append video=HDMI-A-1:1920x1080M@60D to the APPEND line (swap HDMI-A-1 for yours). Example: APPEND boot=UUID=... video=HDMI-A-1:1920x1080M@60D quiet.github+1

    Apply and Test

    Save, remount read-only (mount -o remount,ro /flash), reboot. Kernel now initializes DRM at 1080p@60Hz (M=reduced blanking, D=preferred), smoothing boot/GUI on your AMD hardware before Kodi loads. Tweak Kodi resolution afterward if needed".

    But is it correct?

    Since today (!) we have modernized forum rules. Please read them carefully.

    Thread

    Forum Rules

    General Conduct

    • Be polite and respectful to forum staff and other users
    • Be polite and respectful towards this project and other projects
    • Be patient, user and staff are spread all over the world, an answer may take time
    Posting

    • One topic per thread
    • Posts should be written in English (add text in your native language if needed)
    • Be as descriptive and detailed as possible. We are not mind readers!
    • If AI tools have been used to create your post or triage an issue, name the tool and version in the post
    • Do not
    …
    newphreak
    March 15, 2016 at 1:02 AM
    Quote from Da Flex

    Since today (!) we have modernized forum rules. Please read them carefully.

    Thread

    Forum Rules

    General Conduct

    • Be polite and respectful to forum staff and other users
    • Be polite and respectful towards this project and other projects
    • Be patient, user and staff are spread all over the world, an answer may take time
    Posting

    • One topic per thread
    • Posts should be written in English (add text in your native language if needed)
    • Be as descriptive and detailed as possible. We are not mind readers!
    • If AI tools have been used to create your post or triage an issue, name the tool and version in the post
    • Do not
    …
    newphreak
    March 15, 2016 at 1:02 AM

    Not a good start! Maybe it was quoting AI without saying which and the model? And/or something else?

    Quote from User100

    Not a good start! Maybe it was quoting AI without saying which and the model? And/or something else?

    We want proper quotation whenever AI is involved. The rule change is no reaction to your content. We made this decision to avoid bot postings. Sorry.