My wifi card, Herald BE Wifi 7 Max, is completely hidden in my system. I tried the lspci grep command and it didn't even show my card, it only showed my ethernet adapter. Please help.
Announcement
Collapse
No announcement yet.
Wifi card not recognized, please help..
Collapse
X
-
Welcome to KFN.
How did you install Kubuntu? What version? Without Wifi, you would have had to have a wired Ethernet connection. Is that the case?Windows no longer obstruct my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
- Top
- Bottom
-
Which specific command?Originally posted by moldypastaman View PostI tried the lspci grep command and it didn't even show my card
Try using lspci without using grep, it isn't necessary for basic info, and your exact command for the grep side might just be incorrect or doesn't filter for the correct wording used.
That device is a Qualcomm NCM865, and it should be detected, unless it isn't seated correctly or otherwise has been disabled in the BIOS or something. Even if it did not work, it would show up in lspci.
Qualcomm wifi is often a big pita, but I don't see any strong info on it related to *buntu, but enough from other distros in the past couple of years that it does seem to work, with possible issues
Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/Kubuntu LTS
HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE Linux
- Top
- Bottom
Comment
-
And for me, it is the exact opposite; I see my wifi card but not the Ethernet. It depends on how the device labels itself, and maybe this card does not use the word "network" for this at all.Originally posted by moldypastaman View PostI used the lspci -nn | grep -i network command, which only showed a Broadcom Ethernet controller.
If you are worried about the possibly long output from running lspci -nn without any text filters, try subbing different text strings in place of "network". Say "wi-fi" or just "wi"
But even running it without the grep part, it should be very obvious which line refers to your Wi-Fi card.
Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/Kubuntu LTS
HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE Linux
- Top
- Bottom
Comment
-
Always remember too, Linux is case sensitive. network isn't the same as Network. When using grep it is 'better' IMO, to be as unspecific as possible while still being relevant to what you are looking for. I would use lspci -nn | grep work (which I just did on my laptop) and it produced a single match:
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43413 802.11bgn Wireless Network Adapter [14e4:4727] (rev 02)Windows no longer obstruct my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
- Top
- Bottom
Comment
-
grep -i makes is case-insesnitive. On my small PC, "net" shopws both, network shows one.
Code:arm@arm-mini:~$ lspci -nn | grep -i network 01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] [8086:2725] (rev 1a)
Code:arm@arm-mini:~$ lspci -nn | grep -i net 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3] 01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] [8086:2725] (rev 1a)
Code:arm@arm-mini:~$ lspci -nn | grep -i wi 01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] [8086:2725] (rev 1a)
Code:arm@arm-mini:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:591f] (rev 05) 00:02.0 VGA compatible controller [0300]: Intel Corporation Kaby Lake-S GT2 [HD Graphics 630] [8086:5912] (rev 04) 00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af] 00:14.2 Signal processing controller [1180]: Intel Corporation 200 Series PCH Thermal Subsystem [8086:a2b1] 00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA controller [AHCI mode] [8086:a282] 00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #7 [8086:a296] (rev f0) 00:1d.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #9 [8086:a298] (rev f0) 00:1f.0 ISA bridge [0601]: Intel Corporation 200 Series PCH LPC Controller (Q270) [8086:a2c6] 00:1f.2 Memory controller [0580]: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller [8086:a2a1] 00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio [8086:a2f0] 00:1f.4 SMBus [0c05]: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller [8086:a2a3] 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3] 01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] [8086:2725] (rev 1a) 02:00.0 Non-Volatile memory controller [0108]: Silicon Motion, Inc. SM2263EN/SM2263XT (DRAM-less) NVMe SSD Controllers [126f:2263] (rev 03)
Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/Kubuntu LTS
HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE Linux
- Top
- Bottom
Comment
-
that happens ...Originally posted by moldypastaman View PostI have fixed the problem. I tried all listed commands and they showed nothing, so I determined it was a hardware issue and reset my network controller. Thank you for the help.
sometimes the simplest little things is the cause of headaches
ʟɨռʊӼ ʄօʀ ʟɨʄɛ
- Top
- Bottom
Comment
Users Viewing This Topic
Collapse
There are 0 users viewing this topic.







Comment