networkmanager restart = no more wireless IN CURRENT 19/12/2015
 

Hi , if

wireless no working more , need to reboot to recover

stop / start do the same.


Tested in a full fresh current install (19/12/2015) , and in 3 different machines.

fresh install , i install recordmydesktop to make video.

youtube video
https://www.youtube.com/watch?v=eJI7...ature=youtu.be

as see in the video , wireless no return more afetr restart service ... the ethernet working , nm running but no wireless.

test in 3 machines

1 - tower pc + ralink usb 3070 chip
2 - netbook asus pci atheros 9000 pci ath9k driver
3 - usb card with ath9k_htc driver for ar9271

wireless lost ever and need reboot.

i not touch nothing , install and test.

in dmesg only relevant is the line

[ 189.218550] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

networkmanager restart = no more wireless IN CURRENT 19/12/2015
 

Just wondering, what is the result of :
rfkill list

Btw, did you tried to use iwconfig / ifconfig / iwlist and so on ?

rfkill list all


all are NO BLOCKED

NO SOFT BLOCKED
NO HARDWARE BLOCKED


working.

Its a NetworkManager problem...i think.

Some extra info , installation choose the hugesmp kernel.
In the network config dialog i choose the last option in the dialog menu

networkmanager autoconfiguration.


I dont know if networkmanager need a udev rule to manage wireless devices.
Ethernet are ever working as espected , well...restart service no broke ethernet , only wireless.

no one can test restart networkmanager to see ?

only me bug ?

i think ,no ..because 3 diferente machines with different adapters.

Hello USUARIONUEVO,

I did restart with network networkmanager and i did not have the problem on icewm.

I had an issue with network manager and my wifi card after the last update. To solve the issue I had to unplug my system (powering it down didn't work) wait a few minutes, plug it back in and boot my system up. (I had to starve the "gremlins" of electricity before they left. :p). Since I run "current" also some old firmware could have been "stuck" from all the updates.


Just an idea & Good Luck

Could you make sure your /etc/rc.d/rc.inet1 is no executable. if it is you will have this issue. pick one or the other not both. make sure rc.networkmanager is executable
as for your chip if it was working before it will work again. I hope this helps.

No lucky.

inite1 ,inet2 and rc.networkmanager are executables by defaukt.

i try uncheck executable in init1 , no working if service restart , same is uncheck inet2.


That is only in slackware-current , and only lost the wireless cards , in dmesg see somethin to LINK NOT READY FOR wlan0

I blacklisted ipv6 , nothing works.

If service restart , losT wireless.

Fresh , default slackware-current 3 machines 3 chipsets.

If install wicd and restart wicd , all go O.K , but networkmanager NO.


----------------------------------------------------------------------------

/etc/rc.d/rc.networkmanager restart

the first time executing de restart service aparently work (except wirelees no return)

after one service restart , then try again .. or try to stop.


NO STOPPP , if see in system process NetworkManager IS RUNNING , but

/etc/rc.d/rc.networkmanager status

say is not


some times see a D-BUS errors messages ..


1 - restart service
2 - stop service
3 - see how is in system process running..you have net

Ok , ... im not replay in this time, because PROBLEM PERSIST , current 04 march 2016 on current


But , trying to find something ,i encounter this


if plays with "sudo" ... script service works perfectly ...why?


sudo /etc/rc.d/rc.networkmanager restart

do it perfectly , but if not use sudo , dont work well... then i think is some problem permission on some part.


but , where?

Im running in runlevel 4 with root , no understand why need sudo to work correctly.

If some one test , and use kde, please ..open the task manager to control how if use restart 2 times , service non stop.

But using sudo ,,, ever works well.

Do you not try to run the script as root? All the scripts in /etc/rc.d/ are designed to be ran as root, and running them as a normal user won't usually work.

What is the output of your commands when you try to run them regularly and with sudo?

no , you no understand.

Im as a root user , then by need sudo to work properly?

If some one go to test , please, for best connect with wireless ..in the first restart lost conection...but process networkmanager remain ,and cant kill with


killall NetworkManager or another one, i can kill only using the task manager , rigth click ...send kill.


_____________________________________

/etc/rc.d/rc.networkmanager

line 36
$NETWORKMANAGER_BIN --> sudo $NETWORKMANAGER_BIN

lines 58 & 63 same order
kill -HUP $(echo $line | cut -b 1-5) --> sudo kill -HUP $(echo $line | cut -b 1-5)

line 68
kill $pidlist &>/dev/null --> sudo kill $pidlist &>/dev/null


now the rc.networkmanager WORKS

You keep making noise in this thread about a problem that only you appear to see.
Do you use DHCP with your wireless connections?
If so, I suspect that when you kill NetworkManager you are not also killing the DHCP process. In Slackware, this is dhcpcd by default, but dhclient can also be used.
When NetworkManager starts, it expects to also initiate DHCP, if DHCP has been requested. I am wondering whether you have a stale DHCP process running when you restart NetworkManager, leading to the problem that you see.

rc.networkmanager kills dhcp and dhcpcd ...


pff ,thats incredible...come on.

connect via wireless , and restart networkmanager ... its easy


if use the rc.networkmanager script with sudo , all works well, but not working if not sudo.

I had to switch networkmanager from dhcpcd to dhclient (in networkmanager.conf) to get it to connect to my friend's router.

pidof NetworkManager
9999



ps aux | grep NetworkManager
root 9999 0.2 0.2 103572 14336 ? Ssl 20:39 0:01 /usr/sbin/NetworkManager
root 10010 0.0 0.1 8744 7464 ? S 20:39 0:00 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-102fc991-43e4-447e-a4c3-d87a2b29e9cd-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0
root 10468 0.0 0.0 3336 1996 pts/1 S+ 20:47 0:00 grep NetworkManager