• Content Count

  • Joined

  • Last visited

  1. Note also that many build scripts will attempt to use several cores to speed things up, but the RAM-to-core ratio of SBCs is often not very favourable to this. You can usually add an option on the command line (often -j) to set the number of parallel jobs to run. 1 or 2 is probably more suitable than defaults like 4 or "number of cores" or "number of cores + 1".
  2. It's actually listed on the page (the Buster minimal variant): The red X means it's not supported, but it's available.
  3. This probably depends on your specific use case and the specific features you use. In my case I find it very stable, but I don't use any of the video acceleration features for instance, or sound, or cameras, and I haven't tested WiFi much. The only thing I'm waiting for is 3D GPU support.
  4. If by BT you mean Bluetooth like I do, it's working in 5.3 on the Orange Pi 3 using the Armbian nightly, it includes the firmware for the chip, there's just a bit of setup to do. IIRC all that is really needed is the init script available in the package included here: and a little change covered here:
  5. Do you mean you can't get any version of Armbian to run on your Orange Pi 3 at all? I have one that's running very well using the Buster minimal version based on 5.3, including X, Chromium, HDMI output, Ethernet, USB, SPI... I have only tested Wi-Fi very quickly, but it worked out of the box. BT and SPI needed a little bit more configuration. I started from Armbian_5.98.191009_Orangepi3_Debian_buster_dev_5.3.5_minimal but have upgraded several times since. Currently on 5.3.7 5.98.191026. I'm booting directly from SD card, if that matters (no eMMC, 1 GB RAM). Really the only thing I'm missing for now is 3D GPU support (panfrost), other than that it's just perfect, though I don't use video at all so I have no idea of the support on that front. By the way, thanks to all for the really great job!
  6. I think you already have that one, but just in case, output on an Orange Pi 3 (which should be a pretty recent one): SoC bin: slow chip (bin=1) (raw=1)
  7. Ah indeed, I see that it's actually not whitelisted in the mesa panfrost driver. I also see the mesa panfrost driver blacklists Chromium which is my target use case, so it seems the panfrost+mesa route is not yet viable. So what options are there to be able to use the T720 GPU at the moment, if any? * Only using vendor system images such as those provided * Use armbian + binary driver + X11 driver (e.g. as described here: https://linux-sunxi.org/Xorg + https://linux-sunxi.org/Mali_binary_driver)? Is this actually applicable to the T720 or just the Mali 400 (probably with different drivers)? In the latter case (if that is even possible), is there any automated process to achieve that (e.g. download a specific Armbian image, install specific packages...) or is still a very manual process? Thanks in advance for any hints!
  8. I'm not sure I understand the question, but I'm using Panfrost (or at least trying to), which as far as I understand, is the blob-less driver. Not quite sure whether mesa from packages is actually configured with panfrost support, though, is there a way to check that?
  9. Hi, could you provide a few more details about how you got this to work? I just can't get X to use panfrost on my Orange Pi 3, it's stuck on llvmpipe. Kernel: Linux orangepi3 5.3.7-sunxi64 #5.98.191020 SMP Sun Oct 20 02:43:11 CEST 2019 aarch64 GNU/Linux Logs about panfrost: sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff000010becf50) sun4i-drm display-engine: bound 6510000.tcon-top (ops 0xffff000010bf1138) sun4i-drm display-engine: bound 6515000.lcd-controller (ops 0xffff000010be9450) sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff000010bec2f8) [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0 sun4i-drm display-engine: fb0: sun4i-drmdrmfb frame buffer device panfrost 1800000.gpu: clock rate = 432000000 panfrost 1800000.gpu: bus_clock rate = 100000000 panfrost 1800000.gpu: mali-t720 id 0x720 major 0x1 minor 0x1 status 0x0 panfrost 1800000.gpu: features: 00000000,10309e40, issues: 00000000,21054400 panfrost 1800000.gpu: Features: L2:0x07110206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002821 AS:0xf JS:0x7 panfrost 1800000.gpu: shader_present=0x3 l2_present=0x1 [drm] Initialized panfrost 1.0.0 20180908 for 1800000.gpu on minor 1 Mesa is 19.3.0 from packages (it was bumped to this version a few days ago). I added a file /etc/X11/xorg.conf.d/02-panfrost.conf containing: Section "ServerFlags" Option "AutoAddGPU" "off" Option "Debug" "dmabuf_capable" EndSection Section "OutputClass" Identifier "Panfrost" MatchDriver "sun4i-drm" Driver "modesetting" Option "PrimaryGPU" "true" EndSection But still nothing but llvmpipe. Did I miss something? Does the mesa from packages include panfrost support? Should I build from source? If you built from source, what options did you use? Thanks!