Firmware loading problem
Hello Folks,
First of all, sorry to bother you with that users-question, but the forum is
down for at least one week now...
I have a problem with my bcm4311 card.
As far as I read, it is now (2.6.21) fully compatible with the driver you
write.
I'm using Gentoo x86_64 and have set up the card using your docs. I also
downloaded the firmware and used fwcutter to put it into /lib/firmware
and /lib64/firmware. These directories are correct, as I have a TV card,
also, which loads its firmware from that directory.
But the bcm43xx module does not load any firmware and the card is not
correctly set up.
[EMAIL PROTECTED] ~ $ /usr/sbin/lspci -n | grep 43
03:00.0 0280: 14e4:4311 (rev 01)
[EMAIL PROTECTED] ~ $ /usr/sbin/lspci | grep 03:00
03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI
(rev 01)
[EMAIL PROTECTED] ~ $
I use the firmware in 80211g.zip (BCMWL564.SYS) which is for 64bit, but I also
tried SP23107.exe (bcmwl5.sys) as source file. I hope this is correct.
What am I doing wrong? I will attach the trace of 'modprobe bcm43xx'.
Thanks in advance!
--
MfG Jan
execve(/sbin/modprobe, [modprobe, bcm43xx], [/* 44 vars */]) = 0
brk(0) = 0x508000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab1aec4f000
uname({sys=Linux, node=kohni-mobil, ...}) = 0
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=154579, ...}) = 0
mmap(NULL, 154579, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2ab1aec5
close(3)= 0
open(/lib/libz.so.1, O_RDONLY)= 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0 \35\0\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=89696, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab1aec76000
mmap(NULL, 1135880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab1aed51000
mprotect(0x2ab1aed66000, 1048576, PROT_NONE) = 0
mmap(0x2ab1aee66000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x15000) = 0x2ab1aee66000
close(3)= 0
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0p\324\1\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1314928, ...}) = 0
mmap(NULL, 2334920, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2ab1aee67000
mprotect(0x2ab1aef99000, 1044480, PROT_NONE) = 0
mmap(0x2ab1af098000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x131000) = 0x2ab1af098000
mmap(0x2ab1af09d000, 16584, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2ab1af09d000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab1af0a2000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab1af0a3000
arch_prctl(ARCH_SET_FS, 0x2ab1af0a2ae0) = 0
mprotect(0x2ab1af098000, 12288, PROT_READ) = 0
mprotect(0x2ab1aed4f000, 4096, PROT_READ) = 0
munmap(0x2ab1aec5, 154579) = 0
create_module(NULL, 0) = -1 ENOSYS (Function not implemented)
uname({sys=Linux, node=kohni-mobil, ...}) = 0
fstat(2, {st_mode=S_IFCHR|0600, st_rdev=makedev(4, 1), ...}) = 0
brk(0) = 0x508000
brk(0x529000) = 0x529000
open(/etc/modprobe.conf, O_RDONLY|O_NONBLOCK|O_DIRECTORY) = -1 ENOTDIR (Not a
directory)
open(/etc/modprobe.conf, O_RDONLY)= 3
fstat(3, {st_mode=S_IFREG|0644, st_size=5917, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab1aec5
read(3, ### This file is automatically g..., 4096) = 4096
read(3, unl0 ipip\nalias cipcb0 cipcb\nali..., 4096) = 1821
read(3, , 4096) = 0
close(3)= 0
munmap(0x2ab1aec5, 4096)= 0
open(/lib/modules/2.6.21-gentoo-r3/modules.dep, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=191416, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x2ab1aec5
read(3, /lib/modules/2.6.21-gentoo-r3/ke..., 4096) = 4096
read(3, l/net/ipv6/netfilter/ip6_tables, 4096) = 4096
read(3, lter/xt_string.ko: /lib/modules/..., 4096) = 4096
read(3, /net/netfilter/xt_NFQUEUE.ko: /l..., 4096) = 4096
read(3, el/net/ipx/ipx.ko: /lib/modules/..., 4096) = 4096
read(3, dules/2.6.21-gentoo-r3/kernel/ne..., 4096) = 4096
read(3, l/net/netfilter/nf_conntrack.ko ..., 4096) = 4096
read(3, ules/2.6.21-gentoo-r3/kernel/net..., 4096) = 4096
read(3, les/2.6.21-gentoo-r3/kernel/driv..., 4096) = 4096
read(3, drivers/media/dvb/frontends/cx24..., 4096) = 4096
read(3, .6.21-gentoo-r3/kernel/drivers/m..., 4096) = 4096
read(3, edia/dvb/frontends/bcm3510.ko /l..., 4096) = 4096
read(3, ia/dvb/frontends/lgdt330x.ko /li..., 4096) = 4096
read(3,
Re: Firmware loading problem
Jan Kohnert wrote: Hello Folks, First of all, sorry to bother you with that users-question, but the forum is down for at least one week now... I have a problem with my bcm4311 card. As far as I read, it is now (2.6.21) fully compatible with the driver you write. Yes, that is true. I'm using Gentoo x86_64 and have set up the card using your docs. I also downloaded the firmware and used fwcutter to put it into /lib/firmware and /lib64/firmware. These directories are correct, as I have a TV card, also, which loads its firmware from that directory. But the bcm43xx module does not load any firmware and the card is not correctly set up. There is no difference between the firmware in a 32- or 64-bit driver. The difference only matters when the original Windows or OS X driver is being used, as with ndiswrapper. There are, however, two different versions of the firmware. V3 is used with the softmac version of bcm43xx, which is the version you are using, and V4 is used with the mac80211 version. Please check the output of 'dmesg | grep bcm43xx'. I think it will say that your firmware is too new. You need to get a copy of a V3 driver and extract its firmware. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Firmware loading problem
Thanks for the quick response! Larry Finger schrieb: Jan Kohnert wrote: But the bcm43xx module does not load any firmware and the card is not correctly set up. There is no difference between the firmware in a 32- or 64-bit driver. The difference only matters when the original Windows or OS X driver is being used, as with ndiswrapper. There are, however, two different versions of the firmware. V3 is used with the softmac version of bcm43xx, which is the version you are using, and V4 is used with the mac80211 version. Please check the output of 'dmesg | grep bcm43xx'. I think it will say that your firmware is too new. You need to get a copy of a V3 driver and extract its firmware. Here is the output, but however, I cannot see, anything would be loaded... kohni-mobil ~ # dmesg | grep bcm43xx bcm43xx driver bcm43xx: Chip ID 0x4311, rev 0x1 bcm43xx: Number of cores: 4 bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243 bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243 bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 4, Type 2, Revision 8 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off kohni-mobil ~ # Anyway, I will try to find V3, download, test and report. Larry -- MfG Jan pgpSRXBUKkjOY.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Firmware loading problem
Jan Kohnert wrote: Thanks for the quick response! Here is the output, but however, I cannot see, anything would be loaded... kohni-mobil ~ # dmesg | grep bcm43xx bcm43xx driver bcm43xx: Chip ID 0x4311, rev 0x1 bcm43xx: Number of cores: 4 bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243 bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243 bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 4, Type 2, Revision 8 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off kohni-mobil ~ # Anyway, I will try to find V3, download, test and report. The set of messages from my interface are as follows: bcm43xx driver bcm43xx: Chip ID 0x4311, rev 0x1 bcm43xx: Number of cores: 4 bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243 bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243 bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 4, Type 2, Revision 8 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off bcm43xx: PHY connected bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) bcm43xx: Radio turned on bcm43xx: Radio enabled by hardware bcm43xx: Chip initialized You are missing the last 5 lines. Did you do an 'ifup eth1', or the equivalent? Those lines are generated after the interface is brought up. If it had tried to load V4 firmware, there would have been a different message. One other thing to check - if you do an 'lsmod | grep firmware' command, do you see 'firmware_class'? Perhaps your system is not autoloading the firmware, but I think that also generates an error. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Firmware loading problem [SOLVED]
Larry Finger schrieb: You are missing the last 5 lines. Did you do an 'ifup eth1', or the equivalent? Those lines are generated after the interface is brought up. Doh! I did not. Now it reads: bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) bcm43xx: Radio turned on bcm43xx: Radio disabled by hardware bcm43xx: Chip initialized bcm43xx: 32-bit DMA initialized bcm43xx: Keys cleared bcm43xx: Selected 802.11 core (phytype 2) bcm43xx: Radio hardware status changed to enabled It works! After all I think, the main problem was, that I did not install the firmware to /lib64/firmware, when I tried first (at that time, I also tried to bring the interface up, which failed), and after that I never tried to bring the interface up again... Sorry for the noise and much thanks for your patient help. Larry -- MfG Jan pgpy72A1qHVtx.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
BCM4309 with bcm43xx-mac80211 and WPA
hi, does bcm43xx-mac80211 support WPA for the BCM4309 chipset ? It seems that the driver detects and initialised the card, but I can't connect to my router. I'm using NetworkManager and it does see my router, but doesn't connect to it. Not to mention that after a while the driver causes a system freeze. I'm using WPA PSK-TKIP I've also tried with the bcm43xx (and a V3 firmware), but that doesn't seem to recognise the card at all. 'dmesg' reports only this: ieee80211_crypt: unregistered algorithm 'NULL' ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] bcm43xx driver and I don't get an interface associated to the card. thanks -Ioannis ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Ioannis Nousias wrote: hi, does bcm43xx-mac80211 support WPA for the BCM4309 chipset ? It seems that the driver detects and initialised the card, but I can't connect to my router. I'm using NetworkManager and it does see my router, but doesn't connect to it. Not to mention that after a while the driver causes a system freeze. I'm using WPA PSK-TKIP Yes, bcm43xx-mac80211 supports WPA. I don't know about the system freeze, but most problems in associating and authenticating with mac80211 are due to low signal strengths. The driver is improving, but still has problems. I've also tried with the bcm43xx (and a V3 firmware), but that doesn't seem to recognise the card at all. 'dmesg' reports only this: ieee80211_crypt: unregistered algorithm 'NULL' ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] I do not think that you selected IEEE802.11i TKIP encryption under the Generic IEEE802.11 stack when you configured your system. The message here is ieee80211_crypt: registered algorithm 'TKIP'. I am assuming that wpa_supplicant is available and started by NetworkManager. That is what happens on my system. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Larry Finger wrote: Ioannis Nousias wrote: hi, does bcm43xx-mac80211 support WPA for the BCM4309 chipset ? It seems that the driver detects and initialised the card, but I can't connect to my router. I'm using NetworkManager and it does see my router, but doesn't connect to it. Not to mention that after a while the driver causes a system freeze. I'm using WPA PSK-TKIP Yes, bcm43xx-mac80211 supports WPA. I don't know about the system freeze, but most problems in associating and authenticating with mac80211 are due to low signal strengths. The driver is improving, but still has problems. ok I see. I do get transmission errors (PHY). I've also tried with the bcm43xx (and a V3 firmware), but that doesn't seem to recognise the card at all. 'dmesg' reports only this: ieee80211_crypt: unregistered algorithm 'NULL' ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] I do not think that you selected IEEE802.11i TKIP encryption under the Generic IEEE802.11 stack when you configured your system. The message here is ieee80211_crypt: registered algorithm 'TKIP'. I am assuming that wpa_supplicant is available and started by NetworkManager. That is what happens on my system. Larry in the bcm43xx case, NetworkManager doesn't detect a wireless card at all. Its menu shows only 'Wired Network'. As I said, the card doesn't seem to be recognised. I was thinking to compile the latest version, but if I'm not mistaken, this: 'git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git' is the entire kernel source. Can I compile somehow the bcm43xx or bcm43xx-mac80211 only for my current kernel ? thanks ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Ioannis Nousias wrote: in the bcm43xx case, NetworkManager doesn't detect a wireless card at all. Its menu shows only 'Wired Network'. As I said, the card doesn't seem to be recognised. What is the result of the command 'dmesg | grep bcm43xx'? I was thinking to compile the latest version, but if I'm not mistaken, this: 'git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git' is the entire kernel source. Can I compile somehow the bcm43xx or bcm43xx-mac80211 only for my current kernel ? Yes, that is the complete source. What is your current kernel? Do you have kernel sources on your machine? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Larry Finger wrote: Ioannis Nousias wrote: in the bcm43xx case, NetworkManager doesn't detect a wireless card at all. Its menu shows only 'Wired Network'. As I said, the card doesn't seem to be recognised. What is the result of the command 'dmesg | grep bcm43xx'? bcm43xx driver nothing else I was thinking to compile the latest version, but if I'm not mistaken, this: 'git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git' is the entire kernel source. Can I compile somehow the bcm43xx or bcm43xx-mac80211 only for my current kernel ? Yes, that is the complete source. What is your current kernel? Do you have kernel sources on your machine? Larry I'm using 2.6.21-1.3228.fc7 (that's Fedora 7) and I only heave the development package for my kernel, which is not a complete kernel source, but is enough to compile some kernel modules against it (I've tried with uvc-linux for instance) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
