Search the Community

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 anyone say where should I continue checking? BR

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.

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'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 OctoPrint, I got an error message about not enough space. When I did a df -m , I had plenty of space on the main partition, I posted on the OctoPrint forum and it was pointed out that my /tmp was tiny. Would anyone have any ideas of what is going on and what I can do to fix it? Here's the OctoPrint Error: Uploading backup, this can take a while. Please wait... Restoring from backup... Unpacking backup to /tmp/tmpf_d22xwu...Removing temporary unpacked folderError while running restoreTraceback (most recent call last): File "/home/ageoffri/OctoPrint/lib/python3.12/site-packages/octoprint/plugins/backup/__init__.py", line 1243, in _restore_backup zip.extract(member, temp) File "/usr/lib/python3.12/zipfile/__init__.py", line 1726, in extract return self._extract_member(member, path, pwd) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/zipfile/__init__.py", line 1802, in _extract_member shutil.copyfileobj(source, target) File "/usr/lib/python3.12/shutil.py", line 204, in copyfileobj fdst_write(buf)OSError: [Errno 28] No space left on device Restore failed! Chec And here's the df -m : Filesystem 1M-blocks Used Available Use% Mounted on tmpfs 198 4 195 2% /run /dev/mmcblk0p1 59861 3078 56137 6% / tmpfs 988 1 988 1% /dev/shm tmpfs 5 0 5 0% /run/lock tmpfs 988 0 988 0% /tmp /dev/zram1 47 3 41 6% /var/log tmpfs 198 1 198 1% /run/user/1000

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 ?

hello, i have a Pine A64 and i have a problem with audio since i installed pulseaudio, i have no audio output and all audio devices are lost and the mouse cursor blinks(g every 0.5 second when i move the mouse

Hi all, I try to work with Pine64 7" inch LCD on Pine64 A64 board but not working I just modify /boot/armbianEnv.txt for add pine64_lcd=on and add the module how is described on the installation iso, but nothing happens. In the boot file I have found dispmode directive because when installed I used hdmi port to see first boot. Please Help me!

I need to use a 10 inch 800x600 DSI display in a Pine64 project and I think the easiest way to do this would be to modify the driver for the Pine 7 inch DSI display. It appears to me that the display resolution is hard coded in this driver (panel-feiyang-07024di26a30d.ko) and not supplied by a device tree overlay like some other Armbian SBCs. In the C source for this driver, I see the following data structure which defines a 1024x600 screen size for the 7 inch display ... static const struct drm_display_mode feiyang_default_mode = { .clock = 55000, .hdisplay = 1024, .hsync_start = 1024 + 310, .hsync_end = 1024 + 310 + 20, .htotal = 1024 + 310 + 20 + 90, .vdisplay = 600, .vsync_start = 600 + 12, .vsync_end = 600 + 12 + 2, .vtotal = 600 + 12 + 2 + 21, .type = DRM_MODE_TYPE_DRIVER | DRM_MODE_TYPE_PREFERRED, }; It looks simple enough to modify these values to work with my 1024x600 display, but I'm unsure what would be the best way to accomplish this. Which of the following could I do? a) Just rebuild the modified driver alone and drop the new .ko file into the filesystem. or b) Do a full Armbian image build using modified feiyang driver source. Building the driver alone seems simpler, but I have zero experience with doing this sort of thing. I've installed the Linux headers package for the Allwinner A64 and piddled with building a trivial hello-world driver as outlined in the "Linux Kernel Module Programming Guide" doc that's floating around on the web. That was easy enough to get working, but have no idea what magic incantations would be needed in the makefile for a real driver. Building the Armbian image is appealing to me because the compile.sh script from the Armbian git repo does all the magic driver building for you. If I can somehow insert a modified version of the feiyang driver source into the OS image build process, that would do what I need. So do either of these approaches make any sense at all and if so, can anyone suggest how to do plan A or plan B? Thanks in advance.

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 i have had my linux box turned of for a very long time and i was trying to run updates but it doesnt seem to want to update, is there something i can do? im very green when it comes to Linux. I tried to do the url command but it didnt work: root@pine64:~# sudo armbianmonitor -u System diagnosis information will now be uploaded to <!doctype html> <html lang=en> <head> <meta charset=utf-8> <title>&nbsp;</title> </head> <style> body { font-family: monospace; margin: 2em; } </style> <body> <p>ix.io is taking a break &#127867;</p> <img src="/underconstruction.gif" width="200px"> </body> </html> ------------------------------------------------------------------------------------------ Here is the update commands i did: root@pine64:~# apt-get update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Hit:3 http://httpredir.debian.org/debian buster-updates InRelease Get:4 https://armbian.github.io/configng stable InRelease [3264 B] Ign:5 http://httpredir.debian.org/debian buster-backports InRelease Err:6 http://httpredir.debian.org/debian buster-backports Release 404 Not Found [IP: 151.101.86.132 80] Hit:7 http://netcup.armbian.com/apt buster InRelease Err:4 https://armbian.github.io/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 Reading package lists... Done E: The repository 'http://httpredir.debian.org/debian buster-backports Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: https://armbian.github.io/configng stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 E: The repository 'https://armbian.github.io/configng stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root@pine64:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@pine64:~# pihole -up [✗] Update local cache of available packages Error: Unable to update package cache. Please try "sudo apt update" root@pine64:~# sudo apt update Hit:1 http://httpredir.debian.org/debian buster InRelease Hit:2 http://httpredir.debian.org/debian buster-updates InRelease Ign:3 http://httpredir.debian.org/debian buster-backports InRelease Hit:4 http://security.debian.org buster/updates InRelease Err:5 http://httpredir.debian.org/debian buster-backports Release 404 Not Found [IP: 151.101.86.132 80] Get:6 https://armbian.github.io/configng stable InRelease [3264 B] Hit:7 http://fi.mirror.armbian.de/apt buster InRelease Err:6 https://armbian.github.io/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 Reading package lists... Done E: The repository 'http://httpredir.debian.org/debian buster-backports Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: https://armbian.github.io/configng stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 E: The repository 'https://armbian.github.io/configng stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root@pine64:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster ---------------------------------------------------------------------------------------------------------------------

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 worked. What else can I try? Armbian_24.5.0-trunk.223_Pine64_trixie_current_6.6.22_minimal.img.xz.log Armbian_24.2.1_Pine64_bookworm_current_6.6.16_minimal.img.xz.log Armbian_23.11.1_Pine64_bookworm_current_6.1.63.img.xz.log Armbian_23.8.1_Pine64_bookworm_current_6.1.47.img.xz.log Armbian_23.5.1_Pine64_bookworm_current_6.1.30.img.xz.log

Hi, on latest Armbian 23.11.1 Bookworm with PINE64 board I noticed those warnings in journal: Feb 12 10:00:45 pine64 systemd[1]: /lib/systemd/system/systemd-journal-upload.service:33: Unknown key name 'RestartSteps' in s> Feb 12 10:00:45 pine64 systemd[1]: /lib/systemd/system/systemd-journal-upload.service:34: Unknown key name 'RestartMaxDelaySec> I suspect the `systemd-journal-upload.service` is not in tact with systemd daemon version installed.

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 the headphone jack and ethernet port aren't working properly on Armbian, though they do work on Manjaro, but perhaps it's best to focus first on getting an official Armbian image to boot on the A64-LTS.) Here's the output of `armbianmonitor -U`: http://paste.debian.net/1266079

Hi, Can anyone tell me how can i remove the wifi and ethernet services completely from the armbian.

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.