[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2014-05-25 Thread Robert B
This just started working for me with the 3.14 release of the Linux kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1142385 Title: B43 Wireless Autoconnect Failure To manage notifications abo

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2014-01-19 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1142385 T

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-11-19 Thread Callum Hutchinson
Hi, sorry I'm afraid I just don't have the time right now to reinstall Ubuntu and give it the testing you're asking for. As such I think the bug needs to remain in it's current state, I cannot test the upstream kernel nor install a dev build of Ubuntu. If there's anything I need to do to 'close'

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-11-19 Thread Christopher M. Penalver
Callum Hutchinson, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please just make a comment to this. Also, could you please test the latest upst

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-05-02 Thread Callum Hutchinson
RC8 fix wasn't present for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1142385 Title: B43 Wireless Autoconnect Failure To manage notifications about this bug go to: https://bugs.launchpad.net

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-05-01 Thread Callum Hutchinson
Interesting, so we both definitely have the same card and are affected by the same issue. What do you get when you run the firmware-b43-installer? Does the terminal output anything about an unsupported device with the PCI ID tag? Odd that rc8 of 3.9 seemed to fix this and then the final 3.9 kerne

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-05-01 Thread monochromec
Issue resurfaced again this morning, syslog is inconclusive. Upstream kernel driver in 3.9 still seems to be buggy - unfortunately this issue cannot be reproduced easily it seems. Will investigate further time permitting. For the meantime I'm going back to the 3.2.0.32 kernel which seems to be the

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-04-30 Thread Callum Hutchinson
Hmm, what card is it in your Macbook? I just reinstalled Raring and installed the freshly released 3.9 kernel and installed b43-fwcutter and firmware-b43-installer. I'm still getting the unsupported device error upon executing the installer command. I'll try the BCM kernel source listed in addit

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-04-29 Thread monochromec
Issue seems to have disappeared in kernel 3.9. As indicated in my last comment, I installed an upstream kernel (3.9.0-030900rc8-generic to be precise) and ran a 24 hour ping test. According to system logs no connection drops or loss of beacons. As a side effect, I could also remove the b43 from the

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-04-28 Thread monochromec
Affects kernel 3.8.0-19-generic (stock on raring) too. I noticed wifi connections dropping constantly and overall pretty bad wifi performance after upgrading to raring recently. Testing with a 3.6.3 kernel produced the same results. At first I thought the firmware was to blame but after toying arou

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-04-12 Thread Callum Hutchinson
Done, bug is hopefully reported upstream via email. Couldn't use the suggested format originally as seen in comment #12 but I've attached the info as the text document that comment links to. Hopefully this is sufficient enough :) -- You received this bug notification because you are a member of U

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-27 Thread Joseph Salisbury
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-24 Thread Callum Hutchinson
Here's something else interesting, if I disable wifi and re-enable it after manually connecting the connection is fine. It's as if you have to tell the card that the ESSID is what it is and then it'll connect no problems. Also curiously, apparently the wlan0 interface doesn't exist and hence, run

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-21 Thread Callum Hutchinson
Still not fixed with mainline kernel 3.9rc3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1142385 Title: B43 Wireless Autoconnect Failure To manage notifications about this bug go to: https://bugs

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-09 Thread Callum Hutchinson
Here is the output from the terminal for reinstalling the firmware-b43-installer package. Interesting that it's 'unsupported' now. ** Attachment added: "termoutput" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142385/+attachment/3564753/+files/termoutput -- You received this bug no

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-07 Thread Callum Hutchinson
Tested 3.9 kernel and this seems to make the issue worse as now my hardware has a delay on how long until connecting to networks becomes available in the network manager menu. ** Tags removed: kernel-unable-to-test-upstream ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu)

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-05 Thread Callum Hutchinson
I've added the unable to test tag, the kernel doesn't appear to have been fully compiled and packaged in the Mainline PPA at the minute, I'll keep checking back though. Leaving as uncomfirmed at the moment until I've actually got a kernel to test :) ** Tags added: kernel-unable-to-test-upstream -

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-05 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages. If this bug is fixed in the ma

[Bug 1142385] Re: B43 Wireless Autoconnect Failure

2013-03-04 Thread Callum Hutchinson
Also forgot to mention, ran 'apt-get install --reinstall firmware-b43-installer' and it downloaded fine, went to post config run it and said something along the lines of 'Aborting: Unsupported Device 14e4:4331'. 4331 happens to be the card's model number in the Mac mini I have. Hope this helps.