Bug 153762

Summary: Add support for ndiswrapper
Product: [openSUSE] SUSE Linux 10.1 Reporter: Michael Stather <kontakt>
Component: NetworkAssignee: Michal Zugec <mzugec>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Enhancement    
Priority: P5 - None CC: andreas.hanke
Version: RC 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Michael Stather 2006-02-27 18:09:31 UTC
Some of the other distribution have this, and IMHO it should also be included in SuSE as fast as possible.
Not that it´s a clean thing, but user just care whether their wireless cards do work or not.
So integrate it into YaST network settings.
Comment 1 Michael Gross 2006-02-28 13:15:12 UTC
Isn't this already featured, Martin?
Comment 2 Martin Vidner 2006-02-28 13:18:44 UTC
Not yet. Which distros have it?
Comment 3 Michael Stather 2006-03-05 17:47:53 UTC
AFAIK Mandriva and Ubuntu, perhaps others too
Ubuntu does also have a very nice tool called "ndisgtk" which lets you add/delete the drivers with a GUI.
Comment 4 Martin Vidner 2006-08-28 11:52:36 UTC
Reassigning to the new maintainer of yast2-network.
Comment 5 Michal Zugec 2006-08-30 06:47:09 UTC
move to later
Comment 6 Stephan Kulow 2008-06-25 09:35: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 7 Stephan Kulow 2008-06-25 09:37:57 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 8 Stephan Kulow 2008-06-25 09:42:19 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 9 Stephan Kulow 2008-06-25 09:53:43 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 ;(