guidol

normally the font and font-size can be reconfigured from the hdmi-console via dpkg-reconfigure console-setup

I also had this issue the last time I reinstalled the build-system. I have a 18MBit line, but do not get from all servers >= 500Kb sec. It depends on the country. As Iam in turkey - most servers are very slow and if I have the chance (like on debian install) I choose the servers in Germany which are much faster for me (up to 1800Kb/sec), but armbian didnt let choose me

I also use a Orange Pi One as PiHole without problems. As Backup a NanoPi A64 is also running here PiHole if the Orange Pi One is down

At the page https://myr2d2build.com/build/issues-91-100/issue-99/ we could see thats the R2D2 Board (which was in Issue 99) is a board from the company named "Orange Pi" named ROBOT v1.2 , but the pictures arent sharp enough to read more. If the Board contains a SDCard and not only emmc then it could be more easy to replace the sounds.

The Kernel 6.0.10 is working for me here. Only got the problems with the not installed DTBs/Overlays - the Neo2 DTBs/Overlays I copied out of the NanoPi A64 install with Kernel 6.0.10 With 6.0.10 I can wait for 6.1 to come Linux npi-neo2-24 6.0.10-sunxi64 #22.11.1 SMP Wed Nov 30 11:26:36 UTC 2022 aarch64 GNU/Linux

Today I had the same problem with my two Neo2 v1.0 After Update/Reboot the director /boot/dtb/allwinner/overlay was completly missing for dtb-6.0.10-sunxi64 (and the directory /boot/dtb-6.0.10-sunxi64/allwinner/ has only -dtb files from the end of Noveber (maybe they are right)) But Iam was in the lucky case that my NanoPi A64 had upgraded successfully to 6.0.10 and all the dtb-files including the overlay-folde for 6.0.10 was there. So I copied these files over to /boot/dtb/allwinner (symbolic link dtb => dtb-6.0.10-sunxi64) and by restarting the Neo2 v1.0 did boot again, because of the missing overlays .dtbo/.scr the Neo2 V1.0 wasnt booting only to emergency mode If anyone need the dtb-directory for sunxi64 and Kernel 6.0.10 I will attach they here at this thread. I dont know whats the difference between the Neo2 and the NanoPi A64 (both sunxi64). The upgrade to 6.0.10 did also work fine on a Orange Pi Zero (sunxi only) allwinner60.zip

@Nefedorov Sorry - I have no clue about it. For the 5102 I corrected the .DTBs with some other user to make it work. I have no idea abot TDM and how to use 4 soundcards at once

Because I didnt want a end0: as eth0: device on my NanoPi A64 I added extraargs=net.ifnames=0 to my /boot/armbianEnv.txt But on bootup the armbian-motd told me RX today: Error: No interface matching "eth0" found in database. The armbian-motd in /etc/default has the line PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -E "en|eth|wl" -m 1)" On the commandline I do get a clear etho with this command: root@npi-a64-116:~# ls -1 /sys/class/net/ | grep -E "en|eth|wl" -m 1 eth0 Where is "the database"? and why have we an end0: device (and not and enx?) [EDIT] found how to add the eth0 to the database (on my other SBCs is was already there). The command is: vnstat --add -i eth0 in the thread System diagnosis information has been uploaded to https://paste.armbian.com/etodezihuf

As Caution-Information: Today I updated a NanoPi Neo 2 v1.1 with armbian bullseye bleeding edge-kernel-setting via apt update/upgrade from Kernel 5.19.16 to 6.0.10 (also from armbian 22.08 to armbian 22.11.1) and had a no-boot after restart serial-TTL-Log after reboot: The problem was (the system did work fine before incl. restart etc), that the file /boot/dtb/allwinner/sun50i-h5-nanopi-neo2-v1.1.dtb was missing - and also the complete directory /boot/dtb/allwinner/overlay/ including /boot/dtb/allwinner/overlay/sun50i-h5-usbhost1.dtbo /boot/dtb/allwinner/overlay/sun50i-h5-usbhost2.dtbo /boot/dtb/allwinner/overlay/sun50i-h5-fixup.scr was also mising I had to open my silver-Neo2-NAS-case, extract the SDCard and copy this file and directory from ym other Neo2 (under kernel 5.19.16) over to the SDcard from ym Neo 2 v1.1 So I dont know if I get the same problem, when I try to update my 2 Neo 2 v1.0 Anyone else had bootup-lockup(s) after the 22.11 update?

I can recommend the USB Image Tool: Info-Page: https://www.alexpage.de/usb-image-tool/ Download at: https://www.alexpage.de/usb-image-tool/download/

I think good informations are also on https://linux-sunxi.org/Jide_Remix_Mini https://linux-sunxi.org/H64

first thing would be t check if the analog-audio is enabled in the .dtb/.dts with the command aplay -l Is there only the HDMI-device listed or also the analog 3.5mm-audio-device?

Maybe I could create (a) overlay(s), but at this time only the following hardware can be toggled via armbian-config -> system -> hardware:

Here is a working (USB-ports & analog Sound) patched sun50i-a64-nanopi-a64 .DTS/.DTB for Kernel 5.18.15 under armbian bullseye Dont know why these arent automatically configured at armbian/kernel-compile _ _ ____ _ _ __ _ _ | \ | | _ \(_) / \ / /_ | || | | \| | |_) | | / _ \| '_ \| || |_ | |\ | __/| | / ___ \ (_) |__ _| |_| \_|_| |_| /_/ \_\___/ |_| Welcome to Armbian 22.08.0-trunk Bullseye with Linux 5.18.15-sunxi64 No end-user support: community creations System load: 2% Up time: 16 min Local users: 2 Memory usage: 14% of 984M IP: 192.168.6.116 CPU temp: 27°C Usage of /: 24% of 15G RX today: 23.9 MiB [ General system configuration (beta): armbian-config ] Last login: Wed Sep 7 14:05:25 2022 from 192.168.6.17 root@npi-a64-116:~# uname -a Linux npi-a64-116 5.18.15-sunxi64 #trunk SMP Thu Aug 4 12:51:25 +03 2022 aarch64 GNU/Linux root@npi-a64-116:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun50ia64audio [sun50i-a64-audio], device 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sun9ihdmi [sun9i-hdmi], device 0: SUN9I-HDMI PCM i2s-hifi-0 [SUN9I-HDMI PCM i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 sun50i-a64-nanopi-a64_5_18_15.zip DTS_Changes_NPI_A64.doc DTS_Changes_NPi_A64.pdf

@thedocbwarren How did you start and connect to the Ordoid C2? Because I used the bullseye-cli and it booted right away - BUT I had only the "problem" (like before on C2 images) that I cant connect via SSH to the C2 for the initial setup. The initial setup is only at the HDMI-Port (and an the first boot the filesystem-resize took some time) After I completed the inital setup via HDMI and USB-Keyboad I can connect normally via SSH BTW: After a rebout I have to power off/on for the next startup (u-boot problem) u-boot seems to be actual from the new installation on the MicroSD-Card: root@odroid-c2-3:~# dd if=/dev/mmcblk0 of=/tmp/installed_uboot.bin skip=97 count=1376 1376+0 records in 1376+0 records out 704512 bytes (705 kB, 688 KiB) copied, 0.0471277 s, 14.9 MB/s root@odroid-c2-3:~# strings /tmp/installed_uboot.bin | grep "U-Boot 20" U-Boot 2022.01-armbian (Aug 30 2022 - 06:46:25 +0000) odroid-c2

CLI or Desktop (which Desktop?) ? Jammy, Bulleye or Sid? which images did you try?

doesnt it show up as wlx[MAC-address of your adapter]?

In the newer version of ser2net (like v4.3.3-1) the /etc/ser2net.conf is replaced by the /etc/ser2net.yaml which has the yaml-format OK - here is a working version in yaml-format: # A fully featured configuration file is in # /usr/share/doc/ser2net/examples/ser2net.yaml define: &banner \r\nZ80-MBC2 via Telnet on Port [\p]\r\nDevice connected to [\d]\r\n connection: &z80mbc2 accepter: telnet(rfc2217),tcp,2023 enable: on options: banner: *banner kickolduser: true telnet-brk-on-sync: true connector: serialdev, /dev/ttyUSB0, 115200n81,local

but its one of the boards that boot also "BASIC Engine NextGeneration" https://betest.freeflarum.com/d/87-h3-based-boards-that-boot-enginebasic-ng/23 and https://basicengine.org/nextgen.html

Hi Hans decompile .dtb to .dts dtc -I dtb -O dts /boot/dtb/allwinner/sun50i-h5-orangepi-zero-plus.dtb -o /boot/dtb/allwinner/sun50i-h5-orangepi-zero-plus.dts edit (nano) the .dts (replace heartbeat with none) in the led-1 part: leds { compatible = "gpio-leds"; led-0 { label = "orangepi:green:pwr"; gpios = <0x37 0x00 0x0a 0x00>; linux,default-trigger = "default-on"; }; led-1 { label = "orangepi:red:status"; gpios = <0x0e 0x00 0x11 0x00>; linux,default-trigger = "heartbeat"; }; }; recompile .dts to .dtb (this will gibe many non-problematic warning onscreen): dtc -I dts -O dtb /boot/dtb/allwinner/sun50i-h5-orangepi-zero-plus.dts -o /boot/dtb/allwinner/sun50i-h5-orangepi-zero-plus.dtb then reboot PS: maybe you would "apt-mark hold " your dtb-package (find it with dpkg -l|grep dtb ) sun50i-h5-orangepi-zero-plus.dtb sun50i-h5-orangepi-zero-plus.dts

try (and reboot) cp /usr/lib/firmware/brcm/brcmfmac43456-sdio.txt /usr/lib/firmware/brcm/brcmfmac43456-sdio.radxa,rockpi4b.txt

here is a working link to the archive: https://web.archive.org/web/20211227155426/https://forum.0cd.xyz/t/building-u-boot-for-the-espressobin/511

Its old , but maybe it could help a little bit? https://web.archive.org/web/20180104180446/http://wiki.macchiatobin.net/tiki-index.php?page=Boot+from+removable+storage+-+Ubuntu and http://macchiatobin.net/forums/topic/booting-failure-of-new-board/#post-1512

As I read http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=3399 it seems to be possible. At the URL is a information how to change the .DTB for the OPi Zero to use the USB-OTG as USB-HOST You have to find the right usb-port (usb@1c19000) in the .DTB/.DTS for the OPi One DTB to DTS decompile dtc -I dtb -O dts /boot/dtb/sun8i-h3-orangepi-one.dtb -o /boot/dtb/sun8i-h3-orangepi-one.dts EDIT change in the .DTS: change the line: dr_mode = "otg"; to dr_mode = "host"; in the section usb@1c19000 from: usb@1c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x03 0x20>; resets = <0x03 0x11>; interrupts = <0x00 0x47 0x04>; interrupt-names = "mc"; phys = <0x10 0x00>; phy-names = "usb"; extcon = <0x10 0x00>; dr_mode = "otg"; status = "okay"; phandle = <0x48>; }; to: usb@1c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x03 0x20>; resets = <0x03 0x11>; interrupts = <0x00 0x47 0x04>; interrupt-names = "mc"; phys = <0x10 0x00>; phy-names = "usb"; extcon = <0x10 0x00>; dr_mode = "host"; status = "okay"; phandle = <0x48>; }; DTS to DTB compile dtc -I dts -O dtb /boot/dtb/sun8i-h3-orangepi-one.dts -o /boot/dtb/sun8i-h3-orangepi-one.dtb then REBOOT As attachment the new compiled version (when you have the same kernel as I 5.15.4 @MacBreaker PS: Liebe Gruesse nach Hessen - vor 6 Jahren habe ich in Babenhausen bei Frankfurt/Darmstadt gewohnt - nun in der Tuerkei.... sun8i-h3-orangepi-one.dtb

@NicoD iy you got the early 2B with Cortex-/ CPU then it wont work, but there is a 2B V1.2 with Cortex-A53 (BCM2837) at 900Mhz which could work because it can handle 64bit