-
-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swap fn and Ctrl key (t430s) #711
Comments
It is possible to patch the cmos layout in the coreboot source. Unfortunately I get lost in the Heads source code and couldn't find out how to add an additional option for the patch. |
Solution: |
I have the same issue, but I am on x230 with a classic keyboard (https://www.thinkwiki.org/wiki/Install_Classic_Keyboard_on_xx30_Series_ThinkPads). I was suggested to apply the fn and ctrl swap via nvramtool (see |
Have you followed the instructions on this page? If not, do this first:
Please keep in mind: Executing nvramtool in dom0 might be a threat to your system security. If this did not work, you can still rebuild Heads with the changed cmos settings (swapped fn&ctrl key and the like) and flash it again. Hope this helps. A more simple step by step explanation takes to much time for me as well unfortunately. The best I can do at the moment is already covered in my wiki linked above. |
@Siproqu is there a PR to merge upstream? |
Yes there is: linuxboot/heads-wiki#77 |
@Siproqu yes sorry, just totally forgot about it! Interesting that you could just hexedit Mac address in both sections. Will test this on x230 soon |
I did
what results in
Is that correct? I am confused about "dirty". |
I successfully built heads for my T430s (pull requests are coming soon). As the fn and ctrl key are swapped on this model (the ctrl key is not under to the shift key) it is extremely annoying to use Qubes with its ctrl+shift+c/v shortcuts.
Usually people using the nvramcui to swap them. But how should I do it in Heads?
Do I have to rebuilt Heads with nvramcui enabled in the coreboot settings? Or is there another way?
The text was updated successfully, but these errors were encountered: