New Broadcom driver for recent 43xx wireless devices

Share your own howto's etc. Not for support questions!

Postby Typhoon » 2008-10-01 23:29

I have the same ssh problem with my Dell 1525. Any solutions would be gratefully received!!
Typhoon
Blue Mountains, Australia
Typhoon
 
Posts: 66
Joined: 2007-04-18 05:49
Location: Australia

Aha!

Postby superjoe30 » 2008-10-02 02:30

Solution:

It's this bug:
https://bugs.launchpad.net/ubuntu/+sour ... bug/259816

Someone suggested "force vlan_mode to off on initialization of device" and wrote this patch:
http://kernel.ubuntu.com/git?p=ubuntu/u ... 6df6eaa59f

I incorporated this patch into the drivers posted in the first post, compiled the kernel module, and insmodded them, and it completely fixed the problems.

I was experiencing the same rare but deadly kernel panics as Typhoon, and we'll see if this code change hopefully fixes that as well.
superjoe30
 
Posts: 12
Joined: 2008-10-01 23:03

Postby noname » 2008-10-02 18:17

Typhoon wrote:Hello noname.

I don't have a solution, but I notice two things that are quite different from the listings on my own machine.

In you lspci listing, The "Capabilities" says "<access denied>". On my machine, I get a very detailed listing of capabilities.

Second, it seems that your router is not broadcasting an ESSID. I have read elsewhere that connection can be flaky when the broadcast is turned off. And it adds little or nothing to security.

Suggestion: get hold of a live 32 bit distro and see if you get different results from the lspci listing.

Let us know how you go.


Typhoon, thanks for your attention. I had stopped trying to make it work and only after I read your comment I got back to work to try to figure out the problem.
Running the LiveCD ( I used knoppix 5.1.1 ) I got the information on the Capabilities information that was hidden on Debian until I couple of minutes ago (now it's available).
I reconfigurated the linksys router, removed all security and tried a lot of times, both wireless gnome tool and shell environment, 'til the moment the wireless started working.
I think the problem was due to ssb module, i'm not totally sure 'cause i've done so many changes.
I'll reboot the system now (and right after i'll configure the wireless security) and check if it will be still working. :)
noname
 
Posts: 8
Joined: 2008-08-16 14:45

Postby superjoe30 » 2008-10-03 12:22

I wrote a guide on how to fix this problem:

http://www.superjoesoftware.com/article ... n-wireless
superjoe30
 
Posts: 12
Joined: 2008-10-01 23:03

Postby Typhoon » 2008-10-04 20:51

I don't know what's gone wrong. Everything was working OK for me, but suddenly I get a kernel panic as soon as the Network Manager starts.

I can install by hand, and it works fine. As soon as I shut down and reboot, no joy. I followed the excellent instructios in superjoe30's guide. I get the same problem whether I use the "plain" Broadcom module or the patched one from superjoe30.

The only clue I see is this: when compiling the 'vanilla' module, I get the following warning:

WARNING: modpost: missing MODULE_LICENSE() in /home/alant/hybrid_wl/wl.o
see include/linux/module.h for more information.

I don't get the warning with the superjoe30 patch, but the problem persists.

Any help appreciated!
Typhoon
Blue Mountains, Australia
Typhoon
 
Posts: 66
Joined: 2007-04-18 05:49
Location: Australia

Postby superjoe30 » 2008-10-04 21:33

Typhoon, when you lspci | grep Network, which version of the broadcom hardware do you have?

I have 4310:

0b:00.0 Network controller: Broadcom Corporation BCM4310 USB Controller (rev 01)
superjoe30
 
Posts: 12
Joined: 2008-10-01 23:03

Postby Typhoon » 2008-10-04 23:47

Yep, BCM4310.

It was working OK, so I must have changed something. I did fool around a little with wpa_supplicant. Maybe I didn't get the /etc/network/interfaces file back the way it should be. Can you please post yours?
Typhoon
Blue Mountains, Australia
Typhoon
 
Posts: 66
Joined: 2007-04-18 05:49
Location: Australia

Postby superjoe30 » 2008-10-04 23:56

Here's mine. I didn't change anything, so this should just be the default one for debian.

http://eth.pastebin.com/f1e302f0e
superjoe30
 
Posts: 12
Joined: 2008-10-01 23:03

Postby Typhoon » 2008-10-05 00:35

OK, thanks. I did have an error, but it still hasn't fixed my problem. Looking in the log, I see this message:

Oct 5 11:23:05 chickie kernel: [ 104.167805] wl: module license 'MIXED/Proprietary' taints kernel.

I don't know what it means, but when I unplug the wired connection, the network manager tries to hook me to the wireless and everything freezes.

EDIT: Oh, well. I can start it by hand and it resumes OK after sleep or hibernate. I guess I can live with it. Strange though.
Typhoon
Blue Mountains, Australia
Typhoon
 
Posts: 66
Joined: 2007-04-18 05:49
Location: Australia

Postby superjoe30 » 2008-10-05 01:01

Weird, as soon as you posted that I started getting the exact same kernel panics. It seems that the problem only occurs when it loads up automatically. Before I logged into gdm, I pressed Ctrl+Alt+F1 and logged in, sudo rmmod wl, and then ctrl+alt+F7 and then logged into gdm. Then of course wireless doesn't work. So I opened up a terminal and sudo modprobe wl. Then keep checking that icon, and as soon as it starts to try to connect to your network, click that same network. For example, if it says "connecting to linksys" quick, click on the icon and from the list of networks click linksys. Then it should connect without a kernel panic. From that point, hibernate instead of shutting down.

It's a temporary fix, until someone patches it.
superjoe30
 
Posts: 12
Joined: 2008-10-01 23:03

Postby Typhoon » 2008-10-05 03:03

OK, I think the problem is the interaction between the wl module and the Network Manager. Here is a solution that has worked for me through several reboots.

Use the wpa_supplicant roaming capability. This allows the wireless connection to be made without the use of the Network Manager.

Setting up wpa_supplicant is described in another thread of this forum: viewtopic.php?t=27573

I had to use eth1 instead of wlan0, but otherwise the instructions worked well.
Typhoon
Blue Mountains, Australia
Typhoon
 
Posts: 66
Joined: 2007-04-18 05:49
Location: Australia

success :-)

Postby nadavkav » 2008-10-05 20:47

i installed the iw module with no problems compiling it.
it recognized my hardware and loaded successfully
i have tx2520ej + BCM4310 USB Controller (rev 01)

===
product: BCM4310 USB Controller [14E4:4315]
vendor: Broadcom Corporation [14E4]
bus info: pci@0000:08:00.0
logical name: wlan0
version: 01
serial: 00:21:00:34:08:ce
width: 64 bits
clock: 33MHz
capabilities:
Power Management,
Message Signalled Interrupts,
PCI Express,
bus mastering,
PCI capabilities listing,
ethernet,
Physical interface,
Wireless-LAN
configuration:
broadcast: yes
driver: wl
ip: 192.168.1.101
latency: 0
module: wl
multicast: yes
wireless: IEEE 802.11bg

===

but i could not connect to my access point (linksys) although i saw it
with "iwlist wlan0 scan" (i got very low signal)

i tried the "patch" that was suggested a few posts ago but got kernel panics :-(

===
Broadcom BCM4315 802.11 Wireless Controller 5.10.27.6
<3>RTNL: assertion failed at net/core/dev.c (1002)
[12943.508268] Pid: 29393, comm: modprobe Tainted: P 2.6.26-1-amd64 #1
[12943.508268]
[12943.508268] Call Trace:
[12943.508268] [<ffffffff803bc192>] dev_open+0x2a/0xa0
[12943.508268] [<ffffffffa04e1988>] :wl:dev_wlc_ioctl+0x54/0x9c
[12943.508268] [<ffffffff8022ad5c>] __wake_up+0x38/0x4f
[12943.508268] [<ffffffffa04cfcf1>] :wl:bcm_mkiovar+0x53/0x61
[12943.508268] [<ffffffffa04e27c4>] :wl:dev_wlc_intvar_set+0x43/0x4e
[12943.508268] [<ffffffffa04e493c>] :wl:wl_pci_probe+0x413/0x451
[12943.508268] [<ffffffff802ac5d2>] find_inode+0x28/0x6d
[12943.508268] [<ffffffff802ac489>] iput+0x27/0x60
[12943.508268] [<ffffffff802e24b9>] sysfs_addrm_finish+0x62/0x1ea
[12943.508268] [<ffffffff802e21b4>] sysfs_find_dirent+0x1b/0x2f
[12943.508268] [<ffffffff80328469>] pci_device_probe+0xa9/0xf8
[12943.508268] [<ffffffff80384bf4>] driver_probe_device+0xd0/0x14d
[12943.508268] [<ffffffff80384cb7>] __driver_attach+0x46/0x6d
[12943.508268] [<ffffffff80384c71>] __driver_attach+0x0/0x6d
[12943.508268] [<ffffffff80384397>] bus_for_each_dev+0x44/0x6f
[12943.508268] [<ffffffff803847cd>] bus_add_driver+0xb4/0x203
[12943.508268] [<ffffffff80384f13>] driver_register+0x8d/0x101
[12943.508268] [<ffffffff803286cd>] __pci_register_driver+0x47/0x7a
[12943.508268] [<ffffffff80254e9b>] sys_init_module+0x190e/0x1aa4
[12943.508268] [<ffffffff80295d65>] __kmalloc+0x0/0x130
[12943.508268] [<ffffffff80224d44>] cstar_do_call+0x1b/0x65
[12943.508268]
[12943.668322] RTNL: assertion failed at net/ipv6/addrconf.c (2297)
[12943.668322] Pid: 29393, comm: modprobe Tainted: P 2.6.26-1-amd64 #1
[12943.668322]
[12943.668322] Call Trace:
[12943.668322] [<ffffffffa03e4784>] :ipv6:addrconf_notify+0x63b/0x846
[12943.668322] [<ffffffff80364b30>] account+0xd9/0xe9
[12943.668322] [<ffffffff80364c8c>] extract_entropy+0x47/0x90
[12943.668322] [<ffffffff80400000>] add_grhead+0x8/0x83
[12943.668322] [<ffffffff803d5cee>] rt_cache_invalidate+0x13/0x26
[12943.668322] [<ffffffff804011b7>] ip_mc_up+0x45/0x50
[12943.668322] [<ffffffff803d5d39>] rt_cache_flush+0x11/0xe0
[12943.668322] [<ffffffff802496c8>] notifier_call_chain+0x29/0x4c
[12943.668322] [<ffffffff803bc204>] dev_open+0x9c/0xa0
[12943.668322] [<ffffffffa04e1988>] :wl:dev_wlc_ioctl+0x54/0x9c
[12943.668322] [<ffffffff8022ad5c>] __wake_up+0x38/0x4f
[12943.668322] [<ffffffffa04cfcf1>] :wl:bcm_mkiovar+0x53/0x61
[12943.668322] [<ffffffffa04e27c4>] :wl:dev_wlc_intvar_set+0x43/0x4e
[12943.668322] [<ffffffffa04e493c>] :wl:wl_pci_probe+0x413/0x451
[12943.668322] [<ffffffff802ac5d2>] find_inode+0x28/0x6d
[12943.668322] [<ffffffff802ac489>] iput+0x27/0x60
[12943.668322] [<ffffffff802e24b9>] sysfs_addrm_finish+0x62/0x1ea
[12943.668322] [<ffffffff802e21b4>] sysfs_find_dirent+0x1b/0x2f
[12943.668322] [<ffffffff80328469>] pci_device_probe+0xa9/0xf8
[12943.668322] [<ffffffff80384bf4>] driver_probe_device+0xd0/0x14d
[12943.668322] [<ffffffff80384cb7>] __driver_attach+0x46/0x6d
[12943.668322] [<ffffffff80384c71>] __driver_attach+0x0/0x6d
[12943.668322] [<ffffffff80384397>] bus_for_each_dev+0x44/0x6f
[12943.668322] [<ffffffff803847cd>] bus_add_driver+0xb4/0x203
[12943.668322] [<ffffffff80384f13>] driver_register+0x8d/0x101
[12943.668322] [<ffffffff803286cd>] __pci_register_driver+0x47/0x7a
[12943.668322] [<ffffffff80254e9b>] sys_init_module+0x190e/0x1aa4
[12943.668322] [<ffffffff80295d65>] __kmalloc+0x0/0x130
[12943.668322] [<ffffffff80224d44>] cstar_do_call+0x1b/0x65
[12943.668322]
[12943.668322] RTNL: assertion failed at net/ipv6/addrconf.c (1710)
[12943.668322] Pid: 29393, comm: modprobe Tainted: P 2.6.26-1-amd64 #1
[12943.668322]
[12943.668322] Call Trace:
[12943.668322] [<ffffffff8020e428>] dump_stack+0x69/0x6f
[12943.668322] [<ffffffffa03e39aa>] :ipv6:addrconf_add_dev+0x2f/0x56
[12943.668322] [<ffffffffa03e47b2>] :ipv6:addrconf_notify+0x669/0x846
[12943.668322] [<ffffffff80364b30>] account+0xd9/0xe9
[12943.668322] [<ffffffff80364c8c>] extract_entropy+0x47/0x90
[12943.668322] [<ffffffff80400000>] add_grhead+0x8/0x83
[12943.668322] [<ffffffff803d5cee>] rt_cache_invalidate+0x13/0x26
[12943.668322] [<ffffffff804011b7>] ip_mc_up+0x45/0x50
[12943.668322] [<ffffffff803d5d39>] rt_cache_flush+0x11/0xe0
[12943.668322] [<ffffffff802496c8>] notifier_call_chain+0x29/0x4c
[12943.668322] [<ffffffff803bc204>] dev_open+0x9c/0xa0
[12943.668322] [<ffffffffa04e1988>] :wl:dev_wlc_ioctl+0x54/0x9c
[12943.668322] [<ffffffff8022ad5c>] __wake_up+0x38/0x4f
[12943.668322] [<ffffffffa04cfcf1>] :wl:bcm_mkiovar+0x53/0x61
[12943.668322] [<ffffffffa04e27c4>] :wl:dev_wlc_intvar_set+0x43/0x4e
[12943.668322] [<ffffffffa04e493c>] :wl:wl_pci_probe+0x413/0x451
[12943.668322] [<ffffffff802ac5d2>] find_inode+0x28/0x6d
[12943.668322] [<ffffffff802ac489>] iput+0x27/0x60
[12943.668322] [<ffffffff802e24b9>] sysfs_addrm_finish+0x62/0x1ea
[12943.668322] [<ffffffff802e21b4>] sysfs_find_dirent+0x1b/0x2f
[12943.668322] [<ffffffff80328469>] pci_device_probe+0xa9/0xf8
[12943.668322] [<ffffffff80384bf4>] driver_probe_device+0xd0/0x14d
[12943.668322] [<ffffffff80384cb7>] __driver_attach+0x46/0x6d
[12943.668322] [<ffffffff80384c71>] __driver_attach+0x0/0x6d
[12943.668322] [<ffffffff80384397>] bus_for_each_dev+0x44/0x6f
[12943.668322] [<ffffffff803847cd>] bus_add_driver+0xb4/0x203
[12943.668322] [<ffffffff80384f13>] driver_register+0x8d/0x101
[12943.668322] [<ffffffff803286cd>] __pci_register_driver+0x47/0x7a
[12943.668322] [<ffffffff80254e9b>] sys_init_module+0x190e/0x1aa4
[12943.668322] [<ffffffff80295d65>] __kmalloc+0x0/0x130
[12943.668322] [<ffffffff80224d44>] cstar_do_call+0x1b/0x65
[12943.668322]
[12943.668322] RTNL: assertion failed at net/ipv6/addrconf.c (420)
[12943.668322] Pid: 29393, comm: modprobe Tainted: P 2.6.26-1-amd64 #1
[12943.668322]
[12943.668322] Call Trace:
[12943.668322] [<ffffffff8020e428>] dump_stack+0x69/0x6f
[12943.668322] [<ffffffffa03e3944>] :ipv6:ipv6_find_idev+0x2f/0x66
[12943.668322] [<ffffffffa03e39b2>] :ipv6:addrconf_add_dev+0x37/0x56
[12943.668322] [<ffffffffa03e47b2>] :ipv6:addrconf_notify+0x669/0x846
[12943.668322] [<ffffffff80364b30>] account+0xd9/0xe9
[12943.668322] [<ffffffff80364c8c>] extract_entropy+0x47/0x90
[12943.668322] [<ffffffff80400000>] add_grhead+0x8/0x83
[12943.668322] [<ffffffff803d5cee>] rt_cache_invalidate+0x13/0x26
[12943.668322] [<ffffffff804011b7>] ip_mc_up+0x45/0x50
[12943.668322] [<ffffffff803d5d39>] rt_cache_flush+0x11/0xe0
[12943.668322] [<ffffffff802496c8>] notifier_call_chain+0x29/0x4c
[12943.668322] [<ffffffff803bc204>] dev_open+0x9c/0xa0
[12943.668322] [<ffffffffa04e1988>] :wl:dev_wlc_ioctl+0x54/0x9c
[12943.668322] [<ffffffff8022ad5c>] __wake_up+0x38/0x4f
[12943.668322] [<ffffffffa04cfcf1>] :wl:bcm_mkiovar+0x53/0x61
[12943.668322] [<ffffffffa04e27c4>] :wl:dev_wlc_intvar_set+0x43/0x4e
[12943.668322] [<ffffffffa04e493c>] :wl:wl_pci_probe+0x413/0x451
[12943.668322] [<ffffffff802ac5d2>] find_inode+0x28/0x6d
[12943.668322] [<ffffffff802ac489>] iput+0x27/0x60
[12943.668322] [<ffffffff802e24b9>] sysfs_addrm_finish+0x62/0x1ea
[12943.668322] [<ffffffff802e21b4>] sysfs_find_dirent+0x1b/0x2f
[12943.668322] [<ffffffff80328469>] pci_device_probe+0xa9/0xf8
[12943.668322] [<ffffffff80384bf4>] driver_probe_device+0xd0/0x14d
[12943.668322] [<ffffffff80384cb7>] __driver_attach+0x46/0x6d
[12943.668322] [<ffffffff80384c71>] __driver_attach+0x0/0x6d
[12943.668322] [<ffffffff80384397>] bus_for_each_dev+0x44/0x6f
[12943.668322] [<ffffffff803847cd>] bus_add_driver+0xb4/0x203
[12943.668322] [<ffffffff80384f13>] driver_register+0x8d/0x101
[12943.668322] [<ffffffff803286cd>] __pci_register_driver+0x47/0x7a
[12943.668322] [<ffffffff80254e9b>] sys_init_module+0x190e/0x1aa4
[12943.668322] [<ffffffff80295d65>] __kmalloc+0x0/0x130
[12943.668322] [<ffffffff80224d44>] cstar_do_call+0x1b/0x65
[12943.668322]

===

i revert to the original wl sources

and changed my /etc/network/interfaces to

Code: Select all
allow-hotplug wlan0
iface wlan0 inet dhcp
wireless-mode managed
wireless-essid home


and now it works fine :-)

thank you everyone !!!
nadavkav
 
Posts: 7
Joined: 2008-10-05 20:35
Location: Israel

Postby Typhoon » 2008-10-05 23:28

I think that using the "wireless" commands in the /etc/network/interfaces file means that Network Manager is no longer used. Not sure about this, but if so, then it is similar to my solution above.

The kernel panic messages that you show are the same that I had when Network Manager tried to start.
Typhoon
Blue Mountains, Australia
Typhoon
 
Posts: 66
Joined: 2007-04-18 05:49
Location: Australia

Postby superjoe30 » 2008-10-06 03:06

nadavkav, can you use ssh, ftp, and telnet from a terminal?
superjoe30
 
Posts: 12
Joined: 2008-10-01 23:03

Postby nadavkav » 2008-10-06 07:48

i do not use NetworkManager

and i get only the welcome message when i use ftp from the console
funny ! since i use KDE and it works fine from konqueror or krusader

i saw wireshark logging FTP over TCP retransmit messages
sending USER ftp command and the server replys with welcome message

you think it is related or some issue with cli ftp ?
nadavkav
 
Posts: 7
Joined: 2008-10-05 20:35
Location: Israel

PreviousNext

Return to Docs, Howtos, Tips & Tricks

Who is online

Users browsing this forum: No registered users and 2 guests

fashionable