From: "Rákosi Gergely" <rakosi.gergely@gmail.com>
To: James Cameron <quozl@laptop.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: rtl8723be on Fedora27
Date: Tue, 21 Nov 2017 21:52:12 +0100 [thread overview]
Message-ID: <e639e8df-7cea-87c5-add9-cea1c5e57a8a@gmail.com> (raw)
In-Reply-To: <20171121203746.GC5400@us.netrek.org>
2017-11-21 21:37 keltezéssel, James Cameron írta:
> On Tue, Nov 21, 2017 at 03:08:16PM +0100, Rákosi Gergely wrote:
>> 2017-11-18 16:52 keltezéssel, Larry Finger írta:
>>> On 11/17/2017 06:22 PM, Rákosi Gergely wrote:
>>>> Hello Larry,
>>>>
>>>> First of all, thanks your help.
>>>> Lets see...here is the kernel version: 4.13.12-300
>>>> The machine is an Asus ROG 553VE
>>>>
>>>> The firmware which loading in the dmesg is : rtlwifi/rtl8723befw_36.bin
>>>> The output of md5sum is : 1850c1308fbcd95e9f6a7f58ede1e35f
>>> [...]
>>> sudo iw dev wlan0 scan | egrep "SSID|signal"
>>>
>>> Post that output. In addition, copy the dmesg output to some pastebin
>>> and post the link as well.
>>>
>>> Larry
>>>
>> Hello Larry,
>>
>> I hope this email post format is good, and fit to the rules.
>> Here is the output:
>>
>> root@skynet-x2 ~]# iw dev wlp2s0 scan | egrep "SSID|signal"
>> signal: -46.00 dBm
>> SSID: SKYNET-X2
>> [...]
>> [root@skynet-x2 ~]#
> Scan results seem normal. Was this scan before disconnect?
> - Yes, this command output taken while the connection was OK
>> And the dmesg output:
>>
>> https://pastebin.com/iqQSu2hD
> Is now v4.13.13.
> - Yes, thats the upgraded kernel
> This is interesting, an H2C command was dropped, but no idea which.
>
> [ 9.848052] rtl8723be: error H2C cmd because of Fw download fail!!!
>
> Disconnection happened at boot+440 seconds, associate+429 seconds;
>
> [ 439.871033] rtlwifi: AP off, try to reconnect now
> [ 439.871093] wlp2s0: Connection to AP 4c:5e:0c:c7:fa:e3 lost
>
> I cannot tell what causes disconnect. I wonder if the same
> timing of the problem happens always, or if the timing varies.
>
> - The timing always changing, never is the same. And I dont realize the cause at now...
> Init MAC failed was another 30 seconds later;
>
> [ 468.600670] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
> [ 469.618926] rtl8723be: Init MAC failed
>
> Looking at _rtl8723be_init_mac, there are two false returns; hardware
> power on fail, and llt write fail.
>
> Sorry, I don't have rtl8723be hardware.
>
> Rákosi, did any older kernel keep connection?
>
> - The oldest kernel is 4.13.9-300.fc27.x86_64 in Fedora 27 installation, but did the same.
If you can give advise how, and what I do, then I'll try it.
Thanks,
Gergely
next prev parent reply other threads:[~2017-11-21 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 8:16 rtl8723be on Fedora27 Rákosi Gergely
2017-11-17 15:51 ` Larry Finger
2017-11-18 0:22 ` Rákosi Gergely
2017-11-18 15:52 ` Larry Finger
2017-11-21 14:08 ` Rákosi Gergely
2017-11-21 20:37 ` James Cameron
2017-11-21 20:52 ` Rákosi Gergely [this message]
2017-11-21 21:30 ` James Cameron
2017-11-23 14:36 ` Rákosi Gergely
2017-11-23 18:24 ` Larry Finger
2017-11-23 18:29 ` Rákosi Gergely
2017-11-18 5:06 ` rosenp
2017-11-18 7:50 ` Rákosi Gergely
2017-11-18 15:40 ` Larry Finger
2017-11-18 15:19 ` Larry Finger
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=e639e8df-7cea-87c5-add9-cea1c5e57a8a@gmail.com \
--to=rakosi.gergely@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quozl@laptop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox