I have a broadcom 4318 wireless chip. I read a lot of posts on this forum and installed the b43 driver, but I still have no wireless connection. So a new thread.
Can anybody help me with a suggestion what to do now? I can see a message “timed out” with dmesg, but I don’t know how to fix that.
Also I discovered in /var/log 2 files called NetworkManager-date (with date the actual date). The problem here is that these files are big: 770MB and 902MB. I cannot open them because they are just too big. But why are these files that big?
Thanks a lot!
André
Output of lspci:
06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Some parts out of dmesg (I hope the right ones…):
b43-phy0: Broadcom 4318 WLAN found
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded Features: PMLR, Firmware-ID: FW13 ]
(...)
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
input: b43-phy0 as /devices/virtual/input/input10
ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 17
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
NET: Registered protocol family 17
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:13:f7:2f:2e:a5
wlan0: authenticate with AP 00:13:f7:2f:2e:a5
wlan0: authenticate with AP 00:13:f7:2f:2e:a5
wlan0: authentication with AP 00:13:f7:2f:2e:a5 timed out
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
First, files being “too big” isn’t a problem in Linux… you just need
the right tools. First, try the following:
less /var/log/Networkmanager-date
When you get in there press the capital ‘G’ and it should take you to
the bottom. Page Up and Down will let you navigate (along with the
arrow keys) from there. ‘vi’ is the same so you can use that too.
You may find that the ‘date’ files are actually older files and there is
an original, but it’s hard to tell. If so, use the newer one. You may
also want to try renaming these if they are still growing so new files
can be created and written-to. Rename them and then restart your
network at least (in case a file handle is open to those boxes… this
may end up being an unnecessary step):
‘rcnetwork restart’ #as root
Good luck.
drek2 wrote:
| Hi all,
|
| I have a broadcom 4318 wireless chip. I read a lot of posts on this
| forum and installed the b43 driver, but I still have no wireless
| connection. So a new thread.
| Can anybody help me with a suggestion what to do now? I can see a
| message “timed out” with dmesg, but I don’t know how to fix that.
|
| Also I discovered in /var/log 2 files called NetworkManager-date (with
| date the actual date). The problem here is that these files are big:
| 770MB and 902MB. I cannot open them because they are just too big. But
| why are these files that big?
|
| Thanks a lot!
| André
|
| Output of lspci:
|
Ok, I can read those big files. But still no wireless.
Some output which may be helpful for you to help me :): (Please tell me if you need another output.)
laptop:/var/log # dmesg | grep b43
b43-phy0: Broadcom 4318 WLAN found
input: b43-phy0 as /devices/virtual/input/input10
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
Sorry for the large amount of code, but it also might be helpful: (I removed the words “laptop NetworkManager” in each line)
Jun 27 12:18:03: <info> starting...
Jun 27 12:18:03: <info> eth0: Device is fully-supported using driver '8139too'.
Jun 27 12:18:03: <info> Found new Ethernet device 'eth0'.
Jun 27 12:18:03: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_16_d4_69_aa_30
Jun 27 12:18:03: <info> wlan0: Device is fully-supported using driver 'b43-pci-bridge'.
Jun 27 12:18:03: <info> wlan0: driver supports SSID scans (scan_capa 0x01).
Jun 27 12:18:03: <info> Found new wireless (802.11) device 'wlan0'.
Jun 27 12:18:03: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_19_7d_07_53_0a
Jun 27 12:18:03: <info> Trying to start the supplicant...
Jun 27 12:18:03: <info> Trying to start the system settings daemon...
Jun 27 12:18:07: <info> (eth0): device state change: 1 -> 2
Jun 27 12:18:07: <info> (eth0): bringing up device.
Jun 27 12:18:07: <info> (eth0): preparing device.
Jun 27 12:18:07: <info> (eth0): deactivating device.
Jun 27 12:18:07: <info> (wlan0): device state change: 1 -> 2
Jun 27 12:18:07: <info> (wlan0): bringing up device.
Jun 27 12:18:09: <info> (wlan0): preparing device.
Jun 27 12:18:09: <info> (wlan0): deactivating device.
Jun 27 12:18:09: <info> (eth0): carrier now ON (device state 2)
Jun 27 12:18:09: <info> (eth0): device state change: 2 -> 3
Jun 27 12:18:09: <info> (wlan0): device state change: 2 -> 3
Jun 27 12:18:09: <info> Activation (eth0) starting connection 'System eth0'
Jun 27 12:18:09: <info> (eth0): device state change: 3 -> 4
Jun 27 12:18:09: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 27 12:18:09: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 27 12:18:09: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 27 12:18:09: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 27 12:18:09: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 27 12:18:09: <info> (eth0): device state change: 4 -> 5
Jun 27 12:18:09: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun 27 12:18:09: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 27 12:18:09: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 27 12:18:09: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 27 12:18:09: <info> (eth0): device state change: 5 -> 7
Jun 27 12:18:09: <info> Activation (eth0) Beginning DHCP transaction.
Jun 27 12:18:10: <info> dhclient started with pid 2276
Jun 27 12:18:10: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 27 12:18:10: <info> (wlan0): supplicant interface state change: 1 -> 2.
Jun 27 12:18:11: <info> DHCP: device eth0 state changed (null) -> preinit
Jun 27 12:18:17: <info> DHCP: device eth0 state changed preinit -> bound
Jun 27 12:18:17: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Jun 27 12:18:17: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Jun 27 12:18:17: <info> address 172.20.33.118
Jun 27 12:18:17: <info> netmask 255.255.252.0
Jun 27 12:18:17: <info> gateway 172.20.32.3
Jun 27 12:18:17: <info> nameserver '172.20.32.2'
Jun 27 12:18:17: <info> nameserver '172.20.32.2'
Jun 27 12:18:17: <info> domain name 'vhl.local'
Jun 27 12:18:17: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 27 12:18:17: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Jun 27 12:18:17: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jun 27 12:18:18: <WARN> nm_system_set_hostname(): nm_system_set_hostname(): gethostbyaddr failed, h_errno = 1
Jun 27 12:18:18: <info> (eth0): device state change: 7 -> 8
Jun 27 12:18:18: <info> Clearing nscd hosts cache.
Jun 27 12:18:18: <info> Policy set (eth0) as default device for routing and DNS.
Jun 27 12:18:18: <info> Activation (eth0) successful, device activated.
Jun 27 12:18:18: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 27 12:19:17: <info> (eth0): carrier now OFF (device state 8)
Jun 27 12:19:17: <info> (eth0): device state change: 8 -> 2
Jun 27 12:19:17: <info> (eth0): deactivating device.
Jun 27 12:19:17: <info> eth0: canceled DHCP transaction, dhclient pid 2276
Jun 27 12:19:17: <info> Clearing nscd hosts cache.
Jun 27 12:19:20: <info> (eth0): carrier now ON (device state 2)
Jun 27 12:19:20: <info> (eth0): device state change: 2 -> 3
Jun 27 12:19:20: <info> Activation (eth0) starting connection 'System eth0'
Jun 27 12:19:20: <info> (eth0): device state change: 3 -> 4
Jun 27 12:19:20: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 27 12:19:20: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 27 12:19:20: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 27 12:19:20: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 27 12:19:20: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 27 12:19:20: <info> (eth0): device state change: 4 -> 5
Jun 27 12:19:20: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun 27 12:19:20: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 27 12:19:20: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 27 12:19:20: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 27 12:19:20: <info> (eth0): device state change: 5 -> 7
Jun 27 12:19:20: <info> Activation (eth0) Beginning DHCP transaction.
Jun 27 12:19:20: <info> dhclient started with pid 3216
Jun 27 12:19:20: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 27 12:19:20: <info> DHCP: device eth0 state changed normal exit -> preinit
Jun 27 12:19:25: <info> DHCP: device eth0 state changed preinit -> bound
Jun 27 12:19:25: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Jun 27 12:19:25: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Jun 27 12:19:25: <info> address 172.20.33.118
Jun 27 12:19:25: <info> netmask 255.255.252.0
Jun 27 12:19:25: <info> gateway 172.20.32.3
Jun 27 12:19:25: <info> nameserver '172.20.32.2'
Jun 27 12:19:25: <info> nameserver '172.20.32.2'
Jun 27 12:19:25: <info> domain name 'vhl.local'
Jun 27 12:19:25: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 27 12:19:25: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Jun 27 12:19:25: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jun 27 12:19:26: <WARN> nm_system_set_hostname(): nm_system_set_hostname(): gethostbyaddr failed, h_errno = 1
Jun 27 12:19:26: <info> (eth0): device state change: 7 -> 8
Jun 27 12:19:26: <info> Clearing nscd hosts cache.
Jun 27 12:19:26: <info> Policy set (eth0) as default device for routing and DNS.
Jun 27 12:19:26: <info> Activation (eth0) successful, device activated.
Jun 27 12:19:26: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 27 12:43:24: <info> DHCP: device eth0 state changed bound -> renew
Jun 27 12:43:24: <info> address 172.20.33.118
Jun 27 12:43:24: <info> netmask 255.255.252.0
Jun 27 12:43:24: <info> gateway 172.20.32.3
Jun 27 12:43:24: <info> nameserver '172.20.32.2'
Jun 27 12:43:24: <info> nameserver '172.20.32.2'
Jun 27 12:43:24: <info> domain name 'vhl.local'
Jun 27 12:43:24: <info> Clearing nscd hosts cache.
Jun 27 12:43:25: <WARN> nm_system_set_hostname(): nm_system_set_hostname(): gethostbyaddr failed, h_errno = 1
Jun 27 12:43:25: <info> Clearing nscd hosts cache.
Jun 27 12:43:25: <info> Policy set (eth0) as default device for routing and DNS.
drek2 wrote:
> Ok, I can read those big files. But still no wireless.
> Some output which may be helpful for you to help me :): (Please tell me
> if you need another output.)
>
> Code:
> --------------------
> laptop:/var/log # dmesg | grep b43
> b43-phy0: Broadcom 4318 WLAN found
> input: b43-phy0 as /devices/virtual/input/input10
> 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
> --------------------
>
> Sorry for the large amount of code, but it also might be helpful: (I
> removed the words “laptop NetworkManager” in each line)
>
> Code:
> --------------------
>
> Jun 27 12:18:03: <info> starting…
> Jun 27 12:18:03: <info> eth0: Device is fully-supported using driver ‘8139too’.
> Jun 27 12:18:03: <info> Found new Ethernet device ‘eth0’.
> Jun 27 12:18:03: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_16_d4_69_aa_30
> Jun 27 12:18:03: <info> wlan0: Device is fully-supported using driver ‘b43-pci-bridge’.
> Jun 27 12:18:03: <info> wlan0: driver supports SSID scans (scan_capa 0x01).
> Jun 27 12:18:03: <info> Found new wireless (802.11) device ‘wlan0’.
> Jun 27 12:18:03: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_19_7d_07_53_0a
> Jun 27 12:18:03: <info> Trying to start the supplicant…
> Jun 27 12:18:03: <info> Trying to start the system settings daemon…
> Jun 27 12:18:07: <info> (eth0): device state change: 1 → 2
> Jun 27 12:18:07: <info> (eth0): bringing up device.
> Jun 27 12:18:07: <info> (eth0): preparing device.
> Jun 27 12:18:07: <info> (eth0): deactivating device.
> Jun 27 12:18:07: <info> (wlan0): device state change: 1 → 2
> Jun 27 12:18:07: <info> (wlan0): bringing up device.
> Jun 27 12:18:09: <info> (wlan0): preparing device.
> Jun 27 12:18:09: <info> (wlan0): deactivating device.
> Jun 27 12:18:09: <info> (eth0): carrier now ON (device state 2)
> Jun 27 12:18:09: <info> (eth0): device state change: 2 → 3
> Jun 27 12:18:09: <info> (wlan0): device state change: 2 → 3
> Jun 27 12:18:09: <info> Activation (eth0) starting connection ‘System eth0’
> Jun 27 12:18:09: <info> (eth0): device state change: 3 → 4
> Jun 27 12:18:09: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled…
> Jun 27 12:18:09: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started…
All the rest of the lines refer to your wired connection (eth0), which
is preferred over the wireless.
What is the output of ‘sudo /usr/sbin/iwlist wlan0 scan’? Do you see
your AP? Please post the output.
If the scan shows data, have you tried right-clicking on the panel
applet in the lower right-hand corner of the screen and selecting the
wireless? This assumes you are using KDE. I don’t know where the
applet is for Gnome.
I had a similar problem that was fixed after networkmanager update and creating a new wireless connection clicking on knetworkmanager.
It’s curious that dmesg tells me that hardware wireless key still enables and disables radio even if it’s enabled by software and I don’t that message in your output.
All the rest of the lines refer to your wired connection (eth0), which is preferred over the wireless.
What is the output of ‘sudo /usr/sbin/iwlist wlan0 scan’? Do you see your AP? Please post the output.
If the scan shows data, have you tried right-clicking on the panel applet in the lower right-hand corner of the screen and selecting the wireless? This assumes you are using KDE. I don’t know where the applet is for Gnome.
Larry
The wireless scan works, see below. I use KDE4, and left or right clicking (doesn’t matter which button) on the knetworkmanager icon I get the options menu (New connection, Deactivate connection, Configure notifications, Edit connections, Quit). There are no wireless connections shown. (But the scan says there are! How to use them?)
In openSUSE 10.3 I got the menu with right clicking and with left clicking a window with connection info and statistics.
I have knetworkmanager version 0.7r821737-0.1. The latest according to YaST.
Some extra notifications: when I start up knetworkmanager with my utp cable already connected, it shows a green earth icon and I have internet. When I remove the cable the icon becomes gray (of course no internet). When I reconnect the cable the icon looks like an utp connector (with internet).
Try setting your WIRED connection to ‘manual’ or ‘never’, when you want to use
your wireless-adapter. [If they are both enabled, it’s my experience that the
routing table won’t let you onto the Internet, as that’s an illegal configuration
when they’re both on the same sub-net.]
Network manager 7 is still very unintuitive. As far as I’m concerned, the devs had perfected network management in the previous version. Anyway, with NM7, I’m not able to use wifi if the ethernet cable is plugged in - doesn’t matter if it’s disabled or not.
To connect to wifi, disconnect your ethernet cable. Clicky the network manager icon > new connection > wlan0. Select the essid from the list and go through the steps. At the end, select connect and save to connect. Once the essid is saved, you’ll see it listed under the wlan section next time you need to connect.
man4open wrote:
> Hello All,
>
> I have a Broadcom bcm4328 with my Dell XPS1330, I’ve tried ndiswrapper
> and now b43 still can’t use my wireless.
>
> I greatly appreciate if someone can give me some tips on how to make my
> wireless functional in OpenSuse11.
You should have started a new thread. The one you hijacked is about
BCM4318 - the answers for BCM4328 are VERY different.
The short answer is that b43 does not work for a BCM4328. No 802.11n
devices have been reverse engineered. That work is in progress, but
nowhere near completion.
You might Google for the Broadcom hybrid driver and try it.