TRay

Another interesting thing is that snd_usb_audio is not loaded as a module and seems to be compiled. I tried in /boot/armbianEnv.tx in extrargs= put snd_usb_audio.index=0 but that didn't work either, unless a different name should be provided instead of snd_usb_audio.

By the way, it's a shame the old method of forcing the bit card number via /etc/modprobe.d/alsa.conf didn't work on Armbian. options snd_usb_audio index=0 options sun4i_codec index=1 options snd_hdmi_audio index=2 alias snd-card-0 snd_usb_audio alias snd-card-1 sun4i_codec alias snd-card-2 snd_hdmi_audio That's why I was looking for a way to disable these additional audio codecs and HDMI, but maybe it's because snd_usb_audio, etc., aren't loaded as modules in the new kerne

Ok I check via ls /proc/device-tree/__symbols__/ addr_mgt hdmi_con_in name r_i2c_pins tcon_tv0 ahub1_codec hdmi_in nmi_intc rmii_pins tcon_tv0_in ahub1_cpu hdmi_in_tcon_top ohci0 r_pio tcon_tv0_in_tcon_top_mixer0 ahub1_mach hdmi_out ohci1 r_rsb tcon_tv0_in_tcon_top_mixer1 ahub1_plat hdmi_out_con ohci2 r_rsb_pins tcon_tv0_out ahub_dam_mach hdmi_phy ohci3 rtc tcon_tv0_out_tcon_top ahub_dam_plat i2c0 osc24M sid ths axp313 i2c0_pins pio spdif ths_calibration ccu i2c1 planes spdif_tx_pin uart0 codec i2c1_pi_pins prcm_ppu spi0 uart0_ph_pins cpu0 i2c2 pwm spi0_cs0_pin uart1 cpu1 i2c2_ph_pins pwm0 spi0_pins uart1_pins cpu2 i2c2_pi_pins pwm0_pin spi1 uart1_rts_cts_pins cpu3 i2c3 pwm1 spi1_cs0_pin uart2 cpu_critical i2c3_pa_pins pwm1_pg_pin spi1_cs1_pin uart2_pg_pins cpu_opp_table i2c3_pg_pins pwm1_ph_pin spi1_pins uart2_pg_rts_cts_pins cpu_speed_grade i2c3_ph_pins pwm1_pi_pin sram_c uart2_ph_pins cpu_target i2c4 pwm2 sram_c1 uart2_ph_rts_cts_pins cpu_threshold i2c4_pg_pins pwm2_ph_pin syscon uart2_pi_pins crypto i2c4_ph_pins pwm2_pi_pin tcon_lcd0 uart2_pi_rts_cts_pins ddr_temp_critical iommu pwm3 tcon_lcd0_in uart3 de ir pwm3_ph_pin tcon_lcd0_in_tcon_top_mixer0 uart3_pi_pins de3_sram ir_rx_pin pwm3_pi_pin tcon_lcd0_in_tcon_top_mixer1 uart3_pi_rts_cts_pins display_clocks l2_cache pwm4 tcon_lcd0_out uart4 dma lradc pwm4_ph_pin tcon_top uart4_pi_pins dump_reg mdio0 pwm4_pi_pin tcon_top_hdmi_in uart4_pi_rts_cts_pins ehci0 mdio1 pwm5 tcon_top_hdmi_in_tcon_tv0 uart5 ehci1 mixer0 pwm5_pin tcon_top_hdmi_out uart5_pins ehci2 mixer0_out r_ccu tcon_top_hdmi_out_hdmi usbotg ehci3 mixer0_out_tcon_top_mixer0 reg_aldo1 tcon_top_mixer0_in usbphy emac0 mixer1 reg_dcdc1 tcon_top_mixer0_in_mixer0 ve_sram emac1 mixer1_out reg_dcdc2 tcon_top_mixer0_out ve_temp_critical ext_rgmii_phy mixer1_out_tcon_top_mixer1 reg_dcdc3 tcon_top_mixer0_out_tcon_lcd0 watchdog ext_rgmii_pins mmc0 reg_dldo1 tcon_top_mixer0_out_tcon_tv0 wifi_pwrseq gic mmc0_pins reg_usb1_vbus tcon_top_mixer1_in x32clk_fanout_pin gpadc mmc1 reg_vcc33_wifi tcon_top_mixer1_in_mixer1 gpu mmc1_pins reg_vcc5v tcon_top_mixer1_out gpu_temp_critical mmc2 reg_vcc_wifi_io tcon_top_mixer1_out_tcon_lcd0 hdmi mmc2_pins r_i2c tcon_top_mixer1_out_tcon_tv0 After decompiling the DTS image (H618): grep -A 15 "codec {" /tmp/extracted_tree.dts soundcard-mach,codec { }; }; ahub1_plat { #sound-dai-cells = <0x00>; compatible = "allwinner,sunxi-snd-plat-ahub"; apb_num = <0x01>; dmas = <0x25 0x04 0x25 0x04>; dma-names = "tx\0rx"; playback_cma = <0x80>; capture_cma = <0x80>; tx_fifo_size = <0x80>; rx_fifo_size = <0x80>; tdm_num = <0x01>; tx_pin = <0x00>; -- soundcard-mach,codec { sound-dai = <0x33>; phandle = <0x98>; }; }; usb@5100000 { compatible = "allwinner,sun50i-h616-musb\0allwinner,sun8i-h3-musb"; reg = <0x5100000 0x400>; clocks = <0x02 0x70>; resets = <0x02 0x32>; interrupts = <0x00 0x19 0x04>; interrupt-names = "mc"; phys = <0x34 0x00>; phy-names = "usb"; extcon = <0x34 0x00>; root@host:/tmp# grep -A 15 "hdmi_sound {" /tmp/extracted_tree.dts root@host:/tmp# grep -A 10 "ahub1_mach {" /tmp/extracted_tree.dts ahub1_mach { compatible = "allwinner,sunxi-snd-mach"; soundcard-mach,name = "HDMI"; soundcard-mach,format = "i2s"; soundcard-mach,frame-master = <0x31>; soundcard-mach,bitclock-master = <0x31>; soundcard-mach,slot-num = <0x02>; soundcard-mach,slot-width = <0x20>; status = "okay"; phandle = <0x97>; HDMI Audio is located under the label: ahub1_mach Analog Codec is associated with: ahub1_plat and codec These nodes have a default status of "okay," which causes them to occupy slots 0 and 1. and use /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&codec>; __overlay__ { status = "disabled"; }; }; fragment@1 { target = <&ahub1_codec>; __overlay__ { status = "disabled"; }; }; fragment@2 { target = <&hdmi>; __overlay__ { status = "disabled"; }; }; fragment@3 { target = <&spdif>; __overlay__ { status = "disabled"; }; }; fragment@4 { target = <&ahub1_mach>; __overlay__ { status = "disabled"; }; }; }; and after reboot not show HDMI and Codec audio and USB sound card has 0 number

Unfortunately, there's no technical way to connect to the UART to see. I'm not sure if I got the names right. Maybe the HDMI and audio codecs have different names in the tree devices ? Is there any way to find them?

Ok tried: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&codec>; __overlay__ { status = "disabled"; }; }; fragment@1 { target = <&hdmi_sound>; __overlay__ { status = "disabled"; }; }; }; and run armbian-add-overlay disable-internal-audio.dts But after reboot, still Codec and HDMI exist in the list of cards Maybe I wrote the overlay file?

After updating the system, when the 6.12.x kernel was updated to 6.18.25, the audio codec and HDMI codecs appeared in the list, which caused the USB sound card to be renumbered from 0 to 2. I know I can change the number from 0 to 2, but there's a system image that users use with their configuration, which previously had the card number set to 0. As a result of the system update, everyone lost communication with the sound card in the application. I'm looking for a solution to restore the system so that the USB sound card remains number 0. If anyone has any good advice on how to make the USB sound card permanently have number 0 in the list or how to block Codec and HDMI audio in the system so that they are not present?

How to disable HDMI and CODEC in system where is ne kernel 6.18.25 cat /proc/asound/cards 0 [Codec ]: sun4i-codec - H616 Audio Codec h616-audio-codec 1 [HDMI ]: HDMI - HDMI HDMI 2 [Device ]: USB-Audio - USB PnP Sound Device C-Media Electronics Inc. USB PnP Sound Device at usb-5200400.usb-1, full speed I need an always USB sound card with the number of 0

Yes it looks like but with reboot on Ornage Pi zero back. After fixing the problem with kernel 6.12.xx https://github.com/armbian/build/issues/8197 now when we use kernel like 6.18.24 we can not reboot OZPI v1. When we run 'reboot' it is rather to power off so it looks like it is a problem with Crust https://github.com/armbian/build/pull/8503 it wille nice to fix this problem with reboot in kernel 6.18.x like was fixed in 6.12.x I know that the Orange Pi Zero platform is on community support, but maybe there will be a volunteer who will fix this problem. but extraargs=reboot=watchdog help solve problem

It seems that the problem with the computer not booting on first boot returned with kernel 6.18.x. I have to restart the computer twice (power cycle) to get it to boot. The computer always started on first boot on Armbian 26.x with kernel 6.12.x, but after updating ArmBin when the 6.18.x kernels were released, the problem returned: OZPI v1 doesn't always start on the first try, and I have to turn it off and on again. Of course, when there's a kernel update, I run amrmbian-install, but that doesn't solve the recurring problem.

Today all works, thank you for all who fixed this problem 🙂 apt update Get:1 http://security.debian.org trixie-security InRelease [43,4 kB] Get:2 http://deb.debian.org/debian trixie InRelease [140 kB] Get:3 http://deb.debian.org/debian trixie-updates InRelease [47,3 kB] Get:5 https://github.armbian.com/configng stable InRelease [5 467 B] Get:4 http://armbian.lv.auroradev.org/beta trixie InRelease [39,4 kB] Get:6 http://deb.debian.org/debian trixie-backports InRelease [54,0 kB] Get:7 http://security.debian.org trixie-security/main armhf Packages [88,8 kB] Get:8 http://deb.debian.org/debian trixie/non-free armhf Packages [69,9 kB] Get:9 http://deb.debian.org/debian trixie/non-free-firmware armhf Packages [6 685 B] Get:10 https://github.armbian.com/configng stable/main armhf Packages [434 B] Get:11 http://deb.debian.org/debian trixie/main armhf Packages [12,7 MB] Get:12 http://deb.debian.org/debian trixie/contrib armhf Packages [50,6 kB] Get:13 http://deb.debian.org/debian trixie-updates/main armhf Packages [5 144 B] Get:14 http://deb.debian.org/debian trixie-backports/main armhf Packages [133 kB] Get:15 http://deb.debian.org/debian trixie-backports/contrib armhf Packages [4 368 B] Get:16 http://deb.debian.org/debian trixie-backports/non-free-firmware armhf Packages [3 856 B] Get:17 http://deb.debian.org/debian trixie-backports/non-free armhf Packages [1 520 B] Fetched 13,4 MB in 12s (1 073 kB/s) 32 packages can be upgraded. Run 'apt list --upgradable' to see them.

Igor, I understand the issue is complex, as you say, but for now I can only report that this didn't work. However, if I manage to resolve it, please let me know what we should do next, as I don't want to lose the work I've done on the image I downloaded. I also understand that these are BETA test images.

Today when I run: apt clean and rm -rf /var/lib/apt/lists/* apt update Ign:10 http://beta.armbian.com trixie/trixie-utils all Packages Err:8 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10351 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Ign:11 http://beta.armbian.com trixie/trixie-desktop armhf Packages 0% [7 InRelease 30.1 kB/47.3 kB 64%]Error: Transaction http://beta.armbian.com/dists/trixie/InRelease was already aborted and is aborted again Err:10 http://beta.armbian.com trixie/trixie-utils all Packages File has unexpected size (3562 != 3343). Mirror sync in progress? [IP: 23.186.113.5 80] Get:12 http://deb.debian.org/debian trixie-backports InRelease [54.0 kB] Get:13 http://deb.debian.org/debian trixie/main armhf Packages [12.7 MB] Get:14 http://deb.debian.org/debian trixie/non-free armhf Packages [69.9 kB] Get:15 http://deb.debian.org/debian trixie/non-free-firmware armhf Packages [6,685 B] Get:16 http://deb.debian.org/debian trixie/contrib armhf Packages [50.6 kB] Get:17 http://deb.debian.org/debian trixie-updates/main armhf Packages [5,144 B] Get:18 http://deb.debian.org/debian trixie-backports/non-free-firmware armhf Packages [3,856 B] Get:19 http://deb.debian.org/debian trixie-backports/non-free armhf Packages [1,520 B] Get:20 http://deb.debian.org/debian trixie-backports/main armhf Packages [132 kB] Get:21 http://deb.debian.org/debian trixie-backports/contrib armhf Packages [4,364 B] Error: Transaction http://beta.armbian.com/dists/trixie/InRelease was already aborted and is aborted again

I'm sorry, but I don't really understand what a microSD card has to do with the problem above to perform system updates?

I've been trying to update the system for 2 days but I can't: sudo apt update Get:1 http://deb.debian.org/debian trixie InRelease [140 kB] Get:2 http://security.debian.org trixie-security InRelease [43.4 kB] Get:4 http://security.debian.org trixie-security/main armhf Packages [88.5 kB] Get:5 https://github.armbian.com/configng stable InRelease [5,467 B] Get:6 https://github.armbian.com/configng stable/main armhf Packages [434 B] Get:3 http://armbian.lv.auroradev.org/beta trixie InRelease [39.4 kB] Get:7 http://armbian.lv.auroradev.org/beta trixie/trixie-desktop all Packages [731 B] Get:8 http://armbian.lv.auroradev.org/beta trixie/trixie-desktop armhf Packages [2,250 B] Get:9 http://armbian.lv.auroradev.org/beta trixie/trixie-utils armhf Packages [8,303 B] Ign:9 http://armbian.lv.auroradev.org/beta trixie/trixie-utils armhf Packages Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Get:10 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB] Get:11 http://deb.debian.org/debian trixie-backports InRelease [54.0 kB] Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Get:12 http://armbian.lv.auroradev.org/beta trixie/trixie-utils all Packages [3,343 B] Ign:12 http://armbian.lv.auroradev.org/beta trixie/trixie-utils all Packages Get:13 http://deb.debian.org/debian trixie/main armhf Packages [12.7 MB] Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Ign:12 http://beta.armbian.com trixie/trixie-utils all Packages Get:14 http://deb.debian.org/debian trixie/non-free armhf Packages [69.9 kB] Get:15 http://deb.debian.org/debian trixie/contrib armhf Packages [50.6 kB] Get:16 http://deb.debian.org/debian trixie/non-free-firmware armhf Packages [6,685 B] Get:17 http://deb.debian.org/debian trixie-updates/main armhf Packages [5,144 B] Get:18 http://deb.debian.org/debian trixie-backports/non-free armhf Packages [1,520 B] Get:19 http://deb.debian.org/debian trixie-backports/contrib armhf Packages [4,348 B] Get:20 http://deb.debian.org/debian trixie-backports/non-free-firmware armhf Packages [3,856 B] Get:21 http://deb.debian.org/debian trixie-backports/main armhf Packages [130 kB] Fetched 13.4 MB in 18s (754 kB/s) Error: Failed to fetch http://beta.armbian.com/dists/trixie/trixie-utils/binary-armhf/Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Error: Failed to fetch http://beta.armbian.com/dists/trixie/trixie-utils/binary-all/Packages.bz2 File has unexpected size (3942 != 3343). Mirror sync in progress? [IP: 23.186.113.5 80] Error: Some index files failed to download. They have been ignored, or old ones used instead.

when send command poweroff or reboot alywas display client_loop: send disconnect: Broken pipe instead in on ArmBian Debian 12: Connection to 192.168.1.12 closed by remote host. Connection to 192.168.1.12 closed. but maybe on Debian 13 now is different message after reboot or poweroff