Superkoning
-
Posts
75 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Superkoning
-
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.
-
I can NOT confirm: I can just run apt install docker.io -y and then docker run -it ubuntu:22.04 /bin/bash and it all works root@nezha:~# docker run -it ubuntu:22.04 /bin/bash Unable to find image 'ubuntu:22.04' locally 22.04: Pulling from library/ubuntu 1edfbf9ed16b: Pull complete Digest: sha256:b6b83d3c331794420340093eb706a6f152d9c1fa51b262d9bf34594887c2c7ac Status: Downloaded newer image for ubuntu:22.04 root@130be7978c79:/# uname -a Linux 130be7978c79 5.19.0-rc1-d1 #trunk Thu Jun 23 10:42:46 MSK 2022 riscv64 riscv64 riscv64 GNU/Linux root@130be7978c79:/# So ... how/when did you get an error?
-
FYI / FWIW: my syslog was full with hostapd logging like below. Annoying. I "solved" that by using armbian-config -> set up the AP ... which failed, but the logging disappeared from my syslog. Jun 25 15:29:34 nezha systemd[1]: hostapd.service: Scheduled restart job, restart counter is at 2195. Jun 25 15:29:34 nezha systemd[1]: Stopped Access point and authentication server for Wi-Fi and Ethernet. Jun 25 15:29:34 nezha systemd[1]: Starting Access point and authentication server for Wi-Fi and Ethernet... Jun 25 15:29:34 nezha hostapd[4725]: Could not open configuration file '/etc/hostapd/hostapd.conf' for reading. Jun 25 15:29:34 nezha hostapd[4725]: Failed to set up interface with /etc/hostapd/hostapd.conf Jun 25 15:29:34 nezha hostapd[4725]: Failed to initialize interface Jun 25 15:29:34 nezha systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE Jun 25 15:29:34 nezha systemd[1]: hostapd.service: Failed with result 'exit-code'. Jun 25 15:29:34 nezha systemd[1]: Failed to start Access point and authentication server for Wi-Fi and Ethernet.
-
Oh, wow ... just replugging worked. Keyboard and ethernet USB adapter are working. Thanks. FWIW: the USB hub is unpowered. So impressive the Dock can power the hub plus keyboard plus ethernet adapter. Jun 25 15:40:18 nezha kernel: [ 5654.678714] usb 4-1: new full-speed USB device number 16 using ohci-platform Jun 25 15:40:18 nezha kernel: [ 5654.907759] usb 4-1: New USB device found, idVendor=058f, idProduct=9254, bcdDevice= 3.12 Jun 25 15:40:18 nezha kernel: [ 5654.907780] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 25 15:40:18 nezha kernel: [ 5654.907791] usb 4-1: Product: Generic USB Hub Jun 25 15:40:18 nezha kernel: [ 5654.907800] usb 4-1: Manufacturer: ALCOR Jun 25 15:40:18 nezha kernel: [ 5654.916213] hub 4-1:1.0: USB hub found Jun 25 15:40:18 nezha kernel: [ 5654.917858] hub 4-1:1.0: 4 ports detected with output of usb-devices T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 16 Spd=12 MxCh= 4 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=058f ProdID=9254 Rev=03.12 S: Manufacturer=ALCOR S: Product=Generic USB Hub C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
-
I have a 2 port USB hub. It works on my laptop with Ubuntu 20.04 and on my laptop with Ubuntu 22.04, but not on my Lichee RV Dock D1 with Ubuntu 22.04: a USB keyboard connected via the USB hub is not working. On my D1, syslog says: Jun 25 14:56:40 nezha kernel: [ 3036.734170] usb 4-1: New USB device found, idVendor=058f, idProduct=9254, bcdDevice= 3.12 Jun 25 14:56:40 nezha kernel: [ 3036.734190] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 25 14:56:40 nezha kernel: [ 3036.734201] usb 4-1: Product: Generic USB Hub Jun 25 14:56:40 nezha kernel: [ 3036.734209] usb 4-1: Manufacturer: ALCOR Jun 25 14:56:40 nezha kernel: [ 3036.741616] hub 4-1:1.0: USB hub found Jun 25 14:56:40 nezha kernel: [ 3036.745592] hub 4-1:1.0: config failed, hub doesn't have any ports! (err -19) When I google "config failed, hub doesn't have any ports! (err -19)" there are a few hits, but very low level tech talk, often related to Raspberry Pi CM4, which didn't help me. On my Ubuntu 20.04 laptop, syslog says Jun 25 15:11:30 witte2004 kernel: [87916.031446] usb 1-1: new full-speed USB device number 14 using xhci_hcd Jun 25 15:11:30 witte2004 kernel: [87916.180513] usb 1-1: New USB device found, idVendor=058f, idProduct=9254, bcdDevice= 3.12 Jun 25 15:11:30 witte2004 kernel: [87916.180521] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 25 15:11:30 witte2004 kernel: [87916.180526] usb 1-1: Product: Generic USB Hub Jun 25 15:11:30 witte2004 kernel: [87916.180531] usb 1-1: Manufacturer: ALCOR Jun 25 15:11:30 witte2004 kernel: [87916.181829] hub 1-1:1.0: USB hub found Jun 25 15:11:30 witte2004 kernel: [87916.181921] hub 1-1:1.0: 4 ports detected Tips how to solve this and make the USB hub working on my D1?
-
Out of curiosity: - does network work? If so, via wifi, or with a ethernet-usb-module? - is the MangoPI pro still for sale? Sold out on Ali, AFAIK
