guidol

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

@NicoD why only for the RPI4? I commented out (like you said in the video) the 2GHz overclock out of the config.txt and booted the image on the RPI3b(+) for a headless-server-only version (No Desktop) Little problem was the /erc/rc.local where I mount my SAMBA from another pistyle-sbc, because the Network card is getting up very late. So I had to add a "sleep 20" at the beginning of my /etc/rc.local Armbian on my the RPi 3B v1.2 takes around 185MB for booting - so enough space to do something Because onboard audio doesnt work I used a USB-Audio with a proper /etc/asound.conf After a "dpkg-reconfigure console-setup" the RPi does copy many new/current modules again and seem to setup the system better. To gain back some memory from the RPi3 I changed the GPU memory in the config.txt from 256MB to 32MB to get 950MB useable for the headless-server armbianmonitor -u result at: http://ix.io/3Fly

as a normal armbian-image it should be root as user and 1234 as initial password

If you have time and a spare Allwinner H3-CPU system (like the Orange Pi One or PC (not PC2 because of H3 CPU) you could try the BASIC Engine NG for H3-PiComputers/Boards. The - bare metall - BASIC seems to have very powerful commands - see the Online-Manual A forum in BETA state is at this URL I downloaded and booted the SDCard-Image from the 14.10.2021 (compressed size 5.4MB) from this directory Image was written with Balena Etcher to the SDCard Have fun and write new BASIC-programms!

@ismurdegusthe following content are the right sources for focal (no debian url needed for security). Fill the named 2 files with this content and your update should be safe /etc/apt/sources.list # =================================== deb http://ports.ubuntu.com/ focal main restricted universe multiverse #deb-src http://ports.ubuntu.com/ focal main restricted universe multiverse deb http://ports.ubuntu.com/ focal-security main restricted universe multiverse #deb-src http://ports.ubuntu.com/ focal-security main restricted universe multiverse deb http://ports.ubuntu.com/ focal-updates main restricted universe multiverse #deb-src http://ports.ubuntu.com/ focal-updates main restricted universe multiverse deb http://ports.ubuntu.com/ focal-backports main restricted universe multiverse #deb-src http://ports.ubuntu.com/ focal-backports main restricted universe multiverse /etc/apt/sources.list.d/armbian.list # =================================== deb http://apt.armbian.com/region/EU/ focal main focal-utils focal-desktop

I installed the bullseye version of Kernel 5.10.60-sunxi and my named asound.conf Sound Test is right with this command: speaker-test -Dhw:I2Smaster -c2 Inet-Radio Stream is playing here with mpg123 -v -b 1024 http://mp3.ffh.de/radioffh/hqlivestream.mp3 dmesg onyl shows root@nanopineo:~# dmesg |grep -i sound [ 1.228909] Advanced Linux Sound Architecture Driver Initialized. [ 3.873701] No soundcards found.

I used the following short code as /etc/asound.conf : pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 } This only defined the card 0 subdevice 0 as standard and didnt create a soft-volume-control ( I also dont know if it would work when created). I use the I2S without volume,control, because its digital I control the volume-level externally on the speakers. for mpg123 you can also address the Card 0 directly (when there is no asound.conf) with the -a option like mpg123 -v -b 1024 -a hw:0,0 ./your_song.mp3 see https://linux.die.net/man/1/mpg123 or use speaker-test -DI2Smaster -c2 see https://linux.die.net/man/1/speaker-test

It doesnt do any harmful..... The good thing is - I2S is compiled into the actual kernels, but had to be enabled in the .dtb (decompile .dtb to dts, enable it, compile .dts to .dtb) This isnt available via armbian-config..... Then compile a addon-overlay dts to dtb onto the Neo via 1 commandline You havent to use the armbian-build-system anymore - all can be done on the Neo after installing armbian See this Message in the old Thread:

you could try to use/read my "old" thread about using a I2S PCM5102 Soundcard-hat with the Neo:

You could test the options from this page: https://unix.stackexchange.com/questions/387502/disable-bluetooth-at-boot - via /etc/bluetooth/main.conf AutoEnable=false - rfkill sudo rfkill block bluetooth - lsmod / blacklist the modules

and before the exit 0 in /etc/rc.local

on my BananaPi M1 I can only control the green LED, but for that usage I do use the following command-line: echo 'mmc0' > /sys/class/leds/bananapi:green:usr/trigger only green LED available: # ls -l /sys/class/leds/ lrwxrwxrwx 1 root root 0 Sep 11 22:11 bananapi:green:usr -> ./../devices/platform/leds/leds/bananapi:green:usr

@lvmc as far as I know there is no backup of the armbian-part of xenial. For your /etc/apt/sources.list you should use as a part of the url http://ports.ubuntu.com/dists/xenial/ because only at this server there are armhf and arm64 packages available. Ckeck / add these xenial-source-directorys which does include newer files: [DIR] xenial-backports/ 2021-08-30 18:14 - [DIR] xenial-proposed/ 2021-08-30 18:33 - [DIR] xenial-security/ 2021-08-30 18:13 - [DIR] xenial-updates/ 2021-08-30 18:14 - [DIR] xenial/ 2016-04-21 07:43

because there are normally since many different u-boot versions no problems with that you should consider to tr another SD-Card or Power-Supply. On my NanoPi Neo I do use 16GB Grey/Red Sandisk-SD-Cards (80x Speed) without any problems.

@masteripper did you try to "boot the TX3 of by depressing the pinhole button while inserting the power cord." maybe then you will get another output? Try to read the following thread to get an idea?: https://forum.xda-developers.com/t/tanix-tx3-firmware-s905x3-mali-g31.4016613/

@gounthar also maybe here some other idea? https://hackaday.com/2021/08/16/new-part-day-raspberry-pi-hat-for-ieee1588-precision-time-protocol/

but WHY do you want to compile the WiFi-Driver when already a working one is included in armbian? The EW-7811Un is one of my oldest WiFi-Dongles from the beginning of the Raspberry Pi 1 Area, because it was one of the first working Donges on a RPi1 When I do insert my Edimax - I get it listed in lsusb, get the firmware loaded in dmesg and do get a new wlan-device (wlan0/wlan1 depending on the SBC) which is normally useable: lsusb 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 002: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg [234675.296067] usb 1-1: new high-speed USB device number 2 using ehci-platform [234675.458033] usb 1-1: New USB device found, idVendor=7392, idProduct=7811, bcdDevice= 2.00 [234675.458084] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [234675.458099] usb 1-1: Product: 802.11n WLAN Adapter [234675.458112] usb 1-1: Manufacturer: Realtek [234675.458124] usb 1-1: SerialNumber: 00e04c000001 [234675.612830] rtl8192cu: Chip version 0x10 [234675.719057] rtl8192cu: Board Type 0 [234675.719387] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [234675.719571] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [234675.719739] ieee80211 phy1: Selected rate control algorithm 'rtl_rc' [234675.723064] usbcore: registered new interface driver rtl8192cu [234675.755713] usbcore: registered new interface driver rtl8xxxu [234675.816426] rtl8192cu: MAC auto ON okay! [234675.855924] rtl8192cu: Tx queue select: 0x05 ifconfig wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 74:da:38:0e:3c:1a txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I dont know how to disable USB "only" in u-boot. But on a Odroid C2 we had restart issues which did belong to the u-boot version which was installed on the flash of the SBC and this wasnt in every case the u-boot version which was installed as a .deb-package. So maybe my BPi M1 has another u-boot version installed in flash?