Bug 547916 - No network at all (wireless nor cable) after dist-upgrade
Summary: No network at all (wireless nor cable) after dist-upgrade
Status: RESOLVED DUPLICATE of bug 546213
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Network (show other bugs)
Version: RC 1
Hardware: x86 openSUSE 11.2
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-17 14:38 UTC by Marc Schlegel
Modified: 2009-10-18 09:09 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Schlegel 2009-10-17 14:38:44 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.3 Firefox/3.5.3

HARDWARE: ThinkPad T60p

I did a dist-upgrade yesterday from M8 to RC1 using zypper dup. After everything went fine I did a restart.

Since then, the network isnt working at all. The Networkmanager shows no error, instead he shows the status active. No website is working, cant ping anything, nor is any other network related thing working.

So I tried to access the network via cable, but same thing here. After that, I went to Yast and configured the classic way. After some restarts trying to troubleshot this, I gave up and reverted back to M8 -> network working without any problem. I reverted back using the upgrade functionality on the disc.

Reproducible: Always

Steps to Reproduce:
1.upgrade using zypper dup
2.restart
3.try to use the network
Actual Results:  
no network working at all

Expected Results:  
flawlessly working network
Comment 1 Marc Schlegel 2009-10-17 19:46:35 UTC
with the help of the opensuse forum, there are two steps to solve this.

delete /etc/resolv.conf

run /sbin/netconfig update -f

now network runs fine. still, this shouldnt happen
Comment 2 Stephan Binner 2009-10-18 09:09:17 UTC
dupe

*** This bug has been marked as a duplicate of bug 546213 ***