MX Linux Forum

I wonder if unloading the webcam and wi-fi modules before a suspend makes any difference.

I have no idea, but I think that now with two separate machines having the identical problem that the solution goes over to StarLabs...

I'm happy to report that StarLabs is responding appropriately:

Hi Jerry,

I'm opening a support ticket to help track this one and we can focus on getting to the route cause.

That's so encouraging. These are good machines.
And thanks for your work!

Now have this message and, since it is not in the repos, could use some input from @dolphin_oracle on how to proceed:

I did see that your machine went out with the AMI firmware, whilst we are currently focusing greatly on coreboot, I'd recommend switching. coreboot is starting to exceed AMI in performance and power consumption alone. However, we can look at this on AMI, as it is likely to be kernel-related for power usage on suspend.

Download page is here: https://www.coreboot.org/downloads.html

... Just, on this opportunity: Where do the Distrowatch guys get the (wrong) info from ? Or.. don't they check / verify etc..?

This just shows that it's an untrustable site / source.

Switching bios programs as got to be in the machine settings somewhere. I don’t think you’ll find a package in the repo that will do that.

Here are the instructions for installing coreboot from Starlabs:
https://support.starlabs.systems/kb/gui ... g-coreboot
I tried it when using MX 21, but it did not work.
Certain prerequisites couldn't be met under MX.
To experiment, I installed Linux Mint, and coreboot installed successfully.
I don't know why. (I no longer have that machine).


edit the above link and its links to follow were instructions for downloading and switching branches under Debian 11

Thanks to both. Have to mull this one over...

I'd first see if the 6.5 Liquorix kernel has the same issue before the drastic BIOS replacement. I also think that whatever kernel Ubuntu is using successfully will work on MX, and Ubuntu's "linux-firmware" blob is ahead of ours by about six months again, so I'd try updating ours by getting the firmware tarball from the kernel git, extracting it, and running "sudo make install" in the extracted folder.