CONNEXION
  • RetourJeux
    • Sorties
    • Hit Parade
    • Les + populaires
    • Les + attendus
    • Soluces
    • Tous les Jeux
    • Gaming
  • RetourActu Gaming
    • News
    • Astuces
    • Tests
    • Previews
    • Toute l'actu gaming
  • RetourBons plans
    • Bons plans
    • Bons plans Smartphone
    • Bons plans Hardware
    • Bons plans Image et Son
    • Bons plans Amazon
    • Bons plans Cdiscount
    • Bons plans Decathlon
    • Bons plans Fnac
    • Tous les Bons plans
  • RetourJVTech
    • Actus High-Tech
    • Intelligence Artificielle
    • Smartphones
    • Mobilité urbaine
    • Hardware
    • Image et son
    • Tutoriels
    • Tests produits High-Tech
    • Guides d'achat High-Tech
    • JVTech
  • RetourCulture
    • Actus Culture
    • Culture
  • RetourVidéos
    • A la une
    • Gaming Live
    • Vidéos Tests
    • Vidéos Previews
    • Gameplay
    • Trailers
    • Chroniques
    • Replay Web TV
    • Toutes les vidéos
  • RetourForums
    • Hardware PC
    • PS5
    • Switch 2
    • Xbox Series
    • Switch
    • Pokemon pocket
    • FC 25 Ultimate Team
    • League of Legends
    • Tous les Forums
  • PC
  • PS5
  • Xbox Series
  • Switch 2
  • PS4
  • One
  • Switch
  • iOS
  • Android
  • MMO
  • RPG
  • FPS
En ce moment Genshin Impact Valhalla Breath of the wild Animal Crossing GTA 5 Red dead 2
Liste des sujets

drivers nvidia gentoo amd64 libglx

Oppidum
Oppidum
Niveau 8
19 mai 2005 à 19:28:34

bonjour,

j´ai une gentoo amd64, j´ai essayé linstalation des dernier driver nvidia, seulement a l´instalation des lib32 bit, il me di que pas mal de fichier existe deja...

lorsque je lance startx apré linstalation, kde match, mais 2 a 3 minute dutilisation lecran freeze seul la souris peu bouger mais rien ne repond

lorsque je redemar, il me di que libglx.so na pas etai trouvé

fatal error: screens no found

jai essayer emerge nvidia-glx...sans sucéé
jai bien sur modifier xorg.conf avec load glx, drievr nvidia...

une aide ?

Oppidum
Oppidum
Niveau 8
19 mai 2005 à 19:32:07

jai desactiver vesa... ds le kernel mais tjs la meme chose

jai trouvé sur un forum ceci, si sa peu vous aider a m´aider...
-------------------
a création du lien :

Code:
ln -s / usr/X11R6/lib/modules/extensions/libglx.so / usr/X11R6/lib/modules/extensions/libglx.a

résoudrait le pb apparement.

-------------------------------
mais le pb je sais pas ladapter a ma config 64bit, jai essayer kelk truc mais sans succé

Oppidum
Oppidum
Niveau 8
19 mai 2005 à 19:51:40

bon je sais pas si sa marche mais en gtout k, jai desinsataler pui reinstaler opengl... apré linstal des driver, jai du metre aussi use= nvidia sansdoute, et la sa bug pu...enfin fo attendre

jai modifier aussi video 65556 . ..

je sais pas qui a fai koi mais sa a lair de marcher

maintenan jaimerai savoir pq jai un afichage pouri, plus gros ? alors ke ma reolution est la meme que san sdriver 1400*1050 ? ? en 24bit

Oppidum
Oppidum
Niveau 8
19 mai 2005 à 21:44:25

bon non en fait sa merd tjs autan !

pq quand je lance startx apré linstall des driver nvidia, kde marche pendan quelque minute... et quand je redemar x ne veu pu se lancer ! !! alors que les module nvidia son bien charger...

bon en gros mes symptome: sous kde apré linstal des nvidia module: freeze ecran, souris qui marche, apré quelque minute dutilisation

apré redemarage:
startx:
ee) nvidia(0) failed load the nvidia kernel module
( ee) nvidia ( 0) *****abording****
( ee) screen(s) found, but none have usable configuration

fatal error
no screens found

quelqu un peu me copier coller son xorg.conf
pour que je puisse le comparer au mien ( je suis sur gentoo amd64 + xorg 6.8+ nvidia derneior driver pour amd64+ kde3.4
merci

Oppidum
Oppidum
Niveau 8
19 mai 2005 à 23:42:28

perssonne peu maider ?

Briaeros007
Briaeros007
Niveau 10
20 mai 2005 à 09:08:07

Section " Extensions"
Option " Composite" " off"
Option " XEVIE" " off"
EndSection
Section " Module"

  1. This loads the DBE extension module.

Load " dbe" # Double buffer extension

  1. This loads the miscellaneous extensions module, and disables
  2. initialisation of the XFree86-DGA extension within that module.

SubSection " extmod"
Option " omit xfree86-dga" # don´t initialise the DGA extension
EndSubSection

  1. This loads the Type1 and FreeType font modules

Load " type1"
Load " freetype"

  1. This loads the GLX module

Load " glx"

  1. This loads the DRI module
  2. Load " dri"

EndSection

Section " Files"

  1. The location of the RGB database. Note, this is the name of the
  2. file minus the extension ( like " .txt" or " .db"). There is normally
  3. no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

  1. Multiple FontPath entries are allowed ( which are concatenated together),
  2. as well as specifying multiple comma-separated entries in one FontPath
  3. command ( or a combination of both methods)

#

#

FontPath " /usr/X11R6/lib/X11/fonts/100dpi/"
FontPath " /usr/X11R6/lib/X11/fonts/75dpi/"
FontPath " /usr/X11R6/lib/X11/fonts/TTF/"
FontPath " /usr/X11R6/lib/X11/fonts/Type1/"
FontPath " /usr/X11R6/lib/X11/fonts/util/"
FontPath " /usr/X11R6/lib/X11/fonts/CID/"
FontPath " /usr/X11R6/lib/X11/fonts/local/"
FontPath " /usr/X11R6/lib/X11/fonts/misc/"

  1. The module search path. The default path is shown here.

ModulePath " /usr/X11R6/lib/modules"

EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************

Section " ServerFlags"

  1. sets the inactivity timeout for the blanking phase

Option " BlankTime" " 5"

  1. sets the inactivity timeout for the standby phase

Option " StandbyTime" " 5"

  1. sets the inactivity timeout for the suspending phase

Option " SuspendTime" " 10"

  1. sets the inactivity timeout for the off phase

Option " OffTime" " 15"

  1. enable Xinerama

Option " Xinerama" " on"

EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************

Section " InputDevice"

Identifier "Keyboard1"
Driver "kbd"

  1. For most OSs the protocol can be omitted ( it defaults to " Standard").
  2. When using XQUEUE ( only for SVR3 and SVR4, but not Solaris),
  3. uncomment the following line.
  1. Option " Protocol" " Xqueue"

Option " AutoRepeat" " 500 30"

  1. Specify which keyboard LEDs can be user-controlled ( eg, with xset(1))
  2. Option "Xleds" " 1 2 3"

Option " LeftAlt" " Meta"
Option " RightAlt" " ModeShift"

  1. To customise the XKB settings to suit your keyboard, modify the
  2. lines below ( which are the defaults). For example, for a non-U.S.
  3. keyboard, you will probably want to use:
  4. Option " XkbModel" " pc102"
  5. If you have a US Microsoft Natural keyboard, you can use:
  6. Option " XkbModel" " microsoft"

#

  1. Then to change the language, change the Layout setting.
  2. For example, a german layout can be obtained with:
  3. Option " XkbLayout" " de"
  4. or:
  5. Option " XkbLayout" " de"
  6. Option " XkbVariant" " nodeadkeys"

#

  1. If you´d like to switch the positions of your capslock and
  2. control keys, use:
  3. Option " XkbOptions" " ctrl:swapcaps"
  1. These are the default XKB settings for Xorg
  1. Option " XkbModel" " pc101"
  2. Option " XkbLayout" " us"
  3. Option " XkbVariant" " "
  4. Option " XkbOptions" " "
  1. Option " XkbDisable"

Option " XkbModel" "pc105"
Option " XkbLayout" "fr"

EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************

Section " InputDevice"

  1. Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option " Protocol" " IMPS/2"
Option " Device" " /dev/psaux"
Option " ZAxisMapping" " 4 5"

  1. Mouse-speed setting for PS/2 mouse.
  1. Option " Resolution" "256"
  1. When using XQUEUE, comment out the above two lines, and uncomment
  2. the following line.
  1. Option " Protocol" "Xqueue"
  1. Baudrate and SampleRate are only for some Logitech mice. In
  2. almost every case these lines should be omitted.
  1. Option " BaudRate" "9600"
  2. Option " SampleRate" "150"
  1. Emulate3Buttons is an option for 2-button Microsoft mice
  2. Emulate3Timeout is the timeout in milliseconds ( default is 50ms)
  1. Option " Emulate3Buttons"
  2. Option " Emulate3Timeout" " 50"
  1. ChordMiddle is an option for some 3-button Logitech mice
  1. Option " ChordMiddle"

EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************

#

  1. Section " InputDevice"
  2. Identifier " Mouse2"
  3. Driver " mouse"
  4. Option " Protocol" " MouseMan"
  5. Option " Device" " /dev/mouse2"
  6. EndSection

#

  1. Section " InputDevice"
  2. Identifier " spaceball"
  3. Driver " magellan"
  4. Option " Device" " /dev/cua0"
  5. EndSection

#

  1. Section " InputDevice"
  2. Identifier " spaceball2"
  3. Driver " spaceorb"
  4. Option " Device" " /dev/cua0"
  5. EndSection

#

  1. Section " InputDevice"
  2. Identifier " touchscreen0"
  3. Driver " microtouch"
  4. Option " Device" " /dev/ttyS0"
  5. Option " MinX" " 1412"
  6. Option " MaxX" " 15184"
  7. Option " MinY" " 15372"
  8. Option " MaxY" " 1230"
  9. Option " ScreenNumber" " 0"
  10. Option " ReportingMode" " Scaled"
  11. Option " ButtonNumber" " 1"
  12. Option " SendCoreEvents"
  13. EndSection

#

  1. Section " InputDevice"
  2. Identifier " touchscreen1"
  3. Driver " elo2300"
  4. Option " Device" " /dev/ttyS0"
  5. Option " MinX" " 231"
  6. Option " MaxX" " 3868"
  7. Option " MinY" " 3858"
  8. Option " MaxY" " 272"
  9. Option " ScreenNumber" " 0"
  10. Option " ReportingMode" " Scaled"
  11. Option " ButtonThreshold" " 17"
  12. Option " ButtonNumber" " 1"
  13. Option " SendCoreEvents"
  14. EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************
  1. Any number of monitor sections may be present

Section " Monitor"

Identifier " Screen 2"

  1. HorizSync is in kHz unless units are specified.
  2. HorizSync may be a comma separated list of discrete values, or a
  3. comma separated list of ranges of values.
  4. NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR´S
  5. USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 30-70

  1. HorizSync 30-64 # multisync
  2. HorizSync 31.5, 35.2 # multiple fixed sync frequencies
  3. HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
  1. VertRefresh is in Hz unless units are specified.
  2. VertRefresh may be a comma separated list of discrete values, or a
  3. comma separated list of ranges of values.
  4. NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR´S
  5. USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-160
Option " DPMS"
EndSection

Section " Monitor"

Identifier " Screen 1"
HorizSync 30-72
VertRefresh 50-150
Option " DPMS"
EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************
  1. Any number of graphics device sections may be present
  1. Standard VGA Device:
  1. Section " Device"
  2. Identifier "Standard VGA"
  3. VendorName "Unknown"
  4. BoardName "Unknown"
  1. The chipset line is optional in most cases. It can be used to override
  2. the driver´s chipset detection, and should not normally be specified.
  1. Chipset "generic"
  1. The Driver line must be present. When using run-time loadable driver
  2. modules, this line instructs the server to load the specified driver
  3. module. Even when not using loadable driver modules, this line
  4. indicates which driver should interpret the information in this section.
  1. Driver " vga"
  2. The BusID line is used to specify which of possibly multiple devices
  3. this section is intended for. When this line isn´t present, a device
  4. section can only match up with the primary video device. For PCI
  5. devices a line like the following could be used. This line should not
  6. normally be included unless there is more than one video device
  7. intalled.
  1. BusID " PCI:0:10:0"
  1. VideoRam 256
  1. Clocks 25.2 28.3
  1. EndSection
  1. Device configured by xorgconfig:
  1. Section " Device"
  2. Identifier " rage128"
  3. Driver " ati"
  4. VideoRam 16384
  5. Option " RenderAccel" " True" # si nvidia

# Option " AllowGLXWithComposite" " true"

  1. BusID " PCI:1:0:0"

# Insert Clocks lines here if appropriate

  1. EndSection

Section " Device"
Identifier " gf2mx200"
Driver " nvidia"
VideoRam 32768

Option " NvAGP" " 3"
Option " NoLogo" " true"
Option " RenderAccel" " True" # ALPHA
Option " DigitalVibrance" " 10"
Option " CursorShadow" " true"
Option " CursorShadowAlpha" " 125"
Option " UseEdidFreqs" " true"
Option " XvmcUsesTextures" " false"

  1. Option " TwinView" " false"
  2. Option " TwinViewOrientation" " " #Above, Below , Clone , RightOf, LeftOf
  3. Option " SecondMonitorHorizSync" " range(s)"
  4. Option " SecondMonitorVertRefresh" " range(s)"
  5. Option " MetaModes" " string"
  6. Option " NoTwinViewXineramaInfo" " boolean"
  7. Option " TVStandard" " string"
  8. Option " TVOutFormat" " string"
  9. Option " TVOverScan" " Decimal value in the range 0.0 to 1.0"

# Option " AllowGLXWithComposite" " true"
BusID " PCI:1:0:0"
# Insert Clocks lines here if appropriate
EndSection

Section " Device"
Identifier " gf2mx400"
Driver " nvidia"
VideoRam 65536
Option " NoLogo" " true"
Option " RenderAccel" " True" # ALPHA
Option " DigitalVibrance" " 10"
Option " CursorShadow" " true"
Option " CursorShadowAlpha" " 125"
Option " UseEdidFreqs" " true"
Option " XvmcUsesTextures" " false"

  1. Option " AllowGLXWithComposite" " true"

BusID " PCI:0:10:0"
# Insert Clocks lines here if appropriate
EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************
  1. Any number of screen sections may be present. Each describes
  2. the configuration of a single screen. A single specific screen section
  3. may be specified from the X server command line with the " -screen"
  4. option.

Section " Screen"
Identifier " Screen 1"
Device " gf2mx400"
Monitor " Screen 1"
DefaultDepth 16

Subsection " Display"
Depth 8
Modes " 1280x1024" " 1024x768" " 800x600" " 640x480"
ViewPort 0 0
Virtual 1600 1280
EndSubsection
Subsection " Display"
Depth 16
Modes " 1024x768" " 800x600" " 640x480"
ViewPort 0 0
Virtual 1024 768
EndSubsection
Subsection " Display"
Depth 24
Modes " 1024x768" " 800x600" " 640x480"
ViewPort 0 0
Virtual 1024 768
EndSubsection
EndSection
Section " Screen"
Identifier " Screen 2"
Device " gf2mx200"
Monitor " Screen 2"
DefaultDepth 16

Subsection " Display"
Depth 8
Modes " 1280x1024" " 1024x768" " 800x600" " 640x480"
ViewPort 0 0
Virtual 1600 1280
EndSubsection
Subsection " Display"
Depth 16
Modes " 1024x768" " 800x600" " 640x480"
ViewPort 0 0
Virtual 1024 768
EndSubsection
Subsection " Display"
Depth 24
Modes " 1024x768" " 800x600" " 640x480"
ViewPort 0 0
Virtual 1024 768
EndSubsection
EndSection

#

    • ***********************************************
    • *****************

#

    • ***********************************************
    • *****************
  1. Any number of ServerLayout sections may be present. Each describes
  2. the way multiple screens are organised. A specific ServerLayout
  3. section may be specified from the X server command line with the
  4. " -layout" option. In the absence of this, the first section is used.
  5. When now ServerLayout section is present, the first Screen section
  6. is used alone.

Section " ServerLayout"

  1. The Identifier line must be present

Identifier " Simple Layout"

  1. Each Screen line specifies a Screen section name, and optionally
  2. the relative position of other screens. The four names after
  3. primary screen name are the screens to the top, bottom, left and right
  4. of the primary screen. In this example, screen 2 is located to the
  5. right of screen 1.

Screen " Screen 1"
Screen " Screen 2" LeftOf " Screen 1"

  1. Each InputDevice line specifies an InputDevice section name and
  2. optionally some options to specify the way the device is to be
  3. used. Those options include " CorePointer", " CoreKeyboard" and
  4. " SendCoreEvents".

InputDevice " Mouse1" " CorePointer"
InputDevice " Keyboard1" " CoreKeyboard"

EndSection

  1. Section " DRI"
  2. Mode 0666
  3. EndSection
Oppidum
Oppidum
Niveau 8
20 mai 2005 à 13:00:20

briaeros007 jte remerci

Sous forums
  • Aide à l'achat Mac
  • Macintosh
  • Création de sites web
  • Création de Jeux
  • Linux
  • Programmation
  • Internet
  • Steam Deck
  • Hardware