Power & Source of Big Ideas

NanoPI M4 - does not recognize 4K monitors - limited to 1920

Moderators: chensy, FATechsupport

Hello,
super happy with M4 sofar. Easy install from SD to MMC, it is fast with Friendlyarm Desktop 18.04 dec 19, 2018 release.
but
HDMI output defaults to 1920x1080@60. Works fine for most scenario's but i want feed some big 4K screens on the wall with NanoPI. Tested with LG 27UD68P en IiyamaPL2792UH both support 3840x2160.
xrandr gives

Code: Select all

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 disconnected primary (normal left inverted right x axis y axis)
HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
   1920x1080     60.00*   59.94    30.00    29.97 
   1920x1080i    60.00    59.94 
   1600x900      60.00 
   1280x1024     60.02 
   1280x800      59.91 
   1152x864      59.97 
   1280x720      60.00    59.94 
   1024x768      60.00 
   800x600       60.32 
   720x480       60.00    59.94 
   640x480       60.00    59.94 
DP-1 disconnected (normal left inverted right x axis y axis)

dmesg | grep -Ei "(drm)|(edid)" gives

Code: Select all

[    1.066491] rk-vcodec ff650000.vpu_service: drm allocator with mmu enabled
[    1.071026] rk-vcodec ff660000.rkvdec: drm allocator with mmu enabled
[    1.095922] [drm] Initialized drm 1.1.0 20060810
[    1.099771] [drm] Rockchip DRM driver version: v1.0.1
[    1.665254] rockchip-drm display-subsystem: defer getting devfreq
[    1.667354] [drm] no mcu-timing node found in /vop@ff900000
[    1.667872] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffffff8008cf31b8)
[    1.669547] [drm] no mcu-timing node found in /vop@ff8f0000
[    1.670059] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffffff8008cf31b8)
[    1.673867] rockchip-drm display-subsystem: bound ff970000.edp (ops 0xffffff8008cea738)
[    1.677982] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffffff8008ce80a8)
[    1.681797] rockchip-drm display-subsystem: bound fec00000.dp (ops 0xffffff8008ce9060)
[    1.682523] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.683111] [drm] No driver support for vblank timestamp query.
[    1.721115] rockchip-drm display-subsystem: can't not find any loader display
[    1.721774] rockchip-drm display-subsystem: failed to show loader logo
[    1.722707] Freeing drm_logo memory: 2252K
[    1.763123] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 14
[    1.763705] rockchip-vop ff8f0000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11
[    2.053336] rockchip-drm display-subsystem: fb0:  frame buffer device
[    4.701131] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Not connected. Disabling cdn
[    6.820147] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11
[    7.939483] [drm] unsupported connector property: hdmi_color_depth_capacity


@chensy let me know if you need anything else to debug
greetings William
As an alternative, you could try out this Image:
https://github.com/avafinger/nanopi-m4- ... -emmc-only

As a bonus, you get Kodi 18 RC5.
After login you run kodi. Kodi will detect your 4K Display and set properly res. mode.
Don't be fooled if you get the wrong mode at booting, kodi will set the correct mode.

If you care only for a Desktop experience, please ignore this.

PS. This is experimental and will format your eMMC and you end up losing your current data.
Hi,

If you are using an image with X, take a look on this thread:

viewtopic.php?f=62&t=1891

Who is online

In total there are 4 users online :: 0 registered, 0 hidden and 4 guests (based on users active over the past 5 minutes)
Most users ever online was 106 on Tue Jun 04, 2019 5:48 pm

Users browsing this forum: No registered users and 4 guests