SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In YaST2 where you set up the interfaces, you can choose to have the interface start on boot. The problem might be that eth0 is setup to start on boot when you aren't using it. Try changing it for the NIC card to start on connection.
Doing this will change which interface is listed in the ifplugd configuration file.
i think yast2 has a bug there. when i changed it in yast2 -> networkdevices -> inter PRO/wireless 2200 -> advanced.. -> detaied setting -> cable connection : nothing changed in /etc/sysconfig/netwok/ifcfg-wlan....
i edited the file and change ifplug into manual
i did it for both ifcfg-wlan.. anud ifcfg-eth.... i reboot the computer,
load up the device with "ifup". connected the net - fine, load a browser and... the system freezed again!!!
After you do "ifup <device>" try doing a "ping google.com" and see what happens.
then check ifconfig for an IP address.
if all goes well, from your terminal type "firefox" and see if you can get any error output from your terminal?
If it freezes again after all that, I'd suggest rebooting and checking /var/log/messages for errors, you'll have to look towards the bottom and check date/times.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.