Created attachment 998 [details] MCC network setup showing lack of device to connect broadcom driver On kernel updates, when setting up the wireless, I've been running into an issue where wlan0 will show up for the ndiswrapper driver and the other option, but not for the broadcom driver itself. I'm currently using the 2.6.38.8-6.1 kernel to deal with another issue (amd74xx driver versus sata_amd) and the test udev that was used to try to fix that issue earlier on.
is dkms-broadcom-wl installed ?
Component: Release (media or process) => RPM PackagesSource RPM: (none) => drakx-net
Yes it is, and the drivers appear to compile into the kernel at first run without error (at least from what I can tell in verbose startup mode)
CC: (none) => wrw105
CC: sysadmin-bugs => (none)
CC: (none) => mageia, marja11
Try as root echo "blacklist b43" >> /etc/modprobe.d/blacklist-mga and reboot
CC: (none) => krytarowski
Blacklisting just left no device available for either the native b43 driver or ndiswrapper. I'll attach a snapshot momentarily. I had to remove the blacklist and run modprobe to be able to use the wireless again.
Broadcom-wl driver conflicts with b43 and I have to blacklist it... and I don't use ndiswrapper... Do you use 3 driver concurrently?
Those are just the options that come up when I run the mcc network connection for wifi. The problem doesn't appear to be a driver issue, but that a device isn't available for the broadcom driver. In the picture I've attached, instead of: wlan0:Broadcom... I just see :broadcom... with no device attached, so I can't use it as a live system
In fact what is the real issue ?
Manuel, The issue (at least at the level I'm working on) is this: Once I have installed the native broadcom driver for my built-in wi-fi card, I attempt to configure it with MCC, and the result is as shown in the attached picture. In short, whether udev, the kernel, etc., doesn't configure a device to work with the broadcom driver. If you look at the picture, it shows the following: :broadcom corporation BCM4312 802.11a/b/g wlan0:wlan0 wlan0:Use a Windows driver (with ndiswrapper) Any attempt to use the native driver throws the following error: Unable to find the network device for the selected device (using wl driver) Ideally, I'd like it to show up as a wifi device so I can see signal strength easily, as under mandriva in the past it has configured as eth0, but just working at this point would be greatly appreciated!
(In reply to comment #8) > Manuel, > > The issue (at least at the level I'm working on) is this: Once I have > installed the native broadcom driver for my built-in wi-fi card, I attempt to > configure it with MCC, and the result is as shown in the attached picture. In > short, whether udev, the kernel, etc., doesn't configure a device to work with > the broadcom driver. If you look at the picture, it shows the following: > > :broadcom corporation BCM4312 802.11a/b/g > wlan0:wlan0 > wlan0:Use a Windows driver (with ndiswrapper) > > Any attempt to use the native driver throws the following error: > Unable to find the network device for the selected device (using wl driver) > > Ideally, I'd like it to show up as a wifi device so I can see signal strength > easily, as under mandriva in the past it has configured as eth0, but just > working at this point would be greatly appreciated! Ok thanks. Blino, ideas ? (just to be sure also attach lspcidrake -v)
Assignee: bugsquad => mageiaSummary: device not found for broadcom driver => device not found for BCM4312 driver
r852 : Ricoh Co Ltd|xD-Picture Card Controller [SYSTEM_OTHER] (vendor:1180 device:0852 subv:103c subd:30b7) (rev: 05) unknown : Ricoh Co Ltd|R5C592 Memory Stick Bus Host Adapter [SYSTEM_OTHER] (vendor:1180 device:0592 subv:103c subd:30b7) (rev: 0a) sdhci_pci : Ricoh Co Ltd|R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [SYSTEM_SDHCI] (vendor:1180 device:0822 subv:103c subd:30b7) (rev: 19) firewire_ohci : Ricoh Co Ltd|R5C832 IEEE 1394 Controller [SERIAL_FIREWIRE] (vendor:1180 device:0832 subv:103c subd:30b7) wl : Broadcom Corporation|BCM4312 802.11a/b/g [NETWORK_OTHER] (vendor:14e4 device:4312 subv:103c subd:1360) (rev: 01) k8temp : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] Miscellaneous Control [BRIDGE_HOST] (vendor:1022 device:1103) amd64_edac_mod : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] DRAM Controller [BRIDGE_HOST] (vendor:1022 device:1102) unknown : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] Address Map [BRIDGE_HOST] (vendor:1022 device:1101) unknown : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] HyperTransport Technology Configuration [BRIDGE_HOST] (vendor:1022 device:1100) forcedeth : nVidia Corporation|MCP51 Ethernet Controller [BRIDGE_OTHER] (vendor:10de device:0269 subv:103c subd:30b7) (rev: a3) snd_hda_intel : nVidia Corporation|MCP51 High Definition Audio (vendor:10de device:026c subv:103c subd:30b7) (rev: a2) unknown : nVidia Corporation|MCP51 PCI Bridge [BRIDGE_PCI] (vendor:10de device:026f) (rev: a2) sata_nv : nVidia Corporation|MCP51 Serial ATA Controller [STORAGE_IDE] (vendor:10de device:0266 subv:103c subd:30b7) (rev: f1) pata_amd : nVidia Corporation|MCP51 IDE [STORAGE_IDE] (vendor:10de device:0265 subv:103c subd:30b7) (rev: f1) ehci_hcd : nVidia Corporation|MCP51 USB Controller [SERIAL_USB] (vendor:10de device:026e subv:103c subd:30b7) (rev: a3) ohci_hcd : nVidia Corporation|MCP51 USB Controller [SERIAL_USB] (vendor:10de device:026d subv:103c subd:30b7) (rev: a3) unknown : nVidia Corporation|MCP51 PMU [PROCESSOR_CO] (vendor:10de device:0271 subv:103c subd:30b7) (rev: a3) nv_tco : nVidia Corporation|MCP51 SMBus [SERIAL_SMBUS] (vendor:10de device:0264 subv:103c subd:30b7) (rev: a3) unknown : nVidia Corporation|MCP51 LPC Bridge [BRIDGE_ISA] (vendor:10de device:0260 subv:103c subd:30b7) (rev: a3) unknown : nVidia Corporation|MCP51 Host Bridge [MEMORY_RAM] (vendor:10de device:0270 subv:103c subd:30b7) (rev: a2) Card:NVIDIA GeForce 6100 to GeForce 360: nVidia Corporation|C51 [Geforce Go 6150] [DISPLAY_VGA] (vendor:10de device:0244 subv:103c subd:30b7) (rev: a2) shpchp : nVidia Corporation|C51 PCI Express Bridge [BRIDGE_PCI] (vendor:10de device:02fd) (rev: a1) shpchp : nVidia Corporation|C51 PCI Express Bridge [BRIDGE_PCI] (vendor:10de device:02fc) (rev: a1) unknown : nVidia Corporation|C51 Memory Controller 2 [MEMORY_RAM] (vendor:10de device:027e) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 3 [MEMORY_RAM] (vendor:10de device:027f subv:103c subd:30b7) (rev: a2) unknown : nVidia Corporation|C51 Host Bridge [MEMORY_RAM] (vendor:10de device:02ff subv:103c subd:30b7) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 4 [MEMORY_RAM] (vendor:10de device:02f9 subv:103c subd:30b7) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 5 [MEMORY_RAM] (vendor:10de device:02f8 subv:103c subd:30b7) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 1 [MEMORY_RAM] (vendor:10de device:02fe subv:103c subd:30b7) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 0 [MEMORY_RAM] (vendor:10de device:02fa subv:103c subd:30b7) (rev: a2) unknown : nVidia Corporation|C51 Host Bridge [MEMORY_RAM] (vendor:10de device:02f0 subv:103c subd:30b7) (rev: a2) hub : Linux 2.6.38.8-desktop-8.mga ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) usb_storage : HTC|Android Phone [Mass Storage|SCSI|Bulk (Zip)] (vendor:0bb4 device:0c8d) hub : Linux 2.6.38.8-desktop-8.mga ohci_hcd|OHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0001) usbhid : Logitech|USB Trackball [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:046d device:c408)
And maybe "rfkill list" and (as root): # iwconfig (you can anonimize domain/encryption info from that)
CC: (none) => dvgevers
CC: (none) => marianne
I've been looking into my modprobe.d directory. There's a file in there called blacklist-broadcom-wl.conf (I may have added this in a previous attempt to get this to work, I just don't remember any more!) The contents of this file: blacklist brcm80211 blacklist b43 blacklist ssb blacklist bcma I don't see it called by blacklist-mga. Could this be the problem?
I think the blacklist was added by the update to the broadcom driver. After trying the driver, still the same issue. Could this be an issue with udev/kernel? The reason I ask is that a device node is not added to the card. Also, I've had to uninstall the current broadcom driver so I can at least use the ssb driver to get some form of wifi, Again, not ideal but until we get this worked out, it's the best I can do.
Your hardware may work removing dkms-broadcom-wl and installing b43-openfwwf : I have the same 4312 hardware. Be sure to reboot after removing dkms-broadcom-wl as it blacklists open-source drivers.
CC: (none) => lists.jjorge
After installing M2B1, I've found the issue is also happening in cauldron, so I've changed the version to Cauldron for the issue. It's finding the broadcom wireless driver, but not assigning a device node to it.
Version: 1 => Cauldron
(In reply to comment #15) > After installing M2B1, I've found the issue is also happening in cauldron, so > I've changed the version to Cauldron for the issue. > > It's finding the broadcom wireless driver, but not assigning a device node to > it. Please answer to https://bugs.mageia.org/show_bug.cgi?id=3159#c14 so that we can continue investigating.
Now that version is changed to cauldron, setting this report to block bug 5015 @ Bill, Sometimes when I comment users think they don't need to answer a question that was made before anymore. Please do answer José's question in Comment 14 and 16
Blocks: (none) => 5015
Marja and Jose, The ssb driver was working under 1. There had been issues under cauldron, but it looks like the issue is fixed with the latest updates (drakxnet?). still, using this driver looks more like a workaround, rather than the manufacturer's driver, which is why I filed the bug in the first place.
(In reply to comment #18) > The ssb driver was working under 1. There had been issues under cauldron, but > it looks like the issue is fixed with the latest updates (drakxnet?). OK, so closing the bug. > > still, using this driver looks more like a workaround, rather than the > manufacturer's driver, which is why I filed the bug in the first place. You are wrong : the manufacturer does not provide a linux driver for this hardware.
Status: NEW => RESOLVEDResolution: (none) => FIXED