-
Upcoming Events
-
-
Volunteering positions
-
Single board computer maintainer
Position: Board maintainerNumber of places: 64Applicants: 70
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
755
Orange Pi Zero 3
oops, I missed reading that 100% cpu, but it is ok it is a a53 after all 😅 videos I'd guess is still 'difficult' on z3, accordingly there is some support for gpu vector graphics but I'd guess mostly just triangles. video decoding can be done with just neon (vector computation) , but i'd guess there is still limited access to video decoding hardware. using neon is likely to give that 100% cpu reading as the cpu is busy literally, using real video hardware would be 'invisible' in a sense, the cpu usage may look low but that one won't see that the video hardware itself may after all be reading 100%. -
2
Can't build box86 or box64 on Orange pi zero 2w
Copying the file over from my rpi zero 2w didn't work. I may try compiling on a different OS on the opi tomorrow to see if that will compile fully. -
6
Manually adding new Mesa & Mali drivers to Armbian (Debain 6.12)
@laibsch It would be good to get this solved as there are a lot of boards out there and they are expensive kit, also this effects both Armbian Ubuntu as well as Debian. I was hapilly running my own Ubuntu Plucky Armbian Unofficial and had desktop functioning fine on my BananaPi-M7 for several apt-get upgrades. I use ssh mainly as I run it as a server for development purposes, but like to use desktop for dev purposes too. Then suddenly the screen went blank and looked like it was continually trying to start up. On reinstalling Armbian Ubuntu Nobel, then Plucky again I worked out that Gnome had been running as v46, but at some point Ubuntu had reverted to v44. I am not sure if this was the breaking change but it seems to at least be parallel. i.e. it was working and I can demonstrate it working and not working repeatedly. Hi @Cesar R. I will run through your repo mods tomorrow and see if I can replicate. It would be good to get this fixed for both Ubuntu and Debian on BananaPi-M7 and Radxa Rock 5B+ and the other boards for Armbian. As I say theres a lot of boards out there and they are expensive. Maybe some of the board manufacturers would pay towards the fix also ? I am just in it for the solution as I need the boards for dev work. -
2
Help wanted setting up OBS Studio using hdmiin as "Video Capture Device" on rock-5b-plus
Been a bit but posting just in case. Doing exactly this with the same image you have downloaded (vendor kernel armbian cinnamon). OBS in bookworm is actually a bit too old (there is a segfault on opening the HDMI In), and the newest version does not run on Bookworm because of a too old ffmpeg. I got this setup working by updating the image to Trixie and compiling OBS myself. OBS (in any capacity) on the Panfrost driver can be launched by setting the GL mode manually using: PAN_MESA_DEBUG=gl3 obs -
144
Jetson Nano
I've just be trying again and have managed to get X running on my Nano. But not very well I fear. My first problem is that the Nano can't read the screen EDID. I get lots of "transfer timed out" errors for i2c-1 in the log. I believe this is the ddc connection to the HDMI port. Has anybody here seen this issue and found a solution ? The killer I hit before was that Xorg would hang when first checking the ports (e.g. /sys/class/drm/card0-HDMI-A-1). What I have found is that removing /dev/dri/* before starting X avoids this hang and I do get my desktop and all works. But it seems awfully risky to delete files such as /dev/dri/* and I'm hoping there's a better way. The hang could be an Xorg bug because the same hang happens on a Raspberry Pi 5 when running a 64-bit system but not when running a 32-bit system. As the Nano can't read the EDID it will default to 1024x768 mode. If I force an EDID using drm.edid_firmware=xxx in the kernel command line I can get 1920x1080 on a small HD screen but not on other 1920x1080 screens I've tried. What could confuse the issue here is that I'm running a custom 6.6.87 kernel and use sysvinit rather than systemd. So perhaps my problems are partially self-inflicted. But I have managed to get my 4GB Nano running X with one monitor. The video driver is only the fbdev driver so how well it works with videos etc. remains to be seen. Cheers, Steven
-
-
Member Statistics