Gusty updates broke my wireless connectivity

No. It does not need improvement, it needs to be re-fixed! It has become
broken during an update. As my post said, it did not work out-of-the-box on
Feisty. It did, however, work on Gusty, Tribe 3, before the 3rd of Aug.

Thanx for the hard work. I am getting pretty happy about an Ubuntu desktop.

zeddock

On 8/7/07, Brian Murray <email address hidden> wrote:
>
> ** Tags added: needs-improvement
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

tried to nominate for gusty but it was not listed.

zeddock.

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Additionally, it is not quite clear to me where the bug lies. Is it that your wireless connection is not called wlan0 or that you are unable to connect to a wireless network? Thanks in advance!

uname -a
Linux Lat-Lap 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686
GNU/Linux

dmesg.log attached

lspci-vvnn.log attached

Where s the problem?
When I first tried Gusty Tribe 3 wireless worked. I could both, connect to
the internet without a patch cable connected to my laptop, and I could
single-left-click on the network manager icon in the notification area of
the top panel. Once clicked, it showed several wireless networks which were
available.

Since wireless had been a problem in Feisty I quickly looked at the
interfaces file and found wlan0 and wlan was shown correctly in the
network-manager application and if I did a iwconfig.

Now, there are no wireless networks show in the network manager icon in the
notification area...
iwconfig reports wireless on eth3 with a nickname of broadcom 4306
and I cannot connect if the cable is disconnected.

So... the problem is both!<smile>
I really think that the wlan0 versus eth3 is part of the problem.

Wish I could go back to that wonderful time when it started working. But
alas, I do not know how.

Thanx for working this.

zeddock

PS. Just looked into those files. Wow! You know what all that means?!

On 8/8/07, Brian Murray <email address hidden> wrote:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
> Please include as attachments the following additional information, if you
> have not already done so (please pay attention to lspci's additional
> options), as required by the Ubuntu Kernel Team:
> 1. Please include the output of the command 'uname -a' in your next
> response. It should be one, long line of text which includes the exact
> kernel version you're running, as well as the CPU architecture.
> 2. Please run the command 'dmesg > dmesg.log' and attach the resulting
> file 'dmesg.log' to this bug report.
> 3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach
> the resulting file 'lspci-vvnn.log' to this bug report.
> For your reference, the full description of procedures for kernel-related
> bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies. Additionally, it is not quite clear to me where the bug lies. Is it that
> your wireless connection is not called wlan0 or that you are unable to
> connect to a wireless network? Thanks in advance!
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Sourcepackagename: None => linux-source-2.6.22
> Assignee: (unassigned) => Brian Murray
> Status: New => Incomplete
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Unfortunately, Malone's e-mail interface, does not accept attachments via e-mail at this point in time so if you could please visit your bug's web page and attach them manually that would be great. Additionally, if you could add your '/etc/network/interfaces' file too that would be helpful. Thanks again!

Here are the attachments...

I found this in your log files:

[ 27.432000] bcm43xx: Error: Microcode "bcm43xx_microcode4.fw" not available or load failed.

Do you know if you are using ndiswrapper or the broadcom driver on your laptop? Do you still have the bcm43xx-fwcutter package installed? How do you go about updating your system? Thanks again!

I update my system by clicking on System/Administration/Update Manager.
My sources have been changed for some things, I do very few things through the commandline. Not that I don't like it, just that my users will not be able to so I had better find a guweeee way or plan on doing the work myself!

BTW, here is my interfaces file, also my networks and iftab files.

========
auto lo
iface lo inet loopback

iface eth0 inet static
address 128.183.80.234
netmask 255.255.254.0
gateway 128.183.80.1

auto eth0

iface wlan0 inet static
address 192.168.0.122
netmask 255.255.255.0
gateway 192.168.0.1
wireless-essid Dlink

auto wlan0

iface eth2 inet static
address 128.183.80.234
netmask 255.255.254.0
gateway 128.183.80.1

auto eth2
==========
networks file:
==========
# symbolic names for networks, see networks(5) for more information
link-local 169.254.0.0
==========
iftab:
==========
# This file assigns persistent names to network interfaces.
# See iftab(5) for syntax.

eth0 mac 00:0d:56:ec:bc:24 arp 1
wlan0 mac 00:90:4b:1a:17:41 arp 1
==========

zeddock

Maybe I have messed up Source information? What should they be. How should
I check?

jim

On 8/10/07, Brian Murray <email address hidden> wrote:
>
> I found this in your log files:
>
> [ 27.432000] bcm43xx: Error: Microcode "bcm43xx_microcode4.fw" not
> available or load failed.
>
> Do you know if you are using ndiswrapper or the broadcom driver on your
> laptop? Do you still have the bcm43xx-fwcutter package installed? How
> do you go about updating your system? Thanks again!
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

In Gutsy '/etc/iftab' has been deprecated in favor of '/etc/udev/rules.d/70-persistent-net.rules' so perhaps that is causing an issue. Could you migrate your settings from your '/etc/iftab' to /etc/udev/rules.d/70-persistent-net.rules' and report back? Thanks again.

If I knew what that meant I would feel much better about myself. :|

Honestly, If you give me steps I can comply, Until I hear differently, I will do this:
sudo gedit /etc/iftab
(Select all and CUT)
Close gedit.

sudo gedit /etc/udev/rules.d/70-persistent-net.rules
(Paste into this file)
Save/Close
rm /etc/iftab

Is this what you want for me to do?

zeddock

I decided to go with...
sudo mv /etc/iftab /etc/iftab.HOLD
... for that last line. <smile>

zeddock

No change. Still no wlan0 and still no wireless since Aug 3rd. Please go back and find out what happened?

Thanx,

zeddock

This is the format of my /etc/udev/rules.d/70-persistent-net.rules file:

# PCI device 0x8086:0x4222 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:19:d2:2e:7f:c6", NAME="wlan"

Also did you check to make sure that you have the bcm43xx-fwcutter package installed?

I didn't check. Was just counting on default system.
You want me to?

Also, I see Tribe 4 released. Should I do anything with that?

My .rules file is below: You can see how I just added what had been in
interfaces.

====
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x8086:0x1010 (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:60:1a:58:ca",
NAME="eth0"

# PCI device 0x8086:0x1010 (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:60:1a:58:cb",
NAME="eth1"

# PCI device 0x14e4:0x165d (tg3)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:56:ec:bc:24",
NAME="eth2"

# PCI device 0x14e4:0x4324 (bcm43xx)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:90:4b:1a:17:41",
NAME="eth3"

# USB device 0x0bb4:0x0b04 (rndis_host)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="80:00:60:0f:e8:00",
NAME="eth4"

# Ethernet devices
eth0 mac 00:0d:56:ec:bc:24 arp 1
wlan0 mac 00:90:4b:1a:17:41 arp 1
====

On 8/14/07, Brian Murray <email address hidden> wrote:
>
> This is the format of my /etc/udev/rules.d/70-persistent-net.rules file:
>
> # PCI device 0x8086:0x4222 (ipw3945)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:19:d2:2e:7f:c6",
> NAME="wlan"
>
> Also did you check to make sure that you have the bcm43xx-fwcutter
> package installed?
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Yes, please ensure that the bcm43xx-fwcutter package is installed.

The lines you have appended to that file won't work. If you want the interface with MAC address 00:90:4b:1a:17:41 to be identified as wlan0 you will need to replace the 'NAME="eth3"' line with 'NAME="wlan0"'.

What about the arp 1 on the end of those lines? I do not see that in your
formatting.
Here is the new content:
========
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.
# Ethernet devices

# PCI device 0x14e4:0x165d (tg3)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:56:ec:bc:24",
NAME="eth0"

# PCI device 0x14e4:0x4324 (bcm43xx)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:90:4b:1a:17:41",
NAME="wlan0"

# PCI device 0x8086:0x1010 (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:60:1a:58:cb",
NAME="eth1"

# PCI device 0x8086:0x1010 (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:60:1a:58:ca",
NAME="eth2"

# USB device 0x0bb4:0x0b04 (rndis_host)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="80:00:60:0f:e8:00",
NAME="eth3"
========
zeddock

On 8/14/07, Brian Murray <email address hidden> wrote:
>
> Yes, please ensure that the bcm43xx-fwcutter package is installed.
>
> The lines you have appended to that file won't work. If you want the
> interface with MAC address 00:90:4b:1a:17:41 to be identified as wlan0
> you will need to replace the 'NAME="eth3"' line with 'NAME="wlan0"'.
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

bcm43xx-fwcutter package is installed.
Still no joy.

zeddock

On 8/14/07, Brian Murray <email address hidden> wrote:
>
> Yes, please ensure that the bcm43xx-fwcutter package is installed.
>
> The lines you have appended to that file won't work. If you want the
> interface with MAC address 00:90:4b:1a:17:41 to be identified as wlan0
> you will need to replace the 'NAME="eth3"' line with 'NAME="wlan0"'.
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

What is next Brian? I did answer your question but this bug still says incomplete.

Should I take another action?

This is my current file:
===
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.
# Ethernet devices

# PCI device 0x14e4:0x165d (tg3)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:56:ec:bc:24", NAME="eth0"

# PCI device 0x14e4:0x4324 (bcm43xx)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:90:4b:1a:17:41", NAME="wlan0"

# PCI device 0x8086:0x1010 (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:60:1a:58:cb", NAME="eth1"

# PCI device 0x8086:0x1010 (e1000)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0d:60:1a:58:ca", NAME="eth2"

# USB device 0x0bb4:0x0b04 (rndis_host)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="80:00:60:0f:e8:00", NAME="eth3"
===

For others watching this bug and having similar issues, I want to pass on info about wicd.
I think it should replace network-manager in gusty.

Take a look here:http://ubuntuforums.org/showpost.php?p=3206660&postcount=5

It did not solve this bug but man! It sure is nice to have a network tool better than network-manager to see what is on, off, and generally not working.

zeddock

Brian, I am updating regularly. The problem still exists, not only for me but for many others. Should the package be listed as an updated version?
Here is a link: http://ubuntuforums.org/showthread.php?t=340689

That forum post is about using ndiswrapper so you can use the Windows driver for your network adapter, but I am under the impression that you are using the bcm43xx driver. If I am correct where exactly did you put the firmware when it was working? Using 'locate bcm43xx_microcode4.fw' may be helpful in finding it.

That thread is how I have gotten wireless to work in the past... on Feisty.
I did try it once on Gusty but way before Tribe 2. I have not used the
method so far for Gusty. Gusty, prior to Aug 3rd was working "out of the
box".

Here is what I get from your requested commandline query...
/lib/firmware/2.6.22-8-generic/bcm43xx_microcode4.fw

Does this help?

Thanx!

zeddock

On 8/17/07, Brian Murray <email address hidden> wrote:
>
> That forum post is about using ndiswrapper so you can use the Windows
> driver for your network adapter, but I am under the impression that you
> are using the bcm43xx driver. If I am correct where exactly did you put
> the firmware when it was working? Using 'locate bcm43xx_microcode4.fw'
> may be helpful in finding it.
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Right, you are now running the 2.6.22-9 version of the kernel which would look in '/lib/firmware/2.6.22-9-generic/' for the firmware. You could move the firmware to '/lib/firmware/2.6.22-9-generic/'. However, that isn' the best solution as if there is another kernel update you will have to move the firmware again. The best solution is to put the firmware in '/lib/firmware/'. How did you firmware end up in the 2.6.22-8-generic directory?

I do not know how it ended up there.
How is moving the firmware to /lib/firmware going to help?

I will move it now and reboot. I am also moving .5 version. Should I
remove the .#??

zeddock

On 8/17/07, Brian Murray <email address hidden> wrote:
>
> Right, you are now running the 2.6.22-9 version of the kernel which
> would look in '/lib/firmware/2.6.22-9-generic/' for the firmware. You
> could move the firmware to '/lib/firmware/2.6.22-9-generic/'. However,
> that isn' the best solution as if there is another kernel update you
> will have to move the firmware again. The best solution is to put the
> firmware in '/lib/firmware/'. How did you firmware end up in the
> 2.6.22-8-generic directory?
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

The bcm43xx-fwcutter package will first look in '/lib/firmware' and then in the specific kernel version subfolder of '/lib/firmware'.

Thought I responded to this.
The suggested change has made no difference. What other information can I get to you that will assist you in solving this?

Thanx!
Zeddock

I have done a fresh install of Tribe5 and same problem exists.

What next Brian?

PS. Thank you for all of your efforts on this.

zeddock

On 8/20/07, Brian Murray <email address hidden> wrote:
>
> The bcm43xx-fwcutter package will first look in '/lib/firmware' and then
> in the specific kernel version subfolder of '/lib/firmware'.
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I have a similar problem with my wireless.. It hangs the computer. This does happen when i start a large filetransfer.
I have a Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02) with ndiswrapper.. The fwcutter does not work for me at all.
kernel 2.6.22-10-386 on a Dell Inspiron 8500
Anyone with any idea what it could be?

Hardware: BCM4306, rev 02

Using the bcm43xx driver, *not* ndiswrapper. Kernel package is 2.6.22-10 (all updates applied as of this morning, although it broke a couple weeks ago). The correct firmware is definitely installed in /lib/firmware and nowhere else.

Problem: I can see networks to connect to (using e.g. KNetworkManager). Trying to connect fails; for instance, again using KNetworkManager, it stops at 57% complete "Activation Stage: IP configuration started".

From bug#124159 ("Broadcom bcm43xx Wireless driver regression in gutsy"), it looks like a connection *can* be made (using the bcm43xx drivers in the current kernel), but the throughput is very low and strongly dependent on distance/signal strength - so perhaps I'm simply too far away. Of course, then it works out as "bcm43xx hardware can't connect to anything farther than 5 feet away", which is still pretty broken...

dmesg shows repeated error messages:
[ 29.036000] bcm43xx: TODO: Incomplete code in keymac_write() at /build/buildd/linux-source-2.6.22-2.6.22/drivers/net/wireless/bcm43xx/bcm43xx_main.c:1112

(and also at line 1114). (Yes, the full output of dmesg, as well as version_signature, lspci -vvnn, and uname -a, is all attached.)

Looking at the source confirms this - that bit of keymac_write() really is just a stub. That function is exactly the same in the 2.6.20 source (package 2.6.20-16.31 from feisty).

So I guess this turned out to be a "me too" and/or a "bump".

Diquito - due to the fact that you are using ndiswrapper and not the bcm43xx driver you should submit a separate bug report.

What does Triaged mean please?
Zeddock

On 9/7/07, Brian Murray <email address hidden> wrote:
>
> Diquito - due to the fact that you are using ndiswrapper and not the
> bcm43xx driver you should submit a separate bug report.
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Importance: Undecided => High
> Assignee: Brian Murray => Ubuntu Kernel Team
> Status: Confirmed => Triaged
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I have similar problem on my laptop (Fujitsu-Siemens Amilo Pro V2055). In Feisty works wifi very good (after bcm43xx-fwcutter installation), but in Gutsy is problem. Gutsy shows me a dialog with option to enable this and automaticcaly installs bcm43xx-fwcutter. There are two possibilites - download fw file from server or from disk. When I click on server downloading, fw downloads, when I click on find local file (or similar), it makes nothing. I have fast latest version of Gutsy and I must download via ethernet cabel. Wifi doesnt work for me in Gutsy. bcm43xx-fwcutter is still installed. I do not use ndiswrapper, in FF I had some problems with it. bcm43xx-fwcutter was very good in FF.

Thanks for your answer (and sorry for my bad english)

Brian,
I am writing to you from a fresh Tribe5 install.
bcm43xx still not working. R-D-M still not handling it properly.
What next please?

Thanx,

zeddock

On 9/11/07, Libor Šedivý <email address hidden> wrote:
>
> I have similar problem on my laptop (Fujitsu-Siemens Amilo Pro V2055).
> In Feisty works wifi very good (after bcm43xx-fwcutter installation),
> but in Gutsy is problem. Gutsy shows me a dialog with option to enable
> this and automaticcaly installs bcm43xx-fwcutter. There are two
> possibilites - download fw file from server or from disk. When I click
> on server downloading, fw downloads, when I click on find local file (or
> similar), it makes nothing. I have fast latest version of Gutsy and I
> must download via ethernet cabel. Wifi doesnt work for me in Gutsy.
> bcm43xx-fwcutter is still installed. I do not use ndiswrapper, in FF I
> had some problems with it. bcm43xx-fwcutter was very good in FF.
>
> Thanks for your answer (and sorry for my bad english)
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

This helped me from bug 13500 https://bugs.launchpad.net/ubuntu/+source/restricted-manager/+bug/135000
Basilio was kind enough to post this:
user@machine:~$ cd /tmp
user@machine:/tmp$ sudo rmmod bcm43xx
user@machine:/tmp$ wget -c http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
user@machine:/tmp$ sudo bcm43xx-fwcutter -w /lib/firmware/`uname -r`/ wl_apsta-3.130.20.0.o
user@machine:/tmp$ sudo modprobe bcm43xx

I added a sudo to the last line.

No reboot needed. Go check your icon and find that wireless networks now show up.
I am using a Dell Latitude D800 with a bcm4309 in it.

Thanx Basilio.

Tribe 5 daily as of 9/22/07
Fresh install of formatted drive with Live CD install.
Then Update Manager
Reboot
Wireless working at 24MBs

zeddock
YAHOOOOOOO!

Should probably add that wireless throughput was increased via:
iwconfig eth1 rate 5.5M
or
iwconfig wlan0 rate 5.5M <===If you changed the name of the device

zeddock

Same problem here--wireless on my Dell Latitude D600 was working great with my BCM4309 (via the firmware cutter) in Feisty--now broken in Gutsy when using the restricted driver manager's autoinstaller of BCM43xx-fwcutter and automatic firmware extractor. No wireless networks show up in network-manager.

I upgraded from Feisty and do NOT want to do a fresh install. Ideas/solutions welcome--I'm clearly not the only one with this problem!

P.S. when I slide a NetGear (atheros) PC card into the PC card slot, all wireless networks show up normally in network-manager, so this is definitely a problem with the BCM4309 card.

other bugs like same/similar problem

https://bugs.launchpad.net/ubuntu/+source/bcm43xx-fwcutter/+bug/87970
https://bugs.launchpad.net/ubuntu/+bug/150262

Latest Gusty update seems to offer new 43xx firmware update in restricted manager. I did it and then used command:
sudo iwconfig wlan0 rate 5.5M

Hopefully this will raise the throughput from what is shown as 24 to 5.5M

zeddock

Wow!
sudo iwconfig wlan0 rate 11M

seems to really improve performance. If someone wants to tell me how to quantify the changes I would be happy to post back.

zeddock

I do not want to step on any toes but "Triaged" seems inappropriate for where this is right now. The problems are certainly "confirmed" so I am going to change that if I have permissions to do so. Please let me know if this is inappropriate.

zeddock

Scratch that entry about "sudo iwconfig wlan0 rate 11M"

It didn't really work well.

zeddock

On 10/12/07, zeddock <email address hidden> wrote:
> I do not want to step on any toes but "Triaged" seems inappropriate for
> where this is right now. The problems are certainly "confirmed" so I am
> going to change that if I have permissions to do so. Please let me know
> if this is inappropriate.
>
> zeddock
>
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Status: Triaged => Confirmed
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

zeddock, you may want to read this: https://wiki.ubuntu.com/Bugs/Status
Triaged is actually a better status then confirmed, so you shouldn't change a status back from triaged to confirmed.

Thanx!
I've been waiting for someone to confirm or deny that issue. I actually
searched a bit on it, but came away more confused than anything else. Now I
have to go fix all the ones I have changed before someone smacks me!

Thanx again!

zeddock

On 10/17/07, albert <email address hidden> wrote:
>
> zeddock, you may want to read this: https://wiki.ubuntu.com/Bugs/Status
> Triaged is actually a better status then confirmed, so you shouldn't
> change a status back from triaged to confirmed.
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I had this problem with bcm43xx after upgrading from 7.04 to 7.10 as well. I ran ndiswrapper on 7.04 so, after removing ndiswrapper, and reinstalling ndiswrapper from source with no success. I then spent many frustrating hours trying and failing to get the firmware cutter restricted driver to work until I came back to ndiswrapper and resolved to make it work again.

Directions for ndiswrapper found here: https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper

after this step:
depmod -a
modprobe ndiswrapper

tail /var/log/messages reveals the problem:
laptop kernel: [ 16.716000] ndiswrapper: changing interface name from 'wlan0' to 'eth1'
Oct 20 12:41:14 laptop kernel: [ 66.416000] ADDRCONF(NETDEV_UP): eth1: link is not ready

My fix was to edit /etc/udev/rules.d/70-persistent-net.rules I changed ETH1 to WLAN0, saved the changes and rebooted. And now
the messages log says:
laptop kernel: [ 53.940000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

I am wireless again,
I Hope this helps.

It happen also to me on Dell INSPEIRON 6400 and other, look in the **last** messages in this thread:
http://ubuntuforums.org/showthread.php?t=405990

"tail /var/log/messages reveals the problem:
laptop kernel: [ 16.716000] ndiswrapper: changing interface name from 'wlan0' to 'eth1'
Oct 20 12:41:14 laptop kernel: [ 66.416000] ADDRCONF(NETDEV_UP): eth1: link is not ready

My fix was to edit /etc/udev/rules.d/70-persistent-net.rules I changed ETH1 to WLAN0, saved the changes and rebooted. And now
the messages log says:
laptop kernel: [ 53.940000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

I am wireless again,"

This is what I get without change anything:
 ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 20 20:18:33 nadav-laptop kernel: [ 1503.324000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Why it's not work if it's should be ok?

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.