On Wed, 24 Mar 2010 03:31:42 +0700
Chris Lopes clo...@gmail.com wrote:
Ok. I got my wireless card to detect networks again. I also had a
theory and tried to reproduce the problem, and was successful in doing
so. Here are my steps to reproduce:
1) Have Vista running and connected to a
On Tue, 23 Mar 2010 23:37:45 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
(On 2.6.33, b43 works around this by falling back to PIO.)
I think it requires 2.6.34 for this (currently 2.6.34-rc2).
Chris
___
Bcm43xx-dev mailing list
On Wed, 17 Mar 2010 20:09:41 +0100
Miklos Vajna vmik...@frugalware.org wrote:
Hi,
I recently upgraded to 2.6.33, then 2.6.34-rc1, but both have the same
bugs:
1) The earlier mentioned problem is still there, the b43 driver
disconnects if no WPA is used by the AP.
(This is not an issue
On Thu, 18 Mar 2010 00:26:32 +
Chris Vine ch...@cvine.freeserve.co.uk wrote:
[snip]
I suggest you add to this thread in linux-acpi (and lkml), that you
can reproduce the problem, and it might then get some attention:
http://marc.info/?l=linux-kernelm=126879129905898w=2 .
Ah, I see you
On Mon, 8 Mar 2010 17:22:26 +
Chris Vine ch...@cvine.freeserve.co.uk wrote:
I have noticed that although my BCM4312 802.11b/g [14e4:4315] wireless
device works using the PIO option in 2.6.33, it breaks after a suspend
or hibernate. Attempts to bring up the wlan0 interface with
'ifconfig
I have noticed that although my BCM4312 802.11b/g [14e4:4315] wireless
device works using the PIO option in 2.6.33, it breaks after a suspend
or hibernate. Attempts to bring up the wlan0 interface with
'ifconfig wlan0 up' after suspension or hibernation results in the
following message (although
On Sun, 28 Feb 2010 14:44:12 -0500
William Bourque william.bour...@polymtl.ca wrote:
New test patch attached.
Please CC linux-wirel...@vger.kernel.org on further e-mails,
bcm43xx-dev appears to be having problems.
Hmm... I don't know if it is only coincidence, but this one seems to
On Sun, 28 Feb 2010 15:51:14 -0500
William Bourque william.bour...@polymtl.ca wrote:
Chris Vine wrote:
On Sun, 28 Feb 2010 19:58:11 +0100
Michael Buesch m...@bu3sch.de wrote:
It says 8k for all of my devices there. So an MMIO write to 0x2000
and above writes to completely random memory
On Sat, 27 Feb 2010 02:41:48 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
Someone should test the following:
-Open drivers/ssb/driver_chipcommon_pmu.c
-In ssb_pmu_init, replace 0x4325 with 0x4312. (This is not the correct
way to fix this, but should be enough for a test. The correct fix
On Fri, 26 Feb 2010 23:03:28 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
I suspect that timing is not the true reason for the problem, rather,
there is a race condition between PhoenixBIOS and b43, for which wl
probably uses a (firmware?) workaround.
I meant that it is the reason for
On Mon, 21 Dec 2009 17:18:01 -0500
William Bourque william.bour...@polymtl.ca wrote:
Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary.
On Sat, 19 Dec 2009 10:43:29 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
Hi,
If possible, please test this patch starting from a cold boot. It is a
variation of something we tried earlier, but enough different to try
it.
Thanks,
Larry
I applied this to 2.6.32.2 and it didn't
On Sat, 28 Nov 2009 20:59:32 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
It is not my day. This statement is the one that I wanted.
Please see if this one does any good.
It doesn't improve things for me, I'm afraid.
Chris
___
Bcm43xx-dev
On Fri, 27 Nov 2009 14:57:12 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
Please try this patch without the pm_qos patch to see if it helps.
The Broadcom wl driver does this during the setup.
Thanks,
Larry
It doesn't improve things I am afraid.
Chris
On Mon, 23 Nov 2009 22:58:36 -0500
William Bourque william.bour...@polymtl.ca wrote:
Larry Finger wrote:
One last check. I would appreciate receiving answers to the
following questions. These questions apply to anyone else with this
problem.
Does the pm_qos patch help your fatal DMA
On Tue, 24 Nov 2009 10:50:13 -0500
William Bourque william.bour...@polymtl.ca wrote:
[snip]
I was using the B43 (GPL) driver but with the proprietary firmware
extracted from Broadcom crap with bfwcutter.
The proprietary driver provided by Broadcom (what you refer as wl?)
fails to even detect
On Tue, 24 Nov 2009 11:43:32 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
On 11/24/2009 10:58 AM, William Bourque wrote:
I did tried before, it succesfully built, it was loading (modprobe)
correctly but no new interface was registered by it.
However, I might have done something
On Tue, 24 Nov 2009 13:06:43 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
This E-mail is to summarize what I have learned to date.
The pm_qos change does nothing useful. It may have helped a little,
but the side effects are far worse than the benefits.
Most systems work better with
On Sat, 21 Nov 2009 00:15:12 +
Chris Vine ch...@cvine.freeserve.co.uk wrote:
WARM BOOT FROM KERNEL WITH WL MODULE INSTALLED
The patched kernel makes no change on a warm boot in the sense that
if I warm boot after initialising the wireless device with the wl
module then the b43 module
On Fri, 20 Nov 2009 06:43:05 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
One last check. I would appreciate receiving answers to the following
questions. These questions apply to anyone else with this problem.
Does the pm_qos patch help your fatal DMA error problem,
particularly when
On Sun, 15 Nov 2009 15:42:25 -0800 (PST)
Linus Torvalds torva...@linux-foundation.org wrote:
On Sun, 25 Oct 2009, Chris Vine wrote:
And Chris, just out of interest - does FORCE_PIO work for you too?
Yes.
So I've been trying to debug this, but no real luck. The Broadcom
official
On Sat, 14 Nov 2009 09:52:15 +
Andrew Benton b3n...@gmail.com wrote:
It was working fine last night but I can't get that kernel to connect
today. Nothing has changed, I can see no reason why it was working
and isn't working now. It feels like a hardware problem.
I'm recompiling with a
On Sun, 25 Oct 2009 19:30:56 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
Also try apic=off
acpi=off (IIRC another DMA error victim, but with error code
0x0800 had ACPI clobbering his DMA).
Specifically me, and I resolved it, until it is fixed, by blacklisting
the 'processor' ACPI
On Sun, 25 Oct 2009 22:40:50 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
Another thing to test: boot into Windows (or any other OS where the
card works), initialize the card, reboot (not cold-boot) into Linux,
try to load b43. If this succeeds, then we are missing something in
the init
On Sun, 25 Oct 2009 21:57:08 +
Chris Vine ch...@cvine.freeserve.co.uk wrote:
On Sun, 25 Oct 2009 22:40:50 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
Another thing to test: boot into Windows (or any other OS where the
card works), initialize the card, reboot (not cold-boot
On Sun, 25 Oct 2009 15:08:11 -0700 (PDT)
Linus Torvalds torva...@linux-foundation.org wrote:
On Sun, 25 Oct 2009, Chris Vine wrote:
On Sun, 25 Oct 2009 22:40:50 +0100 Gábor Stefanik
netrolller...@gmail.com suggested:
Another thing to test: boot into Windows (or any other OS where
On Fri, 23 Oct 2009 08:48:38 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
On 10/23/2009 05:46 AM, Chris Vine wrote:
I will probably do that (maybe), but nonetheless I have identified
the offending ACPI module. If I blacklist the 'processor' module
then b43 works. I strongly
On Fri, 23 Oct 2009 06:25:33 +0200
Peter Stuge pe...@stuge.se wrote:
Chris Vine wrote:
The problem is not with b43, but with ACPI. The debugging will
need to be done by that set of devs.
OK. I may try blacklisting different ACPI modules and see if I can
identify which one
On Thu, 22 Oct 2009 17:06:53 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
Chris,
Michael was right in that my previous debug messages were badly setup.
Please try the attached patch as a replacement for the previous one.
It will look at the data that is pushed into the DMA
On Thu, 22 Oct 2009 17:55:55 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
On 10/22/2009 05:46 PM, Chris Vine wrote:
No, I hadn't. But on doing so, booting with acpi=off makes b43 work
correctly.
In the light of this, do you want me to continue with this
debugging? I have
On Wed, 21 Oct 2009 14:30:49 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
On 10/20/2009 04:56 PM, Chris Vine wrote:
On Mon, 19 Oct 2009 16:53:24 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
This set of dmesg outputs was better; however, please set
CONFIG_B43_DEBUG=y in your
On Wed, 21 Oct 2009 18:05:31 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
Then try this patch without the previous one. It will generate some
warnings but they are harmless.
Working warm boot:
cfg80211: Using static regulatory domain
On Mon, 19 Oct 2009 16:53:24 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
This set of dmesg outputs was better; however, please set
CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel.
Please post the full dmesg for warm and cold reboot.
For a warm boot it is:
cfg80211:
On Mon, 19 Oct 2009 11:55:01 +0200
Michael Buesch m...@bu3sch.de wrote:
On Monday 19 October 2009 11:46:00 Michael Buesch wrote:
On Monday 19 October 2009 11:37:56 Chris Vine wrote:
On Sun, 18 Oct 2009 22:14:31 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
I see no difference
On Mon, 19 Oct 2009 11:55:01 +0200
Michael Buesch m...@bu3sch.de wrote:
On Monday 19 October 2009 11:46:00 Michael Buesch wrote:
On Monday 19 October 2009 11:37:56 Chris Vine wrote:
On Sun, 18 Oct 2009 22:14:31 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
I see no difference
On Mon, 19 Oct 2009 12:12:59 +0200
Michael Buesch m...@bu3sch.de wrote:
Post the full log, please, so we can _verify_ that it's irrelevant.
Everything else is just bad guesswork.
Full marks for attitude. What do you take, for this purpose, as
being the full log? All of /var/log/messages,
On Mon, 19 Oct 2009 16:53:24 -0500
Larry Finger larry.fin...@lwfinger.net wrote:
This set of dmesg outputs was better; however, please set
CONFIG_B43_DEBUG=y in your configuration and rebuild the kernel.
Please post the full dmesg for warm and cold reboot.
My original posting (16 October) gave
On Fri, 16 Oct 2009 21:35:54 +0200
Gábor Stefanik netrolller...@gmail.com wrote:
Could you please try the real wireless-testing tree (as opposed to
compat-wireless)?
Also, what I noticed is that everyone with this problem appears to
have an Intel Atom CPU... weird. Maybe something weird is
On Fri, 16 Oct 2009 21:35:54 +0200
Gábor Stefanik netrolller...@gmail.com wrote:
Could you please try the real wireless-testing tree (as opposed to
compat-wireless)?
Also, what I noticed is that everyone with this problem appears to
have an Intel Atom CPU... weird. Maybe something weird is
On Sat, 17 Oct 2009 08:24:59 -0400
Gene Heskett gene.hesk...@verizon.net wrote:
NDI what 'filter' you are using, but I just checked back over a
30 day corpus of this list, and no message in that 30 days even
rated above a 0 for spaminess, all were in the -2.3 to -2.5 range
according to
Hi,
I have a Levono S-12 Netbook, which has the Atom N270 processor and a
Broadcom 14e4:4315 wireless chip with low power PHY. lspci -vnn | grep
14e4 gives:
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5906M
Fast Ethernet PCI Express [14e4:1713] (rev 02)
03:00.0
On Fri, 16 Oct 2009 9:45:40 -0400
fre...@carolina.rr.com wrote:
2.6.32-rc? and wireless-compat was thought to work as well as
wireless-testing ... hmmm
Ah right. I had been trying 2.6.32-rc4 by itself and compat-wireless
with 2.6.31. If I build compat-wireless on top of 2.6.32-rc.4 the dma
42 matches
Mail list logo
