ag123

a uwe5622 Wifi problem seem to afflict the Orange Pi Zero 3 as well thoughts are it may take using newer drivers and uwe5622 firmware codes https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-6.1-sun50iw9/drivers/net/wireless/uwe5622 i read somewhere that various works on uwe5622 drivers has been done in the 'upstreamed' recent kernels > 6.5 ? There has been complaints that different vendor's uwe5622 drivers creates a problem as they possibly conflict. Hence, it may help to try find the 'upstreamed' uwe5622 driver implementations and perhaps 'backport' it into the current kernels used in armbian e.g. 6.1.31

for ARM based SOCs, a problem is that there is no 'generic' kernel that can support the specific in chip and on board hardware components e.g. the HDMI graphics drivers, all the various components wifi, ethernet, even on chip interfaces such as usb, memory flash, mmc support and even power management, powering on and off and all that are *distinct* and most of that *undocumented* across ARM SOCs, this is true be they 32 bits or 64 bits. which practically means that searching for an 'OS' that is 'compatible' is going to either simply draw a blank or that you are going to get an 'OS' in which many parts are broken, e.g. no HDMI, no graphics drivers, no usb, no wifi, no ethernet, no nothing etc. you simply have to research the challenges supporting all the different boards here. bitness is a different challenge, for one, using 64 bits vs 32 bits may mean gigabytes of gigabytes / billions of all the apps, shared libraries, kernel, drivers etc would need to be recompiled into 64 or 32 bit binaries. effectively needing 2 universes of binaries to support the whole suite of apps

moderators/admins, I'm thinking it could help to put Orange Pi Zero 3 in its own unmaintained boards sub section, it is likely there'd be more threads related to this and to move this thread and the other thread into the new orange pi zero 3 board section

I'd just like to put a note that for wifi, even the propietary drivers seemed 'unstable', I'm not sure if it is just the drivers itself or something else

hi, just like to join this discussion in a 'development' sense it seemed there are some works in the head Linux v6.5-rc1 https://groups.google.com/g/linux-sunxi/c/p64EM9m9inY https://linux-sunxi.org/Xunlong_Orange_Pi_Zero3 https://linux-sunxi.org/Linux_mainlining_effort they seemed to be continued works on H616 mainlining efforts, but that those are working on H618 e.g. Orange Pi zero 3 etc it could be good to look at the head revisions e.g. v6.5 when we 'backport' codes into e.g. v6.1.31 that is used with armbian. that could save a lot of rework if at some point we (armbian) decide to move on and use a new kernel e.g. v6.5 and accordingly, i read a post that say things like the wifi drivers as different vendors tried to implement their own drivers, it creates a 'problem' for the mainlining efforts to attempt to reconcile 2 different versions of the 'same driver'. Hence, it may be good to look at head revisions e.g. v6.5 while 'porting' them back into v6.1.31. it would likely allow us to have 1 version of drivers e.g. from mainline that possibly works on different boards using the same wifi chips etc.

I've been trying the vendor images (non-armbian, but likely an armbian derivative) https://drive.google.com/drive/folders/1CJYrhHyyje9dEY4-t7JhcZBJfdAFBJro https://drive.google.com/drive/folders/10zlO-0mMz-fqRQOKAOWX-mQA_UbN_C1n and the wifi malfunctioned after running for some 1+ days, things got worse as initially i've been able to manually restart the wifi. then some other corruption creep in on the microsd card and I'm not sure the cause of it. note, non-armbian. for armbian, i think wifi etc is still 'work in progress', wifi isn't quite working yet as of last try, as noted in some earlier comments above.

i think orange pi zero 3 is after all gaining popularity as it is an 'upgraded' orange pi zero 2, 2+ with more dram, e.g. like up to 4 GB, that will make a lot of difference for some apps http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html

there is a new thread open on orange pi zero 3

I'd guess you can try some of the unsupported , user build images a couple of posts back https://github.com/leeboby/armbian-images I've tried the Debian 'server' images on a 2GB board, and the findings are in the comments above. I've also tried the Orange Pi released images, those work better. But that among the surprises, it seemed there are some hardware problems even with those images released by Orange Pi. Ethernet is not working after a while and after a few reboots, things are totally jammed even on the serial console. But that to work with these boards, use a serial console with a usb-uart dongle, as you may not be able to access it over ethernet and/or wifi. quite some details is covered with the comments above.

those look quite interesting, I'm thinking if it may be good to backport those changes back into 6.1.x used with Armbian currently. However, I'd think similarly, it is going to take a lot of work to do the same, including testing etc. another idea which may be quite interesting could be to try the new v6.5 kernel, compile from source, but thinking it through, the steps would likely to be quite similar with tests etc. e.g. that it is less likely to be a 'just works' setup and requires quite a bit of work to have all the peripherals working.

for some reasons I didn't find related docs in the company's web site https://www.marvell.com/products/infrastructure-processors/armada-38x.html those docs links are apparently not accessible but instead stumbled into a copy elsewhere in a web search https://ulli-kroll.de/Downloads/NAS326/A38x-Functional-Spec-PU0A.pdf the interesting section is chapter 26 Real time clock pages 303 accordingly, the real time clock runs on a 32khz crystal, so check your board to see if it is there. if it isn't there, maybe it isn't using the real time clock after all. And that if it is there, find in the source codes for the real time clock implementation, apparently some details about the RTC registers are documented, so those should after all match the func spec. And perhaps you may find your way around the code to 'tweak' the register settings etc. if it is a 'pseudo RTC' i.e. didn't exist, then it is probably a 'simulated' h/w clock which may be written in s/w, it'd take reading the codes to find out that curious facts hope that helps

1 sec every 60 sec? that's a pretty big drift. oh and btw hwclock seemed to have some ways to adjust for drift, but that'd probably means you need to sync your time to NTP

get a phone charging power bank to power the board, charge the battery and power the board, those are the modern UPS otherwise, if it is occasional data, to have it flushed to the disk, the command is usually sync and that does the trick

alternatively, create a swap file or swap partition like Igor mentioned. I'd prefer a swap partition as it is probably a smaller overhead

tried the Debian bookworm image from OrangePi dmesg [ 2282.163357] device wlan0 entered promiscuous mode [ 2282.229125] unisoc_wifi unisoc_wifi wlan0: sprdwl_change_beacon failed [ 2282.229151] unisoc_wifi unisoc_wifi wlan0: sprdwl_cfg80211_start_ap failed to start AP! [ 2282.242846] device wlan0 left promiscuous mode didn't work as well, so it has more to do with the wifi driver code, however, the errors are different. it'd seem there is also some conflicts with wpa_supplicant etc edit: I managed to get hostapd up on OrangePi Z3 using OrangePi's Debian bookworm image after all. apparently, 'limited' options are supported, 802.11g apparently seemed possible. # hostapd.conf # the interface used by the AP interface=wlan0 # bridge, this probably isn't necessary if you are not bridging bridge=br0 # "g" simply means 2.4GHz band hw_mode=g # the channel to use channel=5 # limit the frequencies used to those allowed in the country #ieee80211d=1 # the country code #country_code=US # 802.11n support #ieee80211n=1 # QoS support, also required for full speed on 802.11n/ac/ax #wmm_enabled=1 # the name of the AP ssid=orangepi # 1=wpa, 2=wep, 3=both auth_algs=1 # WPA2 only wpa=2 wpa_key_mgmt=WPA-PSK rsn_pairwise=CCMP wpa_passphrase=somepassword - NetworkManager has to be set as unmanaged for wlan0, nmcli dev set wlan0 managed no this is temporary there is a way to make the confit permanent as well https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-configuring_ip_networking_with_nmcli#configuring-networkmanager-to-ignore-certain-devices disable bluetooth and wpa_supplicant service to avoid conflicts systemctl stop bluetooth.service systemctl disable bluetooth.service systemctl stop wpa_supplicant.service systemctl disable wpa_supplicant.service it would normally be necessary to configure a dhcp server if there is no other on the network or configure a bridge and place wlan0 and the ethernet interface on it. Note that when you are playing with bridging etc, it is advisable to use the uart interface. it is super easy to hose the connected ethernet interface e.g. using nmcli network manager commands and after that there is 'no way' to access the board other than using uart (and perhaps usb gadget) interface. on the OrangePi images, connecting to AP seemed possible wlan0: connected to wifi "wlan0" wifi (unisoc_wifi), 80:A0:53:73:A3:89, hw, mtu 1500 inet4 192.168.2.158/24 route4 192.168.2.0/24 metric 600 route4 default via 192.168.2.1 metric 600

much ado about serial terminal /dev/ttyS0 I've got a weird problem on the OPi Z3, thus far I've seen all the boot messages on the serial console, it turns out it is /dev/ttyS0. However, it doesn't 'accept/receive any inputs'. Hence, I can't login over serial tty. tried > systemctl stop serial-getty@ttyS0.service > echo hello > /dev/ttyS0 -- ok I saw that in the serial terminal :) > cat /dev/ttyS0 -- type something from the other end, nothing > systemctl start serial-getty@ttyS0.service -- ok login prompt appears in the serial terminal, but can't login I got so confused, I tried a 'loop back' test on my serial dongle, i.e. I took out the wire connected to RX pin on the Opi board, and connect it to TX on my usb-uart dongle. type something, ok i saw what i typed 'perfect' take out the wire, nothing, as expected next I plug that wire back to the RX pin on Opi board, oops something jerked on the connection, all gibberish, ok reboot, unplug power replug. Oops, now even ethernet goes out dark oh but suddenly I see the login prompt on my serial console again, type something, username, password voila logged in then to fix ethernet power down from serial console 'systemctl poweroff', unplug, replug again, retried a few times. finally, ... now I've got ethernet and serial tty console back it seemed to be a 'hardware' problem, a pin stuck 'low' or 'high'? well, I'd never know the mystery, but in case a usb-uart dongle is 'not working' try disconnect and reconnect the TX, RX, GND wires oh and about gibberish, like these 1st check your *baud rates*, it'd need to be 115200 bps and 8N1, thereafter it seemed to work 'quite perfect' my USB-uart dongle is actually an stm32f103 'blue pill' board https://stm32-base.org/boards/STM32F103C8T6-Blue-Pill.html running a stm32duino sketch https://github.com/rogerclarkmelbourne/Arduino_STM32/tree/master/STM32F1/libraries/A_STM32_Examples/examples/Communication/USB-uart-w-signals this sketch has got some bugs, hence I'd not recommend it. But in case anyone decides to use that post the questions in https://www.stm32duino.com/ and if i chanced upon it, i'd try to answer it there. but that there are 'cheap and good' usb-uart dongles, e.g. the (original, as in the chip) FT232 dongles and a search for "usb uart" in the usual online marketplaces Amazon, Ebay, Aliexpress etc would turn them up. https://www.amazon.com/s/ref=nb_sb_noss?field-keywords=usb+uart get 3.3v ones

I tried messing with hostapd, running the uwe5622 wifi in AP mode, trying to setup as a WiFi hotspot. used the 'generic' WPA passphrase based configs as like the 'simple' entries https://wiki.gentoo.org/wiki/Hostapd not much success, in dmesg [ 229.654023] (NULL net_device): sprdwl_uninit_fw failed! [ 229.654158] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 229.713879] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 229.717841] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 240.180745] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 240.217512] (NULL net_device): sprdwl_init_fw failed! [ 240.217801] ieee80211 phy0: sprdwl_cfg80211_del_iface driver removing! [ 339.310954] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 339.311346] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 341.419621] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 341.420389] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! [ 343.663494] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! then in /var/log/syslog 2023-08-08T21:56:25.386610+08:00 orangepizero3 wpa_supplicant[910]: wlan0: CTRL-EVENT-SCAN-FAILED ret =-5 retry=1 2023-08-08T21:56:26.389340+08:00 orangepizero3 wpa_supplicant[910]: wlan0: CTRL-EVENT-SCAN-FAILED ret =-5 retry=1 2023-08-08T21:56:27.391984+08:00 orangepizero3 wpa_supplicant[910]: wlan0: CTRL-EVENT-SCAN-FAILED ret =-5 retry=1 2023-08-08T21:56:27.958806+08:00 orangepizero3 wpa_supplicant[910]: p2p-dev-wlan0: CTRL-EVENT-DSCP-PO LICY clear_all 2023-08-08T21:56:27.960039+08:00 orangepizero3 systemd[1]: Stopping wpa_supplicant.service - WPA supp licant... ^ those are consistent with nmcli d wifi list returning an empty list further down on hostapd 2023-08-08T21:58:17.537085+08:00 orangepizero3 systemd[1]: Starting hostapd.service - Access point and authentication server for Wi-Fi and Ethernet... 2023-08-08T21:58:17.637276+08:00 orangepizero3 hostapd[1775]: nl80211: Could not configure driver mode 2023-08-08T21:58:17.637497+08:00 orangepizero3 hostapd[1775]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 2023-08-08T21:58:17.637649+08:00 orangepizero3 hostapd[1775]: nl80211 driver initialization failed. 2023-08-08T21:58:17.637735+08:00 orangepizero3 hostapd[1775]: wlan0: interface state UNINITIALIZED->DISABLED 2023-08-08T21:58:17.637818+08:00 orangepizero3 hostapd[1775]: wlan0: AP-DISABLED 2023-08-08T21:58:17.637925+08:00 orangepizero3 hostapd[1775]: wlan0: CTRL-EVENT-TERMINATING 2023-08-08T21:58:17.638017+08:00 orangepizero3 hostapd[1775]: hostapd_free_hapd_data: Interface wlan0 wasn't started 2023-08-08T21:58:17.639465+08:00 orangepizero3 kernel: [ 339.310954] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! 2023-08-08T21:58:17.639480+08:00 orangepizero3 kernel: [ 339.311346] unisoc_wifi unisoc_wifi wlan0: sprdwl_uninit_fw failed! 2023-08-08T21:58:17.641144+08:00 orangepizero3 systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE 2023-08-08T21:58:17.641602+08:00 orangepizero3 systemd[1]: hostapd.service: Failed with result 'exit-code'.

USB works, managed to mount a sd card in a usb card reader and examine some files. [ 890.861713] usb 1-1: new high-speed USB device number 4 using ehci-platform [ 891.021896] usb 1-1: New USB device found, idVendor=8564, idProduct=4000, bcdDevice= 0.04 [ 891.021926] usb 1-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ 891.021944] usb 1-1: Product: Transcend [ 891.021957] usb 1-1: Manufacturer: TS-RDF5A [ 891.021971] usb 1-1: SerialNumber: 000000000004 [ 891.023086] usb-storage 1-1:1.0: USB Mass Storage device detected [ 891.023810] scsi host0: usb-storage 1-1:1.0 [ 891.066751] usbcore: registered new interface driver uas [ 892.041439] scsi 0:0:0:0: Direct-Access TS-RDF5A Transcend 0004 PQ: 0 ANSI: 6 [ 892.042515] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 892.413021] sd 0:0:0:0: [sda] 62552064 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 892.414640] sd 0:0:0:0: [sda] Write Protect is off [ 892.414655] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00 [ 892.416125] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 892.424143] sda: sda1

cool, congrats the uwe5622 wifi apparently have issues, while wifi scan using nmcli d wifi list initially works, attempts to connect to a station results in a dump recorded in dmesg, some abstracts: [ 6.931488] wifi ini path = /lib/firmware/wifi_2355b001_1ant.ini [ 6.957269] sprdwl:sprdwl_get_fw_info length mismatch: len_count=83, r_len=89 [ 6.957278] sprdwl:sprdwl_get_fw_info, drv_version=1, fw_version=2, compat_ver=0 [ 6.957282] sprdwl:chip_model:0x2355, chip_ver:0x0 [ 6.957286] sprdwl:fw_ver:35940, fw_std:0x7f, fw_capa:0x120fff [ 6.957290] sprdwl:mac_addr:24:b7:2a:46:13:f7 [ 6.957296] sprdwl:credit_capa:TX_WITH_CREDIT [ 6.957298] sprdwl:ott support:0 ... lots of verbose stuff like [ 146.832213] sdiohal:chn8 tx push old, cmdid=25, mstime=146361, record_time=146361 [ 146.832222] chn8 tx push old: 00 00 00 00 .........;...... [ 146.832273] WCN_ERR: mdbg_dump_data dump memory error:-110 [ 146.832280] WCN: mdbg dump bt modem 0 ok! [ 146.832284] WCN_ERR: read HCI_ARM_WR_RD_MODE reg error:-1 [ 146.832291] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 146.832295] WCN: mdbg dump bt_cmd buf 0 ok! [ 146.832298] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 146.832302] WCN: mdbg dump btevent buf 0 ok! [ 146.832306] WCN_ERR: mdbg_dump_data dump memory error:-1 ... [ 165.825379] NETDEV WATCHDOG: wlan0 (unisoc_wifi): transmit queue 0 timed out [ 165.825509] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x230/0x240 [ 165.825554] Modules linked in: algif_hash algif_skcipher af_alg bnep hci_uart btqca btrtl btbcm btintel bluetooth ecdh_generic ecc sunrpc lz4hc lz4 zram binfmt_misc polyval_ce polyval_generic sunxi_cir rc_core sunxi_cedrus(C) videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc sprdwl_ng sunxi_addr cfg80211 sprdbt_tty rfkill uwe5622_bsp_sdio fuse dm_mod motorcomm dw_hdmi_cec dwmac_sun8i mdio_mux display_connector [ 165.825855] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 6.1.31-sunxi64 #1 [ 165.825874] Hardware name: OrangePi Zero3 (DT) [ 165.825885] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) so connect failed thereafter nmcli d wifi list returns an empty list I'm not sure how to recover from that, disable and enable the IF did not help sudo ip link set wlan0 down sudo ip link set wlan0 up nmcli d wifi list still returns an empty list lsmod ... uwe5622_bsp_sdio 204800 2 sprdbt_tty,sprdwl_ng uwe5622_bsp_sdio is linked to sprdbt_tty,sprdwl_ng, which in turns is linked to other stuff, hence it can't be simply 'rmmod'ed, reboot works, recovers the wifi scanning, but not connecting. (witnessed another dmesg dump after reboot, but initially "nmcli d wifi list" still works, it stops after a while and return an empty list

I did a little google search and stumbled into this https://linux-sunxi.org/Bootable_SD_card my guess is, when you get U-Boot SPL 2021.07-armbian (Jul 12 2023 - 10:04:49 +0000) DRAM: 4096 MiB Trying to boot from MMC1 At least a part of uboot started up on the SD / MMC card, as the 'SPL' part of uboot resides at 8 k address, in that seek=8, dd instruction. for the rest I'm not sure what happened.

for the 1.5 GB and 4GB boards there are some instructions and binaries here https://github.com/leeboby/opizero3-uboot-dtb for the 4 GB version the google translation is like such: 1 First download the bin file of 4g memory u-boot: 4gb memory u-boot bin file 2 Then download the dtb file corresponding to 4gb memory: 4gb memory dtb file 3 Then insert the TF card that has been burnt into the opizero3 linux6.x system into other linux machines 4 Then use the sudo fdisk -l command to view the device name of the tf card: For example: /dev/sdax 5 Then mount the file system in the tf card to the /mnt directory of the linux machine: sudo mount /dev/sdax /mnt 6 Then copy the dtb file to the /boot/dtb/allwinner/ directory in the TF card (please modify this directory according to the actual situation, do not copy): example code, need to adapt based on actual sitiation: sudo cp sun50i-h616-orangepi-zero3-4gb.dtb /mnt/boot/dtb/allwinner/sun50i-h616-orangepi-zero3.dtb 7 Then use the following command to update the bin file of u-boot to the TF card sudo dd bs=1k seek=8 if=u-boot-sunxi-with-spl-opizero3-4gb.bin of=/dev/sdax Note that steps 3 - 7 are done on a different Linux machine (which probably can even be a small board e.g. Raspberry Pi or an existing Armbian board that runs. And assuming that you are workng it say on a usb SD card reader. If you are working that on your PC, do be careful with the commands, as it is intended to edit binaries on the image written to a TF card. Be careful about working on your PC to idenfity the correct device disk or risk trashing data on your hard drives.

hi, no worries, it'd be good if OPi Z 3 becomes a 'supported' board, it is a pretty good board really, as a little Wifi router. for the Debian bookworm image booting up on my 2 GB OPi Z 3 the front parts is like such U-Boot SPL 2021.07-armbian (Jul 12 2023 - 10:04:49 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.9(debug):armbian NOTICE: BL31: Built : 02:24:54, Jul 11 2023 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0827f8, model: OrangePi Zero3 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. U-Boot 2021.07-armbian (Jul 12 2023 - 10:04:49 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero3 I2C: ready DRAM: 2 GiB MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... No working controllers found Autoboot in 1 seconds, press <Space> to stop ÿÿþÿÿïÿswitch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3259 bytes read in 4 ms (794.9 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 207 bytes read in 3 ms (67.4 KiB/s) 39163 bytes read in 9 ms (4.1 MiB/s) 4203 bytes read in 7 ms (585.9 KiB/s) Applying kernel provided DT fixup script (sun50i-h616-fixup.scr) ## Executing script at 45000000 18189653 bytes read in 1509 ms (11.5 MiB/s) 22464520 bytes read in 1864 ms (11.5 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=417f0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 18189589 Bytes = 17.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 48ea7000, end 49fffd15 ... OK Loading Device Tree to 0000000048e35000, end 0000000048ea6fff ... OK Starting kernel ... Loading, please wait... Starting systemd-udevd version 252.6-1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... ^[[2J^[[3J^[[-1;-1fdone.^M Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.^M Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems^M done.^M Begin: Will now check root file system ... fsck from util-linux 2.38.1^M [/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1 ^M armbi_root: recovering journal^M armbi_root: clean, 48679/944704 files, 489197/3800064 blocks^M done.^M done.^M Begin: Running /scripts/local-bottom ... done.^M Begin: Running /scripts/init-bottom ... done.^M ^M Welcome to ^[[1mArmbian 23.08.0-trunk bookworm^[[0m!^M armbi_root: recovering journal^M armbi_root: clean, 48679/944704 files, 489197/3800064 blocks^M done.^M done.^M Begin: Running /scripts/local-bottom ... done.^M Begin: Running /scripts/init-bottom ... done.^M ^M Welcome to ^[[1mArmbian 23.08.0-trunk bookworm^[[0m!^M The rest are the kernel boot proper, as it is verbose, I've attached it here. Note that I'm booting the 'server' image rather than the bigger 'desktop' image. I've not done Armbian 23.08.0-trunk Jammy as I ran into the OpenSSH daemon 'killed' issue which I didn't have a solution at hand to 'fix' it. I'm not sure what else I'd be able to help thus far. Apparently, the uboot or rather the boot loader setup is the tricky part as 1GB & 2 GB, 1.5 GB and 4 GB has different boot loader setups. armbianbookworkbootlog.zip

well avahi-daemon and avahi-utils should be bundled in the 'core' Armbian base distribution, well that's my pet peeve, prejudice . apt-get install avahi-daemon avahi-utils darn, missing vi(m) apt-get install vim edit vi /etc/avahi/avahi-daemon.conf ... [publish] publish-workstation=yes then from another station > avahi-browse -a + eth0 IPv6 orangepizero3 [02:00:6c:53:f7:f9] Workstation local > ping -4 orangepizero3.local PING orangepizero3.local (192.168.1.173) 56(84) bytes of data. 64 bytes from 192.168.1.173 (192.168.1.173): icmp_seq=1 ttl=64 time=0.514 ms > ssh orangepizero3.local user@orangepizero3.local's password: ___ ____ _ _____ _____ / _ \| _ \(_) |__ /___ _ __ ___|___ / | | | | |_) | | / // _ \ '__/ _ \ |_ \ | |_| | __/| | / /| __/ | | (_) |__) | \___/|_| |_| /____\___|_| \___/____/ Welcome to Armbian 23.08.0-trunk Bookworm with Linux 6.1.31-sunxi64 No end-user support: built from trunk System load: 27% Up time: 28 min Memory usage: 6% of 1.94G IP: 192.168.1.173 CPU temp: 43°C Usage of /: 12% of 15G RX today: 9.4 MiB [ 0 security updates available, 1 updates total: apt upgrade ] Last check: 2023-08-07 20:59 Last login: Mon Aug 7 21:06:17 2023 user@orangepizero3:~$ looks pretty decent, system load is a little high though for what is a 'verbatim' setup lol user@orangepizero3:~$ nmcli d DEVICE TYPE STATE CONNECTION end0 ethernet connected Wired connection 1 lo loopback connected (externally) lo wlan0 wifi disconnected -- p2p-dev-wlan0 wifi-p2p disconnected -- user@orangepizero3:~$ nmcli d wifi IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY A0:36:BC:4A:3B:49 CopperTiger Infra 9 270 Mbit/s 90 ▂▄▆█ WPA2 WPA3 F0:2F:74:74:70:F1 CopperTiger Infra 9 270 Mbit/s 70 ▂▄▆_ WPA2 WPA3 24:F5:A2:42:E3:81 Linksys07844 Infra 12 540 Mbit/s 70 ▂▄▆_ WPA2 ok so it seemed wifi works as well

next try the Debian bookworm image instead https://github.com/leeboby/armbian-images Welcome to ARMBIAN! Documentation: https://docs.armbian.com | Community: https://forum.armbian.com IP address: 192.168.1.173 Create root password: ****** Repeat root password: ****** Warning: Weak password, it does not contain enough DIFFERENT characters! Choose default system command shell: 1) bash 2) zsh 1 Shell: BASH Creating a new user account. Press <Ctrl-C> to abort yay, I'm in SSH, confirmed ethernet works ssh 192.168.1.173 -l root root@192.168.1.173's password: ___ ____ _ _____ _____ / _ \| _ \(_) |__ /___ _ __ ___|___ / | | | | |_) | | / // _ \ '__/ _ \ |_ \ | |_| | __/| | / /| __/ | | (_) |__) | \___/|_| |_| /____\___|_| \___/____/ Welcome to Armbian 23.08.0-trunk Bookworm with Linux 6.1.31-sunxi64 No end-user support: built from trunk System load: 28% Up time: 16 min Memory usage: 6% of 1.94G IP: 192.168.1.173 CPU temp: 44°C Usage of /: 11% of 15G RX today: 56.3 KiB [ 0 security updates available, 1 updates total: apt upgrade ] Last check: 2023-08-07 20:51 Last login: Mon Aug 7 20:41:40 2023 from 192.168.1.2 er erm, it is actually nice and colorful, text copy couldn't get the colors strangely, the serial terminal is blank in the bootup, but that sshd over ethernet 'just works' ok I 'accidentally' saw this in the serial terminal in after a reboot Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 armbi_root: clean, 48668/944704 files, 488641/3800064 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.08.0-trunk bookworm! [ OK ] Created slice system-getty.slice - Slice /system/getty. [ OK ] Created slice system-modpr…lice - Slice /system/modprobe. [ OK ] Created slice system-seria… - Slice /system/serial-getty. [ OK ] Created slice user.slice - User and Session Slice. [ OK ] Started systemd-ask-passwo… Requests to Wall Directory Watch. [ OK ] Set up automount proc-sys-…rmats File System Automount Point. [ OK ] Reached target integrityse…Local Integrity Protected Volumes. [ OK ] Reached target slices.target - Slice Units. ... long [ OK ] Started unattended-upgrade…0m - Unattended Upgrades Shutdown. [ OK ] Started vnstat.service - vnStat network traffic monitor. [ OK ] Finished openvpn.service - OpenVPN service. [ OK ] Started rc-local.service - /etc/rc.local Compatibility. [ OK ] Started systemd-hostnamed.service - Hostname Service. [ OK ] Finished systemd-user-sess…ervice - Permit User Sessions. Starting plymouth-quit-wai… until boot process finishes up... Starting plymouth-quit.ser… Terminate Plymouth Boot Screen... Armbian 23.08.0-trunk Bookworm ttyS0 orangepizero3 login: well, I still have problems typing things into the console, it seemed the characters typed 'didn't get across' to the H618 uart, even though this time the text is properly received and displayed at 115200 baud from a different PC

next up try the 'unofficial' armbian images https://github.com/leeboby/armbian-images ok in armbian I got a boot console on the uart Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.37.2 [/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1 armbi_root: recovering journal armbi_root: clean, 43126/916864 files, 567125/3800064 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.08.0-trunk jammy! -.mount [ OK ] Created slice Slice /system/modprobe. [ OK ] Created slice Slice /system/serial-getty. [ OK ] Created slice User and Session Slice. [ OK ] Started Forward Password R…uests to Wall Directory Watch. [ OK ] Set up automount Arbitrary…s File System Automount Point. [ OK ] Reached target Slice Units. [ OK ] Reached target Swaps. [ OK ] Reached target System Time Set. [ OK ] Reached target Local Verity Protected Volumes. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Listening on Syslog Socket. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Listening on initctl Compatibility Named Pipe. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. [ OK ] Reached target Socket Units. Mounting Huge Pages File System... Mounting POSIX Message Queue File System... Mounting Kernel Debug File System... Starting Restore / save the current clock... Starting Set the console keyboard layout... Starting Create List of Static Device Nodes... Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module configfs... Starting Load Kernel Module drm... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module fuse... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... Starting Load Kernel Modules... Starting Remount Root and Kernel File Systems... Starting Coldplug All udev Devices... dev-hugepages.mount dev-mqueue.mount [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Kernel Debug File System. sys-kernel-debug.mount [ OK ] Finished Restore / save the current clock. fake-hwclock.service [ OK ] Finished Create List of Static Device Nodes. kmod-static-nodes.service [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module configfs. [ OK ] Finished Load Kernel Module drm. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module fuse. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Load Kernel Module ramoops. Mounting FUSE Control File System... Mounting Kernel Configuration File System... [ OK ] Finished Remount Root and Kernel File Systems. systemd-remount-fs.service [ OK ] Mounted FUSE Control File System. sys-fs-fuse-connections.mount [ OK ] Mounted Kernel Configuration File System. sys-kernel-config.mount Starting Load/Save Random Seed... Starting Create System Users... run-credentials-systemd\x2dsysusers.service.mount [ OK ] Finished Set the console keyboard layout. keyboard-setup.service [ OK ] Finished Load/Save Random Seed. systemd-random-seed.service [ OK ] Finished Create System Users. systemd-sysusers.service Starting Create Static Device Nodes in /dev... [ OK ] Finished Create Static Device Nodes in /dev. systemd-tmpfiles-setup-dev.service [ OK ] Reached target Preparation for Local File Systems. Mounting /tmp... Starting Rule-based Manage…for Device Events and Files... [ OK ] Mounted /tmp. tmp.mount [ OK ] Reached target Local File Systems. Starting Armbian leds state... Starting Armbian ZRAM config... Starting Set console font and keymap... Starting Tell Plymouth To Write Out Runtime Data... [ OK ] Finished Coldplug All udev Devices. systemd-udev-trigger.service Starting Helper to synchronize boot up for ifupdown... [ OK ] Finished Set console font and keymap. console-setup.service [ OK ] Finished Tell Plymouth To Write Out Runtime Data. plymouth-read-write.service [ OK ] Finished Helper to synchronize boot up for ifupdown. ifupdown-pre.service [ OK ] Finished Armbian leds state. armbian-led-state.service [ OK ] Started Rule-based Manager for Device Events and Files. systemd-udevd.service Starting Show Plymouth Boot Screen... [ OK ] Listening on Load/Save RF …itch Status /dev/rfkill Watch. Starting Load/Save RF Kill Switch Status... [ OK ] Started Show Plymouth Boot Screen. plymouth-start.service [ OK ] Started Forward Password R…s to Plymouth Directory Watch. [ OK ] Reached target Local Encrypted Volumes. [ OK ] Reached target Path Units. [ OK ] Found device /dev/ttyS0. [ OK ] Reached target Hardware activated USB gadget. dev-zram0.swap Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Load Kernel Module ramoops. [ OK ] Finished Armbian ZRAM config. armbian-zram-config.service Starting Armbian memory supported logging... var-log.hdd.mount var-log.mount systemd-rfkill.service [ OK ] Started Load/Save RF Kill Switch Status. [ OK ] Finished Load Kernel Modules. systemd-modules-load.service Starting Apply Kernel Variables... [ OK ] Finished Apply Kernel Variables. systemd-sysctl.service Starting Raise network interfaces... Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module ramoops. [ OK ] Finished Raise network interfaces. networking.service Starting Load Kernel Module chromeos_pstore... Starting Load Kernel Module efi_pstore... Starting Load Kernel Module pstore_blk... Starting Load Kernel Module pstore_zone... Starting Load Kernel Module ramoops... [ OK ] Finished Load Kernel Module chromeos_pstore. [ OK ] Finished Load Kernel Module efi_pstore. [ OK ] Finished Load Kernel Module pstore_blk. [ OK ] Finished Load Kernel Module ramoops. [ OK ] Finished Load Kernel Module pstore_zone. [ OK ] Finished Armbian memory supported logging. armbian-ramlog.service Starting Journal Service... [ OK ] Started Journal Service. systemd-journald.service Starting Flush Journal to Persistent Storage... [ OK ] Finished Flush Journal to Persistent Storage. systemd-journal-flush.service Starting Create Volatile Files and Directories... [ OK ] Finished Create Volatile Files and Directories. systemd-tmpfiles-setup.service Mounting RPC Pipe File System... [ OK ] Started Entropy Daemon based on the HAVEGE algorithm. haveged.service Starting RPC bind portmap service... Starting Network Name Resolution... Starting Record System Boot/Shutdown in UTMP... [ OK ] Mounted RPC Pipe File System. run-rpc_pipefs.mount [ OK ] Reached target rpc_pipefs.target. [ OK ] Reached target NFS client services. [ OK ] Finished Record System Boot/Shutdown in UTMP. systemd-update-utmp.service [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Listening on D-Bus System Message Bus Socket. Starting Armbian hardware monitoring... Starting Armbian hardware optimization... [ OK ] Finished Armbian hardware monitoring. armbian-hardware-monitor.service [ OK ] Started RPC bind portmap service. [ OK ] Reached target Preparation for Remote File Systems. [ OK ] Reached target Remote File Systems. [ OK ] Reached target RPC Port Mapper. rpcbind.service [ OK ] Finished Armbian hardware optimization. armbian-hardware-optimize.service [ OK ] Reached target Basic System. Starting Save/Restore Sound Card State... [ OK ] Started Regular background program processing daemon. cron.service [ OK ] Started D-Bus System Message Bus. dbus.service Starting Network Manager... [ OK ] Started Save initial kernel messages after boot. dmesg.service Starting Remove Stale Onli…t4 Metadata Check Snapshots... Starting LSB: Load kernel …d to enable cpufreq scaling... Starting LSB: rng-tools (Debian variant)... Starting System Logging Service... Starting Resets System Activity Logs... Starting User Login Management... Starting WPA supplicant... [ OK ] Finished Save/Restore Sound Card State. [ OK ] Reached target Sound Card. alsa-restore.service [ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots. rsyslog.service [ OK ] Started System Logging Service. [ OK ] Started LSB: rng-tools (Debian variant). rng-tools-debian.service [ OK ] Finished Resets System Activity Logs. sysstat.service [ OK ] Started LSB: Load kernel m…ded to enable cpufreq scaling. loadcpufreq.service Starting LSB: set CPUFreq kernel parameters... cpufrequtils.service [ OK ] Started LSB: set CPUFreq kernel parameters. [ OK ] Started Network Name Resolution. systemd-resolved.service [ OK ] Reached target Host and Network Name Lookups. Starting LSB: Set sysfs variables from /etc/sysfs.conf... Starting Bluetooth service... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. sysfsutils.service [ OK ] Started User Login Management. systemd-logind.service [ OK ] Started WPA supplicant. wpa_supplicant.service [ OK ] Started Network Manager. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. NetworkManager.service Starting chrony, an NTP client/server... Starting OpenVPN service... Starting /etc/rc.local Compatibility... Starting Notify NFS peers of a restart... Starting OpenBSD Secure Shell server... Starting Permit User Sessions... [ OK ] Started Unattended Upgrades Shutdown. unattended-upgrades.service [ OK ] Started vnStat network traffic monitor. vnstat.service [ OK ] Finished OpenVPN service. openvpn.service [ OK ] Started /etc/rc.local Compatibility. rc-local.service [ OK ] Started Notify NFS peers of a restart. rpc-statd-notify.service [ OK ] Finished Permit User Sessions. systemd-user-sessions.service [ OK ] Started Bluetooth service. bluetooth.service [ OK ] Reached target Bluetooth Support. Starting Hold until boot process finishes up... Starting Terminate Plymouth Boot Screen... Starting Hostname Service... [FAILED] Failed to start OpenBSD Secure Shell server. [FAILED] Failed to start OpenBSD Secure Shell server. Armbian 23.08.0-trunk Jammy ttyS0 orangepizero3 login: for some reason, the board didn't register the keystrokes typed in the console, maybe it is some issues with my usb serial - uart dongle. but well that looks cool bummer can't login to SSH, but ping works, so ethernet works