OpenSUSE 12.1 KDE 32BIT. My wireless adapter is Linksys WPC300N V1 PCMCIA card. I installed Broadcom wl driver via YAST Software Management (both files broadcom-wl and broadcom-wl-kmp-default). Still no wireless despite blinking LINK pilot light.
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11bgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:130 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
dmesg
13.941219] lib80211: common routines for IEEE802.11 drivers
13.941224] lib80211_crypt: registered algorithm 'NULL'
13.947894] wl: module license 'unspecified' taints kernel.
13.947904] Disabling lock debugging due to kernel taint
13.981249] wl 0000:0a:00.0: enabling device (0000 -> 0002)
13.981270] wl 0000:0a:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
13.981284] wl 0000:0a:00.0: setting latency timer to 64
14.150511] ifup[567]: Service network not started and mode 'auto' -> skipping
14.163790] lib80211_crypt: registered algorithm 'TKIP'
14.164512] eth1: Broadcom BCM4329 802.11 Hybrid Wireless Controller 5.100.82.112
14.241682] ifup[602]: Service network not started and mode 'auto' -> skipping
I did blacklist b43 and ssb, as well as ath5k, the kernel driver of Atheros AR-5001 for built-in miniPCIe wireless G adapter.
I also noted that the LINK pilot light with wl installed is not as solid and steady as that exists when the default b43-pci-bridge kernel driver is in place. The latter exists prior to Broadcom wl being installed and YAST Software Management shows b43-fwcutter as installed. Since there is no wireless with b43-pci-bridge, I decided to try wl.
These files will be downloaded from the Broadcom Web Site if they do not exist
and you have a Wired network connection now. If you do not have these files
and no network connection, this installation script file will fail to work.
on to your computer now (y/N)?y
KBUILD_NOPEDANTIC=1 make -C /lib/modules/uname -r/build M=pwd clean
make[1]: Entering directory /usr/src/linux-3.1.10-1.9-obj/i386/default' Wireless Extension is the only possible API for this kernel version Using Wireless Extension API make[1]: Leaving directory /usr/src/linux-3.1.10-1.9-obj/i386/default’
KBUILD_NOPEDANTIC=1 make -C /lib/modules/uname -r/build M=pwd
make[1]: Entering directory /usr/src/linux-3.1.10-1.9-obj/i386/default' Wireless Extension is the only possible API for this kernel version Using Wireless Extension API LD /home/tt888/Downloads/hybrid_wl/built-in.o CC [M] /home/tt888/Downloads/hybrid_wl/src/shared/linux_osl.o CC [M] /home/tt888/Downloads/hybrid_wl/src/wl/sys/wl_linux.o CC [M] /home/tt888/Downloads/hybrid_wl/src/wl/sys/wl_iw.o CC [M] /home/tt888/Downloads/hybrid_wl/src/wl/sys/wl_cfg80211.o LD [M] /home/tt888/Downloads/hybrid_wl/wl.o WARNING: modpost: missing MODULE_LICENSE() in /home/tt888/Downloads/hybrid_wl/wl.o see include/linux/module.h for more information Building modules, stage 2. Wireless Extension is the only possible API for this kernel version Using Wireless Extension API MODPOST 1 modules WARNING: modpost: missing MODULE_LICENSE() in /home/tt888/Downloads/hybrid_wl/wl.o see include/linux/module.h for more information CC /home/tt888/Downloads/hybrid_wl/wl.mod.o LD [M] /home/tt888/Downloads/hybrid_wl/wl.ko make[1]: Leaving directory /usr/src/linux-3.1.10-1.9-obj/i386/default’
root’s password:
cat: /etc/rc.local: No such file or directory
/home/tt888/bin/install-wireless: line 128: /etc/rc.local: Permission denied
Your Broadcom hybrid-portsrc_x86_32-v5_100_82_112.tar.gz and files have been installed
James, could you comment on the last 2 lines above? I don’t quite understand!
There is NEVER a need to uninstall b43-fwcutter for any reason.
If you do not wish to use b43 and select wl instead, you should blacklist ssb
and b43. The advantage of keeping the firmware around is that you can switch b43
on by unloading wl and loading b43. When you update the kernel, and wl is not
available, you can still use b43.
No, I am not using NM. I just checked YAST > Network Settings> ifup and the connection has NO subnet mask (255.255.255.0) at all. Instead, the Netmask field only has “/24”. I suspect this is related to the following portion of dmesg output:
355.288032] martian source 192.168.1.255 from 192.168.1.104, on dev eth0
355.288039] ll header: ff:ff:ff:ff:ff:ff:00:14:d1:c3:90:e3:08:00
355.290555] martian source 192.168.1.255 from 192.168.1.104, on dev eth1
355.290561] ll header: ff:ff:ff:ff:ff:ff:00:14:d1:c3:90:e3:08:00
376.839474] martian source 192.168.1.255 from 192.168.1.104, on dev eth0
376.839481] ll header: ff:ff:ff:ff:ff:ff:00:14:d1:c3:90:e3:08:00
376.841936] martian source 192.168.1.255 from 192.168.1.104, on dev eth1
The IP addresses following “martian source” is wrong.
I may look for another wireless adapter that works consistently in Debian, Ubuntu, Fedora and especially openSUSE.
I finally did get wireless connection established! Not sure if any or all of the following steps help solves the problem:
#echo modprobe wl >> /etc/rc.local
#etc/init.d/network start
(Screen shows: "redirecting to systemctl"
YAST > Network Settings > Enter HOST name in the first page (General or Overview) >Switch from ifup to Network Manager
Unplug CAT5 cable
Reboot
I still have the following 2 lines in dmesg, but they no longer concern me as long as wireless connection is established:
13.704416] eth1: Broadcom BCM4329 802.11 Hybrid Wireless Controller 5.100.82.112
13.772089] ifup[607]: Service network not started and mode 'auto' -> skipping
On 05/04/2012 01:46 AM, taytong888 wrote:
>
> Hello caf4926,
>
> No, I am not using NM. I just checked YAST> Network Settings> ifup
> and the connection has NO subnet mask (255.255.255.0) at all. Instead,
> the Netmask field only has “/24”.
The /24 is shorthand for 24 bits of ones from the left. If you count them (255
== 8 bits), that is identical with 255.255.255.0.