Samsung monitor stays black for several minutes until showing image
Using Debian sid/unstable with self-built Linux since a while, an old Samsung monitor stays black for several minutes until an image is shown. Not even the system firmware messages are shown. The green LED blinks periodically as trying to synchronize but after fifteen seconds the beat skips and it blinks again periodically. This only happens, when the monitor was powered off or in standby for several minutes. Rebooting the system the system firmware messages and Linux messages are shown right away.
I am attaching the Linux logs with drm.debug=0xe
. Is it broken hardware, or is there something wrong with the driver?
[ 0.454438] simple-framebuffer simple-framebuffer.0: [drm:simpledrm_probe] display mode={"": 60 47185 1024 1024 1024 1024 768 768 768 768 0x40 0x0}
[ 0.454448] simple-framebuffer simple-framebuffer.0: [drm:simpledrm_probe] framebuffer format=XR24 little-endian (0x34325258), size=1024x768, stride=4096 byte
[ 0.454453] simple-framebuffer simple-framebuffer.0: [drm:simpledrm_probe] using I/O memory framebuffer at [mem 0xd0000000-0xd02fffff flags 0x200]
[ 0.454496] simple-framebuffer simple-framebuffer.0: [drm:drm_fb_build_fourcc_list] adding native format XR24 little-endian (0x34325258)
[ 0.454602] simple-framebuffer simple-framebuffer.0: [drm:drm_sysfs_connector_hotplug_event] [CONNECTOR:35:Unknown-1] generating connector hotplug event
[ 0.454609] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
[ 0.454615] [drm:drm_client_modeset_probe]
[ 0.454620] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:35:Unknown-1]
[ 0.454626] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:35:Unknown-1] status updated from unknown to connected
[ 0.454640] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:35:Unknown-1] probed modes :
[ 0.454643] [drm:drm_mode_debug_printmodeline] Modeline "1024x768": 60 47185 1024 1024 1024 1024 768 768 768 768 0x48 0x0
[ 0.454649] [drm:drm_client_modeset_probe] connector 35 enabled? yes
[ 0.454653] [drm:drm_client_modeset_probe] Not using firmware configuration
[ 0.454655] [drm:drm_client_modeset_probe] looking for cmdline mode on connector 35
[ 0.454658] [drm:drm_client_modeset_probe] looking for preferred mode on connector 35 0
[ 0.454660] [drm:drm_client_modeset_probe] found mode 1024x768
[ 0.454662] [drm:drm_client_modeset_probe] picking CRTCs for 4096x4096 config
[ 0.454665] [drm:drm_client_modeset_probe] desired mode 1024x768 set on crtc 33 (0,0)
[ 0.454669] simple-framebuffer simple-framebuffer.0: [drm:__drm_fb_helper_initial_config_and_unlock] test CRTC 0 primary plane
[ 0.454673] simple-framebuffer simple-framebuffer.0: [drm:drm_fbdev_generic_helper_fb_probe] surface width(1024), height(768) and bpp(32)
[ 0.454689] simple-framebuffer simple-framebuffer.0: [drm:drm_mode_addfb2] [FB:36]
[ 0.455273] fbcon: Deferring console take-over
[ 0.455275] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[…]
[ 2004.373173] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2004.376331] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2004.390797] amdgpu 0000:30:00.0: [drm:drm_mode_rmfb_work_fn] Removing [FB:102] from all active usage due to RMFB ioctl
[ 2004.405834] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2004.409021] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2004.439665] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2004.442282] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[…]
[ 2047.307648] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2047.907916] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2048.507160] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2049.107416] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2049.707577] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2050.306592] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2050.906856] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2051.507220] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2052.106038] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2057.316271] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 1
[ 2097.209611] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2097.211042] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 0
[ 2102.372051] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 1
[ 2157.203897] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2157.204159] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 0
[ 2162.275930] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 1
[ 2217.200778] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:102]
[ 2217.201044] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 0
[ 2222.435722] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 1
[ 2277.197759] amdgpu 0000:30:00.0: [drm:drm_mode_addfb2] [FB:104]
[ 2277.198274] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 0
[ 2282.339738] [drm:vblank_control_worker [amdgpu]] Allow idle optimizations (MALL): 1
What do the drm_mode_addfb2
mean for example?