Keyboard and Mouse not functioning

[JFLim1]

Hi @ophub,

Installed Armbian_22.02.0_Aml_s922x_bullseye_5.4.171_2022.01.12.0851.img.gz on SD Card. Somehow the newly burned image on SD Card using Etcher or Rufus, the SD Card cannot seems to be recognised when I try to inspect the newly burned SD Card image using another linux image on USB Flash. Basically with "Disks" or "Gparted" the SD Card is NOT Allocated. Cannot mount or show up on File Manager.

But the funny thing is, managed to boot up on second try on GT King Pro Rev A. After boot up, performed the following:

sudo apt update sudo apt upgrade "had dpkg warning ...linux-image-current-meson64 missing..." but it upgraded successfully. armbian-tf e (to expand the SD Card) sudo mv u-boot.ext to u-boot.ext-none (per my understanding u-boot.ext is not require with kernel 5.4.y) reboot successfully

The issue is during boot up I noticed: Failed ...keymap....

On TTY session keyboard works without issue.

Proceeded to install GNOME 41 following the instructions from https://www.linuxcapable.com/how-to-install-gnome-41-desktop-unstable-on-debian-11-bullseye/

Installed GNOME 41 successfully.

Reboot a success to gdm3 login greeting screen. But the issue is keyboard and mouse not functioning/working. Cannot enter the password to proceed to Desktop Environment! Unplug and replug keyboard or mouse make NO difference.

Cannot go back to TTY session with "ctl+alt+F1" or "ctl+alt+F2" so basically stuck and not usable now.

Any advice? How to get Armbian_22.02.0_Aml_s922x_bullseye_5.4.171_2022.01.12.0851.img.gz (kernel 5.4.y without u-boot.ext) to work on DE (i.e. keyboard and mouse working).

[ophub]

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.

[MX10-AC2N]

@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.

[MX10-AC2N]

@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

[ophub]

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

[ophub]

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.

[MX10-AC2N]

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?

[ophub]

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.

[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. 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.

[JFLim1]

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.

[JFLim1]

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/

[MX10-AC2N]

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

[JFLim1]

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.

[MX10-AC2N]

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..

[JFLim1]

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.

[MX10-AC2N]

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

[MX10-AC2N]

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 https://github.com/ophub/amlogic-s9xxx-armbian/issues/72#issuecomment-1016577181 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

[MX10-AC2N]

@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

[MX10-AC2N]

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