There is a lot of complexity in what you are doing, imho unnecessary. All the messing around with keys etc is not needed. And you need to use the 0.7.1 debian downloads with the 202303 release (not 0.7.0 from your steps).
PS; as someone who has been building, releasing and administering unix then linux systems for a loong time; I beg you not to use aptitude. It’s rubbish (in a very complex way).
It’s possible I used the 0.7.1 .sh script. I downloaded it from livinglinux youtube url.
With respect to aptitude, I have found it useful over the years when there are broken packages, aptitude provides alternative steps in a menu to make it easy to deal with. It’s usually able to overcome the issues in this way. It’s some exceptional to use however. In most cases it’s more convenient to use apt-get install, but there are circumstances for me when packages are broken where I find using aptitude helps. What would you use instead?
I have no equivalent tool like this one in dnf or rpm-ostree land to fix broken packages. I either have to rollback or remove packages in those circumstances. What would you use instead in fedora land?
Here is my clinfo output after everything was installed. I’m very happy to see this detected. I wish there were easier documentation to follow to ensure we have everything we need to develop with opencl and gles and vulkan on visionfive 2. I’ll try to build the demos for each again and report back.
Installing the image on a 32GB SD Card. System boots and can be accessed via SSH
But on the display (4K HDMI Display with 3840x2160) there will only be shown a mouse cursor. The cursor cannot be moved by mouse, but system itself stays accessible via ssh.
Which resolutions via HDMI are hardcoded in the image? The I can test it on a more appropriate display? Or are ther any hints to bring it up on the 4K display?
Another question: I have ordered the board with the additional ESWIN6600 USB-Wlan adapter. As the kernel of debian does not officially support this module I would aks if someone has already compiled a loadable .ko module for it.
I would dismiss the hours-lasting recompilation of the kernel
There should be a script in /opt to fix this dreadful aberration. The script should be run immediately after a fresh install. This (202303) release is a show-case for wayland which I abhore. I am old-fashioned and prefer xorg and XFCE.
Logging into the GUI is a two step process. The login manager runs first, by default this is GDM but if you install XFCE and select lightDM when asked, you will get that instead.
It is on this login screen that you get to select which desktop to use.
There is a ‘cog’ icon in the lower right of the GDM login screen. Click and you can select XFCE instead of Gnome.
In LightDM there is a icon in the top bar to select which desktop to use, it not obvious but is to the right, before the accessibility and clock items. This opens a select list of available desktops.
You need to select XFCE specifically, before logging in. Otherwise it remembers your last (default) choice of Gnome + Wayland.
However…
… probably means you have damaged the install enough to need a reinstall.
I can see the USB Wireless dongle (and a lot of messages from it in the kernel logs).
But did anybody manage to take it into AP mode? nmcli seems to try and fail after a while. Is this even supposed to be possible (is the hardware theoretically able to support AP mode)?
How can I switch from Gnome to XFCE in the 202303 image? Gnome is being extremely slow for me in both Wayland and XFCE. Like, it takes 5 seconds to register mouse movement.