Bugzilla – Bug 104390
YOU-script for d/l NVIDIA-drivers will lead GeForce 2 users into trouble.
Last modified: 2005-08-15 13:35:08 UTC
Somehow I already had the MS Fonts and NVIDIA script in YOU. Both failed to d/l the fonts/drivers, yet did not throw an error. However it seems that the NVIDIA-script will not change from 9.3 to 10, so there will be problems for users who own a NVIDIA-card (e.g. GeForce2) and use the script, as the most recent drivers do not support any card older than GeForce3. Yet the script's title only states: NVIDIA-drivers. As a result users will end up with X not coming up, which is extremely difficult to solve for people not familiar with sax2. If they just own one computer they even cannot access the internet, because X not coming up, ergo cannot get help online. Best solution would be to make the script detect the graphics card and handle which driver to d/l. The easiest solution would be to offer two scripts, one labled e.g. "Geforce3 and above", the other "older cards". I think that Version: 1.0-7174 is the last driver to work for GeForce 2 and lower.
This should be probably for -> MIR But Installation (YaST) logs would be helpful
This is a problem in the YOU patch and not within YOU. ==> Reassigning to Mr. Maintenance ;-)
Assigning to the "creator" of the updates.
We don't plan to support various nvidia drivers. The script behind the YOU patch is already adjusted (for Beta1!) not to download and try to install the nvidia driver on boards with legacy nvidia chipsets. AFAIK YOU is still not capable to show only Patches, which are useful for the user.
Is there an error message, or does YOU just load the script, not d/l the drivers and show to te user 100% done?
There is an error message: "Legacy nVidia chipsets are no longer supported since " "driver version 1.0-7664" Unfortunately YOU cannot display it. Therefore the script returns with exit code 0, because many users were confused by an error when selecting the nvidia patch with e.g. a radeon board.
We could add it in a POST-message, but I think this will confuse even more users, cause a post-message can't be bound to a condition.