1
[ 74.936281] b43-phy0 debug: Loading firmware version 351.126 (2006-07-29
05:54:02)
[ 76.197406] b43-phy0 debug: Chip initialized
[ 76.199682] b43-phy0 debug: 32-bit DMA initialized
[ 76.213855] DEV: registering device: ID = 'b43-phy0:tx'
[ 76.213863] kobject b43-phy0:tx: registe
,
>> 0x, 0x, 0x
>> b43-phy0: Controller RESET (DMA error) ...
>> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
>> b43-phy0: Controller restarted
>> b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x, 0x,
>&
vious models were experiencing problems with power saving. Use
>>> modinfo to find out what power saving parameters the module has and try
>>> disabling these, in case power management is the cause of the
>>> interruptions you are experiencing.
>> I'm not enoug
aving parameters the module has and try
> > disabling these, in case power management is the cause of the
> > interruptions you are experiencing.
>
> I'm not enough experienced to see that and deactivate it.
>
> My modinfo output :
> # modinfo b43
> filename:
>
e?
> >>
> >> b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x0000, 0x,
> >> 0x, 0x00000000, 0x
> >> b43-phy0: Controller RESET (DMA error) ...
> >> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
> &
Hi,
Has anyone managed to get BCM4312, 802.11b/g (pcie) Device: pci
0x4315, going with the b43 module?
b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x, 0x,
0x, 0x, 0x
b43-phy0: Controller RESET (DMA error) ...
b43-phy0: Loading firmware version 410.2160
I guess linux-firmware is a package released by the kernel folks
>> containing certain firmware blobs? It looks like rt73 is in there but
>> not b43.
>
> Maybe these?
> /lib/firmware/brcm/bcm4329-fullmac-4.bin
> /lib/firmware/brcm/bcm4329-fullmac-4.txt
> /lib/firmware/brc
troller RESET (DMA error) ...
> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
> b43-phy0: Controller restarted
> b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x, 0x,
> 0x, 0x, 0x
>
> I've unmasked and am using the
; advice and running without it for some time now - on desktops and
> > servers.
>
> Do you run a modular kernel or compile everything in? I do the latter,
> and on 3.17.0 turning this off caused the b43 firmware for my wifi
> card to not load. I'll give you that 3.17.0 has
ed loading firmware
error? Perhaps missing firmware stops eth0 from being created. I'd try
installing linux-fireware and trying again (assuming you havent
already).
>>> I guess linux-firmware is a package released by the kernel folks
>>> containing certain firmware blobs? It
e ago using b43-fwcutter
011. I have to hard-code the network settings in /etc/conf.d/net for my home
network, but am able to use wpa_supplicant whenever I go elsewhere. (I think
it's my home wireless router that causes the issue; probably needs a firmware
upgrade.)
Any how, I recently upgrade
re experiencing problems with power saving. Use modinfo to
> find out what power saving parameters the module has and try disabling these,
> in case power management is the cause of the interruptions you are
> experiencing.
I'm not enough experienced to see that and deactivate it
locate any
APs and running wpa_supplicant hangs scanning for an AP to attach to.
The driver seems to find the card ok and I followed the instructions
here: http://wireless.kernel.org/en/users/Drivers/b43 to get the correct
firmware. I also compiled both b43 and b43-legacy (since I have a
ocal.start, or the start section
> > >>> of /etc/conf.d/local if using baselayout2.
> > >>
> > >> Have you been through the guidance in this page to find out which
> > >> kernel driver you ought to use with your card?
> > >> http://
used them in
infrastructure mode with no problems (wpa2). However, here's the
official page:
http://linuxwireless.org/en/users/Drivers/b43
according to
http://linuxwireless.org/en/users/Drivers/b43/devices
your card (14E4:4311) is supported.
You need the firmware for the card, and the app
uot;iwscan" does not locate any
APs and running wpa_supplicant hangs scanning for an AP to attach to.
The driver seems to find the card ok and I followed the instructions
here: http://wireless.kernel.org/en/users/Drivers/b43 to get the correct
firmware. I also compiled both b43 and b43-legac
On Monday 27 Oct 2014 13:40:32 Douglas J Hunley wrote:
> On Fri, Oct 24, 2014 at 10:44 AM, Mick wrote:
> > I just enabled the wireless adaptor and I connected to the neighboor's AP
> > fine
>
> > with my b43 firmware (BCM4312 chipset):
> So is this a module in yo
nly says that your config doesn't
> > contain references to b43.
> >
> > If you do "make menuconfig" and then search for b43 (type slash to reach
> > the search functionality) many entries will show up: I count 23 hits in
> > 2.6.39-gentoo-r1 kernel.
> &g
> I see a lot of this in dmesg:
>
> b43-phy0 ERROR: MAC suspend failed
>
> I can connect to other wireless routers just fine, and I can connect
> to this one via ethernet. I've tried configuring it in various ways,
> security is disabled, and I've tried specifyin
l series and also updated the firmware. Have a good
> look in here to find the latest suitable firmware for your NIC:
>
> http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware
I upgraded to the latest firmware in portage and the "MAC suspend
failed" errors have disappeared, but I still
he "unable to apply firmware patch" messages on my desktop
which also uses the r8169 driver and doesn't have linux-firmware
installed.
I guess linux-firmware is a package released by the kernel folks
containing certain firmware blobs? It looks like rt73 is in there but
not b43.
- Grant
stalled from a different package?
Run emerge -p linux-firmware on that box to see if there's a blocker.
> I guess linux-firmware is a package released by the kernel folks
> containing certain firmware blobs? It looks like rt73 is in there but
> not b43.
Maybe these?
/lib/firmware/br
uck. Does anyone know what I could be doing wrong?
> >> >
> >> > Check that you're using the latest kernel and the latest firmware. I
> >> > used to get this error with a particular cisco access point and it
> >> > went away when I updated to
On Tuesday 20 April 2010 15:25:14 Paul Hartman wrote:
> On Tue, Apr 20, 2010 at 5:21 AM, Mick wrote:
> > Hmm, it's stuck in US mode for some reason. Firmware?
>
> Maybe you're right, I googled and found some info that the old
> broadcom driver didn't support c
t; >>
> >> Have you been through the guidance in this page to find out which
> >> kernel driver you ought to use with your card?
> >> http://linuxwireless.org/en/users/Drivers/b43
> >
> > Yes. Unfortunately it's a 14e4:4320/ with BCM4306/2 Chip s
uck. Does anyone know what I could be doing wrong?
>> >> >
>> >> > Check that you're using the latest kernel and the latest firmware. I
>> >> > used to get this error with a particular cisco access point and it
>> >> > went away wh
t firmware. I
> > used to get this error with a particular cisco access point and it went
> > away when I updated to 2.6.34 kernel series and also updated the
> > firmware. Have a good look in here to find the latest suitable firmware
> > for your NIC:
> >
> > ht
Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-ff-ff-89-78-e4
Capabilities: [16c] Power Budgeting
If I understood the wiki correctly, with the new kernel I don't have to
run b43-fwcutter, but just emerge the b43-fir
A_FIRMWARE="radeon/R600_rlc.bin radeon/R700_rlc.bin"
> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/"
>
> In my /lib/firmware I have:
>
> # ls -la /lib/firmware/
> total 1448
> drwxr-xr-x 5 root root4096 Sep 14 2012 .
> drwxr-xr-x 14 root root 12288
I'm trying to get my Broadcom 4311 b/g card to work with the native
kernel driver (bcm43xx) and b43-fwcutter but it's does not work. I
placed the extracted firmware code in /lib/firmware and dmesg states
that it failed to load the module. Has anyone gotten this card to work
and how
t
> my new kernel drivers are the right ones for this particular D-Link
> WiFi adapter?
It's certainly a great sign, but it may or may not be enough. I'm by no
means an expert, but I believe I have to install some extra firmware
(b43-firmware) to use on my laptop as it's not in
7.457924] systemd-udevd[1428]: renamed network interface eth0 to enp11s0
while my wireless NIC stays named as always was (wlan0):
[7.822350] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[7.838741] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1
[7.838760] b43-phy0 debu
; infrastructure mode with no problems (wpa2). However, here's the
> official page:
>
> http://linuxwireless.org/en/users/Drivers/b43
>
> according to
>
> http://linuxwireless.org/en/users/Drivers/b43/devices
>
> your card (14E4:4311) is supported.
>
> You nee
the latest firmware. I
>> > used to get this error with a particular cisco access point and it went
>> > away when I updated to 2.6.34 kernel series and also updated the
>> > firmware. Have a good look in here to find the latest suitable firmware
>> > for your NI
On Tue, Apr 20, 2010 at 5:21 AM, Mick wrote:
> Hmm, it's stuck in US mode for some reason. Firmware?
Maybe you're right, I googled and found some info that the old
broadcom driver didn't support channels 12 and 13 for some reason with
certain hardware. However, it appea
might be as simple as doing "iwconfig wlan0 rate 54M
fixed". However, I just noticed that the linuxwireless page about b43
has changed since yesterday; there are new instructions regarding the
versions of firmware and fwcutter tool to use (011), and specific info
regarding kernel 2.6.
have functioning NIC's now.
>
> Glad you got this sorted.
>
> Is there a conclusion if we should be planning to move away from x11-
> drivers/radeon-ucode, net-wireless/b43-fwcutter, et al and use sys-
> kernel/linux-firmware instead?
> --
> Regards,
> Mick
I'm not the right guy to make the call but I think the fact that the
r8169 firmware exists only in linux-firmware (as far as Portage
packages) says something.
- Grant
rs 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > My yes-or-no question: does the appearance of "wlan0" imply that
> > my new kernel drivers are the right ones for this particular D-Link
> > WiFi adapter?
>
> It's certainly a great sign, but it may
fortunately it's a 14e4:4320/ with BCM4306/2 Chip set (4306 Rev 2), so
it
requires the b43-legacy driver, and only firmware version FW10 supports the
hardware from what I can tell.
It just seems to me that I went from a working wireless on 2.6.30 to a
non-working wireless on 2.6.34. I'
Hi~
I drive my bcm4312 by module b43 and firmware , learned from
http://linuxwireless.org/en/users/Drivers/b43
It is drive successfully, but when I start my openvpn , it looks like that
the kernel is crashed.
The kernel log :
[13446.745188] sched: RT throttling activated
[15653.842657] tun
age possibly suggests uses "-Dbroadcom", but the
following supports "-Dwext" since I have the b43legacy driver working (firmware
extracted using b43-fwcutter a while back; dmesg reports version 0x127).
http://linuxwireless.org/en/users/Drivers/b43
I have both the iwconfig ut
o use with your card?
>> http://linuxwireless.org/en/users/Drivers/b43
>
> Yes. Unfortunately it's a 14e4:4320/ with BCM4306/2 Chip set (4306 Rev 2), so
> it
> requires the b43-legacy driver, and only firmware version FW10 supports the
> hardware from what I can tell.
>
&g
On Fri, Oct 24, 2014 at 10:44 AM, Mick wrote:
> I just enabled the wireless adaptor and I connected to the neighboor's AP fine
> with my b43 firmware (BCM4312 chipset):
So is this a module in your kernel? It wasn't clear to me from your reply
--
Douglas J Hunley (doug.
it rate to 54Mb but card suddenly stopped working :-(.
So, I revert back to previous mode. Now i can see variable rates. Network
is working
fine. So, i guess bit rate doesn't make much difference(does it ??).
> However, I just noticed that the linuxwireless page about b43
> has changed si
wpa_supplicant man page possibly suggests uses "-Dbroadcom", but the
following supports "-Dwext" since I have the b43legacy driver working
(firmware extracted using b43-fwcutter a while back; dmesg reports
version 0x127).
http://linuxwireless.org/en/users/Drivers/b43
I
ot; )
> iwconfig_wlan0="mode managed"
> wpa_timeout_wlan0=15
>
> Both these were based on configurations I found while researching gentoo
> wireless configurations:
>
> http://en.gentoo-wiki.com/wiki/Wireless_Networking
>
> the wpa_supplicant man page possibly suggest
ECTED]> wrote:
>
>
>
>
>
>
>
>
>
> I'm trying to get my Broadcom 4311 b/g card to work with the native kernel
> driver (bcm43xx) and b43-fwcutter but it's does not work. I placed the
> extracted firmware code in /lib/firmware and dmesg states that it failed
systems have functioning NIC's now.
Glad you got this sorted.
Is there a conclusion if we should be planning to move away from x11-
drivers/radeon-ucode, net-wireless/b43-fwcutter, et al and use sys-
kernel/linux-firmware instead?
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
>
> []'s
>
> On Dec 13, 2007 6:53 PM, Marzan, Richard non Unisys
>
> <[EMAIL PROTECTED]> wrote:
> > I'm trying to get my Broadcom 4311 b/g card to work with the native
> > kernel driver (bcm43xx) and b43-fwcutter but it's does not work. I placed
&g
dmesg says only:
tom@tombook ~ $ dmesg | grep -i firmware
[0.099927] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
I already have linux-firmware in my system, just put brcmsmac in my kernel
(was set to =n), and still have same result tough.
Only difference is that rfkill list all now
cular D-Link
>>> WiFi adapter?
>>
>> It's certainly a great sign, but it may or may not be enough. I'm by no
>> means an expert, but I believe I have to install some extra firmware
>> (b43-firmware) to use on my laptop as it's not in the kernel (un
On 03/18/2012 02:29 AM, 林守磊 wrote:
> Hi~
>
> I drive my bcm4312 by module b43 and firmware , learned from
> http://linuxwireless.org/en/users/Drivers/b43 It is drive
> successfully, but when I start my openvpn , it looks like that the
> kernel is crashed.
> The kernel log
ers.
Do you run a modular kernel or compile everything in? I do the latter,
and on 3.17.0 turning this off caused the b43 firmware for my wifi
card to not load. I'll give you that 3.17.0 has other issues, but..
--
Douglas J Hunley (doug.hun...@gmai
On Tuesday 20 April 2010 22:24:41 Mick wrote:
> On Tuesday 20 April 2010 15:25:14 Paul Hartman wrote:
> > On Tue, Apr 20, 2010 at 5:21 AM, Mick wrote:
> > > Hmm, it's stuck in US mode for some reason. Firmware?
> >
> > Maybe you're right, I googled and f
formation: Len=78
> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [d0] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [13c] Virtual Channel
> Capabilities: [160] Device Serial Number 00-00-ca
nt as /class/input/input5
Clocksource tsc unstable (delta = 62992454 ns)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 220k freed
b43-phy0: Broadcom 4318 WLAN found
phy0: Selec
e wlan0 - I'd have to stop wlan0, rfkill unblock all, then start
wlan0 again to get a connection. Very annoying.
Using KNetworkManager I have found it on occasion being blocked, but mostly
unblocked.
> Also, what is your wireless NIC? It may be worth checking that you are still
> usin
uestion: does the appearance of "wlan0" imply that
> >>> my new kernel drivers are the right ones for this particular D-Link
> >>> WiFi adapter?
> >>
> >> It's certainly a great sign, but it may or may not be enough. I'm by no
>
00 seconds
>
> I'm not sure what 'sit0' is, but it doesn't seem to affect the outcome.
>
> HTH others who may face the same problem.
Thanks for sharing this Philip. I was surprised to see that firmware for NICs
are meant to be added in this kernel config option. I th
e *not* on?
Also, what is your wireless NIC? It may be worth checking that you are still
using the correct driver for your wireless chipset?
http://linuxwireless.org/en/users/Drivers/b43
and that you are using the latest firmware?
http://linuxwireless.org/en/users/Drivers/b43#Device_firmware_installation
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
On 13 Dec 2007, at 20:53, Marzan, Richard non Unisys wrote:
I'm trying to get my Broadcom 4311 b/g card to work with the native
kernel driver (bcm43xx) and b43-fwcutter but it's does not work. I
placed the extracted firmware code in /lib/firmware and dmesg
states that it fail
ortunately I did not find
anything that applied to my situation.
One thing different about my new kernel config is that because I have a
Broadcom card, I moved to the new b43 driver instead of the old
b43_legacy driver. I am using version 4 firmware however I had the same
problem with version
d think that my problem is that I am unable
> to decrypt WEP packets for any device other than my own. This is a
> simple 64 bit WEP network in my home. Unfortunately I did not find
> anything that applied to my situation.
>
> One thing different about my new kernel config is th
it WEP network in my home. Unfortunately I did not find
anything that applied to my situation.
One thing different about my new kernel config is that because I have a
Broadcom card, I moved to the new b43 driver instead of the old
b43_legacy driver. I am using version 4 firmware however I had the sam
On Monday 19 April 2010 20:24:18 you wrote:
> On Monday 19 April 2010 18:26:14 Stroller wrote:
> > On 18 Apr 2010, at 23:35, Mick wrote:
> > > ...
> > > OK, I found what the problem was ... the AP is currently transmitting
> > > on channel 13, which it seems is
for any device other than my own. This is a
simple 64 bit WEP network in my home. Unfortunately I did not find
anything that applied to my situation.
One thing different about my new kernel config is that because I have a
Broadcom card, I moved to the new b43 driver instead of the old
b43_l
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=b43-pci-bridge latency=0
resources: irq:17 memory:f090-f0903fff
and further down:
...
*-network
description: Wireless interface
physical id: 4
logical name
device other than my own. This
is a simple 64 bit WEP network in my home. Unfortunately I did not
find anything that applied to my situation.
One thing different about my new kernel config is that because I have
a Broadcom card, I moved to the new b43 driver instead of the old
b43_legacy driv
v1] Device Serial Number c3-09-04-ff-ff-d7-70-1a
Capabilities: [16c v1] Power Budgeting
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
===
From lshw:
==
*-pci:2
descri
1.14
net-nds/rpcbind-0.2.0-r1
net-proxy/dante-1.1.19-r4
net-proxy/ntlmaps-0.9.9-r2
net-proxy/tsocks-1.8_beta5-r5
net-wireless/b43-fwcutter-017
net-wireless/crda-1.1.2-r3
net-wireless/rfkill-0.5
net-wireless/wireless-regdb-20130213
net-wireless/wireless-tools-30_pre9
net-wireless/wpa_supplicant-2.0-
70 matches
Mail list logo
