Pine A64

We have initial support for Pine64/Pine64+ for a long time in our repository but not released any official images yet. Since this will change soon a sneak preview what to expect. Hardware related issues: Please don't blame Armbian for the few design flaws Pine64 and Pine64+ show: These boards use Micro USB for DC-IN which is the worst possible decision. Most USB cables have a resistance way too high and are responsible for severe voltage drops when consumption increases, then the tiny Micro USB contacts have also a pretty high contact resistance and also maximum amperage for this connector is limited to 1.8A by USB specs. So in case you want …

Hi, We are currently developing a low cost single board computer base on Allwinner A64 Processor. Please refer to the pine64.com and https://www.kickstarter.com/projects/pine64/577817754?token=12cf383f for more detail on the board. Currently we requesting open source community to participate and help to bring up Linux BSP to Ubuntu. Please let us know if you are interested. Thanks and regards, KH Goh

Hi, I have a couple of these boards which I have been using with Armbian and the old, 3.10 kernel. Ideally I would really like to go mainline as later kernels have some functionality that would be useful for my use of the board. The only remaining reason (apart from cpu freq.) for sticking to the 3.10 kernel has been the lack of MIPI DSI support in mainline, but now I see that, despite the Matrix at http://linux-sunxi.org/Linux_mainlining_effort still being red for A64 mipi, some work is being/has been done by Maxime Ripard. I'm just wondering if anyone here knows if a working mainline kernel with DSI for the Pine 64 is starting to look like a p…

Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)? Thanks a lot for help.

Hello community, I got some brand new Pine H64 Model B this week. Anyone interested in a free test device? Markus

Hi all, I hope someone can help me with an annoying but not pressing eMMC boot problem. Recently I bought myself a Pin64 H64 3GB SBC and an 32GB eMMC module (actually ordered a 16GB but got a 32GB :-) ) I have a Waveshare 7" TFT touchscreen attached. SBC and Screen are powered either a 5V/3A PSU or a batterypack. Now the board boots fine and fast! from a Samsung EVO sd card .. no problems there, but I cannot get the board to boot from the eMMC module. What I have done so far: 1) Flash an Armbian Buster image to the eMMC (using a USB_eMMC converter) with Etcher on Linux Mint... Boot the board from eMMC WITHOUT…

Hi, I am glad you are interested to help us. A long time ago at the end of 2015 the Kickstarter was founded and since middle of 2016 the hardware is available. If you look at our download page of Pine64 you can see that since then we have collected a lot of information of which some of it maybe obsolete/outdated/resolved: https://www.armbian.com/pine64/ Now, if you are a lucky owner of such a SBC you have THE CHANCE to help the armbian project. Will you please download the latest Xenial legacy kernel 3.10.y and verifiy if some of the problems listed on the website are already solved in the current release? And if so, please re…

After a recent (long overdue) update on my pine64 I found that pps-gpio was no longer working. Further investigation found that the default kernel configuration with 4.19.x no longer includes CONFIG_PPS_CLIENT_GPIO (nor CONFIG_PPS_CLIENT_LDISC). Anyone wishing to use pps-gpio (via overlay) will need to configure and build a custom kernel. user@pine64:~$ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=pine64 BOARD_NAME="Pine64" BOARDFAMILY=sun50iw1 VERSION=5.76.190218 LINUXFAMILY=sunxi64 BRANCH=next ARCH=arm64 IMAGE_TYPE=nightly BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image user@pine64:~$ uname -a Linux pine64 4.19.25-sunxi64 #5.76.…

Pardon my noob question, I am still learning. I have been running Armbian on my Pine board for quite some time, now I would like to use it as a NAS. I really have no idea how or where start. thanks

After flashing Armbian 5.20 to my SD card, running apt-get upgrade, it fails to boot with the new kernel. The last thing I get from the console is Image lacks image_size field, assuming 16MiB ## Loading init Ramdisk from Legacy Image at 45300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3845164 Bytes = 3.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 45000000 Booting using the fdt blob at 0x45000000 reserving fdt memory region: addr=45000000 size=200000 reserving fdt memory region: addr=41010000 size=10000 reserving fdt …

Hi, I have a pine64 with the official touch screen, currently running Xenial with legacy kernel. I followed the instructions to enable the touchscreen: Also starting with 5.24 Pine64’s own LCD with touchscreen support can simply be activated in /boot/armbianEnv.txt by setting pine64_lcd=on and adding gt9xxf_ts to /etc/modules followed by a reboot. which works fine. Preferably, I'd like to use a later kernel, as I'm not interested in any graphical HW acceleration but would like some of the other improvements in later kernels. When I tried the instructions with kernel 4.9, I couldn't find the gt9xxf_ts module. Is there any way of making this…

HI, I built the latest images for the Pine64+ & Pine64so - kernel 4.14.x + Debian 9 using the Armbian build scripts and had a problem with the ethernet not operational. Any help would greatly be appreciated. U-Boot SPL 2017.11-armbian (Dec 13 2017 - 23:42:42) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL3-1: Running on A64/H64 (1689) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 23:41:50, Dec 13 2017 NOTICE: Configuring AXP PMIC NOTICE: PMIC: setup successful INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to no…

U-Boot SPL 2019.01-armbian (Apr 08 2019 - 01:44:37 +0200) DRAM: 4096 MiB Trying to boot from MMC1 NOTICE: BL31: v2.1(debug):8a08e27 NOTICE: BL31: Built : 00:11:54, Apr 5 2019 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc06ea70, model: Pine H64 INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 NOTICE: PMIC: AXP805 detected INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services WARNING: BL31: cortex_a53: CPU workaround for 819472 was missing! WARNING: BL31: cortex_a53: CPU workaround for 824069 was missing! WARNING: BL31: cortex_a53: CPU workaround for 827319 …

I am posting the following in the capacity of an errand boy ;) Anarsoul has done a lot of work on the A64 and has custom patches for the Pine A64, SOPine and the Pinebook that have not found their way into mainline yet (his git: https://github.com/anarsoul/). He only does Arch and has no knowledge of Debian/ Ubuntu. I recently asked on Twitter and PINE64 forum which OS users would like to see the Pinebook ship and many users reported Armbian. If anyone would be willing to help incorporate Anarsoul's work into Armbian so that we could have more features working on the aforementioned devices on mainline, then please have a chat with him in the linux-sunxi or pine6…

I suggest relevant discussion continues in this thread. I also urge mods to move relavant posts from here. What is Pinebook ? https://www.pine64.org/?page_id=3707 http://www.cnx-software.com/2016/11/24/pinebook-arm-linux-laptop-powered-by-allwinner-a64-processor-to-sell-for-89-and-up/

Hi, I try to enable sound on headphone jack with pine64+ but i could not Alsa says "no sound found" at dmesg Could anyone help me? Thank you root@pine64:~# dmesg|grep -i sound [ 2.686397] No soundcards found. [ 6.323086] input: sun50i-a64-audio Headset Jack as /devices/platform/sound/sound/card0/input5 root@pine64:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun50ia64audio [sun50i-a64-audio], device 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sun50ia64hdmi [sun50i-a64-hdmi], device 0: 1c22800.i2s…

All, Don´t know if anybody else did it... but I got Bluetooth running by modifying the device tree and adding support for communication between the RTL8723BS and UART1 and loading the needed RTL8723B firmware. Distro: Armbian Buster Kernel version: 5.4.30-sunxi64 This is how I did it: 1) Create a patch (xx.patch) with the next content and place it in ~/build/userpatches/kernel/sunxi-current/ --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-04-06 12:37:45.584912094 +0200 +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-04-06 12:37:45.584912094 +0200 @@ -498,6 +498,21 …

Is there a way to boot the Pine-A64 LTS with Armbian via eMMC? I can use the SD card to boot the armian-Sopine image, but the eMMC memory is not recognized. With the Ayufan image (jessie-minimal) on SD card (https://github.com/ayufan-pine64/linux-build/releases), I can at least recognize the eMMC memory and using sudo dd bs = 30M if = Image / jessie-minimal-sopine-0.7.19-118.img of =/dev/ mmcblk1 copy to the eMMC memory. I removed the SD card and booted with eMMC. I did the same steps with the Armbian image and write the Armbian image on the eMMC (with the Ayufan image on SD card) sudo dd bs=30M if=Image/Armbian_5.38_Pine64so_U…

I've tried searching the forums for info on the Pine H64 Model B, but all the information is rather outdated, so I have some questions: Is this board supported by the images on the Pine H64 page which show a Model A board? (There was mention they work but without ethernet support.) Has ethernet support been fixed in the Pine H64 images for Model B? Are nightly builds still disabled for these boards?

I recently bought a couple of A64-LTS boards from the Pine Store, but I couldn't get the official Armbian images to boot on them. https://www.armbian.com/pine64/ I could, however, get Manjaro to boot on them, and when I created an SD card with U-Boot from the Manjaro SD card, and the partition from the Armbian (Bullseye CLI) image, it booted into Armbian. I noticed, though, that Manjaro distinguishes between the Pine A64(+) and the Pine A64-LTS. Tow-boot also makes the same distinction. So I wondered if maybe Armbian wasn't booting on my A64-LTS boards because it wasn't making that distinction, but it should be. (I also noticed that …

I'm searching for an IDE like VSCode or Atom for my Pine64 with 2GB. I've found a way to install VSCode named Code OSS headmelted, but after 15 minutes the memory gone to be overflow, with the risk to collapse the os. Excluding Geany, is there some IDE that works and can be used for NodeJS/ES6 ?

Ethernet does not appear to be working on the latest versions of Armbian with pine64 512mb model (has only 10/100MBps Eth) Current Version: ARMBIAN 5.83 stable Debian GNU/Linux 9 (stretch) 4.19.38-sunxi64 - I have tried 2 boards in case its a hardware issue, no go. - Ethernet works with Armbian Xenial (3.10 legacy kernel) - The network port shows activity when initially powering up, but when it begins boot lights go out. - I have tried many older and newer kernels, including the new 5.1.0 dev kernel, with no luck. - Eth0 show up with command "ip address" but not with "ifconfig" - When I try running "sudo ethtool eth0" I get error…

I am a bit lost how to create a bootable micro SD card with Armbian version for Pine64 board... I've downloaded Armbian_5.20_Pine64_Debian_jessie_3.10.102.7z file from Armbian site, extracted it using 7Zip on my Windows 7 machine and got following 6 files: armbian.txt armbian.txt.asc Armbian_5.25_Pine64_Debian_jessie_default_3.10.104.img Armbian_5.25_Pine64_Debian_jessie_default_3.10.104.img.asc sha256sum.sha AS I understiid, the *.img file is the disk image itself. However writing it to the SD card (using Etcher, as recommended, as well as Win32DiskImager that I've always used to write Pine64 images, then also tried with Rufus) renders t…

Has anyone gotten the ov5640 camera working with the SOPINE and baseboard? I'm using a prebuilt image from https://www.armbian.com/download/ - Armbian 5.38 stable Ubuntu 16.04.4 LTS 3.10.107-pine64 I've set camera_type=ov5640 in /boot/armbianEnv.txt and rebooted, but I'm having some trouble loading the camera module: Spoiler pi@pine64so:~$ sudo modprobe -r -f ov5640 pi@pine64so:~$ sudo modprobe -r -f vfe_v4l2 pi@pine64so:~$ sudo modprobe ov5640 pi@pine64so:~$ sudo modprobe vfe_v4l2 pi@pine64so:~$ dmesg [ 241.175358] [OV5640@lex]sensor_remove ov5640 sd = ffffffc076b9be00! [ 250.718969] [VFE]vfe_exit [ 250.719007] [VFE]vfe_runtime_resu…

Hello, This is my first attempt to install Armbian on a Pine64 + that I bought 2 weeks ago. I created one from the source, but as the battery management failed, I tried it with a constructed image (Armbian_5.69_Pine64_Debian_stretch_next_4.19.13.img), but it's still the same: everything works fine, except battery management. The state of battery and energy should appear as files in the /sys/class/power/directory, but this directory is not created. I can see this directory and the battery information in other images (like the version of the 3.1 kernel of Ayufan). What I have seen is a strange error (for me) in dmesg, related to the power management modules (axp..…

Hello, I have an A64 2GB ( kickstarter ) with the zwave module in Uart on which I installed the latest version of armbian ( Armbian 24.11.1 Bookworm Minimal ) kernel 6.6.62-current-sunxi64 I have activated the Uart2 via armbian-config but I still can not connect via stty or MinOZW sudo MinOZW /dev/ttyS2 ERROR: Failed to set serial port parameters ERROR: Failed to open serial port /dev/ttyS2 sudo stty -F /dev/ttyS2 115200 Input/output error can you help me ?

5.10.4-sunxi64 pine64 board with goodix 7" mipi-dsi LCD touchscreen. The LCD output is working fine across reboots after enabling the dt overlay using armbian-config. For the touchscreen, I have added "goodix" to /etc/modules and the digitizer works fine from all cold boots: ~$ dmesg | grep -i goodix [ 5.836601] Goodix-TS 1-005d: supply VDDIO not found, using dummy regulator [ 5.843605] Goodix-TS 1-005d: ID k}\xfa, version: 7b6f [ 5.866815] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-005d/input/input5 but a reboot leads to either: [ 5.856172] Goodix-TS 1-005d: supply VDDI…

Hi, Wasn't sure where to start this as it's at-least potentially and partially off-topic regarding Armbian. First of all, thanks for what appears to be the best distro for the small ARM-soc devices, including the PINE64. I really appreciate all the work and houtrs that many people are dedicating to the project. Some history: The Logitech Squeezebox Touch was launched in April 2010) It has 4.3" colour touchscreen Connects to Logitech Media Server (LMS) through Ethernet or Wifi and plays songs stored there or from a wide range of internet sources. Supports 16- and 24-bit audio with a sampling rate of up to 96 kHz (or up to 192 kHz, enabled by us…

Running Armbian Ubuntu Xenial 16.04 on a PineA64, legacy kernel 3.10.105-pine64. Why is it necessary or desirable to put the variable 'ethaddr' in armbianEnv.txt? I thought the hardware mac address would be detected by the kernel. Perhaps not?

Hi. I have a 2GB Pine64+ and have armbian on it. Yes, it's not new, but I noticed the problem only now. It's because my use - in short, I use these boards for hobbyistic low level programming - say an OS loader writing, so it's flash and test, never been looking into linux too deep - only needed utilities. staring at the top is not of that set. Now, when reached the DT parsing, passed by uboot, on this board, my loader, noticed 1GB of RAM... Basically, 1GB, as I see, is a default value set in the dts for pine64-plus yet. The DT is not updated on the fly by uboot, as it looks should be. and when I went to Linux, I saw the same - it sees it as 1GB! …

Hi, I've opened with tag orangepiprime because there was no a64 tag eventhough in the Armbian site is flagged as standard support, tell me if i have to reopen it elsewhere. Anyhow I'm constantly getting kernel panics during boot, I've tested images minimal/cli images starting from 23.5.1 down to 24.5.0 (just downloaded the image and flashed with balena etcher), attached there are all the serial logs of the boot processes, all of them are the same more or less. I've tried: powering from GPIO changing powersupply changing usb cable 4 different uSD cards changing the board hooking it up to a display and none of them …

I recently upgraded my working Pine A64-LTS board to Armbian 10.9 by using standard 'apt-get update' followed by 'apt-get upgrade' The update went fine (no error messages) and i rebooted the unit. The unit was unable to mount the root filesystem it complaint about UUID probably incorrect, but this was not the case. After doing some research i found out that the DTB file was changed on the mmc0 part. The option 'non-removable' was removed wich let to the kernel using the PUSH-PUSH routine? cd pins to see if a SD card is present. It looks like it that not all versions of the Pine A64-LTS have this pin or maybe in the past …

[Photo of LED] http://www13.plala.or.jp/pskitty/img/pa64sysled/DSC_0045-photo-led.jpg [LED holes illustration] http://www13.plala.or.jp/pskitty/img/pa64sysled/pine64-drawing-v2-p6.jpg Hi, this is my first post here, after few first hours with Armbian on a 1G Pine64 board... I did a small initialization script to turn "ON" the System LED (upopulated "LED" label on the board), so that it helps to user to know that the boot process is running... I like to ask the dev team to think about including something like it to the Pine64 Armbian images, since the Pine64 board itself does not provide such indicator, the user is left in…

How can I use / release the ports PC0-PC3 (GPIO 64 - 67) in kernel 4.19? In my project I am using the ports PC0-PC3 (GPIO 64 - 67) for in-circuit programming (with avrdude). Everything was fine until I switched from kernel 4.14 to kernel 4.19. Now the ports are already in use. (Although according to the pine64 schematics nothing is connected to those ports) sudo cat /sys/kernel/debug/pinctrl/1c20800.pinctrl/pinmux-pins ... pin 64 (PC0): device 1c68000.spi function spi0 group PC0 pin 65 (PC1): device 1c68000.spi function spi0 group PC1 pin 66 (PC2): device 1c68000.spi function spi0 group PC2 pin 67 (PC3): device 1c68000.spi fun…

Latest Ubuntu Jammy CLI version and I get: update-initramfs: Generating /boot/initrd.img-5.15.48-sunxi64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for module r8152 after apt upgrade.

Hi! I'm using the Sopine A64 Armbian Buster image version 5.91 in combination with my PineA64-LTS SBC. First off I'd like to say that it runs great, thank you guys very much for providing this fully featured image and thereby keeping this SBC up to date! For the last few weeks I've been trying to get the Pine 64 7" LCD screen to work with it, but so far unfortunately I haven't been able to. What I've tried: Follow instructions to get LCD working as stated on the older brother's PineA64 page: add 'pine64_lcd=on' to /boot/armbianEnv.txt, and add 'gt9xxf_ts' to /etc/modules, then reboot. No luck. Read about the Allwinne…

There was a huge thread a year ago about enabling SPI on Pine64, but it seemed to sometimes apply to longsleep generated kernel vs what I would think would be an out-of-the box build for Pine64 using the Armbian configuration. It wasn't clear to me exactly what needed to be done with today's build configuration, if anything. My ultimate goal is to integrate the IndustrialBerry ENC28J60 dual ethernet port card with Pine64. http://www.industrialberry.com/ethernetberry-v-1-1/ They have a recipe for RaspPi. I'm hoping there might be a similar type of recipe geared to the Pine64. Using the Armbian configurator, I insured the SPI bits were enabled (…

Hi everybody. Does anybody know how can i add the mali driver listed below to the latest Armbian image? Any suggestion would highly appreciated. http://wiki.pine64.org/index.php/Mali_Driver

Hi, I have a Pine64-1gb laying around collecting dust for more that a year and had the idea to replace my RPi3 whitch is now running as a VPN Router. The RPi3 is restricted to 2 streams and cause cpu load to 100% so mabe the Pine64 could help here. As I already setup the RPi3 as VPN Router I thought I use the same procedure for the Pine64 with Armbian Jessie. This is what I use: HW: Pine64 with 1gb ram (Model: PA641GB) OS: ARMBIAN 5.38 stable Debian GNU/Linux 8 (jessie) 3.10.107-pine64 VPN software: OpenVPN VPN Service: PIA Here a small tutorial of the commands that I'v been used to create this VPN Gateway:…

After a reboot, my HDMI does not send anymore signal. The resolution of my desktop (using x11vnc) is 1024x768. This is the pastebin from dmesg: dmesg from Pine64 There are some error on sunxi8. Can someone help me?

Dear friends! I have a project, where I needed to use 4 infrared receivers and 2 transmitters connected to GPIO. After a lot of research I realized how to cook all stuffs together: So I have Pine64 A64 512MB cards (not the plus model), running Armbian 20.05.0-trunk.038 nightly, (uname -r: 5.4.18-sunxi64). I needed to freeze upgrades for two reasons: Boot hangs up: The armbian thinks that I have the plus model: on every upgrade I need to replace the "sun50i-a64-pine64-plus.dtb" file with "sun50i-a64-pine64.dtb" at /boot/dtb/allwinner because the non-plus model (512MB) has different ethernet hardware. Missing gpio-ir-recv kernel module from stock A…

Hi. I have been running mainline on a Pine64 with mipi-dsi lcd Feiyang display since Focal release. I default application ran directly on framebuffer without X, with startup log rolling until the application loaded, but after recent update including kernel 6.6.44 the display is completely black, all the way from boot. I can see that the screen is being identified at boot, but not sure what else to check. Here are relevant lines from dmesg and modules: $ dmesg | grep mipi [ 10.113223] sun6i-mipi-dsi 1ca0000.dsi: Attached device fy07024di26a30d $ lsmod | grep fy0702* panel_feiyang_fy07024di26a30d 12288 0 Please can …

Hello everbody, thank you very much for your comprehensive answers and letting me know that the issue is caused by an EOL fact. So i changed to the recommended builds, but unfortunately it seems that none of it is bootable, or useable, neither Xenial, nor jessie, not even the newest bionic. Is there some sort of general problem that makes those builds unbootlable? Jessie Xenial

I am trying to port my app running on legacy OS to Mainline OS and found some problems: I was able to replicate problem with following actions: 1) git cloned fresh copy of source to new directory - OK 2) edited config-default.conf: KERNEL_ONLY="no" KERNEL_CONFIGURE="no" CLEAN_LEVEL="make,debs,oldcache,images" DEST_LANG="en_US.UTF-8" BOARD="pine64so" BRANCH="next" RELEASE="xenial" BUILD_DESKTOP="yes" KERNEL_KEEP_CONFIG="no" # do not overwrite kernel config before compilation EXTERNAL="no" # build and install extra applications and drivers EXTERNAL_NEW="prebuilt" …

Hey Igor and fellow Armbian forum members! I have worked with Armbian on my OPi PC and used the rtl8192cu-fixed github replacement driver, and recently just edited /etc/modules to include 8192cu(btw apt-get upgrade breaks this). However on my Pine64, dmesg says: rtlwifi/rtl8192cufw.bin isn't available. I have tried manually placing the Debian .bin file into the proper /lib but haven't been able to get the wlan0 to show up under iwconfig(yea I have already enabled it in /etc/network/interfaces. lsusb and lsmod both show some entries for 8912cu. Thanks for any insight, and let's hope we can fix this so that people can use their wifi adapters soon .

Hi, I just installed the Armbian on a Pine A64+ (Armbian Focal, mainline based kernel 5.9.y). I'm having trouble getting audio from the 3.5mm stereo output. I've tried several things, including a speaker test: speaker-test -c 2 -Dsysdefault:sun50ia64audio I tried editing /etc/asound.conf but it doesn't seem to affect anything. Do changes to that file apply instantly? What can I do to test/diagnose the issue?

Using legacy Xenial image on pine64, I found that VPN server could not be executed due to the lack of PPP and IPSEC kernel options and probably other modules. Could be enabled on future releases ? Best regards, Gustavo.

After upgrading from 4.14.70-sunxi64 to 4.19.13-sunxi64 Pine64+ board started to misbehave after running for some time. Dmesg shows: Armbian-release: BOARD=pine64 BOARD_NAME="Pine64" BOARDFAMILY=sun50iw1 VERSION=5.70 LINUXFAMILY=sunxi64 BRANCH=next ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image With Armbian Pine64 3.10 kernel board worked without hanging for 2+ years. I also tried 4.18.xx-sunxi64 kernel from dev branch - same problem.

Yesterday, I upgraded my Pine A64 LTS to the 5.10.21 kernel: The system rebooted just fine, though took longer then before. I didn't realize why until today, when I tried to access /media/mmcboot and discovered that it wasn't there. In fact, there is no /dev/mmcblk0p1 device at all. It's bizarre: it boots from the MicroSD, switches to my SSD, but then the MicroSD card device is simply gone when the system is up. I do not see this on two other Pine A64 (not LTS) systems. I was able to mount the microSD card on one of the other systems, and fsck reported everything was fine. I could also see all of the files just fine. The files …

Hello. I'm a bit confused, i have a PINE64 board ("PINE A64+", 2GB mem.) (this one : https://www.pine64.org/?product=sopine-a64-baseboard-combo) I installed some years ago ARMBIAN on it - everything is running fine. But i'm still on kernel 3.X something : ``` uname -a Linux pine64 3.10.107-pine64 #2 SMP PREEMPT Fri Feb 8 10:23:10 CET 2019 aarch64 GNU/Linux cat /etc/armbian.txt ------------------------------------------------------------------------------- Title: Armbian 5.73 Pine64 Debian jessie default Kernel: Linux 3.10.107 Build date: 28.01.2019 ... ``` …

I am using Armbian Buster on Pine64-LTS units. I recently upgraded version 19.11.3 to 20.02.1 and since having problems with high kworker load and strange warning in dmesg output: [ 7.734729] ------------[ cut here ]------------ [ 7.737084] WARNING: CPU: 1 PID: 30 at drivers/clocksource/arm_arch_timer.c:360 sun50i_a64_read_cntpct_el0+0x24/0x30 [ 7.738928] Modules linked in: cpufreq_dt realtek axp20x_usb_power industrialio pinctrl_axp209 dw_hdmi_cec lima dw_hdmi_i2s_audio gpu_sched dwmac_sun8i mdio_mux [ 7.741485] CPU: 1 PID: 30 Comm: kworker/1:1 Not tainted 5.4.20-sunxi64 #20.02.1 [ 7.743435] Hardware name: Pine64 LTS (DT) [ 7.745514] Wor…

If someone is interested i have compiled some TSLIB deb packages for the Pine64 Touch Screen to work without evdev driver or any other service behind. Advantages: * Easy to install (if you know how to edit xorg.conf) * No service needed * No calibration needed Disadvantages: * works on X11 only Information and deb packages: https://github.com/avafinger/pine64-touchscreen Hope it can be useful.

Hello, I'm using an pine64 with the old mainline Ubuntu server (version 5.32.170911, kernel 4.13) for my project. Thanks for the great work for the Pine64-Armbian! I would like to change to a new image LTS kernel 4.14, because the existing kernel version is no longer supported. Unfortunately I only find the Debian Stretch version on the mainline kernel download server. Is it possible to get a new image with Mainline kernel 4.14 and Ubuntu server? and if not: - If there is no image with 4.14 Ubuntu server, can I change from legacy ubuntu to kernel 4.14? By the way, why ist the mainline-version using debian stretch, but legacy …

I have tried searching but there doesn't seem to be much info on PPS support. It is a standard part of modern kernels and should be pretty consistent. On a Pine64+ using mainline kernel (debian-stretch-next) I chose an interrupt-enabled pin (PH9) updated /boot/armbianEnv.txt with overlays=pps-gpio uart1 uart2 param_pps_pin=PH9 and rebooted. I have a device (a GPS) with its PPS output connected to the Pi2 bus pin 13 that corresponds to PH9 and during boot this appears to be configured as a new PPS source: [ 5.548061] pps pps0: new PPS source pps@0.-1 [ 5.548135] pps pps0: Registered IRQ 145 as PPS source /dev/pps0 is indeed created by udev…

Hi. I am getting a kernel Oops in the Pine64+ . . . .see below. Kernel is 5.8.13-sunxi64. It was installed after a recent update. I would like to drop back to the previous kernel if possible. Does this seem like a reasonable search term for a suitable kernel? Any ideas on searching and installing a previous kernel appreciated. sudo apt-cache search kernel 5.8* | grep sunxi64 linux-dtb-current-sunxi64 - Linux DTB, version 5.8.13-sunxi64 linux-dtb-dev-sunxi64 - Linux DTB, version 5.9.0-rc7-sunxi64 linux-dtb-legacy-sunxi64 - Linux DTB, version 5.4.62-sunxi64 linux-headers-current-sunxi64 - Linux kernel headers for 5.8.13-sunxi64 on arm64…

Hello, I want to monitor the temperature of my Pine64, because I run the pine in an relatively warm environment. Unfortunately, the usual ways do not lead to a reasonable result: I tried the armbianmonitor: "armbianmonitor -m" with this result: Time CPU n/a load %cpu %sys %usr %nice %io %irq CPU 17:08:20: --- 0.00 0% 0% 0% 0% 0% 0% -13552°C 17:08:25: --- 0.00 0% 0% 0% 0% 0% 0% -13673°C and read the file: /sys/devices/virtual/thermal/thermal_zone0/temp: contains the same wrong value -13552 Is there a way to activate the temperature measurement? I am using th…

Hi, Not sure if this is me being stupid or a general problem with the 4.10 kernel: As there are now Mainline 4.10.0-next-20170125 images available from the main Pine64 download page, I tried flashing a spare card to start working on the touchscreen. Neither of the Server images based in 4.10 will boot on my board (no Ethernet activity so I can't ssh in). I also tried updating a working 3.10.104 / 5.25 installation with the dev. 4.x kernel, using the guide: Finally tried with a cross compiled kernel, built using the developer guide: https://docs.armbian.com/Developer-Guide_Build-Preparation/ All with same result: Board apparently doesn't b…

For PINE A64 with Ubuntu Focal (stable and nightly) with a 5 MP camera, the documentation states to add camera_type=s5k4ec to /boot/armbianEnv.txt and reboot. After rebooting, the kernel module is not available. modinfo s5k4ec returns: modinfo: ERROR: Module s5k4ec not found. The file /boot/config-5.9.8-sunxi64 shows that only camera sensors OV2640 and MT9V011 are available and CONFIG_VIDEO_S5K4ECGX is not set. Is this an issue with the build?

Hello, I have an issue, i am running the Pine LTS board on eMMC using Armbian latest stable image. We want to access the serial port on the board, so to test i downloaded putty, i select serial and click open. I get an error when opening this, so i have to run: sudo chmod 777 /dev/tty50 and sudo chmod /dev/tty52 on each boot, then i am able to open the serial port using putty. When i look at the ls -l /dev/tty50 i get: crw--w---- 1 root tty 4, 50 Jan 30 30 16:07 tty50. After etensive research i added my user cst to the tty group, but when i reboot i still have to manually run chmod again to access the serial port. Can someone please …

Hello, today I made an upgrade of my pine64-mainline and failed miserably - my new armbian image won't boot any more. So I did some more tests with a new more different sd-cards, power supply and the mailine kernel form the download site (https://dl.armbian.com/pine64/Ubuntu_xenial_dev_nightly.7z): Again, the same behaviour, the image doesn't bott any more after "apt update" and "apt upgrade". Please, could someone help me with this problem? I hope these lockup logs help in troubleshooting. Thanks a lot! boot-fail-2017-09-06-A.log boot-fail-2017-09-06-B.log

I read in the documentation for the mainline kernel that the upper USB port is configured as OTG by default. ("It’s possible to convert the upper USB port (normally an OTG port) into a full USB host port using an own PHY by setting some magic bits.") See also the post of thkaiser: https://forum.armbian.com/index.php?/topic/1917-armbian-running-on-pine64-and-other-a64h5-devices/&tab=comments#comment-15074 Because I can use the upper USB port, I assume the "magic bits" were configured. But I had problems with the lower USB-Port. The output of "lsusb" gave me: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:…

I believe the TP-Link AC600 wireless usb adapter uses the Mediatek chipset. Has anybody got this running on a Pine A64?

I am using an armbian build image on PINE A64+ board with the kernel 3.10.107. During build i enabled below I2S driver as built-in. CONFIG_SND_SOC_SUNXI_RW=y CONFIG_SND_SOC_SUNXI_AUDIO_DMA=y CONFIG_SND_SOC_SUNXI_TDM=y CONFIG_SND_SUNXI_SOC=y CONFIG_SND_SOC_INTERNAL_AUDIOCODEC=y CONFIG_SND_SOC_INTERNAL_I2S=y CONFIG_SND_SOC_AUDIO_CODEC_MACHINE=y CONFIG_SND_SOC_DAUDIO_PLATFORM=y CONFIG_SND_SOC_VIRCODEC=y CONFIG_SND_SOC_DAUDIO0_MACHINE=y # CONFIG_SND_SOC_DAUDIO1_MACHINE is not set CONFIG_SND_SUNXI_SOC_HDMIAUDIO=y The Internal Audio and HDMI Audio are initialized successfully but failed to snddaudio0 which can be accessed from Euler bus…

Hi, Pine 64's delivery is in full swing and thousands of people are receiving/received their Pine64 boards (Mine is scheduled for May). One of the survey shows that majority of the people have chosen to install linux on their boards. Many people are struggling to find a good image for their boards and current some what stable image is based on already end of life 3.10 kernel and there is promising development by sunxi. I am sure that thousands will get benefited if they get Armbian for Pine64. So How about Armbian for Pine 64? Regards, -- Avinash

vmlinuz-4.20.7-sunxi64 works fine (the Armbianmonitor URL is from that) but 5.1.0 breaks eth: 1c30000.ethernet: Unsupported interface mode: rgmii-txid

I have a Pine64+ 2GB and use Waveshare 3.5 (A). Armbian Bionic Ubuntu installed. I tried to initiate Waveshare screen by following steps: - Enable spidev0.0 from armbianEnv.txt (confirm with /dev/spidev0.0) - modprobe fbtft by: sudo modprobe fbtft_device name=piscreen But I got error with step 2. Here is the output of dmesg [ 4419.154174] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.163004] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.164436] spidev spi0.0: spidev spi0.0 1000kHz 8 bits mode=0x00 [ 4419.164564] spidev spi0.0: Deleting s…

Hi, Thanks to the hard work of your team, the Pine64-plus touchscreen now works great with the mainline kernel and legacy images are no longer listed in the download options, but it looks like some of the instructions at https://www.armbian.com/pine64/ are still referring to the "old way" of doing things: ie: Pine64’s own LCD with touchscreen support can simply be activated in /boot/armbianEnv.txt by setting pine64_lcd=on and adding gt9xxf_ts to /etc/modules followed by a reboot. The LCD screen is now activated by manipulating the DT overlays, which can even be done from armbian-config - hardware, and the touchscreen module is…

LCD support does not appear to be working in the latest builds (stable kernel 5.8.6, development kernel 5.9.7) My understanding is that this has been an issue for a while with A64 boards, specifically the Pine64, but that it was working at one time. Here's what I've tried so far: -Followed instructions at https://docs.armbian.com/Hardware_Allwinner/ and added "setenv video-mode sunxi:480x272-24@60,monitor=lcd,hpd=1,edid=1" to boot.cmd and put "saveenv" at the end, re-compiled boot.scr -Did a modprobe of panel-olimex-lcd-olinuxino -Rebooted several times -Ensured that LCD jumper was closed and verifie…

I tried to get armbian running on my new pine64. Therefore I downloaded the latest two 7z-files for debian and ubuntu. But neither of them does an auto-resize nor does the first boot took more than 30sec - contrary to the documentation. I'm using the SD cards delivered with the pine64 (16GB). In a related post I've found there has been "update-rc filesystem defaults" to (re-)trigger the process (or update.rc). Neither nor I've found. How can I get the distribution created in the correct way on the SD card?

I am currently using the Armbian 20.02 release and doing some tests with the serial ports of a Pine64-LTS board. I noticed that i could not get all the serial ports to work. I needed to make a couple of changes in order to get them all working. Maybe i did something wrong and my changes were not needed, but i still would like to list them here in order to help other users who are having problems with the serial ports. When first starting up the armbian release i used the armbian-config tool to enable the uart 1, uart 2, uart 3 and uart4. I rebooted but noticed not all ports where present. I noticed a message in the dmesg log showi…

Hi have Armbian_5.30_Pine64_Ubuntu_xenial_default_3.10.105_desktop installed and it all works well. How do I configure it so that if no keyboard is plugged in that a virtual keyboard is displayed?

Hi, i'm new with linux and SBC. My final goal is to use the board as a voice command recognition system (without display) and to be honest i do not know how to start. I downloaded Armbian desktop on microSD using balenaEtcher and I inserted it in the board e powered it! i do not have a display unfortunatly and i do not know if desktop version is the best choice or i have to install an embedded version if exists. Could help please? thanks

Hi, I'm trying to use the emmc device located on the Pine64LTS - not neccessarily to boot (though that would be nice). I'm employing a 16GB FORESEE card, which I obtained from the Pine folks. First I installed the Stable SoPine64 Armbian_5.30_Pine64so_Ubuntu_xenial_default_3.10.105 image from the Download web page. When I booted the image from an microSD card, only /dev/mmcblk0 showed up - no /dev/mmcblk1. When I tried to boot from the image loaded on the emmc card, the boot failed. Next I tried to build a more up-to-date image, using: git clone --depth 1 https://github.com/armbian/build cd build ./compile.sh And using the ch…

I have a brand new Pine H64-B. I can get AOSC to start on it, but needed to get Ambian to work. It will partly boot up, but never gets to the the CLI or desktop I have a good SD Card (AOSC works fine, works on a Pi; tried 32G and 128G, ) and power supply. Armbian_5.89.190626_Pineh64_Debian_stretch_dev_5.1.12.img Armbian_5.88_Pineh64_Debian_stretch_dev_5.1.7.img Armbian_5.88_Pineh64_Ubuntu_bionic_dev_5.1.7.img They get up to: Welcome to Debian GNU/Linux 9 (stretch)! ... snip ... [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started udev Kernel Device Manager. [ OK ] Started udev Coldplug all…

Hi, After many attempt to installs and remove various version of teamviewer, I finally was able to make it run successfully. I try to use many architecture package even if they were not supposed to work. The running teamviewer is at the following link. I know it's not supposed to work but it is. https://download.teamviewer.com/download/linux/teamviewer-host_armhf.deb Here kind of command that I used randomly (I know, not really scientific approach!) sudo dpkg --add-architecture amd64 sudo dpkg --add-architecture i386 sudo apt-get install -f sudo apt-get update sudo dpkg --remove-architecture amd64 …

Hi I have been trying to allocate specific gpio's as input via the Device Tree, this ultimately being for a custom made board. I can and have successfully allocated pins PB0, PB1, PB3 & PB5, which are showing in /dev/inputs/by-path and have been verified working with evtest. Working code :- /dts-v1/; /plugin/; / { fragment@0 { target = <&pio>; __overlay__ { input_0: input_0 { pins = "PB0"; function = "gpio_in"; bias-pull-up; }; }; }; fragment@1 { target-path = "/"; __overlay__ { button_1 { compatible = "gpio-keys"; pinctrl-names = "default"…

I just received my Pine A64 LTS V1.2 board, 7" LCD TOUCH SCREEN PANEL, and playbox enclosure. I flashed an sd card with Linux Armbian Focal: https://dl.armbian.com/pine64so/Focal_current If the LCD is connected via the DSI port, the boot freezes during UBoot. If I disconnect the LCD from the DSI connector, we get past the first part of UBoot immediately and it eventually brings me to the login prompt. I do observe that the green power LED appears to light then turn off about when it freezes on boot with the DSI connector attached. I have the official 5 V 2 A SOPINE supply from the store (https://store.pine64.org/product/sopine-baseboard-us-p…

(One liner added later : the problem turned out to be the Cisco SOHO switch. They're "broken from the factory". Not what you'd expect, normally or in particular from Cisco.) Hi, everyone. I've taken the liberty of posting here with regard to my problem as I have the understanding the PINE64 forums proper are run by crazy people; my thought being to stay away from there. So, I have a 1 GB PINE64. I have ethernet performance problems - but NOT, I believe, in any way related to the early production models with their hardware fault or with gigabit ethernet being flakey. My PINE64 is in fact connected to a 100mbit hub, and is …

Hi, I was unable to get static MAC address working on my Pine64. I have the kernel boot argument, console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 panic=10 consoleblank=0 enforcing=0 loglevel=1 mac_addr=3a:bd:50:94:8b:06 But still, the from dmesg, [ 12.954581] sun8i-emac 1c30000.ethernet: device MAC address slot 0 aa:90:02:81:eb:e9 In the interfaces file, auto eth0 iface eth0 inet dhcp hwaddress ether 3a:bd:50:94:8b:06 But this caused error in ifup and system start up (networking cannot start since ifup failed with device in use) Although ifup failed, eth0 is visible in ifconfig, which means something else had already …

Hello! I installed a fresh Armbian (5.31; Server) on my Pine64 yesterday. Today I wanted to start playing around with GPIO ... And it seems like Pin 72 isn't working ... Doing the same on Pin 77, everything works fine ... For the secound test, I used https://github.com/databit/Pine64-CPP. I only added some Debug info to example.cpp. Spoiler Script started on Fri 28 Jul 2017 01:35:44 PM CEST root@pine64:/sys/class/gpio# echo "72" > export bash: echo: write error: Device or resource busy root@pine64:/sys/class/gpio# echo "72" > unexport bash: echo: write error: Invalid argument root@pine64:/sys/class/gpio# ls export gpi…

I'm guessing it wasn't intentional that the current legacy Armbian_5.30_Pine64_Ubuntu_xenial_default_3.10.105 image for the pine64 wouldn't work without the battery? Because the "Warning: Low battery power, shutting down to recharge" line (10th line from the end) is an absolute corker (or should I say showstopper?) when there is no battery connected to the pine64! It fell over on a 2G pine64 board that I was about to build up with Armbian. Spoiler HELLO! BOOT0 is starting! boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f boot0 version : 4.0.0 set pll start set pll end rtc[0] value = 0x00000000 rtc[1] value = 0x00000000 rtc[2] value = 0…

This is an old, original Pine64 Board w/ 1GB RAM. Armbian Version: 5.69 I am unable to get audio signal (output) from the Audio Jack. Tried normal headphone with 3 contacts, also tried headset with 4 contacts, BOTH fail to get audio out. Tried Stretch and also Ubuntu, no success... Does anybody succeed getting audio out from the onboard audio jack with Armbiam? If so, can you give a brief description of the procedure/steps and the soft(s) you are using? When using a external USB Audio adapter everything seems to work fine (connecting to the Adapter Audio Jack), so, I guess that from the point of view of…

As I said in another topic, I'm trying to make bluetooth work with my Pine64 1GB board The other topic is there : Yesterday I tried using `rtk_hciattach` from https://github.com/lwfinger/rtl8723bs_bt That was the program I was using with legacy kernel. After a fresh start (removed the Power USB and plugged it back in) I get this output : root@pine64:~/src/rtl8723bs_bt# ./rtk_hciattach -n -s 115200 /dev/ttyS1 rtk_h5 Realtek Bluetooth init uart with init speed:115200, final_speed:115200, type:HCI UART H5 Realtek Bluetooth :Realtek hciattach version 2.5 Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8 Realtek B…

Mainline stable Armbian stable for Pine64 worked great. I have successfully make my 3.5 TFT screen work but not the touch screen. I read some tutorials, mostly guide. This guide for TFT and Touch is really detailed. For touch: - Step 1: ads7846 driver seems ok - Step 2: ads7846_device there is a warning after make and make install, and it said to skip depmod - After this, I tried sudo modprob ads7846 sudo modprob ads7846_device model=7846 cs=1 gpio_pendown=1 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900 ads7846 is ok (confirmed with lsmod). But ads7846_device return invalid argum…

I am currently developing a custom board which is based of the Pine64/Pine64-R18 dev board. I previously had an issue with the ethernet not working at u-boot level using the sopine based R18 board, this I resolved by patching u-boot with the relevant emac sections that were missing from the device tree. On the custom board we have used the R18 processor with the LAN8720 ethernet-phy chip rather than the RTL8211 used by the pine, and can't get the ethernet to initialise. We have checked rmii clock timings etc and compared the custom board to the Pine and have noticed the following:- MDC has been measured to be running at 18.6Mhz, resultin…

How can I keep the LTS-kernel (4.14) with a terminal command? The lastest update/upgrade installs the kernel 4.17. How can I avoid this kernel-update? For my long term-project I need the LTS-kernel 4.14. Some time ago I updated by mainline-system (Ubuntu server kernel 4.13 to 4.14-kernel with the following command apt-get -y -qq --no-install-recommends install linux-image-next-sunxi64 linux-headers-next-sunxi64 linux-u-boot-pine64-next linux-xenial-root-next-pine64 linux-dtb-next-sunxi64 Thanks a lot.

I'm running Armbian 20.08 Focal on a Pine64 with 2GB RAM. Mostly everything runs fine, but I do have a problem with getting audio out of the headphone plug. In pavucontrol I can see audio is playing (an internet stream) on Built-in Stereo, but nothing can be heard when connecting speakers. To be clear: I don't want audio out of HDMI, but just from the headphone plug. I have also played around with alsamixer and unmuted everything that was muted and turning up the volume, but still no audio to be heard... Has anybody gotten this to work?

Hi, I've tried to change the default console from ttyS0 to ttyS3, using the mainline kernel but I don't get it to work. Modifying boot.cmd I managed to change the tty's baudrate like this: "if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "${consoleargs} console=ttyS0,38400"; fi" after recompiling with "mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr" it gave me an 38400-baud-output begining with line "Loading, please wait...starting version 229" But changing the settings to use ttyS3 does not work at all: "if test "${console}" = "serial" || test "${conso…

problem description as follow: our compile env: root@ubuntu69:/tycom/armbian# uname -a Linux ubuntu69 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu69:/tycom/armbian# cat /etc/os-release NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" Board：PINE H64 Compile Env：from https://github.com/armbian In our compile environment，generate the image file：Armbian_5.67_Pineh64_Debian_stretch_dev_4.19.2.img，we burn it into SD by Etcher，the booting is hang，no error message: Starting kernel ... …

Hi everyone, I'm using Pine64 LTS for a project. According to AXP803 datasheet Page37 & 38, the charge LED indicator can be set to Mode A or Mode B. Does anyone know how to change this setting via sysfs, or other interface(I2c, Uart) ? pine@pine64so:/sys/class/power_supply$ ls axp20x-battery axp813-ac pine@pine64so:/sys/class/power_supply$ cd axp813-ac pine@pine64so:/sys/class/power_supply/axp813-ac$ ls device health input_current_limit online power present subsystem type uevent voltage_min pine@pine64so:/sys/class/power_supply/axp813-ac$ cat uevent POWER_SUPPLY_NAME=axp813-ac POWER_SUPPLY_HEALTH=Good POWER_SUPPLY_PRESENT=1 POWER_SU…

Hello, I'm using a Pine 64 LTS with the SoPine image Armbian 21.02.3 Bionic with Linux 5.4.88-sunxi64 I have made various changes and installations to this image, so I want/need to continue using this image. Unfortunately, with the new hardware of the Pine 64 LTS (Pine64 LTS-V2) network connection is no longer possible. (Note: With the current SoPine image there is a network connection). Is there any way to reinstall the current network drivers in my image? I would be very grateful for any help.

I am trying to display a bootlogo.bmp on boot without success. HDMI and also LCD. I don't mean the four tuxes (pines) on kernel load, i want to display it from u-boot. I am using Armbian 5.26 (don't know why kernel is 3.10.104), upgraded from 5.25. I have placed bootlogo.bmp on /boot but still nothing displayed by u-boot. All my u-boot builds also fails to display it. Has anyone tried it with success?

The notes here, https://www.armbian.com/pine64/ talk about a beta image that has hardware acceleration enabled for the pine64. Unfortunately, the link is no longer valid. Anyone have a link to images I can use with the pine64 that have hardware (2d primarily) that i can use?

I tried to flash the latest Armbian (Armbian_5.52.180715_Pine64_Ubuntu_bionic_dev_4.18.0-rc4) on my A64+. When starting I can't bott and gett one of these error messages: Does anybody have any idea what might go wrong? I know it's not stable yet. After that message, the device waits for an image from a TFTP Server.

An extravagant man of boundless vision-part Raymond Loewy, component Buckminster Fuller, component Willy Wonka, and a smidgen Pepe Le Pew-Philippe Starck is nominally a industrial designer however truly an almost-anything-you-can-think-of designer. >> https://www.facebook.com/Bestmasticatingjuicers.zones He became famous in the 1980s and 90s because of his prong-like toothbrushes and citrus-juicers for Alessi, his sculptural chairs for Kartell, and his revolutionary interiors for Ian Schrager's first creation of boutique resorts, one of them New York's Royalton along with Miami Beach's Delano. Since then, his interests have ranged wider still, from his Sta…

Hi, Since I still couldn't find a enclosure for my Pine64 H64 model-B, I mocked up one myself using a Eur 6,50 Raspberry Pi 4 case. 1) From the USB/ETH connector side I cut out the sections in between the connectors since there is a small offset that pushes the Pine64 board aside when closing the case. 2) From one of the cover lulls, I cut out a section to fit over the IR sensor. 3) On the HDMI side I cut out the two ports holes of the RPI micro hdmi connections and I made a notch in the USB-C hole to fit the power connector of the Pine64. 4) Drilled a hole in the cover large enough for the WIFI/BT antenna connector, on the board,…

Hi, Armbian gurus. I tried latest Armbian image for PineH64-b. (Armbian_20.11_Pineh64-b_focal_current_5.8.16_desktop) And I surprisingly found there is no audio device when I looked around.( by #aplay -l ) Is this expected for now? My older 5.6 kernel has HDMI device at least. I tried search audio problem around but had no discover so far. Please allow me to confirm with you. I'm looking for a good 5.8 multimedia-capable kernel to merge with my gentoo rootfs. Thank you.

By following the instruction how to enable ili9486 on orange pi, I have tried to do that with pine64. So, I installed armbian focal 22.10 with 5.15 kernel, enabled spidev and overlayed dts with tft installation and initialization. But still have a white display. Also I was trying another way to use/edit fbtft, the same issue. `dmesg` shows that spi driver no compatible with ili9486

Hi. Is there no support for btrfs in the latest armbian-ubuntu-xenial for Pine64s? Linux pine54 3.10.104-pine64 #2 SMP PREEMPT Thu Feb 23 22:26:21 CET 2017 aarch64 aarch64 aarch64 GNU/Linux root@pine54:~# mkfs.btrfs /dev/sda1 btrfs-progs v4.4 See http://btrfs.wiki.kernel.org for more information. failed to open /dev/btrfs-control skipping device registration: No such file or directory Label: (null) UUID: d8362fb9-1b9c-4d92-8222-6745f842efcf Node size: 16384 Sector size: 4096 Filesystem size: 7.04GiB Block group profiles: Data: single 8.00MiB Metadata: DUP 368.62MiB Sys…

Hi, Just want to check what the recommended approach is with today's dist-upgrade. I noticed that armbian-bsp-cli-pine64 was held back, so tried a manual install to see what the problem was. Seems like apt wants to remove linux-focal-root-current-pine64 to upgrade armbian-bsp-cli-pine64. Is this a temporary dependency issue? Obviously not performing the upgrade unless informed of the correct approach. BR.