Fn key doesn't work

The fn key doesn’t in my laptop, it was working when using window ? so what should i do ?

Please post the output of inxi -Fxza

Welcome to the forum!

Please see:


how would that be useful ?

It shows what kernel you’re on, what laptop you’re using, what BIOS version you’re on, some drivers, etc.

1 Like

Sorry, can’t be politically correct reading that :

I luv’ when I see an OP:

  1. NOT answering an helper command suggestion
  2. Questioning the very command.

Hey ! Asparagus : U asked for help !

  1. Give us the command outcome, point !
  2. Or tell us you know it all and shut the thread.

Bonus : learn politeness : it is thank people who read your OP…

1 Like

@nam1962 You can be PC, you know… that was insulting to Asparagus! :stuck_out_tongue: Plus the OP was probably just wanting to know what that was going to do before running it.

@SeifTahawy54 Without some basic info about your system, it’s pretty hard to work out where to start with diagnosing what could be the problem. Hence why a moderator also linked a thread on ‘how to provide good information’ when asking for support. You will find out when you take the time to read that post that it tells you to ALWAYS provide the output of inxi -Fza (which is a tool that shows information about your hardware and operating system configuration), properly formatted as code, so that those you are asking for help have that baseline to work from.

1 Like

If you read the page linked by the moderator you will know how that would be useful.

1 Like

Well, I apologize to any offensed asparagus :nerd_face:
In due escalation, asparagus comes before cauliflower and well before dreaded broccoli. (this to show that I was overly polite)

Indeed, in this type of thread, several thousands of experiences showed me that if a garden appellation didn’t generate OP’s excuses, it was because a troll was revealed… :japanese_goblin:

Hey people,
firstly, thanks for help i didn’t mean to be rude i just asked because i’m curious about how it would be useful :grinning:.
second, i’m sorry that i haven’t read the instructions carefully.
third, there is the output

System:    Kernel: 5.7.14-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 
           root=UUID=05872a85-2790-430f-a93f-a3eb98896785 rw quiet apparmor=1 security=apparmor 
           resume=UUID=11d424d7-e083-428d-9604-e910c85a15c7 udev.log_priority=3 
           Desktop: KDE Plasma 5.19.4 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: LENOVO product: 81BF v: Lenovo ideapad 520-15IKB serial: <filter> 
           Chassis: type: 10 v: Lenovo ideapad 520-15IKB serial: <filter> 
           Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <filter> UEFI: LENOVO v: 6JCN23WW 
           date: 01/23/2018 
Battery:   ID-1: BAT0 charge: 24.7 Wh condition: 25.4/35.0 Wh (73%) volts: 8.4/7.6 
           model: LGC L16L2PB3 type: Li-poly serial: <filter> status: Unknown 
CPU:       Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Kaby Lake 
           family: 6 model-id: 8E (142) stepping: A (10) microcode: D6 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28808 
           Speed: 2046 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 3088 2: 3326 3: 3312 4: 3010 
           5: 2918 6: 3291 7: 3249 8: 3305 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: 
           conditional, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:5917 
           Device-2: NVIDIA GP108M [GeForce MX150] vendor: Lenovo driver: nvidia v: 440.100 
           alternate: nouveau,nvidia_drm bus ID: 01:00.0 chip ID: 10de:1d10 
           Device-3: Syntek EasyCamera type: USB driver: uvcvideo bus ID: 1-8:5 chip ID: 174f:241a 
           Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: modesetting,nvidia 
           alternate: fbdev,intel,nouveau,nv,vesa display ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.1.5 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           alternate: snd_soc_skl bus ID: 00:1f.3 chip ID: 8086:9d71 
           Sound Server: ALSA v: k5.7.14-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo 
           driver: r8169 v: kernel port: 3000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Lenovo 
           driver: ath10k_pci v: kernel port: 3000 bus ID: 03:00.0 chip ID: 168c:0042 
           IF: wlp3s0 state: up mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-7:4 chip ID: 0cf3:e500 
Drives:    Local Storage: total: 1.03 TiB used: 321.90 GiB (30.6%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda vendor: Samsung model: MZ7TE128HMGR-00004 size: 119.24 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 300Q scheme: GPT 
           ID-2: /dev/sdb vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: LCM2 scheme: GPT 
Partition: ID-1: / raw size: 110.15 GiB size: 107.92 GiB (97.98%) used: 20.21 GiB (18.7%) fs: ext4 
           dev: /dev/sda2 
Swap:      Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2 
       dev: /dev/sda3 

Sensors: System Temperatures: cpu: 49.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 279 Uptime: 2h 15m Memory: 7.56 GiB used: 3.59 GiB (47.5%) Init: systemd
v: 245 Compilers: gcc: 10.1.0 Packages: 1335 pacman: 1322 lib: 347 rpm: 0 flatpak: 5
snap: 8 Shell: Bash v: 5.0.18 running in: konsole inxi: 3.1.05

finally, sorry if you understand that i was rude :smiley:

You should update your BIOS. Looks like there is a newer one released 01/12/20.

Also you can try Kernel 5.8, it fixes some laptop issues for some people.

1 Like

Well, you just proved :

  1. that you’re not an asparagus, nor other green stuff with hairs :stuck_out_tongue:
  2. that my method to demonstrate point 1 can be harsh but is efficient :wink:

Possible alternate test for your key :

sudo showkey

Then test fn - f11 then f11
you should have

keycode 114 press
keycode 114 release
keycode  87 press
keycode  87 release

If possible, try the same from a live session

Thanks, i’ll try this solution

Hi, i’ve tried this and the key isn’t visible.

Even from a live session ?

It working now :smiley: