Good morning all,

I have an older Dell E6500 with 3GB RAM, 120 GB SSD, and a heavily modified (German) MX Linux which is based on Debian, OS. During the most recent installation I had to use Boot Repair in order to correct some boot issues the system was having in order to properly recognize grub. Before that, WiFi worked without a problem. I'm wondering if the Boot Repair .iso might have had something to do with the WiFi since there's an "enable WiFi" as part of the boot repair process ... ???

I took some pictures which I labeled in order to better explain the problem. Please take a look at those. They're in 1 to 5 order. Thank you.

Attached Thumbnails

         

There's another thread here ... https://www.linuxquestions.org/quest...es-4175662747/ ... which had pretty much the identical problem, but on a Lenovo R500 machine. The problems were never resolved in that thread either. From the suggestions on that thread I've already tried:

Advice #4 from that Thread:
sudo rfkill list; sudo rfkill unblock all
This provided me with 4 results, each including ... softblock no & hardblock no

Advice #5 from that Thread:
ping -c 3 startpage.com
The result was an unknown name or unknown service message.

ping -c 3 8.8.8.8
Result was 3 packets transmitted, 3 packets received, 0% packet loss, time 2003ms

Also tried Advice #7 from that Thread:
ls -l /etc/resolv.conf
cat /etc/resolv.conf
The result of those was ... No Errors - Name Server IP created by Network Manager

You seem to have a number of wifi sources - at least 2. Wifi connection programs commonly presume that they are the only kid on the block, and overwrite the vital files to suit themselves.

Boot with one wifi source only. Then you have a chance of fixing that.

Also tried from that above thread, posts #12 through #14
systemd-resolve --status

Here's the output of that:


@business_kid

Thank you. I don't believe that's the solution. My Linux and Windows machines always find the nearby available WiFi connections within the immediate area, that's perfectly normal. It's been that way for several years now and I don't believe that disabling all of the other recognized connections will make a difference ... since the system only attempts to connect to the one that had previously been in use anyway. None of the others are working on this system. They're just being found nearby. Some of them don't even belong to us. I'll give it a try though and will report back.

Nope, disabling the other connections made no difference at all. I even tried deleting them. After a reboot the connections were all found again, but not being used. In order to use a connection I had to add the password and then it appeared to work again. But as before, without actually working. Strictly visually everything appears to be fine & working.

I could not follow the Bluetooth deletion/installation suggestion of the above thread, because without a working signal I wouldn't be able to use synaptic either.

I did go ahead and disable Bluetooth though ... which also made no difference before and after a reboot of the machine.

That's it for me today, wife doesn't like for me to spend our Sundays working on a system. Will check back briefly in a few hours though. Any additional input/suggestions would be appreciated. Thanks.

open /etc/resolvconf/resolv.conf.d/head
with
and add these two lines
exit and save
Then run

@colorpurple21859
Just wanted to let you know that I haven't forgotten the thread. Been slammed with computer work because of the upcoming holidays, but still plan on pursuing this until it's (hopefully) resolved.

When you get over S.O.S. [Saturnalia Overload Syndrome] try the 'route' command for your network status, and the bluetoothctl command for you Bluetooth issues. Both are console type jobs, and just may need root.

Alright, I finally gave up.
After creating a new MX image from a couple of months ago and re-installing it on the system, all was well again. Wifi working as it should. Thank you, everyone who tried to help with this.