MX Linux Realtek Wi-fi Issues

Other Distributions
21

The problem is identical. A scan shows a number of wifi channels, including my router, but all show signal strength as 0.
Is there a command to see if that file is actually read?
Since MX is not my main system, I only get around to it one or two times a week. My next effort will be to change the kernel to the one I mentioned earlier, linux-image-6.9.10-amd64-unsigned Version: 6.9.10-1~mx23+1

2 Likes
22

I hope you rebooted after editing that file?

1 Like
23

You can look at the access time of the file

stat or ls -lu

2 Likes
24

I rebooted into the same os. I did not boot first into Debian, from whose grub I access MX. AFAIK, that’s only necessary for a new kernel

1 Like
25

Correct. The purpose of reboot is to force MX to reread the config files.
Nothing to do with Debian.

1 Like
26

The problem has been solved in a way I could have done from the beginning and saved myself valuable hours wasted trying to configure myself out of the rut. I upgraded the kernel from 6.1.0-40 to 6.9.10-amd and it started up immediately.
My warning to others: Claude seems to have a bias towards complicated coding fixes. A human, as Neville did, would have said “the kernel is too old for the new hardware.”

7 Likes
27

Most times KDE gets the Wi-Fi network right. At times you have to manually use the gear icon in Network —> Connections to add a connection..

2 Likes
28

The app TLP has, in recent years been expanded to encompass all PCs. Adding tlp, tlp-rdw and tlpui gives a GUI interface via a Radio subsection to turn off power saving related to Wi-Fi and also Bluetooth. Sometimes a GUi option has less user anxiety associated with it.

2 Likes
29

Sorry to hear of your less than stellar first experience. MX Linux 25 has a 6.12.x kernel. MX has a AHS edittion that many times has newer kernel & firmware than the Debian stable based MX Linux Xfce. By default the KDE edition of MX is also ‘AHS enabled’ BTW. Unfortunately in your case it wasn’t new enough. MX Dev pull new firmware updates from Debian and even Ubuntu several times a year.
FWIW a Google alert brought me here.

1 Like
30

THe reason I started using MX was that I wanted to try out KDE and chose Neon. At the time my hardware was VERY old and when Neon updated to KDE 6.0 with Wayland by default, it was impossibly unstable. @nevj recommended MX KDE because it works great with old HW and I wasn’t disappointed. THen, I moved, packed everything in a truck and drove to the new home. Within one month, the old computer would not start. Thank God I bought a mini pc (the new hardware), but then what made MX such a good choice resulted in these problems.
Sometimes, I just want to quit all technology and spend my remaining years gardening, hiking and cooking.

2 Likes
31

I just turned 72 and really believe when they find me gone it will be forehead on keyboard!

2 Likes
32

Excellent news that the kernel update fixed the issue. For future reference, if you encounter any random Wi-Fi drops—especially on a laptop—that configuration file remains a useful remedy.

On a separate point, AI sucks a lot of times.

2 Likes
33

I go looking for interesting technical challenges. They can be a great way to learn.
But not like your MX problem, that is just a nuisance.
A bit of redundancy helps in coping with these sorts of dropouts… if one system fails, you need something to fall back on.

2 Likes