Mailinglist Archive: radeonhd (352 mails)

[Matthias Hopf <mhopf@xxxxxxx>]

First of all, is this a regression, or did you have this with previous
versions as well, or is this the first test?

On Apr 11, 08 10:40:26 -0400, Tyson Whitehead wrote:
> 1- The EDID information for the laptop screen is not aquired under any
> circumstances.  The Xorg log file contains lines like so
>
> (II) RADEONHD(0): Query for AtomBIOS Get Panel EDID: failed
> (WW) RADEONHD(0): No monitor size info, assuming 96dpi
>
> (strange that 'Panel' is not all in caps there like everywhere else).
> The VESA driver, however, reports the following:

This still happens from time to time - apparently the Vesa BIOS does
emulate DDC there. Strange. Maybe we should think about accessing the
Vesa BIOS if we don't get any other information. Egbert?

> 2- If I plug an external monitor into the HDMI port (through a HDMI ->
> DVI cable), either before or after starting Xorg, the monitor indicates
> it is switchng to DVI mode, but nothing happens on the computer end
> (xrandr report nothing and nothing shows up in the Xorg logs).

Maybe your connector table is buggered up. You might want to check
  Option "HPD" "swap"
and/or verify with rhd_conntest as described in the README.

> 3- If I plug an external monitor into the VGA port before starting Xorg,
> it is recognized, and I can fully control it via xrandr.  However, I
> loose my ability to switch to a virtual terminal (ctrl+alt+F1), and the

What do you mean with "loose"? Doesn't it do the switch any more, or is
the screen blank?

> latop screen also refuses to work (remains dark) on any subsequent
> restarts of Xorg (without rebooting the latop) unless the external
> monitor is re-plugged into the VGA port before the restart.

This very much looks like a broken connector table.

> Further, once I unplug the VGA connection, xrandr starts reporting bogus
> DVI-D_1 information until the next time I re-plugin the VGA connection
> (even if nothing has ever been plugged into the HDMI connection):

Eek. Sounds like some data structures are pushed around the wrong way.
Or maybe a side effect of the broken connector table?

> tyson@whitehead2:~$ xrandr --output VGA_1 --auto
> X Error of failed request:  BadMatch (invalid parameter attributes)
>     Major opcode of failed request:  155 (RANDR)
>     Minor opcode of failed request:  21 ()
>     Serial number of failed request:  17
>     Current serial number in output stream:  17

You have to get a newer xrandr (1.2.3 or git). That is actually a FAQ.

Can you create a bug report with your information?

Matthias

-- 
Matthias Hopf <mhopf@xxxxxxx>      __        __   __
Maxfeldstr. 5 / 90409 Nuernberg   (_   | |  (_   |__          mat@xxxxxxxxx
Phone +49-911-74053-715           __)  |_|  __)  |__  R & D   www.mshopf.de
-- 
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx