Mailinglist Archive: radeonhd (529 mails)
| < Previous | Next > |
Re: [radeonhd] ASUS A8Jp, Mobility Radeon X1700 - DVI-connected monitor doesn't work
- From: Coleman Kane <cokane@xxxxxxxxxx>
- Date: Sat, 01 Dec 2007 16:30:59 -0500
- Message-id: <4751D293.3050705@xxxxxxxxxx>
Coleman Kane wrote:
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
--- src/rhd_monitor.c.orig 2007-12-01 16:26:14.000000000 -0500
+++ src/rhd_monitor.c 2007-12-01 16:27:29.000000000 -0500
@@ -56,7 +56,7 @@
{
int i;
- xf86Msg(X_NONE, " Bandwidth: %dMHz\n", Monitor->Bandwidth / 1000);
+ xf86Msg(X_NONE, " Bandwidth: %0.2fMHz\n", lrintf(Monitor->Bandwidth) /
1000.0F);
xf86Msg(X_NONE, " Horizontal timing:\n");
for (i = 0; i < Monitor->numHSync; i++)
xf86Msg(X_NONE, " %3.1f - %3.1fkHz\n", Monitor->HSync[i].lo,
Kirill Belokurov wrote:Apply the attached patch to your latest radeonhd sources, rebuild,
On Friday 30 November 2007, Matthias Hopf wrote:It looks like the mode that your system tries to set up requires 88.8MHz
Unfortunately, with "noRandr" it is broken even worser: the Xorg simplyCan you verify that this issue happens withNo, unfortunately this didn't resolve the issue: the error mesage from(missed the CC to list, resending)Should be fixed in git now.
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):
the
Option "NoRandr"
as well? It probably will.
If everything works you should see an image on all connected monitors
including panel.
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
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
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
--- src/rhd_monitor.c.orig 2007-12-01 16:26:14.000000000 -0500
+++ src/rhd_monitor.c 2007-12-01 16:27:29.000000000 -0500
@@ -56,7 +56,7 @@
{
int i;
- xf86Msg(X_NONE, " Bandwidth: %dMHz\n", Monitor->Bandwidth / 1000);
+ xf86Msg(X_NONE, " Bandwidth: %0.2fMHz\n", lrintf(Monitor->Bandwidth) /
1000.0F);
xf86Msg(X_NONE, " Horizontal timing:\n");
for (i = 0; i < Monitor->numHSync; i++)
xf86Msg(X_NONE, " %3.1f - %3.1fkHz\n", Monitor->HSync[i].lo,
| < Previous | Next > |