after install suse 11 my wireless not working . I try all setting but useless . I give up and exploring suse 11 then I went to delete my default user and recreate it and reboot . after that some how my wireless is working .
what going on here
Seems to me there are too many possibilities here to give you a definitive answer. I like the possibility that it might have needed just the reboot.
it didn’t work again after disconnect . no matter how many times I try to connect , it always fail .
Found the way to solve this is to run yast then do some modify in network setting and save . then reboot . after that the wireless can connect .
you must redo the step again the next time you try to connect .
I getting sick of this soooo many problem with opensuse 11 (kde 4) . it totally unstable (thinking install back suse 10.3) .
You can install kde3 alonk with kde4 and log into kde3 until kde4 improves, as it will. They can both be installed simultaneously. Or you can reinstall openSUSE 11.0 and select the kde3 desktop rather than the kde4
try that already .the problem is with this new version of networkmanager
Do you mead the network manager in KDE4 or in KDE3.x?
There was a patch pushed out last night for networkmanager. Have you installed it? run ‘zypper dup’ (no quotes) from a console as su, or run the opensuse updater. You’ll need an active Internet connection though.
just done the opensuse updater . after update my wireless network show disable . no matter what i do it just won’t enable . the networkmanager now worse than before update .
what should i do now 
I was also having the same problem as yours … very tired of editing the wireless device in the yast to connect the wireless everytime, but after i updated it with the patch, i edited the wireless device in yast and then restarted the knetworkmanager and delete all the connections saved there, then i created a new one and make check the autoconnect option while creating new connection ( you have to click next a few times to see this option ) and now it works good. it auto connects while i turn on the computer.
you may try to reinstall the knetworkmanager (and try updating with the patch.)
Good Luck
nope it won’t work . I give up . I probably will go back to suse 10.3 and wait until 11.1 come out then try again.
I have been using suse since version 9 until now without any problem . to be frank that I’m quite disappoint with opensuse 11 . soo many obvious bugs here and there that even a novice opensuse user will notice it . but they still released it . it’s like no body be bother to test it.
Finally it work .
here what I did . I reinstall clean suse 11 then I download and install driver from here Download - Linux Wireless .
since I not expert , I not sure whether I compile and install correctly .
after that make change in yast2 and restart . my wireless working fine now . even after I restart/shutdown .
thanks finally .
i haveing this same problem, but after deinstall knetworkmenager everything wokrs good
Yesterday I updated knetworkmanager, and … WiFi stated to work. I rebooted - it works. Today it doesn’t work and I can’t make it work in any way. Knetworkmanager doesn’t see my network ( Vista can see). I tried to install compat-wireless - first make comand failed ( no rules for modules ). WiFi doesn’t work, Sound doesn’t work nd WEB-camera doesn’t work. I hardly can imagine such situaion on Windows. Linuxis not desktop system!
gennadiys wrote:
> Yesterday I updated knetworkmanager, and … WiFi stated to work. I
> rebooted - it works. Today it doesn’t work and I can’t make it work in
> any way. Knetworkmanager doesn’t see my network ( Vista can see). I
> tried to install compat-wireless - first make comand failed ( no rules
> for modules ). WiFi doesn’t work, Sound doesn’t work nd WEB-camera
> doesn’t work. I hardly can imagine such situaion on Windows. Linuxis
> not desktop system!
Would you mind supplying supplying some real information, or would you
just rather bitch about Linux? If the latter, please go back to the
Blue Screen of Death OS (sic) and leave us alone. FYI, wireless on
Linux works as well as it does with Vista. In addition, my openSUSE
11.0 can print to the printer attached to Windows XP - Vista cannot.
My wife’s Vista computer has to relay its printing through my Linux
computer. Don’t tell me how well Windoze works!
If you want to get wireless working, please open a console and enter
the command ‘/sbin/lspci -v’. One of the sets of output will describe
your wireless device. You should post that section. Next enter the
command ‘/sbin/lspci -n’ and post the part of that output that has the
same bus (the part that looks like 04:00.0 at the beginning) as you
found above. Finally, type use a command ‘dmesg > dmesg.txt’. Use any
text editor on file dmesg.txt and post all the lines that relate to
your wireless device.
Larry
Out of interest are you using ndiswrapper at all to expose windows drivers to linux?
Just that if so, and from personal experience, then you will probably need to get suse to trigger a modprobe on ndiswrapper at boot (/etc/init.d/boot.local)
When you use YaST, it does this on request, which then allows access to the driver.
@ gennadiys and all other haters…
Suse is an awesome distro, so don’t say that 11 is no good…I am dual booting a brand new laptop, and guess what? 3 days ago, I had no touchpad, no webcam, no wireless, and no Nvidia drivers…and this morning I finally got EVERYTHING working!
Don’t get me wrong, I have given up in the past, and stuck with my 'Buntus and OS X so many times before…It’s a learning curve, but you feel awesome when it finally clicks…There are things that OpenSuse does that Ubuntu is nowhere near (reverse engineering our crap Broadcom drivers, for instance, so we don’t have to use ndiswrapper in the future)…I dont know too many distros taking the time to do that…
Just because you’re not ready for OpenSuse, don’t think that means OpenSuse isn’t ready for anyone else…I can honestly say that I have problems w/ wireless in Mac OS X Leopard as I do in Linux Distro’s…Problem is, it’s been 10 months and Apple hasn’t released a real “fix,” yet…also using Broadcom I believe, and they’ve only got 3 cards to work with!
Forums are the greatest place on the planet, use them to your benefit…And a little hint, people in here probably aren’t going to appreciate you ditching a distro without posting the output from your terminal…they ask for that so they CAN help you…
I think I’ll go play on my FULLY working HP laptop now 
_Anthony
I am having the same problem on suse 11. i found out something interesting: if i use the networkmanager then the wireless card does not connect to the network, but my ethernet card works fine. if i change the settings in order to use ifup, then the wireless card works fine and the ethernet doesn’t work!
inur wrote:
> I am having the same problem on suse 11. i found out something
> interesting: if i use the networkmanager then the wireless card does
> not connect to the network, but my ethernet card works fine. if i
> change the settings in order to use ifup, then the wireless card works
> fine and the ethernet doesn’t work!
When you use ifup, you need to configure your ethernet with YaST. When
you use NetworkManager, you need to configure your wireless connection.
thank you! now everything is working with networkmanager: wireless and ethernet… but believe me, i don’t know what i did new! i always repeated the same things… confgure here… configure there…:rolleyes:
I just upgraded my Dell Vostro 1400 to 11.0 today and I am having the same kind of garbage going on with my wireless. The Vostro worked 100% flawlessly in 10.3.
I’m not sure exactly why we went backwards with 11.0. This is not the first time this has happened to me and I’ve been with SuSE since the dawn of time.
For me it’s not really that big of a deal, but where I am concerned is if someone had started using 10.3 and found it useful and things were grand then they upgrade to 11.0 and everything goes to heck in a hand basket. Not only is my wireless a major issue, the trackpad is acting completely flaky, it was fine on 10.3 and in the 11.0 gui installer, once booted it’s nearly unusable…
Ah well, not complaining but just letting the team know there are some issues…