Anyhow with X running, (As someone who never uses & hates Networkmanager) try for a wifi type icon in the top right hand corner. You need your ESSSID, & password for wpa_supplicant.

After my last posting, I had a lot of trial-and-error, almost random attempts, with a lot of searching through SUSE docs, googling how-to-rpm (offline), networkmanager, etc.
....
A) Firstly, the box had been set up to use the network settings via the "old method" (ifup), and so I did (try to) use YAST to set up my wlan0, -even to the router name, WPA password, etc. But, I kept getting "The following packages need to be installed: iw." I found this posting:
https://forums.opensuse.org/showthre...ine-iw-package
The guru there showed some paths that eventually led me to:
http://ftp5.gwdg.de/pub/opensuse/dis...s/suse/x86_64/
pretty complete - had
iw-0.9.18-6.1.x86_64.rpm
and
rfkill-0.4-7.1.x86_64.rpm (just in case -- saw this on a lot of other forums as very useful)
I learned to do rpm -i iw-0.9.18-6.1.x86_64.rpm
-Then, went back into YAST, finished up (chose my router's name in the list, added the WPA1,2-PSK PW), and then my iwconfig looked great. -But it still wouldn't start.

2) So --- Tried to reset YAST Network Settings to update via NetworkManager (after, as requested, starting NM via line-command (all I could find)). -In this case, the settings eventually always died after a long "compile", saying "No Network"...

3) Just decided to hack around the GUIs, and went into "System Settings", and found it has "Network Connections". -Somewhere in here, BTW, KWALLET appeared to me to store info ;-) . Anyway, I manually "forced" the wireless to choose my own wifi router via this tool (again WPA1,2 PSK), and added its PW. DHCP - yes, but wasn't at all sure what MODE to use (I chose the default, "Infrastructure", instead of "Ad-Hoc"), left the BSSID as blank, MTU as "Automatic"... "PROXY" ??? -I decided on "Automatically detect...", this time. -Looked darn close! -Some of my various hacking around sent out warnings to me that my wlan is blocked by the firewall, so I found a "Firewall" GUI, and chose to switch the wlan0 to "External Domain", -which, it seemed was necessary to open things up...

4) Things looked pretty, but still nothing... I then double-clicked on the K-NetworkManager -- didn't pop up or anything, but I got a notice that I was connected! -And the old firefox finally showed internet acivity!!!

5) Reboot -and , yup, "Access Point: Not-Associated" again. -Went over to the apps, found that KNetworkManager again, and dragged it to my desktop as an icon. Double-clicked that, and I get an access notice again. -And wifi internet...
-So, now I can do just a double-click that icon to turn on the wifi connection to my router (only).


Well, I do have internet now, thanks to your help (and all those previous forums out there). -Interesting that, on that machine, some sites DID block me (like DUCKDUCKGO)using firefox. Don't know if it's some bad SSL/TL/ID/IP from my current 11.4 (2011) system, -or just the outdated encryptions in the 2011 FIREFOX??? (BTW, that old firefox is wayyyy more user-friendly and it's wayyy easier to block cookies, etc. -I guess this was before the mega-corps took over them too?? )

Any better ideas / help still much appreciated!! -This was mostly trial-and-error ;-) ...

Congratulations!

That's about as good as you get with Networkmanager. Wifi is sweet when it works, and a bitch when it doesn't. You can mark this solved. One suggestion might be to copy the relevant folder into the Startup folder, so the network always boots when you start X?

Hi

Where are these folders? -Any ideas before I close down this item?

Thanks!

Sorry - I meant the relevant startup icon(s). I know little to nothing about networkmanager - by deliberate choice. I never use it.

-Don't blame you, -but it's at least working!

-What do you use instead, BTW?

I'm in Slackware: No systemd; no networkmanager unless you want it. I use init scripts.

I go back to the days when it was a real issue to get each peripheral working, and I'm used to doing stuff. I set that up, and it never varies.

Sounds like a good setup, -and real knowledge
Yes, I'm not a monster fan of GUIs myself , -especially "cloudy" ones... -I'll take "xv" any day over whatever image viewers ;-)
Slackware, I think, is at least one of the original linux's, eh? Thumbs up!

I was playing with linux some time before I 'promoted' myself to slackware. No dependency checking, no 'one size fits all.' You get a system that you set up your way - the way you like it. It means work at times. I'd suggest to do an LFS build first.

Slackware does sound like what a "real" unix should be, so I'm going to look into that for sure

But, at this moment, I've got an old linux box up and running, and have managed to reply for the 1st time on it (had to use konqueror -- the firefox version is too out-dated and inflexible to connect to almost anything, whereas at least konqueror will allow some certificate overrides).
-There are the (by now, falling-behind) large scientific packages that were laboriously loaded on by the previous owner that I'll be playing with. -When I decide to gamble, it'll be time for the big upgrade! ;-)

Cheers again, business kid!

@Craigkes: New problem, new thread is usually the rule here.

Short answer: The driver and firmware is in a later kernel you haven't got installed. I don't know when it was added. Alternatively you can d/l it and compile your own. Please do a thread search.