Bug 179088

Summary: Wireless doesn't work after restart
Product: [openSUSE] SUSE Linux 10.1 Reporter: Chase Stephens <chase.stephens>
Component: NetworkAssignee: Tambet Ingo <tambet>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: suse-beta
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: lsmod output before runnig YaST
lsmod output after runnig YaST
Output of /var/log/messages while running YaST

Description Chase Stephens 2006-05-26 14:06:05 UTC 
My Intel 2200 wireless card works fine after running YaST, but if I restart my system, I have to run YaST again before the net manager will recognize the card.

Novell tells me wireless cards aren't supported, and I haven't been able to find a soltuion on any of the borads, so I'm assuming this is a bug.
Comment 1 Christian Boltz 2006-05-26 18:57:58 UTC 
Please compare the output of   lsmod   before and after running YaST.
Also check if the YaST run causes messages in /var/log/messages.

Some information about your access point would be useful: What type of encryption do you use? Is the ESSID hidden or broadcasted?

A last question: does it work if you use "traditional method with ifup" instead of network manager? (You can configure this in YaST network module.)
Comment 2 Chase Stephens 2006-05-26 21:30:07 UTC 
I'll attach lsmod before and after YaST as well as the output from /var/log/messages while it's running.

My access point is a Linksys wireless router using 64-bit WEP, open system, and the ESSID is broadcast.

If I switch to traditional mode, the interface comes up fine.

Thanks,
Chase
Comment 3 Chase Stephens 2006-05-26 21:32:12 UTC 
Created attachment 85351 [details]
lsmod output before runnig YaST
Comment 4 Chase Stephens 2006-05-26 21:32:53 UTC 
Created attachment 85352 [details]
lsmod output after runnig YaST
Comment 5 Chase Stephens 2006-05-26 21:33:32 UTC 
Created attachment 85353 [details]
Output of /var/log/messages while running YaST
Comment 6 Robert Love 2006-06-02 15:33:53 UTC 
This is not a NetworkManager bug.

Chase: What does `hal-device | grep <interface>` return, where <interface> is your ipw2200's interface (e.g., eth1)?

I am curious of the output before running YaST, when things do not work, and after, when things do work.

Thanks!
Comment 7 Chase Stephens 2006-06-05 12:40:26 UTC 
The output doesn't change. Here's what I get:

hal-device | grep eth0 output:

Before YaST:
  net.interface = 'eth0'  (string)
  linux.sysfs_path = '/sys/class/net/eth0'  (string)

After YaST:
  net.interface = 'eth0'  (string)
  linux.sysfs_path = '/sys/class/net/eth0'  (string)

Is there a particular file under /sys/class/net/eth0 you'd like me to check?

Thanks,
Chase
Comment 8 Tambet Ingo 2007-01-08 10:17:20 UTC 
Still having issues with NM? Can you please attach your /var/log/NetworkManager log file?
Comment 9 JP Rosevear 2007-02-07 15:32:40 UTC 
No response in a month and probably a duplicate.

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