Bug 7946 - The name of NVidia card ranges is confusing
Summary: The name of NVidia card ranges is confusing
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard: MGA2TOO
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2012-11-01 16:43 CET by Henri de Solages
Modified: 2019-04-08 20:19 CEST (History)
4 users (show)

See Also:
Source RPM: ldetect-lst
CVE:
Status comment:


Attachments

Description Henri de Solages 2012-11-01 16:43:24 CET
Description of problem:
In XFdrake, NVdia cards are grouped by series in a way not obvious at all for non specialists. Notably, the range "GeForce 6100 to GeForce 360" is unintelligible for someone who doesn't know NVidia naming system history.

Version-Release number of selected component (if applicable):
Drakxtools version 14.22.3

How reproducible:
Always.

Steps to Reproduce:
1.Open MCC
2.Choose Hardware â Set up the graphical server
3.Choose Vendor â NVidia

I suggest to split this category into 2:
"GeForce 6100 to GeForce 9900"
"GeForce 100 to GeForce 360"
Manuel Hiebel 2012-11-05 23:21:14 CET

Keywords: (none) => USABILITY
Version: 2 => Cauldron
Assignee: bugsquad => thierry.vignaud
Whiteboard: (none) => MGA2TOO
Severity: minor => enhancement

Comment 1 Thierry Vignaud 2012-11-06 11:33:02 CET
Anssi what do you think?
Can we find some names related to generations instead?

CC: (none) => anssi.hannula
Source RPM: drakx-kbd-mouse-x11-0.102-1.mga2.src.rpm => ldetect-lst

Comment 2 Henri de Solages 2012-11-06 19:49:13 CET
Even if you can, the generation names are not written neither on the box nor on the card, and probably not even in the instructions. I had to read the Wikipedia article to understand that my GeForce 7200GS was considered as "7 series" and was between GeForce 6100 and GeForce 360. And I went to Wikipedia just because I couldn't find any category for my card in Mageia's list.
Comment 3 Anssi Hannula 2012-11-21 22:28:36 CET
Clarifying the list would be good, however splitting the category as suggested would take some manual work as we'd need to figure out which pci ids belong to which category... It is doable, though, if one has time.

Note that it usually should not be necessary for the user to figure out which of the cards listed matches their card, as that is auto-detected. The UI is not very clear on that, though...
Comment 4 Lewis Smith 2019-04-06 14:26:22 CEST
Trying to clear this very old (7y) bug if possible. In the Mageia 6 XFdrake NVidia list, at the end of comment 0, this line has changed to:
 GeForce 6100 to GeForce 7950
and there is no sign of this one:
 GeForce 100 to GeForce 360

@Bill, TJ : I am CCing you as known Nvidia gurus for your comments, please.
My feeling is to close this (old if necessary), ideally knowing it no longer applies.
TIA

CC: (none) => andrewsfarm, lewyssmith, wilcal.int

Comment 5 Thomas Andrews 2019-04-06 15:09:59 CEST
The gpus are listed according to the driver that applies, and whether there is a proprietary driver available. That changes with each release, as Nvidia issues new drivers and ceases support for legacy drivers.

The list in M7 is less confusing than the one in Cauldron was when this bug was filed, but it still has one confusing point: when Nvidia switched from using 4-digit numbers to using 3 digits. And there's little that can be done, for now, because the "Geforce 9800" and "Geforce 210" use the same driver, so they need to be listed together.

But, as pointed out in Comment 3, XFDrake usually points out the correct group. I've never seen it tell me the WRONG one.

So yeah, I think this could be closed as either old, or no longer valid.
Comment 6 Thierry Vignaud 2019-04-08 17:53:07 CEST
Done

Resolution: (none) => OLD
Status: NEW => RESOLVED

Comment 7 Lewis Smith 2019-04-08 20:19:28 CEST
Thanks TJ for your input; which I see Thierry seized!

Note You need to log in before you can comment on or make changes to this bug.