Alberto Mardegan wrote: > I tried the package you pointed me to; I don't see any apparent > improvement, but the logs have definitely changed and now they report > three ports (?).
Three ports are quite common actually, even if the driver has never been able to exploit them so far. Such a board often has 2 rendering pipelines that can be programmed to write on various ports. > Maybe we can have some faster progressing if I add some debugging > printfs here and there in the driver; is there a mailing list for it? > Or in any case, feel free to tell me some things to try out. Could you send the output of xrandr --verbose with this driver? (make sure you have xbase-clients 7.2 installed). > Monitor -- AUTO > Connector -- VGA > DAC Type -- TVDAC/ExtDAC > TMDS Type -- None > DDC Type -- CRT2_DDC > (II) RADEON(0): Port1: > Monitor -- AUTO > Connector -- Proprietary/LVDS > DAC Type -- None > TMDS Type -- None > DDC Type -- LCD_DDC > (II) RADEON(0): Port2: > Monitor -- AUTO > Connector -- STV > DAC Type -- TVDAC/ExtDAC > TMDS Type -- None > DDC Type -- NONE It sees the VGA output, the internal LVDS panel, and a TV output. > (II) RADEON(0): Output VGA-1 disconnected > (II) RADEON(0): Output LVDS connected > (II) RADEON(0): Output S-video disconnected > (II) RADEON(0): Output LVDS using initial mode 1280x800 But it does not see that VGA-1 is connected. I hope it's not caused by your not behaving as a real monitor (that's why I asked earlier whether you could try with a real monitor). Or it could be a problem with the connector table. Does it help if you do something like this? xrandr --addmode VGA-1 800x600 xrandr --output VGA-1 --mode 800x600 I'll see with Alex Deucher who wrote this code, he might have an idea. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
