https://bugzilla.novell.com/show_bug.cgi?id=216530
Summary: When Atheros card detected, give a hint about binary drivers Product: openSUSE 10.2 Version: Beta 1 plus Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dominique.leuenberger@tmf-group.com QAContact: jsrain@novell.com
When an Atheros card is detected in a notebook, the user needs to install the madwifi package, which for known reasons are not distributed with openSUSE.
It would be a very nice hint for the user if he could get a small information about the website http://en.opensuse.org/Atheros_madwifi in this case.
The solution would be somehow similiar to the one used in xine, about video playing.
If it can not be included in YAST in that short time, at least a comment in the release notes should make it.
https://bugzilla.novell.com/show_bug.cgi?id=216530
locilka@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |kmachalkova@novell.com
https://bugzilla.novell.com/show_bug.cgi?id=216530
------- Comment #2 from sh@novell.com 2006-10-31 04:26 MST ------- AFAIK libzypp does support hardware dependencies, but the way this works is usually that some package has an "enhances" dependency on that hardware. If there is no package that could have this "enhances" dependency (and this is the point here), the only way out I see is to create a pseudo package - one that is basically empty or consists only of a "README" file - that has that "enhances" dependency and either a "notify" text set or, better, a license the user has to confirm. Even though "install notify" might sound better at first, that is only displayed if the user clicks directly on that package, so this won't work out. A license OTOH the user will have to confirm, i.e. he will be prompted in any case.
https://bugzilla.novell.com/show_bug.cgi?id=216530
------- Comment #3 from dominique.leuenberger@tmf-group.com 2006-10-31 04:36 MST ------- That doesn't sound to bad to me.
For it being completely perfect, the maintainer of the MadWifi Packages most probably should mark the dummy package as 'obsolete' by his packages.
And having it always popping up on installation is much better than just having the notify that it could be available. The user really should be informed about that.
https://bugzilla.novell.com/show_bug.cgi?id=216530
------- Comment #4 from cthiel@novell.com 2006-10-31 04:56 MST ------- Klaus, what's your opinion on this?
https://bugzilla.novell.com/show_bug.cgi?id=216530
------- Comment #5 from kkaempf@novell.com 2006-10-31 07:44 MST ------- The 'dummy package approach' is probably the best we can do currently.
This dummy package should also recommend (weak requires) the madwifi package so the real driver gets installed if available.
Going forward, we could make messages (as used in patches) first-class objects to implement hardware-dependant user notifications.
https://bugzilla.novell.com/show_bug.cgi?id=216530
mzugec@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rchevalier@novell.com
------- Comment #6 from mzugec@novell.com 2006-12-04 06:55 MST ------- *** Bug 119812 has been marked as a duplicate of this bug. ***
https://bugzilla.novell.com/show_bug.cgi?id=216530
kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |LATER
------- Comment #7 from kmachalkova@novell.com 2007-02-09 05:31 MST ------- -> 10.3
https://bugzilla.novell.com/show_bug.cgi?id=216530#c8
Katarina Machalkova kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |holgi@novell.com
--- Comment #8 from Katarina Machalkova kmachalkova@novell.com 2007-09-13 08:19:45 MST --- *** Bug 307745 has been marked as a duplicate of this bug. ***
https://bugzilla.novell.com/show_bug.cgi?id=307745
https://bugzilla.novell.com/show_bug.cgi?id=216530
Katarina Machalkova kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Installation Product|openSUSE 10.2 |openSUSE 11.0 Version|Beta 1 plus |unspecified
https://bugzilla.novell.com/show_bug.cgi?id=216530
User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=216530#c9
Stephan Kulow coolo@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER |
--- Comment #9 from Stephan Kulow coolo@novell.com 2008-06-25 03:10:32 MDT --- mass reopening of later+remind bugs of 11.0
https://bugzilla.novell.com/show_bug.cgi?id=216530
User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=216530#c10
Katarina Machalkova kmachalkova@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |libzypp AssignedTo|kmachalkova@novell.com |zypp-maintainers@forge.prov | |o.novell.com QAContact|jsrain@novell.com |qa@suse.de
--- Comment #10 from Katarina Machalkova kmachalkova@novell.com 2009-01-19 05:51:24 MST --- Certainly not an issue that could be solved on yast2-network level - this is something for libzypp maintainers (maybe pulling in related packages when certain hardware is detected already works somehow, but I'm really no expert in this).
https://bugzilla.novell.com/show_bug.cgi?id=216530
User dominique.leuenberger@tmf-group.com added comment https://bugzilla.novell.com/show_bug.cgi?id=216530#c11
--- Comment #11 from Dominique Leuenberger dominique.leuenberger@tmf-group.com 2009-02-11 10:15:17 MST --- Pulling in a package based on existing hardware is done for all sort of drivers, based on the Supplements: tag.
The 'problem' here is that for Atheros, and also broadcom cards, a binary blob needs to be installed in plus.
For the bcm cards there is a simple script (most likely also for atheros) (for bcm it's /usr/sbin/install_bcm43xx_firmware )
The 'problem' is that a 'typical' user installing openSUSE does not know about the existance of this script and he neesd to be informed or even 'supported' in performing this step. (b43-fwcutter is automatically installed if you have a bcm chip, but it's presence remains a mystery for most users...)