Greetings, I have a problem with the Wi-Fi network. It keeps loading but doesn't show the connection. I don't know what it is.

ysmaely1

New Member
Joined
Jul 12, 2025
Messages
9
Reaction score
0
Credits
60
I recently upgraded from Ubuntu 20.04 LTS to Ubuntu 24.04 LTS, and after that, my Wi-Fi stopped working. I'd appreciate your response; I've tried several methods, but none have worked. Has anyone else been through this?

Everything is enabled, but it seems the driver is disabled. However, I don't really know what to do there. In Windows, it recognizes the Wi-Fi driver, and I can see each of the networks. However, in Ubuntu, I still have the same problem. I can't see any of the networks, so I can't connect there.

1752289838504.png
 
Last edited:


We will need a bit more info on your card to get an answer. Please go to a terminal and type this command and post the output here for starters.
Code:
inxi -Nn
you may have to install inxi first
Code:
sudo apt install inxi
 
1752319132739.png
It keeps loading but doesn't recognize the networks, in Windows it does recognize them, I have two systems installed on my laptop.
On the other hand, I don't know why I get the firmware error.
1752319206470.png
 
Well your B43 drivers do need to be re-installed after a major update [in most cases] the B43 drivers should be in the distribution repositories [assuming yo installed non-free driver pack if its classed as an extra]
 
first looks like you have two broadcom drivers install or your trying to install two. What I needed was the actual broadcom card info Did you execute the inxi command? most broadcom card will work with broadcom sta or wl but it depends on which card you have we need to know that first.
 
Well your B43 drivers do need to be re-installed after a major update [in most cases] the B43 drivers should be in the distribution repositories [assuming yo installed non-free driver pack if its classed as an extra]
I already tried downloading firmware-b43-installer, but I still don't get anything on the wifi network.
 
first looks like you have two broadcom drivers install or your trying to install two. What I needed was the actual broadcom card info Did you execute the inxi command? most broadcom card will work with broadcom sta or wl but it depends on which card you have we need to know that first.
I think one is ethernet and the other is for wifi
 
Looks to me like your running Linux in a VM/VB, is this correct?
go into the VB/M settings and make sure the Broadcom dongle is enabled, [big gamble here i am assuming that you are using a usb dongle as a direct connection for the VM] if not you should be using the internal Bridge to the host system
 
1752324084629.png
1752324099570.png


I don't understand why it appears blocked in one section but unlocked in the other. I've already tried to unlock it but the changes aren't made.
 
can you install inxi and paste back the results of inxi -Nn
 
that intel card should work out of the box as the driver is in the kernel. So it it's not working it may be that you have a wifi off/on switch turned off. you can tell by entering this command
Code:
rfkill list
The switch depending upon the machine may be a combination of F keys or an actual switch.
 
Last edited:
Device 14:3 is an Intel Wifi chipset. Not broadcom. You have a RealTek Ethernet chip. Not wifi.

Agreed-
Code:
Ethernet controller: Realtek Semiconductor Co, LTD RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev15)
And the WiFi:
Network Intel Corporation Alder Lake PCH CNVL WiFi (rev 01)

The network is disabled in post #12.
I'm thinking that that broadcom driver should be removed unless OP is using a wifi dongle in order for the VM to work.

I think finding out 'what driver' is loading will help.
Like @kc1di said that driver for Intel is in the kernel. And if for some reason it's not it can be easily downloaded.
I know the drivers on Intel's website work. I downloaded the one I needed for my Intel wifi for Devuan to run.

 
I'm thinking that that broadcom driver should be removed unless OP is using a wifi dongle in order for the VM to work.
@Alexzee :-

Hm. The OP is not being very forthcoming with info.....until you "push" him/her. They're convinced this is a bare-metal install on the primary drive.....but why are all those virtual drivers showing, if that's the case?

Curiouser & curiouser...

Anyway, I don't see the Broadcom driver is hurting anything, and it's probably fine right where it is. If there's no Broadcom chip in the system, then nothing will attempt to use it.....and it may as well remain. If a wifi dongle ever gets used - that DOES have a Broadcom chip - it'll be there ready & waiting.

It doesn't occupy a ton of space, does it? Somewhere around 6-700 kb, IIRC......from past experience.

Is anybody really that concerned about saving every tiny last little bit of drive space these days?

(shrug...)


Mike. ;)
 
@Alexzee :-

Hm. The OP is not being very forthcoming with info.....until you "push" him/her. They're convinced this is a bare-metal install on the primary drive.....but why are all those virtual drivers showing, if that's the case?

Curiouser & curiouser...

Anyway, I don't see the Broadcom driver is hurting anything, and it's probably fine right where it is. If there's no Broadcom chip in the system, then nothing will attempt to use it.....and it may as well remain. If a wifi dongle ever gets used - that DOES have a Broadcom chip - it'll be there ready & waiting.

It doesn't occupy a ton of space, does it? Somewhere around 6-700 kb, IIRC......from past experience.

Is anybody really that concerned about saving every tiny last little bit of drive space these days?

(shrug...)


Mike. ;)
As far as the forthcoming information I see what you do brother.:)

Looking through the output form lspci, I don't see why a Broadcom driver would be needed.
That is if this Ubuntu installation is in fact installed to the HDD.

I'm curious what the output of these 2 commands bring forth.

Code:
cat /etc/os-release

sudo fdisk -l

Anytime spent, IMO, on being over concerned on the last bit of space is time wasted and could be 'better spent' on fixing the real issue at hand.
 


Follow Linux.org

Members online


Top