gamelaster

Hi @Igor and @Werner, I updated the post a bit to clarify it more. Thanks for the notes. Regards, gamiee

On some devices (mostly headless) like Pine A64 LTS and other SBCs with Allwinner SoCs is Lima blacklisted by default or not supported by distribution. For getting Lima work, you need to use distribution, which have already Mesa with Lima support (Mesa 20.1+) (or compile latest Mesa from sources, but this is not included in this tutorial). At the moment of writing, it's Ubuntu Focal and Debian Bullseye. I personally prefer Debian more, so in my case, download Debian Bullseye image for your SBC and burn it into the board. After booting into your board, find file named /etc/modprobe.d/blacklist-NAMEOFYOURSBC.conf (for me it's blacklist-pinea64-lts.conf), find line with: blacklist lima and comment it by adding # at begin of this line, so it will look like this: # blacklist lima Reboot the device and Lima should work finely. If you will have any questions or issues, let me know - gamiee

Sorry, I has been very busy those weeks, but I will try to look on it this christmas holidays. About the workaround, it's very strange why it PWM doing problems, I will check it.

I was testing it yesterday, the OS don't hang, just LCD is disabled for some strange reason. The OS works fine on HDMI display, so I think the patches mess up something about LCD. Today I didn't had much time, so hopefully those days I will find out where is problem. - gamiee

I will try to figure out why it doesn't boot (at least provide dmesg). Yeah, smaeul is working on suspend (since it's highly related to his Crust ARISC Firmware), probably it will be in 4.20.

Hi, Great job Igor. I have working Bluetooth and Audio, it works pretty good (shown on video lower) (Note that this my build uses Anarsoul's kernel with no patches (Only some I kept)). I will make Pull Requests for Bluetooth and Audio support for A64, probably this weekend (Should work also on Teres). Also please, it's possible to add support for test "bleeding edge" images (like this one)?

Hi! I already successfully get mainline Armbian working on Pinebook (no sound - working on fix, and also suspend took much time to wake up), but, I don't like the way how I made it. Github repo: https://github.com/gamelaster/build/tree/pinebook-build I set the branch to "next", I set kernel repository to anarsoul's kernel (contains latest patches for A64 and also for Pinebook & Sopine devices) and deleted all patches from sunxi-next (all that patches has been for 4.14), I just kept and add some of patches. But this is probably terrible idea. @Igor or anyone, can you please me suggest better way to support "next" kernel (The task is to support latest anarsoul's kernel)? I was thinking about changing KERNELFAMILY variable, but really dunno, I'm using Armbian build environment for first time. P.S. the beta automatical build for Pinebook boots u-boot, then kernel, but in kernel is something messed up (the LCD shutdowns after few second of kernel booted), but I will try to fix it, to have "dev" support too Thanks for advices! - gamiee

Hello, I want to ask, which Bluetooth driver is used in mainline kernel for AP6210. I know for WiFi is used brcmfmac. Thank you.