Unable to connect wireless <RESOLVED>

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Unable to connect wireless <RESOLVED>

Post by ichido »

My Dell has LM 18.3 Cinnamon, which works fine using Network Manager!
Same laptop, save hard drive, with LM 18.3 Mate, cannot connect using Wifi.
LM 18.3 Mate doesn't have Network Manager, so I cannot connect to wifi.
Out put from inxi -Fxz gets:

~ $ inxi -Fxz
System: Host: dave-Inspiron-1525 Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: MATE 1.18.0 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18.3 Sylvia
Machine: System: Dell (portable) product: Inspiron 1525
Mobo: Dell model: 0U990C Bios: Dell v: A11 date: 03/10/2008
CPU: Dual core Intel Pentium Dual T2370 (-MCP-) cache: 1024 KB
flags: (lm nx sse sse2 sse3 ssse3) bmips: 6915
clock speeds: max: 1733 MHz 1: 1333 MHz 2: 1333 MHz
Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
bus-ID: 00:02.0
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1280x800@60.00hz
GLX Renderer: Mesa DRI Intel 965GM
GLX Version: 2.1 Mesa 17.0.7 Direct Rendering: Yes
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network: Card-1: Marvell 88E8040 PCI-E Fast Ethernet Controller
driver: sky2 v: 1.30 port: de00 bus-ID: 09:00.0
IF: enp9s0 state: down mac: <filter>
Card-2: Broadcom BCM4312 802.11b/g LP-PHY
driver: b43-pci-bridge bus-ID: 0b:00.0
IF: N/A state: N/A mac: N/A
Drives: HDD Total Size: 160.0GB (5.1% used)
ID-1: /dev/sda model: WDC_WD1600BEVS size: 160.0GB
Partition: ID-1: / size: 38G used: 5.6G (16%) fs: ext4 dev: /dev/sda5
ID-2: swap-1 size: 2.20GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 51.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A fan-2: 0 fan-3: 0
Info: Processes: 162 Uptime: 3 min Memory: 331.8/3940.4MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35


If I cannot connect to the internet, then how can I update my drivers?
How can I get "Network Manager" into my LM 18.3 Mate?
Thanks in advance.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
HAWR
Level 9
Level 9
Posts: 2713
Joined: Thu Jun 06, 2019 1:15 pm

Re: Unable to connect wireless

Post by HAWR »

Hello Ichido,

I don't know the mate desktop, but I couldn't imagine, that it has no network manager, when I look at the picture of the official release notes:

https://linuxmint.com/rel_sylvia_mate.php

Has the network manager disappeared after an update? And how was it, when you had booted the live system before installation? Have you tried it in the menu with the network settings?

Please try the following commands in the terminal:

Code: Select all

sudo systemctl start NetworkManager.service

Code: Select all

sudo systemctl enable NetworkManager.service
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

I have 2 versions of Linux Mint on my Dell 1525 64 bit laptop.
LM 18.3 Cinnamon Sylvia 64Bit on sda4 & LM 18.3 Mate Sylvia on sda5. (I hate to admit it, but I also have M.S. Windows 7 on sda2, and the Wifi works fine.)
Cinnamon "Network Manager", "Network Applet@cinnamon.org", works Fine. It is what I am using to get on to this Forum.
Mate "Wcid" Network manager, cannot "See" Any Wifi Signal, so I cannot connect. When I booted the Live from a USB drive, the network would not work, so I thought that when I Installed it, the network would work, but no dice.
All 3 Systems are using the Same Hardware on the same laptop and the same Wifi Networks, so I cannot figure out WHY it works in Cinnamon, but Not in Mate.
I suspect the Wcid may be the problem.
I have tried several different distros like Ubuntu, Linux Mint, Lubuntu, and all of them had this problem.
I tried the Smart Phone Tethering in the Mate and it also works fine, except it is eats up all of my monthly High Speed Access.
I will try the Terminal Commands you suggested and I'll get back to you.
Thanks for your help.
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

I followed your Terminal Commands, but no change.
I tried to "Update", no go. "Ubuntu repositories not found."
When I boot up the Mate, after the Green LM Logo appears and the five little dots under the Logo end the color change "Process Progression"?
After that, the Screen goes Black, until I press the "Enter" key, then it shows and Loads the Desktop.
The Wicd Still doesn’t find any Wifi Networks.

Linux Mint 18.3 Cinnamon does not do that!
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

First let me say Thanks for the Phone Tethering tip!

My progress...
Your questions;

Q Has the network manager disappeared after an update?
A No

Q And how was it, when you had booted the live system before installation?
A Same as before.

Q Have you tried it in the menu with the network settings?
A yes, no change.

The two Terminal Commands do Nothing.
"Please try the following commands in the terminal:

Code: Select all

sudo systemctl start NetworkManager.service

Code: Select all

sudo systemctl enable NetworkManager.service"

My Cinnamon uses "Network Manager" and it works great, where as Mate uses Wicd, which does not work.
I used the Phone Tethering to Update/Change Drivers to the Recommended Broadcom, rebooted, no change/No Connection(Cannot Find Wireless Network).

All the other Ubuntu. Linux Mint do Not work with the Wicd. Is there a way to replace Wicd with "Network Manager"?

Do you know of a Linux Mint Distro which uses "Network Manager"?
Thanks again for your help.
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
HAWR
Level 9
Level 9
Posts: 2713
Joined: Thu Jun 06, 2019 1:15 pm

Re: Unable to connect wireless

Post by HAWR »

Hello ichido,

I didn't know, that WICD is the default network manager in LM Mate, so my commands couldn't work in your case. Often WICD is the solution, if there are problems with NetworkManager. Maybe here it's the other way around. You could try to use the NetworkManager instead of WICD to see, if it works. If it doesn't help, we can revert it.

Open up a Terminal and execute the following commands:

Install NetworkManager:

Code: Select all

sudo apt-get install network-manager-gnome network-manager
Then remove WICD:

Code: Select all

sudo apt-get remove wicd wicd-gtk
Restart your system.

Confirm everything is working, then remove WICD config files:

Code: Select all

sudo dpkg --purge wicd wicd-gtk
sleeper12
Level 21
Level 21
Posts: 14604
Joined: Thu May 25, 2017 3:22 pm

Re: Unable to connect wireless

Post by sleeper12 »

I don't know about 18.3, but my Mint 18 Mate has network manager as default, not wicd.
Last edited by sleeper12 on Tue Jan 28, 2020 3:07 pm, edited 1 time in total.
JeremyB
Level 21
Level 21
Posts: 13880
Joined: Fri Feb 21, 2014 8:17 am

Re: Unable to connect wireless

Post by JeremyB »

With an internet connection do

Code: Select all

sudo apt update && sudo apt install firmware-b43-installer
Reboot
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

With an internet connection do
Code: Select all
sudo ap update && sudo apt install firmware-b43-installer

***
Inspiron-1525 ~ $ sudo ap update && sudo apt install firmware-b43-installer
[sudo] password for dave:
sudo: ap: command not found
***
?

Now I will try "Install Network Manager" from HAWR.
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
sleeper12
Level 21
Level 21
Posts: 14604
Joined: Thu May 25, 2017 3:22 pm

Re: Unable to connect wireless

Post by sleeper12 »

Typo, try:

Code: Select all

 sudo apt update && sudo apt install firmware-b43-installer 
Reboot
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

Now I get the following…

Can not install ‘network-manager-gnome:i386’ (E:Unable to correct problems, you have held broken packages.)
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
sleeper12
Level 21
Level 21
Posts: 14604
Joined: Thu May 25, 2017 3:22 pm

Re: Unable to connect wireless

Post by sleeper12 »

ichido wrote: Wed Jan 29, 2020 12:24 pm Now I get the following…

Can not install ‘network-manager-gnome:i386’ (E:Unable to correct problems, you have held broken packages.)
Do:

Code: Select all

 sudo dpkg --configure -a 

Code: Select all

 sudo apt-get install -f 
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

Results:

dave@dave-Inspiron-1525 ~ $ sudo dpkg --configure -a
[sudo] password for dave:
dave@dave-Inspiron-1525 ~ $ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
python-wicd wicd-daemon
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded.
dave@dave-Inspiron-1525 ~ $ sudo apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
python-wicd wicd-daemon
0 upgraded, 0 newly installed, 2 to remove and 26 not upgraded.
After this operation, 1,155 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 215707 files and directories currently installed.)
Removing wicd-daemon (1.7.4+tb2-1) ...
Removing python-wicd (1.7.4+tb2-1) ...
Processing triggers for man-db (2.7.5-1) ...
dave@dave-Inspiron-1525 ~ $ sudo apt-get install network-manager-gnome network-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
network-manager is already the newest version (1.2.6-0ubuntu0.16.04.3).
network-manager-gnome is already the newest version (1.2.6-0ubuntu0.16.04.4).
0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded.
dave@dave-Inspiron-1525 ~ $ sudo apt update && sudo apt install firmware-b43-installer
Ign:1 http://packages.linuxmint.com sylvia InRelease
Get:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Hit:3 http://packages.linuxmint.com sylvia Release
Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:5 http://archive.canonical.com/ubuntu xenial InRelease
Get:7 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:8 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [818 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:10 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [637 kB]
Get:11 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [479 kB]
Get:12 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [413 kB]
Fetched 2,672 kB in 3s (837 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
26 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
b43-fwcutter
The following NEW packages will be installed:
b43-fwcutter firmware-b43-installer
0 upgraded, 2 newly installed, 0 to remove and 26 not upgraded.
Need to get 27.4 kB of archives.
After this operation, 158 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 b43-fwcutter amd64 1:019-2 [23.3 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 firmware-b43-installer all 1:019-2 [4,120 B]
Fetched 27.4 kB in 1s (21.1 kB/s)
Preconfiguring packages ...
Selecting previously unselected package b43-fwcutter.
(Reading database ... 215631 files and directories currently installed.)
Preparing to unpack .../b43-fwcutter_1%3a019-2_amd64.deb ...
Unpacking b43-fwcutter (1:019-2) ...
Selecting previously unselected package firmware-b43-installer.
Preparing to unpack .../firmware-b43-installer_1%3a019-2_all.deb ...
Unpacking firmware-b43-installer (1:019-2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up b43-fwcutter (1:019-2) ...
Setting up firmware-b43-installer (1:019-2) ...
No chroot environment found. Starting normal installation
--2020-01-29 14:26:52-- http://www.lwfinger.com/b43-firmware/br ... 38.tar.bz2
Resolving www.lwfinger.com (www.lwfinger.com)... 173.254.30.178
Connecting to www.lwfinger.com (www.lwfinger.com)|173.254.30.178|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13514651 (13M) [application/x-tar]
Saving to: ‘broadcom-wl-5.100.138.tar.bz2’

broadcom-wl-5.100.138.tar.bz2 100%[===============================================>] 12.89M 1.74MB/s in 8.6s

2020-01-29 14:27:01 (1.50 MB/s) - ‘broadcom-wl-5.100.138.tar.bz2’ saved [13514651/13514651]

Deleting old extracted firmware...
broadcom-wl-5.100.138/
broadcom-wl-5.100.138/linux/
broadcom-wl-5.100.138/linux/wl_apsta.o
broadcom-wl-5.100.138/linux/wl_ap.o
broadcom-wl-5.100.138/linux/wl_sta.o
broadcom-wl-5.100.138/README
broadcom-wl-5.100.138/config/
broadcom-wl-5.100.138/config/wlconfig_lx_shared
broadcom-wl-5.100.138/config/wl.mk
broadcom-wl-5.100.138/config/wl_default
broadcom-wl-5.100.138/config/wl_hnd
broadcom-wl-5.100.138/config/wlconfig_nomimo
This file is recognised as:
filename : wl_apsta.o
version : 666.2
MD5 : e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
Extracting b43/n0bsinitvals25.fw
Extracting b43/n0bsinitvals17.fw
Extracting b43/ucode17_mimo.fw
Extracting b43/ucode16_lp.fw
Extracting b43/sslpn1initvals27.fw
Extracting b43/lp2bsinitvals19.fw
Extracting b43/sslpn3bsinitvals21.fw
Extracting b43/ucode16_sslpn.fw
ucode time: 01:15:07
Extracting b43/ucode25_lcn.fw
Extracting b43/ucode21_sslpn.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/ucode20_sslpn.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/lp1initvals20.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp2initvals19.fw
Extracting b43/n2bsinitvals19.fw
Extracting b43/sslpn4bsinitvals22.fw
Extracting b43/ucode16_sslpn_nobt.fw
ucode date: 2011-02-23
Extracting b43/n1bsinitvals20.fw
Extracting b43/n1initvals20.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/ucode22_sslpn.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/ht0initvals26.fw
Extracting b43/ucode33_lcn40.fw
Extracting b43/sslpn1bsinitvals20.fw
Extracting b43/lcn400bsinitvals33.fw
Extracting b43/ucode14.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/lp1bsinitvals22.fw
Extracting b43/n16initvals30.fw
Extracting b43/lp0bsinitvals16.fw
Extracting b43/lcn1bsinitvals25.fw
Extracting b43/lcn400initvals33.fw
Extracting b43/n0bsinitvals24.fw
Extracting b43/lcn2bsinitvals26.fw
Extracting b43/lcn1initvals26.fw
Extracting b43/n0bsinitvals22.fw
Extracting b43/n18initvals32.fw
Extracting b43/lcn2initvals26.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/lcn2initvals24.fw
Extracting b43/lcn0initvals26.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/ucode21_sslpn_nobt.fw
ucode time: 01:15:07
Extracting b43/ucode26_mimo.fw
Extracting b43/n2initvals19.fw
Extracting b43/sslpn3initvals21.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/sslpn4initvals22.fw
Extracting b43/pcm5.fw
Extracting b43/ucode22_mimo.fw
Extracting b43/ucode9.fw
Extracting b43/lcn2initvals25.fw
Extracting b43/lp1initvals22.fw
Extracting b43/sslpn1bsinitvals27.fw
Extracting b43/lcn0initvals24.fw
Extracting b43/ucode32_mimo.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/n18bsinitvals32.fw
Extracting b43/n0initvals24.fw
Extracting b43/n0initvals25.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/ucode24_lcn.fw
Extracting b43/n0initvals17.fw
Extracting b43/n0bsinitvals16.fw
Extracting b43/lp0initvals15.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/ucode20_sslpn_nobt.fw
Extracting b43/lcn1initvals24.fw
Extracting b43/sslpn0initvals16.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/lp1bsinitvals20.fw
Extracting b43/sslpn2initvals19.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/lcn1bsinitvals24.fw
Extracting b43/ucode5.fw
Extracting b43/lcn2bsinitvals24.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/n0initvals16.fw
Extracting b43/ucode19_sslpn_nobt.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/ucode11.fw
Extracting b43/lp0initvals16.fw
Extracting b43/ucode16_mimo.fw
Extracting b43/lcn0bsinitvals26.fw
Extracting b43/ht0initvals29.fw
Extracting b43/lcn2bsinitvals25.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/ucode29_mimo.fw
Extracting b43/lcn0bsinitvals24.fw
Extracting b43/ucode19_sslpn.fw
Extracting b43/lcn1initvals25.fw
Extracting b43/ucode30_mimo.fw
Extracting b43/n16bsinitvals30.fw
Extracting b43/ucode25_mimo.fw
Extracting b43/ucode24_mimo.fw
Extracting b43/ucode27_sslpn.fw
Extracting b43/lp0initvals13.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/ht0bsinitvals26.fw
Extracting b43/ucode13.fw
Extracting b43/sslpn2bsinitvals19.fw
Extracting b43/ucode15.fw
Extracting b43/lp0bsinitvals15.fw
Extracting b43/n0initvals11.fw
Extracting b43/lcn0initvals25.fw
Extracting b43/sslpn0bsinitvals16.fw
Extracting b43/sslpn1initvals20.fw
Extracting b43/lcn1bsinitvals26.fw
Extracting b43/n0initvals22.fw
Extracting b43/ht0bsinitvals29.fw
dave@dave-Inspiron-1525 ~ $

Still Not Able to See or Connect to Wireless Network.
I am trying everything I know, But still no Connection.
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
sleeper12
Level 21
Level 21
Posts: 14604
Joined: Thu May 25, 2017 3:22 pm

Re: Unable to connect wireless

Post by sleeper12 »

What does this show:

Code: Select all

 sudo lshw -C network | grep driver 
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

sudo lshw -C network | grep driver

LM 18-2 MATE =
dave@dave-Inspiron-1525 ~ $ sudo lshw -C network | grep driver
[sudo] password for dave:
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair
configuration: driver=b43-pci-bridge latency=0
configuration: broadcast=yes driver=b43 driverversion=4.10.0-38-generic firmware=666.2 link=no multicast=yes wireless=IEEE 802.11
dave@dave-Inspiron-1525 ~ $


LM 18-2 CINNAMON =
dave@dave-Inspiron-1525 ~ $ sudo lshw -C network | grep driver
[sudo] password for dave:
configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 latency=0 link=no multicast=yes port=twisted pair
configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) latency=0 multicast=yes wireless=IEEE 802.11
dave@dave-Inspiron-1525 ~ $

Now I see Different Drivers!?
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
sleeper12
Level 21
Level 21
Posts: 14604
Joined: Thu May 25, 2017 3:22 pm

Re: Unable to connect wireless

Post by sleeper12 »

Try:

Code: Select all

 sudo modprobe b43 
Reboot if needed.
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

Is:
driver=wl0 driverversion=6.30.223.271 (r587334) latency=0 multicast=yes wireless=IEEE 802.11

Very Different from:
driver=b43 driverversion=4.10.0-38-generic firmware=666.2 link=no multicast=yes wireless=IEEE 802.11

wlo vs. b43?
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
HAWR
Level 9
Level 9
Posts: 2713
Joined: Thu Jun 06, 2019 1:15 pm

Re: Unable to connect wireless

Post by HAWR »

Hello ichido,

yes, you have found the difference with the drivers in Cinnamon and Mate. In Cinnamon you use the bcmwl driver (probably installed via the driver manager) and in Mate you now use the b43 driver. Both drivers are listed to support your wifi card. So it could be a try to enable the bcmwl driver in Mate instead of b43:

Code: Select all

sudo apt-get purge firmware-b43-installer
Then go to the driver manager in the menu and install the offered bcmwl driver. After the installation you have to reboot.
ichido
Level 4
Level 4
Posts: 217
Joined: Wed Sep 14, 2011 6:25 pm
Location: U.S.A., Ohio
Contact:

Re: Unable to connect wireless

Post by ichido »

Thanks HAWR, I will give it a shot!

Eureka! That worked!
Thanks a million!
We can easily forgive a child who is afraid of the dark; the real tragedy of life is when men are afraid of the light. –Plato
HAWR
Level 9
Level 9
Posts: 2713
Joined: Thu Jun 06, 2019 1:15 pm

Re: Unable to connect wireless <RESOLVED>

Post by HAWR »

Hello ichido,

I'm glad it's working for you. I was about to suggest that you use only cinnamon. :D
Locked

Return to “Networking”