@kquote03 @ali-guest01 @burakdede
The maintainer suggested to try a patch that is for a similar issue. Maybe it will solve this issue as well. It is up to you if you are interested in testing it and report in order to finally get rid of it in future kernels. There is no obligation! And be aware: if you do, you make your system to a testing environment, which means unintended behavior cannot be excluded - be prepared for that (have a live usb stick with Fedora ready, backup). I don’t expect it in this case but in testing you should always be prepared. Therefore, no worries if you prefer to not do this. But maybe you have fun in making such experiences
See the bugzilla report if you are interested 2121844 – Battery percentage gets stuck at a certain level (asus_ec_sensors locks ACPI mutex) and I suggest to use 5.19.6 for testing (and don’t forget, when testing, to remove the driver from blacklist):
Testing Patches :: Fedora Docs
(Just in case: open a new topic with reference to this one if there are issues with preparing/conducting testing!)
Alternatively, it seems likely that this patch ends up in a future kernel anyway as it solves the issue it originally was developed for. So in this case, we can re-test it later once the kernel with the patch has been released. Might be easier if you prefer to not engage in testing.
To be honest I have no idea what is blacklisting the module and how to do that. Could you please explain what it is and how to do that, that would be very nice of you) I need to learn a lot since I am very new!!! It has not even been two weeks since I moved from windows 11 to fedora 36(to linux as a whole).
Sadly, updating did not help
You are not the only one
First, please focus your question in one thread. This avoids that we have to do double work here.
Second, I suggest to not downgrade in this case. Using a previous kernel is something you do to jump over one kernel that causes troubles when released, so a short time thing. And even in this case it should be checked if the kernel you are reverting to has security issues.
So, you should use the blacklist option for now. You can find our “official” workaround for this bug here: Battery charge indicator broken on certain ASUS motherboards, automatic suspend doesn't work
When playing with commands like those in the workaround, especially when you have no other menu entries you can revert to, always have a USB stick or such with a live Fedora system prepared to use it to revert the steps in case of unintended outcomes!
With the commands and information of the steps you can find much more information about these issues with your preferred search engine.
However, I strongly suggest to try it again without blacklisting with each future kernel update! The issue is known and likely to be fixed in the next kernel update or the one after that. Removing the blacklisting is explained in the workaround link as well. Although this module is not critical, I suggest to not keep it disabled for all time. It is one of those that can cause you trouble if you forget about its blacklisting at some point but want to retrieve (or if an application wants to retrieve) information it provides without remembering why it is not provided that.
Supplement: another related thread: Power indicator state not working in kernel 19.4-200
why does it say :
bash: cd: /boot/loader/entries/: Permission denied
It has to be done with sudo. I corrected that. My bad.
I think it is my bad that I even could not figure out this myself
should it give back any kind of output? I do not see any output:
base) [Ali@ali ~]$ sudo cd /boot/loader/entries/
(base) [Ali@ali ~]$ sudo cd /boot/loader/entries/
No. cd = change directory. Within the directory, you have to check out the content, e.g., using ls. And then, when you know the file names in the directory, you can use an editor to change the respective file (don’t forget sudo). Alternatively, you can skip the cd, just write
sudo <editor> /boot/loader/entries/ but without clicking the enter button, then you push twice TAB and then it will show you the contained files. Fill the command with the respective file name, and then enter.
Also, we are currently working on creating a more comprehensible workaround for this:
That command does not give an output.
Please follow the remaining steps, but remember that sudo will be required for each command there.
^G Help ^O Write Out ^W Where Is ^K Cut ^T Execute ^C Location
^X Exit ^R Read File ^\ Replace ^U Paste ^J Justify ^/ Go To Line
@ computersavvy I suppose there has to be a bunch of code lines, am I right, oh?
Using a default F36 KDE live (the relevant data is equal to F36 Workstation) with 5.19.6, the 5.19.6 file could be opened with
sudo nano /boot/loader/entries/d239886fa9ec440db73734aeb26fa5a6-5.19.6-200.fc36.x86_64.conf → be aware that the exact file names are different in each case, only the ending is constant.
The content of the file is by default
title Fedora Linux (5.19.6-200.fc36.x86_64) 36 (KDE Plasma)
options root=live:CDLABEL=Fedora-KDE-Live-36-1-5 rd.live.image quiet rhgb
You have to work in the options line, which is line 5.
Don’t adjust your file to my example! Just focus on the instructions I made above, or on the proposed common issue workaround.
In nano, this would look like this:
With your preferred search engine, you can find many HowTo’s, tutorials and guides for
nano or other editors (
mc, …). Also, you can check
man nano (or generally,
man <editor> if it is installed)
I think it is due to oems use some software to make better battery life you should ask your oem to provide some of there code and optimizations to the kernel so that we all can have that better experience usually most brand do not provide there optimization ported to linux.
<lacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver>
Is that ok if I just add your suggested
rdblacklist=asus_ec_sensors right at the end of this options line ?
I see, but the problem is I have to wait for the next kernel up to see if the change is made and I do not even know when is the release. Anyway, thank you so much for your support!
@ py0xc3 I mean this line in my case does not end with
rhgb quiet as it is in your example. So that is ok if I just add that code at the end of the line ?
Yes, just add it to the end of your options line. Your file seems to be already modified for nvidia drivers or such.
Absolutely! I just meant that you should keep it in your mind until you see that the kernel has been updated (if you do your updates manually, you can see it directly, or if you boot and you see in grub that a new kernel is listed & booted from). When you see that an update has been done to the kernel, then try to remove the two blacklistings and check out if it works without blacklisting in the new kernel.
However, 5.19.7 is already in testing (I’m already using it : ) and should be there in a few days. You can keep the blacklisting with 5.19.7 as it has not yet a fix for the problem. But I expect the one after 5.19.7 will have.
(base) [Ali@ali ~]$ sudo echo "blacklist asus_ec_sensors" > /etc/modprobe.d/asus_ec_sensors.conf
bash: /etc/modprobe.d/asus_ec_sensors.conf: Permission denied
Should I remove quotes and try again?
First, please use preformatted text brackets for output → mark the text and use the </> button.
Second, correction: this is a special behavior of sudo in conjunction with stdin/stdout (I wasn’t aware of it as I don’t use sudo myself).
I have not much time today, but this can help you to adjust the command yourself for now:
Supplement: The solution above is adjusted. I forwarded it to the workaround. We designed and discussed the workaround to fit all types and configurations of Fedora. So I assume this will avoid issues among different configurations and such.