Superkoning
-
Posts
78 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Superkoning
-
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?
-
I have a problem with my HP monitor connected via HDMI to my Sipeed Lichee Rv Dock Allwinner D1: When HDMI is connected to my Lichee at boot, the screen is in perfect resolution: 1920x1080 60 Hz, small letters, everything visible. However, but after boot, when I reconnect my monitor again to the Lichee, I only see a part of the output: the lower lines are not in the screen, the characters are bigger. When I then go into the HP settings (via the buttons on the underside of the screen), the HP monitor popup menu says: Current Mode: 1024x768 60Hz Optimal Mode: 1920x1080 60 Hz I tried, but in the HP monitor menu I cannot see a way to change that. I tried different options, but no result. I read https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output and tried "setenv video-mode sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=0", but get "-bash: setenv: command not found". I installed gnulib, but no change. Weird. So tips how to solve this?
-
So that is VisionFive? If VisionFive 2 ... do you own (or: have access to) one already?
-
@balbes150 It indeed works with an Ubuntu image from 2022-07 (july): download&write&boot ... perfect.Thanks! FWIW: Linux version 5.19.0-rc1-d1 EDIT Oh, with "sudo apt update" I get N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://deb.volian.org/volian scar InRelease' doesn't support architecture 'riscv64' volian.org? I disabled that in the repo
-
On my Sipeed Lichee RV: I had Debian running for a few weeks, but wanted Ubuntu. I downloaded Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0.img.xz, burned it to a SD card, booted it: First few boots: USB keyboard not working. Also not after plugging in-and-out And then, on boot #4 and higher: boot says thermal thermal_zone0: cpu-htermal: critical temperature reached down reboot: HARDWARE PROTECTION shutdown (Temperature too high) thermal thermal_zone0: cpu-htermal: critical temperature reached down reboot: HARDWARE PROTECTION shutdown (Temperature too high) thermal thermal_zone0: cpu-htermal: critical temperature reached down reboot: HARDWARE PROTECTION shutdown (Temperature too high) Indeed the D1 is quite warm After disconnecting all cables (HDMI, power, USB), and let the SBC cool off for an hour: the same message on the next boot. I'm now back on the debian version, and all is well. So ... could there be something wrong with Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0.img.xz FWIW: about two months ago, I had an earlier version of Ubuntu on my SBC, working great.
-
@Elrie FWIW: I felt the D1 on my Lichee RV, and it's warm (not hot, not cool). superkoning@nezha:~$ cat /etc/armbianmonitor/datasources/soctemp 44743 So I guess that is "milli" degrees celsius About your setup: without any device connected (no USB, no HDMI), and cooled off, if you boot it, is it hot & locked before it finishes booting?
-
I'm just a user, no expert, and I would try a fresh download & write to another (fresh & new) sd card. Plus check power supply. Oh: and no attached device while booting.
-
From https://www.cnx-software.com/2022/08/01/linux-5-19-release-main-changes-arm-risc-v-and-mips-architectures/ "Linux 5.19 Release – Main changes, Arm, RISC-V and MIPS architectures" I guess we can expect the 5.19 release on our board? RISC-V updates Allwinner D1 DMA and LRADC drivers Implementation of page-based memory attributes Device tree – Enables display engine 2.0 with two mixers, a TCON TOP (with DSI and HDMI), one TCON LCD, and one TCON TV. Support for the Svpbmt extension, which allows memory attributes to be encoded in pages Support for running rv32 binaries on rv64 systems, via the compat subsystem Support for kexec_file() Support for the new generic ticket-based spinlocks, which allows us to also move to qrwlock. These should have already gone in through the asm-geneic tree as well A handful of cleanups and fixes, including some larger ones around atomics and XIP
-
I had to create a new image, and afterwards discovered I had the debian not ubuntu version. So for people like me, I've created an overview: $ lynx --dump 'https://disk.yandex.ru/d/da8qJ8wyE1hhcQ/Nezha_D1/ArmbianTV/20220722' | grep xz Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0.img.xz Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0_icewm_desktop.img.xz Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0_xfce_desktop.img.xz Armbian_22.08.0-trunk_Nezha_sid_current_5.19.0.img.xz Armbian_22.08.0-trunk_Nezha_sid_current_5.19.0_icewm_desktop.img.xz Armbian_22.08.0-trunk_Nezha_sid_current_5.19.0_xfce_desktop.img.xz So: jammy (Ubuntu) versus sid (Debian) ... each with text-only versus icewm versus xfce @balbes150 Why is the directory called ArmbianTV? Does TV stand for Television, or something else?
-
https://mangopi.cc/mangopi_mqpro says "mini HDMI connector", so not micro. I would get one (including USB-C power); much easier than going the UART way. That's the great thing about balbes150's image: HDMI and keyboard and mouse just work.