Comment 59 for bug 137234

(In reply to comment #34)
> (In reply to comment #33)
> > Ok sounds like the original bug is fixed here then. The brightness problem
> > could be a kernel issue, can you file a new bug for that with the output of
> > "xrandr --prop" attached and also a listing of your /sys/class/backlight
> > directory (along with the other usual bits)?
> >
>
> Jesse, only if Vincenzo connect the monitor _before_ power on the machine, it
> works. If boot without external monitor , there is no way to bring it up using
> xrandr. That's what comment# 31 mean... It looks like a pipe is always
> disabled...
>
> Correct me if I'm wrong, Vincenzo.

Oh I thought #32 meant everything was working, but on looking at the logs (please just attach the plain logs next time, no need to gzip) it does look like both are the git version of the driver, sorry about that.

Looking again at the dumps and at the latest logs, the startup states are as follows:
plugged in before boot: ADPA: 0x80008018 (enabled, pipe A, +hsync, +vsync)
plugged in after boot: ADPA: 0x40008c18 (disabled, pipe B, +hsync, +vsync)

so far, so good. The VGA output in the first case is enabled and in VGA mode (for text mode probably). And in the second case it's disabled in VGA mode, with DPMS indicating that the monitor is off.

Now once the server starts and programs things, they go bad:
plugged in before boot: ADPA: 0x80000018 (enabled, pipe A, +hsync, +vsync)
plugged in after boot: ADPA: 0x80000000 (enabled, pipe A, -hsync, -vsync)

the first case looks ok, VGA mode just gets disabled, but otherwise the output looks ok. In the second case though it looks like we get the wrong polarity for the mode for some reason. You're not providing any custom modelines are you? Can you try adding one with xrandr that has positive polarity?

Also, can you make sure your machine's ACPI DOS setting (somewhere in /proc/acpi/video) is 2, 3, 6 or 7?