When I start my Linux system (Debian/stable), I see that the last line of dmesg states:
[ 44.043657] rfkill: input handler disabled
What does this mean?
Debian – rfkill: Input Handler Disabled
debianlinux-kernel
Related Solutions
Looking through the Wikipedia page for menuconfig I do not see a similar option. There's a bullet within that page that states the following:
The help information is distributed throughout the kernel source tree in the various files called Kconfig.
So one could use grep to search for whatever you wanted through these files. You can also use ? within menuconfig to summon the help on a given topic too. The key your lookinig for to show hidden menus and submenus appears to be z.
There's also this keyboard shortcut table included in the topic:
References
I have no real answers, but I changed my graphics card from an AMD 7950 to a AMD Vega 64. Now suspend to ram works fine on the amdgpu driver, so I suspect it was a graphics driver issue.
Best Answer
rfkill is a Linux kernel subsystem providing access to hardware and software toggle switches that enable or disable radio transmitters, such as wireless network cards and Bluetooth dongles. The Linux kernel contains an apparently deprecated functionality called
rfkill-inputthat toggles an rfkill switch from inside the kernel in response to pressing a dedicated key on the keyboard (usually labelled with a radio transmitter icon). Userspace software that wants to take over handling such keypresses can disable this built-in functionality by opening/dev/rfkilland invokingioctlwith the commandRFKILL_IOC_NOINPUT. When this happens, the kernel emits the message mentioned in the question.In other words, it’s harmless; it (probably) only means that some userspace software (for example your desktop environment) took over handling of the ‘disable radio’ key. Running
fuser /dev/rfkillmay help you discover which particular process it is.You should expect that the message will disappear altogether in a future kernel version that removes
rfkill-input, with the kernel expecting that userspace shall always be responsible for responding to such keypresses.