| Summary: | latest git driver font issues | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Alex <alevkovich> | ||||||
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
| Status: | RESOLVED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | alevkovich | ||||||
| Version: | 7.3 (2007.09) | ||||||||
| Hardware: | Other | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Alex
2008-04-05 06:54:27 UTC
Your monitor does not provide an edid, so the server does not know what size display you have. You can use xrandr to set the display size, or add the display size to the monitor section of your config. xrandr --fbmm XxY or DisplaySize X Y Replace X and Y with the width and height of your monitor in mm. My monitor section:
Section "Monitor"
#UseModes "16:10"
Identifier "monitor1"
VendorName "Plug'n Play"
DisplaySize 333 209
Option "DPMS"
EndSection
I have a notebook and everything ok with driver v. 6.8.0. So I think the problems are with latest changes.
option IgnoreEDID helped me. But anyway I think there is something wrong in the driver code. (In reply to comment #3) > option IgnoreEDID helped me. But anyway I think there is something wrong in the > driver code. > Sounds like your monitor has a bad edid. Can you attach you xorg log and config? Created attachment 15783 [details]
xorg.conf
Created attachment 15784 [details]
Xorg.0.log
there is no edid so we have no way of knowing what size your monitor is. You'll need to specify the display size in your xorg config file. You'll need to change the identifier of your monitor to LVDS if you want to associate it with your panel rather than the VGA port:
Identifier "LVDS"
Please see this page for more on xrandr configuration:
http://wiki.debian.org/XStrikeForce/HowToRandR12
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.