[SOLVED] Clevo W650sj Wifi not working with latest current iso

edney · 12-10-2017, 07:22 AM

Slackware latest current and all its based distros same problem!

Clevo Laptop W650sj cant make wifi work, it connects but after 3 seconds it disconnects....on windows works fine so i know that the card is not a problem..

Any help or fix soon?

brobr · 12-10-2017, 07:54 AM

Hi, could you provide some more info that could be relevant:
1) what is the network controller (via lscpi);
2) what kernel are you running?
3) how do you connect your wifi (via networkmanager/wicd/ ...)

And did you look around for poss. answers? eg maybe, assuming you have a N135, some clues in these threads: here: or here

hth

allend · 12-10-2017, 07:57 AM

Too slooow.

edney · 12-10-2017, 08:19 AM

Quote:

Originally Posted by brobr

Hi, could you provide some more info that could be relevant:
1) what is the network controller (via lscpi);
2) what kernel are you running?
3) how do you connect your wifi (via networkmanager/wicd/ ...)

And did you look around for poss. answers? eg maybe, assuming you have a N135, some clues in these threads: here: or here

hth

Thank you for your reply!

here`s my lspci file

https://pastebin.com/bnFakXqW

the kernel is root:# uname -r
4.4.76

edney · 12-10-2017, 08:27 AM

The two links you sent me are saying to disable power management over wifi device but none of these files exists here...
On ubuntu and fedora i had similar issues but with bluetooth, i had to disable tlp, but here i dont know what manages the power or where and when...

Any help would be much appreciated!

heyjann · 12-10-2017, 08:57 AM

Seems to be a RTL8723BE chip, then.

Quote:

Originally Posted by edney

The two links you sent me are saying to disable power management over wifi device but none of these files exists here...

"none of these files" meaning files in /etc/modprobe.d? you would need to create those files and edit them to set custom options.

4.4.76 is not the kernel in current, in fact I can't quickly find any moment when it was the default kernel in Slackware, is it custom? Not that that is necessarily a bad thing, but this might be a problem already addressed in later kernel versions.

edney · 12-10-2017, 09:25 AM

Quote:

Originally Posted by heyjann

Seems to be a RTL8723BE chip, then.

"none of these files" meaning files in /etc/modprobe.d? you would need to create those files and edit them to set custom options.

4.4.76 is not the kernel in current, in fact I can't quickly find any moment when it was the default kernel in Slackware, is it custom? Not that that is necessarily a bad thing, but this might be a problem already addressed in later kernel versions.

Yes, so no problem i will create them hehe!

Its the kernel that is on vector and on zenwalk current, that are based on slackware current too!

Also i have the same problem using slackware current iso, tried before posting, so i dont think its kernel related.

edney · 12-10-2017, 09:28 AM

I will try to reinstall slackware current again and see if it fixes the problem will post results here in 20 minutes!

heyjann · 12-10-2017, 10:15 AM

To test different module options I believe you can use

Code:

rmmod rtl8723be

which unloads the module, and then experiment with for example

Code:

modprobe rtl8723be fwlps=0 swlps=0 ips=0

and repeat until you find settings that work well. You can find all the available options with

Code:

modinfo rtl8723be

Once you find a combination that works, you can make it permanent (well, automatically apply, anyway) by creating an /etc/modprobe.d/rtl8723be.conf containing for example

Code:

options rtl8723be fwlps=0 swlps=0 ips=0

For reference
https://wiki.archlinux.org/index.php...using_modprobe

Gordie · 12-10-2017, 10:40 AM

The OP has a similar thread in the Zenwalk forum. It is better addressed there

edney · 12-10-2017, 04:27 PM

Quote:

Originally Posted by Gordie

The OP has a similar thread in the Zenwalk forum. It is better addressed there

Nope because i do also have slackware current installed and the problem is the same! i hope they fix it on slack! hehe is there anyplace in wich i am able to submit the error?

edney · 12-10-2017, 04:28 PM

Well tested all day....slackware current, slackel, zenwalk, vector linux....all the slackware based systems and slackware itself have the same problem!

Hope slack devs fix it?

edney · 12-10-2017, 04:32 PM

i will submit an bug report to slackware devs.

edney · 12-10-2017, 04:40 PM

end of the topic for me, already gave up and reported...

heyjann · 12-10-2017, 04:46 PM

The issue seems related to the functioning of the kernel module, and Slackware uses the kernels that Linus and contributors give us via kernel.org without much or any modification at all.
In other words I doubt this issue is Slackware-specific, or that it could have a Slackware-specific fix.

For example Archlinux also has some recommended options for this module:
https://wiki.archlinux.org/index.php...ae.2Frtl8723be

Ubuntu is also not immune
https://ubuntuforums.org/showthread.php?t=2243978