Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Login screen not available workaround found but can not set the display resolution to 3440x1440 for used Dell Monitor

Featured Replies

Here the workaround to get a "gdm" login screen:

 

root@ password: 

    _             _    _           
   /_\  _ _ _ __ | |__(_)__ _ _ _  
  / _ \| '_| '  \| '_ \ / _` | ' \ 
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|
                                   
 v25.11.2 for Khadas VIM3 running Armbian Linux 6.12.58-current-meson64

 

 Performance:  

 Load:         25%                Uptime:       4 minutes     Local users:  3               
 Memory usage: 8% of 3.68G      
 CPU temp:     38°C                Usage of /:   11% of 58G        
 RX today:     920 MiB               

 Tips:

 Armbian config utility https://tinyurl.com/yc39n6m3

 Commands: 

 Configuration : armbian-config
 Monitoring    : htop


root@khadas-vim3:~# systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.


Issue #1:

 

No login screen on HDMI:



root@khadas-vim3:~# systemctl status gdm.service 
● gdm.service - GNOME Display Manager
     Loaded: loaded (/usr/lib/systemd/system/gdm.service; static)
     Active: active (running) since Mon 2025-12-15 17:25:25 CET; 4min 28s ago
    Process: 2684 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
   Main PID: 2699 (gdm3)
      Tasks: 4 (limit: 4215)
     Memory: 8.9M (peak: 10.4M)
        CPU: 414ms
     CGroup: /system.slice/gdm.service
             └─2699 /usr/sbin/gdm3

Dec 15 17:27:04 khadas-vim3 gdm3[2699]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Dec 15 17:27:04 khadas-vim3 gdm3[2699]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Dec 15 17:28:40 khadas-vim3 gdm3[2699]: Gdm: GdmDisplay: Session never registered, failing
Dec 15 17:28:40 khadas-vim3 gdm3[2699]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Dec 15 17:28:40 khadas-vim3 gdm3[2699]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Dec 15 17:28:40 khadas-vim3 gdm-autologin][3881]: PAM unable to dlopen(pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object file: No >
Dec 15 17:28:40 khadas-vim3 gdm-autologin][3881]: PAM adding faulty module: pam_gnome_keyring.so
Dec 15 17:28:40 khadas-vim3 gdm-autologin][3881]: pam_unix(gdm-autologin:session): session opened for user amach(uid=1000) by amach(uid=0)
Dec 15 17:28:41 khadas-vim3 gdm3[2699]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Dec 15 17:28:41 khadas-vim3 gdm3[2699]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed


root@khadas-vim3:~# ll /dev/dri/
total 0
drwxr-xr-x  2 root root        140 Dec 15 17:25 by-path
crw-rw----+ 1 root video  226,   0 Dec 15 17:25 card0
crw-rw----+ 1 root video  226,   1 Dec 15 17:25 card1
crw-rw----+ 1 root video  226,   2 Dec 15 17:25 card2
crw-rw----+ 1 root render 226, 128 Dec 15 17:25 renderD128
crw-rw----+ 1 root render 226, 129 Dec 15 17:25 renderD129

 

root@khadas-vim3:~# udevadm info /dev/dri/card0
P: /devices/platform/soc/ff900000.vpu/drm/card0
M: card0
R: 0
U: drm
T: drm_minor
😧 c 226:0
N: dri/card0
L: 0
S: dri/by-path/platform-ff900000.vpu-card
E: DEVPATH=/devices/platform/soc/ff900000.vpu/drm/card0
E: DEVNAME=/dev/dri/card0
E: DEVTYPE=drm_minor
E: MAJOR=226
E: MINOR=0
E: SUBSYSTEM=drm
E: USEC_INITIALIZED=2805131
E: ID_PATH=platform-ff900000.vpu
E: ID_PATH_TAG=platform-ff900000_vpu
E: ID_FOR_SEAT=drm-platform-ff900000_vpu
E: DEVLINKS=/dev/dri/by-path/platform-ff900000.vpu-card
E: TAGS=:master-of-seat:uaccess:seat:
E: CURRENT_TAGS=:master-of-seat:uaccess:seat:

 

root@khadas-vim3:~# udevadm info /dev/dri/card1
P: /devices/platform/soc/ffe40000.gpu/drm/card1
M: card1
R: 1
U: drm
T: drm_minor
😧 c 226:1
N: dri/card1
L: 0
S: dri/by-path/platform-ffe40000.gpu-card
E: DEVPATH=/devices/platform/soc/ffe40000.gpu/drm/card1
E: DEVNAME=/dev/dri/card1
E: DEVTYPE=drm_minor
E: MAJOR=226
E: MINOR=1
E: SUBSYSTEM=drm
E: USEC_INITIALIZED=7219633
E: ID_PATH=platform-ffe40000.gpu
E: ID_PATH_TAG=platform-ffe40000_gpu
E: GDM_NUMBER_OF_GRAPHICS_CARDS=3
E: ID_FOR_SEAT=drm-platform-ffe40000_gpu
E: DEVLINKS=/dev/dri/by-path/platform-ffe40000.gpu-card
E: TAGS=:seat:master-of-seat:uaccess:
E: CURRENT_TAGS=:seat:master-of-seat:uaccess:

 

root@khadas-vim3:~# udevadm info /dev/dri/card2
P: /devices/platform/etnaviv/drm/card2
M: card2
R: 2
U: drm
T: drm_minor
😧 c 226:2
N: dri/card2
L: 0
S: dri/by-path/platform-etnaviv-card
E: DEVPATH=/devices/platform/etnaviv/drm/card2
E: DEVNAME=/dev/dri/card2
E: DEVTYPE=drm_minor
E: MAJOR=226
E: MINOR=2
E: SUBSYSTEM=drm
E: USEC_INITIALIZED=7215211
E: ID_PATH=platform-etnaviv
E: ID_PATH_TAG=platform-etnaviv
E: GDM_NUMBER_OF_GRAPHICS_CARDS=3
E: ID_FOR_SEAT=drm-platform-etnaviv
E: DEVLINKS=/dev/dri/by-path/platform-etnaviv-card
E: TAGS=:master-of-seat:uaccess:seat:
E: CURRENT_TAGS=:master-of-seat:uaccess:seat:

 

WORKAROUND - Issue #1:


root@khadas-vim3:/dev/dri# mv card2 card2out


root@khadas-vim3:/dev/dri# ll
total 0
drwxr-xr-x  2 root root        140 Dec 15 17:33 by-path
crw-rw----+ 1 root video  226,   0 Dec 15 17:35 card0
crw-rw----+ 1 root video  226,   1 Dec 15 17:25 card1
crw-rw----+ 1 root video  226,   2 Dec 15 17:25 card2out
crw-rw----+ 1 root render 226, 128 Dec 15 17:25 renderD128
crw-rw----+ 1 root render 226, 129 Dec 15 17:25 renderD129


root@khadas-vim3:/dev/dri# systemctl restart gdm.service 

 

root@khadas-vim3:/dev/dri# systemctl status gdm.service 
● gdm.service - GNOME Display Manager
     Loaded: loaded (/usr/lib/systemd/system/gdm.service; static)
     Active: active (running) since Mon 2025-12-15 17:38:56 CET; 7s ago
    Process: 8999 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
   Main PID: 9006 (gdm3)
      Tasks: 5 (limit: 4215)
     Memory: 6.2M (peak: 7.2M)
        CPU: 172ms
     CGroup: /system.slice/gdm.service
             └─9006 /usr/sbin/gdm3

Dec 15 17:38:56 khadas-vim3 systemd[1]: Starting gdm.service - GNOME Display Manager...
Dec 15 17:38:56 khadas-vim3 systemd[1]: Started gdm.service - GNOME Display Manager.
Dec 15 17:38:56 khadas-vim3 gdm-autologin][9011]: PAM unable to dlopen(pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object file: No >
Dec 15 17:38:56 khadas-vim3 gdm-autologin][9011]: PAM adding faulty module: pam_gnome_keyring.so
Dec 15 17:38:56 khadas-vim3 gdm-autologin][9011]: pam_unix(gdm-autologin:session): session opened for user amach(uid=1000) by amach(uid=0)
Dec 15 17:38:56 khadas-vim3 gdm3[9006]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Dec 15 17:38:56 khadas-vim3 gdm3[9006]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

 

---

 

Issue #2:


Missing Display resolution 3440x1440 for Display Dell U3415W connected to HDMI:

 

root@khadas-vim3:/home/amach# cat xrandr.txt 

Screen 0: minimum 16 x 16, current 2560 x 1440, maximum 32767 x 32767
HDMI-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 800mm x 330mm
   2560x1440     59.91*+
   1920x1440     59.90  
   1600x1200     59.87  
   1440x1080     59.87  
   1400x1050     59.86  
   1280x1024     59.76  
   1280x960      59.94  
   1152x864      59.78  
   1024x768      59.68  
   800x600       59.86  
   640x480       59.38  
   320x240       59.52  
   1920x1200     59.88  
   1680x1050     59.85  
   1440x900      59.89  
   1280x800      59.81  
   1152x720      59.75  
   960x600       59.63  
   928x580       59.88  
   800x500       59.50  
   768x480       59.38  
   720x480       59.71  
   640x400       59.20  
   320x200       58.96  
   2048x1152     59.90  
   1920x1080     59.88  
   1600x900      59.82  
   1368x768      59.88  
   1280x720      59.86  
   1024x576      59.90  
   864x486       59.45  
   720x400       59.55  
   640x350       59.77  


root@khadas-vim3:/dev/dri# inxi -Gxx
Graphics:
  Device-1: meson-g12a-vpu driver: meson_drm v: N/A bus-ID: N/A chip-ID: amlogic:ff900000
  Device-2: meson-g12a-mali driver: panfrost v: kernel bus-ID: N/A chip-ID: amlogic:ffe40000
  Device-3: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: N/A bus-ID: N/A
    chip-ID: amlogic:ff600000
  Display: server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.6 compositor: gnome-shell v: 46.0
    driver: X: loaded: modesetting gpu: meson_drm,panfrost,meson_dw_hdmi tty: 170x62
  Monitor-1: HDMI-A-1 model: Dell U3415W res: 3440x1440 dpi: 109 diag: 865mm (34.1")
  API: EGL v: 1.5 platforms: gbm: drv: etnaviv surfaceless: drv: panfrost inactive: wayland,x11
  API: OpenGL v: 3.1 compat-v: 2.1 vendor: mesa v: 25.0.7-0ubuntu0.24.04.2
    note: console (EGL sourced) renderer: Vivante GC8000 rev 7120, Mali-G52 (Panfrost)

 

 

Please let me know or test to set the display resolution to 3440x1440 - Thank you

 

 

Edited by amach

  • Author

After applying the following two kernel patches which I understand are valid for mainline kernel only, I can use the display properly with a resolution 3440x1440 and refresh rate of 60Hz:

 

patchwork.kernel.org

[RFC,v1] drm/meson: venc: add support for HDMI DMT modes up to 3840x2160 -...

github.com/chewitt/linux

WIP: drm/meson: add support for higher bandwidth DMT modes

committed Jan 5, 2026

xdarklight

+3 -3

There's a report from a user with a DELL U3415W monitor and a Khadas VIM3 statin…

-

But having both patches applied or not does not matter, in general with mainline kernel the display is flickering/shaking only during boot, any idea how to get this addressed? thx

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.