same symptoms on my dad's computer :
since upgrade to xorg 7.1 the graphics output signal from the Matrox
Millenium G400 is out of range in terms of horizontal frequency for my
screen, so I get a blank screen and a message box ("OSD" style) from my
screen which says :
"invalid signal : 82 kHz , 102 Hz"
where a horizontal frequency of 82 kHz is of course out of range for the
screen (72 kHz max) moreover I can't understand where these values comes
from as no modelines listed in Xorg.0.log have these ones (see below).
I can switch without any problem to an other vt where I get the text display
back, the ps aux command indicates that X, gdm and everything else is
running normally.
I can recover a decent display signal back with the vesa driver or fbdev,
but that's only a poor workaround.
here is my xorg.conf : http://flamms.free.fr/nimp/xorg.conf.mga
and there my Xorg.0.log : http://flamms.free.fr/nimp/Xorg.0.log
an extract :
(--) MGA(0): Chipset: "mgag400" (G400)
(**) MGA(0): Depth 24, (--) framebuffer bpp 32
(==) MGA(0): RGB weight 888
(==) MGA(0): Using AGP 1x mode
(--) MGA(0): Linear framebuffer at 0xD4000000
(--) MGA(0): MMIO registers at 0xD6000000
(--) MGA(0): Pseudo-DMA transfer window at 0xD7000000
(==) MGA(0): BIOS at 0xC0000
(--) MGA(0): Video BIOS info block at offset 0x07A80
(==) MGA(0): Write-combining range (0xd4000000,0x2000000)
(--) MGA(0): VideoRAM: 32768 kByte
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/lib/xorg/modules/libddc.so
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Loading /usr/lib/xorg/modules/libi2c.so
(II) Module i2c: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.2.0
ABI class: X.Org Video Driver, version 1.0
(==) MGA(0): Write-combining range (0xd4000000,0x2000000)
(II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) MGA(0): I2C bus "DDC P1" initialized.
(II) MGA(0): I2C device "DDC P1:ddc2" registered at address 0xA0.
(II) MGA(0): I2C device "DDC P1:ddc2" removed.
(II) MGA(0): I2C Monitor info: 0x8227670
(II) MGA(0): Manufacturer: CTX Model: 5370 Serial#: 0
(II) MGA(0): Year: 2000 Week: 0
(II) MGA(0): EDID Version: 1.1
(II) MGA(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
(II) MGA(0): Signal levels configurable
(II) MGA(0): Sync: Separate CompositeSerration on. V.Sync Pulse req. if
CompSync or SyncOnGreen
(II) MGA(0): Max H-Image Size [cm]: horiz.: 33 vert.: 25
(II) MGA(0): Gamma: 2.10
(II) MGA(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) MGA(0): redX: 0.625 redY: 0.338 greenX: 0.281 greenY: 0.602
(II) MGA(0): blueX: 0.149 blueY: 0.073 whiteX: 0.283 whiteY: 0.297
(II) MGA(0): Supported VESA Video Modes:
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED] (interlaced)
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): [EMAIL PROTECTED]
(II) MGA(0): Manufacturer's mask: 0
(II) MGA(0): Supported Future Video Modes:
(II) MGA(0): #0: hsize: 640 vsize 480 refresh: 120 vid: 31793
(II) MGA(0): #1: hsize: 800 vsize 600 refresh: 100 vid: 26693
(II) MGA(0): #2: hsize: 1024 vsize 768 refresh: 90 vid: 24161
(II) MGA(0): #3: hsize: 1280 vsize 960 refresh: 65 vid: 17793
(II) MGA(0): Supported additional Video Mode:
(II) MGA(0): clock: 36.0 MHz Image Size: 310 x 232 mm
(II) MGA(0): h_active: 640 h_sync: 672 h_sync_end 720 h_blank_end 832
h_border: 0
(II) MGA(0): v_active: 480 v_sync: 481 v_sync_end 484 v_blanking: 509
v_border: 0
(II) MGA(0): Supported additional Video Mode:
(II) MGA(0): clock: 56.2 MHz Image Size: 310 x 232 mm
(II) MGA(0): h_active: 800 h_sync: 832 h_sync_end 896 h_blank_end 1048
h_border: 0
(II) MGA(0): v_active: 600 v_sync: 601 v_sync_end 604 v_blanking: 631
v_border: 0
(II) MGA(0): Supported additional Video Mode:
(II) MGA(0): clock: 94.5 MHz Image Size: 310 x 232 mm
(II) MGA(0): h_active: 1024 h_sync: 1072 h_sync_end 1168 h_blank_end 1376
h_border: 0
(II) MGA(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 808
v_border: 0
(II) MGA(0): Ranges: V min: 50 V max: 130 Hz, H min: 30 H max: 72 kHz,
(II) MGA(0): end of I2C Monitor info
(==) MGA(0): Using gamma correction (1.0, 1.0, 1.0)
(==) MGA(0): Min pixel clock is 17 MHz
(--) MGA(0): Max pixel clock is 300 MHz
(II) MGA(0): CTX:7053: Using hsync range of 30.00-72.00 kHz
(II) MGA(0): CTX:7053: Using vrefresh range of 50.00-130.00 Hz
(II) MGA(0): Clock range: 17.75 to 300.00 MHz
(WW) (1024x768h,CTX:7053) mode clock 78.8MHz exceeds DDC maximum 0MHz
(WW) (640x350,CTX:7053) mode clock 31.5MHz exceeds DDC maximum 0MHz
...
The EDID infos seem to be retrieved correctly, but the modelines validation
goes wrong : "(WW) (1024x768h,CTX:7053) mode clock 78.8MHz exceeds DDC
maximum 0MHz". I can't understand where the 0MHz comes from. It's the same
thing for all modes.
Trying to deactivate the use of DDC doesn't change anything. I still get the
blank screen with the invalid signal.
Sorry but I had no time to test the unofficial matrox driver (
http://forum.matrox.com/mga/viewtopic.php?t=20857 ).
So I downgraded from unstable to testing, and everything now works fine with
xorg 7.0
----- By the way it seems to be the same bug as #390739 ------
and the same bug as ubuntu bug #58721.
But I can't find a similar one in the bug database on freedesktop.org.
_________________________________________________________________
Découvrez un moyen pour éliminez tous les virus de votre PC !
http://safety.live.com/site/fr-FR
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
