its the latter. the fn thing doesnt work as the fn key doesnt register input. my initial asumption is that because my kb is on apple format and i couldnt change it to windows because it requires me to press the fn key (iqunix f96)
It’s quite a lot of detailed technology talk, which I don’t expect you to understand. The main takeaway should be this:
So the problem is [temporarily] solved by running: rmmod hid_apple
This command unloads a driver that’s potentially interfering here. The driver will be loaded again on next reboot.
Which is useful, because you can just try it out and if it doesn’t work (or if it breaks something), you can just do a reboot and everything is back to normal.
You will need admin/root permissions to run this command, so the real command you need to run is: sudo rmmod hid_apple
It will ask you for your login password to confirm running the command.
If that does fix it, then we can look into making it permanent.
its the latter. the fn thing doesnt work as the fn key doesnt register input. my initial asumption is that because my kb is on apple format and i couldnt change it to windows because it requires me to press the fn key (iqunix f96)
This sounds exactly like your problem: https://bbs.archlinux.org/viewtopic.php?id=269796
It’s quite a lot of detailed technology talk, which I don’t expect you to understand. The main takeaway should be this:
This command unloads a driver that’s potentially interfering here. The driver will be loaded again on next reboot.
Which is useful, because you can just try it out and if it doesn’t work (or if it breaks something), you can just do a reboot and everything is back to normal.
You will need admin/root permissions to run this command, so the real command you need to run is:
sudo rmmod hid_appleIt will ask you for your login password to confirm running the command.
If that does fix it, then we can look into making it permanent.
thank you, ill try it asap
That just sounds like your keyboard is broken. Your keyboard switching its own functions does not involve the OS
That would have also been my intuition, but apparently the driver is involved. At least, unloading the driver solved it in this case: https://bbs.archlinux.org/viewtopic.php?id=269796