Bug 193183

Summary: Notify user if (ipw-)firmware is missing
Product: [openSUSE] SUSE Linux 10.1 Reporter: Forgotten User --EoyBps8f <forgotten_--EoyBps8f>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED WONTFIX QA Contact: Stanislav Visnovsky <visnov>
Severity: Enhancement    
Priority: P5 - None CC: suse-beta
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User --EoyBps8f 2006-07-18 16:04:43 UTC 
In newsgroups as well as on mailinglists one often encounters people that state that YaST has recognised their WLAN, e.g. ip2xxx, but the card does not work.

For those people it would be helpful, if YaST network-module would not just show the WLAN-card, as that suggests that there is nothing missing and just the need to configure it, but issue a notification that the firmware is missing.

At least for the ipw-firmware there is an easy pattern to check for, i.e. if there are ipw* files in the firmware-dir. I am not sure about other wlan-driver's firmware.
Comment 1 Martin Vidner 2006-08-28 11:52:46 UTC 
Reassigning to the new maintainer of yast2-network.
Comment 2 Michal Zugec 2006-08-30 06:47:16 UTC 
move to later
Comment 3 Stephan Kulow 2008-06-25 09:39:58 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:41:03 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:43:40 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:56:39 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(