View previous topic :: View next topic |
Author |
Message |
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Wed Jan 04, 2012 11:18 am Post subject: After replaying backup - wireless messed up :( |
|
|
Hi!
I had to replay my backup and now my wireless setup is severely broke.
I use Networkmanager, wpa_supplicant and the KDE network applet, all in the latest available ~amd64 versions.
The network applet or wpa_gui are not showing any base stations around, even if there are several there. The scan just shows nothing. Strange thing is: If I put my mobile in USB tethering mode, it just works as a cable network. Too strange.
What I tried so far: reconfiguring, also as root, I get only message "insufficient privileges", remerging solid, networkmanager, wpa_supplicant > doesn't work. Remerging and deleting /etc/NetworkManager/ & /etc/wpa_supplicant before.
This is my backup script, I used it often before and never, ever had such errors:
Code: |
rdiff-backup --print-statistics --exclude-sockets -v 3 --include=/dev/console --exclude=/dev/ --exclude=/tmp/* --exclude=/sys/* --include=/var/tmp/portage --exclude=/var/tmp/* --include=/var/log/emerge.log --exclude=/var/log/* --exclude=/proc/* --include=/usr/portage/distfiles --include=/usr/portage/profiles --exclude=/usr/portage/ --exclude=/home/* --exclude=/media/* --exclude=/mnt/* --exclude=/ccache/* --exclude=/root/.thumbnails --exclude=/reiserfs_priv --exclude-sockets --include=/usr/src/linux-*/.config --exclude=/usr/src/linux-* --exclude=/var/run/* --exclude=/var/lock/* / /media/backup_linux/root-backup/
|
Maybe I forgot an important directory or what? Your thoughts are highly apprdeciated right now! _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Wed Jan 04, 2012 5:00 pm Post subject: |
|
|
Well, still no succes.
My system log is filled rapidly with messages like these:
Code: |
Jan 4 17:56:55 aumakua NetworkManager[3472]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jan 4 17:56:55 aumakua kernel: [ 453.996253] wlan0: authenticate with 02:1a:11:f6:fc:48 (try 1)
Jan 4 17:56:55 aumakua kernel: [ 453.998334] wlan0: authenticated
Jan 4 17:56:55 aumakua kernel: [ 453.998369] wlan0: associate with 02:1a:11:f6:fc:48 (try 1)
Jan 4 17:56:55 aumakua kernel: [ 454.001182] wlan0: RX AssocResp from 02:1a:11:f6:fc:48 (capab=0x411 status=0 aid=1)
Jan 4 17:56:55 aumakua kernel: [ 454.001188] wlan0: associated
Jan 4 17:56:55 aumakua kernel: [ 454.002330] wlan0: disassociating from 02:1a:11:f6:fc:48 by local choice (reason=3)
Jan 4 17:56:55 aumakua kernel: [ 454.002450] wlan0: deauthenticating from 02:1a:11:f6:fc:48 by local choice (reason=3)
Jan 4 17:56:55 aumakua kernel: [ 454.019987] cfg80211: Calling CRDA to update world regulatory domain
Jan 4 17:56:55 aumakua NetworkManager[3472]: <info> (wlan0): supplicant interface state: scanning -> disconnected
Jan 4 17:56:57 aumakua kernel: [ 455.102717] wlan0: authenticate with 02:1a:11:f6:fc:48 (try 1)
Jan 4 17:56:57 aumakua kernel: [ 455.104767] wlan0: authenticated
Jan 4 17:56:57 aumakua kernel: [ 455.104843] wlan0: associate with 02:1a:11:f6:fc:48 (try 1)
Jan 4 17:56:57 aumakua kernel: [ 455.107697] wlan0: RX AssocResp from 02:1a:11:f6:fc:48 (capab=0x411 status=0 aid=1)
Jan 4 17:56:57 aumakua kernel: [ 455.107704] wlan0: associated
Jan 4 17:56:57 aumakua kernel: [ 455.109617] wlan0: disassociating from 02:1a:11:f6:fc:48 by local choice (reason=3)
Jan 4 17:56:57 aumakua kernel: [ 455.109722] wlan0: deauthenticating from 02:1a:11:f6:fc:48 by local choice (reason=3)
Jan 4 17:56:57 aumakua kernel: [ 455.127262] cfg80211: Calling CRDA to update world regulatory domain
|
Still it cannot maintain a connection. At least my wireless interface and appropriate connection is showing up, but does not connect.
I really expect it to be a MAC address problem, dbus or consolekit... Any ideas? _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
CkoTuHa n00b
Joined: 27 Mar 2009 Posts: 74
|
Posted: Sat Jan 07, 2012 3:09 pm Post subject: |
|
|
Disassociating by local choice (reason=3) is classical, typical, very annoying fuck up of linux stack, in this case of 802.11 implementation.
I bet you have intel wifi card, the kernel ver > 3 and are trying to get some stable wifi out of your Wireless-N router.
Can congratulate you. The intel linux wireless guys are full of it. They are really unable to get grip on wifi problems of linux users out there. Wey-Yi Guy, I am looking at you. So, the big idea is - pathetic state of wireless stack of linux. Get used to it.
That said, you can help yourself by building a patched kernel.
What you can try to do to alleviate most of the issues is keep an eye on big boys, and use their patches!
With some redhat patches applied most of your network problems will be gone.
if you are using kernel version 3.1.X, get :
http://kojipkgs.fedoraproject.org/packages/kernel/3.1.7/1.fc16/src/kernel-3.1.7-1.fc16.src.rpm
rpmunpack it
there you will have source for the linux kernel linux-3.1.tar.bz2, tar xjvf it, then cd to linux-3.1, apply the patch : bzcat ../patch-3.1.7.bz2 | patch -p1 and then, apply the patches :
iwlwifi-allow-to-switch-to-HT40-if-not-associated.patch
iwlwifi-do-not-set-the-sequence-control-bit-is-not-n.patch
iwlwifi-tx_sync-only-on-PAN-context.patch
iwlwifi-update-SCD-BC-table-for-all-SCD-queues.patch
mac80211_offchannel_rework_revert.patch
you know how to do it by this time, right ? in the kernel dir issue: patch -p1 <../iwlwifi-allow-to-switch-to-HT40-if-not-associated.patch for example.
then copy your .config to the kernel dir, execute make oldconfig, then make;make modules_install and copy the built kernel bzImage file to your partition adjust grub/lilo.
Hope this helps. Running gentoo is supposed to be "great learning experience". The truth is that it is a great way to spend so much time and effort to distantly learn something about that is something about linux. + a lot of pain guarantee. |
|
Back to top |
|
|
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Mon Jan 09, 2012 8:14 am Post subject: |
|
|
Well, thanks for your reply.
I must say, I don't have an Intel Wifi adapter (ath9k) nor did I ever had problems with it.
This issue somehow "solved" itself, after a lot of remerging, deleting and what not else.
I truly don't know what fixed it in the end. Unsatisfying, I don't know now if it will appear again if I ever replay a backup again.
For gentoo in general: Sometimes it get's frustrating, right. But personally I never found any distro which even comes close to the gentoo experience within 11 years of linux. It just suits me best and all the other "easy to use" distros give you bad trouble too. Plus the community in the other forums (ubuntu & co) sucks hard, where here I get problems solved most of the time.
Regards, Martux _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|