what box? What interface is your keyboard and mouse? Check if the kernel has driver support.

#for had dpkg warning... linux-image-current-meson64
sudo apt-get remove -y linux-image-current-meson64

It is recommended to keep u-boot.ext

try updating other kernels: armbian-update 5.15.14

look at this: #31

what box?
Beelink GT King Pro (Revision A).

What interface is your keyboard and mouse?
USB Keyboard and USB Mouse.

Check if the kernel has driver support.
Appreciate your guidance on how to check? Currently the SD Card can only boot up to GDM3 Greeter Login Screen but stuck there. Keyboard and Mouse does not work for me to proceed further. What commands to check whether kernel keyboard and mouse driver support?

#for had dpkg warning... linux-image-current-meson64
sudo apt-get remove -y linux-image-current-meson64
sudo apt-get install -y linux-image-current-meson64
Noted.
FYI, "apt list linux-image* --installed" return that "linux-image-current-meson64" has been installed.
uname -a output kernel 5.4.171-flippy-69+ and not 5.4.171-meson64.

Willl sudo apt-get install -y linux-image-current-meson64
results in kernel install 5.4.171-meson64 or 5.4.171-flippy-69+? Just curious.

It is recommended to keep u-boot.ext

Noted.
But the u-boot-gtkingpro.bin does not always consistently boot up per my understanding and actual usage. This u-boot.ext from https://disk.yandex.ru/d/ZMQW85B-P6QejA seems to boot up consistently.

try updating other kernels: armbian-update 5.15.14
Cannot upgrade to other kernel as the boot up stuck at Login Greeter Screen and no longer able to do anything.
Will have to burn a new image:
#Armbian_22.02.0_Aml_s922x_bullseye_5.15.14_2022.01.13.1524.img.gz

Thank you.

Out of curiosity why would the newly burn SD Card image not being able to be recognized by Ubuntu or Manjaro?

Burn Armbian_22.02.0_Aml_s922x_bullseye_5.15.14_2022.01.13.1524.img.gz on SD Card (Samsung Evo Plus 64GB) with Rufus.
Boot up stuck at "initramfs". A lot of I/O Errors, dev mmcblk1...

Again the SD Card cannot be recognized by Ubuntu or Manjaro. "Disks" or "Gparted" return SD Card as unallocated.

what box are you? model?
If the SD card is not recognized, you can format it first and change the burning tool, such as https://rufus.ie/

what box are you? model?

Beelink GT King Pro (Revision A, Serial # SA9HH.....)

If the SD card is not recognized, you can format it first and change the burning tool, such as https://rufus.ie/

Yes, I did format the SD Card first and then use Rufus as burning tool. Also tried with Balena Etcher as burning tool. Same issue.

With kernel 5.4.171 image it boot up successfully but after install Gnome Desktop keyboard and mouse not recognized or functioning.

With kernel 5.15.14 image, it cannot boot up successfully stuck at "initramfs" and with a lot of I/O Errors.

Could it be related to u-boot-gtkingpro.bin as u-boot.ext and kernel 5.15.14 not compatible with my device? But I cannot swap the u-boot.ext from the one that I use regularly as I cannot access to SD Card with another Linux OS.

I have the same problem with Armbian_22.02.0_Aml_s912_bullseye_5.4.171_2022.01.12.2339.img.
Tanix tx92 (3gb ddr3, 32gb emmc, s912).
I installed to emmc, same warning about linux-image-current-meson64 missing.
Then I installed XFCE and the mouse and keyboard didn't work.

I tried using ssh, and tried
sudo apt-get remove -y linux-image-current-meson64
sudo apt-get install -y linux-image-current-meson64

On reboot, the tv box went into a bootloop (bad CRC, unable to initialize ethernet due to TIMEOUT).

Tanix tx92 is currently unclear.

Not all boxes support writing to emmc, and the ones that can be written have a special serial number in the armbian-install list. If you are not sure about writing, it is recommended to use on SD/usb/tf.

There are many types of TV boxes, and the boxes that are not in the known list need to be tested by yourself. If you find a good uboot and dtb matching solution, you can share it and help other users.

Tanix tx92 is currently unclear.

Not all boxes support writing to emmc, and the ones that can be written have a special serial number in the armbian-install list. If you are not sure about writing, it is recommended to use on SD/usb/tf.

There are many types of TV boxes, and the boxes that are not in the known list need to be tested by yourself. If you find a good uboot and dtb matching solution, you can share it and help other users.

It was working perfectly from CLI, using h96 pro plus installation profile.
The problem is the DE that don't recognize mouse and keyboard.
The tv box model is TX92-LP.

After installing the desktop, the mouse and keyboard are not recognized. It should be a lack of drivers. What model of USB keyboard are you using?

After installing the desktop, the mouse and keyboard are not recognized. It should be a lack of drivers. What model of USB keyboard are you using?

Peripherals aren't recognized after the desktop environment install (Xfce).
When I have installed armbian on emmc, and rebooted, the keyboard works.

I use this keyboard, by the way https://www.amazon.it/dp/B00W102J5Q/

@ErikPelli

The Nsc Tanix TX92 S912 3GB RAM 32GB ROM 1000M LAN 5G WIFI you used is the first friend to give feedback, can you use it when you write emmc? Can you share which U-BOOT and DTB file you used? Will kernel 5.10 work?

#Are you using this configuration?
Tanix TX92
s912
meson-gxm-octopus-planet.dtb
u-boot-zyxq.bin

Is the product this? https://www.tokopedia.com/nevishopcom/nsc-tanix-tx92-s912-3gb-ram-32gb-rom-1000m-lan-5g-wifi?whid=0

@ErikPelli

The Nsc Tanix TX92 S912 3GB RAM 32GB ROM 1000M LAN 5G WIFI you used is the first friend to give feedback, can you use it when you write emmc? Can you share which U-BOOT and DTB file you used? Will kernel 5.10 work?

Is the product this? https://www.tokopedia.com/nevishopcom/nsc-tanix-tx92-s912-3gb-ram-32gb-rom-1000m-lan-5g-wifi?whid=0

I used the same configuration of h96 pro plus, zyxq uboot and octopus planet dtb (this is the only dtb in which ethernet works correctly, wifi doesn't work).
When I write to emmc it works, even on reboot.
I didn't test 5.10 yet.

Model is in your link, and it's a rebranded Vorke Z6 Plus, so I would add that as well.

@ErikPelli

I used the same configuration of h96 pro plus, zyxq uboot and octopus planet dtb (this is the only dtb in which ethernet works correctly, wifi doesn't work). When I write to emmc it works, even on reboot. I didn't test 5.10 yet.

Model is in your link, and it's a rebranded Vorke Z6 Plus, so I would add that as well.

armbian-update 5.10.91

You can try updating the kernel to version 5.10. Thank you for your sharing, I will add the installation option of this box to armbian-install, and I will record your sharing in CONTRIBUTOR.md

VORKE Z6 Plus Amlogic S912 3GB DDR3 32GB: https://www.tokopedia.com/mbitabn/vorke-z6-plus-android-7-1-2-smart-tv-box-amlogic-s912-3gb-ddr3-32gb?whid=0

I use armbian to access through ssh on my laptop, using the server version mode, and have not installed the desktop. Seeing that everyone connects the mouse and keyboard to use the desktop version, I will buy an external device to try.

@JFLim1

Could it be related to u-boot-gtkingpro.bin as u-boot.ext and kernel 5.15.14 not compatible with my device? But I cannot swap the u-boot.ext from the one that I use regularly as I cannot access to SD Card with another Linux OS.

@JFLim1

Noted. But the u-boot-gtkingpro.bin does not always consistently boot up per my understanding and actual usage. This u-boot.ext from https://disk.yandex.ru/d/ZMQW85B-P6QejA seems to boot up consistently.

According to the documents you provided, I specially made a firmware for you, you can try if it can be used. dc23f3b

In releases, like Armbian_22.02.0_Aml_s922x-reva_focal_xxx.img.gz

armbian-install number 45

@ErikPelli

I used the same configuration of h96 pro plus, zyxq uboot and octopus planet dtb (this is the only dtb in which ethernet works correctly, wifi doesn't work). When I write to emmc it works, even on reboot. I didn't test 5.10 yet.
Model is in your link, and it's a rebranded Vorke Z6 Plus, so I would add that as well.

armbian-update 5.10.91

You can try updating the kernel to version 5.10. Thank you for your sharing, I will add the installation option of this box to armbian-install, and I will record your sharing in CONTRIBUTOR.md

VORKE Z6 Plus Amlogic S912 3GB DDR3 32GB: https://www.tokopedia.com/mbitabn/vorke-z6-plus-android-7-1-2-smart-tv-box-amlogic-s912-3gb-ddr3-32gb?whid=0

I use armbian to access through ssh on my laptop, using the server version mode, and have not installed the desktop. Seeing that everyone connects the mouse and keyboard to use the desktop version, I will buy an external device to try.

I tried this kernel and now mouse and keyboard work, shouldn't it be the default kernel for s912?

@ErikPelli

I tried this kernel and now mouse and keyboard work, shouldn't it be the default kernel for s912?

Did you test a kernel that supports version 5.10?
Which version of the kernel supports your mouse and keyboard?

@ErikPelli

I tried this kernel and now mouse and keyboard work, shouldn't it be the default kernel for s912?

is the default.
Did you test a kernel that supports version 5.10?
Which version of the kernel supports your mouse and keyboard?

The s912 downloadable release was using 5.4, and mouse not working.
I updated to 5.10 and now it works.

In order to save space on github, I only compiled the 5.4 kernel. It seems that different versions need to be compiled by default.

When it is convenient, please test whether the 5.15 kernel supports mouse and keyboard.
armbian-update 5.15.14

According to your message above, maybe serial number 44 is your box
There are several different versions of this box that you modify according to your own version.
After img is flashed into sd, double-click to open, you can modify the files under /boot
Modify the dtb file to meson-g12b-gtking-pro-rev_a.dtb in uEnv.txt

Thanks noted. Did not know that there is a difference in gtking-pro.dtb between regular and Rev A in mainline kernel. I understand in CoreElec (kernel 4.9.y legacy) or linux image with kernel 4.9.y I need to use Rev A dtb but on mainline kernel I have always use the regular meson-g12b-gtking-pro.dtb. Good to know there is a Rev A dtb for GT King Pro. Thank you.

According to the documents you provided, I specially made a firmware for you, you can try if it can be used. dc23f3b

Thank you very much.

In releases, like Armbian_22.02.0_Aml_s922x-reva_focal_xxx.img.gz

Great. Do you have Bullseye build with s922x-reva?

armbian-install number 45

What is this command "armbian-install number 45"? I am not familiar.

What is this command "armbian-install number 45"? I am not familiar.

From releases: https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_Aml_focal_2022.01.15.0035

Download: Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14_2022.01.15.0007.img.gz

when install to emmc: armbian-install
select 45

when write to emmc: armbian-install
select 45

Understood. Currently prefer to run Linux on SD or USB Flash. Look forward your "Releases" with Aml_s922x-reva_bullseye_xxx.img.gz.

Hi @JFLim1 & @ophub
I have the same gtking_pro as @JFLim1 and so I tested the latest release Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14_2022.01.15.0007.img.gz on usb pen but unfortunately the u-boot.ext (719kb) creates a boot-loop... For now only kernel 5.4.y starts without using no file in u-boot.ext..

@JFLim1 @MX10-AC2N

https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_Aml_focal_2022.01.15.1146/Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14_2022.01.15.1116.img.gz

Give feedback on the effect of this adjustment after testing

https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_Aml_focal_2022.01.15.1146/Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14_2022.01.15.1116.img.gz

Give feedback on the effect of this adjustment after testing

Good news. After editing uEnv.txt to use "meson-g12b-gtking-pro-rev_a.dtb". It boot up successfully with the new u-boot.ext you have included. Thank you.

I noticed there is also a "meson-g12b-gtking-pro-rev_a-oc.dtb" in the /boot/dtb/amlogic folder. Is this the over clock rev_a dtb? What CPU speed it over clock to? A73 to 2208 MHz and A53 to 1900 MHz?

Next is to install a Desktop to check whether keyboard and mouse works. I have the hunch it will work. No "Failed ...Keymap..." warning during boot up.

Standard Edition: 1800/1908
Standard Edition-OC: 1992/1992
Version H: 1800/2208
H-OC version: 2016/2208
Rev A: 1800/1908
Rev A - OC version: 1992/1992
Non-pro version: 1800/1908

Now the Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14.img.gz firmware has been configured according to the test results, and can be used directly without modification in the future.

Re-download the newly packaged s922x-reva firmware, do not modify anything, test it

I did exactly the same thing again but this time flashed on a USB key, and I can start without problem by plugging into the USB OTG, I did a reboot by having connected the USB receiver of my dinovo keyboard-mouse and therefore it starts I can connect in SSH on the other hand I lose the HDMI signal on my tv at the time of kernel startup.. So I reuse the gtking-pro.dtb directly taken from the /BOOT partition and cool I recover the hdmi signal throughout boot process.
So the same image file Armbian_22.02.0_Aml_s922x-reva_bullseye_5.15.14_2022.01.16.1511.img.gz works very well on USB media but not at all on SD-card media..

https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_Aml_bullseye_2022.01.16.1816/Armbian_22.02.0_Aml_s922x-reva_bullseye_5.15.14_2022.01.16.1745.img.gz

Do not modify anything, test it

https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_Aml_bullseye_2022.01.16.1816/Armbian_22.02.0_Aml_s922x-reva_bullseye_5.15.14_2022.01.16.1745.img.gz

Do not modify anything, test it

Okay so I flashed this new release on my sd-card, and just plug on my gtking-pro box => boot failed like as I post on imgur > https://imgur.com/a/it5hZhP

Is it possible to boot from usb?
If it cannot be started, rename /boot/u-boot-gtkingpro.bin to u-boot.ext under the test.

https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_Aml_bullseye_2022.01.16.1816/Armbian_22.02.0_Aml_s922x-reva_bullseye_5.15.14_2022.01.16.1745.img.gz
Flashed on usb key, without any modification, just connect to the USB OTG input with my keyboard / mouse receiver plugged into one of the other USB ports.
The startup takes place without any problem.
Just need a good clean of my usb key before..
Kernel 5.4.y boot fine with sd-card but without any u-boot.ext

Thanks for sharing your test results, the armbian system works fine on usb flash.

Congratulations, you found a solution, close this post, it's too long to display.

@ophub
I put a resistor between Rx and GND as stipulated in https://github.com/ophub/amlogic-s9xxx-openwrt/blob/main/router-config/README.md#109-if-you-cant-startup-after-using-the-mainline-u-boot
Suddenly I no longer have the freeze at startup when I use u-boot-gtking-pro.bin as u-boot.ext on the SD-card, however I lose the HDMI signal after starting the kernel and no connection SSH possible.. Misery, I was hoping to finally be able to start the 5.15.y kernel from my sd card, it's still not good..
I try meson-g12b-gtking-pro.dtb from /BOOT and also from /ROOTFS/usr/lib/linux-image-current-meson64/amlogic/ same result = black screen after starting kernel and no ssh connection
I also try meson-g12b-gtking-pro-rev_a.dtb but always same result..
If you have any idea ?
Thank again for all.

@ophub
I flashed Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on my sd-card, without any modification
This time I have signal on my TV but lot of error I/O
see https://imgur.com/a/F6eSJUq

I/O error, dev mmcblk1
The serial number of the sd card is mmcblk1, emmc is mmcblk2, and usb is sda

I asked flippy teacher to use on sd card. He said gtk does not support SD-UHS. The high speed sd standard requires a 3.3/1.8 variable IO voltage, but most boxes only have a fixed 3.3v.

Thank @ophub
It's strange because I've been using this same sd card for quite a while now, first with the firmware from @balbes150 (uses u-boot.ext the 719kb one) but also with your firmware kernel 5.4.y it starts very well from it but without using u-boot.ext.
Strange no?

This is not surprising, because balbes150 is a boutique product. has magical properties

This u-boot.ext can also be used in kernels below 5.10. If it works in a 5.4 kernel, it turns out that it can also work with a 5.10+ kernel. So I have it enabled by default. But many friends think it is unnecessary, so let's cancel it in the 5.4 kernel.

I tested and used u-boot-gtkingpro-rev-a.bin today. The first 10 seconds of booting, the screen was unresponsive and completely black. But it starts after 10 seconds.
Other boxes will start quickly.
According to many tests, this uboot can always be successfully started, but if it is replaced by something else, it cannot be started, which may be related to the model of the box.

Hi @ophub

I tested and used u-boot-gtkingpro-rev-a.bin today. The first 10 seconds of booting, the screen was unresponsive and completely black. But it starts after 10 seconds.
Based on feedback from other Manjaro-Arm users this u-boot-gkkingpro-rev-a.bin works on many amlogic tv boxes not just s922x tv boxes.

This is not surprising, because balbes150 is a boutique product. has magical properties
Hahaha..., With balbes150 image it can be used on SD Card without issue except when I update from 5.10.79-meson64 to 5.10.81-meson64. Once updated to 5.10.81-meson64 kernel, SD Card will NOT boot up, many I/O Error dev mmcblk1. If I install for example kernel 5.15.10-arm64 from another source, on SD Card same balbes150 image as a base. Interesting.

Thanks you for your support. Currently editing this message using Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on USB Flash on GT King Pro Revision A.

Hi @ophub

the screen was unresponsive and completely black. But it starts after 10 seconds.
Also experience "black screen" after boot up successful to desktop and within 5 minutes later "black screen".

Resolved this by renaming/disabling hdmi.rules in /etc/udev/rules.d/

Hi @ophub and @JFLim1
Just to share, now with my gtking-pro box (s/n:SA9HH..) and with the resistor placed in Rx and Gnd, I can use u-boot-gtking-pro as u-boot.ext it works Good..
So I flashed my SD card again, this time with the latest release Armbian_22.02.0_Aml_s922x_bullseye_5.4.172_2022.01.19.1857.img.gz
So I renamed u-boot-gtking-pro.bin to u-boot.ext and started booting from my SD card with all USB inputs used (hard drive, ssd, and remote control receiver..) everything worked..
So I did "armbian-tf -e" and launched "armbian-update 5.10.92 stable yes"
At the reboot I had no signal on my TV but I was able to connect in SSH, I went to rename hdmi.rules.bak in hdmi.rules
I launched a reboot and I had the signal again hdmi.. 5.10.92 works fine from my SD card..!
So I try the update to 5.15.15 and there is this famous problem..

@ophub I flashed Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on my sd-card, without any modification This time I have signal on my TV but lot of error I/O see https://imgur.com/a/F6eSJUq

Hi @MX10-AC2N

Just to share, now with my gtking-pro box (s/n:SA9HH..) and with the resistor placed in Rx and Gnd, I can use u-boot-gtking-pro as u-boot.ext it works Good..

Can you provide details on this modification. Resistor size extra. If there is a picture it will be great. One day when courage strike might try it. Hahaha...

Is there any benefit/difference in using u-boot-gtkingpro.bin versus u-boot-gtkingpro-rev-a.bin?

@ophub I flashed Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on my sd-card, without any modification This time I have signal on my TV but lot of error I/O see https://imgur.com/a/F6eSJUq

I had the same issue/errors (I/O Errors dev mmcblk1...) with balbes150 Armbian-Bullseye on SD Card when I upgrade 5.10.79-meson64 v21.08.4 to 5.10.81-meson64 v21.08.6. Could be due to the 3.3V vs 1.8V @ophub pointed out earlier.

Hi @JFLim1 @ophub
Can you provide details on this modification. Resistor size extra. If there is a picture it will be great. One day when courage strike might try it. Hahaha...
Indeed, I was not very reassured to make this addition of resistance but who tries nothing has nothing...
So I followed what Flippy gave as an indication https://github.com/ophub/amlogic-s9xxx-openwrt/blob/main/router-config/README.md#109-if-you-cant-startup-after-using-the-mainline-u-boot
So I needed a resistor with a value between 5Kohm and 10Kohm, so I looked through the pile of old resistors I had and I found one of a little over 8Kohm, so I soldered this between the Rx and GND terminals clearly visible on the board.
https://imgur.com/a/rm0KPhR

Is there any benefit/difference in using u-boot-gtkingpro.bin versus u-boot-gtkingpro-rev-a.bin?
I can't really say, I'm not sure what it changes but now I can use u-boot-gtking-pro.bin directly without freeze problem when booting it seems less hacky to me than using the u- boot-gtking-pro-rev_a.bin, which was not part of the Ophub builds before we told him about it.

I had the same issue/errors (I/O Errors dev mmcblk1...) with balbes150 Armbian-Bullseye on SD Card when I upgrade 5.10.79-meson64 v21.08.4 to 5.10.81-meson64 v21.08.6. Could be due to the 3.3V vs 1.8V @ophub pointed out earlier.
I don't really know, I have trouble understanding why we manage to start kernel 5.10.y and even as you remind me on the Beelink forum we managed to start https://oph.mdrjr.net/meveric/pool/main/l/linux-upstream/linux-image-5.15.10-arm64_5.15.10-20211220-odroid_arm64.deb starting from the Balbes image..
Suddenly I no longer have the impression that there is a problem in the system parameters but there for once I am completely floundering..

I don't really know, I have trouble understanding why we manage to start kernel 5.10.y and even as you remind me on the Beelink forum we managed to start https://oph.mdrjr.net/meveric/pool/main/l/linux-upstream/linux-image-5.15.10-arm64_5.15.10-20211220-odroid_arm64.deb starting from the Balbes image..
Hi @MX10-AC2N

Suddenly I no longer have the impression that there is a problem in the system parameters but there for once I am completely floundering..

I suspect the kernel config setting had something to do with it. kernel-5.10.79-meson64 NO issue on SD Card and 5.10.81-meson64 I/O Errors on SD Card. Meveric's kernel no issue for the time being.

@JFLim1
That's what I think too, but I have no idea what to do.
Hope this helps @ophub or flippy pinpoint the problem..

Hi @ophub
Sorry to ping you like that, but I would like to know if you had been able to see my last messages since #72 (comment) and especially to know what you think of that ??
Thank again..
Edit: Here is the copy of "dmesg" when I boot kernel 5.10 from my sd-card => https://paste.yunohost.org/jarujumexa.vbs

@ophub @JFLim1
Salvation,
Well this time I have something new, so I start kernel 5.10 from my sd card I run the "armbian-config" command in the system menu I launch the switch to the "nightly" version, from the nightly sources I have access to linux-image-edge-arm64 which uses kernel 5.15.16
So I ran "apt install linux-image-edge-arm64"
This unmounted the /BOOT (Fat) partition and installed all new files in the /boot (ROOTFS) directory.
By copying the new 5.15.16-arm64 files from /boot (ROOTFS) to /BOOT (fat) which must necessarily be remounted..
I also had to redo the dtb folder in /BOOT
and that I rename uInitrd-5.15.16-arm64 to uInitrd and of course vmlinuz-5.15.16-arm64 to uImage in order to keep zImage which corresponds to kernel 5.10.93
Change in uEnv.txt to direct to uImage
Here is a copy of what I do and the reboot.. => https://paste.yunohost.org/ficuzaxuwo.scala
Now I wonder why linux-image-edge-arm64 works without problem while I couldn't successfully armbian-update to 5.15??
Hoping this can help you @ophub

Then I ran "apt update && apt upgrade"

armbian-bsp-cli-lepotato/bullseye 22.02.0-trunk.0016 arm64 [pouvant être mis à jour depuis : 22.02.0-trunk]
armbian-config/bullseye,bullseye 22.02.0-trunk.0004 all [pouvant être mis à jour depuis : 22.02.0-trunk]
armbian-firmware/bullseye,bullseye 22.02.0-trunk.1 all [pouvant être mis à jour depuis : 22.02.0-trunk]
armbian-zsh/bullseye,bullseye 22.02.0-trunk.0016 all [pouvant être mis à jour depuis : 22.02.0-trunk]
hostapd/bullseye 3:2.9-102~armbian20.05.2+1 arm64 [pouvant être mis à jour depuis : 3:2.9-102~armbian20.05.2+1]
linux-libc-dev/bullseye 22.02.0-trunk.0016 arm64 [pouvant être mis à jour depuis : 21.08.6]

Reboot is OK and now I have

Here is dmesg output => https://paste.yunohost.org/egicesucat.sql