I have a Toshiba with an Atheros AR5008 wireless and using openSUSE 12.1. I have used this combination thru several openSUSE OS’s and several years without problems until now!
At boot the connection starts OK with the mains adaptor connected however with a fully charged battery but WITHOUT the adaptor connected, the wireless will not connect. My wireless router is a netgear a/b/g/n dual band auto switcher and when it is connected works very well.
I used to be able to use <rcnetwork start> to get it reconnected but now it seems that doesn’t work anymore - it directs to <systemctl> (whatever that is?)
Does anyone else have this problem and give me some suggestions or advice on this?
On 01/19/2012 08:06 PM, wiilow wrote:
>
> I have a Toshiba with an Atheros AR5008 wireless and using openSUSE
> 12.1. I have used this combination thru several openSUSE OS’s and
> several years without problems until now!
> At boot the connection starts OK with the mains adaptor connected
> however with a fully charged battery but WITHOUT the adaptor connected,
> the wireless will not connect. My wireless router is a netgear a/b/g/n
> dual band auto switcher and when it is connected works very well.
> I used to be able to use<rcnetwork start> to get it reconnected but
> now it seems that doesn’t work anymore - it directs to<systemctl>
> (whatever that is?)
>
> Does anyone else have this problem and give me some suggestions or
> advice on this?
The answer is likely in the output of the dmesg command. Compare what you see
when you boot with the power connected, and what you see when booting on the
battery.
I would guess it has something to do with power saving in the wireless driver.
You can see what load parameters are available with a ‘modinfo ath5k’ command.
Thanks for your prompt response.
I have run dmesg but the response was identical, with mains adaptor connected AND without.
I am sure you are correct, it probably is connected with the ‘power saving’ config within the wireless driver.
The ‘iwconfig’ script just tells me that it does not associate with the wpa and the 'modinfo (-in my case ath9k) is also showing an identical output - with and without
the mains adaptor connected.
Another point that is interesting : I have tried both scenarios (with and without mains adaptor plugged) BUT comparing a start with systemvinit and systemd.
With systemd wireless starts albeit very briefly, then apparently disconnects and indicates that it is ‘waiting for approval to reconnect’ which - even with my password - does NOT reconnect.
With a sysvinit it does not connect at all!
I’m sorry this is such a long winded note but I am completely at a loss to consider what may be be causing this. It may be something in the ‘policykit’ setup.
Any other thoughts or ideas ?