Hi folks,
The same happened with me upgrading from 2.6.22 to 2.6.24 via an upgrade
from Ubuntu Gutsy to Ubuntu Hardy. There is definitely a renaming thing
going on. I tried adding the ATTR clause like you suggested here and also
suggested to another poster if I recall correctly and it didn't work. They
recently pushed a brand spanking new kernel which I haven't tried. What
information would you need to exactly pinpoint the problem. It seems that a
number of people have been bitten by this. Cheers for your great work thus
far by the way.
All the best,
Anthony
On 2/7/08, Larry Finger <[EMAIL PROTECTED]> wrote:
>
> Marcelo Juchem wrote:
> > Hi,
> >
> > I have a HP Presario zv6015 laptop with Debian 4.0 installed
> (using
> > the official unstable repository). When running the kernel 2.6.23,
> > everything works fine, even the Broadcom 4306 wireless card (using
> > module bcm43xx shipped with the kernel and firmware ripped with
> > bcm43xx-fwcutter from official Debian unstable repository). But when I
> > boot with the new kernel 2.6.24, the wireless network stops working. I
> > tried everything found in
> > http://www.linuxwireless.org/en/users/Drivers/b43 and searched a lot
> > of solutions on the Internet, but had no success. Both modules b43 and
> > b43 legacy were tried. I think it is a firmware issue, since I had the
> > same problem with bcm43xx and it was solved when I changed the
> > firmware. I have the following firmware files (tried every version
> > listed below):
> > /lib/firmware/b43/*.fw - 4.x firmware extracted with b43-fwcutter
> > /lib/firmware/b43legacy/*.fw - 3.x firmware extracted with b43-fwcutter
> > /lib/firmware/*.fw - 3.x firmware extracted with bcm43xx-fwcutter
> > Any ideas? I don't have much free time available due to work and
> > college, but I have good C and C++ coding skills and am willing to
> > help.
> >
> > Thanks,
> >
> > Marcelo Juchem
> >
> > Following is the output of some commands and content of some config
> > files to help the diagnostic.
> > ----------------------------------------------
> >
> > using debian linux with kernel linux-image-2.6.24-1-686
> > updated as of 01/31/2008 from the official debian unstable repository
> >
> > firmware extracted to /lib/firmware/b43
> > broadcom-wl-4.80.53.0 - extracted with b43-fwcutter 009
> > broadcom-wl-4.150.10.5 - extracted with b43-fwcutter 010
> >
> > firmware extracted from these files, found at
> > http://www.linuxwireless.org/en/users/Drivers/b43:
> > broadcom-wl-4.80.53.0/kmod/wl_apsta_mimo.o
> > broadcom-wl-4.80.53.0/kmod/wl_apsta.o
> > broadcom-wl-4.150.10.5/driver/wl_apsta_mimo.o
> >
> > b43-fwcutter version 009: obtained from the official debian unstable
> > repository as of 01/31/2008
> > b43-fwcutter version 010: compiled from sources found at
> > http://www.bu3sch.de/b43/fwcutter/
> >
> > --- 'lspci' output - BEGIN ---
> > 03:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
> > Wireless LAN Controller (rev 03)
> > --- 'lspci' output - END ---
> >
> > --- /etc/network/interfaces - BEGIN ---
> > # I changed the ESSID, nickname and password to placeholders
> > iface lo inet loopback
> > auto lo
> >
> > iface eth1 inet dhcp
> > wireless-essid WiFiNetworkESSID
> > wireless-mode Managed
> > wireless-channel 6
> > wireless-nickname nickname
> > wireless-key open s:password
> > hostname nickname
> > auto eth1
> > --- /etc/network/interfaces - END ---
> >
> > --- 'dmesg' output - BEGIN ---
> > b43-phy1: Broadcom 4306 WLAN found
> > phy1: Selected rate control algorithm 'simple'
> > udev: renamed network interface wmaster0 to eth1
> > --- 'dmesg' output - END ---
> >
> > --- 'iwlist eth1 scan' output - BEGIN ---
> > eth1 Interface doesn't support scanning.
> > --- 'iwlist eth1 scan' output - END ---
> >
> > --- 'ifup' output - BEGIN ---
> > Error for wireless request "Set Mode" (8B06) :
> > SET failed on device eth1 ; Operation not supported.
> > Error for wireless request "Set Encode" (8B2A) :
> > SET failed on device eth1 ; Operation not supported.
> > Error for wireless request "Set Frequency" (8B04) :
> > SET failed on device eth1 ; Operation not supported.
> > Error for wireless request "Set ESSID" (8B1A) :
> > SET failed on device eth1 ; Operation not supported.
> > Internet Systems Consortium DHCP Client V3.1.0
> > Copyright 2004-2007 Internet Systems Consortium.
> > All rights reserved.
> > For info, please visit http://www.isc.org/sw/dhcp/
> >
> > eth1: unknown hardware address type 801
> > SIOCSIFFLAGS: Operation not supported
> > SIOCSIFFLAGS: Operation not supported
> > eth1: unknown hardware address type 801
> > Listening on LPF/eth1/
> > Sending on LPF/eth1/
> > Sending on Socket/fallback
> > receive_packet failed on eth1: Network is down
> > option_space_encapsulate: option space agent does not exist, but is
> configured.
> > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
> > send_packet: Network is down
> > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
> > send_packet: Network is down
> > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21
> > send_packet: Network is down
> > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
> > send_packet: Network is down
> > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
> > send_packet: Network is down
> > No DHCPOFFERS received.
> > No working leases in persistent database - sleeping.
> > --- 'ifup' output - END ---
>
>
> I think your renaming is messed up. If you had sent the output of
> iwconfig, I could tell for sure. I
> am betting that your /etc/udev/rules.d/70-persistent-net.rules needs a
> rule like
>
> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="XX:XX:XX:XX:XX:XX",
> ATTR{type}=="1", NAME="eth1"
>
> On your system, I think the ATTR clause is missing and your iwconfig list
> ends up with eth1 and
> wlan0-rename, rather than wmaster0 and eth1. The clue is that wmaster0 has
> type 801.
>
> Fix your udev rules, and it should work.
>
>
> Larry
>
>
> _______________________________________________
> Bcm43xx-dev mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
>
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
