Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
BCM4352 Broadcom WiFi not working
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 9:50 am    Post subject: Reply with quote

axl wrote:
Quote:

[ 5.126358] wl: loading out-of-tree module taints kernel.
[ 5.126360] wl: module license 'MIXED/Proprietary' taints kernel.
[ 5.126361] Disabling lock debugging due to kernel taint
[ 5.127636] wl: module verification failed: signature and/or required key missing - tainting kernel


I think this might be the relevant bit. Although I have no idea what to do next. Seems to me to be a conflict between a less then ideal driver in the kernel, and a better driver outside of kernel which compete for the same resources. Sort of like nouveau & nvidia.

I don't exactly know where this wl module came from, but based on a cursory google reading, seems you have to disable the kernel modules, if you plan to use the broadcom proprietary drivers. so blacklist or disable brcmsmac, bcma and b43.

Now, I wouldn't suggest to actually do that if you have no backup, because I think your removable usb wifi thingy might need 1 or 2 of those. I seen your computer has an ethernet port, so maybe use that instead of your wifi adaptor, and then you can continue to disable those and go with wl alone. Not sure how to proceed at this point.


Ok I tried to add this to /etc/modprobe.d/blacklist.conf:
Code:

blacklist ssb
blacklist brcmsmac
blacklist bcma
blacklist b43

Now ifconfig -a shows me another device:
Code:

enp4s0f1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 88:d7:f6:1f:2a:04  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 300  bytes 22284 (21.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 300  bytes 22284 (21.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s20f0u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.104  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::1262:ebff:fe94:af5c  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::761:9aea:463:bd92  prefixlen 64  scopeid 0x20<link>
        ether 10:62:eb:94:af:5c  txqueuelen 1000  (Ethernet)
        RX packets 2649  bytes 3392347 (3.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1075  bytes 256593 (250.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.219.99  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::9dc9:31e4:4719:6b12  prefixlen 64  scopeid 0x20<link>
        ether 28:c2:dd:e6:06:dd  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 18


I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Last edited by spike32 on Sun Apr 05, 2020 9:52 am; edited 1 time in total
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 9:51 am    Post subject: Reply with quote

NeddySeagoon wrote:
spike32,

Lets rewind a little.

You can try wl or broadcom-sta but only one may be loaded at a time.
If you manage to load both, look in
Code:
lsmod
they will fight over the hardware and neither can win.

This is the lsmod output:
Code:

Module                  Size  Used by
ccm                    20480  3
8021q                  36864  0
garp                   16384  1 8021q
mrp                    20480  1 8021q
stp                    16384  1 garp
llc                    16384  2 stp,garp
vfat                   20480  1
btusb                  57344  0
uvcvideo              114688  0
btrtl                  24576  1 btusb
rtl8xxxu              139264  0
videobuf2_vmalloc      20480  1 uvcvideo
btbcm                  16384  1 btusb
videobuf2_memops       20480  1 videobuf2_vmalloc
btintel                28672  1 btusb
videobuf2_v4l2         28672  1 uvcvideo
videobuf2_common       57344  2 videobuf2_v4l2,uvcvideo
bluetooth             626688  5 btrtl,btintel,btbcm,btusb
videodev              253952  3 videobuf2_v4l2,uvcvideo,videobuf2_common
mac80211              970752  1 rtl8xxxu
mc                     61440  4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
ecdh_generic           16384  1 bluetooth
ecc                    32768  1 ecdh_generic
libarc4                16384  1 mac80211
x86_pkg_temp_thermal    20480  0
intel_powerclamp       20480  0
snd_hda_codec_hdmi     73728  1
coretemp               20480  0
kvm_intel             241664  0
kvm                   786432  1 kvm_intel
irqbypass              16384  1 kvm
rtsx_pci_sdmmc         32768  0
rtsx_pci_ms            24576  0
iTCO_wdt               16384  0
crct10dif_pclmul       16384  1
memstick               20480  1 rtsx_pci_ms
mmc_core              180224  1 rtsx_pci_sdmmc
iTCO_vendor_support    16384  1 iTCO_wdt
crc32_pclmul           16384  0
mei_hdcp               24576  0
crc32c_intel           24576  0
i2c_designware_platform    16384  0
snd_hda_codec_realtek   126976  1
i2c_designware_core    28672  1 i2c_designware_platform
asus_nb_wmi            28672  0
intel_rapl_msr         20480  0
snd_hda_codec_generic    94208  1 snd_hda_codec_realtek
asus_wmi               36864  1 asus_nb_wmi
sparse_keymap          16384  1 asus_wmi
wmi_bmof               16384  0
mxm_wmi                16384  0
ghash_clmulni_intel    16384  0
ledtrig_audio          16384  2 snd_hda_codec_generic,snd_hda_codec_realtek
aesni_intel           372736  2
crypto_simd            16384  1 aesni_intel
snd_hda_intel          49152  3
snd_intel_nhlt         20480  1 snd_hda_intel
cryptd                 24576  2 crypto_simd,ghash_clmulni_intel
glue_helper            16384  1 aesni_intel
intel_cstate           20480  0
snd_hda_codec         155648  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core           98304  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
wl                   6418432  0
intel_uncore          147456  0
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               118784  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
efi_pstore             16384  0
i915                 2375680  42
intel_rapl_perf        20480  0
r8169                  98304  0
joydev                 28672  0
snd_timer              40960  1 snd_pcm
i2c_algo_bit           16384  1 i915
realtek                24576  1
pcspkr                 16384  0
cfg80211              835584  2 wl,mac80211
snd                    98304  14 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
drm_kms_helper        217088  1 i915
serio_raw              20480  0
efivars                20480  1 efi_pstore
soundcore              16384  1 snd
i2c_i801               32768  0
libphy                 98304  2 r8169,realtek
rtsx_pci               81920  2 rtsx_pci_sdmmc,rtsx_pci_ms
rfkill                 28672  6 asus_wmi,bluetooth,cfg80211
sr_mod                 28672  0
drm                   552960  11 drm_kms_helper,i915
cdrom                  73728  1 sr_mod
intel_lpss_pci         20480  0
processor_thermal_device    20480  0
mei_me                 45056  1
intel_lpss             16384  1 intel_lpss_pci
xhci_pci               20480  0
idma64                 20480  0
mei                   118784  3 mei_hdcp,mei_me
intel_rapl_common      28672  2 intel_rapl_msr,processor_thermal_device
xhci_hcd              299008  1 xhci_pci
i2c_core               94208  8 i2c_designware_platform,videodev,i2c_designware_core,drm_kms_helper,i2c_algo_bit,i2c_i801,i915,drm
mfd_core               16384  2 rtsx_pci,intel_lpss
intel_pch_thermal      16384  0
intel_soc_dts_iosf     20480  1 processor_thermal_device
int3403_thermal        16384  0
int340x_thermal_zone    16384  2 int3403_thermal,processor_thermal_device
video                  53248  2 asus_wmi,i915
wmi                    36864  3 asus_wmi,wmi_bmof,mxm_wmi
backlight              20480  3 video,asus_wmi,i915
int3400_thermal        20480  0
acpi_thermal_rel       16384  1 int3400_thermal
asus_wireless          20480  0
acpi_pad              184320  0
mac_hid                16384  0
efivarfs               16384  1
msdos                  20480  0
fat                    86016  2 msdos,vfat
cramfs                 57344  0
overlay               135168  0
squashfs               65536  0
loop                   40960  0
fuse                  139264  1
f2fs                  614400  0
xfs                  1654784  0
nfs                   352256  0
lockd                 122880  1 nfs
grace                  16384  1 lockd
sunrpc                466944  2 lockd,nfs
fscache               393216  1 nfs
jfs                   217088  0
reiserfs              290816  0
btrfs                1482752  0
xor                    24576  1 btrfs
raid6_pq              122880  1 btrfs
libcrc32c              16384  2 btrfs,xfs
ext4                  774144  1
mbcache                16384  1 ext4
jbd2                  131072  1 ext4
sd_mod                 57344  4
mpt3sas               299008  0
raid_class             16384  1 mpt3sas
scsi_transport_sas     45056  1 mpt3sas
megaraid               49152  0
megaraid_sas          176128  0
mptspi                 28672  0
mptscsih               45056  1 mptspi
mptbase                98304  2 mptspi,mptscsih
scsi_transport_spi     40960  1 mptspi
pdc_adma               16384  0
sata_inic162x          16384  0
sata_mv                40960  0
sata_qstor             16384  0
sata_vsc               16384  0
sata_uli               16384  0
sata_sis               16384  0
pata_sis               20480  1 sata_sis
sata_sx4               20480  0
sata_nv                32768  0
sata_via               24576  0
sata_svw               16384  0
sata_sil24             24576  0
sata_sil               16384  0
sata_promise           20480  0
ata_piix               36864  0
ahci                   40960  3
libahci                40960  1 ahci
nvme_fc                45056  0
nvme_loop              20480  0
nvmet                 102400  1 nvme_loop
nvme_rdma              40960  0
rdma_cm                73728  1 nvme_rdma
iw_cm                  57344  1 rdma_cm
ib_cm                  61440  1 rdma_cm
ib_core               360448  4 rdma_cm,nvme_rdma,iw_cm,ib_cm
configfs               53248  3 rdma_cm,nvmet
ipv6                  581632  80 rdma_cm,ib_core
crc_ccitt              16384  1 ipv6
nf_defrag_ipv6         24576  1 ipv6
nvme_fabrics           28672  3 nvme_fc,nvme_rdma,nvme_loop
nvme                   53248  0
nvme_core             106496  5 nvme,nvme_fc,nvme_rdma,nvme_loop,nvme_fabrics
Back to top
View user's profile Send private message
axl
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1027
Location: Romania

PostPosted: Sun Apr 05, 2020 10:17 am    Post subject: Reply with quote

spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 10:22 am    Post subject: Reply with quote

axl wrote:
spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?

I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.
Back to top
View user's profile Send private message
axl
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1027
Location: Romania

PostPosted: Sun Apr 05, 2020 10:26 am    Post subject: Reply with quote

spike32 wrote:
I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.


Does dmesg offer any relevant info? Perhaps syslog or journalctl based on what type of setup you have?

We are looking for pieces of logs relevant to the wl module.
Back to top
View user's profile Send private message
gddman
n00b
n00b


Joined: 11 Aug 2018
Posts: 11

PostPosted: Sun Apr 05, 2020 3:02 pm    Post subject: Reply with quote

spike32 wrote:
axl wrote:
spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?

I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.


Make sure you enable the
Code:
broadcom-sta
USE flag on wpa_supplicant. Or else you won't be able to scan correctly. Basically, this use flag makes you disable the 'fils', 'mesh', and 'mbo' USE flags as well, which are features in wpa_supplicant that are incompatible with wl/broadcom-sta and interfere with its ability to scan.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45435
Location: 56N 3W

PostPosted: Sun Apr 05, 2020 3:13 pm    Post subject: Reply with quote

spike32,

Code:
wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.219.99  netmask 255.255.0.0  broadcast 169.254.255.255


That's your on board wifi. So step 1 is complete, getting the kernel to see it.
Code:
inet 169.254.219.99
is a self assigned link local IP address. That lells that it tried to reach a dhcp server and failed.

dmesg will tell more.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 5:11 pm    Post subject: Reply with quote

gddman wrote:
spike32 wrote:
axl wrote:
spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?

I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.


Make sure you enable the
Code:
broadcom-sta
USE flag on wpa_supplicant. Or else you won't be able to scan correctly. Basically, this use flag makes you disable the 'fils', 'mesh', and 'mbo' USE flags as well, which are features in wpa_supplicant that are incompatible with wl/broadcom-sta and interfere with its ability to scan.

I'm sorry, I don't understand which USE flag I have to add
Back to top
View user's profile Send private message
gddman
n00b
n00b


Joined: 11 Aug 2018
Posts: 11

PostPosted: Sun Apr 05, 2020 5:18 pm    Post subject: Reply with quote

spike32 wrote:
gddman wrote:
spike32 wrote:
axl wrote:
spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?

I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.


Make sure you enable the
Code:
broadcom-sta
USE flag on wpa_supplicant. Or else you won't be able to scan correctly. Basically, this use flag makes you disable the 'fils', 'mesh', and 'mbo' USE flags as well, which are features in wpa_supplicant that are incompatible with wl/broadcom-sta and interfere with its ability to scan.

I'm sorry, I don't understand which USE flag I have to add


It's the 'broadcom-sta' USE flag on the 'wpa_supplicant' package. Then re-emerge wpa_supplicant. I use the broadcom-sta driver as well, and this is what I had to do in order for it to scan correctly.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 5:19 pm    Post subject: Reply with quote

This is the dmesg output https://pastebin.com/wieQqcNc
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 5:31 pm    Post subject: Reply with quote

gddman wrote:
spike32 wrote:
gddman wrote:
spike32 wrote:
axl wrote:
spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?

I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.


Make sure you enable the
Code:
broadcom-sta
USE flag on wpa_supplicant. Or else you won't be able to scan correctly. Basically, this use flag makes you disable the 'fils', 'mesh', and 'mbo' USE flags as well, which are features in wpa_supplicant that are incompatible with wl/broadcom-sta and interfere with its ability to scan.

I'm sorry, I don't understand which USE flag I have to add


It's the 'broadcom-sta' USE flag on the 'wpa_supplicant' package. Then re-emerge wpa_supplicant. I use the broadcom-sta driver as well, and this is what I had to do in order for it to scan correctly.

I tried to re-emerge wpa_supplicant but I have this error:
Code:

sudo emerge --ask net-wireless/wpa_supplicant

/usr/lib64/python3.6/site-packages/portage/package/ebuild/_config/KeywordsManager.py:70: UserWarning: /etc/portage/package.keywords is deprecated, use /etc/portage/package.accept_keywords instead
  UserWarning)

These are the packages that would be merged, in order:

Calculating dependencies /

!!! Problem resolving dependencies for net-wireless/wpa_supplicant
... done!

!!! The ebuild selected to satisfy "net-wireless/wpa_supplicant" has unmet requirements.
- net-wireless/wpa_supplicant-2.9-r2::gentoo USE="broadcom-sta dbus fils hs2-0 mbo mesh qt5 readline -ap -bindist -eap-sim -eapol-test -fasteap -libressl -macsec -p2p -privsep (-ps3) (-selinux) -smartcard -tdls -uncommon-eap-types (-wimax) -wps" ABI_X86="(64)"

  The following REQUIRED_USE flag constraints are unsatisfied:
    broadcom-sta? ( !fils !mesh !mbo )

  The above constraints are a subset of the following complete expression:
    macsec? ( !privsep ) privsep? ( !macsec ) broadcom-sta? ( !fils !mesh !mbo )


What I have done before this is:
Code:
sudo echo "net-wireless/wpa_supplicant broadcom-sta" >> /etc/portage/package.use/wpa_supplicant
Back to top
View user's profile Send private message
gddman
n00b
n00b


Joined: 11 Aug 2018
Posts: 11

PostPosted: Sun Apr 05, 2020 5:37 pm    Post subject: Reply with quote

spike32 wrote:
gddman wrote:
spike32 wrote:
gddman wrote:
spike32 wrote:
axl wrote:
spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?

I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.


Make sure you enable the
Code:
broadcom-sta
USE flag on wpa_supplicant. Or else you won't be able to scan correctly. Basically, this use flag makes you disable the 'fils', 'mesh', and 'mbo' USE flags as well, which are features in wpa_supplicant that are incompatible with wl/broadcom-sta and interfere with its ability to scan.

I'm sorry, I don't understand which USE flag I have to add


It's the 'broadcom-sta' USE flag on the 'wpa_supplicant' package. Then re-emerge wpa_supplicant. I use the broadcom-sta driver as well, and this is what I had to do in order for it to scan correctly.

I tried to re-emerge wpa_supplicant but I have this error:
Code:

sudo emerge --ask net-wireless/wpa_supplicant

/usr/lib64/python3.6/site-packages/portage/package/ebuild/_config/KeywordsManager.py:70: UserWarning: /etc/portage/package.keywords is deprecated, use /etc/portage/package.accept_keywords instead
  UserWarning)

These are the packages that would be merged, in order:

Calculating dependencies /

!!! Problem resolving dependencies for net-wireless/wpa_supplicant
... done!

!!! The ebuild selected to satisfy "net-wireless/wpa_supplicant" has unmet requirements.
- net-wireless/wpa_supplicant-2.9-r2::gentoo USE="broadcom-sta dbus fils hs2-0 mbo mesh qt5 readline -ap -bindist -eap-sim -eapol-test -fasteap -libressl -macsec -p2p -privsep (-ps3) (-selinux) -smartcard -tdls -uncommon-eap-types (-wimax) -wps" ABI_X86="(64)"

  The following REQUIRED_USE flag constraints are unsatisfied:
    broadcom-sta? ( !fils !mesh !mbo )

  The above constraints are a subset of the following complete expression:
    macsec? ( !privsep ) privsep? ( !macsec ) broadcom-sta? ( !fils !mesh !mbo )


What I have done before this is:
Code:
sudo echo "net-wireless/wpa_supplicant broadcom-sta" >> /etc/portage/package.use/wpa_supplicant


Okay, great. You're on the right track. What that's saying is that you also have to disable the fils, mesh, and mbo USE flags (as those conflict with the broadcom-sta use flag)
This should do it
Code:
sudo echo "net-wireless/wpa_supplicant broadcom-sta -fils -mesh -mbo" >> /etc/portage/package.use/wpa_supplicant
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 5:51 pm    Post subject: Reply with quote

gddman wrote:
spike32 wrote:
gddman wrote:
spike32 wrote:
gddman wrote:
spike32 wrote:
axl wrote:
spike32 wrote:
I guess wlp3s0 should be my wifi card. I tried to make it work with wpa supplicant but it doesn't work.


Cool. We're one step close.

Now... what does "it doesn't work" mean? What did you try? What were you expecting and what actually happened? Any error message? Any logs?

I tried to use the interface alongside wpa supplicant. When I try to scan through wpa_cli it says that it fails.


Make sure you enable the
Code:
broadcom-sta
USE flag on wpa_supplicant. Or else you won't be able to scan correctly. Basically, this use flag makes you disable the 'fils', 'mesh', and 'mbo' USE flags as well, which are features in wpa_supplicant that are incompatible with wl/broadcom-sta and interfere with its ability to scan.

I'm sorry, I don't understand which USE flag I have to add


It's the 'broadcom-sta' USE flag on the 'wpa_supplicant' package. Then re-emerge wpa_supplicant. I use the broadcom-sta driver as well, and this is what I had to do in order for it to scan correctly.

I tried to re-emerge wpa_supplicant but I have this error:
Code:

sudo emerge --ask net-wireless/wpa_supplicant

/usr/lib64/python3.6/site-packages/portage/package/ebuild/_config/KeywordsManager.py:70: UserWarning: /etc/portage/package.keywords is deprecated, use /etc/portage/package.accept_keywords instead
  UserWarning)

These are the packages that would be merged, in order:

Calculating dependencies /

!!! Problem resolving dependencies for net-wireless/wpa_supplicant
... done!

!!! The ebuild selected to satisfy "net-wireless/wpa_supplicant" has unmet requirements.
- net-wireless/wpa_supplicant-2.9-r2::gentoo USE="broadcom-sta dbus fils hs2-0 mbo mesh qt5 readline -ap -bindist -eap-sim -eapol-test -fasteap -libressl -macsec -p2p -privsep (-ps3) (-selinux) -smartcard -tdls -uncommon-eap-types (-wimax) -wps" ABI_X86="(64)"

  The following REQUIRED_USE flag constraints are unsatisfied:
    broadcom-sta? ( !fils !mesh !mbo )

  The above constraints are a subset of the following complete expression:
    macsec? ( !privsep ) privsep? ( !macsec ) broadcom-sta? ( !fils !mesh !mbo )


What I have done before this is:
Code:
sudo echo "net-wireless/wpa_supplicant broadcom-sta" >> /etc/portage/package.use/wpa_supplicant


Okay, great. You're on the right track. What that's saying is that you also have to disable the fils, mesh, and mbo USE flags (as those conflict with the broadcom-sta use flag)
This should do it
Code:
sudo echo "net-wireless/wpa_supplicant broadcom-sta -fils -mesh -mbo" >> /etc/portage/package.use/wpa_supplicant

It's working! Thank you so much!
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 5:52 pm    Post subject: Reply with quote

spike32 wrote:

Code:

blacklist ssb
blacklist brcmsmac
blacklist bcma
blacklist b43



Should I uninstall these blacklisted packages?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45435
Location: 56N 3W

PostPosted: Sun Apr 05, 2020 6:08 pm    Post subject: Reply with quote

spike32,

Those are kernel modules. You need take no action now but you can remove them next time you build your kernel.
Meanwhile, the blacklist allows them to be built but not installed.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sun Apr 05, 2020 6:57 pm    Post subject: Reply with quote

What about bluetooth instead? It's built on the same card.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45435
Location: 56N 3W

PostPosted: Sun Apr 05, 2020 7:44 pm    Post subject: Reply with quote

spike32,

Does it work?
What does dmesg say about it?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Mon Apr 06, 2020 7:18 am    Post subject: Reply with quote

NeddySeagoon wrote:
spike32,

Does it work?
What does dmesg say about it?

Nope, it doesn't work.
This is the dmesg output https://pastebin.com/jGp2qAJN

I have already set up kernel options reported in this guide https://wiki.gentoo.org/wiki/Dell_XPS_13_9343
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45435
Location: 56N 3W

PostPosted: Mon Apr 06, 2020 1:57 pm    Post subject: Reply with quote

spike32,

Trimming all the non bluetooth stuff
dmesg:
[    5.700035] Bluetooth: Core ver 2.22
[    5.700046] Bluetooth: HCI device and connection manager initialized
[    5.700048] Bluetooth: HCI socket layer initialized
[    5.700049] Bluetooth: L2CAP socket layer initialized
[    5.700051] Bluetooth: SCO socket layer initialized
[    5.746822] usbcore: registered new interface driver btusb
[    5.858245] Bluetooth: hci0: BCM: chip id 63
[    5.859217] Bluetooth: hci0: BCM: features 0x07
[    5.875220] Bluetooth: hci0: BCM20702A
[    5.876215] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[    6.788321] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1766
[    6.804275] Bluetooth: hci0: DW1550 Bluetooth 4.0 LE


Your kernel looks good. That's the hard bit.
What does rfkill say about bluetooth?

What USE flags is net-wireless/bluez built with?
Code:
eix bluez
or
Code:
emerge -pv bluez
will tell.

What bluetooth functionality are you trying to use?
What happens when you try. Verbatim error message would be good here.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Tue Apr 07, 2020 1:51 pm    Post subject: Reply with quote

NeddySeagoon wrote:
spike32,

Trimming all the non bluetooth stuff
dmesg:
[    5.700035] Bluetooth: Core ver 2.22
[    5.700046] Bluetooth: HCI device and connection manager initialized
[    5.700048] Bluetooth: HCI socket layer initialized
[    5.700049] Bluetooth: L2CAP socket layer initialized
[    5.700051] Bluetooth: SCO socket layer initialized
[    5.746822] usbcore: registered new interface driver btusb
[    5.858245] Bluetooth: hci0: BCM: chip id 63
[    5.859217] Bluetooth: hci0: BCM: features 0x07
[    5.875220] Bluetooth: hci0: BCM20702A
[    5.876215] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[    6.788321] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1766
[    6.804275] Bluetooth: hci0: DW1550 Bluetooth 4.0 LE


Your kernel looks good. That's the hard bit.
What does rfkill say about bluetooth?

What USE flags is net-wireless/bluez built with?
Code:
eix bluez
or
Code:
emerge -pv bluez
will tell.

What bluetooth functionality are you trying to use?
What happens when you try. Verbatim error message would be good here.


Code:
sudo emerge -pv bluez
/usr/lib64/python3.6/site-packages/portage/package/ebuild/_config/KeywordsManager.py:70: UserWarning: /etc/portage/package.keywords is deprecated, use /etc/portage/package.accept_keywords instead
  UserWarning)

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] net-wireless/bluez-5.54:0/3::gentoo  USE="cups mesh obex readline udev -btpclient -debug -deprecated -doc -experimental -extra-tools -midi (-selinux) -systemd -test -test-programs -user-session" ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python3_6 -python3_7 (-python3_8)" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB


Just the bluetooth option in KDE settings says No Bluetooth adapters have been found.
Back to top
View user's profile Send private message
axl
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1027
Location: Romania

PostPosted: Tue Apr 07, 2020 1:52 pm    Post subject: Reply with quote

Did you start the bluetooth service? either /etc/init.d/bluetooth start or systemctl start bluetooth?
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Tue Apr 07, 2020 2:20 pm    Post subject: Reply with quote

axl wrote:
Did you start the bluetooth service? either /etc/init.d/bluetooth start or systemctl start bluetooth?

Sorry, I'm dumb XD Yes it works!
Back to top
View user's profile Send private message
axl
Veteran
Veteran


Joined: 11 Oct 2002
Posts: 1027
Location: Romania

PostPosted: Tue Apr 07, 2020 2:21 pm    Post subject: Reply with quote

That's ok. I am glad you got it working. Anything else that still needs to be fixed?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 45435
Location: 56N 3W

PostPosted: Tue Apr 07, 2020 6:26 pm    Post subject: Reply with quote

spike32,

Depending on what you want to do you may need net-wireless/bluez built with the deprecated and/or extra-tools USE flags.

While it works, that's fine. :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
spike32
Tux's lil' helper
Tux's lil' helper


Joined: 17 Mar 2020
Posts: 96

PostPosted: Sat Apr 11, 2020 10:50 am    Post subject: Reply with quote

I don't know what happened, I have run
Code:
emerge @module-rebuild
following this guide https://wiki.gentoo.org/wiki/NVIDIA/nvidia-drivers
and now my broadcom wifi card doesn't work anymore. It doesn't show up in ifconfig too.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2, 3, 4, 5  Next
Page 2 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum