*** This bug is a duplicate of bug 145382 ***
https://bugs.launchpad.net/bugs/145382
** This bug has been marked a duplicate of bug 145382
[Gutsy] broken 70-persistent-net.rules
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug no
"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 ET
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
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a member
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
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 PROTECTED]> 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 bu
Scratch that entry about "sudo iwconfig wlan0 rate 11M"
It didn't really work well.
zeddock
On 10/12/07, zeddock <[EMAIL PROTECTED]> 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
> goin
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)
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
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification becaus
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
--
Gusty updates broke my wireless connectivity
https://bugs.launc
other bugs like same/similar problem
https://bugs.launchpad.net/ubuntu/+source/bcm43xx-fwcutter/+bug/87970
https://bugs.launchpad.net/ubuntu/+bug/150262
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a mem
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-man
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
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification becaus
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
YAHOOO!
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a
This helped me from bug 13500
https://bugs.launchpad.net/ubuntu/+source/restricted-manager/+bug/135000
Basilio was kind enough to post this:
[EMAIL PROTECTED]:~$ cd /tmp
[EMAIL PROTECTED]:/tmp$ sudo rmmod bcm43xx
[EMAIL PROTECTED]:/tmp$ wget -c
http://downloads.openwrt.org/sources/wl_apsta-3.130.
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 PROTECTED]> wrote:
>
> I have similar problem on my laptop (Fujitsu-Siemens Amilo Pro V2055).
> In Feisty wor
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
What does Triaged mean please?
Zeddock
On 9/7/07, Brian Murray <[EMAIL PROTECTED]> 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 =
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
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 conn
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 Inspi
What next Brian?
PS. Thank you for all of your efforts on this.
zeddock
On 8/20/07, Brian Murray <[EMAIL PROTECTED]> 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
I have done a fresh install of Tribe5 and same problem exists.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete => Confirmed
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a member of
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
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification becau
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 member of Ubuntu
Bugs,
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 PROTECTED]> wrote:
>
> Right, you are now running the 2.6.22-9 version
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 t
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/firmw
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 helpf
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
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/1305
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 bet
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-gene
bcm43xx-fwcutter package is installed.
Still no joy.
zeddock
On 8/14/07, Brian Murray <[EMAIL PROTECTED]> 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:
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; howe
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 br
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
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
No change. Still no wlan0 and still no wireless since Aug 3rd. Please
go back and find out what happened?
Thanx,
zeddock
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
I decided to go with...
sudo mv /etc/iftab /etc/iftab.HOLD
... for that last line.
zeddock
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
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/Clos
Maybe I have messed up Source information? What should they be. How should
I check?
jim
On 8/10/07, Brian Murray <[EMAIL PROTECTED]> 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
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.
--
Gusty updates broke my wi
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 guw way or plan on doing the work mysel
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 y
Here are the attachments...
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/8773849/dmesg.log
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/8773850/lspci-vvnn.log
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
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. Thank
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 c
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 t
tried to nominate for gusty but it was not listed.
zeddock.
--
Gusty updates broke my wireless connectivity
https://bugs.launchpad.net/bugs/130511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
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
** 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 member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
52 matches
Mail list logo
