Hello.
As of Kernel 3.15 a long standing bug in b43 affecting the way it handles rather recent firmware started to become manifest in failure of the driver, see e. g. [0,1]. A patch is available [2] but hasn't made it into 3.15.2.
A version of package linux I recompiled applying the patch works flawlessly, imho other workarounds like sticking with 3.14 or using older firmware are less reasonable.
So I'd like to ask whether there are any chances to get this patch into the linux package. Attaching a file that can be used in prepare() the usual way (patch -p1 -i "${srcdir}/...").
Regards,
Peter Mattern
[0] http://lists.infradead.org/pipermail/b43-dev/2014-June/003471.html [1] http://bbs.archlinux.org/viewtopic.php?id=183114 [2] https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=2fc68e...
On 06/29, Peter Mattern wrote:
Hello.
As of Kernel 3.15 a long standing bug in b43 affecting the way it handles rather recent firmware started to become manifest in failure of the driver, see e. g. [0,1]. A patch is available [2] but hasn't made it into 3.15.2.
A version of package linux I recompiled applying the patch works flawlessly, imho other workarounds like sticking with 3.14 or using older firmware are less reasonable.
So I'd like to ask whether there are any chances to get this patch into the linux package. Attaching a file that can be used in prepare() the usual way (patch -p1 -i "${srcdir}/...").
Regards,
Peter Mattern
[0] http://lists.infradead.org/pipermail/b43-dev/2014-June/003471.html [1] http://bbs.archlinux.org/viewtopic.php?id=183114 [2] https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=2fc68e...
The b43 driver is not officially supported by Arch.
Hong
According to [tomk][1], this was fixed as of last night's kernel (3.15.2).
[1]: https://bbs.archlinux.org/viewtopic.php?pid=1430902#p1430902
On Sun, Jun 29, 2014, at 01:23 PM, Hong Shick Pak wrote:
On 06/29, Peter Mattern wrote:
Hello.
As of Kernel 3.15 a long standing bug in b43 affecting the way it handles rather recent firmware started to become manifest in failure of the driver, see e. g. [0,1]. A patch is available [2] but hasn't made it into 3.15.2.
A version of package linux I recompiled applying the patch works flawlessly, imho other workarounds like sticking with 3.14 or using older firmware are less reasonable.
So I'd like to ask whether there are any chances to get this patch into the linux package. Attaching a file that can be used in prepare() the usual way (patch -p1 -i "${srcdir}/...").
Regards,
Peter Mattern
[0] http://lists.infradead.org/pipermail/b43-dev/2014-June/003471.html [1] http://bbs.archlinux.org/viewtopic.php?id=183114 [2] https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=2fc68e...
The b43 driver is not officially supported by Arch.
Hong
On 30/06/2014 05:43, neersighted wrote:
According to [tomk][1], this was fixed as of last night's kernel (3.15.2).
This message states that the problem was *not* fixed in 3.15.2.
On 29/06/2014 22:23, Hong Shick Pak wrote:
The b43 driver is not officially supported by Arch. Hong
Seems rather odd to me. Sure, the firmware is available via AUR only. But it's a regular mainline kernel module and the firmware cutter is in the repos, too. So any official sources for this?
Btw., meanwhile the patch is in 3.16...
You're right, he edited his post. I rolled back to firmware 5.100.138 and kernel 3.12.9 and seem to be doing okay.
On Sat, Jul 5, 2014, at 10:10 AM, Peter Mattern wrote:
On 30/06/2014 05:43, neersighted wrote:
According to [tomk][1], this was fixed as of last night's kernel (3.15.2).
This message states that the problem was *not* fixed in 3.15.2.
On 29/06/2014 22:23, Hong Shick Pak wrote:
The b43 driver is not officially supported by Arch. Hong
Seems rather odd to me. Sure, the firmware is available via AUR only. But it's a regular mainline kernel module and the firmware cutter is in the repos, too. So any official sources for this?
Btw., meanwhile the patch is in 3.16...
arch-general@lists.archlinux.org