I've just tried kernel 2.6.37-997.201101081429 (from drm-intel-next) and it boots to a blank screen. Switching to a VT and back does not help. In the build.log file we read:
It's normal to receive one or two of these during mode setting activity,
so just make the output debug only. We can change this in the future if
we ever make our training sequences interrupt driven and properly handle
the various types of interrupts.
I've just tried kernel 2.6.37- 997.20110108142 9 (from drm-intel-next) and it boots to a blank screen. Switching to a VT and back does not help. In the build.log file we read:
commit fbf4b94f7d01550 799ff7669c65ebb 0c053e015c
Author: Jesse Barnes <email address hidden>
Date: Fri Jan 7 10:24:43 2011 -0800
drm/i915: make FDI interrupt info debug only
It's normal to receive one or two of these during mode setting activity,
so just make the output debug only. We can change this in the future if
we ever make our training sequences interrupt driven and properly handle
the various types of interrupts.