Mailinglist Archive: radeonhd (529 mails)

[Coleman Kane <cokane@xxxxxxxxxx>]

Coleman Kane wrote:
> Coleman Kane wrote:
>   
> > Kirill Belokurov wrote:
> >   
> >     
> > > On Friday 30 November 2007, Matthias Hopf wrote:
> > >   
> > >     
> > >       
> > > > > > > (missed the CC to list, resending)
> > > > > > >
> > > > > > > Please find it in the attachment. For the record, below is the
> > > > > > > rhd_conntest output when I was dumping it (TFT monitor was
> > > > > > > disconnected this time):
> > > > > > >           
> > > > > > >             
> > > > > > >               
> > > > > > Should be fixed in git now.
> > > > > >         
> > > > > >           
> > > > > >             
> > > > > No, unfortunately this didn't resolve the issue: the error mesage from
> > > > > the
> > > > >       
> > > > >         
> > > > >           
> > > > Can you verify that this issue happens with
> > > >   Option "NoRandr"
> > > > as well? It probably will.
> > > > If everything works you should see an image on all connected monitors
> > > > including panel.
> > > >     
> > > >       
> > > >         
> > > Unfortunately, with "noRandr" it is broken even worser: the Xorg simply 
> > > doesn't start at all:
> > >
> > > (EE) RADEONHD(0): No valid modes found
> > > (EE) Screen(s) found, but none have a usable configuration.
> > >
> > > apparently, there is some issue with rejected panel modes:
> > > (II) RADEONHD(0): Rejected mode "1440x900" (1440x900:88.8Mhz): mode clock 
> > > too 
> > > high
> > >
> > > I am attaching the Xorg log for this case.
> > >
> > > Regards, Kirill
> > >   
> > >     
> > >       
> > It looks like the mode that your system tries to set up requires 88.8MHz
> > display bandwidth, however the panel seems to report that it's max is
> > 88MHz (interpreted as 88.0MHz I assume) meaning that your monitor is
> > telling X that the mode that it gave to X is out-of-range. It looks like
> > a truncation problem to me... I wonder where this is occurring.
> >
> > --
> > Coleman Kane
> >
> >   
> >     
> Apply the attached patch to your latest radeonhd sources, rebuild,
> reinstall, re-run X, and re-send the log. This patch attempts to undo
> that incidental truncation that happens around line 60 of src/rhd_monitor.c.
>
> --
> Coleman Kane
>   
Reviewing the source code a little further, the value displayed here is
likely being pulled from the clock field of the EDID structure for your
panel. This is an integer of whole megahertz value, in this case is 88.
This is likely a bug in the panel by some naive code that originally
wrote the EDID data and truncated 88.8 or 88.9 to 88MHz. I *think* the
proper value should be 89.


Does "IgnoreEDID" work in the driver code yet?

--
Coleman Kane

-- 
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx