Yeah that makes sense, but hum...on Fedora, ubuntu, mint, Opensuse, sabayon and derivates it works...so may them have patched their kernels to avoid the problem? hehehe well in this case i will also report a bug on kernel.org to see if someone can fix it hehehe.;.. actually i wasnt able to fix it on slackware...


Tried Redcore linux and the same problem happens there.

In my case Rfkill is not the problem...i already tried that trick too before start the post.

@edney: Your opening post symptoms and wifi hardware are significant here. There is a known issue with some Realtek (rtl8732be) hardware...

It may well be due to low received signal level (easy to check) caused by the wrong antenna port being in use. It can be fixed by explicitly setting the correct antenna port when loading the driver. See my post here and an outline of what is required to work around the issue here.

1 members found this post helpful.

Good one, but this laptop does have two antennas....tried these also still connects then 3 seconds disconnects...also the signal bar looks full.

Thanks for the tip anyways...i will install other distros and wait for the fix from the devs.

seems a bit of an hit and miss:
1) downgrading the kernel from 4.14 could help:
wifi-rtl8723be-not-working-with-kernels-later-than-4-9-release

but also later than 4.4 could be needed according to this blog with some background to heyjann's advice:
2) realtek-RTL8723BE-wifi-fix-hanging

which shows that it seems to boil down to problematic power management for that chip (2) and or working alongside bluetooth (1).

Slackware devs will not bother with that as long as it looks like a driver/kernel issue; nothing related to the distribution itself.

EDIT: a bit late I see; should have refreshed page before posting this;

1 members found this post helpful.

Dont worry, any tips are welcome because more users may have the same problem and it may help them!

I tried 4.4 and also 4.9 kernels...the problem is still here!

The devs should care if they want the distro to be usable for everybody, since the problem doesnt happens on other distros as i said and as it is driving me away from using it......

If it is working on some distros and not on others, you might want to compare whether the options discussed here are different between these: kernels they use; how wifi is set up with respect to this chip, whether they have particular conf-settings in /etc/modprobe.d/ provided, etc, etc... if in that way you find a solution it might be something that could at least be shared here or put in a slack-howto or something. The variables at the moment seem too many to sort out without being able to test it and for that you need the hardware, something I think you cannot assume the 'slack-devs' have. That's one of the roles of this forum... users with different hardware testing the development in -current and help to find ways around problems (if possible).

1 members found this post helpful.

actually i guess something related to acpi or power management, or bad driver, i dont know i gave up...will follow up to manjaro....hoping devs fix it heheh see ya.

In the past, disconnecting after a few seconds has linked to using dhcpcd as the dhcp client in Network Manager. You can try and switch it to dhclient, which has fixed similar issues others have faced.

You can do this in /etc/NetworkManager/conf.d/00-dhcp-client.conf by commenting out the dhcp=dhcpcd line and uncommenting dhcp=dhclient line. Apparently both clients are problematic in Network Manager, but Pat had better success with dhcpcd.

1 members found this post helpful.

Along the lines of bassmadrigal's suggestion, another thing to try would be to comment out

"duid" in /etc/dhcpcd.conf and uncomment "#clientid"

I have to do this to get connected at work (via eth0)

1 members found this post helpful.

On antergos i got the same problem, how i made it work?

pacman -S base-devel git linux-headers iw rfkill wireless_tools

reboot and its working again...lol

Maybe slackware devs should look into it, seems related to power management because when i re enable wireless_tools it works without any problem...

Sorry to repeat myself but I wonder whether your problem is/was related to how you chose to connect your wifi; so again:
if you use network-manager or wicd most settings that are needed can be set using those apps. Then you won't (need to) use /etc/rc.inet1.conf.

But not using those apps and taking the inet1 route or cl, you might need wireless-tools for which there is a conf file to set up in /etc/rc.d/rc.wireless.conf.

These things rely on your decisions how to set up networking...

I do use network manager, but it gets blank, cant enter any options on it, after this it works...it happens on almost all distros...and is related to power management of this laptop and kernel problems that are not solved yet.

I think my best bet would be replace the wireless card for some that works out of the box.... is there anyplace wich shows a list of the best supported hardware on debian arch or slackware?