Speaking of this; what BIOS version do you all have?
Mine shows (using dmidecode -t bios):
(...)
BIOS Revision: 5.19
Firmware Revision: 1.8
BIOS Revision: 5.19
Firmware Revision: 1.8
I am on kernel 5.15 (Solus) and fortunately keyboard always works for me, only touchpad is a problem. But it is not that annoying for me, I have a dropdown terminal (Yakuake) I created an alias for sudo rmmod -f i2c_hid_acpi && sudo modprobe i2c_hid_acpi and each time it stops forking I pop down the terminal, type the alias name, and it works again. It is annoying, but still Minibook X is the least problematic Linux laptop I have ever owned, and I owned a lot of niche ones.
But it is really weird I am not getting the keyboard problems. Could it be that newer kernel introduced this problem? Because we are using the same firmware, really weird.
Edit: Today the keyboard stopped working for the first time for me. I need to figure out a way to execute a shortcut on the desktop as root, best if without a password, so I can reset keyboard using touchscreen
Iâm sorry to hear that youâre having keyboard issues too, but in a way itâs âgoodâ as it means the problem is very consistent among our various MiniBook X devices.
I am not sure if your specific desktop environment has this option available through its settings, but try looking for the option that disables the trackpad when youâre typing. If you turn off that option, youâll most likely notice that the trackpad doesnât get this problem anymore, as the issue is --as far as I know-- always caused by the keyboard getting a key âstuck.â I could be wrong though, but Iâd love to hear if youâre able to try this to see if that solves the trackpad symptom at least.
1 Like
You were right, that really seems to be it!
Oh, and BTW, I found a really easy way to reset the keyboard only using touchscreen.
do sudo visudo and at the end add ALL ALL=NOPASSWD: /sbin/rmmod,/sbin/modprobe (first ALL can be your username for more safety).
This will allow for those commands to be run as root without putting in password.
Then I created a desktop shortcut that executes sudo rmmod -f i2c_hid_acpi && sudo modprobe i2c_hid_acpi.
And that is it, it certainly doesnât fix the main issue, but makes the laptop more usable for now.
Just make sure you can easily navigate to it only using touchscreen.
Hello, everybody, howâs battery life on your distro of choice?
Considering to buy one myself and run Fedora 36.
If I understood correctly, most issues, except keyboard and trackpad, are fixed and are in latest kernel at this point, thanks to all the things done by u guys.
I think sleep is broken too, with the screen not waking up. Hibernation works perfectly though.
After tuning governor for power save I get comparable times as on Windows, but it varies from 3.5h with low backlight, to 2 with maximum brightness, which is not a lot.
The keyboard and touchpad are annoying but livble, but I donât expect them to ever get fixedâŠ
Oh, and BTW, is accelerometer working for you guys? And convertible mode too? On 5.15 neither works, keyboard is not disabled when in tablet mode.
1 Like
As Jacek mentioned, the keyboard issue is not resolved yet unfortunately.
One of two parts of sleep related problems mentioned above have been fixed, the second one is as of right now not yet tackled by Intelâs engineers. Weâre waiting for them on that. In the mean time, you can rely on a lighter sleep mode (though battery drains actively with that mode), use Hibernation, or just turn off your computer. I used to have Hibernation enabled, but these days I just turn it off when Iâm done for the moment. SSDs are nice and fast, so itâs pretty quick (and I can take care of software updates while Iâm at it).
Great choice! Iâm running Fedora 36 Silverblue on it myself. Itâs a solid choice and GNOME looks gorgeous with this display, and because of GNOMEâs menubar at the top, it actually ends up working really nicely with the MiniBook Xâ in-display camera too :).
2 Likes
All the issues mentioned donât bother me as much as battery life. Nowhere near the advertised â8hâ âall day longâ. Thatâs a real deal breaker.
Anyways, thank you for quick and detailed answers!
Have a sunny day!
I wonder if there are anyone who are still interested in this topicâŠ
Just information. The issue of display comeback from suspend/resume(deep sleep) has been fixed by upstream intel drm driver development community[1]. This fix will be merged to mainline kernel in the future:)
[1] DSI display don't come back from resume (#6131) · Issues · drm / intel · GitLab
2 Likes
Iâm running Manjaro with 6.1 and see hibernation working. S3 suspend does not yet bring back the screen to live, so it stays black.
But I have not yet experienced the touchpad issues (cursor freezes while buttons still work as with 5.17 kernels) nor the keyboard freeze issues.
2 Likes
Four months using Deepin (with hibernation) without any issues.
@jeg thats great! Can you also share some details as Deepin is not the reason youâre not having issues but the underlying kernel and settings.
What is the kernel you are running?
Hibernation works, but what about S3?
Did you never experience the touchpad issue?
Did you never experience the keyboard issue?
Did you change any settings?
Thanks in advance for the elaborate answer.
I have fixed the wrongly rotated screen with this udev file. Just save it as /lib/udev/hwdb.d/61-sensor-MiniBookX, make sure you have iio-sensor-proxy installed and with screen-autorotate installed and activated the screen rotates always correctly.
Hi, in Deepin you can choose between two kernels. I used the newer one, a hwe 5.18 kernel. The only things I changed in the settings app were screen rotation and hibernation. I also installed tlp. S3 I have not tested it as I use hibernation. I did not have problems with the touchpad or with the keyboard. Interestingly the Nreal glasses work (as a secondary screen) direct from the USB C port.
For context, before Deepin I was using Ubuntu 22.04 with some 5.19 release candidate kernel so that the computer would shutdown, I also used hibernation because of the suspension issue. In Ubuntu, I did not had the keyboard problem but had the touchpad freezing issue.
1 Like
keep in mind that the only real issue is âctrlâ key getting âstuckâ , as by default the âblock touchpad while typingâ is active, this would cause the touchpad to be unresponsive. This was what caused the touchpad to âmalfunctionâ
The âctrlâ getting stuck was happening to a lot of people, its a minor issue, and happens rarely
Sadly this is not true for many, as not just the ctrl key gets âstuckâ but any other key can and will get stuck, too. This is the only thing that prevented me from being able to actually use the Minibook X under Linux, as I personally can live without S3 sleep.
I tried all kinds of things, even adding two special kinds of tape between the keyboard ribbon cable and battery, compiling my own Kernel with keyboard input timings tweaked, but sadly nothing ever helped solve the issue for me. It seems to require a fix on the firmware level, and is not something that can be handled on our end. At least for those of us who sadly got the issue, as it does seem like not everyone has it.
Itâs mostly Ctrl for me but Iâve had Shift stuck as well once or twice. Seems to happen when I do three-key shortcuts like Ctrl-Shift-Tab or Ctrl-Fn-PgDn, but not always. Itâs just enough to be annoying.
I recently watched this video by Ben Eater on how keyboards work. Seems like the issue could be tracked down with a scope but mine is pretty basic and doesnât have binary decoding so I donât think thatâs something I want to go through manually 
hello, i just bought chuwi minibook x and try install ubuntu 22.04. all feature works fine, except WiFi.
resume of my installation using this command :
inxi -Fxxxrz && rfkill list && iwconfig && mokutil --sb-state
result :
System:
Kernel: 5.19.0-41-generic x86_64 bits: 64 compiler: N/A
Desktop: KDE Plasma 5.24.7 tk: Qt 5.15.3 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
Machine:
Type: Convertible System: CHUWI Innovation And (ShenZhen)
product: MiniBook X v: N/A serial: <superuser required>
Mobo: N/A model: N/A serial: <superuser required> UEFI: N/A
v: ZW-BI-105-S105JWR210-JCB0A-101-I date: 01/13/2023
Battery:
ID-1: BAT0 charge: 28.9 Wh (100.0%) condition: 28.9/28.9 Wh (100.0%)
volts: 8.7 min: N/A model: WB SR 1 WB Lion Battery type: Li-ion
serial: <filter> status: Charging
CPU:
Info: quad core model: Intel Celeron N5100 bits: 64 type: MCP
smt: <unsupported> arch: Tremont rev: 0 cache: L1: 256 KiB L2: 1.5 MiB
L3: 4 MiB
Speed (MHz): avg: 1004 high: 1100 min/max: 800/2800 cores: 1: 1100 2: 717
3: 1100 4: 1100 bogomips: 8908
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel JasperLake [UHD Graphics] driver: i915 v: kernel ports:
active: DSI-1 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:4e61 class-ID: 0300
Device-2: HYGD-220831-A Hy-Usb2.0-1 MIC type: USB driver: uvcvideo
bus-ID: 1-7:3 chip-ID: 1b0a:2bc9 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.4 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.0x12.5")
s-diag: 599mm (23.6")
Monitor-1: DSI-1 res: 1920x1200 hz: 60 size: N/A modes: 1200x1920
OpenGL: renderer: Mesa Intel UHD Graphics (JSL) v: 4.6 Mesa 22.2.5
direct render: Yes
Audio:
Device-1: Intel driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
chip-ID: 8086:4dc8 class-ID: 0403
Device-2: HYGD-220831-A Hy-Usb2.0-1 MIC type: USB driver: uvcvideo
bus-ID: 1-7:3 chip-ID: 1b0a:2bc9 class-ID: 0e02 serial: <filter>
Sound Server-1: ALSA v: k5.19.0-41-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX201 160MHz driver: iwlwifi
v: iwlwifi-stack-public:master:9904:0e80336f bus-ID: 00:14.3
chip-ID: 8086:4df0 class-ID: 0280
IF-ID-1: enxc299414d779d state: unknown speed: -1 duplex: half
mac: <filter>
Bluetooth:
Device-1: Sony Ericsson Mobile AB G8441 (Xperia XZ1 Compact) [Tethering]
type: USB driver: rndis_host v: kernel bus-ID: 1-2:5 chip-ID: 0fce:71f4
class-ID: 0a00 serial: <filter>
Device-2: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-8:4 chip-ID: 8087:0026 class-ID: e001
Report: ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter>
Drives:
Local Storage: total: 476.94 GiB used: 25.03 GiB (5.2%)
ID-1: /dev/nvme0n1 model: NS512GSSD530 size: 476.94 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: V0323A0 temp: 47.9 C scheme: GPT
Partition:
ID-1: / size: 467.89 GiB used: 25 GiB (5.3%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 511 MiB used: 31.3 MiB (6.1%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: apt: 4055
Active apt repos in: /etc/apt/sources.list
1: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
2: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
3: deb http://archive.canonical.com/ubuntu jammy partner
4: deb http://archive.ubuntu.com/ubuntu jammy-security main restricted
5: deb http://archive.ubuntu.com/ubuntu jammy-security universe
6: deb http://archive.ubuntu.com/ubuntu jammy-security multiverse
7: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted
8: deb http://archive.ubuntu.com/ubuntu jammy-updates universe
9: deb http://archive.ubuntu.com/ubuntu jammy-updates multiverse
Active apt repos in: /etc/apt/sources.list.d/deadsnakes-ubuntu-ppa-jammy.list
1: deb https://ppa.launchpadcontent.net/deadsnakes/ppa/ubuntu/ jammy main
No active apt repos in: /etc/apt/sources.list.d/gnuradio-ubuntu-gnuradio-releases-jammy.list
Active apt repos in: /etc/apt/sources.list.d/kismet.list
1: deb https://www.kismetwireless.net/repos/apt/git/jammy jammy main
Active apt repos in: /etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list
1: deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy main
No active apt repos in: /etc/apt/sources.list.d/ondrej-ubuntu-php-jammy.list
No active apt repos in: /etc/apt/sources.list.d/osmocom-latest.list
No active apt repos in: /etc/apt/sources.list.d/softwareradiosystems-ubuntu-srsran-jammy.list
Info:
Processes: 228 Uptime: 23m wakeups: 1 Memory: 11.44 GiB
used: 2.05 GiB (17.9%) Init: systemd v: 249 runlevel: 5 Compilers:
gcc: 11.3.0 alt: 11/12 Shell: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.13
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
lo no wireless extensions.
enxc299414d779d no wireless extensions.
SecureBoot disabled
Platform is in Setup Mode
the main problem is:
- dkms
- backport-iwlwifi-dkms
- iwlwifi
- libbpf not detected while manual compile backport-iwlwifi
wifi detected is : Intel Wi-Fi 6 AX201 160MHz
anyone is success up the WiFi ? thankyou advance 
âŠ
With the upgrade to kernel 6.4 and the latest Linux firmwares the keyboard issue seems to have been resolved. At least I did not experience it anymore in the last three days of use.
2 Likes
Unfortunately not. I tried right away after your message with a fresh NixOS install running Kernel 6.4.2, and the problem is still there. The easiest way Iâve been able to get the problem to rear its head is to boot up a game of some kind and play just a little bit, as heat seems to increase the likeliness of it happening. Less than two minutes into a Xonotic session against bots and my entire keyboard stopped responding again, which is one of a few ways this issue exposes itself.
So unfortunate, as this device is completely unusable for me due to this issue :(.