dopabl.blogg.se - Allwinner a64 mainline

#Allwinner a64 mainline how to#
#Allwinner a64 mainline install#
#Allwinner a64 mainline update#
#Allwinner a64 mainline driver#
#Allwinner a64 mainline android#

Trackback: Préparation Olinuxino A64 en serveur headless | Mossroy.

Please can you send your future feedback over our support e-mail This way you can include logs and images and more details. It is kind of hard to keep the communication over wordpress. Typical format doesn’t clear the board from the boot code (since it is stored before the file system). About the NAND – A64 boards never had NAND but eMMC the installation to the eMMC works as expected but as you noticed the board would not boot with boot card inserted – this is expected since the card boot has precedence over eMMC boot, and if you want to use the card as storage medium you need to delete the boot partition stored on the card – remove the card, let the board boot, then insert the card and type “dd if=/dev/zero of=/dev/mmcblk0 bs=512 seek=16 count=1” then test again. Can’t find the broken package that you mentioned.Not sure about the MAC addresses that is under investigation, it seems like indeed only one MAC address is given to all boards. New image was released last Friday (), and I checked about your points in it. You feedback was forwarded to our developers. My current workaround is to put your image on the SD card, modify /boot/armbianEnv.txt on it to set “rootdev=/dev/mmcblk1p1”, and create another partition on the SD-card to put the data, which is not ideal It’s very sad because I’d like to boot on NAND (because it’s fast and reliable), and put all the data (and logs) on the SD-card (because there’s more space and can be easily replaced if necessary).

#Allwinner a64 mainline install#

Last issue : if I install armbian on the NAND (through armbian-config), it works well BUT the board fails to start if I insert an empty SD-card in it : it seems to try to boot on the SD-card, fails (which is normal), but does not fall back to the NAND. It’s still possible to change the MAC address manually in /etc/network/interfaces, but setting it in u-boot would be more generic IMHO. If so, could this option be set in the next version of the image? Maybe u-boot has not been compiled with CONFIG_OVERWRITE_ETHADDR_ONCE to allow it? (see ). If I access u-boot at startup (with the debug USB cable) and try to set it manually, it fails too.

I tried to add something like “ethaddr=XX:XX:XX:XX:XX:XX” in /boot/armbianEnv.txt but it does not work. I have bought several of these boards but they all have the same MAC address 02:BA:7B:D5:C6:6F, which creates a conflict on the network.

It can easily be fixed with “sudo apt install busybox”. There is a broken package dependency in the image. says they’re working fine.Īfter some further testing of this image, I have a few more remarks : Would it be possible to add the patches from !topic/linux-sunxi/JLpU9PqHzvc in your next version? These patches are in the process of being merged in mainline kernel, even if it’s not done yet. I also noticed that hardware encryption/decryption was not enabled in this image (based on “cat /proc/crypto”). I did not seem to have this regression with Armbian_5.75_Lime-a64_Debian_stretch_next_4.19.20.7z image from (even if this image had stability issues when I tested it)Ĭould it “simply” be the CPU frequency? I noticed that cpufreq-info does not manage to read the current CPU frequency on this image, and /sys/devices/system/cpu/cpu*/cpufreq/ does not exist. I’ll try to be more precise if necessary. It’s like the CPU was almost 3 times slower.

I tested the Debian headless version : it looks stable but I noticed a serious regression on CPU performance, compared to the official ubuntu image (with the 3.10.104 kernel : ) Mainline Linux Kernel 5.0 images for A13, A20 and A33 OLinuXino and SOMs is in progress.

#Allwinner a64 mainline how to#

How to build the images is explained here.

#Allwinner a64 mainline driver#

The driver doesn’t support monitoring them.

No CPU thermal. A64 has 3 thermal zones – CPU, GPU0 and GPU1.

#Allwinner a64 mainline update#

We need some time, right now 50MB/s is the max speed to read write instead of 100-200MB/s which the installed eMMC supports, we will update the image soon with HS200/400 modes enabled.

eMMC do not work in the fastest possible mode yet.

So to make the DTS configurations automatic at boot time.

LCDs are not supported yet, HDMI output is only available, we need one more week to figure out how to automatically detect if the Ethernet or LCD are enabled (there is jumper on the board which switch between LCD or Ethernet as both share pins and can’t work together).

There are two images Debian headless or Ubuntu desktop.

#Allwinner a64 mainline android#

Linux kernel 5.0 was just released and as we were working this week to the release of mainline Linux image for A64-OLinuXino (as till now it has the ugly android based 3.10 kernel) we decided to release latest kernel.