I recently moved to MX Linux and I am planning to stay to it and use it as my main OS. I have been using it for like a good 2 weeks now but from time to time I am experiencing total environment freeze. At first I thought maybe it just needs a restart or whatever but it happened like 4-6 times randomly. I also read about some topics here regarding the same problem but the solutions were not that absolute and kinda like hit and miss solutions. It seems like this is a hardware problem so do you suggest that I just move to another distro? But I developed a liking to MX already and I want to fix the problem. Please help me.
to your grub-menu. You can do this using MX Boot Options (MX Tools) by adding the above kernel parameter to the existing "quiet", so the line looks like
fehlix wrote: ↑Wed Apr 17, 2019 11:21 am
Welcom to the forum!
This is probably related to a nouveau driver issue. Please try adding this boot-parameter
to your grub-menu. You can do this using MX Boot Options (MX Tools) by adding the above kernel parameter to the existing "quiet", so the line looks like
Yo! Thanks for your reply! I will do this and test the environment afterwards. I'll mark the post as solved if the this will do the trick! :) I am excited haha!
Bluesguy wrote: ↑Wed Apr 17, 2019 11:52 am
In addition, hardware checks are always a good thing.
Sometimes a laptop CPU runs too hot due to the CPU heat sink fan exhaust being clogged or fan not functioning ... this certainly can be one of the causes of the "freeze" symptoms you're experiencing ... You can check this in your terminal by running:
$ sudo sensors-detect
This program will help you determine which kernel modules you need to load to use lm-sensors most effectively. It is generally safe and recommended to accept the default answers to all questions. In other words, just press ENTER for each question until the sensor script is set up. After that's done, type "sensors" in the terminal and you'll get the output ... tells you if the CPU is within a safe temperature range.
A hot, malfunctioning drive can also be a culprit ... this can be checked using GSmartControl found in your apps Menu under System ... gives info about the health and temps of your drive(s).
These are some basic hardware checks you can use from time to time. Lastly, try a memtest from your boot options ... it takes a long, long time, but the health status of your memory modules will be verified.
Yo! Thanks for the inputs. For the memtest, I've tried it before installing the OS and I got no issues. For the hardware too hot issue, I think it is not the case because I encountered a freeze after just logging in. Around 2 minutes after logging in. Thanks for the suggestions and I will look into them :)
And if those measures don't fix the issue, there is a BIOS update (from 12/2016) for that motherboard. Those are often released to fix instability issues - although Asus hasn't released any information I can find why this update was released.
timkb4cq wrote: ↑Thu Apr 18, 2019 11:45 pm
And if those measures don't fix the issue, there is a BIOS update (from 12/2016) for that motherboard. Those are often released to fix instability issues - although Asus hasn't released any information I can find why this update was released.
I am currently testing my computer with the added configs in the boot option. If all else fails, do you mind if I ask you how do I update the BIOS? Thanks!
timkb4cq wrote: ↑Thu Apr 18, 2019 11:45 pm
And if those measures don't fix the issue, there is a BIOS update (from 12/2016) for that motherboard. Those are often released to fix instability issues - although Asus hasn't released any information I can find why this update was released.
I am currently testing my computer with the added configs in the boot option. If all else fails, do you mind if I ask you how do I update the BIOS? Thanks!
timkb4cq wrote: ↑Thu Apr 18, 2019 11:45 pm
And if those measures don't fix the issue, there is a BIOS update (from 12/2016) for that motherboard. Those are often released to fix instability issues - although Asus hasn't released any information I can find why this update was released.
I am currently testing my computer with the added configs in the boot option. If all else fails, do you mind if I ask you how do I update the BIOS? Thanks!
fehlix wrote: ↑Wed Apr 17, 2019 11:21 am
Welcom to the forum!
This is probably related to a nouveau driver issue. Please try adding this boot-parameter
to your grub-menu. You can do this using MX Boot Options (MX Tools) by adding the above kernel parameter to the existing "quiet", so the line looks like
I was wondering if there are any log files which can be read to pinpoint the cause of the problem? If anyone knows it please do tell. I'm willing to take some time to do some research and fix the issue. :)