Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
2715 connectés 

 

 

 Mot :   Pseudo :  
  Aller à la page :
 
 Page :   1  2  3  4  5  ..  36  37  38  ..  48  49  50  51  52  53
Auteur Sujet :

[ Nvidia ] Le topic des drivers (304.60)

n°1147457
thana54
made in concept
Posté le 09-07-2009 à 13:16:31  profilanswer
 

Reprise du message précédent :
J'ai aussi du mal avec le 64bits. J'ai dû repasser en 32bits à cause de ca :/

mood
Publicité
Posté le 09-07-2009 à 13:16:31  profilanswer
 

n°1147461
BloodyCarn​age
Posté le 09-07-2009 à 13:44:07  profilanswer
 

C'est pas une question d'avoir du mal en 64bit, le 185.18.14 est notoirement bugé. Les mauvaises langues diront que c'est justement pour ça que c'est une version "stable" :D
Le 185.14.10 beta fonctionne, le 190.09 alpha (?) aussi.

n°1147463
Bitman
STAY APART
Posté le 09-07-2009 à 13:45:30  profilanswer
 

je suis repassé en 180 [:cupra]
 
au moins ca marche direct :o

n°1148209
Sylfurd
UUUURUTORAMAN §§
Posté le 13-07-2009 à 13:38:17  profilanswer
 

Je copie colle mes aventures sur le topik Ubuntu ici puisque cela semble lié avec les drivers Nvidia. J'aimerai savoir si vous rencontrez le même souci, ou si les derniers drivers le resolvent ou pas :o

Sylfurd a écrit :

Hello !

 

Dites, malgrès mon Quad Core, j'ai des performances catastrophiques en Javascript sous Ubuntu et Firefox (3.0 et 3.5)

 

J'ai testé Peacekeeper: http://service.futuremark.com/peacekeeper/index.action et tout rame atrocement, la fenetre freeze même dans la plupart des tests, et le test ne se termine même pas ...

 

Sous chromium natif, c'est jsute parfait tout est ultra fluide, normal vous allez me dire.

 

Là où ça devient drôle c'est qu'en Virtual Box avec Windows XP et Firefox 2.0 ça tourne beaucoup mieux (PeaceKeeper et le Javascript en général).

 

Et là où ça m'embète c'est que je suis développeur Web et assez fan du javascript ...

 

Avez-vous observé le même genre de problèmes ?

Sylfurd a écrit :

Apparement ça semble être un probleme connu avec les drivers officiels Nvidia: https://bugs.launchpad.net/ubuntu/+ [...] bug/223238

Sylfurd a écrit :

Oui, j'viens de désinstaller les drivers Propriétaires Nvidia et ça tourne normalement maintenant ( c'est à dire 100 fois mieux bien que Peacekeeper ne se finisse toujours pas, mais ça peut venir de mes plugins ça )

 

Va falloir que je teste les drivers 180.


Message édité par Sylfurd le 13-07-2009 à 13:39:03

---------------
NNiD: Sylfurd
n°1148210
thana54
made in concept
Posté le 13-07-2009 à 13:43:57  profilanswer
 

J'ai testé peacekeeper, et je vais un score assez minable :whistle:
Dans les 400 avec un sempron @1.6GHz et un chispet 8200.

n°1148211
Sylfurd
UUUURUTORAMAN §§
Posté le 13-07-2009 à 13:45:35  profilanswer
 

Bin en fait sous virtualbox avec FF2.0 j'ai 400 et quelques, c'est aps beaucoup, mais ça tourne BEAUCOUP mieux que sous Ubuntu ... Genre l'animation avec les vaisseaux spatiaux et les reflets j'ai du 1 image toutes les 5 secondes O_O Toi ça tournait bien ? Quelle distro ?


Message édité par Sylfurd le 13-07-2009 à 13:46:24

---------------
NNiD: Sylfurd
n°1148212
thana54
made in concept
Posté le 13-07-2009 à 13:46:59  profilanswer
 

Ah c'est pas beaucoup mieux chez moi, j'ai une sensation de fluidité sur cette scène qu'une seule fois, sinon c'est le roman photo.

n°1148217
Sylfurd
UUUURUTORAMAN §§
Posté le 13-07-2009 à 13:57:22  profilanswer
 

En plus je peux pas me passer de l'accélération 3D, je développe un site qui utilise massivement du Javascript et la 3D en applet java [:hahaguy]

 

Et du coup j'ai soit l'un soit l'autre qui tourne correctement :D


Message édité par Sylfurd le 13-07-2009 à 13:59:18

---------------
NNiD: Sylfurd
n°1148220
BloodyCarn​age
Posté le 13-07-2009 à 14:03:23  profilanswer
 

Comme j'ai déjà répondu sur l'autre topic, chez-moi-ça-marche (C) sur kubuntu ; c'est pas foudroyant dans certain tests, mais la scène des vaisseaux est aussi fluide qu'une vidéo.

n°1148223
Sylfurd
UUUURUTORAMAN §§
Posté le 13-07-2009 à 14:09:44  profilanswer
 

t'as les piloets 190, j'vais vori ça de plus près :jap:


---------------
NNiD: Sylfurd
mood
Publicité
Posté le 13-07-2009 à 14:09:44  profilanswer
 

n°1148225
Sylfurd
UUUURUTORAMAN §§
Posté le 13-07-2009 à 14:30:15  profilanswer
 

Ca marche parfaitement avec les dernieres stables: 185.18.14 [:shay]


---------------
NNiD: Sylfurd
n°1148227
thana54
made in concept
Posté le 13-07-2009 à 14:32:19  profilanswer
 

euh non, pas chez moi alors. Bon j'avais un peu la flemme de fermer mes autres onglets aussi (flash, ajax à gogo).

n°1148228
Sylfurd
UUUURUTORAMAN §§
Posté le 13-07-2009 à 14:37:44  profilanswer
 

Moi c'est le jour et la nuit, ça fait plaisir :D Bon j'ai toujorus pas mon score final mais ça je m'en fiche, j'peux enfin naviguer sans problème !


Message édité par Sylfurd le 13-07-2009 à 14:38:06

---------------
NNiD: Sylfurd
n°1148229
Sylfurd
UUUURUTORAMAN §§
Posté le 13-07-2009 à 14:43:33  profilanswer
 

thana54 a écrit :

euh non, pas chez moi alors. Bon j'avais un peu la flemme de fermer mes autres onglets aussi (flash, ajax à gogo).

Après t'as pas une foudre de guerre non plus :o


---------------
NNiD: Sylfurd
n°1148289
the_k586
♥ Punk à Chats ♥
Posté le 13-07-2009 à 18:50:04  profilanswer
 

Minefield(v3.6a1pre) Scored:
2385 Points

 

Midori(v0.1.7) Scored:
4887 Points

 


:o


Message édité par the_k586 le 13-07-2009 à 18:55:57

---------------
♦ bl0g ♦ // ♠ Twitter ♠ // << Just for the lulz ! The Only reason anyone does anything >> // Free Open DNS
n°1149932
zaverell
Posté le 21-07-2009 à 16:35:10  profilanswer
 

salut,
 
pilote 190.16 beta officiel du jour  
 
http://www.nvidia.fr/object/linux_ [...] 16_fr.html
 
à tester  
 
  :)

n°1149933
Profil sup​primé
Posté le 21-07-2009 à 16:38:09  answer
 

Dites ça sert vraiment de mettre a jour ses drivers ? (jai une 8600M GT), y a des gains de perfs ?

n°1149934
raphoun
Posté le 21-07-2009 à 16:38:39  profilanswer
 

zaverell a écrit :

salut,
 
pilote 190.16 beta officiel du jour  
 
http://www.nvidia.fr/object/linux_ [...] 16_fr.html
 
à tester  
 
  :)


Cool merci :)
 
EDIT: ne marche pas avec ma 8600GTM, j'ai un écran noir à la place de GDM...

Message cité 1 fois
Message édité par raphoun le 21-07-2009 à 17:01:19
n°1149936
thana54
made in concept
Posté le 21-07-2009 à 16:46:53  profilanswer
 


Corrections de bugs ? Améliorations dans certaines utilisations ? ...

n°1149950
BloodyCarn​age
Posté le 21-07-2009 à 17:19:07  profilanswer
 

Je dirais surtout : compatibilité avec les xorg/kernel récents.

n°1149958
thana54
made in concept
Posté le 21-07-2009 à 18:17:55  profilanswer
 

Changelog de la version beta

Citation :


Release highlights:
 
    * Added GLX protocol support (i.e., for GLX indirect rendering) for the following OpenGL extensions:
          o GL_ARB_draw_buffers
          o GL_EXT_Cg_shader
          o GL_EXT_gpu_program_parameters
          o GL_NV_fragment_program
          o GL_NV_gpu_program4
          o GL_NV_register_combiners
          o GL_NV_vertex_program1_1
          o GL_NV_vertex_program2
    * Added unofficial GLX protocol support (i.e., for GLX indirect rendering) for the following OpenGL extensions:
          o GL_ARB_geometry_shader4
          o GL_ARB_shader_objects
          o GL_ARB_texture_buffer_object
          o GL_ARB_vertex_buffer_object
          o GL_ARB_vertex_shader
          o GL_EXT_bindable_uniform
          o GL_EXT_compiled_vertex_array
          o GL_EXT_geometry_shader4
          o GL_EXT_gpu_shader4
          o GL_EXT_texture_buffer_object
          o GL_NV_geometry_program4
          o GL_NV_vertex_program
          o GL_NV_parameter_buffer_object
          o GL_NV_vertex_program4
      GLX protocol for GL_EXT_vertex_array was also updated to incorporate rendering using GL_ARB_vertex_buffer_object. Use of these extensions with GLX indirect rendering requires the AllowUnofficialGLXProtocol X configuration option and the __GL_ALLOW_UNOFFICIAL_PROTOCOL environment variable.
    * Fixed a bug that caused glXGetVideoSyncSGI, glXWaitVideoSyncSGI, and glXGetRefreshRateSGI to operate on the wrong screen when there are multiple X screens.
    * Fixed glXQueryVersion to report GLX version 1.4. NVIDIA's GLX version has been 1.4 for several releases, and was already reported as 1.4 in the GLX client and GLX server version strings.
    * Fixed a problem that caused window border corruption when the screen is rotated.
    * Fixed a bug that causes corruption or GPU errors when an application paints a redirected window whose background is set to ParentRelative on X.Org servers older than 1.5. This was typically triggered by running Kopete while using Compiz or Beryl.
    * Added support for configuring the GPU PowerMizer Mode on GeForce 8 or later GPUs with multiple performance levels via nvidia-settings and NV-CONTROL.
    * Fixed a bug in VDPAU that could cause visible corruption when decoding H.264 clips with alternating frame/field coded reference pictures, and a video surface is concurrently removed from the DPB, and re-used as the decode target, in a single decode operation. This affected all GPUs supported by VDPAU.
    * Fixed a bug in VDPAU that could cause visible corruption near the bottom edge of the picture when decoding VC-1 advanced profile clips whose heights are not exact multiples of 16 pixels, on G98 and MCP7x (IGP) GPUs.
    * Enhanced VDPAU to better handle corrupt/invalid H.264 bitstreams on G84, G86, G92, G94, G96, or GT200 GPUs. This should prevent most cases of "display preemption" that are caused by bitstream errors.
    * Fixed an X server crash when using the VDPAU overlay-based presentation queue and VT-switching away from the X server.
    * Enhanced VDPAU's detection of the GPU's video decode capabilities.
    * Fixed a bug in VDPAU that could cause ghosting/flashing issues when decoding H.264 clips, in certain full DPB scenarios, on G98 and MCP7x.
    * Fixed VDPAU to detect an attempt to destroy the VdpDevice object when other device-owned objects still exist. VDPAU now triggers "display preemption", and returns an error, when this occurs.
    * Enhanced VDPAU's error handling and resource management in presentation queue creation and operation. This change correctly propagates all errors back to the client application, and avoids some resource leaks.
 
The 190.16 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP.
The 190.16 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86-64 is available for download via FTP.
 
Please see the README (x86, x86_64) for more information about this release.
 
Please note: This NVIDIA Linux graphics driver release supports GeForce 6xxx and newer NVIDIA GPUs, GeForce4 and older GPUs are supported through the 96.43.xx and 71.86.xx NVIDIA legacy graphics drivers. GeForce FX GPUs are supported through the 173.14.xx NVIDIA legacy graphics drivers.
 
Please also note: If you encounter any problems with the 190.16 NVIDIA Linux graphics driver release, please start a new thread and include a detailed description of the problem, reproduction steps and generate/attach an nvidia-bug-report.log file (please see http://www.nvnews.net/vbulletin/showthread.php?t=46678 for details).

n°1149959
burn2
Pour ceux qui viendront après
Posté le 21-07-2009 à 18:19:37  profilanswer
 

Citation :


 Added support for configuring the GPU PowerMizer Mode on GeForce 8 or later GPUs with multiple performance levels via nvidia-settings and NV-CONTROL


 
ça j'aimerais bien comprendre pourquoi les GF6 et 7 n'y ont pas le droit...
 
Sinon pas mal de changement apparement.


---------------
"C'est vrai qu'un type aussi pénible de jour on serait en droit d'espérer qu'il fasse un break de nuit mais bon …"
n°1149960
thana54
made in concept
Posté le 21-07-2009 à 18:20:57  profilanswer
 

Surtout des corrections de bug pour vdpau. Donc à tester et on ressort la trousse de clips :p (et le mouchoir au cas où)

n°1149968
BloodyCarn​age
Posté le 21-07-2009 à 19:02:46  profilanswer
 

burn2 a écrit :

Citation :


 Added support for configuring the GPU PowerMizer Mode on GeForce 8 or later GPUs with multiple performance levels via nvidia-settings and NV-CONTROL


 
ça j'aimerais bien comprendre pourquoi les GF6 et 7 n'y ont pas le droit...
 


 
+1
C'est un peu l'habitude de nvidia de créer plusieurs versions d'une techno qui n'ont pas du tout la même implémentation même si elles partagent le même nom marketing. Au final, nvidia ne supporte que la plus récente, mais ça suffit à créer un flou dans la tête du consommateur.
A mon avis, les GF6 et 7 se feront éjecter dans les legacy d'ici la fin de l'année ; je crois qu'on sait tous ce que ça veut dire en terme de qualité du support.

n°1150050
Profil sup​primé
Posté le 22-07-2009 à 10:06:25  answer
 

raphoun a écrit :


Cool merci :)
 
EDIT: ne marche pas avec ma 8600GTM, j'ai un écran noir à la place de GDM...


 

thana54 a écrit :


Corrections de bugs ? Améliorations dans certaines utilisations ? ...


 

BloodyCarnage a écrit :

Je dirais surtout : compatibilité avec les xorg/kernel récents.


 
Okay, donc je reste sur les 180 pour le moment vu que ça marche nickel

n°1150416
BloodyCarn​age
Posté le 23-07-2009 à 19:28:18  profilanswer
 

Les 190.16 auront pas fait long feu, voilà déjà les 190.18...
 

Changes since 190.16:
 
    * Fixed an initialization problem on some mobile GPUs.
    * Worked around X.Org X server Bugzilla bug #22804. This bug allows X clients to send invalid XGetImage requests to the hardware, leading to screen corruption or hangs. This was most commonly triggered by running JDownloader in KDE 4.
    * Fixed a crash in nvidia-settings displaying GPU information when in Xinerama.


 

n°1150423
thana54
made in concept
Posté le 23-07-2009 à 19:34:59  profilanswer
 

updated
 

Citation :


Changes since 190.16:
 
    * Fixed an initialization problem on some mobile GPUs.
    * Worked around X.Org X server Bugzilla bug #22804. This bug allows X clients to send invalid XGetImage requests to the hardware, leading to screen corruption or hangs. This was most commonly triggered by running JDownloader in KDE 4.
    * Fixed a crash in nvidia-settings displaying GPU information when in Xinerama.
 
Changes since 185.18.*:
 
    * Added GLX protocol support (i.e., for GLX indirect rendering) for the following OpenGL extensions:
          o GL_ARB_draw_buffers
          o GL_EXT_Cg_shader
          o GL_EXT_gpu_program_parameters
          o GL_NV_fragment_program
          o GL_NV_gpu_program4
          o GL_NV_register_combiners
          o GL_NV_vertex_program1_1
          o GL_NV_vertex_program2
    * Added unofficial GLX protocol support (i.e., for GLX indirect rendering) for the following OpenGL extensions:
          o GL_ARB_geometry_shader4
          o GL_ARB_shader_objects
          o GL_ARB_texture_buffer_object
          o GL_ARB_vertex_buffer_object
          o GL_ARB_vertex_shader
          o GL_EXT_bindable_uniform
          o GL_EXT_compiled_vertex_array
          o GL_EXT_geometry_shader4
          o GL_EXT_gpu_shader4
          o GL_EXT_texture_buffer_object
          o GL_NV_geometry_program4
          o GL_NV_vertex_program
          o GL_NV_parameter_buffer_object
          o GL_NV_vertex_program4
      GLX protocol for GL_EXT_vertex_array was also updated to incorporate rendering using GL_ARB_vertex_buffer_object. Use of these extensions with GLX indirect rendering requires the AllowUnofficialGLXProtocol X configuration option and the __GL_ALLOW_UNOFFICIAL_PROTOCOL environment variable.
    * Fixed a bug that caused glXGetVideoSyncSGI, glXWaitVideoSyncSGI, and glXGetRefreshRateSGI to operate on the wrong screen when there are multiple X screens.
    * Fixed glXQueryVersion to report GLX version 1.4. NVIDIA's GLX version has been 1.4 for several releases, and was already reported as 1.4 in the GLX client and GLX server version strings.
    * Fixed a problem that caused window border corruption when the screen is rotated.
    * Fixed a bug that causes corruption or GPU errors when an application paints a redirected window whose background is set to ParentRelative on X.Org servers older than 1.5. This was typically triggered by running Kopete while using Compiz or Beryl.
    * Added support for configuring the GPU PowerMizer Mode on GeForce 8 or later GPUs with multiple performance levels via nvidia-settings and NV-CONTROL.
    * Fixed a bug in VDPAU that could cause visible corruption when decoding H.264 clips with alternating frame/field coded reference pictures, and a video surface is concurrently removed from the DPB, and re-used as the decode target, in a single decode operation. This affected all GPUs supported by VDPAU.
    * Fixed a bug in VDPAU that could cause visible corruption near the bottom edge of the picture when decoding VC-1 advanced profile clips whose heights are not exact multiples of 16 pixels, on G98 and MCP7x (IGP) GPUs.
    * Enhanced VDPAU to better handle corrupt/invalid H.264 bitstreams on G84, G86, G92, G94, G96, or GT200 GPUs. This should prevent most cases of "display preemption" that are caused by bitstream errors.
    * Fixed an X server crash when using the VDPAU overlay-based presentation queue and VT-switching away from the X server.
    * Enhanced VDPAU's detection of the GPU's video decode capabilities.
    * Fixed a bug in VDPAU that could cause ghosting/flashing issues when decoding H.264 clips, in certain full DPB scenarios, on G98 and MCP7x.
    * Fixed VDPAU to detect an attempt to destroy the VdpDevice object when other device-owned objects still exist. VDPAU now triggers "display preemption", and returns an error, when this occurs.
    * Enhanced VDPAU's error handling and resource management in presentation queue creation and operation. This change correctly propagates all errors back to the client application, and avoids some resource leaks.

n°1151386
thana54
made in concept
Posté le 28-07-2009 à 18:59:26  profilanswer
 

Mise à jour de la version stable

Citation :


Release Highlights
 
    * Added code to forcibly terminate long-running CUDA kernels when Ctrl-C is pressed.
    * Fixed a bug that could cause occasional memory corruption problems or segmentation faults when running OpenGL applications on Quadro GPUs.
    * Fixed a deadlock in the OpenGL library that could be triggered in certain rare circumstances on Quadro GPUs.
    * Fixed an interaction problem between PowerMizer and CUDA applications that caused the performance level to be reduced while the CUDA kernel is running.
    * Made CUDA compute-exclusive mode persistent across GPU resets.
    * Fixed the order of outputs in the GPUScaling nvidia-settings property.
    * Fixed a bug that caused graphics corruption in some OpenGL applications when the Unified Back Buffer is enabled the application window is moved.
    * Fixed a bug that caused glXGetVideoSyncSGI, glXWaitVideoSyncSGI, and glXGetRefreshRateSGI to operate on the wrong screen when there are multiple X screens.
    * Fixed a bug that causes corruption or GPU errors when an application paints a redirected window whose background is set to ParentRelative on X.Org servers older than 1.5. This was typically triggered by running Kopete while using Compiz or Beryl.
    * Fixed a bug in VDPAU that could cause visible corruption when decoding H.264 clips with alternating frame/field coded reference pictures, and a video surface is concurrently removed from the DPB, and re-used as the decode target, in a single decode operation. This affected all GPUs supported by VDPAU.
    * Fixed a bug in VDPAU that could cause visible corruption near the bottom edge of the picture when decoding VC-1 advanced profile clips whose heights are not exact multiples of 16 pixels, on G98 and MCP7x (IGP) GPUs.
    * Enhanced VDPAU to better handle corrupt/invalid H.264 bitstreams on G84, G86, G92, G94, G96, or GT200 GPUs. This should prevent most cases of "display preemption" that are caused by bitstream errors.
    * Fixed an X server crash when using the VDPAU overlay-based presentation queue and VT-switching away from the X server.
    * Enhanced VDPAU's detection of the GPU's video decode capabilities.
    * Fixed a bug in VDPAU that could cause ghosting/flashing issues when decoding H.264 clips, in certain full DPB scenarios, on G98 and MCP7x.
    * Fixed VDPAU to detect an attempt to destroy the VdpDevice object when other device-owned objects still exist. VDPAU now triggers "display preemption", and returns an error, when this occurs.
    * Enhanced VDPAU's error handling and resource management in presentation queue creation and operation. This change correctly propagates all errors back to the client application, and avoids some resource leaks.
 
 
The 185.18.29 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP.
The 185.18.29 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86-64 is available for download via FTP.
 
Please see the README (x86, x86-64) for more information about this release.
 
Please note: This NVIDIA Linux graphics driver release supports GeForce 6xxx and newer NVIDIA GPUs, GeForce4 and older GPUs are supported through the 96.43.xx and 71.86.xx NVIDIA legacy graphics drivers. GeForce FX GPUs are supported through the 173.14.xx NVIDIA legacy graphics drivers.

n°1152219
thana54
made in concept
Posté le 01-08-2009 à 10:32:14  profilanswer
 

185.18.31 stable
 

Citation :


Release highlights since 185.18.29:
 
    * Fixed a crash on certain mobile GPUs.
 
Release highlights since 185.18.14:
 
    * Added code to forcibly terminate long-running CUDA kernels when Ctrl-C is pressed.
    * Fixed a bug that could cause occasional memory corruption problems or segmentation faults when running OpenGL applications on Quadro GPUs.
    * Fixed a deadlock in the OpenGL library that could be triggered in certain rare circumstances on Quadro GPUs.
    * Fixed an interaction problem between PowerMizer and CUDA applications that caused the performance level to be reduced while the CUDA kernel is running.
    * Made CUDA compute-exclusive mode persistent across GPU resets.
    * Fixed the order of outputs in the GPUScaling nvidia-settings property.
    * Fixed a bug that caused graphics corruption in some OpenGL applications when the Unified Back Buffer is enabled the application window is moved.
    * Fixed a bug that caused glXGetVideoSyncSGI, glXWaitVideoSyncSGI, and glXGetRefreshRateSGI to operate on the wrong screen when there are multiple X screens.
    * Fixed a bug that causes corruption or GPU errors when an application paints a redirected window whose background is set to ParentRelative on X.Org servers older than 1.5. This was typically triggered by running Kopete while using Compiz or Beryl.
    * Fixed a bug in VDPAU that could cause visible corruption when decoding H.264 clips with alternating frame/field coded reference pictures, and a video surface is concurrently removed from the DPB, and re-used as the decode target, in a single decode operation. This affected all GPUs supported by VDPAU.
    * Fixed a bug in VDPAU that could cause visible corruption near the bottom edge of the picture when decoding VC-1 advanced profile clips whose heights are not exact multiples of 16 pixels, on G98 and MCP7x (IGP) GPUs.
    * Enhanced VDPAU to better handle corrupt/invalid H.264 bitstreams on G84, G86, G92, G94, G96, or GT200 GPUs. This should prevent most cases of "display preemption" that are caused by bitstream errors.
    * Fixed an X server crash when using the VDPAU overlay-based presentation queue and VT-switching away from the X server.
    * Enhanced VDPAU's detection of the GPU's video decode capabilities.
    * Fixed a bug in VDPAU that could cause ghosting/flashing issues when decoding H.264 clips, in certain full DPB scenarios, on G98 and MCP7x.
    * Fixed VDPAU to detect an attempt to destroy the VdpDevice object when other device-owned objects still exist. VDPAU now triggers "display preemption", and returns an error, when this occurs.
    * Enhanced VDPAU's error handling and resource management in presentation queue creation and operation. This change correctly propagates all errors back to the client application, and avoids some resource leaks.
 
 
The 185.18.31 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP.
The 185.18.31 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86-64 is available for download via FTP.
 
Please see the README (x86, x86-64) for more information about this release.
 
Please note: This NVIDIA Linux graphics driver release supports GeForce 6xxx and newer NVIDIA GPUs, GeForce4 and older GPUs are supported through the 96.43.xx and 71.86.xx NVIDIA legacy graphics drivers. GeForce FX GPUs are supported through the 173.14.xx NVIDIA legacy graphics drivers.

n°1152526
thana54
made in concept
Posté le 03-08-2009 à 21:55:00  profilanswer
 

190.18.03 avec support de l'OpenGL 3.2
 

Citation :

Release highlights:
 
    * Support for OpenGL 3.2 on certain GPUs. Please see the driver download page for a list of GPUs that support OpenGL 3.2.
 
The 190.18.03 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 and Linux/x86_64 is available for download via HTTP.
 
Please note: This NVIDIA Linux graphics driver release supports GeForce 6xxx and newer NVIDIA GPUs, GeForce4 and older GPUs are supported through the 96.43.xx and 71.86.xx NVIDIA legacy graphics drivers. GeForce FX GPUs are supported through the 173.14.xx NVIDIA legacy graphics drivers.

n°1152529
StK-
Posté le 03-08-2009 à 22:56:39  profilanswer
 

Salut,
 
Dites, depuis que j'ai mis à jour de la 180.x à la 185.x, à chaque reboot j'ai une erreur m'expliquant qu'il y a un conflit sur les composants du module, qu'il y a un bout en 180.x et l'autre en 185.x.  
 
Je résoud le problème avec un petit modprobe -r nvidia nvidiafb, en relanceant le .run, il "compile" le module et hop c'est reparti mais bon c'est strange...
 
J'ai essayé a la fois avec le .run de la 180.x et celui de la 185.x de lancer le --uninstall mais ça n'a pas résolu le problème.
 
Est-ce que vous sauriez quel composant s'est planqué, ou le trouver, ou auriez vous une piste svp ?
 
Merci d'avance,
Kévin
 
Edit : Topic très bien fait  :jap: , qui m'a apprit que je pouvais m'accrocher avec ma 7900GS pour le VDPAU :( ... va falloir se pencher sur ffmpeg-mt (multi-threads) pour esperer lire du 1080p de façon fluide !


Message édité par StK- le 03-08-2009 à 23:00:09
n°1152531
e_esprit
Posté le 03-08-2009 à 23:01:36  profilanswer
 

Ca serait pas dans ton initrd ?


---------------
Ce n'est point ma façon de penser qui a fait mon malheur, c'est celle des autres.
n°1152533
StK-
Posté le 03-08-2009 à 23:15:35  profilanswer
 

e_esprit a écrit :

Ca serait pas dans ton initrd ?


 
Bingo ! J'ai manifestement quelques lacunes sur le fonctionnement du initrd :o
 
Merci beaucoup  :jap:

n°1155601
thana54
made in concept
Posté le 16-08-2009 à 18:03:54  profilanswer
 

Ca peut intéresser du monde: http://www.nvnews.net/vbulletin/sh [...] p?t=137469
 

Citation :

Install of Drivers on Debian AMD64 testing/sid
More a HU/howto for anyone that wants to install drivers onto current versions of Debian testing/sid. The locations of the 32 bit libs have changed recently and the /emul tree is dead. All 32 bit packages should be going to /lib32 and /usr/lib32.
 
The driver install scripts currently don't take this into account (and since it's only testing/unstable I'm not sure if they will in the near future). To ensure that the driver files go to the correct locations:
 
Code:

downloaded script file> --compat32-prefix=/usr --compat32-libdir=lib32 --compat32-chroot=


 
The compat32-prefix should be the same as the default setting, however compat32-libdir defaults to lib and compat32-chroot defaults to /emul/ia32-linux, so needs to be unset.
 
At least the above works with my setup (so far ).
 
Of course if you don't install the 32 bit compatibility libraries there's no issue in any case.

n°1157085
BloodyCarn​age
Posté le 22-08-2009 à 12:59:50  profilanswer
 

Citation :

190.25 (beta) Linux x86/x86-64 released
 
Release highlights:
 
    * Added code to reject screen modes based on available DisplayPort link bandwidth. Fixes display corruption caused by allowing high bandwidth modes on display devices that can't handle them, such as certain DisplayPort-to-VGA adapters that only support 2 DisplayPort lanes.
    * Fixed an initialization problem on some mobile GPUs.
    * Worked around X.Org X server Bugzilla bug #22804. This bug allows X clients to send invalid XGetImage requests to the hardware, leading to screen corruption or hangs. This was most commonly triggered by running JDownloader in KDE 4.
    * Fixed a crash in nvidia-settings displaying GPU information when in Xinerama.

n°1157101
thana54
made in concept
Posté le 22-08-2009 à 14:17:51  profilanswer
 

Changelog de la version stable

Citation :


Release highlights:
 
    * Fixed a bug that caused kernel panics when starting X on some mobile GPUs.
    * Fixed an interaction problem between VDPAU and PowerMizer when using VDPAU solely as a display mechanism, and not to decode video streams. The GPU performance level should now be raised, if required, in this scenario.
    * Fixed VDPAU to avoid "display preemption" in some cases where a VdpOutputSurface is deleted while it is still active (either queued or visible) in a VdpPresentationQueue. In particular, this can occur in MPlayer when using the "-fs" option, and could completely prevent VDPAU from operating successfully, depending on the exact timing conditions.
 
 
 
The 185.18.36 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP.
The 185.18.36 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86-64 is available for download via FTP.
 
Please see the README (x86, x86-64) for more information about this release.
 
Please note: This NVIDIA Linux graphics driver release supports GeForce 6xxx and newer NVIDIA GPUs, GeForce4 and older GPUs are supported through the 96.43.xx and 71.86.xx NVIDIA legacy graphics drivers. GeForce FX GPUs are supported through the 173.14.xx NVIDIA legacy graphics drivers.

n°1158693
jean pierr​e
Posté le 27-08-2009 à 23:10:04  profilanswer
 


 
Bonsoir,
 
pour la version, voir en fonction de ta config et du post au dessus du tiens ou du lien ci dessous
 
http://forum.hardware.fr/forum2.ph [...] w=0&nojs=0

n°1160408
thana54
made in concept
Posté le 02-09-2009 à 14:35:11  profilanswer
 

XBMC doit intégrer par défaut les drivers >180.29 nécessaires pour décoder de la HD. Donc normalement, tu n'as rien à faire pour lire directement ce genre de flux.

 

Ensuite, tu peux installer à la main ou faire les mises à jour, c'est une ubuntu qui tourne derrière (ctrl + alt + F1 pour accéder à tty1).

Message cité 1 fois
Message édité par thana54 le 02-09-2009 à 14:35:56
mood
Publicité
Posté le   profilanswer
 

 Page :   1  2  3  4  5  ..  36  37  38  ..  48  49  50  51  52  53

Aller à :
Ajouter une réponse
 

Sujets relatifs
Problème config XF86Config-4 avec Nvidia Ti4600 dualview + MDK 10Fedora et install driver nvidia
[Debian SID] Compilation driver nvidia sur un 2.6.7probleme interference alsa et nvidia?
Driver Nvidia --> Fréquence trop élevée en console ! [Résolu][DEBIAN] driver nvidia
Probleme à l'install des drivers nvidia // Resoludrivers ATI... encore et toujours...
[Xorg et drivers Nvidia] 
Plus de sujets relatifs à : [ Nvidia ] Le topic des drivers (304.60)


Copyright © 1997-2025 Groupe LDLC (Signaler un contenu illicite / Données personnelles)