Bug 34577 - Can't use dkms-broadcom-wl
Summary: Can't use dkms-broadcom-wl
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-25 16:02 CEST by Bernard SIAUD
Modified: 2025-09-03 11:15 CEST (History)
2 users (show)

See Also:
Source RPM: broadcom-wl
CVE:
Status comment:


Attachments

Description Bernard SIAUD 2025-08-25 16:02:08 CEST
Description of problem:
I can't use Wi-Fi


Version-Release number of selected component (if applicable):
6.30.223.271 67.mga10.nonfree x86_64

How reproducible:
Try to configurate my Wi-Fi whith "drakconnect"

Steps to Reproduce:
1. click "Sans fil (Wi-FI)"
A pop say :
Certains paquetages (broadcom-wl) sont nécessaires mais ne sont pas disponibles. Ces paquetages sont disponibles dans Mageia, ou dans le dépôt officiel de paquetages non-free.

Le composant suivant est manquant : wl

Les fichiers requis peuvent aussi être installés à partir de cette URL :
http://www.broadcom.com/support/802.11/linux_sta.php

After :
Impossible d'installer les paquetages (dkms-broadcom-wl) !

But, dkms-broadcom-wl is installed !
Comment 1 Lewis Smith 2025-08-26 21:04:04 CEST
Thank you for the report.

> How reproducible:
> Try to configurate my Wi-Fi whith "drakconnect"
> 1. click "Sans fil (Wi-FI)"
> A pop say :
> Certains paquetages (broadcom-wl) sont nécessaires mais ne sont pas
> disponibles. Ces paquetages sont disponibles dans Mageia, ou dans le dépôt
> officiel de paquetages non-free.
> Le composant suivant est manquant : wl
> 
> After :
> Impossible d'installer les paquetages (dkms-broadcom-wl) !
> 
> But, dkms-broadcom-wl is installed !
The last sentance matters... And implies that you have 'nonfree' repos enabled.
Perhaps you could post the evidence:
 $ rpm -q --last dkms-broadcom-wl

And also give some information about your system:
 $ inxi -MSi

CC: (none) => lewyssmith
Source RPM: (none) => broadcom-wl

Comment 2 Bernard SIAUD 2025-08-26 22:36:45 CEST
[root@localhost ~]# rpm -q --last dkms-broadcom-wl
dkms-broadcom-wl-6.30.223.271-67.mga10.nonfree.x86_64 mar. 29 juil. 2025 20:29:19
[root@localhost ~]# inxi -MSi
System:
  Host: localhost Kernel: 6.12.43-desktop-1.mga10 arch: x86_64 bits: 64
  Console: pty pts/0 Distro: Mageia 10
Machine:
  Type: Laptop System: Dell product: Latitude E6430s v: 01 serial: B8S73X1
  Mobo: Dell model: 0XHTPW v: A00 serial: /B8S73X1/CN1296134K00D6/
    BIOS: Dell v: A19 date: 05/08/2017
Network:
  Device-1: Intel 82579LM Gigabit Network driver: e1000e
  IF: eno1 state: down mac: f0:1f:af:06:7e:8b
  Device-2: Broadcom BCM43228 802.11a/b/g/n driver: N/A
  IF-ID-1: enp0s20u1 state: unknown speed: -1 duplex: half
    mac: 7e:7b:ef:44:65:86
  IP v4: 10.155.255.201/24 type: dynamic noprefixroute scope: global
  IP v6: fe80::7c7b:efff:fe44:6586/64 virtual: proto kernel_ll scope: link
  WAN IP: 82.64.160.244
Comment 3 Lewis Smith 2025-08-28 21:41:28 CEST
Thank you for this information.

Assigning to Kerbel/Drivers, but it may be a problem with our utilites, so CC'ing Mageiatools whose bug it might be.

CC: lewyssmith => mageiatools
Assignee: bugsquad => kernel

Comment 4 Giuseppe Ghibò 2025-08-28 21:51:57 CEST
It might be a duplicate of #33821.

CC: (none) => ghibomgx

Comment 5 Bernard SIAUD 2025-08-29 07:24:52 CEST
Papoteur as resolved this problem in the news broadcom-wl rpm.

Thank's Papoteur.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 6 Giuseppe Ghibò 2025-08-29 09:11:44 CEST
But networkmanager works on that hardware?
Comment 7 Bernard SIAUD 2025-09-03 11:15:41 CEST
It's good ? Not ?

[root@localhost ~]# systemctl status networkmanager.service 
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-09-03 10:58:21 CEST; 14min ago
 Invocation: 57436f2d1f8c4b348fa0f11b40a8a3eb
       Docs: man:NetworkManager(8)
   Main PID: 1016 (NetworkManager)
      Tasks: 4 (limit: 9362)
     Memory: 12.3M (peak: 13.2M)
        CPU: 696ms
     CGroup: /system.slice/NetworkManager.service
             └─1016 /usr/sbin/NetworkManager --no-daemon

sept. 03 11:06:20 localhost NetworkManager[1016]: <info>  [1756890380.8345] policy: set 'System DartyBox_F16E (wlp2s0)' (>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.1362] dhcp4 (wlp2s0): state changed new lease, addr>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.2976] dhcp4 (wlp2s0): state changed new lease, addr>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.2999] policy: set 'System DartyBox_F16E (wlp2s0)' (>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.4292] device (wlp2s0): state change: ip-config -> i>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.4341] device (wlp2s0): state change: ip-check -> se>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.4344] device (wlp2s0): state change: secondaries ->>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.4349] manager: NetworkManager state is now CONNECTE>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.4355] device (wlp2s0): Activation: successful, devi>
sept. 03 11:06:21 localhost NetworkManager[1016]: <info>  [1756890381.4361] manager: NetworkManager state is now CONNECTE>

Note You need to log in before you can comment on or make changes to this bug.