Pine A64

Does anyone know where i can find linux headers for the LTS/Sopine, or an image that contains them? None of the images from the wiki seem contain the headers. I installed the Armbian legacy with 3.10.107 and was able to get Pine64 headers using apt-get install linux-headers-pine64 but they seem to be missing many files when i try to compile. Any help is greatly appreciated.

What's the current status of 5.30 on Pine64 mainline? I've a spare Pine64 lying around and was considering compiling latest Armbian for it to poke around a little, test things if that's useful to the dev effort. The downloads page lists support as experimental, but the version there is 5.27 and some of the info seems out of date, ie points to the wrong subforum, etc.

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

Hello everybody, since an Softwareupdate some time ago, i m not able to boot up the Pine64 with any Image. It doesnt matter what distro, or what channel. Does anybody have the same issue?

boot0 version : 4.0.0 set pll start set pll end rtc[0] value = 0x00000000 rtc[1] value = 0x00000000 rtc[2] value = 0x00000000 rtc[3] value = 0x00000000 rtc[4] value = 0x00000000 rtc[5] value = 0x00000000 DRAM driver version: V1.1 rsb_send_initseq: rsb clk 400Khz -> 3Mhz Set DRAM_VCC failed initializing SDRAM Fail. HELLO! BOOT0 is starting! boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f

I have PINE A64 WIFI 802.11BGN/BLUETOOTH 4.0 MODULE I can see wifi card but bt is not working Please help me to make this bt module working $ sudo rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no $

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/

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…

I have Armbian up and running very nicely on the PineA64+ 2GB board. Thanks to the community! Speed concerns aside, is it possible to attach a SATA drive to this board? What would be the recommended way to do so? It is the availability of large storage capacity that we need for our project, not blazingly fast disk writes.

Hello, I have Pine64 2GB I want to connect the temperature sensor DS18B20. How to connect it. Sorry for my English

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?

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.

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 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:…

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 .

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 …

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…

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…

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

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…

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:…

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'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?

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.

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 …

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.

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…

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…

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…

I'm currently looking into a new project which will use (hopefully) the Rpi Waveshare hdmi based 4" lcd touch screen, linked to the pine64/Sopine I'm at research stage, and will be looking into using a current 5.x kernel. If anyone has any info on the waveshare lcd's I need to watch out for or suggestions to get further info (specifically the touch driver side), please post a response. Progress on the project will be posted here, links will be added once I have some basics running. This can hopefully open up the waveshare displays to other devices. @Igor Yes I've read This post but am willing to do what I can to get Armbian to support the d…

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?

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…

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…

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.

I've got an Pine64 a that was one of the Kickstarter models. For a couple of years I've been running OctoPrint on it to run my Qidi i-mates 3d printer. Recently I decided to update from jammy to noble, before I did that I made a backup of my OctoPrint settings and files through the OctoPrint GUI in case of problems. I got a really messed inconsistent with all sorts of dependencies errors because the apt dist-upgrade seemed to freeze and after several hours of no movement I rebooted. As expected it was the mess. I spent about an hour on fixing dependencies but decided it just wasn't worth it as the only thing running is OctoPrint. When I went to restore OctoP…

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.

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.

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.…

I have a feeling this was caused by a p[roblem with the definition of ftdfile variable: line from boot.cmd: load ${devtype} 0 ${fdt_addr_r} ${prefix}dtb/allwinner/${fdtfile} from the serial output: File not found /boot/dtb/allwinner/allwinner/sun50i-a64-pine64-plus.dtb ** note the duplication of Allwinner. Since I couldn't find where it was defined , I just copied the allwinner directory into itself.....:-) which fixed the problem. Perhaps someone could look into this? thanks.

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, Can anyone tell me how can i remove the wifi and ethernet services completely from the armbian.

Hi, Thank you all for so much work to fully implement the mainline kernel for the Pine64! So much is now working out-of-the-box with armbian, that there is no need to use the legacy version based on kernel 3.10. The pine64 does have CIR capabilities and the sunxi-cir kernel module is available, but we are still missing DT bindings for the device, although I see that an overlay file is present for the h5: /dts-v1/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target = <0xffffffff>; __overlay__ { pinctrl-names = "default"; …

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…

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

Not sure if this has been reported - the usual way of enabling spi overaly "overlays=spi-spidev and param_spidev_spi_bus=x" seems to be broken and when an overlay fails at boot time, it tries to load the base dtb from /.../alllwinner/allwinner/*, note the extra allwinner in the path - so it fails. The pin definitions for the Euler SPI are wrong. When you manage to get both SPIs up. SPI 0 is being enabled as spi1.0 and SPI 1 being enabled as spi0.0. It also fails to merge board neutral ili9341 SPI definition files (at boot time) that has always worked on H3 and H5 boards. To work around for now, use the following ( spi0.dts, spi1.dts) to get the spidev's up …

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, 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…

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…

Hi everyone! I'm trying to build my own distribution for the Pine64, and I use armbian as a working reference. I'm able to compile ATF + U-boot + Kernel + rootfs and the board actually boots and I get a console over the serial interface and over HDMI. The problem is that GbE Ethernet does not work. It appears that the 8211 phy is not powered. The good guys on the pine64 IRC pointed to the ATF, where the DC1SW regulator should be turned on in order to power the phy. On armbian everything works just fine. I think I messed up something in the build - wrong version / config / dts in either ATF, U-boot or the linux kernel. …

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…

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.

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…