1. from your screenshot in comment #28, that's not a big deal. backport-iwlwifi-dkms can help on outdated machines but you don't need it. However, since you don't have it installed, and yet the system still have iwlwifi module available from linux-modules-extra package, `ubuntu-drivers` mistakenly thinks you have that driver installed manually, which is a minor issue for `ubuntu-drivers`. It's fine.
2. So let's see what does wapsupplicant/nm say:
* Please remove that 5G network from your saved networks. Or better, empty that.
* enable wapsupplicant debug messages as you have done,
* enable NetworkManager debug messages at boot by adding a logging section:
* Reboot. Try to connect to your 2.4G network and then attach the outout of `journalctl -b > syslog.txt` (which would contain all your syslog of current boot, so you might what to have a check if there is any credential info before uploading).
@florin,
1. from your screenshot in comment #28, that's not a big deal. backport- iwlwifi- dkms can help on outdated machines but you don't need it. However, since you don't have it installed, and yet the system still have iwlwifi module available from linux-modules-extra package, `ubuntu-drivers` mistakenly thinks you have that driver installed manually, which is a minor issue for `ubuntu-drivers`. It's fine.
2. So let's see what does wapsupplicant/nm say:
* Please remove that 5G network from your saved networks. Or better, empty that.
* enable wapsupplicant debug messages as you have done,
* enable NetworkManager debug messages at boot by adding a logging section:
[logging] ALL:info, WIFI:debug, WIFI_SCAN: debug,PLATFORM: debug,SUPPLICAN T:debug, DEVICE: debug
domains=
* Reboot. Try to connect to your 2.4G network and then attach the outout of `journalctl -b > syslog.txt` (which would contain all your syslog of current boot, so you might what to have a check if there is any credential info before uploading).