Media keys misbehaving and double press in a fresh install

rajeevrdev

New Member
Joined
Jul 23, 2023
Messages
12
Reaction score
6
Credits
98
I just installed linux mint 21.2 on my asus vivobook 16 and it hasnt been easy. linux kernel 6.0.2-26. Currently i am having many trouble with media keys.

Issues
  • Caps lock key acting as lower brightness key as well
  • Media keys single press acting as double press. Single press on mute would mute it then unmute. Same with volume up(increase twice), down, brightness up, down
  • Print screen also acting as brightness down as well.

These happen regardless of fn lock. Things I have tried.
  • Trying to change shortcut of mute with key press but issue remain.
  • Disabling key repeat in keyboard but issue remain

I am adding xev output for key presses. I really dont understand what it means. Any help to solve these would be appreciated

Caps lock
Code:
KeyPress event, serial 38, synthetic NO, window 0x5800001,
    root 0x770, subw 0x0, time 3421828, (267,778), root:(299,842),
    state 0x10, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

PropertyNotify event, serial 38, synthetic NO, window 0x5800001,
    atom 0x1cd (XKLAVIER_STATE), time 3421831, state PropertyNewValue

KeyRelease event, serial 38, synthetic NO, window 0x5800001,
    root 0x770, subw 0x0, time 3422041, (267,778), root:(299,842),
    state 0x12, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

MappingNotify event, serial 38, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 38, synthetic NO, window 0x5800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 39, synthetic NO, window 0x5800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 39, synthetic NO, window 0x0,
    keys:  4294967177 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0


Mute
Code:
FocusOut event, serial 38, synthetic NO, window 0x5800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 38, synthetic NO, window 0x5800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 38, synthetic NO, window 0x0,
    keys:  4294967216 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

MappingNotify event, serial 38, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 38, synthetic NO, window 0x5800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 39, synthetic NO, window 0x5800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 39, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

Brightness up
Code:
MappingNotify event, serial 38, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 38, synthetic NO, window 0x5800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 39, synthetic NO, window 0x5800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 39, synthetic NO, window 0x0,
    keys:  4294967177 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

MappingNotify event, serial 39, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 39, synthetic NO, window 0x5800001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 40, synthetic NO, window 0x5800001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 40, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
 


Were you having these issues with the stock kernel that came with 21.2, or did they start when you installed linux kernel 6.0.2-26?

Was there something that you were having problems with that necessitated the installation of linux kernel 6.0.2-26?
 
Last edited:
Maybe it was something to do with the patch that was issued - https://www.linuxcompatible.org/story/linux-kernel-602-released/
The OP didn't give much info in his first post, and the VivoBook (especially the VivoBook 16), depending on specific model can have some cheap hardware configs, such as mediatek wifi modules which are not well supported.
https://www.linux.org/threads/wifi-not-working-on-asus-vivobook-16.46047/
I saw that he went up to the linux kernel 6.0.2-26, and thought it might be to solve the cheap wifi adapter problem.
Thats' why I asked:
Were you having these issues with the stock kernel that came with 21.2, or did they start when you installed linux kernel 6.0.2-26?

Was there something that you were having problems with that necessitated the installation of linux kernel 6.0.2-26?
 
Last edited:
Yes these issues existed in 5.15 kernel as well. I updated the kernel as i had wifi driver issue which is still not supported. But I stick to this kernel as it works without any issues. The above issues were present in older kernel as well. I am not sure how to go about fixing it.
 
That wifi post was by myself. I wanted to separate issues.
Does skipping that model mean it won't be supported in the future? It's wifi 6e card.
The issue above is single press to mute button acts as two presses.
 

Solutions for some bugs in Linux Mint 21.2

There are 4 different models of the Vivobook on Asus's website.
And, there are other models too. You didn't say which one you own.

Which model do you have rageevrdev?

You may want to have a look in your "Driver Manager" and see what's there.
If there are additional drivers that Mint can find it will show.

Another practice would be to update/upgrade the BIOS.
Should you decide to do that make sure that the BIOS upgrade is for your "exact machine and exact model". Also, double check it before you do it as if you have the wrong BIOS upgrade it could turn your machine into a brick.

 
Does skipping that model mean it won't be supported in the future? It's wifi 6e card.
Just because it's a Wifi 5e card doesn't necessarily mean it will get support. One would hope it will, but it's a cheap wifi adapter that's not used on many laptops.
 
If you still have the wifi issue and you want to stick with Mint you could purchase a wifi dongle and blacklist the onboard nic that's onboard.
Just an idea.
 
If you still have the wifi issue and you want to stick with Mint
It's not a "Mint" issue, it's a kernel issue. They've got support for older and newer mediatek wifi adapers, but skipped right over the model he has. Second to last post here
 
It's not a "Mint" issue, it's a kernel issue. They've got support for older and newer mediatek wifi adapers, but skipped right over the model he has. Second to last post here
Shame the kernel doesn't have support for OP machine.

I did research for 2 weeks before I did my last pc build to ensure that there was support in the Linux kernel.

Is there a Linux Compatability List on this site?
 
I did research for 2 weeks before I did my last pc build to ensure that there was support in the Linux kernel.
ALWAYS bro! :cool:
The OP should've returned it instead of buying a usb Wifi dongle, and purchased something with an Intel Wifi adapter, but he just said it's been two weeks. Not sure if the return window is still open.
 
It has been 2 weeks. I bought a usb wifi dongle.
Then if you haven't went past Asus's return policy you may be able to return it to them for a refund.

What's Asus's policy on returning your laptop?
 
ALWAYS bro! :cool:
The OP should've returned it instead of buying a usb Wifi dongle, and purchased something with an Intel Wifi adapter, but he just said it's been two weeks. Not sure if the return window is still open.
Agreed!:-
 

Members online


Top