![]() Seeing you’ve had it on XFCE and I had it on GNOME, the desktop environment is likely not the issue. Would love to know what causes the freezes when it screensaves, as it’ll do it when the system is idle or under any load. None of REISUB, ctrl alt combos or sysrq combos work. I have been only using it for about 6wks now, and the freezes are a thing I don’t remember happening. While the SSD had been heavily used before, when i installed F34, i did a full install from a clean slate. All of which are working and recognized by neofetch. Hardware: 6th Gen i7-6500U, 16GB RAM, 512GB SSD, integrated graphics. Now it freezes on screensave or lock screen overnight about once every week.Ĭurrent specs and situation: Linux Kernel 5.12.9, GNOME 40.1 on Xorg, and Fedora 34 as mentioned. But then it was beginning to get more intolerable and I switched back to Fedora 34, which I was always more comfortable with. So for a few months I did switch to the more commonly used Ubuntu 20.04, which was working well, except that it would randomly freeze whenever about once a week. Then I had a login loop error lock me out. Disabling ACPI will also prevent hyper-threading from working on Intel processors (though in that case there is a comprimise – acpi=ht – that might allow hyper-threading to work while still disabling most of ACPI).Īh ha! Sounds like a similar scenario to me.īefore the beginning of 2021, I was bad at upgrades, and had Fedora 27. ![]() Completely disabling ACPI, for example, will prevent the system from being able to automatically power-off when you perform a soft shutdown (you will have to press the physical unit’s power button after all the services have stopped). Another example that I personally encountered recently required adding iommu=soft to the list of kernel arguments to get the OS to load at all.īeware that there are often trade offs to setting kernel parameters to non-default values. For example, if you are having problems with power management, you can disable that feature by adding noacpi to the list of kernel command line arguments. Sometimes the problem can be worked around temporarily by disabling a particular kernel feature. Unfortunately, If you’ve done several updates since the “last known good” kernel was installed, it might be difficult to download and install the last working version from koji. The solution is typically to use an older kernel. I think when it is that “unresponsive”, it is almost certainly a problem with the kernel. The mouse, keyboard and screen are nonresponsive It’s very funny and first time that this happen to me with a GNU/Linux distro. I don’t know if this is the best place to report this, but when I shutdown my computer from Fedora 33 at the end when the computer supposedly be off, the monitor start doing a funny flickering of colors ( wach the video) I know is not a hardware issue because when I do it from Windows 10, this doesn’t happen. Maybe this has to do with Wayland being the default graphical interface but I have to say that this also happen when I login with the x.org session. It opens a full screen terminal, which will ask for a login and password and can be frustrating when you’ve never seen this terminal before.ĭoesn’t work neither, not imput of any kind work when this happen. A virtual terminal (VT) will confuse people who are new to linux. When you say it ‘opens a terminal’, most people will think it’s that little terminal program that opens up in a window. CitaI would like to add for anyone reading this, CTRL+ALT+F3 is a virtual terminal.
0 Comments
Leave a Reply. |