Hello, I followed the “Getting Your Wireless to Work” instructions. Please help. I’ve returned to Linux after many years, and modem/Internet still a pain. I dual booted my Windows 7 64 bit system, and installed OpenSuse 12.3 with KDE. WiFi does not work. I did manually reboot to get Network Manager operating after install. Network Manager is chosen in YAST. Here is the info I gathered using the instructions.
**
Windows Control Panel Info**
Control Panel -> Device Manager -> Network Adaptors I see:
DW1530 Wireless-N WLAN Half-Mini Card
Intel(R) 82579LM Gigabit Network Connection
**
Linux YAST -> Hardware -> Hardware Information**
1) There is no “Wireless Lan”
2) There was no DW1530 either, as shown in Windows Device Manager
3) I believe the “Broadcom Network controller” info below is my WiFi from my Hardware output. And I suspect that the DW1530 mentioned above, is the driver for the Broadcom.
Checked Boot.msg for Firmware messages**
[FONT=Times New Roman]2013-05-12T02:44:33.493371+04:00 linux kernel: 0.183699] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[/FONT]**I searched boot.msg for the word Broadcom
**[size=3][FONT=Times New Roman][FONT=Times New Roman]2013-05-12T04:18:10.487385+04:00 linux-ksey kernel: 2.327629] usb 2-1.8: Manufacturer: Broadcom Corp
Note: The driver DW1530 does not appear in boot.msg file .
[/FONT] Sudo /usr/sbin/iwlist scan
lo Interface doesn’t support scanning.
em1 Interface doesn’t support scanning.
/usr/sbin/iwconfig
lo no wireless extensions.
em1 no wireless extensions.**
And in KDE “Network Connections” **
The tabs “Wired”, “VPN”, “DSL” can be selected. The “Wireless” tab is greyed out
I hope somebody can guide me on this.
Thanks
[/size][/FONT]
On 05/11/2013 07:06 PM, gz1968 wrote:
>
> Hello, I followed the “Getting Your Wireless to Work” instructions.
> Please help. I’ve returned to Linux after many years, and modem/Internet
> still a pain. I dual booted my Windows 7 64 bit system, and installed
> OpenSuse 12.3 with KDE. WiFi does not work. I did manually reboot to
> get Network Manager operating after install. Network Manager is chosen
> in YAST. Here is the info I gathered using the instructions.
> *
> Windows Control Panel Info*
> Control Panel -> Device Manager -> Network Adaptors I see:
> DW1530 Wireless-N WLAN Half-Mini Card
> Intel(R) 82579LM Gigabit Network Connection
> *
> Linux YAST -> Hardware -> Hardware Information*
> 1) There is no “Wireless Lan”
> 2) There was no DW1530 either, as shown in Windows Device
> Manager
> 3) I believe the “Broadcom Network controller” info below is my
> WiFi from my Hardware output. And I suspect that the DW1530 mentioned
> above, is the driver for the Broadcom.
>
> 32: PCI 300.0: 0280 Network controller
> [Created at pci.319]
> Unique ID: svHJ.xf2myFHT2jA
> Parent ID: qTvu.bsXBLqvax56
> SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:03:00.0
> SysFS BusID: 0000:03:00.0
> Hardware Class: network
> Model: “Broadcom Network controller”
> Vendor: pci 0x14e4 “Broadcom”
> Device: pci 0x4359
> SubVendor: pci 0x1028 “Dell”
> SubDevice: pci 0x0011
> Driver: “bcma-pci-bridge”
> Driver Modules: “bcma”
> Memory Range: 0xe6d00000-0xe6d03fff (rw,non-prefetchable)
> IRQ: 17 (238 events)
> Module Alias:
> “pci:v000014E4d00004359sv00001028sd00000011bc02sc80i00”
> Driver Info #0:
> Driver Status: bcma is active
> Driver Activation Cmd: “modprobe bcma”
> Config Status: cfg=no, avail=yes, need=no, active=unknown
> Attached to: #22 (PCI bridge) *
>
> Checked Boot.msg for Firmware messages*
> 2013-05-12T02:44:33.493371+04:00 linux kernel:
> 0.183699] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
>
> *I searched boot.msg for the word Broadcom
> 2013-05-12T04:18:10.487385+04:00 linux-ksey kernel:
> 2.327629] usb 2-1.8: Manufacturer: Broadcom Corp
>
> Note: The driver DW1530 does not appear in boot.msg file .
>
> Sudo /usr/sbin/iwlist scan
> lo Interface doesn’t support scanning.
>
> em1 Interface doesn’t support scanning.
>
> /usr/sbin/iwconfig
> lo no wireless extensions.
>
> em1 no wireless extensions.
>
> And in KDE “Network Connections” *
> The tabs “Wired”, “VPN”, “DSL” can be selected. The “Wireless” tab is
> greyed out
>
> I hope somebody can guide me on this.
> Thanks
The kernel pays no attention to the model numbers that are attached by the OEM
vendor, which is Dell in this case. Drivers are loaded based on the PCI or USB
ID, which is a PCI ID of 14e4:4359 in your case.
Your device is recognized by the bcma sub-driver and main driver brcmsmac. I do
not know how good the support is, but you will need to have the kernel-firmware
package loaded. The alternative is to use the closed-source driver wl. To
install it, activate the packman repo and install the package for
broadcom-wl-kmp for your kernel.
An in-kernel driver will be automatically updated when the kernel changes;
however, one of the unpleasant side effects of an out-of-kernel driver is that
you will need a new version of that driver whenever your kernel is changed. Yhat
includes minor version changes! As long as you have a wired connection
available, that is not a problem; however, if you depend solely on wireless for
network access, I recommend that you go to the Broadcom site, download the
necessary hybrid source/binary blob file, and get all the parts needed to
rebuild the driver on your machine.
Thank you for responding:
If I understand correctly, my Broadcom BCM5880 for WiFi is recognized by these “bcma” sub-driver and main driver “brcmsmac”. Therefore, I get the results as shown below. Correct? But these drivers, apparently do not support specifically the PCI ID of “14e4:4359” of my Broadcom BCM5880 WiFi. So it is either build the driver, which is beyond me. I looked at Broadcom site, not much help there. Or install this Broadcom-kl-kmp package. I found three packages. Which one?
For any out-of-kernel driver, you must choose the one that matches exactly the
kernel that you are using. You can determine that with the ‘uname -r’ command.
The interpretation of “desktop-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm” is as
follows:
It is built using version 5.100.82.112 of the Broadcom driver.
It works with the desktop variant of kernel 3.7.10_1.4-11.2.x86_64. This one is
probably what you need.
It’s Fixed !!! Thanks for the help.
I found the RPM build for the broadcom-wl files for SuSE 12.3 on the PACKMAN site. For anybody with this problem later, I did as follows:
In a console terminal type
uname -r
I saw 3.7.10-1.1-desktop but yours will be different.
So my kernel type is “desktop”. Will need this later.
Setup this mirror as a Depository in YAST
a) YAST -> Software Repositories -> ADD -> ftp or http (depending on what your mirror) -> (Enter the URL and the name you like)
b) Now in YAST -> Software Management search for “broadcom-wl”
c) Choose both
broadcom-wl
broadcom-wl-kmp-{kernel type} Mine was desktop, so I choose broadcom-wl-kmp-desktop
d) Accept
Reboot computer. I’m sure there is a way to start up the software without rebooting if you know how.
After rebooting
a) Configure Desktop -> Network Settings -> Wireless -> Add Wireless -> Scan and the rest is typical.
b) By the way, FireFox would not work or open a site for the first few tries after I was finished. Even though I could ping out, and was connected to the Internet using Wi-Fi. It started working after a few minutes. So that was weird.
You don’t need to find Packman mirrors. In Software Repositories in YaST, you can clock on Add and then choose Community Repositories. Packman is listed there. Just add the ones you want.
I just switched from the unsupported xp to linux and as a novice this is my first major stumbling block. Following the excellent step-by-step description, I installed the driver, but when I try to activate it, the network setting window shows only the “Wired” and the “VPN” tabs active without any content, although I am connected via Ethernet cable. What am I missing?
Another issue is the driver for my NVIDIA G98 (GeForce 9300 GE) dual monitor card, as two monitors are recognized but the second is not alive. Any suggestion?
On 01/02/2014 05:06 PM, mgl wrote:
>
> I just switched from the unsupported xp to linux and as a novice this is
> my first major stumbling block. Following the excellent step-by-step
> description, I installed the driver, but when I try to activate it, the
> network setting window shows only the “Wired” and the “VPN” tabs active
> without any content, although I am connected via Ethernet cable. What am
> I missing?
> Another issue is the driver for my NVIDIA G98 (GeForce 9300 GE) dual
> monitor card, as two monitors are recognized but the second is not
> alive. Any suggestion?
Is this your first post? I use NNTP, and that info is not available here.
Assuming that it is, welcome.
Please start a new post for each problem. The one on wireless is appropriate
here, but the graphics adapter should be posted in the hardware forum. You will
get more attention than jumping onto the end of an old thread.
When you post the new entry on your wireless, please include the output of the
following commands:
/sbin/lspci -nn
iwconfig
sudo zypper in rfkill
/usr/sbin/rfkill list
Please post computer output insice code tags (In the advanced edit section).
Enter YaST->Network Devices->Network Settings->Global Options and switch to “User-controlled using NetworkManager” there.
If that is already activated, switch back to “Traditional Method with ifup”, click OK, enter again and switch back to NetworkManager.
There was a bug in 12.3 that could cause the NetworkManager service to not be activated correctly (or resp. the ifup service not deactivated).
That could explain why the NetworkManager applet is not working for you…
But it should work again after doing that switch in YaST.