Bug 146972

Misfiled against XFree86 (which does not exist in FC3), reassigning
to "xorg-x11" component.

> The Dell driver kinda worked, but the display was garbled on the
> right side of the screen.  The Generic driver just plain didn't
> work.  

Could you clarify a bit what is meant by "Dell driver" and "Generic
driver"?  Does Dell supply additional video drivers, or are you
refering to manually choosing your monitor from a list in our
config tool?

Please run "ddcprobe" and paste the results here.  Also, please
attach your X server config file and log file as individual
uncompressed file attachments.

Setting status to "NEEDINFO", awaiting requested file attachments
and clarifications requested in comment #2.  Thanks in advance.

Created attachment 110876 [details]
X Config file

As requested...

Sorry for the confusion!  I was referring to selecting Dell manually
as a manufacturer within your config tool.

The results of the ddcprobe are below:

______________________________________________________

Videocard DDC probe results
Description:  ATI Technologies Inc. M3
Memory (MB):  8

Monitor DDC probe results
Monitor DDC Probe failed.

______________________________________________________

I'm not clear on what file the 'log file' is referring to.  Can you
provide more information on what you need and I'll be happy to send it
along.

Thanks in advance!

Please upgrade to the latest rawhide xorg-x11 release, which contains
numerous fixes that mays solve this issue.  If the problem still exists
in the latest rawhide xorg-x11 packages, it probably indicates a generic
bug in X.Org that is not Fedora Core specific.  In this case, file a bug
report in X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg"
component, along with full details, and attach a copy of your X.Org server
config file and log file.  If you require technical support or assistance
in obtaining this information, you can write to the xorg
mailing list also.

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.

Setting status to "NEEDINFO", awaiting X.Org bug report URL for
tracking.

(In reply to comment #5)
> Sorry for the confusion!  I was referring to selecting Dell manually
> as a manufacturer within your config tool.
> 
> The results of the ddcprobe are below:
> 
> ______________________________________________________
> 
> Videocard DDC probe results
> Description:  ATI Technologies Inc. M3
> Memory (MB):  8
> 
> Monitor DDC probe results
> Monitor DDC Probe failed.

This indicates that your display either does not support DDC, or that
you're using a KVM switch that does not pass the DDC signal through
correctly.  Since this is an M3 however, I'm assuming it is the former.
A lot of older laptops with M3/M4 era hardware do not support DDC.  As
such, there's no way to autodetect the display, and it must be chosen
from the list of available monitors manually.  If there is no entry
for a particular display, it can be set up manually by the user by
hand editing the config file and punching in values from the monitor's
manual or datasheet, or by submitting the manufacturer's .INF file for
the monitor to us from Microsoft Windows driver download from their
website.

So, when our tool lists it as "unknown", this is correct and not possible
to work around unless the hardware really does support DDC.

>Setting the monitor to the Dell Laptop Display 1024x768 will result
>(after logoff/logon) in garbled output on the right side of the display.

This would be a video driver bug most likely, but a separate issue
from wether or not DDC probing works (or is possible on this machine).


> I'm not clear on what file the 'log file' is referring to.  Can you
> provide more information on what you need and I'll be happy to send it
> along.

The X server log file, X server config file, the output of lsmod,
a copy of /var/log/messages, and any other information that might
be useful.

Also, please report the issue to X.Org as requested in comment #6 above,
which will accelerate the likelyhood of finding a solution for this problem
before FC4 is finalized.

Either way, please respond as soon as you can, so we can make some
progress on diagnosis for this.

Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue.  Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:

        http://fedora.redhat.com/download

If this issue turns out to still be reproduceable in the latest
version of Fedora Core, 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.

Setting status to "CURRENTRELEASE".