Re: Another strange thing with the driver
On Friday 02 February 2007 00:48, Rafael J. Wysocki wrote: BTW, can anyone please point me to a file containing the firmware that's known to work with the 4311 and can be extracted by fwcutter? http://bu3sch.de/bcm43xx_fw.php -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Another strange thing with the driver
On Thu, Feb 01, 2007 at 12:46:17PM -0800, Igor Korot wrote: Hi, guys, I just did a little test yesterday, and today. The problem below occur when on the dual-boot laptop, you boot Windows first, suspend it to disk, then boot Linux. I have a Dell Inspiron E1505 with WinXP and Gentoo installed. And this is exactly what happened. If you then re-boot Linux (Gentoo, in my case), and will try to bring the interface up, it will run without any problems. I don't know what is happenning after hibernating the XP, and booting Linux, and why the interface is up after re-booting Linux, but that the story behind this problem. Probably you are using different firmware versions under windows and linux ([EMAIL PROTECTED] and [EMAIL PROTECTED]). It could be a problem of already uploaded v4 firmware that will not work with the v3 linux driver or vice versa. Martin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Another strange thing with the driver
Igor Korot wrote:
Hi, guys,
I just did a little test yesterday, and today.
The problem below occur when on the dual-boot laptop, you boot Windows first,
suspend it to disk, then boot Linux.
I have a Dell Inspiron E1505 with WinXP and Gentoo installed.
And this is exactly what happened.
If you then re-boot Linux (Gentoo, in my case), and will try to bring the
interface up, it will run without any problems.
I don't know what is happenning after hibernating the XP, and booting Linux,
and why the interface is up after re-booting Linux, but that the story behind
this problem.
Larry, will Kismet out help to track this one as well?
It might. I'm not sure what is happening. At least you will know if the
interface is broadcasting.
Thank you.
Hi, Larry,
I found another strange thing with the driver.
I was able to successfully establish the connection using wireless tools.
I just installed wpa_supplicant, and here is what happened:
IgorsGentooOnNetwork igor # ifconfig eth1 up
SIOCSIFFLAGS: Protocol error
Looking at dmesg, I found that the problem is in the firmware:
bcm43xx: PHY connected
bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27)
bcm43xx: InitVals (bcm43xx_initvalXX.fw) file-format error. Please fix your
bcm43xx firmware files.
bcm43xx: core_up for active 802.11 core failed (-71)
Here is my /etc/conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
#Wireless-tools
#nis_domain_lo=IgorsGentoo
#modules=(iwconfig)
#key_ESSID1=[1] s:IgorsNetwork key [1] enc open
#key_ESSID2=[1] ---dd key [1] enc estricted
#preferred_aps=(ESSID1 ESSID2)
#Wpa_supplicant
modules=( wpa_supplicant )
wpa_supplicant_eth1=-Dbcm43xx
Here is my /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
network={
ssid=IgorsNetwork
psk=abcdef
priority=5
}
Do I need to re-install the firmware going from wireless tools to
wpa_supplicant?
Not usually. It looks as if your firmware got corrupted.
Larry
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Another strange thing with the driver
On Thursday, 1 February 2007 22:56, Larry Finger wrote:
Igor Korot wrote:
Hi, guys,
I just did a little test yesterday, and today.
The problem below occur when on the dual-boot laptop, you boot Windows
first, suspend it to disk, then boot Linux.
I have a Dell Inspiron E1505 with WinXP and Gentoo installed.
And this is exactly what happened.
If you then re-boot Linux (Gentoo, in my case), and will try to bring the
interface up, it will run without any problems.
I don't know what is happenning after hibernating the XP, and booting
Linux, and why the interface is up after re-booting Linux, but that the
story behind this problem.
Larry, will Kismet out help to track this one as well?
It might. I'm not sure what is happening. At least you will know if the
interface is broadcasting.
Thank you.
Hi, Larry,
I found another strange thing with the driver.
I was able to successfully establish the connection using wireless tools.
I just installed wpa_supplicant, and here is what happened:
IgorsGentooOnNetwork igor # ifconfig eth1 up
SIOCSIFFLAGS: Protocol error
Looking at dmesg, I found that the problem is in the firmware:
bcm43xx: PHY connected
bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27)
bcm43xx: InitVals (bcm43xx_initvalXX.fw) file-format error. Please fix your
bcm43xx firmware files.
bcm43xx: core_up for active 802.11 core failed (-71)
Here is my /etc/conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
#Wireless-tools
#nis_domain_lo=IgorsGentoo
#modules=(iwconfig)
#key_ESSID1=[1] s:IgorsNetwork key [1] enc open
#key_ESSID2=[1] ---dd key [1] enc estricted
#preferred_aps=(ESSID1 ESSID2)
#Wpa_supplicant
modules=( wpa_supplicant )
wpa_supplicant_eth1=-Dbcm43xx
Here is my /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
network={
ssid=IgorsNetwork
psk=abcdef
priority=5
}
Do I need to re-install the firmware going from wireless tools to
wpa_supplicant?
Not usually. It looks as if your firmware got corrupted.
BTW, can anyone please point me to a file containing the firmware that's
known to work with the 4311 and can be extracted by fwcutter?
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Another strange thing with the driver
On Monday 29 January 2007 10:10, Igor Korot wrote: bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) bcm43xx: InitVals (bcm43xx_initvalXX.fw) file-format error. Please fix your bcm43xx firmware files. Rather self-explaining, no? What do I have to say additionally to the dmesg log? -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Another strange thing with the driver
Igor Korot wrote:
Hi, Larry,
I found another strange thing with the driver.
I was able to successfully establish the connection using wireless tools.
I just installed wpa_supplicant, and here is what happened:
IgorsGentooOnNetwork igor # ifconfig eth1 up
SIOCSIFFLAGS: Protocol error
Looking at dmesg, I found that the problem is in the firmware:
bcm43xx: PHY connected
bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27)
bcm43xx: InitVals (bcm43xx_initvalXX.fw) file-format error. Please fix your
bcm43xx firmware files.
bcm43xx: core_up for active 802.11 core failed (-71)
Here is my /etc/conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
#Wireless-tools
#nis_domain_lo=IgorsGentoo
#modules=(iwconfig)
#key_ESSID1=[1] s:IgorsNetwork key [1] enc open
#key_ESSID2=[1] ---dd key [1] enc estricted
#preferred_aps=(ESSID1 ESSID2)
#Wpa_supplicant
modules=( wpa_supplicant )
wpa_supplicant_eth1=-Dbcm43xx
Here is my /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
network={
ssid=IgorsNetwork
psk=abcdef
priority=5
}
Do I need to re-install the firmware going from wireless tools to
wpa_supplicant?
No. Changing the connection tools did not cause this problem. Your firmware got
corrupted by some
event, which is the reason you need to re-install the firmware. In any case,
the log message is clear.
Larry
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
