Hi
I've now upgraded to broadcom-sta-dkms 6.30.223.248-3.3 and running
kernel 4.1.0-rc3 and everything works just fine. Thanks!
Br,
Anders
> > DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-rc1 (x86_64)
> > Sat May 2 20:28:51 CEST 2015
> > /bin/sh: line 0: [: : integer expression expected
> > /bin/sh: line 0: [: : integer expression expected
>
> I cannot reproduce this with 4.1.0-rc2 and dkms. Might be a locale
>
Hi!
Thank you very much for adding this patch!
Greetings,
Bruno
On 2015-05-06 21:38, Eduard Bloch wrote:
> On Wed, 29 Apr 2015 16:44:14 +0200 Bruno Bierbaumer
> wrote:
>> Hello!
>> I would say it fits in here, because the problem first appears with
>> Linux 3.18 and the bug is about supporting
On Wed, 29 Apr 2015 16:44:14 +0200 Bruno Bierbaumer wrote:
> Hello!
> I would say it fits in here, because the problem first appears with
> Linux 3.18 and the bug is about supporting Linux 3.18+.
> Fixing a bug that we know of as we go also sounds like a good idea.
> Also just my opinion.
Ok, as
Hallo,
* Anders Hedlund [Sat, May 02 2015, 08:51:58PM]:
> Hi,
> I'm trying out the interdiff by Eduard but get the below error when trying
> to install the new package. Do you guys know what's wrong?
Partially...
> DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-rc1 (x86_64)
> Sat Ma
Hi,
I'm trying out the interdiff by Eduard but get the below error when trying
to install the new package. Do you guys know what's wrong?
DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-rc1 (x86_64)
Sat May 2 20:28:51 CEST 2015
/bin/sh: line 0: [: : integer expression expected
/bin/s
Hello!
I would say it fits in here, because the problem first appears with
Linux 3.18 and the bug is about supporting Linux 3.18+.
Fixing a bug that we know of as we go also sounds like a good idea.
Also just my opinion.
Sounds like a good plan to wait for any reaction by the maintainer.
Greeting
Hallo,
* Bruno Bierbaumer [Wed, Apr 29 2015, 02:49:23PM]:
> Yes, there are many reports about this lockup.
Maybe, but as said, it was not strictly in the scope of this bugreport.
It deserves a new bug report with important severity, IMHO.
> Original one is here:
> https://bugs.gentoo.org/show_bug
Yes, there are many reports about this lockup.
Original one is here:
https://bugs.gentoo.org/show_bug.cgi?id=523326#c24
I don't think it 3.18 specific and Gentoo and Arch are definitely also
applying the patch to broadcom-sta for all kernel versions.
See:
-
https://sources.gentoo.org/cgi-bin/view
Hallo,
* Bruno Bierbaumer [Wed, Apr 29 2015, 01:14:36PM]:
> Hallo Eduard,
> Thank you for working on this bug!
>
> Did you forgot this patch:
> https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6#file-broadcom-sta-6-30-223-248-linux-3-18-null-pointer-crash-patch
> in the NMU?
Well, kind of. I
Hallo Eduard,
Thank you for working on this bug!
Did you forgot this patch:
https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6#file-broadcom-sta-6-30-223-248-linux-3-18-null-pointer-crash-patch
in the NMU?
Greetings,
Bruno
On 2015-04-29 12:54, Eduard Bloch wrote:
> Dear Maintainer,
>
> afte
Dear Maintainer,
after a long period of inactivity, I decided to NMU this package with
the mentioned fixes and also kernel 4.0 support.
The NMU is not effective yet, the package is in the 10-day DELAYED queue
so you have lots of times to abort this action by uploading an official
version.
Interd
12 matches
Mail list logo