netdev - Re: Wifi RTL8723bu driver test: failed to scan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171204165458.0bf87509@dell-desktop.home>
Date:   Mon, 4 Dec 2017 16:54:58 +0100
From:   Mylene JOSSERAND <mylene.josserand@...e-electrons.com>
To:     Jes Sorensen <jes.sorensen@...il.com>
Cc:     kvalo@...eaurora.org, linux-wireless@...r.kernel.org,
        netdev@...r.kernel.org,
        Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
        Maxime Ripard <maxime.ripard@...e-electrons.com>
Subject: Re: Wifi RTL8723bu driver test: failed to scan

Hello,

Le Tue, 28 Nov 2017 11:14:10 -0500,
Jes Sorensen <jes.sorensen@...il.com> a écrit :

> On 11/22/2017 04:51 AM, Mylene JOSSERAND wrote:
> > Hello Jes Sorensen,
> > 
> > I am currently testing a LM811 Wifi/BT USB dongle [1] on a Sinlinx
> > SinA33 Allwinner SoC board [2]. I saw that I should use the realtek
> > driver RTL8723BU for this USB dongle.
> > 
> > Currently, I am only testing the Wifi and the mainline driver
> > (kernel 4.14-rc7) does not seem to work. At least, the scanning
> > does not output anything.
> > 
> > I tested the driver recommended by LM Technologies [3] and it works
> > fine (scan, connect and ping are ok). Before investigating on the
> > differences between these two drivers, do you have any idea about
> > this issue?
> > 
> > Here are the commands and output I got with mainline's driver:  
> 
> I have not looked at the driver these LM Technologies people are
> referring to, but I am guessing it's the vendor code.

Yes, it is.

> 
> 8723bu is a little dicey because it has BT in the chip and if you
> enable that the two drivers need to interact, which rtl8xxxu
> currently doesn't know about. Check your dmesg output to make sure
> you don't have some BT thing loaded hijacking the chip.

Okay, I was also testing the BT so maybe, it was the case. I will
have a try without any BT drivers.

Anyway, thank you for your help!

Best regards,

-- 
Mylène Josserand, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com