Jump to content

Superkoning

  • Posts

    59
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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
  3. 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?
  4. 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.
  5. 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?
  6. 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.
  7. 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
  8. 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?
  9. 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
  10. With "apt update", I get: N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://cli.github.com/packages stable InRelease' doesn't support architecture 'riscv64' N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease' doesn't support architecture 'riscv64' ... is it safe to disable these two repo's? root@nezha:~# apt update Hit:2 http://ports.ubuntu.com jammy InRelease Hit:3 http://ports.ubuntu.com jammy-security InRelease Hit:4 http://ports.ubuntu.com jammy-updates InRelease Hit:5 http://ports.ubuntu.com jammy-backports InRelease Hit:6 http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy InRelease Hit:1 https://cli.github.com/packages stable InRelease Hit:7 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://cli.github.com/packages stable InRelease' doesn't support architecture 'riscv64' N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease' doesn't support architecture 'riscv64'
  11. Oh, wow, it just works! I downloaded Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0_xfce_desktop.img.xz, burned it to a SD-card with balena-Etcher, put it into my Lichee Dock D1, booted it ... and it worked. Amazing! I connected a 10+ year old USB-to-ethernet adapter, and ethernet was working. Really impressive. Thank you! root@nezha:~# uname -a Linux nezha 5.19.0-rc1-d1 #trunk Fri Jun 17 14:51:17 MSK 2022 riscv64 riscv64 riscv64 GNU/Linux and root@nezha:~# lsusb Bus 004 Device 008: ID 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  12. FWIW: I'm an Armbian user, and, yes, I've done a few donations in the past.
  13. Now that affordable RISC-V SBC's are appearing, are there plans to investigate and possibly support them from Armbian? BeagleV: Beta version has been delivered to developers. Now runs Fedora. Price: 150 USD. Nezha RISC-V SBC: Seems available, see https://www.cnx-software.com/2021/05/20/nezha-risc-v-linux-sbc/ . 99 USD. OS: "Tina, a fork of OpenWrt, officially supported by Allwinner, " ... D1 Linux RISC-V SBC: promised for May, but we have to wait and see. https://www.cnx-software.com/2021/04/13/allwinner-d1-linux-risc-v-sbc-processor/ If it helps, I'm willing to do a small donation.
  14. @usual user Thank you for all your work and time and explanation! You have provided me with a working Armbian Ubuntu on my Cubox, so I'm happy. Thank you
×
×
  • Create New...