Long time lurker here but just made the account. I've been having problems lately when trying to shutdown the system freezes/hangs/crashes or whichever one of those. It seems that this happens as soon as network manager is put down. That being said, problems with the ath9k drivers are not new to me, but now that the driver IS working it seems to cause a crash as soon as it is terminated. This also happens if I manually shutdown the networkmanager daemon with "rc.d stop networkmanager".
These are the last lines from the log after a reboot:
Oct 12 13:38:20 willy-arch shutdown: shutting down for system reboot
Oct 12 13:38:20 willy-arch init: Switching to runlevel: 6
Oct 12 13:38:23 willy-arch NetworkManager: <info> caught signal 15, shutting down normally.
Oct 12 13:38:23 willy-arch NetworkManager: <info> (wlan0): now unmanaged
Oct 12 13:38:23 willy-arch NetworkManager: <info> (wlan0): device state change: activated -> unmanaged (reason 'removed') [100 10 36]
I would like to know if this is just happening to me or if it a known problem and if there is any solution. Having to hard reset your computer every time you try to shutdown can't possibly do any good to the hardware.
zackyramone, welcome to the forums, or at least welcome as a contributing member of the forums. I no longer use SysV or initscripts, but I am curious if you ahve ever tried to wait it out? Does it eventually shut down, or is is actually frozen?
I have waited a couple of minutes, at best 10 minutes, but to no avail. Might, I add, I hadd this problem with Fedora too, but I thought that it was a problem which was pertaining to that distro itself, however, I seem to be mistaken. I have tried changing terminals and even Ctrl+Prt Scr, but nothing happens so I'm figuring the system is crashing as that would usually work although I have never tried it as Linux has never rashed on me except or when wireless is involded.
Have you tried systemd? Since dbus is packaged with systemd these days, it is simply a matter of putting init=/lib/systemd/systemd on the bootloader command line. Might I suggest also seeing if using a different network management system might yeild different results. I am a former wicd user, and it was great while I used it. But I have moved on to netcfg. Who knows, maybe I will continue to progress to simpler things and evertually be doing it manually. BTW, what happens if you diable the network-manager daemon, and then connect manually, then shut down?
Hmm I will have to read up on systemd as I don't really know what it's about. As for other network managers, both wicd and netcfg crash as soon as they start scanning or try to connect to to a wireless network. And by "crash" I mean that my system is no longer usable and I have to hard reset. Shutting down the daemon also crashes the system
Since there is no reply, I might want to update that even after changing to a fully native systemd setup the system still freezes whenever I try to shutdown, reboot or even turn off NetworkManager.service.
As far as I know, dowgrading to that version does not solve my problem, rather, it seems to have caused a multitude of problems regarding X and keyboard settings and the lack of customisability of xfce4.