Bug 2074493 - Fedora 36 Silverblue does not load /etc/modprobe.d module options
Summary: Fedora 36 Silverblue does not load /etc/modprobe.d module options
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kmod
Version: 36
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-12 10:55 UTC by matteo
Modified: 2023-05-25 18:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 18:07:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description matteo 2022-04-12 10:55:22 UTC
I use a Thinkpad X220. In order to control its fans, I use thinkfan. Thinkfan relies on the built-in module "thinkpad_acpi" to work. In particular, the option "fan_control=1" must be enabled in order to enable it to control the fans.

In Fedora 35 Silverblue, Fedora 35 Workstation and Fedora 36 Workstation, I can enable this option by creating the file /etc/modprobe.d/thinkfan.conf containing:

options thinkpad_acpi fan_control=1

However, in Fedora Silverblue 36 this option seems to not be read at system boot, causing thinkfan not to start.

Please note: this works in "normal" 36, it worked in Silverblue 35 and it worked in Workstation 35. It does not work on Silverblue 36, whether it is a rebase from Fedora 35 or a clean install.

Also, it works if I manually unload and load thinkpad_acpi using modprobe after boot.

I have bypassed the problem by using the following command:

sudo rpm-ostree kargs --append='thinkpad_acpi.fan_control=1'

In this way, I force the system to load the desired options at boot time. However, it seems that loading the desired options from /etc/modprobe.d does not work anymore.

P.S. I've selected as component thinkfan, but I think it's not thinkfan's fault. I do not know, however, which component causes this!

Comment 1 Sandro Mani 2022-04-12 15:02:44 UTC
I've got no experience with Fedora Silverblue, but I'd try kmod as component. Nothing thinkfan can do about this I believe.

Comment 2 matteo 2022-04-12 16:03:56 UTC
My apologies for tagging thinkfan. I've updated the bug using kmod as a component, thank you very much for the heads up!

Comment 3 Yauheni Kaliuta 2022-04-12 16:39:50 UTC
What does
modprobe -c  | grep thinkpad_acpi
show ?

Comment 4 matteo 2022-04-12 17:11:43 UTC
If I boot without the rpm-ostree kargs that I've mentioned above, the output is the following:

options thinkpad_acpi fan_control=1
alias acpi*:IBM0068:* thinkpad_acpi
alias acpi*:LEN0068:* thinkpad_acpi
alias acpi*:LEN0268:* thinkpad_acpi
alias dmi:bvnIBM:bvrI[MU]ET??WW* thinkpad_acpi
alias tpacpi thinkpad_acpi

In this case, thinkfan tells me that the module has not been loaded:

apr 12 18:59:40 abaco systemd[1]: Started thinkfan.service - thinkfan 1.3.1.
apr 12 18:59:40 abaco thinkfan[778]: ERROR: ~TpFanDriver: Resetting fan control in /proc/acpi/ibm/fan: Invalid argument
apr 12 18:59:40 abaco systemd[1]: thinkfan.service: Main process exited, code=exited, status=1/FAILURE
apr 12 18:59:40 abaco thinkfan[778]: ERROR: Module thinkpad_acpi doesn't seem to support fan_control

If I then use these two commands and restart thinkfan, it loads fine:

sudo modprobe -rv thinkpad_acpi
sudo modprobe -v thinkpad_acpi


If I boot with the rpm-ostree kargs, the output is the following:

options thinkpad_acpi fan_control=1
options thinkpad_acpi fan_control=1
alias acpi*:IBM0068:* thinkpad_acpi
alias acpi*:LEN0068:* thinkpad_acpi
alias acpi*:LEN0268:* thinkpad_acpi
alias dmi:bvnIBM:bvrI[MU]ET??WW* thinkpad_acpi
alias tpacpi thinkpad_acpi


In this case, thinkfan loads fine!

Comment 5 Yauheni Kaliuta 2022-04-12 17:26:14 UTC
So, modprobe works fine as expected. I can guess it's loaded by something  else (initramfs?) and I have no idea how.

Comment 6 Yauheni Kaliuta 2022-04-12 17:44:41 UTC
Does lsinitrd show the module?

Comment 7 matteo 2022-04-12 18:10:22 UTC
As I'm using Silverblue, I'm not sure where to find the initramfs image! The output of lsinitrd is:

No <initramfs file> specified and the default image '/boot/initramfs-5.17.2-300.fc36.x86_64.img' cannot be accessed!

Comment 8 Yauheni Kaliuta 2022-04-12 18:38:09 UTC
Anyway, I do not see at the moment any problem in kmod utilities.

Comment 9 Ben Cotton 2023-04-25 17:00:33 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 10 Ludek Smid 2023-05-25 18:07:11 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.