Sirs,
I am attempting to setup SuSe 11.2 on an HP dv5 laptop. I have the correct drivers and modules installed (i think). I have read the suggestions on posting and I hope I have gathered all of the correct information. I have worked on this for a few days so it would be difficult to recall all of the steps I have done (and undone).
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
and
02:00.0 0280: 14e4:4315 (rev 01)
I believe this device is supported. 14e4:4312
I have to run:
sudo modprobe b43
And then:
Running dmsg | grep -i firmware
2142.782838] Broadcom 43xx driver loaded Features: PML, Firmware-ID: FW13 ]
/usr/sbin/iwconfig
wlan0 IEEE 802.11 Access Point: Not-Associated
Link Quality:5 Signal level:0 Noise level:166
Rx invalid nwid:0 invalid crypt:2 invalid misc:0
It is not connected, nor can I make it connect…
sudo /usr/sbin/iwlist
Cell 01 - Address: 00:12:17:7A:B6:78
ESSID:"NotANetwork"
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:5/5 Signal level:-27 dBm Noise level:-92 dBm
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Ok, so there is the transmitter.
I cannot ping or connect in anyway. Any help would be apreciated
Thanks,
The Kapt’
I keep fiddling with it…
mevans@linux-m4rc:~> /usr/sbin/iwconfig wlan0 essid NotANetwork
Error for wireless request “Set ESSID” (8B1A) :
SET failed on device wlan0 ; Operation not permitted.
I tried setting thee key also, turned off encryption, tried WEP. Still no joy.
The Kapt’
On 04/16/2010 05:56 PM, kaptdeath wrote:
>
> I keep fiddling with it…
>
> mevans@linux-m4rc:~> /usr/sbin/iwconfig wlan0 essid NotANetwork
> Error for wireless request “Set ESSID” (8B1A) :
> SET failed on device wlan0 ; Operation not permitted.
>
> I tried setting thee key also, turned off encryption, tried WEP. Still
> no joy.
Just do the command ‘dmesg | grep b43’.
There aren’t any messages that match pattern in dmesg.
I’m not sure what these mean, but they look interesting:
dmesg | grep -i wlan
7.346970] eth0 renamed to wlan0 by udevd [365]
7.347552] udev: renamed network interface eth0 to wlan0
55.956578] wlan0: no IPv6 routers present
dmesg | grep -i eth0
7.326642] eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36
7.346970] eth0 renamed to wlan0 by udevd [365]
7.347552] udev: renamed network interface eth0 to wlan0
7.387974] eth1_rename renamed to eth0 by udevd [377]
7.388667] udev: renamed network interface eth1_rename to eth0
15.841424] r8169: eth0: link down
15.841909] ADDRCONF(NETDEV_UP): eth0: link is not ready
Perhaps I should reinstall?
The Kapt’n
On 04/16/2010 09:46 PM, kaptdeath wrote:
>
> There aren’t any messages that match pattern in dmesg.
>
> I’m not sure what these mean, but they look interesting:
>
> dmesg | grep -i wlan
> 7.346970] eth0 renamed to wlan0 by udevd [365]
> 7.347552] udev: renamed network interface eth0 to wlan0
> 55.956578] wlan0: no IPv6 routers present
>
> dmesg | grep -i eth0
> 7.326642] eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller
> 5.60.48.36
> 7.346970] eth0 renamed to wlan0 by udevd [365]
> 7.347552] udev: renamed network interface eth0 to wlan0
> 7.387974] eth1_rename renamed to eth0 by udevd [377]
> 7.388667] udev: renamed network interface eth1_rename to eth0
> 15.841424] r8169: eth0: link down
> 15.841909] ADDRCONF(NETDEV_UP): eth0: link is not ready
>
> Perhaps I should reinstall?
As has been discussed many times here, the 14e4:4315 device is not
supported by any kernel before 2.6.32. You could reinstall a thousand
times and it still wouldn’t work until you installed 11.3.
Use the Broadcom wl driver.
Thanks for the info. I must have missed that tidbit. So instead of:
modprobe b43
its
modprobe wl
or perhaps you could direct me to some instructions applicable to 11.2?
Thanks,
The Kapt’n
I reread your first sticky. I didn’t see instructions on “blacklisting” b43 and ssb modules. However it appears that I am getting these in the first update. I went ahead and reinstalled as I’m sure I had really hosed things up. Sorry about being so dense, but not everyone gets to be a wireless god:P
Oh, the link at the end of the first sticky post kinda got me on the wrong track anyway.
I’ll post when the reinstall finishes.
The Kapt’n
Ok, everything works now. When you use yast to install the two broadcom RPMs from packman (which I THINK uninstalls the b43 and ssb modules) AND run the /usr/sbin/install_bcm43xx_firmware. You are in business. Thanks for the help lwfinger! I guess I was making it too complicated. Learned a lot of useful command line wireless commands tho.
One thing though. Did I understand you correctly in that if my kernel is ever upgraded (does that include patches, like NVIDIA?) I have to repeat this process?
Thanks again,
The Kapt’n
On 04/17/2010 11:06 AM, kaptdeath wrote:
>
> Ok, everything works now. When you use yast to install the two broadcom
> RPMs from packman (which I THINK uninstalls the b43 and ssb modules) AND
> run the /usr/sbin/install_bcm43xx_firmware. You are in business.
> Thanks for the help lwfinger! I guess I was making it too complicated.
> Learned a lot of useful command line wireless commands tho.
You don’t need the firmware for wl. As Broadcom owns the copyright, they
can build it into the driver and distribute it that way. As we do not
have that right, b43 has to get firmware by extracting it from a
Broadcom driver, which is what the script does.
> One thing though. Did I understand you correctly in that if my kernel
> is ever upgraded (does that include patches, like NVIDIA?) I have to
> repeat this process?
Yes, all kernel modules MUST be built for the kernel in which they
will run. That applies to things like wl as well as the accelerator
modules for graphics. That is why I use the framebuffer driver for my
nVidia card.
Thanks, I guess it was a good thing that I installed the NVIDA kernel before I did the Broadcom patches (I do like that 3d acceleration). I did an lsmod while the system was doing its first update and saw the b43 and ssb modules (which seemed a bit odd).
If I understand correctly I needed to do all of the steps, just that some of the steps did things that I didn’t need. ie. The install script installed the firmware (not needed) but copied wl.ko into the correct location? I looked for wl.ko before I ran the script and didn’t find it. I could be wrong though (it has happed before)
Thanks for trying to enlighten me.
The Kapt’n
Oops, ignore the last post. I see now, I should have checked the RPM contents and the script file. The script is completely unnecessary. The two RPMs remove the b43 and ssb modules and install wl.ko. (dunno why I didn’t find it after I ran the RPMs). :\
Good luck with the next round of wireless hacking.
The Kapt’n
This is non sense, no sane RPM would remove any modules present by another RPM (in this case even the main kernel package).
The modules are blacklisted and will not be loaded automatically again.
Because one needs to unload the modules b43/ssb and then load the new one once manually if one does not want to reboot the machine.
Again, a sane RPM will never do this automatically as there might be other working devices needing those modules (and yes, there are some examples).
The solution with blacklisting is better, but not yet perfect (for certain cases, i.e. if there is a wired device needing ssb), but this would lead too far away from topic.