[FEAT] Maybe we can output the model of the chip currently used by the graphics card?
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- c
- Área
- cli, operating-systems
Línea de trabajo
En el issue no se identifican archivos de implementación, pruebas ni puntos de entrada. Empieza localizando el módulo existente de fastfetch para la información de la tarjeta gráfica y su detección de hardware específica de la plataforma, y después compara la salida disponible de lspci en Linux y Windows. Se considera terminado cuando se informe del nombre del chip gráfico allí donde la detección sea compatible, sin perder el nombre existente de la tarjeta ni la salida de la memoria de vídeo.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
In most cases, the current information (graphics card name and video memory capacity) does indeed reflect all the information many people need to know. However, as an enhancement, maybe we can output the specific chip model of the graphics card? This would be useful in some scenarios, because graphics cards with the same marketing name may actually have different chip models (for example, RTX4060 uses AD107 and AD106 chips to provide the same specifications, while Radeon RX550 uses two chips (Lexa PRO (also known as Polaris 12) and Baffin LE) to offer two specifications (512SP and 640SP)).
This makes providing more information (such as chip name and the number of stream processors) useful. However, there seems to be no universal method to obtain the accurate number of stream processors, so I won’t make any comments or requests about this. But in most cases, outputting the chip name should be possible. On Linux, lspci can usually do this. For example, the following lspci line indicates that this is an RX550 series graphics card based on the Lexa PRO chip:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7)
And (at least for me), lspci on Windows is also effective. I downloaded lspci for Windows from here, and it correctly outputted my graphics card model (Radeon RX6500XT) and the chip it uses (Navi 24):
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] (rev c1)
Motivation
Custom modules should be able to achieve this, but I don’t think it would be inappropriate to incorporate it as part of fastfetch. fastfetch is already capable of retrieving a significant amount of hardware information, this proposal aligns with your requirements (“We only accept hardware or system level software feature requests.”) and should be feasible to implement.
Additional context
I also tested this on a computer with an Intel integrated graphics card. lspci outputs the code name of the current integrated graphics card, which is similar to my goal of “outputting the graphics card chip model” (used to distinguish graphics cards with different chips but the same marketing name). I think we should do this for Intel integrated graphics cards. Here is the output:
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 03)
I also tested AMD integrated graphics cards from different periods, and there were no issues.
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev e2)
c1:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 (rev c8)
Although I currently don’t have an environment to test Nvidia graphics cards, I vaguely remember that for Nvidia graphics cards, lspci also outputs the chip name.
(Sorry, I am using a translation service, so I might have inadvertently used an incorrect way to express my request. I hope you can understand and be tolerant of this. Thank you very much!)
- Lenguaje dominante
- C
- Estrellas
- 25.4k
- Forks
- 947
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 21
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de fastfetch-cli/fastfetch
-
[LOGO] VentoOSAbiertologo request
Dificultad 1/5 Menos de una hora Aptitud para principiantes 80/100
fastfetch-cli/fastfetch#2742 ·
Los mantenedores suelen responder en 1 día
-
[LOGO] MacroMag OSPosiblemente ocupada @maldyrek la tomó hace 1 día. Abiertologo request
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
fastfetch-cli/fastfetch#2740 ·
Los mantenedores suelen responder en 1 día
-
logo request
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
fastfetch-cli/fastfetch#2713 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[LOGO] Visnux LinuxPosiblemente ocupada @rafaelsoje la tomó hace 19 días. Abiertologo request
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
fastfetch-cli/fastfetch#2700 ·
Los mantenedores suelen responder en 1 día
-
[LOGO] ZelixOSPosiblemente ocupada @Hwi0228 la tomó hace 24 días. Abiertologo request
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
fastfetch-cli/fastfetch#2685 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de fastfetch-cli/fastfetch
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
good first issue kernel
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
JackFurton/who-would-build-a-kernel-in-java#316 ·
Los mantenedores suelen responder en 1 día
-
Bandwidth selector rotary direction is inconsistent with the regular menu on portable modelsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
PE5PVB/TEF6686_ESP32#970 ·
-
bug sev-3
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día