linhz0hz

I want to run some legacy program written in .NET on some of my arm SBCs. When I run it on the board natively connected to screen, I got same issues drecribed in https://stackoverflow.com/questions/28674759/running-simple-winforms-application-on-mono-for-arm and https://github.com/mono/mono/issues/13049 I tested it does not work on LePotato and Orangepi3B, but works on Rock 5B so I think this is more general than specific board, but not affecting all boards. On the other hand, the program executes correctly when I run it through SSH with X forwarding. It also works with vendor provided image on Orangepi3B and Rock 4B. Some answer in the stackoverflow page suggests that "HW cursor size seems to be actually reported by video driver, so you can probably just try another one, like recent xf86-video-fbdev." So I am not sure if this is related to how armbian or graphic drivers handle certain information. Maybe it is as simple as changing a default cursor size can fix it? I just don't know where to look. This might be more general than specifically LePotato board. I would appreciate any hint / suggestions!

I have a rock 4b+ and I used it as an android box for a while. Then today I tried to flash it with latest armbian image (23.8.1) and it does not boot in microSD or when I flash it through USB OTG. I have erased the SPI flash completely and install the correct spi_loader. It also boots properly with Radxa debian image. Initially I though this is a boot issue, but after checking with a serial cable, it turns out this is a HDMI issue.. After I finish the usual procedure to setup password etc... I got this: Now starting desktop environment... root@rockpi-4b:~# [ 633.211385] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 633.212145] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 633.212986] ff8a0000.i2s-i2s-hifi: ASoC: error at __soc_pcm_open on ff8a0000.i2s-i2s-hifi: -22 [ 639.440718] rockchip-pinctrl pinctrl: pin gpio3-29 already requested by leds; cannot claim for ff880000.i2s [ 639.441636] rockchip-pinctrl pinctrl: pin-125 (ff880000.i2s) status -22 [ 639.442248] rockchip-pinctrl pinctrl: could not request pin 125 (gpio3-29) from group i2s0-8ch-bus-bclk-off on device rockchip-pinctrl [ 639.443344] rockchip-i2s ff880000.i2s: Error applying setting, reverse things back [ 639.444084] rockchip-i2s ff880000.i2s: bclk disable failed -22 Help / hints are highly appreciated!

As a datapoint, I tried one of the archive images and it booted successfully (bookwork edge 6.5.2 xfce) on my sd card. However when I attempted armbian-config install to NVMe (with bootloader written to MTD of course) it did not boot.

I am not familiar with alsamixer, especially with command line interface. But I want to add that I had some touble getting audio through HDMI when I tried the Jammy Gnome / Jammy XFCE images. It was kind of intermittent. I was messing with some settings and I think somehow when I changed to independent volume in L and R channel and changed them back, somehow the sound appeared. I could not reproduce the condition again, but I think you might want to try to tweak a few unrelated settings. Also you might want to check your power supply? I had other board stability issues when I did not give it enough power. I do not know to what extend is the known PD power supply problem solved in current software, but as I was booting from NVMe I could use a PD supply. The other safe bet is to provide 12V supply directly from the pins.

I thought the RK3399 GPU drivers were included in the mainline very very recently? You might not notice it because it was software rendered?

Reporting my experience here: I successfully used this method to flash Jammy xfce/gnome provided under this link: https://stpete-mirror.armbian.com/dl/rock-5b/rc/ Wifi works, I did not test ethernet directly but it was recognized in nmcli. So maybe the problem you see is only a problem of the image you use?