| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Thinking about memory bot...
Forum: General Discussion on Pinebook Pro
Last Post: xiley32050
09-02-2026, 01:21 AM
» Replies: 0
» Views: 114
|
Hardware Feature Suggesti...
Forum: Quartz64 Hardware and Accessories
Last Post: Independent Researcher
08-30-2026, 07:19 PM
» Replies: 0
» Views: 139
|
Single-board computers an...
Forum: General
Last Post: Spaker
08-29-2026, 08:12 PM
» Replies: 0
» Views: 151
|
Pinephone visibly losing ...
Forum: General Discussion on PinePhone
Last Post: baptx
08-29-2026, 11:18 AM
» Replies: 9
» Views: 8,505
|
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
08-28-2026, 01:32 AM
» Replies: 1
» Views: 12,835
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
08-27-2026, 09:15 AM
» Replies: 0
» Views: 170
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 287
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,789
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 464
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 2,101
|
|
|
| Best Clusterboard Distribution |
|
Posted by: AZClusterboard - 03-29-2019, 07:39 PM - Forum: Clusterboard
- Replies (8)
|
 |
Armbian still has not released a new image (even though they've had the fix for over a week now) and I was thinking about maintaining my own distro based on Alpine Linux. It seems to be geared towards lightweight server style hardware. Anyone use something else that is well maintained? Anyone have experience porting it? I saw some threads for other Pine64 products but nothing in Sopine.
(here is their about page in case you've never heard of that distro)
https://alpinelinux.org/about/
|
|
|
|
Armbian - need help, locked out myself by setting backlight to zero |
|
Posted by: UltraBloxX - 03-29-2019, 09:28 AM - Forum: Linux on Pinebook
- Replies (6)
|
 |
Hello!
Armbian has an issue, that it's possible to set backlight to zero, effectively blanking the screen completely. Accidentally, I've pulled the slider in XFCE too much and disabled the backlight completely.
Unfortunately, I'm not sure, how to fix this, because systemd launches unit "restore backlight levels" during the bootup and turns the backlight off right on the boot.
This wouldn't be a much of a problem, but I'm currently on a trip, and I have no MicroSD with another OS to fix the problem (Armbian is installed to eMMC). Somehow, I need to disable backlight restore service, or go into single-user mode, so that I can edit the configuration, but all I currently have access to is an Android smartphone and U-Boot on the Pinebook. Serial console is not an option either.
|
|
|
|
| lost disks |
|
Posted by: chengjianwen - 03-29-2019, 01:39 AM - Forum: General Discussion on ROCKPRO64
- Replies (1)
|
 |
I found the messages in /var/log/syslog:
Mar 29 14:47:05 rockpro64 kernel: [ 5.802114] hdmi-audio-codec hdmi-audio-codec.6.auto: ASoC: Failed to add ELD: -16
Mar 29 14:47:05 rockpro64 kernel: [ 5.803150] rk-hdmi-dp-sound hdmi-dp-sound: multicodec <-> ff8a0000.i2s mapping ok
Mar 29 14:47:05 rockpro64 kernel: [ 5.803864] hdmi-audio-codec hdmi-audio-codec.6.auto: ASoC: Failed to create Playback debugfs file
Mar 29 14:47:05 rockpro64 kernel: [ 5.820672] mali ff9a0000.gpu: Looking up mali-supply from device tree
Mar 29 14:47:05 rockpro64 kernel: [ 5.820941] mali ff9a0000.gpu: Failed to get leakage
Mar 29 14:47:05 rockpro64 kernel: [ 5.821561] mali ff9a0000.gpu: Looking up mali-supply from deviMar 29 14:47:05 rockpro64 kernel: [ 5.678886] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
Mar 29 14:47:05 rockpro64 kernel: [ 5.726767] rockchip-saradc ff100000.saradc: Looking up vref-supply from device tree
Mar 29 14:47:05 rockpro64 kernel: [ 5.726782] rockchip-saradc ff100000.saradc: Looking up vref-supply property in node /saradc@ff100000 failed
Mar 29 14:47:05 rockpro64 kernel: [ 5.726818] ff100000.saradc supply vref not found, using dummy regulator
Mar 29 14:47:05 rockpro64 kernel: [ 5.727583] rockchip-saradc ff100000.saradc: failed to get voltage
Mar 29 14:47:05 rockpro64 kernel: [ 5.728293] rockchip-saradc: probe of ff100000.saradc failed with error -22
Mar 29 14:47:05 rockpro64 kernel: [ 5.801359] rk-hdmi-dp-sound hdmi-dp-sound: control 3:0:0:ELD:0 is already present
Mar 29 14:47:05 rockpro64 kernel: [ 5.802114] hdmi-audio-codec hdmi-audio-codec.6.auto: ASoC: Failed to add ELD: -16
Mar 29 14:47:05 rockpro64 kernel: [ 5.803150] rk-hdmi-dp-sound hdmi-dp-sound: multicodec <-> ff8a0000.i2s mapping ok
Mar 29 14:47:05 rockpro64 kernel: [ 5.803864] hdmi-audio-codec hdmi-audio-codec.6.auto: ASoC: Failed to create Playback debugfs file
Mar 29 14:47:05 rockpro64 kernel: [ 5.820672] mali ff9a0000.gpu: Looking up mali-supply from device tree
Mar 29 14:47:05 rockpro64 kernel: [ 5.820941] mali ff9a0000.gpu: Failed to get leakage
and the two 4T disks attached was lost now.
I disconnected one disk's power supply, the situation don't changed.
|
|
|
|
| MSI-X support for KVM? |
|
Posted by: pfworks - 03-28-2019, 07:31 PM - Forum: Linux on Rock64
- Replies (1)
|
 |
I'm running the ubuntu 18.04 image for the rockpro64. Whenever I try to run a virtual arm host, I always get this no matter what gic_version I use:
libvirtError: internal error: process exited while connecting to monitor: 2019-03-29T01:23:38.158817Z qemu-system-aarch64: -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1: MSI-X is not supported by interrupt controller
I've even tried passing pci=nomsi on the virtual.
Any advice here? I've done the updates, and am wondering if anyone has suggestions before I build the latest libvirt, virt-tools and qemu.
|
|
|
|
| Not able to boot Armbian 5.75@Rock64 4GB |
|
Posted by: wundidajah - 03-28-2019, 01:22 PM - Forum: Linux on Rock64
- Replies (1)
|
 |
Hello,
i'll trying since days to boot following image on my Rock64:
Armbian_5.75_Rock64_Debian_stretch_default_4.4.174
Flashed it via etcher without any problem.
As soon as I boot I'll get after one minte a Exception stack ....
Exception Stack
I'm able to flash and boot Ubuntu 18.04 Bionic minimal 32bit Image.
There I have troubles to find/install the WLAN adapter.
I wanted to buil a Home-SIEM with the Rock64 (https://medium.com/@fbotes2/secure-dns-i...faa85bd833)
My Setup:
ROCK64 SINGLE BOARD COMPUTER
DRAM: 4GB
ROCK64 USB 3.0 Dual Band 1200Mbps WIFI 802.11A/B/G/N/AC (RTL8812AU) Adapter
1 $21.99
32GB CLASS10 MICROSD CARD
Have somebody a clue or hint?
|
|
|
|
big.little cluster not exposed? |
|
Posted by: bavay - 03-28-2019, 07:46 AM - Forum: Linux on RockPro64
- Replies (2)
|
 |
I've installed Ayufan's kernels on Armbian (both 5.0 and 4.20 work great, after fixing a missing link in /boot: uInitrd -> uInitrd-5.0.0-1103-ayufan-g5cdba61f032d).
But I've noticed that cpu-intensive tasks keep moving around the cores as if the operating system has no clue which ones are the big cores and which ones the little ones. I had to run "taskset -p -c 5-6 xxx" to force PID xxx to run on the A72 cores. When I do lscpu, I don't see that there are different classes of cores.
The raid benchmarks (in dmesg, at start of the system) gets results much lower than under Armbian's 4.4.174 kernel, which is consistent with the system running them on A57 cores instead of A72. I'm still using dtb-4.4.174 in /boot, so the kernel can pick the dtb from there.
It seems to have no effect, so I guess, that in Ayufan's kernels the dtb is compiled into the kernel? Has somebody else noticed this?Is there an easy way to use Armbian's DTB (when decompiling Armbian's DTB, it generates a DTS that has much more details than the DTS in Ayufan's kernels)?
Thanks,
Mathias
|
|
|
|
| interface error on OMV |
|
Posted by: chengjianwen - 03-27-2019, 08:19 AM - Forum: General Discussion on ROCKPRO64
- No Replies
|
 |
I installed OMV from ayufan
then I want to config the interface from DHCP to static ip. But When I applied after saved it, there is an "networking.service - Raise network interfaces" error occured.
I logged in and input the "hostname -I" command, it print two ip addresses as:
192.168.0.9 192.168.0.100
the first ip is from dhcp, and the second ip is static ip I hope it to be.
and I input "ifconfig eth0", there is only one ip displayed, it is 192.168.0.9.
So I had to change static ip to dhcp again, and the network is ok now.
So, the question is: how can I set static ip for it?
|
|
|
|
|