Bug 1451 - Functional keys Fn+ do not work for laptop ASUS k55D
: Functional keys Fn+ do not work for laptop ASUS k55D
Status: RESOLVED WORKSFORME
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: Marathon
: All Linux
: Normal normal
: ---
Assigned To: ROSA Linux Bugs
: ROSA Linux Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-14 15:31 MSK by FirstLevel
Modified: 2013-02-14 14:56 MSK (History)
2 users (show)

See Also:
RPM Package: kernel-nrj-desktop-3.0.38-1rosa.lts-1-1
ISO-related:
Bad POT generating:
Upstream:


Attachments
diag.txt (19.02 KB, text/plain)
2013-01-14 15:32 MSK, FirstLevel
Details
dmesg_messages.-in-ltstxt.txt (48.03 KB, text/plain)
2013-01-16 09:49 MSK, FirstLevel
Details
32.png (171.16 KB, image/png)
2013-02-02 14:24 MSK, FirstLevel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description FirstLevel 2013-01-14 15:31:11 MSK
Description of problem:
I have laptop  ASUS K55D  with ROSA Marathon 2012 LTS installed. Functional keys for my laptop (Fn+F*) do not work.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 FirstLevel 2013-01-14 15:32:01 MSK
Created attachment 1046 [details]
diag.txt
Comment 2 FirstLevel 2013-01-14 15:32:15 MSK
I have attached lspcidrake and lshw output
Comment 3 Denis Silakov 2013-01-14 15:44:03 MSK
Can you also provide dmesg output after pressing a problematic key? It's interesting to check if it has 'Unknown key pressed' messages.

It's also interesting if these keys work in Desktop.Fresh 2012 (one can try 'live' mode, no need to install).
Comment 4 FirstLevel 2013-01-16 09:49:08 MSK
Created attachment 1057 [details]
dmesg_messages.-in-ltstxt.txt

It is output of dmesg command and tail -n 100 /var/log/messages in ROSA 2012 LTS
Comment 5 Denis Silakov 2013-01-25 22:42:55 MSK
Interesting, I don't see the messages I've expected to find there...

I can't provide a ready-to-use solution atm, only to perform some experiments (like in bug #1381). First, it makes sense to check what 'xev' command says when you press a problematic key (https://wiki.archlinux.org/index.php/Extra_Keyboard_Keys). If you see something with xev for your keys, you may follow the way suggested in bug #1381.

Otherwise one should require to dig deeper, like here: http://crunchbang.org/forums/viewtopic.php?id=19034
Comment 6 FirstLevel 2013-02-02 14:24:29 MSK
(In reply to comment #5)
> Interesting, I don't see the messages I've expected to find there...
> 
> I can't provide a ready-to-use solution atm, only to perform some
> experiments (like in bug #1381). First, it makes sense to check what 'xev'
> command says when you press a problematic key
> (https://wiki.archlinux.org/index.php/Extra_Keyboard_Keys). If you see
> something with xev for your keys, you may follow the way suggested in bug
> #1381.
> 
> Otherwise one should require to dig deeper, like here:
> http://crunchbang.org/forums/viewtopic.php?id=19034

In LTS RElease after execution of command: xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'
user has got such output - see attach 32.png
While pressing pronlem keys (fn+f7) nothing is appeared in konsole


In ROSA 2012.1 Fresh live mode all functional keys are working.

Объясните, пожалуйста.
С уважением Кирюшин О.Н.

Added document : Document Ticket 3508 - 32.png
Comment 7 FirstLevel 2013-02-02 14:24:48 MSK
Created attachment 1130 [details]
32.png
Comment 8 FirstLevel 2013-02-14 14:56:55 MSK
Case is not actual for user