Ok I have my wireless working via
sudo /usr/sbin/install_bcm43xx_firmware
sudo /sbin/modprobe -rv b43
sudo /sbin/modprobe -v b43
was working for about 3 weeks than nothing
I am at a lost try to re install firmware reboot I can see the network but can not connect to it. And help is great
thanks
On 11/15/2009 06:26 PM, zero1976 wrote:
>
> Ok I have my wireless working via
> sudo /usr/sbin/install_bcm43xx_firmware
> sudo /sbin/modprobe -rv b43
> sudo /sbin/modprobe -v b43
> was working for about 3 weeks than nothing
> I am at a lost try to re install firmware reboot I can see the network
> but can not connect to it. And help is great
> thanks
Please post the output of ‘dmesg | grep b43’.
What method of connecting are you using?
I hope this is what you need if not can you give me the common thanks for the help
nput: USB 2.0 Camera as /devices/pci0000:00/0000:00:0b.1/usb2/2-4/2-4:1.0/input/input9
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 21
HDA Intel 0000:00:10.1: PCI INT B -> Link[LAZA] -> GSI 21 (level, high) -> IRQ 21
HDA Intel 0000:00:10.1: setting latency timer to 64
HDA Intel 0000:00:10.1: PCI: Disallowing DAC for device
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00241b005af00f00]
b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm ‘pid’
Broadcom 43xx driver loaded Features: PMLR, Firmware-ID: FW13 ]
Adding 2104472k swap on /dev/sda1. Priority:-1 extents:1 across:2104472k
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
loop: module loaded
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
fuse init (API version 7.9)
type=1505 audit(1258374286.904:2): operation=“profile_load” name="/bin/ping" name2=“default” pid=2152
type=1505 audit(1258374286.948:3): operation=“profile_load” name="/sbin/klogd" name2=“default” pid=2153
type=1505 audit(1258374287.032:4): operation=“profile_load” name="/sbin/syslog-ng" name2=“default” pid=2154
type=1505 audit(1258374287.120:5): operation=“profile_load” name="/sbin/syslogd" name2=“default” pid=2155
type=1505 audit(1258374287.224:6): operation=“profile_load” name="/usr/sbin/avahi-daemon" name2=“default” pid=2156
usblp0: removed
type=1505 audit(1258374287.312:7): operation=“profile_load” name="/usr/sbin/identd" name2=“default” pid=2172
type=1505 audit(1258374287.396:8): operation=“profile_load” name="/usr/sbin/mdnsd" name2=“default” pid=2197
type=1505 audit(1258374287.492:9): operation=“profile_load” name="/usr/sbin/nscd" name2=“default” pid=2235
type=1505 audit(1258374287.672:10): operation=“profile_load” name="/usr/sbin/ntpd" name2=“default” pid=2254
type=1505 audit(1258374287.748:11): operation=“profile_load” name="/usr/sbin/traceroute" name2=“default” pid=2270
powernow-k8: Found 1 AMD Turion™ 64 X2 Mobile Technology TL-52 processors (2 cpu cores) (version 2.20.00)
powernow-k8: 0 : fid 0x8 (1600 MHz), vid 0x12
powernow-k8: 1 : fid 0x0 (800 MHz), vid 0x1e
Clocksource tsc unstable (delta = -99064795 ns)
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plase use
nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
NET: Registered protocol family 17
input: b43-phy0 as /devices/virtual/input/input10
firmware: requesting b43/ucode5.fw
firmware: requesting b43/pcm5.fw
eth0: no IPv6 routers present
firmware: requesting b43/b0g0initvals5.fw
firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
b43-phy0: Radio hardware status changed to DISABLED
b43-phy0: Radio turned on by software
b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.
Bluetooth: Core ver 2.13
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
On 11/16/2009 06:46 AM, zero1976 wrote:
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> b43-phy0: Radio hardware status changed to DISABLED
> b43-phy0: Radio turned on by software
> b43-phy0: The hardware RF-kill button still turns the radio physically
> off. Press the button to turn it on.
Could you please read this??? It clearly states that your radio is turned OFF
by a RADIO KILL switch. If you look around your machine, you will find one -
turn it on!
Yes I see it now but can not find where or how to turn it on. Was in the network settings and try a bunch of thing nothing. Can the wifi onbaord card be bad??
Thanks again
I have a dv9000z, with a similar problem.
My switch is ON - it’s the slide switch immediately to the right (and below) the 3 LEDs on the left front lip of the dv9000. My slide switch’s LED is on, glowing BLUE, to indicate that the Broadcom’s firmware has indeed been loaded.
When I “upgraded” from openSUSE 11.1 to 11.2 (doing a “rolling upgrade” over the 'net), my wireless stuff was extinguished. I notice now, in /var/log/messages, immediately below the b43 firmware loading messages:
ADDR_CONF(NETDEV_UP): wlan0: link not ready
I’ve read in other fora that Fedora and Ubuntu seem to be having similar problems, supposedly related to the (enabling of support for the) rfkill switch in recent kernels. There is a kernel module ‘rfkill’ that’s being loaded in concert with ‘cfg80211’, and trying to suppress it with “rfkill=0” as an argument to the kernel in /boot/grub/menu.lst appears to have no effect.
Others have suggested inserting in /etc/modprobe.conf, which is a bit difficult since it no longer exists in openSUSE 11.{1|2}. I suspect that it might be possible to tweak something in /etc/modprobe.d but it’s unclear to me what would be the optimal approach.
So, I’m open to suggestions or, preferably, a pointer to a Release Note or Bugzilla entry. (I saw your comments above after I made some comments in the thread “opensuse 11.2 and knetworkmanager”).
Well, I got it working.
Continued digging through various other threads gleaned BZ 550907 and 550908, and the discussion indicated that I needed to click on the NetworkManager icon -> Manage Connections -> Network Connections -> highlight my connection -> edit -> IP Address -> box in lower right corner (Basic Settings by default) -> Routes. Then UNCHECK both “Ignore automatically obtained routes” AND “Use only for resourced on this connection”. Then click on “OK” and then “Apply” and "OK on the Network Connections page.
Then, it’s recommended that you reboot (my personal preference, since it’s on my laptop) or at least restart the network and logout/login.