Superkoning
-
Posts
77 -
Joined
-
Last visited
Reputation Activity
-
Superkoning got a reaction from Easy Target in Armbian image and build support for RISC-V.
Yes, RVV 0.7.1 versus RVV 1.0.
Enabling RVV 0.7.1 seems like a minefield / swamp. With a lot of tools that need to be enabled for RVV 0.7.1, and the powers that be are not in favour of that.
On https://www.reddit.com/r/RISCV/new/ follow the wise but sobering words of Bruce Hoult.
-
Superkoning got a reaction from gounthar in Armbian image and build support for RISC-V.
No, I'm not on any list or pre-order.
I'll wait until an all-in price is known (incl EU VAT en shipping). And an install procedure that is feasible for me.
-
Superkoning got a reaction from gounthar in Armbian image and build support for RISC-V.
FWIW: someone (an early bird) has received it:
-
Superkoning got a reaction from balbes150 in Armbian image and build support for RISC-V.
Wifi works on my Lichee RV D1; set up via armbian-config
-
Superkoning reacted to balbes150 in Armbian image and build support for RISC-V.
The latest Ubuntu images use the new kernel, Debian uses the old kernel. The kernel development process is ambiguous and may have different side effects. Try previous versions of Ubuntu.
-
Superkoning got a reaction from Werner in Plans for RISC-V boards like BeagleV, Nezha RISC-V SBC and Allwinner D1 SBC?
FWIW: I'm an Armbian user, and, yes, I've done a few donations in the past.
-
Superkoning got a reaction from lanefu in Plans for RISC-V boards like BeagleV, Nezha RISC-V SBC and Allwinner D1 SBC?
FWIW: I'm an Armbian user, and, yes, I've done a few donations in the past.
-
Superkoning got a reaction from Igor in Plans for RISC-V boards like BeagleV, Nezha RISC-V SBC and Allwinner D1 SBC?
FWIW: I'm an Armbian user, and, yes, I've done a few donations in the past.
-
Superkoning got a reaction from NicoD in FYI: auto-mount USB-disk with "usbmount"
This is a FYI:
My armbian did not automount my USB-disk. Possbile reason "By default, disk drives do not auto-mount in Ubuntu Server Edition.".
Anyway: I solved it with usbmount:
First install usbmount.
Then, in /etc/usbmount/usbmount.conf change the line
#MOUNTOPTIONS="sync,noexec,nodev,noatime,nodiratime"
to
MOUNTOPTIONS="sync,noexec,nodev,noatime,nodiratime,user,umask=0000"
to make it writeable for all users.
HTH
-
Superkoning got a reaction from Igor in Upgrade Armbian Bionic to Cosmic ... is that going to work?
I bought a new 32GB SD-card, put Armbian Bionic on it, and succesfully upgraded to Cosmic.
FWIW:
$ grep -irn cosmic /etc/apt/* | grep -vi "#" /etc/apt/sources.list:1:deb http://ports.ubuntu.com/ cosmic main restricted universe multiverse /etc/apt/sources.list:4:deb http://ports.ubuntu.com/ cosmic-security main restricted universe multiverse /etc/apt/sources.list:7:deb http://ports.ubuntu.com/ cosmic-updates main restricted universe multiverse /etc/apt/sources.list:10:deb http://ports.ubuntu.com/ cosmic-backports main restricted universe multiverse /etc/apt/sources.list.distUpgrade:1:deb http://ports.ubuntu.com/ cosmic main restricted universe multiverse /etc/apt/sources.list.distUpgrade:4:deb http://ports.ubuntu.com/ cosmic-security main restricted universe multiverse /etc/apt/sources.list.distUpgrade:7:deb http://ports.ubuntu.com/ cosmic-updates main restricted universe multiverse /etc/apt/sources.list.distUpgrade:10:deb http://ports.ubuntu.com/ cosmic-backports main restricted universe multiverse
and lines still with Bionic (otherwise I got errors):
$ grep -irn bionic /etc/apt/* | grep -vi "#" /etc/apt/sources.list.d/armbian.list:1:deb http://apt.armbian.com bionic main bionic-utils bionic-desktop /etc/apt/sources.list.d/armbian.list.distUpgrade:1:deb http://apt.armbian.com bionic main bionic-utils bionic-desktop
sander@cubox:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.10 Release: 18.10 Codename: cosmic
And this is what I wanted to achieve:
sander@cubox:~$ openssl version OpenSSL 1.1.1 11 Sep 2018
-
Superkoning got a reaction from chwe in Orange Pi Prime crashes when compiling
I have the same on my NanoPi NEO2: lockup with "make -j4". No problems with "make -j1" (=only use one core). Can you try if that is the same on your system?