[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#294556: marked as done (xfree86-xserver: savage driver does not query monitor DDC)

Your message dated Wed, 17 Jan 2007 18:59:56 +0100
with message-id <45AE641C.40103@ens-lyon.org>
and subject line Bug#294556: xfree86-xserver: savage driver does not query monitor DDC
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xfree86-xserver
Version: xserver-xfree86
Severity: normal


Hi, as per the Subject, the savage driver doesn't ask the monitor about 
its capabilities via DDC, leading to the X server defaulting to 75 dpi, 
and showing very small fonts.

I have observed this behaviour on multiple on-board GFX machines, and 
even switching to the 'vesa' generic driver shows the expected results in 
the XFree86.0.log, and set the display DPI to 86x84 for a 15" TFT 
display.

I can confirm that similar machines using the 'via' driver, and another 
machine using 'nv' driver get the DDC info correctly - this problem seems 
to be local to the 'savage' driver.

Compare:
(II) SAVAGE(0): VESA BIOS detected
(II) SAVAGE(0): VESA VBE Version 3.0
(II) SAVAGE(0): VESA VBE Total Mem: 7104 kB
(II) SAVAGE(0): VESA VBE OEM: S3 Graphics ProSavage DDR Family BIOS
(II) SAVAGE(0): VESA VBE OEM Software Rev: 2.0
(II) SAVAGE(0): VESA VBE OEM Vendor: S3 Garphics Incorporated.
(II) SAVAGE(0): VESA VBE OEM Product: VBE 3.0
(II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 0.0
(--) SAVAGE(0): Chip: id 8d04, "ProSavage DDR-K"
(--) SAVAGE(0): Engine: "ProSavage"
(--) SAVAGE(0): mapping MMIO @ 0xec000000 with size 0x80000
(==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0)
(--) SAVAGE(0): probed videoram:  8192k
(--) SAVAGE(0): Detected current MCLK value of 14.318 MHz
(II) SAVAGE(0): Generic Monitor: Using hsync range of 30.00-60.00 kHz
(II) SAVAGE(0): Generic Monitor: Using vrefresh range of 50.00-75.00 Hz
(II) SAVAGE(0): Clock range:  10.00 to 220.00 MHz
(II) SAVAGE(0): Not using default mode "640x350" (vrefresh out of range)
(II) SAVAGE(0): Not using default mode "320x175" (vrefresh out of range)
[....]
(**) SAVAGE(0):  Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) SAVAGE(0): Modeline "320x240"   12.60  320 328 376 400  240 245 246 262 doublescan -hsync -vsync
(==) SAVAGE(0): DPI set to (75, 75)

with ...

(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 7104 kB
(II) VESA(0): VESA VBE OEM: S3 Graphics ProSavage DDR Family BIOS
(II) VESA(0): VESA VBE OEM Software Rev: 2.0
(II) VESA(0): VESA VBE OEM Vendor: S3 Garphics Incorporated.
(II) VESA(0): VESA VBE OEM Product: VBE 3.0
(II) VESA(0): VESA VBE OEM Product Rev: Rev 0.0
(**) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(II) VESA(0): VESA VBE DDC supported
(II) VESA(0): VESA VBE DDC Level 2
(II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) VESA(0): VESA VBE DDC read successfully
(II) VESA(0): Manufacturer: AOC  Model: a562  Serial#: 10257
(II) VESA(0): Year: 2003  Week: 50
(II) VESA(0): EDID Version: 1.3
(II) VESA(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
(II) VESA(0): Sync:  Separate
(II) VESA(0): Max H-Image Size [cm]: horiz.: 30  vert.: 23
(II) VESA(0): Gamma: 2.30
(II) VESA(0): DPMS capabilities: Off; RGB/Color Display
(II) VESA(0): First detailed timing is preferred mode
(II) VESA(0): redX: 0.628 redY: 0.353   greenX: 0.290 greenY: 0.595
(II) VESA(0): blueX: 0.144 blueY: 0.088   whiteX: 0.304 whiteY: 0.325
(II) VESA(0): Supported VESA Video Modes:
(II) VESA(0): 720x400@70Hz
[...]

(II) VESA(0): Total Memory: 111 64KB banks (7104kB)
(WW) VESA(0): config file vrefresh range 50-75Hz not within DDC vrefresh range 55-75Hz
(II) VESA(0): Generic Monitor: Using hsync range of 30.00-60.00 kHz
(II) VESA(0): Generic Monitor: Using vrefresh range of 50.00-75.00 Hz
(II) VESA(0): Not using built-in mode "1280x960" (width too large for virtual size)
(--) VESA(0): Virtual size is 1024x768 (pitch 1024)
(**) VESA(0): *Built-in mode "1024x768"
(**) VESA(0):  Built-in mode "800x600"
(**) VESA(0):  Built-in mode "640x480"
(--) VESA(0): Display dimensions: (300, 230) mm
(--) VESA(0): DPI set to (86, 84)


Cheers,
Gavin.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8

--- End Message ---
--- Begin Message --- 
Closing, as suggested by the submitter, since he does not use this setup
anymore.
Feel free to reopen if you ever reproduce the problem.

Brice

--- End Message ---
Reply to: