All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlo Caione <carlo@endlessm.com>
To: Jes Sorensen <Jes.Sorensen@gmail.com>
Cc: kvalo@codeaurora.org, linux-wireless@vger.kernel.org,
	mylene.josserand@free-electrons.com,
	Linux Upstreaming Team <linux@endlessm.com>
Subject: RTL8723bu: poor signal and connection troubles
Date: Wed, 10 Jan 2018 12:15:51 +0000	[thread overview]
Message-ID: <CAL9uMOFT3VwqHs5+wvot+dxArvhd7Bi-U5+CKhYUXjYwHcU=jg@mail.gmail.com> (raw)

Hi,
this is a follow up email to [0] since the problem was never fully
investigated / solved and I keep seeing the same problem also on my
hardware.

Also in my case the hardware is a rtl8723bt transceiver
(0x0bda:0xb720), this time shipped on the internal USB bus in a cheap
laptop branded Zyrex Sky 232.

As already reported by Mylene the problem is that using this
transceiver and the latest Linus master you can barely see any WiFi
network around and also when a WiFi network is actually seen, the
connection is impossible since the signal strength is too low to have
a reliable connection. Of course during my tests BT is off and no BT
driver is probed at all.

Using the downstream driver at [1] everything works correctly.

I tried to debug a bit the issue, in particular comparing functions
and registers related to the antenna setup (.power_on, .enable_rf,
.phy_init_antenna_selection, .phy_iq_calibrate hooks) but everything
seems pretty much the same on the two drivers (even though slightly
differences do exist).

Any idea / suggestion on how to debug this problem? I guess it's worth
to start looking at this since several platforms are being affected
now.

Cheers,

[0] https://www.spinics.net/lists/netdev/msg468028.html
[1] https://github.com/lwfinger/rtl8723bu

-- 
Carlo Caione  |  +44.7384.69.16.04  |  Endless

             reply	other threads:[~2018-01-10 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 12:15 Carlo Caione [this message]
2018-01-11 10:30 ` RTL8723bu: poor signal and connection troubles Barry Day
2018-01-21 21:46   ` Jes Sorensen
2018-01-21 22:56     ` Carlo Caione
2019-01-29  9:56       ` Chris Chiu
2019-02-12 15:38         ` Chris Chiu
2018-01-18 10:43 ` Carlo Caione

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAL9uMOFT3VwqHs5+wvot+dxArvhd7Bi-U5+CKhYUXjYwHcU=jg@mail.gmail.com' \
    --to=carlo@endlessm.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=mylene.josserand@free-electrons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.