Macbook Pro 2018 15' Keyboard disabled in rEFLnd after rebooting from Bootcamp
An EFI boot manager utility
Status: Beta
Brought to you by:
srs5694
Menu
▾
▴
Hi, I encountered a strange problem when using rEFInd on my newly purchased 15 inch Macbook Pro. rEFInd worked well after installation and I have no problem booting / rebooting into OSX. Only after I boot into Windows 10 Bootcamp and then restart, my laptop went into rEFInd successfully but the keyboard seems disabled (arrow keys does not work, but the count down boot timer still functions). What might be causing this? Thank you for your help!
Last edit: Peter 2018-08-13
I am using the internal keyboard of the macbook pro
This seems to be the problem with the Bootcamp drivers for 2018 Macbook Pros as other users encountered the same issue.
Hi, did you have any luck resolving this? Any error messages or anything that could point to the problem?
I'm considering buying a MacBook Pro 2018 w/ Norwegian keyboard, but I do need to use rEFInd in order to enable VT-X during boot (so I can use Docker for Windows).
No, it is still not resolved yet on my Macbook Pro 2018 (I reinstalled bootcamp to make sure. This problem is still there). Maybe the new Mojave release will resolve this issue.
To clarify, this problem happens if you "restart" the computer while in Windows Bootcamp and tries to switch to MacOS using rEFInd. If you "shutdown" the computer while in Windows and then startup again, you will not have this problem.
Last edit: Peter 2018-08-18
Thanks for the clarification. I hope that annoying thing gets fixed.
By any chance, do you know if VT-X gets enabled correctly with rEFInd on Windows? Or better, does Windows for Docker work? Thanks.
In theory, the
enable_and_lock_vmxoption inrefind.confshould enable the VMX bit on the CPU, which should do what you want. This option could wreak havoc with AMD CPUs, though, so it's disabled by default. I strongly recommend you read the documentation linked to inrefind.conffor details. Note that I don't use this feature myself; it was contributed by Emerson Barcelos. I've received reports from others that it does work, though.This sounds like a USB initialization issue. Is Windows booting in EFI mode or in BIOS/CSM/legacy mode? (If you don't know, use
gdiskto see if the disk has a hybrid MBR -- if it does, then Windows is booting in BIOS mode; if not, then Windows is booting in EFI mode.) It's possible that the mode-switching is causing problems; or it's possible that rebooting from Windows is leaving the USB hardware in a state that Apple's firmware can't handle. Unfortunately, switching the Windows boot mode is non-trivial, so you might look into other alternatives, like updating or replacing your keyboard or USB drivers in Windows. I'm not a Windows expert, so I can't suggest any specifics. You might want to ask about this on a Windows forum.