Re: scheda video agp con driver liberi
Alessandro Pellizzari ha scritto:
Se c'e`, allora e` colpa del monitor/scheda video, e devi specificare le
frequenze a mano con HorizSync e VertRefresh, ma per questo ti servono
le specifiche del monitor.
Se e` un LCD 17" in su, puoi provare con
HorizSync "30-60"
VertRefresh "50-60"
Eventualmente abbassando il 60 in HorizSync un po' alla volta (prova di
2 in due, quindi 58, 56, 54, ...)
Ho seguito le tue indicazioni, ora mi appare una schermata che mi dice:
[cut]
Parse error on line 82 of section Monitor in file /etc/X11/xorg.conf
The HorizSync keyword must be followed by a list of numbers or ranges.
(EE) Problem parsing the config file
(EE) Error parsing the config file
Fatal server error:
no screens found
(WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
(WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
Se ancora non funziona, controlla /var/log/Xorg.*.log e vedi le righe
che iniziano con WW (warning) o EE (error).
Ecco ciò che ho estrapolato in ordine di "apparizione":
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode
disabled
(WW) (1280x960,M17AAC) mode clock 148.5MHz exceeds DDC maximum 140MHz
(WW) (1280x1024,M17AAC) mode clock 157.5MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,M17AAC) mode clock 162MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,M17AAC) mode clock 175.5MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,M17AAC) mode clock 189MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,M17AAC) mode clock 202.5MHz exceeds DDC maximum 140MHz
(WW) (1600x1200,M17AAC) mode clock 229.5MHz exceeds DDC maximum 140MHz
(WW) (1792x1344,M17AAC) mode clock 204.8MHz exceeds DDC maximum 140MHz
(WW) (1792x1344,M17AAC) mode clock 261MHz exceeds DDC maximum 140MHz
(WW) (1856x1392,M17AAC) mode clock 218.3MHz exceeds DDC maximum 140MHz
(WW) (1856x1392,M17AAC) mode clock 288MHz exceeds DDC maximum 140MHz
(WW) (1920x1440,M17AAC) mode clock 234MHz exceeds DDC maximum 140MHz
(WW) (1920x1440,M17AAC) mode clock 297MHz exceeds DDC maximum 140MHz
(WW) (1400x1050,M17AAC) mode clock 151MHz exceeds DDC maximum 140MHz
(WW) (1400x1050,M17AAC) mode clock 155.8MHz exceeds DDC maximum 140MHz
(WW) (1400x1050,M17AAC) mode clock 184MHz exceeds DDC maximum 140MHz
(WW) (1680x1050,M17AAC) mode clock 147.14MHz exceeds DDC maximum 140MHz
(WW) (1920x1200,M17AAC) mode clock 193.16MHz exceeds DDC maximum 140MHz
(WW) (1920x1200,M17AAC) mode clock 230MHz exceeds DDC maximum 140MHz
(WW) (1920x1440,M17AAC) mode clock 341.35MHz exceeds DDC maximum 140MHz
(WW) (2048x1536,M17AAC) mode clock 266.95MHz exceeds DDC maximum 140MHz
(WW) (2048x1536,M17AAC) mode clock 340.48MHz exceeds DDC maximum 140MHz
(WW) (2048x1536,M17AAC) mode clock 388.04MHz exceeds DDC maximum 140MHz
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
Bye.
Ciao, grazie e....
buona Domenica.
Reply to: