Comment 3 for bug 385477

This patch addresses an issue in the r4100 series - mine particularly is the R4125CA.

If there are more in the R4000 series this could very well apply as well. Though, i need to make sure the quirk is the same with the following information:

Can you post the output of the following from outside of X (i.e. no gui)

# scankey -s > mykeylog.txt
on keyboard, press volume down a few times, then press volume up (-- then wait for 10 seconds to make the program exit, since ctrl-c is deactivated while it runs)

We may also need the output of dmidecode, so that we can properly identify your hardware, to identify it to the kernel. You can run this safely in or out of X.

# dmidecode > dmi_log.txt

this program is available from sys-apps/dmidecode .

I can then add a few lines to also include the first R4000 series (i.e. >= R4000, <=R4099 )

Thanks for the help :)