Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Gábor Stefanik
On Fri, Feb 26, 2010 at 8:33 AM, Nathan Schulte rekl...@gmail.com wrote: 2010/1/25 Gábor Stefanik netrolller...@gmail.com A few things to check: -Is this on PhoenixBios? I have the same laptop as Lucas, a Dell Vostro 1510.  As Lucas has mentioned, this is indeed a PhoenixBIOS -Does

Re: Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Gábor Stefanik
On Fri, Feb 26, 2010 at 12:12 PM, rekl...@gmail.com wrote: On Feb 26, 2010 3:23am, Gábor Stefanik netrolller...@gmail.com wrote: The firmware version included in 4.174.64.19 is 478.104 (notice that is is not 4178.104, but 478.104 - the driver and firmware versions are not related!). Ah yes,

Re: Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Gábor Stefanik
2010/2/26 Nathan Schulte rekl...@gmail.com: I apologize for so many messages. I wanted to note that the reasoning for lsmod only showing the ntfs module, is due the fact that ntfs (and b43 and ssb) are the only drivers compiled as modules. When loading b43 without mmiotrace running, I receive

Re: Re: Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Gábor Stefanik
On Fri, Feb 26, 2010 at 4:04 PM, rekl...@gmail.com wrote: On Feb 26, 2010 8:49am, Gábor Stefanik netrolller...@gmail.com wrote: However, you did not do what I requested - before the 2nd mmiotrace, load and unload wl (the hybrid driver), not b43 - it is wl that appears to make the card work.

Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Larry Finger
On 02/26/2010 09:27 AM, Gábor Stefanik wrote: On Fri, Feb 26, 2010 at 4:13 PM, rekl...@gmail.com wrote: On Feb 26, 2010 9:08am, Gábor Stefanik netrolller...@gmail.com wrote: That's odd... the error only occurs when you stop the mmiotrace?! Yes, the error only occurs when I stop the mmiotrace

Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Gábor Stefanik
2010/2/26 Larry Finger larry.fin...@lwfinger.net: On 02/26/2010 09:27 AM, Gábor Stefanik wrote: On Fri, Feb 26, 2010 at 4:13 PM,  rekl...@gmail.com wrote: On Feb 26, 2010 9:08am, Gábor Stefanik netrolller...@gmail.com wrote: That's odd... the error only occurs when you stop the mmiotrace?!

[PATCH] b43: Make driver fall back gracefully to PIO mode after fatal DMA errors

2010-02-26 Thread Larry Finger
Subject: Make b43 driver fall back gracefully to PIO mode after fatal DMA errors From: Linus Torvalds torva...@linux-foundation.org Date: Fri, 26 Feb 2010 10:34:27 -0800 (PST) This makes the b43 driver just automatically fall back to PIO mode when DMA doesn't work. The driver already told the

Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Gábor Stefanik
2010/2/26 Chris Vine ch...@cvine.freeserve.co.uk: On Fri, 26 Feb 2010 18:22:26 +0100 Gábor Stefanik netrolller...@gmail.com wrote: Note that enabling MMIO trace touches quite a few areas of the kernel rather hard - for example, it AFAIK disables SMP. I wonder if acpi=off or blacklisting

Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Chris Vine
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

Direct probe to AP ... timed out with b43legacy

2010-02-26 Thread van77live
Hello, I am trying to reuse an old HP zd7055ea laptop, which has a BCM4303 card. I am using Ubuntu 9.10 (Karmic). It detected the card on its restricted drivers manager, and installed it correctly. NetworkManager detects the card and lists the detected APs. But it doesn't connect, and then

Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Gábor Stefanik
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 would be special-casing for both 4312 and 4325, at least according to the MMIO trace

Re: LP-PHY Fatal DMA error 0x00000800 on non-ULV Core 2 Duo?!?!!??!

2010-02-26 Thread Larry Finger
On 02/26/2010 07:41 PM, Gábor Stefanik 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 would be special-casing for both