https://bugs.freedesktop.org/show_bug.cgi?id=56461

--- Comment #24 from Chris Paulson-Ellis <ch...@edesix.com> ---
(In reply to comment #23)
> This is probably another bug (you are really lucky ;).

I will bisect again. Don't hold your breath!

> Is timer/nv04.c change needed for 2a44e499 to light up your monitor?

No. I'm only using it when running the patched nouveau git HEAD. Even then I
can leave it out without anything changing - It just suppresses this warning:
nouveau W[  PTIMER][0000:01:00.0] unknown input clock freq

When running the patched git HEAD... Although the LCD is not being driven, the
driver isn't completely dead. I can start and stop X and the screen will go
white, then fade to black each time I do it. This suggests that the backlight
control & power management are okay, but the display timings are wrong. Looking
at the working & broken console output, they both show the same pixel clock. Is
there some way to get the driver to output more verbose display timing info
(fbset -i shows all zeros in the timing line in both the working & non-working
cases)?

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

Reply via email to