[Pm-utils] Problems with 98smart-kernel-video and intel graphics chipsets
victor.lowther at gmail.com
Sat Sep 20 10:30:59 PDT 2008
On Sat, 2008-09-20 at 08:28 -0700, Dan Nicholson wrote:
> On Sat, Sep 20, 2008 at 6:50 AM, Victor Lowther
> <victor.lowther at gmail.com> wrote:
> > On Fri, 2008-09-19 at 21:03 +0200, Michael Biebl wrote:
> >> Can someone with more knowledge about intel hardware and its kernel
> >> modesetting driver please comment on the current status of this driver
> >> with regard to quirk handling and which one should be applied or
> >> filtered out.
> > We will probably have to annoy the driver developers directly.
> > I suspect that the Intel driver will ultimatly still require the s3 and
> > the vbe post, state, and mode quirks.
> That will definitely not be necessary when all is said and done. A
> major driving factor of getting the modesetting done in the kernel was
> so it would stand a better chance to handle suspend and resume. A
> definite goal in all that is that banging the BIOS will not be
> necessary and the card can be reprogrammed directly.
> I read that the Intel kernel modesetting driver is lacking
> suspend/resume support right now.
> That being said, nobody except Fedora users even have the kernel
> modesetting drivers yet. The disabling of quirks in smart-video was
> supposed to be taking advantage of fixes in the DRM i915 driver that
> went in to 2.6.26.
Hmmm... do you have an idea of what, exactly, those fixes were?
I mean, at this point it looks like they helped some quirks but had no
effect on the applicability of others. Given that, it seems like the
best bet for me would be to reenable the s3 and vbe quirks for Intel
until it is widely know that the quirks are, in fact, no longer required
for Intel hardware using kernel drivers.
> I'm pretty sure the current DRM driver is supposed to be handling
> suspend/resume correctly and any issues should be considered a bug.
> Whether you want to file those or just continue to work around them by
> using vbetool, I don't know. See this bug, for instance.
Yeah, that is the same class of bug that I ended up releasing 126.96.36.199
for. The workaround for him after upgrading to 2.6.26 final (which
still exhibited the same failure) was to allow the s3 quirks to still
take effect if the quirk list said they were needed for Intel video.
There was another system that had a bug reported to the fd.o bugtracker
that has the same resolution.
I suspect the that i915 driver is handling suspend/resume correctly for
issues it can be aware of (programming the backlights, resetting modes,
etc), but the stuff we end up handling via quirks tends to be system
Ubuntu Certified Professional
More information about the Pm-utils