Unfortunately I do not control it .
Thank you anyway,
Wenceslao
El 05/11/11 14:28, Uwe Kleine-König escribió:
hI,
On Wed, May 11, 2011 at 08:52:51AM +0200, Wenceslao González-Viñas wrote:
Neither I am a programmer nor I am having much time. If it only
weren't latter, it wouldn't be fair to
hI,
On Wed, May 11, 2011 at 08:52:51AM +0200, Wenceslao González-Viñas wrote:
> Neither I am a programmer nor I am having much time. If it only
> weren't latter, it wouldn't be fair to ask to other people to fix
> the problem. Of course, I am ready to test patches (although I did
> only once, I h
Neither I am a programmer nor I am having much time. If it only weren't
latter, it wouldn't be fair to ask to other people to fix the problem.
Of course, I am ready to test patches (although I did only once, I hope
to be able to do it again...).
Thank you any way from your suggestion.
Whom I
Hi,
Wenceslao González-Viñas wrote:
> From your last post concerning this bug, I did not get what should
> be the procedure from now on.
I would suggest looking at the driver code, adding printk calls to
find out what it reads from the NVRAM (to confirm Ben's hypothesis),
and if it is blank, com
On Wed, 2011-05-11 at 06:55 +0200, Wenceslao González-Viñas wrote:
> Dear Ben and all,
>
> From your last post concerning this bug, I did not get what should be
> the procedure from now on. Should the bug be reported to another
> package ?
[...]
I passed it on to the brcm80211 developers.
B
Dear Ben and all,
From your last post concerning this bug, I did not get what should be
the procedure from now on. Should the bug be reported to another
package ? Or, is there something which is lacking that does not depend
on you or other debian maintainers (eg. firmware or non-free packag
So, then this means that the problem is still there ...
... What else could I try?
Wenceslao
Ben Hutchings ha escrito:
On Sat, 2011-04-30 at 15:48 +0200, Wenceslao González-Viñas wrote:
Dear Ben,
If you want, I could try with this modified of wireless-regdb ... Just
tell me how to obtain
On Sat, 2011-04-30 at 15:48 +0200, Wenceslao González-Viñas wrote:
> Dear Ben,
>
> If you want, I could try with this modified of wireless-regdb ... Just
> tell me how to obtain it .
[...]
I did that before uploading the first version, so you already have it.
Ben.
--
Ben Hutchings
Once a job
Dear Ben,
If you want, I could try with this modified of wireless-regdb ... Just
tell me how to obtain it .
Best and thanks again,
Wenceslao
Ben Hutchings ha escrito:
On Sat, 2011-04-30 at 13:30 +0200, Arend van Spriel wrote:
On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote:
> Af
I do not understand.
I did of course as root. The rule in udev was not defined, though. I
defined it , I restarted it , but no change. It does not matter if I
use EU, ES or whatever. ??
Anyway, I think that is not iw / udev or similar problem as if I put a
ralink stick, it works per
On Sat, 2011-04-30 at 13:30 +0200, Arend van Spriel wrote:
> On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote:
> > After
> > iw reg set EU
> > I do not get any answer in dmesg log.
>
> I assume you did this as root or used sudo. You may have to check
> whether you have the proper udev rules
On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote:
After
iw reg set EU
I do not get any answer in dmesg log.
I assume you did this as root or used sudo. You may have to check
whether you have the proper udev rules in place. See
http://wireless.kernel.org/en/developers/Regulatory/CRDA#Let
After
iw reg set EU
I do not get any answer in dmesg log.
and if I do (after) : iw reg get , I get:
country 98:
(2402 - 2472 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 17)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5600 @ 40), (N/A, 20), DFS
(5650 - 5710
On 04/30/2011 07:04 AM, Ben Hutchings wrote:
I looked at the driver source code and there is certainly an attempt to
use a country code from NVRAM. But maybe it hasn't actually been read
from NVRAM at the point this is done. 'US' seems to be the default if
the country code is blank.
Ben.
Pl
Wenceslao González-Viñas wrote:
[...]
> [ 330.205983] brcm80211: module is from the staging directory, the quality
> is unknown, you have been warned.
> [ 330.212186] brcm80211 :03:00.0: PCI INT A -> GSI 17 (level, low) ->
> IRQ 17
> [ 330.212195] brcm80211 :03:00.0: setting latency ti
15 matches
Mail list logo
