On 28/08/14 15:44, Graham P Davis wrote:
On Thu, 28 Aug 2014 14:00:42 +1000 Basil Chupin
wrote: On 26/08/14 17:52, Graham P Davis wrote:
On Tue, 26 Aug 2014 17:15:58 +1000 Basil Chupin
wrote: I have counted up to 10 several times and now feel I am more or less composed enough to post this message concerning on how to set-up wi-fi in 13.2.
How the h*** is it done?!
For 13.1 I looked at the YouTube video on how to do this and had it working within 30 seconds. But in 13.2 I have now wasted an hour or so trying to figure out the mess which is 'networking'. And what the h*** is "wicked"?!
Is there some documentation on how to get wi-fi working in 13.2, please, or at least a hint on what to do to get my laptop's wi-fi configured?
I've tried using "wicked" with identical settings to what worked with "ifup" but have had no success. I've also tried as many variations as I could think of but still no joy.
NetworkManager worked first time with no bother but, for certain reasons, I prefer to use "ifup". Thanks for the response.
I cannot get the NetworkManager working so I have to ask you - as I will also ask Neil: did you 'upgrade' to 13.2 Factory FROM a working copy of 13.1 or did you install 13.2 as a CLEAN, FRESH installation from, say, the ISO disc?
I made a clean installation from the x86_64 DVD iso using various snapshots up to 20140820. In each case, "wicked" refused to function but NetworkManager worked first time every time.
Thanks again for replying, Graham. Since posting the above I have had a change of fortunes in both 13.1 and 13.2 Factory :-) . A somewhat obtuse statement but let me explain by first talking about 13.1 and then about 13.2. I have both 13.1 and 13.2 installed on the laptop. I got Network Manager working on 13.1 as I mentioned already in another earlier post. But today I noticed that I had forgotten to upgrade KDE to 4.13.3 so I did the upgrade. This resulted in the wi-fi going belly up :-( . Working one moment with KDE 4.11.x but not working as soon as 4.13.3 was installed. So I went looking. What I found is that the applet for wi-fi in the (bottom) panel disappeared and, more importantly, for some reason the Network setting in YaST got screwed up and the Change Host via DHCP got itself deselected. After ticking this box the w-fi started to work again. And just on this point- when I boot up the laptop in 13.1 the wi-fi becomes active almost instantly, whereas in 13.2......... see below. Now re 13.2 Factory. Once again, the problem here lay with the Change Host via DHCP being unselected. Ticking this box got wi-fi working. However, on rebooting 13.2 the wi-fi was NOT working :-( . After some "fooling around" I had it working again mostly by blind luck I think because, as I said, the applet which was in 13.1 is not in 13.2 but by pressing something or another a menu similar to what is found in 13.1 appeared and I was able to type in (hex) password and this appears to have been saved somewhere because on the next reboot wi-fi was working ..... BUT, but it takes at least 1 minute+ to become active, ie actually find the router/modem, whereas in 13.1 this process is almost instantaneous. Don't know the reason for this delay but the good news is that wi-fi finally gets going :-) . * * * There is one more thing re above which caused me a bit of headache - but I now do not remember if it was in 13.1 or 13.2 Factory :-( . At some point after a reboot I couldn't get wi-fi to connect even though it was doing so a few minutes earlier, before the reboot, so I kept going into YaST to check the settings there. But every time I ran YaST I would get the message: WARNING! Network currently handled by Network Manager or completely disabled. YaST is unable to configure some options. Now, I thought to myself, what the h*** is the good of you, YaST, if you cannot configure the Network Manager?! Anyway, this is where I poked around to find where NM could be "activated" since the NM applet had disappeared. I did find the place - cannot remember where now :-( but I will find it if I have to - and what I found was that WEP password somehow dropped a character and this caused the WARNING! msg in YaST. As soon as I corrected the WEP password wi-fi became "activated". BC -- Using openSUSE 13.1, KDE 4.13.3 & kernel 3.16.1-6 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org