-
Notifications
You must be signed in to change notification settings - Fork 48
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
Titan 18HX 2024-08 build keyboard backlight not working #173
Comments
Is your keyboard RGB or just single color? Maybe they used new keyboard backlight controller |
Because I've seen on some RGB laptops that keyboard brightness key just changes mode. Yes, this changes value in EC, but MSI app use only key press event, generated by EC to switch brightness in app |
The various marketing pictures of these show multi-color lights but in linux i've only ever had the keyboard glow red. I just need a backlight working really but whatever they did when they introduced the windows AI key seems to have changed something in that regard. There's no change in the model designation but they at least changed the right ctrl key mapping to now be the "AI key" and possibly more... Also not sure what app we're talking about. |
Check maybe BIOS have control-AI remap button. About app - I mean Windows MSI app and services is uses for processing keyboard brightness key events |
What about fn lock? Does it change control-AI button behavior |
The BIOS is the same one as in the prior machine - haven't seen any new options in the basic menu nor noticed them in the advanced one. FN-lock does not make it a ctrl key: have to hold the actual fn key although other lock functions work. If they broke backlight to introduce a windowsai key where none existed, that would be impressively bad QA. :) |
@sempervictus i think what happened is that the keycodes sent to wmi/ec have been changed after introducing this "AI" key to the keyboard (maybe related to the keyboard controller?). if you can, please follow this guide to see if there are any changes compared to the current supported firmware in msi-ec.c to control the keyboard lights try using OpenRGB. who knows, it might work. |
@mutchiko I think thing which may be different is EC firmware version. Maybe keyboard layout is configured with strap resistors on board, or exists 2 generations of board with different firmware. This should be possible to find by comparing EC firmware versions. First number after dot may be different |
@mutchiko According to version list in this PR - new device might have same hardware as old one, probably keyboard type is set during finalization through DMI settings (at least this way used by other brands). Changes in DMI may require service software. But maybe EC downgrade may work too. DON'T DO EC DOWNGRADE, BECAUSE YOU CAN BRICK YOUR DEVICE!!! |
Laptop model
Titan 18HX
EC firmware version
its actually 1822EMS1.116 but reads as 1822EMS1.114 (see last PR comment)
Description
My 14th gen CPU went south, as so many do, and i had to acquire a replacement machine due to their impossible RMA policy and active refusal to honor right to repair laws (as so many vendors do). Original system was mfg date of 2023-12, new one is 2024-08. It seems that something was changed on the motherboard because the fn+f8 key does change
/sys/devices/platform/msi-ec/leds/msiacpi::kbd_backlight/brightness
but the keyboard does not light up. Moving the new motherboard to the original chassis w/ the original keyboard does not help - same deal: pressing the fn key, the f keys and arrow keys for fan buttons light up but the keyboard itself does not change brightness despite increments showing in# cat '/sys/devices/platform/msi-ec/leds/msiacpi::kbd_backlight/brightness' 3
The other oddity i'm noticing is in the way the right ctrl key now requires the fn key to be held to be recognized... seems they've changed some stuff around without changing the model designation.
This is 6.6.59, module built into the kernel tree - git log says
MSI: EC from git @ 94c2a45c with v116 update
.The text was updated successfully, but these errors were encountered: