Bug 80230
Summary: | xdpyinfo shows wrong monitor size on Dell Inspiron 8000 with 1600x1200 display | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dave.habben |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-24 18:55:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Oliva
2002-12-22 22:09:29 UTC
The DPI is determined in the following order: 1) DDC probe 2) Commandline -dpi option / config file DisplaySize option 3) Default to 75x75dpi If DDC probe is unsupported by the hardware, or if a KVM switch blocks it, or if a driver doesn't support it, then it simply can't be autodetected at all. In this case, the DPI must be specified in the config file or on the commandline. If neither is present, the X server uses 75dpi by default. I fail to see the bug here though. Could you provide details of what exactly you're reporting as buggy here? It was not as much of a bug report as a question on how X managed to come up with the dimensions it did. Since DDC probing doesn't actually work for these Dell Laptop LCD displays, could we perhaps have anaconda/redhat-config-xfree86 to set DisplaySize? For `Dell 1600X Laptop Display Panel', the correct settings would be: DisplaySize 304 228 DisplaySize setting not put in by installer in phoebe2. Also, is there anything that can be done about having this display auto detected? Where should I look to find out why it's not being detected by the installer nor redhat-config-xfree86? Lots of LCD panels simply are not DDC probeable as it isn't implemented in the hardware itself. There's nothing we can do about a panel that doesn't respond to DDC. In order for these to work out of the box, we would require a laptop database which stores the panel dimensions and whatnot for all laptops and panels that are not DDC probeable, or some alternate way via reading the BIOS of the systems. Our config tools could then use this information. However, we do not have such a database, nor a way of reading the information from the BIOS (which is likely to be completely different on every laptop model) currently, so the only way to do this is for the user to hard code it into the config file. It isn't something that is really an XFree86 problem per se, at least IMHO. It's something that is more in the hardware detection and config-tool area. One could argue that XFree86 could implement the BIOS munging hardware detection, and supply a database, but that would be something that would have to come from XFree86.org, and not something we'd be implementing ourselves, at least not any time soon. Caveat: I'm not even completely sure if any of this is that reasonably doable at all without hardware manufacturer cooperation, the above is all theoretical and could be way off base. A long time ago, you said it might be possible to add the dimensions to the hardware database, such that the installer would take care of adding them. This still hasn't been done. For reference, the dimensions for a Dell 1600x1200 Laptop Display Panel are: DisplaySize 304 228 Please upgrade to Fedora Core 2 or later, and if this issue turns out to still be reproduceable, please file a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates. It works in FC3-re1001.0, and probably in FC2 as well. Thanks, |