-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keyboard and Mouse not functioning #72
Comments
what box? What interface is your keyboard and mouse? Check if the kernel has driver support.
It is recommended to keep try updating other kernels: look at this: #31 |
Willl
Noted.
Thank you. |
Out of curiosity why would the newly burn SD Card image not being able to be recognized by Ubuntu or Manjaro? |
what box are you? model? |
Beelink GT King Pro (Revision A, Serial # SA9HH.....)
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. I tried using ssh, and tried 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. |
It was working perfectly from CLI, using h96 pro plus installation profile. |
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). I use this keyboard, by the way https://www.amazon.it/dp/B00W102J5Q/ |
The
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). Model is in your link, and it's a rebranded Vorke Z6 Plus, so I would add that as well. |
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. |
amlogic-s9xxx-armbian/build-armbian/common-files/files/usr/sbin/armbian-install Lines 60 to 63 in 2b0902e
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
|
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_
|
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? |
The s912 downloadable release was using 5.4, and mouse not working. |
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. |
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.
Thank you very much.
Great. Do you have Bullseye build with s922x-reva?
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_ when install to emmc: |
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 |
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 Now the Armbian_22.02.0_Aml_ |
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. |
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? |
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 |
Thanks for sharing your test results, Congratulations, you found a solution, close this post, it's too long to display. |
@ophub |
@ophub |
|
I asked flippy teacher to use on sd card. He said |
Thank @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. |
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. |
Hi @ophub
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
Resolved this by renaming/disabling hdmi.rules in /etc/udev/rules.d/ |
Hi @ophub and @JFLim1
|
Hi @MX10-AC2N
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?
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
|
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. |
Hi @ophub |
@ophub @JFLim1 |
Then I ran "apt update && apt upgrade"
Here is dmesg output => https://paste.yunohost.org/egicesucat.sql |
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).
The text was updated successfully, but these errors were encountered: