Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Edited the question but couldn't identify anything. FYI, I have also identified another option in the comment of this anwer which modified the grub file. But I think I'll wait to see if we can solve this in a more direct way since I don't know much about the grub, and I think changing /etc/default/grub has a high probably that it'll make my distro unbootable. Commented Apr 28, 2017 at 14:43
  • Thanks for the edit. Also edited my question with your suggestion but it didn't really work (apparently they prevent this module to be loaded if booting in UEFI for instability reasons ("bricking")). I'm going to look into debugfs, since I have no idea what that is or how to use it. Commented Apr 29, 2017 at 0:27
  • 1
    So can you boot from legacy mode instead of UEFI to test that this is what prevents the module from loading? debugfs is a filesystem that allows direct access to parts of the kernel for debugging; for this module, it allows you to issue specific commands, and one commands changes keyboard backlights at least for some models. But that doesn't help if the module doesn't load/can't work because of UEFI. Commented Apr 29, 2017 at 9:13
  • I think it's very likely, based on the things I've read, that it would work in legacy mode. The thing is that because this is a work laptop I can't re-install the system in legacy, so I guess if this is the only next step, we hit a dead-end for now. Commented Apr 29, 2017 at 14:20
  • 2
    Looks like it. For reference, here is the commit that introduced the check. Commented Apr 29, 2017 at 18:01