[i855] (Needs intel 2.10) No Xv support for 82852/855GM (KMS bug)

[Baard Johansen]

Binary package hint: xserver-xorg-video-intel

After upgrading to Karmic (alpha) my graphics driver is unable to provide Xv. The following line is printed in Xorg.0.log:

(WW) intel(0): Disabling Xv because no adaptors could be initialized.

I've tried various settings in xorg.conf, with no luck. (XvPreferOverlay, Tiling).

[Update]

From the Q4 anouncment [1]:
Video overlay support with KMS is now supported in xserver-xorg-video-intel 2.10.0. This currently requires Linux 2.6.33, but a backport to 2.6.32 (Lucid version) is available from [2]. Daniel Vetter intends to support this backport which is intended for distros that use kernel 2.6.32 [3]. Although the main code is in the kernel, intel driver 2.10.0 is apparently required [4].

[1]: http://intellinuxgraphics.org/2009Q4.html
[2]: http://gitorious.org/daniel-s-linux-stuff/linux-kernel/commits/intel-kms-overlay-for-2.6.32
[3]: http://lists.freedesktop.org/archives/intel-gfx/2010-January/005372.html
[4]: https://bugs.freedesktop.org/show_bug.cgi?id=20901#c42

[lspci]
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
     Subsystem: Acer Incorporated [ALI] Device 0035
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
     Subsystem: Acer Incorporated [ALI] Device 0035

[Julien Cristau (jcristau)]

*** Bug 21510 has been marked as a duplicate of this bug. ***

[unggnu (unggnu)]

I can confirm this behavior with i915.
This is important until Bug 20664 is fixed. If textured video works without tearing and has no performance issues there is no need for Overlay.

[Julien Cristau (jcristau)]

> --- Comment #2 from <email address hidden> 2009-05-03 08:03:42 PST ---
> I can confirm this behavior with i915.
> This is important until Bug 20664 is fixed. If textured video works without
> tearing and has no performance issues there is no need for Overlay.

wrong. i8xx has no textured video.

[unggnu (unggnu)]

Right, guess which card support will be dropped next ;)

[unggnu (unggnu)]

Any news from the devs on this issue?

[Baard Johansen (baard)]

Binary package hint: xserver-xorg-video-intel

After upgrading to Karmic (alpha) my graphics driver is unable to provide Xv. The following line is printed in Xorg.0.log:

(WW) intel(0): Disabling Xv because no adaptors could be initialized.

I've tried various settings in xorg.conf, with no luck. (XvPreferOverlay, Tiling).

[Geir Ove Myhr (gomyhr)]

Could you please run `apport-collect 395923` on your machine, so that we get the various logs that are useful for troubleshooting and reporting upstream?

[Baard Johansen (baard)]

I think you typed the wrong bug-number above. However, apport-collect fails with:

$ apport-collect 395932
Logging into Launchpad...
Downloading bug...
Bug title: No Xv support for 82852/855GM in Karmic
Collecting apport information for source package xserver-xorg-video-intel...
Uploading additional information to Launchpad bug...
   short text data...
Traceback (most recent call last):
  File "/usr/bin/apport-collect", line 145, in <module>
    upload(report, bug)
  File "/usr/bin/apport-collect", line 52, in upload
    subject='apport-collect data')
  File "/usr/lib/python2.6/dist-packages/launchpadlib/resource.py", line 337, in __call__
    args[key] = simplejson.dumps(value, cls=DatetimeJSONEncoder)
  File "/usr/lib/pymodules/python2.6/simplejson/__init__.py", line 237, in dumps
    **kw).encode(obj)
  File "/usr/lib/pymodules/python2.6/simplejson/encoder.py", line 194, in encode
    return encode_basestring_ascii(o)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xff in position 911: unexpected code byte

[Baard Johansen (baard)]

I would also like to add that Xv is enabled with the alpha 2 release, but stopped working after upgrading the system after installation. Attaching the Xorg-log from before the upgrade, in case this helps.

[Geir Ove Myhr (gomyhr)]

Thank you! It is very useful to know that it worked with alpha 2 before upgrades. The one major change I can think of after alpha 2 is that kernel modesetting (KMS) has been enabled in the kernel. Could you try to disable KMS on an upgraded Karmic to see if KMS is the culprit? To do that, add the following kernel parameter on boot (by pressing E on the GRUB boot menu IIRC): i915.modeset=0

More information about the addition of KMS in ubuntu:
https://lists.ubuntu.com/archives/ubuntu-x/2009-June/000578.html

Xorg.0.log from the test would be appreciated.

[Geir Ove Myhr (gomyhr)]

Btw, I think you can also enable KMS with i915.modeset=1 on alpha-2 if you haven't upgraded yet, and see if it causes the problem.

[Baard Johansen (baard)]

The problem is gone when KMS is disabled. I've already upgraded, but I can reinstall if that will provide you with much extra info.

[Geir Ove Myhr (gomyhr)]

> The problem is gone when KMS is disabled. I've already upgraded, but I can reinstall if that will provide you with much extra info.

That shouldn't be necessary.

It would probably be nice to have the output of `xvinfo` both with and without KMS. Also, are you on 32-bit or 64-bit?

With that information I think this is more or less ready to go upstream. If you feel that you are up to it, you can do it yourself. Otherwise I can put together a report once time permits. Instructions (and a template) for filing a bug upstream is at http://intellinuxgraphics.org/how_to_report_bug.html .

[Geir Ove Myhr (gomyhr)]

Actually, would you mind reporting the apport-collect problem as a bug as well? I suspect the output would actually mean something useful to the developer.

[unggnu (unggnu)]

Textured video works better than before but it still tears in some parts with an i915.

So what is the status of this issue?

[Gordon Jin (gordon-jin)]

*** Bug 22978 has been marked as a duplicate of this bug. ***

[Bryce Harrington (bryce)]

Hi Baard,

I've forwarded your bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=22978 - please subscribe to this bug in case upstream needs further information or wishes you to test something. Thanks ahead of time.

[Baard Johansen (baard)]

Why has this been marked as "Invalid"? Is it because the bug at freedesktop.org has been marked as a duplicate? Shouldn't this bug be marked as duplicate instead?

[Timo Aaltonen (tjaalton)]

the upstream bug was marked as invalid, not the ubuntu one. Updating the url.

[lannyboy (jincool)]

i also encountered the same problem -> No Xv support for 82852/855GM. there is no luck i could just enable it even i tried lines at xorg.conf.

(WW) intel(0): Disabling Xv because no adaptors could be initialized.

i am a using fedora 11.

[Diego-abelenda (diego-abelenda)]

I am really interested in the video overlay as I own a 865GM

00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02)

That works out of the box with KMS but no textured video so... no Xv...

[Daniel-ffwll (daniel-ffwll)]

I've posted my latest work on porting the overlay to kms to <email address hidden>. I'm really interested in test-reports because I have just a 855GM to develop on. I'll upload my latest patches against kernel and ddx on this bug report, too.

Thx for all reports, Daniel

[Daniel-ffwll (daniel-ffwll)]

Created an attachment (id=28587)
patch for ddx

Apply to latest xf86-video-intel git master. To compile you need the
new ioctl definitions from the kernel.

[Daniel-ffwll (daniel-ffwll)]

Created an attachment (id=28588)
patch for ddx

this time the actual patch, not just the log ...

[Daniel-ffwll (daniel-ffwll)]

Created an attachment (id=28589)
patch for kernel

patch is against latest -linus (I'm using 2.6.31-rc5-gitsomething).

To install the new userspace headers do:

$ make install

Then copy usr/include/drm/i915.h someplace where it can be included by the ddx
(quick&dirty: overwrite the system header in /usr/include/drm)

[Diego-abelenda (diego-abelenda)]

well... I just tested the patches and after that the video overlay is detected, I can play videos with mplayer using it, but can't put them in fullscreen, I just get a blue screen and mplayer spams this :

X11 error: BadAlloc (insufficient resources for operation)

so there might be a problem somewhere. There is no error nor warnings in the kernel, the Xorg.log or anywhere else than the output of mplayer.

xvinfo has a promising output:

X-Video Extension version 2.2
screen #0
  Adaptor #0: "Intel(R) Video Overlay"
    number of ports: 1
    port base: 72
    operations supported: PutImage
    supported visuals:
      depth 24, visualID 0x21
    number of attributes: 5
      "XV_COLORKEY" (range 0 to 16777215)
              client settable attribute
              client gettable attribute (current value is 66046)
      "XV_BRIGHTNESS" (range -128 to 127)
              client settable attribute
              client gettable attribute (current value is -19)
      "XV_CONTRAST" (range 0 to 255)
              client settable attribute
              client gettable attribute (current value is 75)
      "XV_SATURATION" (range 0 to 1023)
              client settable attribute
              client gettable attribute (current value is 146)
      "XV_PIPE" (range -1 to 1)
              client settable attribute
              client gettable attribute (current value is -1)
    maximum XvImage size: 2048 x 2048
    Number of image formats: 5
      id: 0x32595559 (YUY2)
        guid: 59555932-0000-0010-8000-00aa00389b71
        bits per pixel: 16
        number of planes: 1
        type: YUV (packed)
      id: 0x32315659 (YV12)
        guid: 59563132-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)
      id: 0x30323449 (I420)
        guid: 49343230-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)
      id: 0x59565955 (UYVY)
        guid: 55595659-0000-0010-8000-00aa00389b71
        bits per pixel: 16
        number of planes: 1
        type: YUV (packed)
      id: 0x434d5658 (XVMC)
        guid: 58564d43-0000-0010-8000-00aa00389b71
        bits per pixel: 12
        number of planes: 3
        type: YUV (planar)

So I think there might be just a little thing missing to make it work, unfortunately I don't know anything about the intel driver to begin the debug. My card :

00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company D530 sff(dc578av) [103c:12bc]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Region 1: Memory at fc400000 (32-bit, non-prefetchable) [size=512K]
        Region 2: I/O ports at 24e0 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [d0] Power ...

[Daniel-ffwll (daniel-ffwll)]

Created an attachment (id=28615)
patch for kernel

this should fix the fullscreen issue.

[Daniel-ffwll (daniel-ffwll)]

On Thu, Aug 13, 2009 at 02:35:30PM -0700, <email address hidden> wrote:
> --- Comment #13 from <email address hidden> 2009-08-13 14:35:29 PST ---
> well... I just tested the patches and after that the video overlay is detected,
> I can play videos with mplayer using it, but can't put them in fullscreen, I
> just get a blue screen and mplayer spams this :
>
> X11 error: BadAlloc (insufficient resources for operation)
>
> so there might be a problem somewhere. There is no error nor warnings in the
> kernel, the Xorg.log or anywhere else than the output of mplayer.

Thanks for testing. I've already fixed the fullscreen issue (it's a
over-eager test in the kernel due to a misconception on my side). I must
have sent out a stale version of the patches. I'll redo them.

One important question: Have you noticed any visual corruptions like
flickering (I have them here on my 855GM) on your 865G? That's the last
problem known to me and having a better picture of which chip revs are
affected may help.

Thanks, Daniel

[Diego-abelenda (diego-abelenda)]

Thanks for your fast work. Now fullscreen works ^^

I had seen pretty bad corruption (1/4 of the screen goes green or displays a part of the video it shouldn't) when I changed the resolution to a lower one, I get a slight one at native resolution (only some lines that appear and disappear, I didn't see it when the full screen wasn't there as it is very small, but now that I can go to fullscreen I can see it).

[Daniel-ffwll (daniel-ffwll)]

> --- Comment #16 from <email address hidden> 2009-08-14 02:37:00 PST ---
> Thanks for your fast work. Now fullscreen works ^^

Good, thanks for testing.

> I had seen pretty bad corruption (1/4 of the screen goes green or displays a
> part of the video it shouldn't) when I changed the resolution to a lower one, I
> get a slight one at native resolution (only some lines that appear and
> disappear, I didn't see it when the full screen wasn't there as it is very
> small, but now that I can go to fullscreen I can see it).

At native resolution, when you stop the video, do the corruptions (slowly)
disappear? Some mouse-moving moving around of other windows may help (does
at least here). Just to make sure we're seeing the same type of
corruption.

About the reduced resolution issue: You may be hitting the completely
untested one-line-mode code. Can you post the output of

$ xrandr

when this happens? Or does the corruption disappear, when you stop the
video (like above)?

-Daniel

[Diego-abelenda (diego-abelenda)]

The corruption only affects the video nothing else.

Ah, the heavy corruption at lower resolution was probably the same issue as the missing fullscreen, it has disappeared.

Now the only remaining corruption are the lines that appear, and it seems dependent on the resolution of the video, the lesser the resolution it is the greater the number of lines. (I got a few lines with a 720p video and a lot with a 640x480 one), they appear and disappear just like if it were a refresh problem.

my xrandr output :

Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 2048 x 2048
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 410mm x 256mm
   1680x1050 59.9*+
   1280x1024 75.0
   1360x768 60.0
   1024x768 75.1 70.1 60.0
   800x600 72.2 75.0 60.3
   640x480 72.8 75.0 60.0
   720x400 70.1

[dentaku65 (dentaku65)]

I can confirm this issue with Karmic Alpha 4
VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
My workaround is to use "nomodeset" at grub boot in order to do not use KMS

[Gordon Jin (gordon-jin)]

Daniel, thanks for the patch.

Jesse, could you review and consider commit?

[Daniel-ffwll (daniel-ffwll)]

On Mon, Aug 31, 2009 at 08:03:22PM -0700, <email address hidden> wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=20901
> --- Comment #19 from Gordon Jin <email address hidden> 2009-08-31 20:03:21 PST ---
> Daniel, thanks for the patch.
>
> Jesse, could you review and consider commit?
Just fyi, there's an ongoing discussion on dri-devel about the right
kernel-userspace interface of this whole thing.

-Daniel

[Michal Nowak (newman)]

Any progress?

[Daniel-ffwll (daniel-ffwll)]

On Sat, Sep 05, 2009 at 04:03:26AM -0700, <email address hidden> wrote:
> --- Comment #21 from Michal Nowak <email address hidden> 2009-09-05 04:03:25 PST ---
> Any progress?

Not really. There's still the bandwidth/watermaking bug (besides that, it
works). But I can't fix that because I don't have the docs (and I've
already tried all odd things that popped up while scanning through the ums
driver). So until someone at intel picks this up/reviews it, it's
unfortunately stalled.

-Daniel

[Jesse Barnes (jbarnes-virtuousgeek)]

Daniel, on your 855 what's the FW_BLC reg when you see the flicker? The overlay FIFO should be controlled by the display plane C bits in that reg; maybe we have a bad watermark or burst size selected.

[Daniel-ffwll (daniel-ffwll)]

On Tue, Sep 08, 2009 at 09:44:33AM -0700, <email address hidden> wrote:
> --- Comment #23 from Jesse Barnes <email address hidden> 2009-09-08 09:44:31 PST ---
> Daniel, on your 855 what's the FW_BLC reg when you see the flicker? The
> overlay FIFO should be controlled by the display plane C bits in that reg;
> maybe we have a bad watermark or burst size selected.

I've already mucked around with FW_BLC and DSPARB values (there are some
small differences to the userspace driver), but turned up nothing. Anyway,
here are the values:

[ 181.323475] DSPARB: 15455
[ 181.323481] watermarks: FW_BLC: 1070128, FW_BLC2: 102

This is on latest git with drm-next (including latest intel stuff) merged
in. Unfortunately the flickering is still there. Below patch created this
output (the i915_regs stuff in drm-next hung my machine so I couldn't use
it).

diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 444cf8c..7f594a1 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -2107,6 +2107,8 @@ static int intel_get_fifo_size(struct drm_device *dev, int plane)
  struct drm_i915_private *dev_priv = dev->dev_private;
  uint32_t dsparb = I915_READ(DSPARB);
  int size;
+
+ printk("DSPARB: %x\n", dsparb);

  if (IS_I9XX(dev)) {
   if (plane == 0)
@@ -2229,6 +2231,8 @@ static void i9xx_update_wm(struct drm_device *dev, int planea_clock,

  I915_WRITE(FW_BLC, fwater_lo);
  I915_WRITE(FW_BLC2, fwater_hi);
+
+ printk("watermarks: FW_BLC: %x, FW_BLC2: %x\n", I915_READ(FW_BLC), I915_READ(FW_BLC2));
 }

 static void i830_update_wm(struct drm_device *dev, int planea_clock,

[Jesse Barnes (jbarnes-virtuousgeek)]

Well, BLC2 does seem to have a low burst length:

42:40: display plane c burst length
  000 - 4
  001 - 8
  010 - 12
  011 - 16
  100 - 20
  101 - 24
  110 - 28
  111 - 32

36:32: display plane c watermark (fetches start when this many or more entries are available in the FIFO), in 32 byte units
  00000 = 32 bytes

The default is 0x307 for this reg... If increasing the burst length doesn't help, maybe it's not a FIFO issue?

[Daniel-ffwll (daniel-ffwll)]

On Tue, Sep 08, 2009 at 06:21:14PM -0700, <email address hidden> wrote:
> --- Comment #25 from Jesse Barnes <email address hidden> 2009-09-08 18:21:11 PST ---
> Well, BLC2 does seem to have a low burst length:
>
> 42:40: display plane c burst length
> 000 - 4
> 001 - 8
> 010 - 12
> 011 - 16
> 100 - 20
> 101 - 24
> 110 - 28
> 111 - 32
>
> 36:32: display plane c watermark (fetches start when this many or more entries
> are available in the FIFO), in 32 byte units
> 00000 = 32 bytes
>
> The default is 0x307 for this reg... If increasing the burst length doesn't
> help, maybe it's not a FIFO issue?

I've tried 0x302 and 0x702 as values for FW_BLC2, but nothing really
changed. Previously I've copied the ums driver behaviour of not setting
anything (i.3. default value = 0x307), but that didn't help, either.

Still, the visual corruptions are nicely aligned, so it looks like the
some cacheline loads are too late. To other very puzzling thing is that
corruptions disappaer after a few secs, as long as no overlay flip is
being issued in the mean time. And the disappear in a very peculiar way,
namely cacheline by cacheline, i.e. I haven't ever seen new corruptions
pop up. Furthermore, when the image is clear, it stays that way (as long
as it does not get redrawn), i.e. even with cpu/gpu load there are no
further corruptions.

Thanks, Daniel

[Jesse Barnes (jbarnes-virtuousgeek)]

On Wed, 9 Sep 2009 06:02:34 -0700 (PDT)
<email address hidden> wrote:

> http://bugs.freedesktop.org/show_bug.cgi?id=20901
>
>
>
>
>
> --- Comment #26 from Daniel Vetter <email address hidden> 2009-09-09
> 06:02:33 PST --- On Tue, Sep 08, 2009 at 06:21:14PM -0700,
> <email address hidden> wrote:
> > --- Comment #25 from Jesse Barnes <email address hidden>
> > 2009-09-08 18:21:11 PST --- Well, BLC2 does seem to have a low
> > burst length:
> >
> > 42:40: display plane c burst length
> > 000 - 4
> > 001 - 8
> > 010 - 12
> > 011 - 16
> > 100 - 20
> > 101 - 24
> > 110 - 28
> > 111 - 32
> >
> > 36:32: display plane c watermark (fetches start when this many or
> > more entries are available in the FIFO), in 32 byte units
> > 00000 = 32 bytes
> >
> > The default is 0x307 for this reg... If increasing the burst
> > length doesn't help, maybe it's not a FIFO issue?
>
> I've tried 0x302 and 0x702 as values for FW_BLC2, but nothing really
> changed. Previously I've copied the ums driver behaviour of not
> setting anything (i.3. default value = 0x307), but that didn't help,
> either.
>
> Still, the visual corruptions are nicely aligned, so it looks like the
> some cacheline loads are too late. To other very puzzling thing is
> that corruptions disappaer after a few secs, as long as no overlay
> flip is being issued in the mean time. And the disappear in a very
> peculiar way, namely cacheline by cacheline, i.e. I haven't ever seen
> new corruptions pop up. Furthermore, when the image is clear, it
> stays that way (as long as it does not get redrawn), i.e. even with
> cpu/gpu load there are no further corruptions.

Ah ok, that sounds like it may cache flush related then. I remember
seeing something similar in the early KMS work. I was mapping the
framebuffer through the GTT, but I hadn't done a GTT domain transition
on it yet, so over time I had lots of cacheline sized writes to the
screen until things had finally flushed out of the CPU. Maybe you're
missing a similar domain transition in your code?

[Daniel-ffwll (daniel-ffwll)]

On Wed, Sep 09, 2009 at 09:41:55AM -0700, <email address hidden> wrote:
> Ah ok, that sounds like it may cache flush related then. I remember
> seeing something similar in the early KMS work. I was mapping the
> framebuffer through the GTT, but I hadn't done a GTT domain transition
> on it yet, so over time I had lots of cacheline sized writes to the
> screen until things had finally flushed out of the CPU. Maybe you're
> missing a similar domain transition in your code?

Thanks alot for the hint, Jesse. I indeed forgot a set_gtt_domain call.
Everything seems to work now. I'll update the patch (I'd like to decouple
the gpu and cpu, atm the running in lockstep for testing purposes) and
resen for testing. Do you think the kernel side of this series could still
be merged into .32?

Thanks, Daniel

[Jesse Barnes (jbarnes-virtuousgeek)]

(In reply to comment #28)
> Thanks alot for the hint, Jesse. I indeed forgot a set_gtt_domain call.
> Everything seems to work now. I'll update the patch (I'd like to decouple
> the gpu and cpu, atm the running in lockstep for testing purposes) and
> resen for testing. Do you think the kernel side of this series could still
> be merged into .32?

Great! Yeah, I'm hoping this can land in .32. I'll review the next set you post.

[Daniel-ffwll (daniel-ffwll)]

Created an attachment (id=29397)
patch for kernel

This is the latest version with the cache-flushing fixed. Recompiling the userspace part is not necessary. Please test, thanks.

Jesse, I'll repost the split-up patch series tomorrow.

-Daniel

[Diego-abelenda (diego-abelenda)]

I just patched the 2.6.31 release with the new kernel patch, it works great, the video corruption is nearly entirely gone, now I have only a "hole" in the video from time to time : 1/6 of the lines are black instead of displaying the video during 1-2 frames, but it's far better than before thank you.

[Daniel-ffwll (daniel-ffwll)]

On Fri, Sep 11, 2009 at 03:07:40AM -0700, <email address hidden> wrote:
> --- Comment #31 from <email address hidden> 2009-09-11 03:07:38 PST ---
> I just patched the 2.6.31 release with the new kernel patch, it works great,
> the video corruption is nearly entirely gone, now I have only a "hole" in the
> video from time to time : 1/6 of the lines are black instead of displaying the
> video during 1-2 frames, but it's far better than before thank you.

Are you using a compositing window manager? If so, can you please test
wheter it works when turning compositin off (perhaps just run a failsafe
session)? I'm experiencing similar issues when using compositioning as you
described.

-Daniel

[Diego-abelenda (diego-abelenda)]

I don't use composition.

[Daniel-ffwll (daniel-ffwll)]

On Fri, Sep 11, 2009 at 04:20:40AM -0700, <email address hidden> wrote:
> --- Comment #33 from <email address hidden> 2009-09-11 04:20:38 PST ---
> I don't use composition.
Ok. Next idea: What video player are you using? Can you test a different
one? xvtest is nice for _very_ basic xv testing (<space> switches colors,
v draws a gradient).

git clone git://anongit.freedesktop.org/~keithp/xvtest

I've got an idea what might be causing this. But some more testing first
would be nice.

-Daniel

[Diego-abelenda (diego-abelenda)]

Oh interesting, as soon as I move its window I cannot switch vt anymore : chvt would just stay there and do nothing, I had to kill it to regain access to the shell, same for xrandr, it became impossible to terminate X in a normal way, even SIGTERM failed, I had to send SIGKILL to it, but all remained the same way so I had to reboot.

I played a little with the default size of the window overlay in xvtest (the #define DEFAULT_WIDTH and DEFAULT_HEIGHT), putting some values beside the default 256x256 (which seems to work no problem).

I discovered that the program causes the screen to be corrupted at many (nearly all ?) other sizes, and I even made it segfault by putting 1600x900 and this segfault made KMS quite angry again, but this time It refused to display anything, black screen nothing else. The same happens if I press "v", the first time it displays a nice color gradient the second time black screen.

No error message in the kernel or X logs.

btw I use mplayer version 1.0_rc2_p20090731-r1 and nothing like that happens.

[Daniel-ffwll (daniel-ffwll)]

> --- Comment #35 from <email address hidden> 2009-09-12 07:02:48 PST ---
Thanks for testing. I'm sorry for this tedious back-and-forth
trial-and-error testing. I've rebased my work onto drm-intel-next and I'm
now exprience similar problems as you described below. I'm working on a
fix, but it needs some more testing.

I've also got an idea on how to fix can't-kill-X-anymore issue (at least
for the common case), but that needs some more time.

> Oh interesting, as soon as I move its window I cannot switch vt anymore : chvt
> would just stay there and do nothing, I had to kill it to regain access to the
> shell, same for xrandr, it became impossible to terminate X in a normal way,
> even SIGTERM failed, I had to send SIGKILL to it, but all remained the same way
> so I had to reboot.
>
> I played a little with the default size of the window overlay in xvtest (the
> #define DEFAULT_WIDTH and DEFAULT_HEIGHT), putting some values beside the
> default 256x256 (which seems to work no problem).
>
> I discovered that the program causes the screen to be corrupted at many (nearly
> all ?) other sizes, and I even made it segfault by putting 1600x900 and this
> segfault made KMS quite angry again, but this time It refused to display
> anything, black screen nothing else. The same happens if I press "v", the first
> time it displays a nice color gradient the second time black screen.
>
> No error message in the kernel or X logs.
>
>
> btw I use mplayer version 1.0_rc2_p20090731-r1 and nothing like that happens.

But the occasional black stripe is still there?

-Daniel

[Daniel-ffwll (daniel-ffwll)]

Created an attachment (id=29518)
patch for ddx

As promised the new kernel patch with the wc-cache flushing fix. This survived one hour of scripted stress-testing on my box. Neither the ums xorg driver nor any of my previous patches managed to do this, so it looks quite solid.

To test apply this on top of the drm-intel-next branch of

git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel

This tree contains another cache flushing fix for i8xx hw by Eric.

Thx, Daniel

[Beni Cherniavsky (cben)]

Also affects me with 945GME on Karmic (latest packages as of 2009-09-21, 2.6.31-10-generic kernel).
Worked before upgrade on Jaunty.

VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)

Problem went away when I added "i915.modeset=0 nomodeset" to kernel command line.
Will try to apport-collect.

P.S. dmesg includes the line:

[ 0.000000] Unknown boot option `i915.modeset=0': ignoring

so it's probably "nomodeset" that does the trick.

[Beni Cherniavsky (cben)]

Architecture: i386
DistroRelease: Ubuntu 9.10
MachineType: MICRO-STAR INTERNATIONAL CO., LTD U-100
Package: xserver-xorg-video-intel 2:2.8.1-1ubuntu1
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=e504864a-886a-4364-9c22-df8ce1944e03 ro quiet splash i915.modeset=0 nomodeset
ProcEnviron:
 LANGUAGE=es_ES.UTF-8
 LANG=es_ES.UTF-8
 SHELL=/usr/bin/fish
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu4
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
Tags: ubuntu-unr
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo
dmi.bios.date: 07/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: U-100
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: Ver.001
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.version: Ver.001
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd07/16/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:
dmi.product.name: U-100
dmi.product.version: Ver.001
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-10-generic

[Pedro Saraiva (pedro-a34195)]

Architecture: i386
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer TravelMate 2300
Package: xserver-xorg-video-intel 2:2.8.1-1ubuntu2
PackageArchitecture: i386
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=859fda5e-c8a5-425b-8d4c-9d4c646aa1cb ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=pt_PT.UTF-8
 LANGUAGE=pt_PT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu6
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
XorgLogOld: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log.old'
dmi.bios.date: 08/03/2004
dmi.bios.vendor: ACER
dmi.bios.version: 3A07
dmi.board.name: TravelMate 2300
dmi.board.vendor: Acer
dmi.board.version: Rev 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Rev.1
dmi.modalias: dmi:bvnACER:bvr3A07:bd08/03/2004:svnAcer:pnTravelMate2300:pvrRev1:rvnAcer:rnTravelMate2300:rvrRev1.0:cvnAcer:ct10:cvrRev.1:
dmi.product.name: TravelMate 2300
dmi.product.version: Rev 1
dmi.sys.vendor: Acer
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-11-generic

[Bryce Harrington (bryce)]

Upstream created a kernel patch to solve this issue, so reassigning to linux.

[Matteo Settenvini (tchernobog)]

I can't play any video without many frames skipping. This makes Ubuntu unusable to watch any video with e.g. Totem or Mplayer. Thus, nominating for fixing it before Karmic final.

@Bryce: could you please provide a link to the patch, so we can evaluate it? Thanks.

[Jesse Barnes (jbarnes-virtuousgeek)]

Eric will be pulling this in shortly...

[Matteo Settenvini (tchernobog)]

Something happened with the updates I did today (it was a couple of days I didn't update, say from Friday).
Now I supposedly have xvideo support (see attached output of xvinfo, until yesterday it gave me "No adapters present"), however things got worse!

The whole system is mostly unusable: using Firefox or other applications (like Deluge or gedit, don't ask me why) brings the cpu to 100%. Browsing to a new page takes 10-15 seconds. Let's not mention opening a file chooser dialog!
Looking with "top" shows Xorg being the culprit: all windows redrawing are painfully slow.

I believe that this fix or another related fix brought us xvideo support, but for some reason the allocated area is wrong. If I try to launch totem, it always crashes with:

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 94 error_code 11 request_code 132 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Mplayer shows a blue screen, and prints a long list of:

VO: [xv] 1024x768 => 1024x768 Planar YV12 [fs]
X11 error: BadAlloc (insufficient resources for operation)0.6% 1 0
X11 error: BadAlloc (insufficient resources for operation)

[Matteo Settenvini (tchernobog)]

Attaching my Xorg.0.log. A lot of errors related to drm not initializing (bad file descriptor), unable to initialize kernel memory manager, and "pinning" xv (no idea what it means) are present.

[Michal Nowak (newman)]

(In reply to comment #38)
> Eric will be pulling this in shortly...

Cool! Thanks everyone involved.

[Matteo Settenvini (tchernobog)]

With today update of the linux kernel (to version 2.6.31.12.23), things reverted back to the situation of having no xvideo support, but at least the system is usable again.

[Pedro Saraiva (pedro-a34195)]

Is the patch already applied on todays xserver-xorg-video-intel update?
I'm still getting:
intel(0): Intel XvMC decoder disabled
(WW) intel(0): Disabling Xv because no adaptors could be initialized.

[Leann Ogasawara (leannogasawara)]

The patch for the kernel is currently in drm-intel-next and not yet merged into Linus' tree nor in Karmic. This will likely be available in Lucid.

ogasawara@emiko:~/drm-intel$ git show 9871afa47454b409473d306f2db48ac736938314
commit 9871afa47454b409473d306f2db48ac736938314
Author: Daniel Vetter <email address hidden>
Date: Tue Sep 15 22:57:34 2009 +0200

    drm/i915: implement drmmode overlay support v4

[Matteo Settenvini (tchernobog)]

So, what's the proper fix for karmic? I can't watch any video without it stuttering and the CPU going to 100%... DVD are absolutely unwatchable.

I made three different installations of jaunty this week, and all three have an Intel 82852/855GM. It may be a coincidence, but at least here in Italy for laptops bought in the years 2003-2007 it's a fairly common integrated video card.

Expect some complaining from users that update to karmic with this bug still unsolved...

[Pedro Saraiva (pedro-a34195)]

The fix is disable kernel mode setting... Put "nomodeset" in the kernel boot
options in grub config file.
Or compile your own kernel and patch it, witch I'll do when I've time...

2009/10/16 Matteo Settenvini <email address hidden>

> So, what's the proper fix for karmic? I can't watch any video without it
> stuttering and the CPU going to 100%... DVD are absolutely unwatchable.
>
> I made three different installations of jaunty this week, and all three
> have an Intel 82852/855GM. It may be a coincidence, but at least here in
> Italy for laptops bought in the years 2003-2007 it's a fairly common
> integrated video card.
>
> Expect some complaining from users that update to karmic with this bug
> still unsolved...
>
> --
> [i855] No Xv support for 82852/855GM (KMS bug)
> https://bugs.launchpad.net/bugs/395932
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Geir Ove Myhr (gomyhr)]

This should go into the release notes of Karmic. Mentioning that Xv (accelerated video playback) does not work on this chipset and that the workaround is to turn off KMS.

[Matteo Settenvini (tchernobog)]

Thanks Pedro. That works for me.

On a side note, what about a small kludge for karmic:

the intel-driver package could install a 09_i810_karmic_fix file in /etc/grub.d reading like:

if [ ! -z "$(lspci | grep 'VGA compatible' | grep '82852/855GM')" ];
  then GRUB_CMDLINE_LINUX="${GRUB_CMDLINE_LINUX} nomodeset";
fi

That would make users happy, would be easy to remove upon transition to lucid or when this bug gets fixed, and would require no further modifications to the release notes. Plus, it would not require user manual intervention (I would have problems to have my girlfriend or dad firing up a console and searching for the grub settings...).

Anyway, if it's too ugly, just disregard this post.

[Steve Langasek (vorlon)]

Documented at <https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes#No%20Xv%20support%20for%20Intel%2082852/855GM%20video%20chips%20with%20KMS>:

When using the default kernel-mode-setting (KMS) option in Ubuntu 9.10, users with Intel 82852/855GM cards will find that they are unable to use the Xv extension for playing videos. This may show up as high CPU usage or stuttering during video playback, or a failure to play videos at all with some applications. As a workaround, users can add the option nomodeset to the kernel boot options in the grub config, to disable the use of KMS. (395932)

[Imi (imrandotuk)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: imran 1419 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
CheckboxSubmission: 4705d679914455604e81fb76abf6b3e2
CheckboxSystem: b1cca5f799a911bbb44e7180c2fd235d
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=596bff38-9913-41e1-9948-cb28dac3eec9
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 23733JG
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: root=UUID=5a0f453c-1464-4094-8353-fd595f147aba ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: tpacpi_bluetooth_sw: Bluetooth
  Soft blocked: yes
  Hard blocked: no
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video
WpaSupplicantLog:

dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 23733JG
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn23733JG:pvrThinkPadT41:rvnIBM:rn23733JG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 23733JG
dmi.product.version: ThinkPad T41
dmi.sys.vendor: IBM

[Previr (previr)]

Hello All,

I have an old PC with Intel 845 Graphics :
======================================================================================
00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 03)
 Subsystem: Micro-Star International Co., Ltd. Device [1462:5778]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 10
 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
 Region 1: Memory at ee000000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: <access denied>
 Kernel modules: i915
======================================================================================

I added 'nomodeset' in '/boot/grub/menu.lst' and did an 'update-grub' :

======================================================================================
title Ubuntu 9.10, kernel 2.6.31-14-generic
uuid 2ff1733b-ba80-4e69-afab-5d7148963775
kernel /boot/vmlinuz-2.6.31-14-generic root=UUID=2ff1733b-ba80-4e69-afab-5d7148963775 ro quiet splash nomodeset
initrd /boot/initrd.img-2.6.31-14-generic
quiet
======================================================================================

The problem still PERSISTS on my PC.

Should I just downgrade to Jaunty where Video Playback was fine?

Best regards,
~Previr

[Previr (previr)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: previr 1490 F.... pulseaudio
 /dev/snd/timer: previr 1490 f.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC658D at irq 17'
   Mixer name : 'Realtek ALC658D'
   Components : 'AC97a:414c4781'
   Controls : 38
   Simple ctrls : 24
CheckboxSubmission: e640f6585f6d8d7a33aad98aefc62c77
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
CurrentDmesg:
 [ 36.519379] ppdev: user-space parallel port driver
 [ 42.185307] eth0: no IPv6 routers present
 [ 108.996265] vlc[1791]: segfault at 0 ip 02404fc0 sp b73077e0 error 6 in libQtGui.so.4.5.2[21e5000+97b000]
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=0797c342-5770-40a7-9910-6959654ef11e
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard PPPPPP-ABA MMMMM
Package: linux (not installed)
ProcCmdLine: root=UUID=2ff1733b-ba80-4e69-afab-5d7148963775 ro quiet splash nomodeset
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_IN
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 02/25/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.08
dmi.board.name: Gamila/Giovani/Neon series
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 030
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.08:bd02/25/2004:svnHewlett-Packard:pnPPPPPP-ABAMMMMM:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnGamila/Giovani/Neonseries:rvr030:cvn:ct3:cvr:
dmi.product.name: PPPPPP-ABA MMMMM
dmi.sys.vendor: Hewlett-Packard

[Beni Cherniavsky (cben)]

Previr, this seems interesting and important.
[mind you, I'm not a developer, just trying to push this bug along]

Can you also attach:
(1) the file /var/log/Xorg.0.log
(2) the output of the command: xvinfo

Downgrading a working system is tricky and painful.
I'd advice to wait for solution/workaround before you resort to that.

Meanwhile, best workaround I had before "nomodeset" solved Xv for me:
  mplayer -vm -vo x11 -framedrop
Be warned that -vm might sometimes switch to a low resolution and not restore it :-(
  xrandr --auto
and
  xrandr -s 1024x768 # or whatever you like
will be your friends then...

[Beni Cherniavsky (cben)]

Previr, could you also attach:
(1) the file /var/log/Xorg.0.log
(2) the output of the command: xvinfo

Downgrading is a somewhat painful, I recommend you wait a bit more for a solution before resorting to that.
Meanwhile, a few tips for minimal-CPU playback:
(1) disable compiz (System→Preferences→Appearance→Desktop Effects) if it's enabled.
(1) use:
        mplayer -vm -vo x11 -framedrop <movie file>
    be prepared that -vm might leave you with a bad resolution on exit;
    if that happens, running:
        xrandr --auto
    or
        xrandr -s 1024x768
    (or whatever resolution you like) should help.

[sorry if this appears twice, it seems lauchpad ate my comment]

[Geir Ove Myhr (gomyhr)]

Guys, please don't do any more `apport-collect 395932`. We don't need that information at this point and it only contributes to making this bug report more unreadable. If you look at the upstream bug report, you will see that Daniel Vetter has been working hard to implement this, but this is aimed at kernel 2.6.32, so it will probably never appear in Karmic, but should make it to Lucid. The commit implementing this upstream seems to be http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=9871afa47454b409473d306f2db48ac736938314 . Doesn't look like has made it into Linus' 2.6.32 tree.

When the Lucid alpha versions with this implemented arrives, testing of this will be appreciated. For now, we don't need any more user input or confirmations.

[Geir Ove Myhr (gomyhr)]

Pervir and Beni, you seem to be talking about an issue which is slightly different than what this bug report was originally about (which is Xv not working with KMS due to overlay video not being implemented for KMS). Please file a new bug report with `ubuntu-bug xserver-xorg-video-intel` for your problem with Xv not working with UMS (which is what you get with nomodeset) on 845G. We need to keep different issues in different bug reports to avoid confusion.

[Previr (previr)]

I agree that this is slightly different and should be filed as a separate bug.

Just for Beni :

[Previr (previr)]

Just for Beni.
I agree that this is slightly different and should be filed as a separate bug.

[Beni Cherniavsky (cben)]

Indeed. Pervir - according to xvinfo you do have Xv working, so it's
a very different bug.

Xorg.0.log says "Failed to pin xv buffer" repeatedly,
which means you might have one of these bugs:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/371275
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/354688

If not, you'll have to file a new bug report.
Also include in that report the output of the video player, and how
exactly it fails to play.

[Previr (previr)]

Before filing a new bug with `ubuntu-bug xserver-xorg-video-intel` for i845G + Karmic, just wanted to share this piece of logs :

[1] mplayer -vo x11 <movie file> ==> This one is OK with video playback
[2] mplayer -vo xv <movie file> ==> This one gives multiple errors.

"X11 error: BadAlloc (insufficient resources for operation)?,?% 0 0
X11 error: BadAlloc (insufficient resources for operation)?,?% 7 0
X11 error: BadAlloc (insufficient resources for operation)
X11 error: BadAlloc (insufficient resources for operation)
X11 error: BadAlloc (insufficient resources for operation)
X11 error: BadAlloc (insufficient resources for operation)
X11 error: BadAlloc (insufficient resources for operation)
X11 error: BadAlloc (insufficient resources for operation)
"

[Geir Ove Myhr (gomyhr)]

There is another upstream bug report regarding 855GM overlay video not working with KMS: https://bugs.freedesktop.org/show_bug.cgi?id=24543 . Looks like it is now implemented, but that the implementation still has bugs.

[Antti Kaihola (akaihola)]

Adding nomodeset fixes this on my Dell Inspiron 500m with a 82852/855GM and a 1400x1050 display, running kernel 2.6.31-15-generic and Xorg from the xorg-edgers ppa (xorg 7.4+3ubuntu10 and intel driver 2:2.9.1~git-0ubuntu0tormod).

With KSM, watching a DVD with Totem, the framerate goes down to almost 1 fps. VLC is almost ok, 10% of frames dropped with 100% CPU load.

Without KSM, VLC is perfect but Totem goes nuts: viewing a DVD works sometimes when using a small window, but never full-screen. It looks like the UI is on top of the video.

Also, I think disabling KSM caused another problem: when waking up from suspend-to-RAM for the first time, the display resolution came up lower than normal, and playing a DVD with VLC on XVideo caused a hard lock-up - not even Alt-SysRq-K,S,U,B could boot the machine.

I tried suspending again manually after rebooting, and now it worked correctly. The lock-up occurred after the laptop had supended automatically due to being idle (I've set a 30 minute timeout for suspend). I'll keep an eye on the issue and see if there's a specific bug report for it.

[sTiLL (stillka)]

Hello,

on my Thinkpad X40 I have same problem. Jut for information, I am using latest 2.6.32 kernel from kernel-ppa and latest intel drivers from xorg-edgers ppa.

(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
(II) intel(0): Creating default Display subsection in Screen section
 "Builtin Default intel Screen 0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 855GME
(--) intel(0): Chipset: "852GM/855GM"
(==) intel(0): video overlay key set to 0x101fe
(II) intel(0): Output VGA1 has no monitor section
(II) intel(0): Output LVDS1 has no monitor section
(II) intel(0): found backlight control interface /sys/class/backlight/thinkpad_screen
(II) intel(0): EDID for output VGA1
(II) intel(0): EDID for output LVDS1
(II) intel(0): Output VGA1 disconnected
(II) intel(0): Output LVDS1 connected
(II) intel(0): Using exact sizes for initial modes
(II) intel(0): Output LVDS1 using initial mode 1024x768
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(==) intel(0): DPI set to (96, 96)
(II) intel(0): [DRI2] Setup complete
(**) intel(0): Tiling enabled
(**) intel(0): SwapBuffers wait enabled
(==) intel(0): VideoRam: 131072 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): No memory allocations
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): DPMS enabled
(WW) intel(0): Disabling Xv because no adaptors could be initialized. <================
(II) intel(0): direct rendering: DRI2 Enabled

And second bug, with new Intel driver "nomodeset" option cause failing of Xserver start:
...
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
(EE) intel(0): No kernel modesetting driver detected.
(II) UnloadModule: "intel"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

[Octavsly-tiscali (octavsly-tiscali)]

Should XVideo be supported on:

- KMS enabled
- 0:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
- mesa 7.7_rc3
- intel driver 2.9.1
- libdrm 2.4.17
- Linux xxxxxx 2.6.32-gentoo #3 SMP Mon Dec 21 23:20:01 CET 2009 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux

since it my case it does not work:
# xvinfo
X-Video Extension version 2.2
screen #0
 no adaptors present

if KMS is disabled XVideo works

Should I open a new bug report?

[Julien Cristau (jcristau)]

> --- Comment #40 from Octavian Petre <email address hidden> 2009-12-23 01:12:20 PST ---
> Should XVideo be supported on:
>
> - Linux xxxxxx 2.6.32-gentoo #3 SMP Mon Dec 21 23:20:01 CET 2009 i686 Intel(R)
> Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux

the i915 overlay code will be included in linux 2.6.33.

[Daniel-ffwll (daniel-ffwll)]

On Wed, Dec 23, 2009 at 06:16:25AM -0800, <email address hidden> wrote:
> the i915 overlay code will be included in linux 2.6.33.

Furthermore you need a more recent xf86-video-intel, support will be
included by default in the upcoming 2.9.10 release.

[DarkMastero (catmastero)]

Tried to update my operating system ad encountered an error disallowing a packet to be installed or upgraded (at least that's what the error message said).

[Roan (roan)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: roan 2076 F.... pulseaudio
                      roan 2451 F.... xfce4-volumed
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC250 at irq 11'
   Mixer name : 'Realtek ALC250 rev 2'
   Components : 'AC97a:414c4752'
   Controls : 33
   Simple ctrls : 21
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=ab05ccfd-84b9-4c58-953b-0f706246d5e8
Lsusb:
 Bus 003 Device 002: ID 046e:52c4 Behavior Tech. Computer Corp.
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA Satellite M35X
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=d631cb7b-21a4-4c48-8ccc-bc662ecb1cc4 ro nomodset acpi=off splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-17-generic N/A
 linux-firmware 1.25
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-17-generic i686
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 03/23/2005
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.90
dmi.board.name: EAL20
dmi.board.vendor: TOSHIBA
dmi.board.version: Null
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd03/23/2005:svnTOSHIBA:pnSatelliteM35X:pvrPSA72U-2KS00U:rvnTOSHIBA:rnEAL20:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite M35X
dmi.product.version: PSA72U-2KS00U
dmi.sys.vendor: TOSHIBA

[Matteo Settenvini (tchernobog)]

This bug is still valid on Lucid. Since it's a LTS, and given the number of people owning Intel cards, I think it'll be nice a backport of the kernel patches needed to fix this bug. Playing a video in Totem with a resolution above 640x480 hogs my CPU at 100% and makes anything larger unwatchable. (P4 2.4GHz here, YMMV). Is it feasible?

[Matteo Settenvini (tchernobog)]

Sorry for the spam: by the way, my system doesn't boot in Lucid with "nomodeset" anymore (Playmouth related? It just hangs on a black screen before starting Xorg), so no workaround is present at the moment.

[ruegi (ruegi-k)]

AlsaDevices:
 total 0
 drwxr-xr-x 2 root root 60 2010-02-09 23:06 by-path
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/sequencer2', '/dev/sequencer', '/dev/seq'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=4ae701c8-e5ca-4c8e-912b-41e859296bd8
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: FUJITSU FMVFC50TW
Package: xserver-xorg-video-intel 2:2.9.0-1ubuntu2.1
PackageArchitecture: i386
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=9ec42193-2568-4e69-9ae6-54f38619f6c7 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=ja_JP.UTF-8
 LANGUAGE=ja_JP.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-18.59-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2.1
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
RfKill: Can't open RFKILL control device: No such file or directory
Uname: Linux 2.6.28-18-generic i686
UserGroups:

XsessionErrors:
 (gnome-settings-daemon:1533): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1533): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1636): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1616): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (nautilus:1836): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 11/20/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.02
dmi.board.name: FJNB027
dmi.board.vendor: FUJITSU
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.02:bd11/20/2008:svnFUJITSU:pnFMVFC50TW:pvr:rvnFUJITSU:rnFJNB027:rvr:cvnFUJITSU:ct3:cvr:
dmi.product.name: FMVFC50TW
dmi.sys.vendor: FUJITSU
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.28-18-generic

[daniel (bocardo+u)]

Is there any chance there will be a fix in time for lucid? Otherwise it will be critical considering the disabling of UMS in “xserver-xorg-video-intel” 2:2.9.1-1ubuntu4 *

* from the changelog here https://launchpad.net/ubuntu/lucid/+source/xserver-xorg-video-intel/2:2.9.1-1ubuntu4

[braseb (braseb37)]

alway no xv support for 82855/855GM with the alpha 3 of lucid and driver xserver-xorg-intel 2.9.1-1ubuntu6

[Søren Holm (sgh)]

I have Xv running fine here. But only in a single monitor configuration. As soon as I add a second monitor Xv stops working. It works again when going back to a single monitor though. My lspci looks like this.

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12)
05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
08:03.0 CardBus bridge: O2 Micro, Inc. OZ711MP1/MS1 MemoryCardBus Controller (rev 21)
08:03.1 CardBus bridge: O2 Micro, Inc. OZ711MP1/MS1 MemoryCardBus Controller (rev 21)
08:03.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 01)
08:03.3 Bridge: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
08:03.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)

[Robert Hooker (sarvatt)]

We have kernel support now as of 2.6.32-16 with the .33 kernel drm backported. xserver-xorg-video-intel 2.10 is the last requirement.

[Craig73 (funrun73)]

Will 2.10 be in Lucid?

On Sun, Mar 14, 2010 at 5:41 PM, Robert Hooker <email address hidden> wrote:

> We have kernel support now as of 2.6.32-16 with the .33 kernel drm
> backported. xserver-xorg-video-intel 2.10 is the last requirement.
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Fix Released
>
> ** Summary changed:
>
> - [i855] (Needs 2.6.33 drm and -intel 2.10) No Xv support for 82852/855GM
> (KMS bug)
> + [i855] (Needs intel 2.10) No Xv support for 82852/855GM (KMS bug)
>
> --
> [i855] (Needs intel 2.10) No Xv support for 82852/855GM (KMS bug)
> https://bugs.launchpad.net/bugs/395932
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu Release Notes: Fix Released
> Status in X.org xf86-video-intel: Fix Released
> Status in “linux” package in Ubuntu: Fix Released
> Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-intel
>
> After upgrading to Karmic (alpha) my graphics driver is unable to provide
> Xv. The following line is printed in Xorg.0.log:
>
> (WW) intel(0): Disabling Xv because no adaptors could be initialized.
>
> I've tried various settings in xorg.conf, with no luck. (XvPreferOverlay,
> Tiling).
>
> [Update]
>
> >From the Q4 anouncment [1]:
> Video overlay support with KMS is now supported in xserver-xorg-video-intel
> 2.10.0. This currently requires Linux 2.6.33, but a backport to 2.6.32
> (Lucid version) is available from [2]. Daniel Vetter intends to support
> this backport which is intended for distros that use kernel 2.6.32 [3].
> Although the main code is in the kernel, intel driver 2.10.0 is apparently
> required [4].
>
> [1]: http://intellinuxgraphics.org/2009Q4.html
> [2]:
> http://gitorious.org/daniel-s-linux-stuff/linux-kernel/commits/intel-kms-overlay-for-2.6.32
> [3]:
> http://lists.freedesktop.org/archives/intel-gfx/2010-January/005372.html
> [4]: https://bugs.freedesktop.org/show_bug.cgi?id=20901#c42
>
> [lspci]
> 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor
> to I/O Controller (rev 02)
> Subsystem: Acer Incorporated [ALI] Device 0035
> 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated
> Graphics Device (rev 02)
> Subsystem: Acer Incorporated [ALI] Device 0035
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/395932/+subscribe
>

[Robert Hooker (sarvatt)]

Unfortunately it looks like 2.9.1 will be the final lucid version due to 2.10 only supporting kernel modesetting. 2.10 will be available in a PPA though, and it is available along with the rest of the X/Mesa stacks already in https://launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

Well, there was a set of discrete Xv fixes which went in after 2.9.0 was cut but before the massive refactoring work for removing UMS hit. It comprised 17 patches total, which I've unified into the patch attached here.

$ diffstat debian/patches/102_xv-fix-8xx-video.patch
 drmmode_display.c | 9
 i830.h | 3
 i830_driver.c | 2
 i830_video.c | 1513 +++++++++++++++++++++++++-----------------------------
 i830_video.h | 20
 i915_video.c | 33 -
 i965_video.c | 48 -
 7 files changed, 755 insertions(+), 873 deletions(-)

This is mostly confined to the i8xx code, but there are some changes to the 9xx video code, which alter the algorithmic logic, so I can't say with 100% certainty that the changes are going to be regression-free for 9xx, which makes me reticent to pull this in for Lucid. There is also a lot of refactoring going on, which probably accounts for most of the size of the patch, and unfortunately also makes it tough to review in detail.

But... Since this backport was pretty straightforward, I've gone ahead and packaged and set up a PPA of this here:
https://edge.launchpad.net/~bryceharrington/+archive/white

If 8xx users can test this and say that it gives a perfect fix to Xv support (i.e. no secondary issues), AND we can get some 9xx users to verify it causes no regressions, then we can look at including this in Lucid. Otherwise, 8xx users can use this ppa or

[daniel (bocardo+u)]

I own a 855 laptop (an inspiron 700m) and can get ahold of a 950 one (a msi wind u100).
If you could give me a set of test to run, I'll test it and report back on both counts.

[Søren Holm (sgh)]

Hi pc contains this.

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

Xv works fine here, even with the current 2.9-driver

BUT whenre running a dual-screen configuration is does not work with any driver. Is that a separate issue?

[braseb (braseb37)]

Thank you for this patch but with my i855GM the messages :
"(==) intel(0): Intel XvMC decoder disabled
(WW) intel(0): Disabling Xv because no adaptors could be initialized."
are alway present.
for replace the driver of lucid, I open synaptic and i force the version
with the version of the ppa and I log out the session.
I do this with a live cd of lucid (daily of 26 march).
is what I have done well?
sorry for my english

2010/3/25 Bryce Harrington <email address hidden>

> Well, there was a set of discrete Xv fixes which went in after 2.9.0 was
> cut but before the massive refactoring work for removing UMS hit. It
> comprised 17 patches total, which I've unified into the patch attached
> here.
>
> $ diffstat debian/patches/102_xv-fix-8xx-video.patch
> drmmode_display.c | 9
> i830.h | 3
> i830_driver.c | 2
> i830_video.c | 1513
> +++++++++++++++++++++++++-----------------------------
> i830_video.h | 20
> i915_video.c | 33 -
> i965_video.c | 48 -
> 7 files changed, 755 insertions(+), 873 deletions(-)
>
> This is mostly confined to the i8xx code, but there are some changes to
> the 9xx video code, which alter the algorithmic logic, so I can't say
> with 100% certainty that the changes are going to be regression-free for
> 9xx, which makes me reticent to pull this in for Lucid. There is also a
> lot of refactoring going on, which probably accounts for most of the
> size of the patch, and unfortunately also makes it tough to review in
> detail.
>
> But... Since this backport was pretty straightforward, I've gone ahead and
> packaged and set up a PPA of this here:
> https://edge.launchpad.net/~bryceharrington/+archive/white<https://edge.launchpad.net/%7Ebryceharrington/+archive/white>
>
> If 8xx users can test this and say that it gives a perfect fix to Xv
> support (i.e. no secondary issues), AND we can get some 9xx users to
> verify it causes no regressions, then we can look at including this in
> Lucid. Otherwise, 8xx users can use this ppa or
>
> ** Patch added: "102_xv-fix-8xx-video.patch"
> http://launchpadlibrarian.net/42006303/102_xv-fix-8xx-video.patch
>
> --
> [i855] (Needs intel 2.10) No Xv support for 82852/855GM (KMS bug)
> https://bugs.launchpad.net/bugs/395932
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Ubuntu Release Notes: Fix Released
> Status in X.org xf86-video-intel: Fix Released
> Status in “linux” package in Ubuntu: Fix Released
> Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged
> Status in “linux” source package in Lucid: Fix Released
> Status in “xserver-xorg-video-intel” source package in Lucid: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-intel
>
> After upgrading to Karmic (alpha) my graphics driver is unable to provide
> Xv. The following line is printed in Xorg.0.log:
>
> (WW) intel(0): Disabling Xv because no adaptors could be initialized.
>
> I've tried various settings in xorg.conf, with no luck. (XvPreferOverlay,
> Tiling).
>
> [Update]
>
> >From the Q4 anouncment [1]:
> Video overlay support with KMS is now supported in xserver-xorg-video-int...

[Mervin Beng (mervinb)]

Bryce, I have been testing xorg-edgers PPA on an MSI Wind (i945), and I noticed that XvMC was disabled even though the XV and XVMC modules were loaded. This was with intel 2.10 and the 2.9 with patch from your PPA. Kernels tested were 2.6.32 with backports, and 2.6.33.

The Xorg.0.log shows the extensions loaded, but XvMC module appears disabled by default.

$ grep -i Xv /var/log/Xorg.0.log
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(==) intel(0): Intel XvMC decoder disabled

Is there some setting for XvMC that I have missed out?

$ lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)

Thanks!

[Robert Hooker (sarvatt)]

Xv and XvMC are not the same things, KMS Xv overlay support is the only thing backported. To use XvMC with xorg-edgers you need to enable it in your xorg.conf like so because it is disabled by default (and is not applicable to 8xx series)

Section "Device"
        Identifier "intel"
        Driver "intel"
        Option "XvMC" "true"
EndSection

if you run man intel in a terminal you will see all of the options.

[Robert Hooker (sarvatt)]

braseb: try enabling the driver, then going to system - preferences - keyboard, pick layouts, then options, and enable the "key sequence to kill the X server" option, and finally press control+alt+backspace

[braseb (braseb37)]

Thank you Robert Hooker for your help but the issue is same the message is
alway present in xorg.0.log but with the 2.10.9xx the problem is resolved.

2010/3/29 Robert Hooker <email address hidden>

> braseb: try enabling the driver, then going to system - preferences -
> keyboard, pick layouts, then options, and enable the "key sequence to
> kill the X server" option, and finally press control+alt+backspace
>
> --
> [i855] (Needs intel 2.10) No Xv support for 82852/855GM (KMS bug)
> https://bugs.launchpad.net/bugs/395932
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Ubuntu Release Notes: Fix Released
> Status in X.org xf86-video-intel: Fix Released
> Status in “linux” package in Ubuntu: Fix Released
> Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged
> Status in “linux” source package in Lucid: Fix Released
> Status in “xserver-xorg-video-intel” source package in Lucid: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-intel
>
> After upgrading to Karmic (alpha) my graphics driver is unable to provide
> Xv. The following line is printed in Xorg.0.log:
>
> (WW) intel(0): Disabling Xv because no adaptors could be initialized.
>
> I've tried various settings in xorg.conf, with no luck. (XvPreferOverlay,
> Tiling).
>
> [Update]
>
> >From the Q4 anouncment [1]:
> Video overlay support with KMS is now supported in xserver-xorg-video-intel
> 2.10.0. This currently requires Linux 2.6.33, but a backport to 2.6.32
> (Lucid version) is available from [2]. Daniel Vetter intends to support
> this backport which is intended for distros that use kernel 2.6.32 [3].
> Although the main code is in the kernel, intel driver 2.10.0 is apparently
> required [4].
>
> [1]: http://intellinuxgraphics.org/2009Q4.html
> [2]:
> http://gitorious.org/daniel-s-linux-stuff/linux-kernel/commits/intel-kms-overlay-for-2.6.32
> [3]:
> http://lists.freedesktop.org/archives/intel-gfx/2010-January/005372.html
> [4]: https://bugs.freedesktop.org/show_bug.cgi?id=20901#c42
>
> [lspci]
> 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor
> to I/O Controller (rev 02)
> Subsystem: Acer Incorporated [ALI] Device 0035
> 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated
> Graphics Device (rev 02)
> Subsystem: Acer Incorporated [ALI] Device 0035
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/395932/+subscribe
>

[Mervin Beng (mervinb)]

Thanks for the pointer Robert!

[Götz Christ (g-christ)]

00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)

With xserver-xorg-video-intel 2:2.9.1-1ubuntu17~bug395932~1 I still get the same message: (WW) intel(0): Disabling Xv because no adaptors could be initialized. Isn't some other update necesary?

Haven't tested with 2.10, I don''t know where to get a deb package for it.

With version 2.10.903+git20100327.df3b2684-0ubuntu0sarvatt Xv works but with the blue background when a window is in front of the video. I get also many Xserver restarts with that driver. For example opening kdiff3 make xserver crash. I haven't used all the xorg edgers repo packages, only the intel video driver.

[Launchpad Janitor (janitor)]

This bug was fixed in the package xserver-xorg-video-intel - 2:2.9.1-3ubuntu1

---------------
xserver-xorg-video-intel (2:2.9.1-3ubuntu1) lucid; urgency=low

  * Merge with Debian.
    - Backport KMS video overlay from upstream 2.10 (lp: #395932)
  * Remaining Ubuntu changes:
    - debian/apport-gpu-error-intel.py, debian/xserver-xorg-video-intel.udev:
      Add apport script to collect debug information on GPU hangs
    - rules: Install udev rule to run the script when the kernel detects hung GPU
    - control: Add intel-gpu-tools to Recommends for use by the above
    - 101_copy-fb.patch: Adds feature to driver so Xserver can draw
      root windows with no background. This enables smooth boot with
      Plymouth.
    - Drop xserver-xorg-video-intel-dbg.install: intel_reg_dumper is now
      provided by the intel-gpu-tools package.
    - apport-gpu-error-intel.py, xserver-xorg-video-intel.install,
      xserver-xorg-video-intel.udev: Add apport hook to catch X freeze bugs
    - 102_avoid_flushing_null.patch: Cherrypick from upstream to I830.
    - 103_check_for_overflow.patch: Cherrypick from upstream to I915.
    - 104_fail_when_prop_values_gone.patch: Cherrypick from upstream to
      drmmode_display.
  * Reduce libdrm-dev requirement to 2.6.18
  * Add 105_free_after_printing.patch: Cherrypick from upstream.
    Avoid printing a just-freed string if the DRM device could not be opened.
  * Add 106_initialize_drmmode_output.patch: Cherrypick from upstream.
    Clear mode_output during output destroy.
 -- Bryce Harrington <email address hidden> Wed, 31 Mar 2010 14:36:51 -0700

[Pedro Saraiva (pedro-a34195)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Pedro Saraiva

Pedro Saraiva
Analyst / Programmer at Maisis - Information Systems, Lda.
Portugal

Confirm that you know Pedro Saraiva
https://www.linkedin.com/e/isd/1283606579/haMwGvir/

------
(c) 2010, LinkedIn Corporation