# Using the keyboard in your UEFI Bios **URL:** \ **Category:** Help and Getting Started\ **Created:** [October 26, 2017, 4:23pm UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544 "2017-10-26T16:23:35Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![hellothumbs](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hellothumbs](https://community.keyboard.io/u/hellothumbs)\ **Post date:** [October 26, 2017, 4:23pm UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/1 "2017-10-26T16:23:35Z")
I’m wondering if anyone else is having issues while working in their UEFI/BIOS boot screens? Here’s what I’m getting while looking at the UEFI/BIOS when booting this PC. The Model 01 is using commit:717733ad6471d27b108d97f0400d1538836d49b5 (flipped a couple thumb keys around) It happens in both “Enable Legacy USB” on and off modes. fn+l (right arrow) - moves selection up pgdn - moves selection down pgup - moves selection to next screen fn+pgdn (end) - moved selection to previous screen it should be doing the fn+hjkl (aka VIM movement bindings) to do the selection previous/down/up/right It feels like the keyboard is being detected in some strange mode when in the UEFI/BIOS screens. Anyone else seeing this behavior? What mode does the keyboard setup as when booting the PC? ---
**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\ **Post date:** [October 26, 2017, 7:39pm UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/2 "2017-10-26T19:39:12Z")
This is most likely because the keyboard is using N-key Roll Over (NKRO), while some BIOSes only support the older 6KRO. @jesse did some work on this around the time of the PVT run, if I remember correctly, but I don’t know how far he got. ---
**Author:** ![jesse](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/jesse/32/361_2.png) [@jesse](https://community.keyboard.io/u/jesse)\ **Post date:** [October 26, 2017, 10:06pm UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/3 "2017-10-26T22:06:36Z")
> [@hellothumbs](#): > > fn+l (right arrow) - moves selection up > > pgdn - moves selection down > > pgup - moves selection to next screen > > fn+pgdn (end) - moved selection to previous screen > > it should be doing the fn+hjkl (aka VIM movement bindings) to do the selection previous/down/up/right > > It feels like the keyboard is being detected in some strange mode when in the UEFI/BIOS screens. Anyone else seeing this behavior? What mode does the keyboard setup as when booting the PC? That’s REALLY weird. What I’d actually be expecting is for it to not work at all in the BIOS because we don’t have ‘legacy’ boot protocol mode support turned on yet. What PC and BIOS is this? That may help me debug a bit. This is something I consider to be a firmware deficiency, but what you’re seeing is better than I thought possible right now. I thought there was an open ticket about this, but there was not. [Boot Protocol mode and negotiation is not implemented. · Issue #220 · keyboardio/Kaleidoscope · GitHub](https://github.com/keyboardio/Kaleidoscope/issues/220) now tracks this. ---
**Author:** ![hellothumbs](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hellothumbs](https://community.keyboard.io/u/hellothumbs)\ **Post date:** [October 27, 2017, 6:49pm UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/4 "2017-10-27T18:49:24Z")
Gigabyte ga-x79-xp4 i7-3930k so not overly old In testing out the laptops, it seems laptops only like to use their internal keyboards and not any attached keyboards. ---
**Author:** ![Otso](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/otso/32/685_2.png) [@Otso](https://community.keyboard.io/u/Otso)\ **Post date:** [November 6, 2017, 7:31am UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/5 "2017-11-06T07:31:03Z")
I’m not able to use the keyboard in the BIOS or for entering BitLocker passphrase in the boot. It works with other keyboards, including my TEK. This is pretty annoying, since now have to boot my laptop detached from my docking station (which is behind my monitors), enter the BitLocker passphrase, and then attach it to the docking station. Looking forward to get issue #220 implemented! 😉 ---
**Author:** ![rapware](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/rapware/32/593_2.png) [@rapware](https://community.keyboard.io/u/rapware)\ **Post date:** [November 10, 2017, 5:48pm UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/6 "2017-11-10T17:48:44Z")
I have a dual boot system and I use the F8 key when booting to popup a HDD dialog (Asus Z87 motherboard). This does not work with the Model 01. The function key is not being detected. The Fn-Bksp does allow me to get into the BIOS and I can select the boot drive from there. I tried mapping the F8 key to a key in the Numlock layer, but that didn’t work either. Update: The assignment to the Numlock Layer actually does work. I guess I was too late when I tried it the first time. It’s just the Fn-8 that doesn’t work. ---
**Author:** ![Simon-Claudius](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/simon-claudius/32/493_2.png) [@Simon-Claudius](https://community.keyboard.io/u/Simon-Claudius)\ **Post date:** [November 11, 2017, 11:05pm UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/7 "2017-11-11T23:05:15Z")
Not sure whether this is related, but my Model 01 doesn’t produce input when logging into macOS (10.13) for the first time after booting up. ---
**Author:** ![godefv](https://avatars.discourse-cdn.com/v4/letter/g/bcef8e/32.png) [@godefv](https://community.keyboard.io/u/godefv)\ **Post date:** [October 30, 2022, 11:56am UTC](https://community.keyboard.io/t/using-the-keyboard-in-your-uefi-bios/544/8 "2022-10-30T11:56:54Z")
Hi, I also can’t use UEFI bios normally. The only thing that has produced any effect so far is F2 (fn+2) which produced the effect of F6 instead… (I am using model 100)