Got errors with cursor freezing in Debian image

So I’ve mentioned this in the Debian forum post, but it seems someone on the Chinese forum is encountering the same issue. That the screen starts, shows cursor and becomes unresponsive. The strangest thing, is that the device actually works while all this is going on.

I’ve narrowed it down and even installed gnome to see if this was a lightdm issue; tried reinstalling lightdm, checked the modetest and seen that my screen supports both 4k and 1080 (it selects 1080, and I tried manually setting via xrandr)

There is nothing in the kernel or xorg logs to suggest what the problem is.

I’ve changed power adapters, peripheral devices, sd cards, added a heatsink; tried a 1080 only screen, tried a TV; tried a HDMI capture card, updated via apt. Nothing fixes this. Do I have a bad unit?

I finally found some errors that look like they might help

root@starfive:/var/log# cat messages | grep err
Jun 10 21:51:52 starfive kernel: [ 0.000000] riscv-intc: unable to find hart id for /cpus/cpu@0/interrupt-controller
Jun 10 21:51:52 starfive kernel: [ 0.000000] riscv-intc: 64 local interrupts mapped
Jun 10 21:51:52 starfive kernel: [ 0.000000] plic: plic@c000000: mapped 136 interrupts with 4 handlers for 9 contexts.
Jun 10 21:51:52 starfive kernel: [ 1.893534] sdhci: Copyright(c) Pierre Ossman
Jun 10 21:51:52 starfive kernel: [ 3.461087] imx219: probe of 6-0010 failed with error -5
Jun 10 21:51:52 starfive kernel: [ 3.784053] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Jun 10 21:51:52 starfive kernel: [ 3.866898] vs-simple-encoder soc:rgb-output: encoder_bind error
Jun 10 21:51:52 starfive kernel: [ 3.889843] vs-simple-encoder soc:dsi-output: encoder_bind error
Jun 10 22:11:21 starfive kernel: [ 0.000000] riscv-intc: unable to find hart id for /cpus/cpu@0/interrupt-controller
Jun 10 22:11:21 starfive kernel: [ 0.000000] riscv-intc: 64 local interrupts mapped
Jun 10 22:11:21 starfive kernel: [ 0.000000] plic: plic@c000000: mapped 136 interrupts with 4 handlers for 9 contexts.
Jun 10 22:11:21 starfive kernel: [ 1.893555] sdhci: Copyright(c) Pierre Ossman
Jun 10 22:11:21 starfive kernel: [ 3.461012] imx219: probe of 6-0010 failed with error -5
Jun 10 22:11:21 starfive kernel: [ 3.790271] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Jun 10 22:11:21 starfive kernel: [ 3.865098] vs-simple-encoder soc:rgb-output: encoder_bind error
Jun 10 22:11:21 starfive kernel: [ 3.888148] vs-simple-encoder soc:dsi-output: encoder_bind error
Dec 23 11:07:49 starfive kernel: [ 0.000000] riscv-intc: unable to find hart id for /cpus/cpu@0/interrupt-controller
Dec 23 11:07:49 starfive kernel: [ 0.000000] riscv-intc: 64 local interrupts mapped
Dec 23 11:07:49 starfive kernel: [ 0.000000] plic: plic@c000000: mapped 136 interrupts with 4 handlers for 9 contexts.
Dec 23 11:07:49 starfive kernel: [ 1.878127] sdhci: Copyright(c) Pierre Ossman
Dec 23 11:07:49 starfive kernel: [ 3.446231] imx219: probe of 6-0010 failed with error -5
Dec 23 11:07:49 starfive kernel: [ 3.772131] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Dec 23 11:07:49 starfive kernel: [ 3.853115] vs-simple-encoder soc:rgb-output: encoder_bind error
Dec 23 11:07:49 starfive kernel: [ 3.876067] vs-simple-encoder soc:dsi-output: encoder_bind error

  1. The debian release note mentions it is an known issue that 4K monitor does not display properly.
  2. Use the only 1080 monitor, enter debian OS, type modetest -M starfive -c to get the monitor edid in console.
1 Like

yeah did that thanks, and it is using 4k monitor in 1080 mode. And it doesn’t work on a 1080 monitor either (same error of freezing cursor). Note that is nothing to do with the resolution.

root@starfive:~# modetest -M starfive -c
Connectors:
id      encoder status          name            size (mm)       modes   encoders
116     115     connected       HDMI-A-1        630x360         13      115
  modes:
        index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
  #0 3840x2160 30.00 3840 4016 4104 4400 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #1 3840x2160 29.97 3840 4016 4104 4400 2160 2168 2178 2250 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 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #6 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
  #7 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #8 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver
  #9 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver
  #10 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver
  #11 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver
  #12 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:
                        00ffffffffffff004c2d1710424a5843
                        261f0103803f24782ac8b5ad50449e25
                        0f5054bfef80714f810081c081809500
                        a9c0b300010108e80030f2705a80b058
                        8a0078682100001e000000fd00324b1e
                        873c000a202020202020000000fc004c
                        5532385235350a2020202020000000ff
                        0048345a523930323232330a20200196
                        020335f04961120313041f10605f2309
                        070783010000e305c0006b030c002000
                        b83c2000200167d85dc401788003e20f
                        81e3060501023a801871382d40582c45
                        0078682100001e023a80d072382d4010
                        2c458078682100001e04740030f2705a
                        80b0588a0078682100001e565e00a0a0
                        a029503020350078682100001a000049
        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:


interesting… i had the same issue with my 4k tv, but with 1080p capture card it stopped freezing

perhaps its not resolution of 4k per se, but something that makes the driver think its 4k and trips the bug?

with a different device (windows/mac/linux) are you able to select higher than 1080p with that monitor?

one thing i found on the chinese forum side, maybe that might help…

[edit] i can confiirm the below snippet works for me on my 4k tv

2 Likes

Thanks.
Are you sure you add line: display-setup-script=xrandr -s 1920x1080 under [Seat:*] in /etc/ligtdm/lightdm.conf ?just like the pictures show?

Exactly. Works with both 55 and 69 debian images. First login attempt always restarts lightdm, so you have to try again. No mouse cursor artifacts, no desktop artifacts. Desktop is slow, probably due to lack of acceleration.

Have the same Problem, none of my Displays work.
On a iiyama 4k Display i get the Black Screen with a Mousecursor that freezes after 5 seconds.
On a Samsung T220 that is capable of 1680x1050 i get no Output at all.

The T220 only have VGA and DVI. I Use a DVI to HDMI Cable.

Output of modetest:

root@starfive:~# modetest -M starfive -c
Connectors:
id      encoder status          name            size (mm)       modes   encoders
116     115     connected       HDMI-A-1        470x300         1       115
  modes:
        index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
  #0 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:
                        00ffffffffffff004c2de50332325754
                        20120103802f1e782aee91a3544c9926
                        0f5054bfef80b30081808140714f0101
                        0101010101017c2e90a0601a1e403020
                        3600da281100001a000000fd00384b1e
                        510e000a202020202020000000fc0053
                        796e634d61737465720a2020000000ff
                        00483958513830373632380a20200025
        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:

I tried several options in /etc/lightdm/lightdm.conf

[Seat:*]
#display-setup-script=xrandr -s 1920x1080
#display-setup-script=xrandr -s 1680x1050
#display-setup-script=xrandr -s 1280x720
display-setup-script=xrandr -s 640x480

Board Revision is 1.3B and Firmware is 2.8.0
Latest debian image fully updated

Hi Joe,

could you please attach output log when you input modetest -M starfive -c to see EDID from your monitor(iiyama), thanks.

Hi Michael,

after powering on today i a login screen but its frozen.

You wantet the edid from my iiyama here it is:

root@starfive:~# modetest -M starfive -c 
Connectors:
id      encoder status          name            size (mm)       modes   encoders
116     115     connected       HDMI-A-1        620x340         18      115
  modes:
        index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
  #0 3840x2160 29.97 3840 4016 4104 4400 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: preferred, driver
  #1 3840x2160 30.00 3840 4016 4104 4400 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #2 3840x2160 25.00 3840 4896 4984 5280 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #3 3840x2160 24.00 3840 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver
  #4 3840x2160 23.98 3840 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver
  #5 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  #6 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver
  #7 1920x1080 50.00 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  #8 1920x1080 24.00 1920 2558 2602 2750 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
  #9 1920x1080 23.98 1920 2558 2602 2750 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver
  #10 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #11 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
  #12 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  #13 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver
  #14 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver
  #15 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver
  #16 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver
  #17 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:
                        00ffffffffffff0026cd027101010101
                        1b180103803e22782a08a5a2574fa228
                        0f5054bfef80e1c0d1c0a9c0d100a940
                        b300818081c0e6730030f2705a80b058
                        8a006d552100001e000000ff00313133
                        33393432373031303737000000fd0017
                        4c1e5c1e000a202020202020000000fc
                        00504c3238383855480a2020202001a9
                        02032ef353100504030207061f141312
                        1116152001dddedf23097f0783010000
                        6d030c001000b83c200060010203e673
                        0030f2705a80b0588a006d552100001e
                        565e00a0a0a02950302035006d552100
                        001b023a801871382d40582c45006d55
                        2100001e011d8018711c1620582c2500
                        6d552100009e00000000000000000092
        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:

I configured lightdm.conf:

[Seat:*]
display-setup-script=xrandr -s 640x480

type or paste code here

And autostart of pixel.sh

#!/bin/sh
xrandr --output HDMI-A-1 --mode 1280x720 -r 50

your monitor is only one resolution? that’s the default value when it cannot get the right EDID

This is from my Samsung T220 (1680x1050)
This Display have only DVI and VGA Connectors.
I use a DVI to HDMI Cable that works with all my other Hardware.

Is it possible to override edid or to show a textmode console?

Yeah, it shows normally for iiyama. but generally. it could be solved by the above workaround.

please try to stop lightdm and modetest it like this:

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

The purpose is to test whether the image can be displayed at this resolution

After following your instructions i get a nice colored Display.

root@starfive:~# modetest -M starfive -D 0 -a -s 116@31:1920x1080 -P 39@31:1920x1080@YUYV -Ftiles
setting mode 1920x1080-60.00Hz on connectors 116, crtc 31
testing 1920x1080@YUYV on plane 39, crtc 31

You just need add display-setup-script=xrandr -s 1920x1080 for /etc/lightdm/lightdm.conf , and then restart lightdm server.

Don’t need add a script that is for tommy’s issues(his monitor has 1080p@120fps mode, so add a boot script to fix framrate to 60fps/50fps etc.) and I don’t know whether it works or not

I disable the pixel.sh script and only let the xrandr line in lightdm.conf.
I rebooted several times because keyboard and mouse not working and promt freezes after some seconds.
But suddently i could type user and password into lightdm and mouse kept working.
After firste login the display got blank and the lightdm login came.
After second try the login to xfce4 is successful.

yes, this is known issue about the first startup requires a second log-in

A ok. Finaly I can report my Hardware as working.

Thank you for your help and keep going the good work. We need open Hardware like this.

P.S. ist there a Browser i can install for the official Debian Build. Firefox and Chromium ar not available per apt.

Have you installed VisionFive2/Engineering Release/Image-69/minimal? Then firefox_105.0_riscv64.deb in the debian-packs should help.

1 Like