Hello,
I'm trying to use rtl8723be wifi on Fedora27 but I still get continuosly
disconnection. The error in the dmesg is "Init MAC failed"
I tried with the following module options too : "fwlps=0 swlps=0" and
the variant of "ant_sel=1 or 2 or 0"
I downloaded the git files from your repo, and do the usual make,make
install, and modprobe stuffs, and then restart the notebook, but I get
the same result.
Thanks your help,
Regards,
Gergely
On 11/17/2017 02:16 AM, R?kosi Gergely wrote:
> Hello,
>
> I'm trying to use rtl8723be wifi on Fedora27 but I still get continuosly
> disconnection. The error in the dmesg is "Init MAC failed"
> I tried with the following module options too : "fwlps=0 swlps=0" and
> the variant of "ant_sel=1 or 2 or 0"
> I downloaded the git files from your repo, and do the usual make,make
> install, and modprobe stuffs, and then restart the notebook, but I get
> the same result.
I know from the E-mail you sent to me privately that you are new to this
process, thus I am going to give you some pointers. It is important for you to
give your kernel version. Yes, for devoted Fedora users, saying that you are
using F27 might be sufficient; however, I am not one of them. You should always
supply the output of the command 'uname -r'.
On the RTL8723BE, "Init MAC failed" is not the dmesg that is expected from
either the HP ant_sel problem, or a power-save problem. Incidentally, although
there are many "fixes" that require modifying the XXps options, the underlying
cause of that issue was fixed almost one year ago.
The main software component that might be wrong is the firmware. Please find the
name of the firmware file that is being loaded from the dmesg output. It will be
rtlwifi/... Once you locate that name, run the command
md5sum /lib/firmware/rtlwifi/xxx
Substitute the actual name for the xxx. Post the output of the md5sum.
Larry
On 11/18/2017 01:50 AM, Rákosi Gergely wrote:
> Hello,
>
> I put in to blacklist the module rtlwifi and rtl8723be, and now I get:
> - kde's networkmanager did not recognize wireless devices
> - in the messages log there are the following :
> "registered new interface driver rtl8xxxu
> Bluetooth: hci0: rtl : Direct firmware load for
> rtl_bt/rtl8723b_config.bin failed with error -2
> - ifconfig give no wireless devices (wlp2s0 or wlan0)
>
> If I blacklist only rtlwifi then load the rtl8723be module like normal.
That is exactly what is expected. You can ignore that missing
rtl_bt/rtl8723b_config.bin. The BT part of the RTL8723BE does not need a
"config.bin". A patch was sent to the BT group to get rid of that message, but
it seems to be lost somewhere.
Larry
2017-11-23 19:24 keltez?ssel, Larry Finger ?rta:
> On 11/23/2017 08:36 AM, R?kosi Gergely wrote:
>> 2017-11-21 22:30 keltez?ssel, James Cameron ?rta:
>>> On Tue, Nov 21, 2017 at 09:52:12PM +0100, R?kosi Gergely wrote:
>>>> 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
>>> Thanks.
>>>
>>>>>> 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...
>>> Thanks.? I had similar problem with different wireless device.
>>>
>>>>> 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.
>>> You might try running "Live CD" of Fedora 26 or Fedora 25, without
>>> installing, to test if unexpected disconnection happens in two older
>>> kernels.? Not for permanent solution, just for easy testing.
>>>
>>> I don't have specific advice for Fedora 27, you might ask Fedora
>>> community about that, or use RHBZ.? A quick search finds this old 2013
>>> page;
>>>
>>> https://fedoraproject.org/wiki/User:Ignatenkobrain/Kernel/Bisection
>>>
>> And now the wireless is working almost 20 hours long, from yesterday
>> afternoon. I dont know why. Lets check some happening:
>> - Yesterday I disconnect the charger from laptop, and lay down at the
>> other room
>> - I left the laptop more than a hour without interaction, so the system
>> is going to sleep
>> - When I push the keyboard the system load up, and everything is working
>> fine
>> - The battery almost depleted when I going back to the original room,
>> and connect the charger
>>
>> Then nothing changed, and I have a working rtl8723be wifi module. Why ?
>
> Who knows? I do not understand why it did not work before the way mine
> does with openSUSE!
>
> Larry
>
>
I found a workaround! If I power up the laptop, and check the wifi, and
if it is OK, then I close down the screen (thats mean laptop going to
sleep). After I open it, and just using like normal, then the connection
working well for a day, or more.
If I dont do that, then comes up the usual problem.
What ? Anybody have an idea what is it mean, and how ?
Thanks
Gergely
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?
> And the dmesg output:
>
> https://pastebin.com/iqQSu2hD
Is now v4.13.13.
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.
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?
--
James Cameron
http://quozl.netrek.org/
2017-11-21 22:30 keltez?ssel, James Cameron ?rta:
> On Tue, Nov 21, 2017 at 09:52:12PM +0100, R?kosi Gergely wrote:
>> 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
> Thanks.
>
>>>> 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...
> Thanks. I had similar problem with different wireless device.
>
>>> 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.
> You might try running "Live CD" of Fedora 26 or Fedora 25, without
> installing, to test if unexpected disconnection happens in two older
> kernels. Not for permanent solution, just for easy testing.
>
> I don't have specific advice for Fedora 27, you might ask Fedora
> community about that, or use RHBZ. A quick search finds this old 2013
> page;
>
> https://fedoraproject.org/wiki/User:Ignatenkobrain/Kernel/Bisection
>
And now the wireless is working almost 20 hours long, from yesterday
afternoon. I dont know why. Lets check some happening:
- Yesterday I disconnect the charger from laptop, and lay down at the
other room
- I left the laptop more than a hour without interaction, so the system
is going to sleep
- When I push the keyboard the system load up, and everything is working
fine
- The battery almost depleted when I going back to the original room,
and connect the charger
Then nothing changed, and I have a working rtl8723be wifi module. Why ?
Thanks,
Gergely
Hello,
I put in to blacklist the module rtlwifi and rtl8723be, and now I get:
- kde's networkmanager did not recognize wireless devices
- in the messages log there are the following :
"registered new interface driver rtl8xxxu
Bluetooth: hci0: rtl : Direct firmware load for
rtl_bt/rtl8723b_config.bin failed with error -2
- ifconfig give no wireless devices (wlp2s0 or wlan0)
If I blacklist only rtlwifi then load the rtl8723be module like normal.
Thanks,
Geri
2017-11-18 06:06 keltezéssel, [email protected] írta:
> On Fri, 2017-11-17 at 09:16 +0100, Rákosi Gergely wrote:
>> Hello,
>>
>> I'm trying to use rtl8723be wifi on Fedora27 but I still get
>> continuosly
>> disconnection. The error in the dmesg is "Init MAC failed"
>> I tried with the following module options too : "fwlps=0 swlps=0" and
>> the variant of "ant_sel=1 or 2 or 0"
>> I downloaded the git files from your repo, and do the usual make,make
>> install, and modprobe stuffs, and then restart the notebook, but I
>> get
>> the same result.
>>
> Could try blacklisting rtlwifi. That way it uses rtl8xxxu.
>> Thanks your help,
>> Regards,
>> Gergely
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
In mailing lists like this, top posting is not recommended. Please read
http://www.idallen.com/topposting.html for a good explanation why top posting is
not good, particularly for complicated threads.
You have the correct firmware. By the way, the code in 4.13.12 should be better
that rtlwifi_new. That latter repo is deliberately kept a little bit behind just
in case there is a regression.
With NO options in the loading, please run the following:
iw dev
You should only see one device. On the "Interface" line, note what your system
calls the wifi device. Substitute that for the "wlan0" in the next command:
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
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
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
Thanks again,
Best Regards,
Gergely
2017-11-17 16:51 keltez?ssel, Larry Finger ?rta:
> On 11/17/2017 02:16 AM, R?kosi Gergely wrote:
>> Hello,
>>
>> I'm trying to use rtl8723be wifi on Fedora27 but I still get continuosly
>> disconnection. The error in the dmesg is "Init MAC failed"
>> I tried with the following module options too : "fwlps=0 swlps=0" and
>> the variant of "ant_sel=1 or 2 or 0"
>> I downloaded the git files from your repo, and do the usual make,make
>> install, and modprobe stuffs, and then restart the notebook, but I get
>> the same result.
>
> I know from the E-mail you sent to me privately that you are new to
> this process, thus I am going to give you some pointers. It is
> important for you to give your kernel version. Yes, for devoted Fedora
> users, saying that you are using F27 might be sufficient; however, I
> am not one of them. You should always supply the output of the command
> 'uname -r'.
>
> On the RTL8723BE, "Init MAC failed" is not the dmesg that is expected
> from either the HP ant_sel problem, or a power-save problem.
> Incidentally, although there are many "fixes" that require modifying
> the XXps options, the underlying cause of that issue was fixed almost
> one year ago.
>
> The main software component that might be wrong is the firmware.
> Please find the name of the firmware file that is being loaded from
> the dmesg output. It will be rtlwifi/... Once you locate that name,
> run the command
>
> md5sum /lib/firmware/rtlwifi/xxx
>
> Substitute the actual name for the xxx. Post the output of the md5sum.
>
> Larry
On Fri, 2017-11-17 at 09:16 +0100, Rákosi Gergely wrote:
> Hello,
>
> I'm trying to use rtl8723be wifi on Fedora27 but I still get
> continuosly
> disconnection. The error in the dmesg is "Init MAC failed"
> I tried with the following module options too : "fwlps=0 swlps=0" and
> the variant of "ant_sel=1 or 2 or 0"
> I downloaded the git files from your repo, and do the usual make,make
> install, and modprobe stuffs, and then restart the notebook, but I
> get
> the same result.
>
Could try blacklisting rtlwifi. That way it uses rtl8xxxu.
> Thanks your help,
> Regards,
> Gergely
On 11/17/2017 11:06 PM, [email protected] wrote:
> On Fri, 2017-11-17 at 09:16 +0100, Rákosi Gergely wrote:
>> Hello,
>>
>> I'm trying to use rtl8723be wifi on Fedora27 but I still get
>> continuosly
>> disconnection. The error in the dmesg is "Init MAC failed"
>> I tried with the following module options too : "fwlps=0 swlps=0" and
>> the variant of "ant_sel=1 or 2 or 0"
>> I downloaded the git files from your repo, and do the usual make,make
>> install, and modprobe stuffs, and then restart the notebook, but I
>> get
>> the same result.
>>
>
> Could try blacklisting rtlwifi. That way it uses rtl8xxxu.
Ignore this suggestion. The RTL8723BE is NOT supported by rtl8xxxu. By the way,
that "u" means that the driver is for USB devices. The "E" at the end of yours
means PCIe!
Larry
On 11/23/2017 08:36 AM, R?kosi Gergely wrote:
> 2017-11-21 22:30 keltez?ssel, James Cameron ?rta:
>> On Tue, Nov 21, 2017 at 09:52:12PM +0100, R?kosi Gergely wrote:
>>> 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
>> Thanks.
>>
>>>>> 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...
>> Thanks. I had similar problem with different wireless device.
>>
>>>> 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.
>> You might try running "Live CD" of Fedora 26 or Fedora 25, without
>> installing, to test if unexpected disconnection happens in two older
>> kernels. Not for permanent solution, just for easy testing.
>>
>> I don't have specific advice for Fedora 27, you might ask Fedora
>> community about that, or use RHBZ. A quick search finds this old 2013
>> page;
>>
>> https://fedoraproject.org/wiki/User:Ignatenkobrain/Kernel/Bisection
>>
> And now the wireless is working almost 20 hours long, from yesterday
> afternoon. I dont know why. Lets check some happening:
> - Yesterday I disconnect the charger from laptop, and lay down at the
> other room
> - I left the laptop more than a hour without interaction, so the system
> is going to sleep
> - When I push the keyboard the system load up, and everything is working
> fine
> - The battery almost depleted when I going back to the original room,
> and connect the charger
>
> Then nothing changed, and I have a working rtl8723be wifi module. Why ?
Who knows? I do not understand why it did not work before the way mine does with
openSUSE!
Larry
On Tue, Nov 21, 2017 at 09:52:12PM +0100, R?kosi Gergely wrote:
> 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
Thanks.
> >> 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...
Thanks. I had similar problem with different wireless device.
> > 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.
You might try running "Live CD" of Fedora 26 or Fedora 25, without
installing, to test if unexpected disconnection happens in two older
kernels. Not for permanent solution, just for easy testing.
I don't have specific advice for Fedora 27, you might ask Fedora
community about that, or use RHBZ. A quick search finds this old 2013
page;
https://fedoraproject.org/wiki/User:Ignatenkobrain/Kernel/Bisection
--
James Cameron
http://quozl.netrek.org/
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
>
> In mailing lists like this, top posting is not recommended. Please
> read http://www.idallen.com/topposting.html for a good explanation why
> top posting is not good, particularly for complicated threads.
>
> You have the correct firmware. By the way, the code in 4.13.12 should
> be better that rtlwifi_new. That latter repo is deliberately kept a
> little bit behind just in case there is a regression.
>
> With NO options in the loading, please run the following:
>
> iw dev
>
> You should only see one device. On the "Interface" line, note what
> your system calls the wifi device. Substitute that for the "wlan0" in
> the next command:
>
> 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
??????? signal: -46.00 dBm
??????? SSID: SKYNET-GYEREK
??????? signal: -56.00 dBm
??????? SSID: BALUHALO
??????? signal: -52.00 dBm
??????? SSID: Apavik
??????? signal: -54.00 dBm
??????? SSID: UPC Wi-Free
??????? signal: -56.00 dBm
??????? SSID: CsomadAirport
??????? signal: -54.00 dBm
??????? SSID: Apavik2
[root@skynet-x2 ~]#
And the dmesg output:
https://pastebin.com/iqQSu2hD
Thanks,
Gergely