(09-12-2018, 06:21 AM)evilbunny Wrote: [ -> ]For what ever reason, only an armhf package exists, not an arm64...
https://packages.debian.org/stretch/ntopng
Thanks for the link. I checked again and noticed that the Debian Buster has an arm64 version.
I tried it and there is only one unsatisfied dependency :
libluajit-5.1-2 (>= 2.0.4+dfsg) needed
I had to install (from Debian buster) :
libluajit-5.1-common
libluajit-5.1-2
ntopng-data_2.4+dfsg1-4
and obviously ntopng_2.4
and then IT WORKS !
I have ntopng running.
Just installed the latest build 0.7.11 with Bionic ARM64 minimal build.
So far I'm impressed. I was using one of the 0.5x stable builds for ages. This one seems much more responsive in relation to it being an always on NAS. Even running the updates and installing them seems quicker. Only downside is reading from my USB3 HDD doesn't go much beyond 40MB/s throughput. So same as the previous build I was using.
(UPDATE: Seems there is a stability issue with this build. Haven't had time to investigate it, but unable to access HDD share or putty to the box). Very simple set of apps on this build.
I installed the last Armbian Debian Buster minimal for Rock64, which works fine but for one point : the STEREO AUDIO DAC ADD-ON BOARD card is not supported. I found that the software necessary to load it was not present, nothing in /usr/local/sbin, and so the command necessary to start the ethernet port does not work :
Code:
/usr/local/sbin/enable_dtoverlay eth1 ethernet@ff550000 okay
I copied the content of the similar directory from the Debian Stretch I used before, and the command is executed. But the card does not take the fixed IP address defined in /etc/network/interfaces.d config file.
This config file is OK because, when I have an USB-Ethernet adapter plugged in on startup, it gets the proper values for eth1 (and the add-on board ethernet port becomes eth2).
If I use the manual configuration with
Code:
ifconfig eth1 192.168.1.184
it works, and everything is running normally. But I have to start manually all the services which were unable to start, because they didn't find eth1 on startup, and this is obviously not a solution for a server which has to run on itself.
Is there a different way to start this ethernet port with Armbian Buster ?
I studied the logs, nothing very clear comes out that. I have attached in a zip file extracts of the syslog and debug log files.
Code:
enable_dtoverlay[690]: Applying...
enable_dtoverlay[690]: /dts-v1/;
enable_dtoverlay[690]: / {
enable_dtoverlay[690]: #011fragment@0 {
enable_dtoverlay[690]: #011#011target-path = "/ethernet@ff550000";
enable_dtoverlay[690]: #011#011__overlay__ {
enable_dtoverlay[690]: #011#011#011status="okay";
enable_dtoverlay[690]: #011#011};
enable_dtoverlay[690]: #011};
enable_dtoverlay[690]: };
(...)
after the list of IRQ POLL:
systemd-udevd[822]: link_config: [b]could not get ethtool features for eth2[/b]
systemd-udevd[822]: Could not set offload features of eth2: Device or resource busy
enable_dtoverlay[690]: Applied!
(...)
kernel: [ 13.402838] of_get_named_gpiod_flags: can't parse 'snps,reset-gpio' property of node '/ethernet@ff550000[0]'
Noob question. There is any way to install Ubuntu Server x64 (amd64) on a RockPro64 board?
(08-26-2019, 05:52 PM)kcirap Wrote: [ -> ]Noob question. There is any way to install Ubuntu Server x64 (amd64) on a RockPro64 board?
No. The RockPro64 (and all the other Pine64 boards/laptops) are not amd64/x86-64 machines. They have ARM processors, much like your smartphone most likely does. Completely incompatible with each other.
Hello,
I'm trying install ARM compiler to compile Blast+ on ARM (
Look here the tutorial that I'm using). I'm using the
Ubuntu 18.04 Bionic Minimal 64bit (arm64) [microSD / eMMC Boot] [0.8.3]. First tun on the fan in maximum RPM using the following command:
Code:
echo 255 >/sys/class/hwmon/hwmon0/pwm
After issue the command above the fan starts up, and then I download ARM compiler from official site, this download 2.3GB tar.gz file and then after unpack I run the install command
Code:
cd ARM-Compiler-for-HPC_19.2_AArch64_Ubuntu_16.04_aarch64/
./arm-compiler-for-hpc-19.2_Generic-AArch64_Ubuntu-16.04_aarch64-linux-deb.sh -a
the command runs well, however at certain point the RockPro64 reboots before complete the installation.
There is any suggestion to fix this?
Hello all! sorry this has already been asked but
Got my first rock64, installed ubuntu-minimal (to test) via PineInstaller with a 32Gb emmc module, ran a lsblk and got this...
why so many partitions?
Is there a reasoning behind this madness or is this just poorly formatted?
Code:
rock64@Rock01:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mtdblock0 31:0 0 4M 0 disk
mmcblk0 179:0 0 29.1G 0 disk
├─mmcblk0p1 179:1 0 3.9M 0 part
├─mmcblk0p2 179:2 0 64K 0 part
├─mmcblk0p3 179:3 0 4M 0 part
├─mmcblk0p4 179:4 0 4M 0 part
├─mmcblk0p5 179:5 0 4M 0 part
├─mmcblk0p6 179:6 0 112M 0 part /boot/efi
└─mmcblk0p7 179:7 0 29G 0 part /
mmcblk0boot0 179:32 0 4M 1 disk
mmcblk0boot1 179:64 0 4M 1 disk
mmcblk0rpmb 179:96 0 4M 0 disk
zram0 252:0 0 248.7M 0 disk [SWAP]
zram1 252:1 0 248.7M 0 disk [SWAP]
zram2 252:2 0 248.7M 0 disk [SWAP]
zram3 252:3 0 248.7M 0 disk [SWAP]
(01-12-2020, 01:39 PM)dpgraham Wrote: [ -> ]Hello all! sorry this has already been asked but
Got my first rock64, installed ubuntu-minimal (to test) via PineInstaller with a 32Gb emmc module, ran a lsblk and got this...
why so many partitions?
Is there a reasoning behind this madness or is this just poorly formatted?
Code:
rock64@Rock01:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mtdblock0 31:0 0 4M 0 disk
mmcblk0 179:0 0 29.1G 0 disk
├─mmcblk0p1 179:1 0 3.9M 0 part
├─mmcblk0p2 179:2 0 64K 0 part
├─mmcblk0p3 179:3 0 4M 0 part
├─mmcblk0p4 179:4 0 4M 0 part
├─mmcblk0p5 179:5 0 4M 0 part
├─mmcblk0p6 179:6 0 112M 0 part /boot/efi
└─mmcblk0p7 179:7 0 29G 0 part /
mmcblk0boot0 179:32 0 4M 1 disk
mmcblk0boot1 179:64 0 4M 1 disk
mmcblk0rpmb 179:96 0 4M 0 disk
zram0 252:0 0 248.7M 0 disk [SWAP]
zram1 252:1 0 248.7M 0 disk [SWAP]
zram2 252:2 0 248.7M 0 disk [SWAP]
zram3 252:3 0 248.7M 0 disk [SWAP]
Bootloaders and other bios'y things live in those partitions on mmcblk0 as arm boards don't have a bios. zram is compressed ram.
Ahh That makes sense, thanks evilbunny!
I guess that's the downside of using an auto-installer, it's a black box
Very cool, was not familiar with the use of zram.
Could anyone point me to a wiki that possible talks about the advantages of four 250M sized zram partitions versus one 1G zram partition? just curious.
edit: Please and thank you!