Patch for Bazzite Kernel as CONFIG_ACPI_DEBUG not set.

[fawqsir]

I am currently on Bazzite, using the Bazzite kernel. This kernel does not have CONFIG_ACPI_DEBUG not set. I have opened an issue there. Is there a way to create a patch for their kernel?

I am using a GL65 9SE laptop and have been using MControlCenter on previous distros (Nobara and Arch) with the only issue being shift. I would like to continue to use this as it is excellent.

I am going to link this issue to the already opened issue in the bazzite kernel.

[mutchiko]

only issue being shift

looks like you didn't install msi-ec, future builds of MCC will warn you about that, so you might want to build it from source. for your testing, since it will report msi-ec and ec_sys module status.

as for bazzite, i can't help you much since i have no experience with such distros. however, if you find a way to make things work together (app + modules), please share with us so we can add steps to the readme that other people can follow.

[fawqsir]

Will the ec_sys module in the kernel with ACPI_EC_DEBUGFS enabled be enough to allow write support and MControlCenter to work properly?

[mutchiko]

please read the readme, you need to also install msi-ec for the app to work properly, ec_sys is only used for fan control, so you will loose some functions like shfit mode for example.

[mutchiko]

any update on your situation? the discussion in the bazzite issue that you opened seems to have stalled...

[fawqsir]

I realize that they want me to work on install msi-ec for all things to work properly. However I have not pursued that as I have prioritized getting the ec_sys module to load. I want the fans to work. That is still unsuccessful. I have successfully installed msicontolcenter. But without the ec_sys module loading, I still cannot control fans. Bazzite has enabled ACPI_EC_DEBUGFS in the testing rebase instead, due to security? The ec_sys module will not load for me with that option enabled. I tried to get others on The bazzite discord to try. No one replied there either. Please rebase to bazzite testing and try to load the ec_sys module. Report your findings. There was a fellow on the bazzite GitHub that was helping. If there is more interest I could try again.

…

On Sat, Jul 12, 2025, 2:27 p.m. mutchiko ***@***.***> wrote: *mutchiko* left a comment (dmitry-s93/MControlCenter#238) <#238 (comment)> any update on your situation? the discussion in the bazzite issue that you opened seems to have stalled... — Reply to this email directly, view it on GitHub <#238 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL7B4IOJMV3PDKJVTZ7YOC33IFVU5AVCNFSM6AAAAAB4NEOVNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANRWGAZDOOJYGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mutchiko]

@fawqsir how about you use a distro that allows access to kernel modules? your situationid kind of expected with immutable distros.

you still have fedora that bazzite is based on as an option.

[NullsetForge]

@mutchiko there are many reasons why people use bazzite, and it being immutable (while I don't condone it) is one of the positive reasons to use it for the common user.

Could you look at this thread and see if you could help the bazzite kernel devs to get this working?
just for the sake of helping the community who could greatly benefit from MControl working on that distro

https://github.com/bazzite-org/kernel-bazzite/issues/25

[mutchiko]

Closing since there is nothing i can do from my side.