A unified reply to a question about the display of debian69

kira · January 6, 2023, 11:17am

Currently there are two main phenomena：

After starting debian, the screen will appear black and a mouse and the mouse cannot move.
Black screen after startup, no mouse.

Corresponding solutions are as follows：
4K display issues：
The 4K monitor will have a black screen and mouse after starting debian, and the mouse will not move.
The main reason is that there is no support for 4K monitors at the moment, if you need to use a 4K monitor you can use the following method (this method will workaround the 4K mode of the monitor and select a resolution of 1920x1080).
1）vi /etc/lightdm/lightdm.conf
2) Add display-setup-script=xrandr -s 1920x1080 under [Seat:*]
3) Reboot the system or type “systemctl restart lightdm”
As shown in the picture:

Black screen after startup, no mouse：

Firstly, see if the green light is flashing, if there is not flashing should not enter the debian system, please update to the latest spl and uboot.
After updating spl and uboot, serial port display into debian system, enter “modetest -M starfive -c” to check if the monitor is connected and the supported resolution.
You can also try using the above method of modifying the resolution.

Thank you all for your support!

aaronfranke · January 6, 2023, 7:04pm

After updating spl and uboot, serial port display into debian system, enter “modetest -M starfive -c” to check if the monitor is connected and the supported resolution.

When I try this on Debian Image 69, I get the message “failed to open device ‘starfive’: No such file or directory”.

However, I will report that the 4K display fix works for my 4K TV, yet I am still unable to connect to my non-TV monitors (tested 1920x1080 and 1680x1050 ones).

tommythorn · January 6, 2023, 8:06pm

I have a black screen with no indication of sync or anything on my fully updated board (yes, spl, uboot, and the 69 debian image, and of course the green LED is blinking). I’ve been using it extensively through ssh. I already posted the result of my modetest -M starfive -c but I’ll repeat it again:

$ sudo modetest -M starfive -c
[sudo] password for tommy: 
Connectors:
id	encoder	status		name		size (mm)	modes	encoders
116	0	connected	HDMI-A-1       	610x350		19	115
  modes:
	index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
  #0 1920x1080 120.00 1920 2008 2052 2200 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver
  #1 1920x1080 119.88 1920 2008 2052 2200 1080 1084 1089 1125 296703 flags: phsync, pvsync; type: driver
  #2 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  #3 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver
  #4 1920x1080 50.00 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  #5 1280x720 120.00 1280 1390 1430 1650 720 725 730 750 148500 flags: phsync, pvsync; type: driver
  #6 1280x720 119.88 1280 1390 1430 1650 720 725 730 750 148352 flags: phsync, pvsync; type: driver
  #7 1280x720 100.00 1280 1720 1760 1980 720 725 730 750 148500 flags: phsync, pvsync; type: driver
  #8 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #9 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
  #10 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #11 1440x576 50.00 1440 1464 1592 1728 576 581 586 625 54000 flags: nhsync, nvsync; type: driver
  #12 1440x480 60.00 1440 1472 1596 1716 480 489 495 525 54054 flags: nhsync, nvsync; type: driver
  #13 1440x480 59.94 1440 1472 1596 1716 480 489 495 525 54000 flags: nhsync, nvsync; type: driver
  #14 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver
  #15 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver
  #16 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver
  #17 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver
  #18 640x480 59.94 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver
  props:
	1 EDID:
		flags: immutable blob
		blobs:

		value:
			00ffffffffffff001c54062701010101
			081e0103803d2378ee11e5ae5044ac25
			0d5054bfcf00d1c0714f81c081408180
			9500b3000101565e00a0a0a029503020
			3500544f2100001e000000fd0030901e
			de3c000a202020202020000000fc0041
			4f5255532046493237510a20000000ff
			003230303830423030303639350a0149
			0203497153020311121304292f0e0f1d
			1e901f3f051461602309170783010000
			67030c002000383c67d85dc401788003
			681a000001013090ece305e301e40f00
			0006e606070162620059e7006aa0a067
			5015203500544f2100001e6fc200a0a0
			a0555030203500544f2100001a977f80
			78703821401c203804544f2100001edf
	2 DPMS:
		flags: enum
		enums: On=0 Standby=1 Suspend=2 Off=3
		value: 0
	5 link-status:
		flags: enum
		enums: Good=0 Bad=1
		value: 0
	6 non-desktop:
		flags: immutable range
		values: 0 1
		value: 0
	4 TILE:
		flags: immutable blob
		blobs:

		value:

In answer to @Michael.Zhu, dmesg showed nothing relevant after running the modetest:

[124626.932348] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[124626.967176] hub 2-2:1.0: USB hub found
[124626.971305] hub 2-2:1.0: 4 ports detected
[124627.081739] usb 1-1.2: new high-speed USB device number 3 using xhci_hcd
[124627.215986] hub 1-1.2:1.0: USB hub found
[124627.220339] hub 1-1.2:1.0: 5 ports detected
[124627.961718] usb 1-1.2.1: new full-speed USB device number 4 using xhci_hcd
[124628.199732] input: C-Media Electronics Inc. USB Advanced Audio Device as /devices/platform/soc/2b000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.2/0003:0D8C:01C2.0001/input/input0
[124628.282151] hid-generic 0003:0D8C:01C2.0001: input: USB HID v1.00 Device [C-Media Electronics Inc. USB Advanced Audio Device] on usb-0000:01:00.0-1.2.1/input2
[124628.451686] usb 1-1.2.4: new full-speed USB device number 5 using xhci_hcd
[124628.660323] hid-generic 0003:048D:8295.0002: device has no listeners, quitting
[124628.771716] usb 1-1.2.5: new high-speed USB device number 6 using xhci_hcd

however upon boot (this time without a display attached), I got:

[   24.030107] vs_gem_dumb_create size = 1000
[   24.034287] Allocated coherent memory, vaddr: 0xFFFFFFE1FB6E6348, paddr: 0x10E8E7000
[   24.042110] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   24.531508] PVR_K:  501: RGX Firmware image 'rgx.fw.36.50.54.182' loaded
[   24.619575] PVR_K:  501: Shader binary image 'rgx.sh.36.50.54.182' loaded
[   24.632673] PVR_K:  501: X connected - (devID = 0)
[   24.830077] vs_gem_dumb_create size = 300000
[   24.835638] Allocated coherent memory, vaddr: 0xFFFFFFE1F97BE0C0, paddr: 0x80200000
[   24.843318] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   24.867122] vs_gem_dumb_create size = 4000
[   24.871345] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B8400, paddr: 0x80058000
[   24.879022] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   24.884773] vs_gem_dumb_create size = 4000
[   24.889030] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B84E0, paddr: 0x8005C000
[   24.896709] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   25.951255] PVR_K:  501: X disconnected - (devID = 0)
[   26.348579] vs_gem_dumb_create size = 1000
[   26.352705] Allocated coherent memory, vaddr: 0xFFFFFFE1FB6E6460, paddr: 0x10E8EC000
[   26.360462] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   26.409359] PVR_K:  755: X connected - (devID = 0)
[   26.439073] vs_gem_dumb_create size = 300000
[   26.444045] Allocated coherent memory, vaddr: 0xFFFFFFE1F97BE0C0, paddr: 0x80200000
[   26.451730] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   26.471126] vs_gem_dumb_create size = 4000
[   26.475349] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B8400, paddr: 0x80058000
[   26.483026] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   26.488922] vs_gem_dumb_create size = 4000
[   26.493095] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B84E0, paddr: 0x8005C000
[   26.500786] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   27.212940] PVR_K:  755: X disconnected - (devID = 0)
[   27.614967] vs_gem_dumb_create size = 1000
[   27.619158] Allocated coherent memory, vaddr: 0xFFFFFFE1FB7641F8, paddr: 0x110CE1000
[   27.626977] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   27.674966] PVR_K:  764: X connected - (devID = 0)
[   27.704721] vs_gem_dumb_create size = 300000
[   27.709624] Allocated coherent memory, vaddr: 0xFFFFFFE1F97BE0C0, paddr: 0x80200000
[   27.717314] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   27.736247] vs_gem_dumb_create size = 4000
[   27.740549] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B8400, paddr: 0x80058000
[   27.748229] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   27.753985] vs_gem_dumb_create size = 4000
[   27.758404] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B84E0, paddr: 0x8005C000
[   27.766078] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   28.453102] PVR_K:  764: X disconnected - (devID = 0)
[   28.850939] vs_gem_dumb_create size = 1000
[   28.855084] Allocated coherent memory, vaddr: 0xFFFFFFE1FB6E8798, paddr: 0x10E98D000
[   28.862843] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   28.912406] PVR_K:  773: X connected - (devID = 0)
[   28.942259] vs_gem_dumb_create size = 300000
[   28.947163] Allocated coherent memory, vaddr: 0xFFFFFFE1F97BE0C0, paddr: 0x80200000
[   28.954823] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   28.974050] vs_gem_dumb_create size = 4000
[   28.978280] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B8400, paddr: 0x80058000
[   28.986013] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   28.991823] vs_gem_dumb_create size = 4000
[   28.996058] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B84E0, paddr: 0x8005C000
[   29.003714] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   29.688962] PVR_K:  773: X disconnected - (devID = 0)
[   30.016386] vs_gem_dumb_create size = 1000
[   30.020511] Allocated coherent memory, vaddr: 0xFFFFFFE1FB6E5350, paddr: 0x10E89E000
[   30.028289] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   30.076385] PVR_K:  782: X connected - (devID = 0)
[   30.106183] vs_gem_dumb_create size = 300000
[   30.111061] Allocated coherent memory, vaddr: 0xFFFFFFE1F97BE0C0, paddr: 0x80200000
[   30.118777] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   30.138085] vs_gem_dumb_create size = 4000
[   30.142391] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B8400, paddr: 0x80058000
[   30.150065] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   30.155848] vs_gem_dumb_create size = 4000
[   30.160017] Allocated coherent memory, vaddr: 0xFFFFFFE1F97B84E0, paddr: 0x8005C000
[   30.167692] ====> vs_gem_alloc_buf, 162.vs_obj->get_pages = 0
[   30.846836] PVR_K:  782: X disconnected - (devID = 0)
[   34.486099] mipi_0p9: disabling

(I have of course booted many times with a monitor attached - same result)

Michael.Zhu · January 7, 2023, 3:47am

thanks @tommythorn , do you mind attached full booting log since I assume the clock of display(1920x1080 120.00fps from your message) is same as that 4k needed. if yes, please modify lightdm.conf as above mentioned

tommythorn · January 8, 2023, 9:34am

I tried that when that was first posted, to no avail:

$ grep -C3 1920x1080 /etc/lightdm/lightdm.conf
# exit-on-failure = True if the daemon should exit if this seat fails
#
[Seat:*]
display-setup-script=xrandr -s 1920x1080
#type=local
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin

Attaching the monitor and power-cycling everything, gets me this verbiage in dmesg. Let me know who else I can try (I have no 1920x1080 monitors):
bootlog.txt (37.3 KB)

FWIW: same monitor and cable works perfectly with host of different boxen.

ADD: I didn’t see anything obviously suspicious in it, but here’s the Xorg.0.log:
Xorg.0.log (17.7 KB)

Michael.Zhu · January 8, 2023, 12:15pm

according to xorg log, I suppose the system is trying to match the monitor with 1080p@120fps. maybe you could change another resolution(e.g. 1280x720) and have a try

tommythorn · January 8, 2023, 12:20pm

Did that: 1280x720, 1440x756, etc, restarting lightdm between changes. Still 100% black, no sync.
I can borrow a 1920x1200 monitor for a temporary experiment. Will report back in a day or so.

tommythorn · January 9, 2023, 6:44am

One Day Later: borrowed a 1920x1200 Benq monitor. Tried both 1920x1080 and 1920x1200 settings in lightdm.conf and got nothing. However, removing the settings completely brought up a login prompt in 640x480 resolution (with the border cut off). I logged in and used a terminal.

dmesg output attached after the three experiments (1920x1200 was last attempt).
new-boot3.log (53.9 KB)

Michael.Zhu · January 9, 2023, 7:35am

yeah, weird. could you please try to boot up with sdimage.img and input modetest -M starfive -D 0 -a -s 116@31:1920x1080 -P 39@31:1920x1080@YUYV -Ftiles or stop the lightdm service in debian and implement above command? thanks.

jorias · January 9, 2023, 5:29pm

Hi,
I get exactly the same bootlog as Tommythorn. Used a native 1920x1080 monitor but without any result. I will try your suggestion, but the sdimage.img is working fine, but is very empty.

jorias · January 10, 2023, 10:10am

I entered this command in the security mode of the 69 image and a colourful screen appeared on the HDMI monitor with diagonal coloured bars.

jorias · January 11, 2023, 12:51pm

I see that there is a new 2.6.0 version. Is there a *.img available?

mzs · January 11, 2023, 1:32pm

My guess would be that it will be released when ready sometime before the Lunar New Year holiday (22nd January to 5th February 2023).

Andres.Jose · January 11, 2023, 2:13pm

Hello.
¿Is it possible to force to other resolution?. Btw, 1280x800 or 1680x1050.
I tried through cvt and xrandr to add both modes with no result.
If this is a controller limitation, please tell me.
Thanks in avance.

kira · January 12, 2023, 2:43am

The supported resolutions that you can find them by entering “modetest -M starfive -c” but only up to 1920x1080.

jorias · January 12, 2023, 1:38pm

lightdm --test-mode --debug gave an error and in:
root@starfive:~# cat /var/log/lightdm/seat0-greeter.log

** (process:4006): WARNING **: 13:21:18.890: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
** Message: 13:21:19.516: Starting lightdm-gtk-greeter 2.0.8 (Aug 17 2021, 15:44:22)
** Message: 13:21:19.517: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf
** Message: 13:21:19.517: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
Failed to launch bus: Failed to connect to session busExcess arguments.

jorias · January 12, 2023, 1:43pm

[+2.63s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+2.63s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=4065
[+2.63s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+2.63s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+2.63s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+2.63s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+2.63s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+2.63s] DEBUG: Registered seat module local
[+2.63s] DEBUG: Registered seat module xremote
[+2.63s] DEBUG: Registered seat module unity
[+2.63s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+2.65s] DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
[+2.65s] DEBUG: Monitoring logind for seats
[+2.65s] DEBUG: New seat added from logind: seat0
[+2.65s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+2.65s] DEBUG: Seat seat0 has property CanMultiSession=no
[+2.65s] DEBUG: Seat seat0: Starting
[+2.65s] DEBUG: Seat seat0: Creating greeter session
[+2.65s] DEBUG: Seat seat0: Creating display server of type x
[+2.66s] DEBUG: Using VT 7
[+2.66s] DEBUG: Seat seat0: Starting local X display on VT 7
[+2.66s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+2.66s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+2.66s] DEBUG: XServer 0: Launching X Server
[+2.66s] DEBUG: Launching process 4070: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+2.66s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+2.66s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+2.66s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+2.67s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+2.67s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+2.67s] DEBUG: User user added
[+4.29s] DEBUG: Got signal 10 from process 4070
[+4.29s] DEBUG: XServer 0: Got signal from X server :0
[+4.29s] DEBUG: XServer 0: Connecting to XServer :0
[+4.33s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+4.33s] DEBUG: Session pid=4076: Started with service ‘lightdm-greeter’, username ‘lightdm’

** (process:4076): WARNING **: 13:41:37.703: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+4.37s] DEBUG: Session pid=4076: Authentication complete with return value 0: Success
[+4.37s] DEBUG: Seat seat0: Session authenticated, running command
[+4.37s] DEBUG: Session pid=4076: Running command /usr/sbin/lightdm-gtk-greeter
[+4.37s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+4.37s] DEBUG: Session pid=4076: Logging to /var/log/lightdm/seat0-greeter.log
[+4.40s] DEBUG: Activating VT 7
[+5.17s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false
[+5.57s] DEBUG: Greeter closed communication channel
[+5.57s] DEBUG: Session pid=4076: Exited with return value 1
[+5.57s] DEBUG: Seat seat0: Session stopped
[+5.57s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+5.57s] DEBUG: Seat seat0: Stopping
[+5.57s] DEBUG: Seat seat0: Stopping display server
[+5.57s] DEBUG: Sending signal 15 to process 4070
[+5.93s] DEBUG: Process 4070 exited with return value 0
[+5.93s] DEBUG: XServer 0: X server stopped
[+5.93s] DEBUG: Releasing VT 7
[+5.93s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+5.93s] DEBUG: Seat seat0: Display server stopped
[+5.93s] DEBUG: Seat seat0: Stopped
[+5.93s] DEBUG: Required seat has stopped
[+5.93s] DEBUG: Stopping display manager
[+5.93s] DEBUG: Display manager stopped
[+5.93s] DEBUG: Stopping daemon
[+5.93s] DEBUG: Exiting with return value 1
root@starfive:~#

tommythorn · January 14, 2023, 8:52am

Hi Michael,

In case this is still relevant, I dropped the linked sdimage.img (containting a buildroot image) on an SDcard, attached my VisionFive 2 to the Asus Aurus FI27Q and powered it up to a black screen as before. Found the IP address and executed the requested command. Note after the output below the command hangs (waited 15 min):

# ps axf|grep lightdm
  657 root     grep lightdm
# modetest -M starfive -D 0 -a -s 116@31:1920x1080 -P 39@31:1920x1080@YUYV -Ftiles
setting mode 1920x1080-120.00Hz on connectors 116, crtc 31
testing 1920x1080@YUYV on plane 39, crtc 31

Michael.Zhu · January 16, 2023, 11:49am

oh, sorry, I forgot the default framerate of your monitor is 120fps. please change the command as below:

modetest -M starfive -D 0 -a -s 116@31:1920x1080-60.00 -P 39@31:1920x1080@YUYV -Ftiles

tommythorn · January 16, 2023, 10:05pm

Progress! Does that mean there is something magic I can put in /etc/lightdm/lightdm.conf to get this to work?
EDIT: FWIW, this was from the debian-69 images with no lightdm running.
EDIT2: curiously it doesn’t work now, even after a reboot. I get “failed to find mode “1920x1080-60.00Hz” for connector 116”