Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

2018-04-05 Thread Jape Person
On 04/05/2018 12:00 PM, Ben Hutchings wrote:
> On Thu, 2018-04-05 at 11:50 -0400, Jape Person wrote:
>> On 04/05/2018 03:43 AM, Ben Hutchings wrote:
>>> On Wed, 2018-04-04 at 19:57 -0400, Jape Person wrote:
 In addition to these findings, has anyone noticed this having an
 adverse effect on file transfers? I suspect what I have seen is
 due to my particular wireless hardware.
>>>
>>> [...]
>>>
>>> This is almost certainly an unrelated regression in the wireless
>>> driver.
>>>
>>> Ben.
>>>
>>
>> Of course, that makes more sense. I wonder if the problem with
>> the driver is elicited by the failure of the regulatory.db to be
>> loaded.
> 
> It still gets loaded by crda, so I don't think so.
> 
>> I don't know enough about this to have any real idea. Should I
>> attempt to report a bug against the driver?
> 
> Yes, you can submit a bug report about the driver upstream
> (linux-wirel...@vger.kernel.org).
> 
> Ben.
> 
I shall endeavor to do so!

Best regards,
JP



Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

2018-04-05 Thread Ben Hutchings
On Thu, 2018-04-05 at 11:50 -0400, Jape Person wrote:
> On 04/05/2018 03:43 AM, Ben Hutchings wrote:
> > On Wed, 2018-04-04 at 19:57 -0400, Jape Person wrote:
> > > In addition to these findings, has anyone noticed this having an
> > > adverse effect on file transfers? I suspect what I have seen is
> > > due to my particular wireless hardware.
> > 
> > [...]
> > 
> > This is almost certainly an unrelated regression in the wireless
> > driver.
> > 
> > Ben.
> > 
> 
> Of course, that makes more sense. I wonder if the problem with
> the driver is elicited by the failure of the regulatory.db to be
> loaded.

It still gets loaded by crda, so I don't think so.

> I don't know enough about this to have any real idea. Should I
> attempt to report a bug against the driver?

Yes, you can submit a bug report about the driver upstream
(linux-wirel...@vger.kernel.org).

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.



signature.asc
Description: This is a digitally signed message part


Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

2018-04-05 Thread Jape Person
On 04/05/2018 03:43 AM, Ben Hutchings wrote:
> On Wed, 2018-04-04 at 19:57 -0400, Jape Person wrote:
>> In addition to these findings, has anyone noticed this having an
>> adverse effect on file transfers? I suspect what I have seen is
>> due to my particular wireless hardware.
> [...]
> 
> This is almost certainly an unrelated regression in the wireless
> driver.
> 
> Ben.
> 
Of course, that makes more sense. I wonder if the problem with
the driver is elicited by the failure of the regulatory.db to be
loaded.

I don't know enough about this to have any real idea. Should I
attempt to report a bug against the driver?

Thank you for your reply.

JP



Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

2018-04-05 Thread Ben Hutchings
On Wed, 2018-04-04 at 19:57 -0400, Jape Person wrote:
> In addition to these findings, has anyone noticed this having an
> adverse effect on file transfers? I suspect what I have seen is
> due to my particular wireless hardware.
[...]

This is almost certainly an unrelated regression in the wireless
driver.

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.



signature.asc
Description: This is a digitally signed message part


Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

2018-04-04 Thread Jape Person
In addition to these findings, has anyone noticed this having an
adverse effect on file transfers? I suspect what I have seen is
due to my particular wireless hardware. (I didn't experiment
with Ethernet connections.)

I used

# sysctl net.ipv4.tcp_congestion_control=cubic

to switch tcp_congestion_control from bbr to cubic. This improve
file transfer speeds between my Debian testing system by roughly
100X on my LAN.

Just posting a note to indicate that -- at least for some people
-- this is a pretty serious bug.

Thanks,
JP



Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

2018-03-06 Thread Ben Hutchings
Control: retitle -1 wireless-regdb: Missing support for kernel direct loading
Control: severity -1 normal

On Wed, 07 Mar 2018 09:04:22 +0800 Paul Wise  wrote:
> Package: wireless-regdb
> Version: 2016.06.10-1
> Severity: serious
> 
> When I booted Debian's package of Linux kernel 4.15 I noticed this in
> my dmesg and systemd journal, it appears that the Linux kernel has
> changed the name (and possibly format) of the regulatory database from
> regulatory.bin to regulatory.db, making the current wireless-regdb
> incompatible with Linux 4.15.
> 
> kernel: cfg80211: failed to load regulatory.db
> kernel: platform regulatory.0: Direct firmware load for regulatory.db failed 
> with error -2
> kernel: platform regulatory.0: firmware: failed to load regulatory.db (-2)
> kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory 
> database

wireless-regdb works in conjunction with crda, and that's still
supported (so far as I can see).

The kernel can also now load a signed db without the need for crda. 
That's what's failing.  Unfortunately this was introduced without a
config option, so it will keep producing these error messages until
wireless-regdb is updated.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.



signature.asc
Description: This is a digitally signed message part


Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

2018-03-06 Thread Paul Wise
Package: wireless-regdb
Version: 2016.06.10-1
Severity: serious

When I booted Debian's package of Linux kernel 4.15 I noticed this in
my dmesg and systemd journal, it appears that the Linux kernel has
changed the name (and possibly format) of the regulatory database from
regulatory.bin to regulatory.db, making the current wireless-regdb
incompatible with Linux 4.15.

kernel: cfg80211: failed to load regulatory.db
kernel: platform regulatory.0: Direct firmware load for regulatory.db failed 
with error -2
kernel: platform regulatory.0: firmware: failed to load regulatory.db (-2)
kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

wireless-regdb depends on no packages.

wireless-regdb recommends no packages.

Versions of packages wireless-regdb suggests:
ii  crda  3.18-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part