Re: boot error
Posted: Wed Feb 19, 2025 12:40 am
Can I use snapshot, then MX Linux USB Maker, and just do a fresh install to solve this problem?
But you will only really know through use.bcreighton wrote: Wed Feb 19, 2025 11:11 am But, it seems to boot and work fine when I use a MX Linux made USB copy?
The MX Live system runs in ram only which is why it seems to work. But when you try to access the HDD, it crashes so it seems obvious that the HDD is the problem.bcreighton wrote: Fri Feb 21, 2025 10:42 am Yea, fresh install, same result. Installed graphic card's codecs, no dice. Think thats it. Odd, the same OS runs off my USB stick without a hitch. Can't figure that one out, but I give up
You can also try (add) the:Kermit the Frog wrote: Thu Nov 28, 2024 8:14 am... you can add
in kernel parameters box in "MX Boot Options".Code: Select all
loglevel=3
i.e. loglevel=0 will print emergency messages only (when system is about to crash or is unstable).https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt wrote:Code: Select all
loglevel= [KNL,EARLY] All Kernel Messages with a loglevel smaller than the console loglevel will be printed to the console. It can also be changed with klogd or other programs. The loglevels are defined as follows: 0 (KERN_EMERG) system is unusable 1 (KERN_ALERT) action must be taken immediately 2 (KERN_CRIT) critical conditions 3 (KERN_ERR) error conditions 4 (KERN_WARNING) warning conditions 5 (KERN_NOTICE) normal but significant condition 6 (KERN_INFO) informational 7 (KERN_DEBUG) debug-level messages
In fact quiet is the equivalent of loglevel=4 that's why the system lets the "warning" messages be printed. By the way, no matter you use loglevel 3 or less they're still recorded in log files (in case one needs to search/inquire something). You can also change the splash to nosplash if you prefer the flowing text (like me) but you don't have to.
Code: Select all
intremap=off