Script para instalar drivers de nvidia y beryl
-
Has probado con las guias que hay en el wiki ?
-
Creo que si, aunque no recuerdo si fue esta última vez o la otra que lo intenté con Dapper. De todos modos lo añado a mis marcadores y probaré de nuevo, que no quiero quedarme sin mis efectos 3D.
-
También podeis pasaros por aquí para estar al tanto de las novedades de beryl.
http://goberylgo.blogspot.com/
Un Saludo!
-
yorus.. has probado esta guia ????
-
Que va, ando escasillo de tiempo ultimamente. A ver si el finde me animo.
-
Bueno, pues me ha dado por probar tu scrpt y decirte que me ha funcionado a la perfección. En el sources.list solo me ha duplicado la entrada de Beryl, por las pruebas que había hecho yo antes. Creo que mi problema estaba en utilizar los drivers de nvidia que vienen con Ubuntu.
Estoy contento, WoW en Linux y Beryl en solo una semana, jejeje.
-
Esto lo tengo que probar yo algun dia…
-
El problemilla que tengo es para arrancarlo al inicio de sesión. Lo intento desde Sistema > Preferencias > Sesiones y luego yendo a la pestaña Programas de inicio y dándole a añadir y poniendo beryl-manager pero no me guarda la configuración y al siguiente inicio de sesión no me salen los bordes de ventana ni las barras de título, ya que está seleccionado Emerald como gestor de temas pero no está arrancado Beryl.
-
Beryl es EXPECTACULAR…. pasas unos dias con KDE+Beryl (en mi caso) y cuando entras en windows, te deprimes xD
-
Hombre estoy deacuerdo de que Beryl es alucinante .. pero tambien hay un monton de programas para hacer moding a windows y dejarlo genial (ahora solo falta que saquen algo parecido al beryl para XP .. seguro q no tardan mucho ) …
-
Con Vista en el mercado no se yo si alguien se va a molestar en hacer algo similar a Beryl en XP.
-
Hombre estoy deacuerdo de que Beryl es alucinante .. pero tambien hay un monton de programas para hacer moding a windows y dejarlo genial (ahora solo falta que saquen algo parecido al beryl para XP .. seguro q no tardan mucho ) …
Cambiar el marco a las ventanas es lo de menos…. ver como "arde" (literal) una ventana al cerrarla no lo he visto nunca xD
-
arder la ventana .. madre mia … eso el mio no lo hace .. tengo q instalar las nuevas versiones ... ;D
-
Hola antes que nada felicitarte por el scrip que te has currado que nos ahorra muchos pasos
Bueno instale el scrip con Kubuntu edgy y tengo beryl, pero lo que no se si tengo es la targeta bien configurada. es una nvidia 6800gt y en el panel de control de KDE pone "Nvidia gforce generic" "controlador nv"
Las fotos y los videos se ven mal, como si me faltaran bits de color y no me deja poner el monitor a mas de 56Hz cuando en windows lo tengo a 70.
Tambien tengo que decir que los efectos de beryl me van bien, con el benchmark que lleva me da 1400 frames en reposo y 230 al rotar el cuboA ver si me podeis hechar una mano que hace mucho que no me ponia con linux y no me atrevo a tocar el xorg.conf
-
Gunfett posteanos tu xorg.conf para echarle un vistazo, y también sería interesante que nos postearas la salida de cat /proc/driver/nvidia/agp/status y cat /proc/driver/nvidia/cards/*
Las fotos y los videos se ven mal, como si me faltaran bits de color y no me deja poner el monitor a mas de 56Hz
Quizá te falte especificar en el kernel la profundidad
VESA driver type (vesafb-tng) --->(1024x768-32@60) VESA default modeUn Saludo!
-
@X24400:~$ cat /proc/driver/nvidia/cards/*
Model: GeForce 6800 GT
IRQ: 74
Video BIOS: 05.40.02.36.08
Card Type: PCI-E
DMA Size: 32 bits
DMA Mask: 0xffffffffcat /proc/driver/nvidia/agp/status
Nada supongo que porque la grafica es pcx, he provado con pcx pci-express y nadaY bueno la frq del monitor ya la tengo a 75 HZ que me he encontrado el mi monitor dentro del panel de control de KDE.
Aqui dejo el xor.conf/etc/X11/xorg.conf (xorg X Window System server configuration file)
This file was generated by dexconf, the Debian X Configuration tool, using
values from the debconf database.
Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
(Type "man /etc/X11/xorg.conf" at the shell prompt.)
This file is automatically updated on xserver-xorg package upgrades only
if it has not been modified since the last upgrade of the xserver-xorg
package.
If you have edited this file but would like it to be automatically updated
again, run the following command:
sudo dpkg-reconfigure -phigh xserver-xorg
Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
FontPath "/usr/share/fonts/X11/misc"path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSectionSection "Module"
Load "bitmap"
Load "ddc"
Load "extmod"
Load "freetype"
Load "int10"
Load "type1"
Load "vbe"
load "glx"
load "GLcore"
load "v4l"
EndSectionSection "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
option "CoreKeyboard"
option "XkbRules" "xorg"
option "XkbModel" "pc105"
option "XkbLayout" "es"
option "XkbOptions" "lv3:ralt_switch"
EndSectionSection "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
option "CorePointer"
option "Device" "/dev/input/mice"
option "Protocol" "ExplorerPS/2"
option "ZAxisMapping" "4 5"
option "Emulate3Buttons" "true"
EndSectionSection "InputDevice"
Driver "wacom"
Identifier "stylus"
option "Device" "/dev/wacom"# Change to
option "Type" "stylus"
option "ForceDevice" "ISDV4"# Tablet PC ONLY/dev/input/event
for USB
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "eraser"
option "Device" "/dev/wacom"# Change to
option "Type" "eraser"
option "ForceDevice" "ISDV4"# Tablet PC ONLY/dev/input/event
for USB
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
option "Device" "/dev/wacom"# Change to
option "Type" "cursor"
option "ForceDevice" "ISDV4"# Tablet PC ONLY/dev/input/event
for USB
EndSection
Section "Device"
identifier "Tarjeta de v�o gen�ca"
boardname "NVIDIA GeForce FX (generic)"
busid "PCI:1:0:0"
driver "nv"
screen 0
vendorname "NVIDIA"
EndSectionSection "Monitor"
identifier "Generic Monitor"
vendorname "Samsung"
modelname "Samsung SyncMaster 710Tplus/711T/712T (Digital)"
HorizSync 30-81
VertRefresh 56-75
modeline "640x480@60" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync
modeline "640x480@72" 31.5 640 664 704 832 480 489 491 520 -vsync -hsync
modeline "640x480@75" 31.5 640 656 720 840 480 481 484 500 -vsync -hsync
modeline "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
modeline "800x600@72" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
modeline "800x600@75" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
modeline "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
modeline "832x624@75" 57.284 832 864 928 1152 624 625 628 667 -vsync -hsync
modeline "1024x768@75" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
modeline "1024x768@70" 75.0 1024 1048 1184 1328 768 771 777 806 -vsync -hsync
modeline "1024x768@60" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync
modeline "1152x864@75" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
modeline "1280x1024@75" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
modeline "1280x960@60" 102.1 1280 1360 1496 1712 960 961 964 994 -hsync +vsync
modeline "1280x1024@60" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
modeline "1280x960@75" 129.86 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
modeline "1400x1050@60" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
modeline "1600x1200@65" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
modeline "1600x1200@60" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
gamma 1.0
EndSectionSection "Screen"
Identifier "Default Screen"
Device "Tarjeta de v�o gen�ca"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
depth 24
modes "1280x1024@60" "1280x960@75" "1280x960@60" "1400x1050@60" "1280x1024@75" "1600x1200@65" "1152x864@75" "1600x1200@60" "1024x768@60" "1024x768@70" "1024x768@75" "832x624@75" "800x600@60" "800x600@75" "800x600@72" "800x600@56" "640x480@75" "640x480@72" "640x480@60"
EndSubSection
EndSectionSection "ServerLayout"
Identifier "Default Layout"
screen 0 "Default Screen" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
EndSectionSection "DRI"
Mode 0666
EndSection
Section "device" #
identifier "device1"
boardname "NVIDIA GeForce FX (generic)"
busid "PCI:1:0:0"
driver "nvidia"
screen 1
vendorname "NVIDIA"
EndSection
Section "screen" #
identifier "screen1"
device "device1"
defaultdepth 24
monitor "monitor1"
EndSection
Section "monitor" #
identifier "monitor1"
gamma 1.0
EndSection
Section "ServerFlags"
EndSection -
Lo del cat /proc/driver/nvidia/agp/status es para comprobar si tienes activado el Fast Writes y la velocidad a la que corre el agp, en tu caso pcie. Miralo en /proc/driver/nvidia o sinó directamente en la configuración del propio módulo nvidia, /etc/modules.d/nvidia que tengas descomentada una linea similar a esta:```
options nvidia NVreg_EnableAGPSBA=1 NVreg_EnableAGPFW=1Comprueba también que tengas activado en el kernel la profundiad y la velocidad de refresco.VESA driver type (vesafb-tng) --->(1024x768-32@60) VESA default mode
Que versión de xorg estás usando? 6.x? es que lo veo algo raro :S Mi xorg.conf 7.1: **Edit** debido a que el foro no adminte mas de 15000 letras posteo mi xorg en el siguiente post y sin el encabezado porque sinó tampoco cabe. -
<pre>
Section "Module"This loads the DBE extension module.
Load "dbe" # Double buffer extensionThis loads the miscellaneous extensions module, and disables
initialisation of the XFree86-DGA extension within that module.
SubSection "extmod" Option "omit xfree86-dga" # don't initialise the DGA extension EndSubSectionThis loads the font modules
Load "type1"Load "speedo"
Load "freetype"Load "xtt"
This loads the GLX module
Load "glx"This loads the DRI module
Load "dri"
Load "v4l"EndSection
**********************************************************************
Files section. This allows default font and rgb paths to be set
**********************************************************************
Section "Files"
The location of the RGB database. Note, this is the name of the
file minus the extension (like ".txt" or ".db"). There is normally
no need to change the default.
Multiple FontPath entries are allowed (which are concatenated together),
as well as specifying multiple comma-separated entries in one FontPath
command (or a combination of both methods)
FontPath "/usr/share/fonts/misc" FontPath "/usr/share/fonts/75dpi" FontPath "/usr/share/fonts/100dpi" FontPath "/usr/share/fonts/TTF" FontPath "/usr/share/fonts/Type1" FontPath "/usr/lib/X11/fonts/local/" FontPath "/usr/lib/X11/fonts/misc/" FontPath "/usr/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/lib/X11/fonts/Speedo/" FontPath "/usr/lib/X11/fonts/Type1/" FontPath "/usr/lib/X11/fonts/TrueType/" FontPath "/usr/lib/X11/fonts/freefont/" FontPath "/usr/lib/X11/fonts/75dpi/" FontPath "/usr/lib/X11/fonts/100dpi/"The module search path. The default path is shown here.
EndSection
**********************************************************************
Server flags section.
**********************************************************************
Section "ServerFlags"
Uncomment this to cause a core dump at the spot where a signal is
received. This may leave the console in an unusable state, but may
provide a better stack trace in the core dump to aid in debugging
Option "NoTrapSignals"
Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
(where n is 1 through 12). This allows clients to receive these key
events.
Option "DontVTSwitch"
Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
This allows clients to receive this key event.
Option "DontZap"
Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
sequences. This allows clients to receive these key events.
Option "Dont Zoom"
Uncomment this to disable tuning with the xvidtune client. With
it the client can still run and fetch card and monitor attributes,
but it will not be allowed to change them. If it tries it will
receive a protocol error.
Option "DisableVidModeExtension"
Uncomment this to enable the use of a non-local xvidtune client.
Option "AllowNonLocalXvidtune"
Uncomment this to disable dynamically modifying the input device
(mouse and keyboard) settings.
Option "DisableModInDev"
Uncomment this to enable the use of a non-local client to
change the keyboard or mouse settings (currently only xset).
Option "AllowNonLocalModInDev"
EndSection
**********************************************************************
Input devices
**********************************************************************
**********************************************************************
Core keyboard's InputDevice section
**********************************************************************
Section "InputDevice"
Identifier "Keyboard1" Driver "kbd"For most OSs the protocol can be omitted (it defaults to "Standard").
When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
uncomment the following line.
Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "Xleds" "1 2 3"
Option "LeftAlt" "Meta"
Option "RightAlt" "ModeShift"
To customise the XKB settings to suit your keyboard, modify the
lines below (which are the defaults). For example, for a non-U.S.
keyboard, you will probably want to use:
Option "XkbModel" "pc105"
If you have a US Microsoft Natural keyboard, you can use:
Option "XkbModel" "microsoft"
Then to change the language, change the Layout setting.
For example, a german layout can be obtained with:
Option "XkbLayout" "de"
or:
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
If you'd like to switch the positions of your capslock and
control keys, use:
Option "XkbOptions" "ctrl:swapcaps"
These are the default XKB settings for Xorg
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "es"
Option "XkbVariant" ""
Option "XkbOptions" ""
Option "XkbDisable"
Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "es" Option "XkbVariant" "es"EndSection
**********************************************************************
Core Pointer's InputDevice section
**********************************************************************
Section "InputDevice"
Identifier and driver
Identifier "Mouse1" Driver "mouse" Option "Protocol" "IMPS/2" # IntelliMouse PS/2 Option "Device" "/dev/input/mice"When using XQUEUE, comment out the above two lines, and uncomment
the following line.
Option "Protocol" "Xqueue"
Mouse-speed setting for PS/2 mouse.
Option "Resolution" "256"
Baudrate and SampleRate are only for some Logitech mice. In
almost every case these lines should be omitted.
Option "BaudRate" "9600"
Option "SampleRate" "150"
Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
horizontal wheel to buttons 6 & 7. Change if your mouse has more than
3 buttons and you need to map the wheel to different button ids to avoid
conflicts.
Option "ZAxisMapping" "4 5 6 7"Emulate3Buttons is an option for 2-button mice
Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Option "Emulate3Buttons"Option "Emulate3Timeout" "50"
ChordMiddle is an option for some 3-button Logitech mice
Option "ChordMiddle"
EndSection
**********************************************************************
Other input device sections
this is optional and is required only if you
are using extended input devices. This is for example only. Refer
to the xorg.conf man page for a description of the options.
**********************************************************************
Section "InputDevice"
Identifier "Mouse2"
Driver "mouse"
Option "Protocol" "MouseMan"
Option "Device" "/dev/mouse2"
EndSection
Section "InputDevice"
Identifier "spaceball"
Driver "magellan"
Option "Device" "/dev/cua0"
EndSection
Section "InputDevice"
Identifier "spaceball2"
Driver "spaceorb"
Option "Device" "/dev/cua0"
EndSection
Section "InputDevice"
Identifier "touchscreen0"
Driver "microtouch"
Option "Device" "/dev/ttyS0"
Option "MinX" "1412"
Option "MaxX" "15184"
Option "MinY" "15372"
Option "MaxY" "1230"
Option "ScreenNumber" "0"
Option "ReportingMode" "Scaled"
Option "ButtonNumber" "1"
Option "SendCoreEvents"
EndSection
Section "InputDevice"
Identifier "touchscreen1"
Driver "elo2300"
Option "Device" "/dev/ttyS0"
Option "MinX" "231"
Option "MaxX" "3868"
Option "MinY" "3858"
Option "MaxY" "272"
Option "ScreenNumber" "0"
Option "ReportingMode" "Scaled"
Option "ButtonThreshold" "17"
Option "ButtonNumber" "1"
Option "SendCoreEvents"
EndSection
**********************************************************************
Monitor section
**********************************************************************
Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"HorizSync is in kHz unless units are specified.
HorizSync may be a comma separated list of discrete values, or a
comma separated list of ranges of values.
NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 30-83HorizSync 30-64 # multisync
HorizSync 31.5, 35.2 # multiple fixed sync frequencies
HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
VertRefresh is in Hz unless units are specified.
VertRefresh may be a comma separated list of discrete values, or a
comma separated list of ranges of values.
NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 70-80EndSection
**********************************************************************
Graphics device section
**********************************************************************
Any number of graphics device sections may be present
Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"The chipset line is optional in most cases. It can be used to override
the driver's chipset detection, and should not normally be specified.
Chipset "generic"
The Driver line must be present. When using run-time loadable driver
modules, this line instructs the server to load the specified driver
module. Even when not using loadable driver modules, this line
indicates which driver should interpret the information in this section.
Driver "nvidia"The BusID line is used to specify which of possibly multiple devices
this section is intended for. When this line isn't present, a device
section can only match up with the primary video device. For PCI
devices a line like the following could be used. This line should not
normally be included unless there is more than one video device
intalled.
BusID "PCI:0:10:0"
VideoRam 256
Clocks 25.2 28.3
EndSection
Device configured by xorgconfig:
Section "Device"
Identifier "My Video Card"
Driver "nvidia"
Option "DPMS" "on"
Option "NvAGP" "1"
Option "RenderAccel" "on"
Option "AllowGLXWithComposite" "true"
Option "AddARGBGLXVisuals" "True"
# unsupported card
#VideoRam 131072
# Insert Clocks lines here if appropriate
EndSection**********************************************************************
Screen sections
**********************************************************************
Any number of screen sections may be present. Each describes
the configuration of a single screen. A single specific screen section
may be specified from the X server command line with the "-screen"
option.
Section "Screen"
Identifier "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 24Subsection "Display" Depth 8 Modes "1280x1024" "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 16 Modes "1280x1024" "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsectionEndSection
**********************************************************************
ServerLayout sections.
**********************************************************************
Any number of ServerLayout sections may be present. Each describes
the way multiple screens are organised. A specific ServerLayout
section may be specified from the X server command line with the
"-layout" option. In the absence of this, the first section is used.
When now ServerLayout section is present, the first Screen section
is used alone.
Section "ServerLayout"
The Identifier line must be present
Identifier "Simple Layout"Each Screen line specifies a Screen section name, and optionally
the relative position of other screens. The four names after
primary screen name are the screens to the top, bottom, left and right
of the primary screen. In this example, screen 2 is located to the
right of screen 1.
Screen "Screen 1"Each InputDevice line specifies an InputDevice section name and
optionally some options to specify the way the device is to be
used. Those options include "CorePointer", "CoreKeyboard" and
"SendCoreEvents".
InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard"EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection</pre> <br /><br /><br />Un Saludo! -
gracias ZenPiPerS he dejado la seccion Module, Screec y device parecidas a la tuya pero adaptadas a mi monitor y ya va mucho mejor.
Ahora a esperar a que salga ubuntu 7.04
-
Joer, ha sido meterme al Linux y venirme todo de golpe.
A ver si es verdad que a Ubuntu le solucionan los problemas de los controladores 3D (sobre todo para ATI), porque he visto lo que hace beryl… y casi me viene la regla. ;DPD: Te debemos una ronda por el curro del script. :sisi:
