| View previous topic :: View next topic |
| Author |
Message |
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
 Posted: Sat Nov 13, 2004 5:34 pm Post subject: problemi xorg |
 |
|
Ciao!
Quando faccio partire X lo schermo risulta diviso in 3 sezioni:
| =======================|====|
|...................................................... |.......|
|...................................................... |.......|
|...................................................... |.......|
|............ A..................................... |..C..|
|...................................................... |.......|
|...................................................... |.......|
|========================|.......|
|..............B......................................|....... |
|======================= |====|
Nella parte A viene visulaizzato "in scala" quello che dovrebbe essere a tutto schermo, perfettamente funzionante.Quindi lo sfondo, il pannello, i menu ecc ecc..
La parte B riporta la parte alta dello schermo interattiva. Per capirci quando sono con il puntatore del mouse in alto su A vedo anche sotto un altro puntatore su B .Come se avessi u n doppio schermo ma in quello piccolo viene riprodotta la parte alta di quello grande.
Nella parte C invece ci sono delle coloratissime e molto coinvolgenti linee verticali.
Sia su B che su C il mouse non va'.Esso si puo' muovere solo in A che e' considerata come dimensione massima dello schermo.
Non credo dipenda dall' hardware visto che quando non sono su X lo schermo e' intero con la risoluzione giusta.
Il problema e' nato da un aggiornamento del world che ha bloccato completamente il pc.Dopo l'hard reset X ha cominciato a dare il sopracitato errore.
Dato che e' da molto che non formattavo e il sync dopo 2 settimane buche era gia' troppo costoso ho deciso di rimettere tutto da 0.
Cosi' ho fatto e ora non mi spiego perche' dia ancora questo problema.
Naturalmente nessun messaggio di errore sul log di Xorg tranne questa info che forse puo' aiutare:
| Code: | | -BScreen : : BScreen : managing screen 0 using visual 0x21, depht 24 |
Se avete bisogno di xorg.conf ve lo metto subito...
Grazie per l'aiuto! |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31478
Location: here
|
| Posted: Sat Nov 13, 2004 5:40 pm Post subject: |
|
|
Ma hai provato a ricompilare xorg? Prova magari anche a postare la configurazione
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sat Nov 13, 2004 11:54 pm Post subject: |
|
|
si ho provato a ri-emergerlo ma niente...
ecco xorg.conf
| Code: | # Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This 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
EndSubSection
# This 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"
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.
RgbPath "/usr/X11R6/lib/X11/rgb"
# 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/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
# FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
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 <Crtl><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 <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><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" "pc102"
# 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 "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbModel" "dell101"
Option "XkbLayout" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Option "Emulate3Buttons"
Option "ZAxis Mapping" "4 5"
# 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 "Generic 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 31.5 - 64.3
#31.5 - 64.3
# HorizSync 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 50 - 70
#50-70
EndSection
# **********************************************************************
# 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 "vga"
# 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 "Generic Video Card"
Driver "nvidia"
Option "NoLogo" "true"
Option "NvAGP" "3"
Option "RenderAccel" "true"
#VideoRam 32768
# 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 "Generic Video Card"
Monitor "Generic Monitor"
DefaultDepth 24
Subsection "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 "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
#Virtual 1600 1200
EndSubsection
EndSection
# **********************************************************************
# 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
|
non e' che potrebbe dipendere da HorizSync e VertRefresh? |
|
| Back to top |
|
|
Simbul
Tux's lil' helper
Joined: 31 Oct 2004
Posts: 113
|
| Posted: Sun Nov 14, 2004 9:16 am Post subject: |
|
|
Hai configurato correttamente la scheda video nvidia?
http://www.gentoo.org/doc/en/nvidia-guide.xml
_________________
Simbul
There's only 10 types of people in the world,
Those who understand binary and those who don't |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sun Nov 14, 2004 9:48 am Post subject: |
|
|
tutto perfetto.
La configurazione e' identica.
Non riesco a capire cosa possa essere, tutto sembra funzionare benissimo.
l'unica cosa e' che provando glxgears sembra un po' troppo lento rispetto al normale (90 frame in 5 sec, 18.000 FPS)
Ma che cavolo sara'????? 
Ci fosse almeno qualche messaggio d'errore....che ne so tanto per dare una mano.... 
Ancora grazie a tutti.... |
|
| Back to top |
|
|
fctk
Veteran
Joined: 28 Jan 2004
Posts: 1424
Location: Milan, Italy, EU
|
| Posted: Sun Nov 14, 2004 10:52 am Post subject: |
|
|
| chiapil wrote: | | non e' che potrebbe dipendere da HorizSync e VertRefresh? |
beh... se i valori che hai inserito sono quelli giusti escluderei che il problema possa dipendere da loro... |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sun Nov 14, 2004 11:35 am Post subject: |
|
|
Sono quelli che avevo quando tutto funzionava solo che ho notato questo messaggio sul log di Xorg
| Code: | (II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce4 440 Go
(--) NVIDIA(0): VideoBIOS: 04.17.00.55.b2
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): VideoRAM: 65536 kBytes
(II) NVIDIA(0): Connected display device(s): DFP-0
(--) NVIDIA(0): Display device DFP-0: maximum pixel clock at 8 bpp: 350 MHz
(--) NVIDIA(0): Display device DFP-0: maximum pixel clock at 16 bpp: 350 MHz
(--) NVIDIA(0): Display device DFP-0: maximum pixel clock at 32 bpp: 350 MHz
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.8.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(WW) NVIDIA(0): The user specified VertRefresh "50.000-70.000" has been
(WW) NVIDIA(0): adjusted to "50.000-60.000" (the intersection with
(WW) NVIDIA(0): EDID-specified VertRefresh "0.000-60.000"
(II) NVIDIA(0): Generic Monitor: Using hsync range of 31.50-64.30 kHz
(II) NVIDIA(0): Generic Monitor: Using vrefresh range of 50.00-60.00 Hz
(II) NVIDIA(0): Clock range: 12.00 to 350.00 MHz
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(WW) (1400x1050,Generic Monitor) mode clock 122MHz exceeds DDC maximum 110MHz
(**) NVIDIA(0): Validated modes for display device DFP-0:
(**) NVIDIA(0): Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(**) NVIDIA(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(**) NVIDIA(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(0): Display dimensions: (320, 240) mm
(--) NVIDIA(0): DPI set to (101, 108)
(II) NVIDIA(0): Setting mode "1280x1024"
|
e mi chiedevo se fossero proprio giusti visto che anche i mm mi sembrano sballati.Cmq e ' un normale 15 pollici. |
|
| Back to top |
|
|
fctk
Veteran
Joined: 28 Jan 2004
Posts: 1424
Location: Milan, Italy, EU
|
| Posted: Sun Nov 14, 2004 11:57 am Post subject: |
|
|
| ma i valori li hai presi dalle specifiche tecniche del tuo monitor? non basta il fatto che funzionavano prima. per quanto riguarda le dimensioni del monitor è bene che tu setti correttamente anche quelle (sezione Monitor esempio: DisplaySize 326 244). io di solito uso un tool, amlc, che genera automaticamente tutta la sezione monitor in base ai dati che gli dati (tra i quali proprio le dimensioni e i refresh). lo puoi trovare qui: http://delenn.tky.hut.fi/amlc/ |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sun Nov 14, 2004 1:04 pm Post subject: |
|
|
Ho seguito il tuo consiglio ma il problema persiste.....
Non so proprio che fare....  |
|
| Back to top |
|
|
fctk
Veteran
Joined: 28 Jan 2004
Posts: 1424
Location: Milan, Italy, EU
|
| Posted: Sun Nov 14, 2004 2:43 pm Post subject: Re: problemi xorg |
|
|
| chiapil wrote: | Naturalmente nessun messaggio di errore sul log di Xorg tranne questa info che forse puo' aiutare:
| Code: | | -BScreen : : BScreen : managing screen 0 using visual 0x21, depht 24 |
|
beh... questo messaggio lo ottengo anch'io ma non sembra causa di alcun problema... (da me tutto funziona perfettamente)
altra cosa: ci puoi dire qual è il modello esatto del monitor? e poi... come hai ottenuto lo xorg.conf? con il generatore automatico o con quello semiautomatico? |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sun Nov 14, 2004 3:25 pm Post subject: |
|
|
il laptop e' un dell inspiron 8200
monitor (riporto pari pari)
Type (active-matrix TFT) UXGA
Height 228.1 mm (9.0 inches)
Width 304.1 mm (12.0 inches)
Diagonal 308.1 mm ( 15 inches)
Maximum resolution 1600x1200 at 16.8 million colors
Refresh rate 60 Hz
Xorg.conf l'ho ottenuto tramite il comando xorgconfig ma ho corretto a mano tutte le inesattezze |
|
| Back to top |
|
|
arnor
Tux's lil' helper
Joined: 01 Nov 2004
Posts: 147
|
| Posted: Sun Nov 14, 2004 4:42 pm Post subject: |
|
|
ho il tuo stesso identico problema.
Il problema si è presentato dopo l'update del pacchetto nvidia-kernel 1.06629 e libreria nvidia-glx 1.06629.
Prima usavo il monitor a 1600x1200 ma ora ho anchio la divisione dello schermo in 3 parti.
A mio avviso è un problema di monitor. hSync o vSync.
Ma non riesco a trovare dei valori giusti. :/
Ciao lo |
|
| Back to top |
|
|
lavish
Bodhisattva
Joined: 13 Sep 2004
Posts: 4296
|
| Posted: Sun Nov 14, 2004 5:02 pm Post subject: |
|
|
| chiapil wrote: | | l'unica cosa e' che provando glxgears sembra un po' troppo lento rispetto al normale (90 frame in 5 sec, 18.000 FPS) |
Eh?!
_________________
minimalblue.com | secgroup.github.io/ |
|
| Back to top |
|
|
fctk
Veteran
Joined: 28 Jan 2004
Posts: 1424
Location: Milan, Italy, EU
|
| Posted: Sun Nov 14, 2004 5:19 pm Post subject: |
|
|
| arnor wrote: | A mio avviso è un problema di monitor. hSync o vSync.
Ma non riesco a trovare dei valori giusti. :/ |
ora che ci penso, però, i valori di hsync e di vsync dovrebbero riferirsi soltanto ai monitor a tubo catodico e non agli lcd... mi pare di aver letto che per quest'ultimi bisogna mettere un valore "standard" ma di più proprio non so... |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sun Nov 14, 2004 6:38 pm Post subject: |
|
|
| lavish wrote: | | chiapil wrote: | | l'unica cosa e' che provando glxgears sembra un po' troppo lento rispetto al normale (90 frame in 5 sec, 18.000 FPS) |
Eh?! |
eeemmmm...stavo compilando.....
ora va a 1800 FPS......  |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sun Nov 14, 2004 6:42 pm Post subject: |
|
|
In effetti anche io non so se i valori di Horiz e Vert siano giusti...ma non so dove trovarli,sul sito della dell c'e' solo quello che ho postato sopra
Cmq si potrebbe provare a rimettere la versione precedente di nvidia-kernel e nvidia-glx.....chissa'....
Sospettavo che dipendesse da un aggiornamento.
UFFFFFFF!!!!!
eh eh eh tutti i comfort delle beta!  |
|
| Back to top |
|
|
ulric
Tux's lil' helper
Joined: 04 Mar 2004
Posts: 137
Location: Vicenza-Padova
|
| Posted: Sun Nov 14, 2004 7:12 pm Post subject: |
|
|
Confermo, ho avuto anch'io il problema.
Tutto era dovuto a cattivi valori, ora ho
HorizSync 30-64
VertRefresh 60
Il problema mi si è presentato quando ho cambiato il cavo dell'lcd da analogico a dvi. |
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Sun Nov 14, 2004 8:41 pm Post subject: |
|
|
Ho provato a mettere i tuoi valori ma non cambia nulla.........
Forse non e' quello.... |
|
| Back to top |
|
|
arnor
Tux's lil' helper
Joined: 01 Nov 2004
Posts: 147
|
| Posted: Mon Nov 15, 2004 9:04 am Post subject: |
|
|
hai provato a fare il downgrade dei driver?
Io con i 6111-r3 non ho problemi.
adesso cercherà sul forum gentoo.org x vedere se qualcuno ha avuto problemi dopo l'update.
Ciao lo |
|
| Back to top |
|
|
arnor
Tux's lil' helper
Joined: 01 Nov 2004
Posts: 147
|
|
| Back to top |
|
|
chiapil
n00b
Joined: 11 Oct 2004
Posts: 27
Location: Oristano
|
| Posted: Mon Nov 15, 2004 8:18 pm Post subject: |
|
|
Ho rimesso la versione precedente dei driver nvidia e il problema e' sparito...indubbiamente e' un bug quindi attenderemo aggiornamenti all'aggiornamento 
Grazie a tutti per l'aiuto! |
|
| Back to top |
|
|
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31478
Location: here
|
| Posted: Mon Nov 15, 2004 8:19 pm Post subject: |
|
|
Metti il tag [risolto] al titolo
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
|
Forum italiano (Italian)
