The two kernels of the two topics we have about this are both nvidia-tainted like the one in the report, so I think this would not add value. But now that you say it, @kquote03 added a third one and noted that he uses default Intel graphics.
@kquote03 Can you check the output of cat /proc/sys/kernel/tainted? Maybe some information from an untainted system can help if you would be willing to provide logs. If the value of the “tainted” file is 0, your kernel is not tainted.
If the output of the command is 0 and if you are willing to provide information for this, you would have to re-create the problem (so, remove the asus_ec_sensors from blacklist), reboot, and if you then experience the problem again, get the output within the affected boot with journalctl --no-hostname -k > dmesg.txt → this dmesg.txt file is what we could provide to the bug report.
My system seems to be holy, so here’s the output of dmesg.txt (I removed some MAC addresses for obvious reasons, I also removed the blacklist and rebooted, the problem appeared again as expected) Ubuntu Pastebin
Another note, suspend DOES work if I manually click suspend, but it doesn’t suspend when closing the lid.
Btw I’m very pleasantly surprised by the amount of effort from your side to fix this, that’s freaking awesome. Thank you so much!
I don’t merge the topics to not mix the elaborations in order to keep it comprehensible.
Thanks for providing more information!
I think we provided what we can so far I forwarded the issue to the maintainer of the driver (see bugzilla). Let’s wait if he or our kernel team need further information from us. For now, I would say our job is done.
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
(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).
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.
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.
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:
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.
With your preferred search engine, you can find many HowTo’s, tutorials and guides for nano or other editors (vi, vim, 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.