I just installed OpenSuse on my Eee PC 1015PW and when I go to Network Management Settings the Wireless tab is greyed out.
Ubuntu could connect with wireless on this 1015PW, but OpenSuse cannot. Anyone know how I can fix this please?

The fix is to test other distros and find one that does. Use unetbootin to make live USB drives to boot from. Then, use the "full size" ISO image for the install. If Ubuntu works, chances are that Mepis or Mint will work too. Try fuduntu or fedora as well.

I had some problems with wireless (nothing to do with SuSE.12.1 - more to do with BT or my ISP). I ended up launching it through a terminal (Konsole in my case) with the following alias:

alias uplan="su -c 'ifup wlan0'; ping -c 3 www.example.com"

The 'ping' sends a packet 3 times to www.example.com (which seems to be a site set up purely for the purpose of being 'pinged'). If the connection has been successful, you should get an output that ends like this:

--- a749.g.akamai.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time
2003ms
rtt min/avg/max/mdev = 29.860/30.835/31.428/0.724 ms

You can terminate the connection using the alias:

alias dlan="su -c 'ifdown wlan0'"

If this doesn't work, something is wrong!

Best of luck.

Ming

Gnome...

Probably the easiest solution is to search "Software Management" in Yast for "NetworkManager", remove the package "NetworkManager-kde4-libs" and replace it with "NewworkManager-gnome" Then follow the steps in the enclosed web-link. Polish may not be your language, but the SUSE GUI is the same, just follow the pictures.

When you're done, this will allow you to start the Gnome applet by typing "nm-applet" in the search box at the top of the menu that opens when you click on the SUSE Kickoff gecko. An icon may, or at times, may not appear in the panel. Even if it is not visible, you will see a space created. Click on the space and you will see the applet settings.

I omitted the step changing the appearance to QtCurve, which may be why the launch icon sometimes doesn't show.

KDE4 has had a problem with its net-manager applet for a long time, too long.

http://susestarter.blogspot.com/2011...use-gnome.html

Sometimes individual desktops misbehave more then others. You can easily have multiple desktops on SuSE. Heck, just install Gnome itself via ethernet. Get LXDE & xfce while you're at it. If one gets online, usually the others can also use that connection. God knows why...

You may have many but...

The applet alone is enough to solve the problem, and its dependencies aren't so extensive that they amount to an installation of most of Gnome along with KDE.

In general though, its best to have more then one desktop. Connecting to printers, DVD burners, handling different file types & modifying the commands in desktop icons all are handled very badly or very well depending on what desktop you use. In linux, there is more then one way to skin a cat.

Run "lspci -v" to determine what the wireless device is. Run "lspci -n" for the manufacture's ID for the devices controller. This info will provide information on the kernel module needed. Then you may need to locate firmware for the kernel module to operate. For atheros devices, you usually don't.

A kernel module is needed before you can even try to authenticate. The yast2 network configuration tool can guide you through the rest.

Post the relevant output from the lspci commands I listed. We can help you more with that info.

1 members found this post helpful.