Superkoning
-
Posts
75 -
Joined
-
Last visited
-
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.
