On 09/02/2012 11:54 AM, Ekimia wrote:
@Larry : We tested cw-3.3 without any success. only the new
underground version from Realtek correct the issues.
Do you know if this version 0006.0514.2012 will be integrated soon ?
it seems There are several Cards with 8188CE and only the newer ones
On 08/15/2012 10:22 PM, Richie Gress wrote:
[1] Summary of Problem.
0bda:8176 RTL8188CUS does not connect to wireless networks
[2] Full description of the Problem.
The RTL8188CUS USB wireless card will not connect to wireless networks. The
connection is attempted over and over again, and
I downloaded the final version of the Ubuntu Studio 9.04 Alternate
AMD64 DVD and installed it on my Turion AMD64 X2-based computer. It
works well except that I could not find a way to get the Gnome applet to
accept a WPA2 secret. It only offered me WEP password or WEP key.
What are the 10 or so
The clocksource tsc unstable message has nothing to do with b43,
b43legacy, or any other wireless driver. It comes from your CPU. Many,
if not all, AMD 64-bit processors will show this message. Mine does, but
it does not affect any operations. Linux uses other clocks that are
stable, and is just
I found a problem with the RTL8187, but not RTL8187B, driver this
afternoon. The patch, which is written for wireless-testing and compat-
wireless, is attached. To apply it on 2.6.28 or older, it needs some
modifications.
** Attachment added: Patch for RTL8187
I don't know why you are getting APIC errors. I certainly doubt that b43
is causing them - it seems much more like a BIOS error that b43 is
triggering. These reports on ACER laptops are the only ones I have seen.
Most users never see anything like this..
To save the output of a command, use the
Since Acer tells you nothing about why Vista needs a new BIOS, it is
impossible to tell whether it would help your problem, or not.
The warning is a general one. If a BIOS reflashing goes wrong, the
motherboard may be bricked. On the other hand, I have done this
operation many times and it has
You clearly need the hp-dmi module. If it isn't in Intrepid, then you
will need to generate your own kernel.
Larry
--
No wifi with b43legacy
https://bugs.launchpad.net/bugs/238896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@Cliff - What is your device? If it is listed in this thread, I missed
it. Please post the first two lines of the output of 'lspci -nnv' that
describe your BCM43xx device.
If yours if a BCM4306/3, it is possible that you have the SPROM
programming error for a device we have not yet seen, or one
Does 'lsmod | grep hp' show that hp-dmi is loaded?
I'm not sure of the differences between alpha6 and alpha5.
In bcm43xx, the driver pays little attention to things like that. At
least the hardware is good.
Larry
--
No wifi with b43legacy
https://bugs.launchpad.net/bugs/238896
You received
In the latest version of the kernel, there is a new module named hp-dmi
that should handle your radio-enable/disable button; however, I have no
way to test it.
The new module will be in linux-2.6.27-3.4, which has not yet hit the
repositories. When it does, install it. After rebooting, you will
The new line in dmesg is good.
The MODALIAS line is what makes input module load.
Please do the following:
Select an alternate console if possible by pressing CTRL/ALT/F2. Login
in, enter the command 'showkey' and press the radio-enable button.
Please report the scan code that gets printed.
Since your wireless enable/disable key doesn't generate a scan code, I'm
not sure what we can do.
From what I read through googling, some Compaq notebooks are unable to
change the state of the wireless in Linux.
One person's solution was For all those with only one system: Go to
BIOS and do the
Furlot,
If the BIOS reset works, ignore this try.
If it fails, this version will simulate pressing the KEY_WLAN key down
and up to see if that sets the radio on.
Larry
** Attachment added: Try 3
http://launchpadlibrarian.net/17485574/new_b43legacy.tar
--
No wifi with b43legacy
I don't need the whole /var/log/messages. The output from 'dmesg | grep
b43' will be enough.
If you do a 'sudo modprobe b43' before 'sudo modprobe b43legacy', does
it load?
Larry
--
No wifi with b43legacy
https://bugs.launchpad.net/bugs/238896
You received this bug notification because you are
Try #2 has been attached. The commands are the same.
Larry
** Attachment added: Try 2
http://launchpadlibrarian.net/17419797/new_b43legacy.tar
--
No wifi with b43legacy
https://bugs.launchpad.net/bugs/238896
You received this bug notification because you are a member of Ubuntu
Bugs, which
Furlot,
Do you use a 32- or 64-bit system?
Larry
--
No wifi with b43legacy
https://bugs.launchpad.net/bugs/238896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Furlot,
I discovered that in 2.6.24 that b43legacy did not connect to the rfkill
system at all. I have attached a tar file named new_b43legacy.tar. After
you download it, you should issue the following commands:
tar xvf new_b43legacy.tar
new_b43legacy/install.sh
These commands will load the new
Furlot,
I'm assuming that pushing the button does not lead to messages like
b43legacy-phy1: Radio hardware status changed to DISABLED
b43legacy-phy1: Radio hardware status changed to ENABLED
AFAIK, none of the b43legacy developers have a device with an rfkill
switch. Obviously, we didn't get
Your SPROM contents are irrelevant. If you have the SPROM bug, then your
device would _NEVER_ transmit, thus never connect. Obviously, that is
not the case.
The performance of BCM4306 devices is the worst of all those driven by
b43. I would like to review the reverse engineering, but development
I have said this before, but I guess it bears repeating.
The revised SPROM changes the contents of something called the
board_flags_lo permanently. The revised kernel changes it dynamically
when the contents of the SPROM are loaded into memory. The net effect is
_EXACTLY_ the same
--
What is the output of 'dmesg | grep ssb', 'dmesg | grep b43', and 'lsmod
| grep b43'? I also want to see the first two lines of output for your
wireless device that come from the command '/sbin/lspci -nnv'.
Larry
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't
I'm not sure of the meaning of the tests. The values in the SPROM are
read only when the base driver ssb is loaded. Unless you reboot, or
modprobe -r b43, changes are ignored. I think you need to do them again.
As to why it doesn't come up running, that is a matter for other of the
Ubuntu mailing
To anyone reading this thread. I reemphasize that changing the SPROM is
not as simple as using an editor on your data because these data must
satisfy an 8-bit CRC.
For efolch:
Your new values are
The change we made in your SPROM disabled the Bluetooth coexistence
function in your firmware. If you use Bluetooth, there will be
interference in the 2.4 GHz band.
Because you had to rewrite the firmware files on the disk, I would like
you to do the following:
1. Write the original SPROM
It cannot be a shell script, but there is an SPROM manipulation program
to do this. See the posting 2 or 3 above this one.
Your revised SPROM contents are
The problem is well known and is due to Broadcom's SPROM miscoding for
most, if not all, PCI versions of the BCM4306 and at least one PCI
version of the BCM4318. The difficulty is with Bluetooth coexistence,
thus we cannot apply the fix to _ALL_ cards without testing a
representative of each card
For Christophe Schneid,
The revised SPROM contents for your device is
Besides the MAC address, there are other parameters in the SPROM where
Broadcom accounts for the specific amplifiers and radio of a device.
When you wrote the SPROM for board A into board B, these were also
overwritten. Fortunately, there are not many of these. The list includes
the antenna gain,
No, don't use that one. It has the MAC address of the second board. If
the second board is working fine, and the first SPROM that you sent came
from the board that is giving the trouble, I have no idea what to do.
Larry
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP
Is there any major difference in their locations, particularly relative
to any interference? What channel are you using? What other channels are
in use in your neighborhood? Try all the real usable channels, i.e. 1,
6, and 11.
Larry
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 :
The firmware can be copied from computer to computer.
Once the modified SPROM is loaded, you don't ever need to do it again.
I would try channel 1 on your AP. Interference in the 2.4 GHz band
doesn't always come from other wifi devices. Any number of household
devices can interfere.
You can
Sorry, I missed that part of your posting.
Yes, your interface has the SPROM coding problem. The fix for it was one
of the first that made it into mainline.
If you want to modify your SPROM so that you can use the standard
kernel, just write the following contents back into your machine:
I don't think that is a b43 problem. I don't use Gnome so I'm not sure
what is available, but under KDE, the wireless connection has an
Autoconnect button that needs to be checked when the connection is
edited. When that is done, the system will look to the wireless before
the wired interface.
Is
Is bcm43xx blacklisted? Are ssb and b43 loaded on boot? You should see
that in the dmesg output.
Larry
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
You received this bug notification because you are a member of
Is the signal weaker on the first card than the second. The logged data
looks like what happens when the signal is marginal. Unfortunately,
mac80211 is not really good at reconnecting when an interface loses the
AP.
As long as it works at all, we have fixed the SPROM programming error.
Sorry I
I think it would, but in all the material that he posted in the initial
message, the critical information (the subvendor and the subdevice
codes) are not there.
Larry
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
The patch does not rewrite the SPROM. What it does is dynamically set
the board flags every time the driver starts. What we are doing is
making the change permanent, which achieves the same effect. Yes, the
patch will be compatible with the rewritten SPROM.
Your new SPROM contents should be
The bug reported in 257020 _IS_ the bug here for the BCM4306 and most of
the problems in this thread. You will find b43 to be much better than
bcm43xx for a couple of reasons. First of all, the softmac used by
bcm43xx never was any good - the mac80211, which is used by b43, is much
better.
One thing I didn't make clear. The revised SPROM should have been
applied to only one card. The reason is that the MAC address is also
encoded in the SPROM. You now have two cards with the same MAC address -
a no-no.
Please send me the MAC address for the second card if you can find it,
and I'll
The revised data for the 2nd card are
014015003717204300800200021000180F007466760C4516A01277FBACFE3C003E000C0201BB
Ben,
That is the one. My code assumed that you were running ssb and b43. You
have bcm43xx loaded. The new version is
In a terminal, please enter the command '/sbin/lspci -nnv' and post the
first two lines of the output for your BCM4306.
We have found a number of devices with the SPROM incorrectly coded. A
fix has been entered into both the Hardy and Intrepid code base, but the
above data will show if your card
For Nattgew:
The numbers you provided are definitive. The patch that was accepted
today will fix your device. You can (1) wait for the fixes to propagate
through the system, (2) you can patch your own kernel, or (3) we can
rewrite your SPROM. Please let me know which you prefer. If the latter,
I can confirm the b43legacy does not crash Intrepid.
--
Loading b43legacy freezes computer
https://bugs.launchpad.net/bugs/192720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: b43-fwcutter
The Broadcom driver selected for firmware extraction is outdated for a
kernel as new as 2.6.26. A revised version of
/usr/share/b43-fwcutter/install_bcm43xx_firmware.sh is attached.
** Affects: b43-fwcutter (Ubuntu)
Importance:
** Attachment added: Revised
/usr/share/b43-fwcutter/install_bcm43xx_firmware.sh
http://launchpadlibrarian.net/16282083/install_bcm43xx_firmware.sh
--
b43-fwcutter in Intrepid uses old firmware
https://bugs.launchpad.net/bugs/251520
You received this bug notification because you are a
The poor performance of the early BCM4306 units - the ones that use
b43legacy - is known to us. Those models have the least work done by the
firmware, and the most by the host cpu. The mistakes in the reverse
engineering all add up and lead to the result you noted. By the time you
get to BCM4306
Despite what everybody says, b43 does work. What b43 does that bcm43xx
does not do is look at the state of the radio-kill switch.
When you boot the system, what output is produced by the command
dmesg | grep b43
What sort of hardware does your Dell computer have to control the radio?
FYI, the
You say that I only experience this with WPA enterprise (eduroam).
Does this mean that it works with WEP and WPA-PSK?
Larry
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentication with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
You received this bug notification because
If the card is built into a laptop, it is probably a mini-PCI.
Your dmesg output is different than some of the others in that you don't
get the Radio hardware status changed to disabled line. Your system
does not have a radio enable/kill switch.
The empty result for the echo and the cat output
Your wireless interface is down. I think this means that it has never
been configured. On my distro (openSUSE), I would configure it with our
system tool for either ifup operations or with NetworkManager. For the
latter case, I would then use the applet to select an AP, etc. I'm sure
someone will
Sorry it has taken so long to respond. I was out of town.
There seems to be a problem with the rfkill and rfkill_input set-up
logic. I have two devices that use b43legacy; however, neither of them
has a radio kill button and/or switch so this section may not have
been thoroughly tested, but the
Do the modules rfkill and rfkill_input show up in the output of lsmod?
--
No wifi with b43legacy
https://bugs.launchpad.net/bugs/238896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
1. Does blacklisting b44 make any difference?
2. What is the form of your BCM4303? Is it a mini-PCI card, a PCI card,
or what?
3. There is a line Radio hardware status changed to disabled in your
dmesg output, that usually is printed when an rf-enable switch is turned
off. Does your machine have
I forgot to select the E-mail box.
--
No wifi with b43legacy
https://bugs.launchpad.net/bugs/238896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
For both Stefan and Damien: What, if anything, does dmesg have to say
regarding b43legacy or ssb?
--
Loading b43legacy freezes computer
https://bugs.launchpad.net/bugs/192720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Are any other messages logged around these ssb: FATAL ERROR ...
messages?
--
Loading b43legacy freezes computer
https://bugs.launchpad.net/bugs/192720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The bug is fixed in the updated kernels; however, the CD has not been
updated. To install from the current CD, you need to do the following:
1. Boot the CD, choose your language, and select install. Next press
F6 and insert break=top into the options line. I'm not sure if it was
necessary, but I
That decision is yours, of course; however, you will still have to
remove your existing card before you will be able to boot.
Larry
--
Loading b43legacy freezes computer
https://bugs.launchpad.net/bugs/192720
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You don't need to buy a USB device. From a terminal, do the following
commands:
sudo su -
echo deb http://ppa.launchpad.net/timg-tpi/ubuntu hardy main \
/etc/apt/sources.list.d/kernel-ppa.list
apt-get update
apt-get -u upgrade
After these commands are executed, a new kernel with patches for the
In many cases, the first error is the only one that has any
significance. I'm confident that your log has a message that the
firmware could not be loaded. I know where periodic messages arise, and
I'll look into stopping them. I don't think it has anything to do with
b44. It does not need any
Ian,
There are numerous improvements in b43 since 2.6.24, but one of the
major advances have been in mac80211's speed-setting algorithm. To get
those changes you would need the 2.6.25 kernel, or the kernels from the
mainline or wireless-testing git trees. They are too intrusive for a
simple
Works for me.
--
Loading b43legacy freezes computer
https://bugs.launchpad.net/bugs/192720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
A patch for this bug has just been submitted to the Ubuntu Kernel Team.
The problem was a kernel NULL pointer and affects BCM4301 and BCM4303
cards, which use the b43legacy driver. After patching, the Ubuntu kernel
works with these devices.
--
Loading b43legacy freezes computer
*** This bug is a duplicate of bug 192720 ***
https://bugs.launchpad.net/bugs/192720
A patch for the bug that causes hard crashes with BCM4301 and BCM4303
cards has been submitted to Ubuntu.
--
Ubuntu Hardy RC not booting
https://bugs.launchpad.net/bugs/220384
You received this bug
If this problem is due to the ASUS hack mentioned earlier, a fix for
that has been submitted to the Ubuntu Kernel Team. I will be watching
this bug for progress.
--
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't
work.
https://bugs.launchpad.net/bugs/182716
You
The b43-pci-bridge driver is a wedge between ssb and the drivers b43 and
b43legacy. It is the part of the system that decides if your bcm43xx
hardware needs the new b43 driver, or b43legacy that handles older
hardware.
Your system was not loading b43 because the patch that allowed the
system to
A patch to implement the BCM4312 rev 2 and BCM4311 rev 2 cards has been
submitted to the Ubuntu Kernel Team. This patch was previously included
in early versions of the Hardy kernel, but was reverted due to reported
difficulties with a BCM4312 rev 1 card. The new version should not have
that
Can you get any of the APIC errors out of your old logs? I'm a bcm43xx
developer and this is the first report of this sort of error.
--
B43 driver causing numerous APIC errors
https://bugs.launchpad.net/bugs/222174
You received this bug notification because you are a member of Ubuntu
Bugs, which
The patch needed to implement you BCM4311 rev 2 card was installed in
earlier versions of Hardy, but was reverted after a regression was
reported on a BCM4312. The necessary patch to reinstall rev 2 cards
without hurting the BCM4312 has been reported.
--
hardy x86_64 b43 not working on HP
The drivers ship with the system. It is the firmware that _MUST_ be
installed separately. Use fwcutter for that.
--
Broadcom B43 wireless doesn't work in 8.04 worked in 7.10
https://bugs.launchpad.net/bugs/219775
You received this bug notification because you are a member of Ubuntu
Bugs, which
If you want to use ndiswrapper with a BCM43xx card with Hardy, you
_MUST_ blacklist ssb. The reason is that ssb owns the BCM43xx PCI ID's.
It then uses internal information in the card to decide whether to load
b43 or b43legacy depending on the age of the equipment.
With the bcm43xx driver, the
The b43 and b44 drivers both utilize the ssb driver. As you noticed, if
ssb loads, then it owns the bcm43xx PCI Id's and ndiswrapper will not
load.
If you want to use b44 for eth0 and ndiswrapper for the wireless
interface, then you need to blacklist ssb and bcm43xx. YTou will then
need the
The code needed to recognize the BCM94311 rev 02 card is not in the
current version of Hardy. It was in some of the test versions but was
reverted because of a problem with BCM4312 cards. A new patch has been
submitted that will allow the usage of the rev 2 cards without any side
effects.
--
I was able to duplicate this problem with a BCM4306 using a new install.
When I downloaded kernel source and built my own kernel, the problem was
gone. Shortly thereafter, the updater installed a new kernel that also
worked. I have not been able to determine what changed. This was with
kernel
Could you try adding the noapic option to the boot and retry b43?
The error message indicates an illegal register address, but there may
be some other issue.
I would also like to see the output of lspci -v for the Broadcom card.
--
B43 driver causing numerous APIC errors
101 - 177 of 177 matches
Mail list logo
