MX Linux Forum

Thanks for your tip, @mx1926 !

I purged the previous version 4.4.1 and the install of 4.5 went without errors.

@siamhie I don't have watchdog installed.

Booting with the option nowatchdog does the trick!

I think I will make this permanent, since I never needed watchdog on my desktop systems.

This is the OP's lsmod with kernel 6.1.0-34-amd64:
$ lsmod
Module Size Used by
snd_seq_dummy 16384 0
snd_hrtimer 16384 1
snd_seq 90112 7 snd_seq_dummy
snd_seq_device 16384 1 snd_seq
fuse 176128 4
qrtr 49152 2
ctr 16384 3
ccm 20480 9
bnep 28672 2
bluetooth 958464 9 bnep
jitterentropy_rng 16384 1 ...

Hello,

after today's updates (~90 packages) boot was stuck on black screen with blinking cursor.

6.1.0-34-amd64 still works.

my only dkms-package is broadcom-sta-dkms, which is needed for WiFi. The installation ran smooth without errors.

My QSI:
System:
Kernel: 6.1.0-34-amd64 [6.1.135-1] arch ...

Damit der MX-Firefox das installierte Sprachpaket benutzt, verwende ich einen kleinen Cheat:

- Firefox schließen

- im Terminal ins Profilverzeichnis/extensions/ wechseln

- Sprachpaket löschen

- Symlink anlegen:
ln -s /opt/firefox/distribution/extensions/langpack-de@firefox.mozilla.org.xpi ...

I notice a slight improvement, but this could also be homeopathic...

Firefox and Vivaldi perform better without demanding for AVX.

Thanks, I know how to work around this; it's just somewhat inconvenient...

Hello, hope this is the right forum for my question:

every time a new version is available, it wants to replace the installed AVX build from test with the SSE2 one on updating.

Would it be possible to give the packages different names to prevent this?

I removed "Anwendung" from shelf --> "Inhalte", and the menu bars appear on top of the windows again.