Superkoning
-
Posts
79 -
Joined
-
Last visited
-
I want to create an IPv6-mostly gateway. So on the LAN-side only IPv6, and the IPv6-mostly gateway taking care of translating traffic from IPv6 (on the LAN) to IPv4-only servers on Internet. -
Orlando: The OP says "Further steps for initial setup are similar for all Armbian systems." ... so what is the login for Armbian? But ... how about Ubuntu on your Nezha D1: https://canonical-ubuntu-boards.readthedocs-hosted.com/en/latest/how-to/allwinner-nezha-d1/ Works for me.
-
FWIW: on my other RISC-V machine (nezha), squashfs does exist. And this is a kind-of Armbian, made by @balbes150 sander@nezha:~$ lsmod | grep -i squashfs squashfs 98304 0 sander@nezha:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy sander@nezha:~$ sander@nezha:~$ uname -a Linux nezha 6.1.0-rc3-d1 #trunk Thu Dec 1 14:53:18 MSK 2022 riscv64 riscv64 riscv64 GNU/Linux -
I need squashfs for snap, but it seems it's not there. I tried installing libsquashfs-dev, libsquashfs1, libsquashfuse0, squashfs-tools, squashfuse, but no improvement Tips how to solve this? sander@bananapif3:~$ sudo modprobe squashfs modprobe: FATAL: Module squashfs not found in directory /lib/modules/6.1.15-legacy-k1 sander@bananapif3:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Armbian-bpi-SpacemiT 24.5.0-trunk noble Release: 24.04 Codename: noble sander@bananapif3:~$ apt list --installed | grep -i squashfs WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libsquashfs-dev/noble,now 1.2.0-1 riscv64 [installed] libsquashfs1/noble,now 1.2.0-1 riscv64 [installed] squashfs-tools/noble,now 1:4.6.1-1build1 riscv64 [installed] sander@bananapif3:~$ snap install hello-world error: system does not fully support snapd: cannot mount squashfs image using "squashfs": ----- mount: /tmp/syscheck-mountpoint-1699862111: unknown filesystem type 'squashfs'. dmesg(1) may have more information after failed mount system call. -----
-
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.
-
@wba did you read & watch It seems like a big task. But what can I say: that youtube video was already too complicated for me. Other posts https://www.reddit.com/r/RISCV/new/ seem to indicate it also involves the compiler and other tools
-
In the first post of this thread.
-
My system (fully updated and rebooted) shows: sander@nezha:~$ uname -a Linux nezha 6.1.0-rc3-d1 #trunk Thu Dec 1 14:53:18 MSK 2022 riscv64 riscv64 riscv64 GNU/Linux Can I upgrade (easily?) to 6.4.0-rc6-d1 ? If so, how?
-
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.
-
FWIW: someone (an early bird) has received it:
-
You ordered it? Or you already received it?
-
Wifi works on my Lichee RV D1; set up via armbian-config
-
default root password is nothing. So at password, press enter. Oh, in my experience, the login is only possible about a minute or two of showing the login prompt.
-
I tried the below, but it didn't work. However I found a workaround! Boot without HDMI connected, and after booting connect HDMI: low resolution, but everything is in the screen! sander@nezha:~$ sudo find / | grep edid | grep 1920 /usr/lib/firmware/edid/1920x1080.bin /usr/lib/firmware/edid/1920x1200_30hz.bin /usr/lib/firmware/edid/1920x1080_50hz.bin /usr/lib/firmware/edid/1920x1080_24hz.bin /usr/lib/firmware/edid/1920x800.bin /usr/lib/firmware/edid/1920x1200_60hz.bin /usr/lib/firmware/edid/1920x1080_23_976hz.bin So I added drm.edid_firmware=/usr/lib/firmware/edid/1920x1080.bin to /boot/extlinux/extlinux.conf and reboot. But no solution
-
Thanks. Which "startup command line" is that? I tried xrandr ("xrandr -q"), but it says "Can't open display". Mabye because it's running CLI, and not X?