Bug 31978 - [855GM] Xvideo output not working on screen depth 16
Summary: [855GM] Xvideo output not working on screen depth 16
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium minor
Assignee: Default DRI bug account
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-29 13:04 UTC by sh29112911
Modified: 2012-06-27 04:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (15.12 KB, application/octet-stream)
2010-12-06 07:08 UTC, sh29112911
no flags Details
Xorg.log (25.76 KB, application/octet-stream)
2010-12-06 07:09 UTC, sh29112911
no flags Details
xorg.conf (970 bytes, application/octet-stream)
2010-12-06 07:10 UTC, sh29112911
no flags Details

Description sh29112911 2010-11-29 13:04:42 UTC
I am trying to get Xvideo working with shadowfb on the popular Intel 855GM chipset.

MPlayer and other similar programs display just a blue rectangle when using Xv output. I can hear the audio track, and no errors appear in stdout. Also, xvinfo tells that an Xv adaptor is present and the overlay seems to be set up according to Xorg.log:

$ cat /var/log/Xorg.0.log | grep overlay
[    22.594] (==) intel(0): video overlay key set to 0x83e
[    23.070] (II) intel(0): Set up overlay video

Modesetting is enabled in the kernel.

kernel 2.6.36.1
xf86-video-intel 2.13.0
xorg-server 1.9.2
Comment 1 sh29112911 2010-12-03 12:58:31 UTC
Found a solution: Xv works again after changing the screen depth to 24 instead of 16. Previously Xv was running happily on depth 16, though.

The problem occurs also on non-shadowfb X sessions with depth 16.
Comment 2 Chris Wilson 2010-12-03 13:43:06 UTC
Do you know which component regressed? ie does 2.6.36 + 2.12 play Xv or 2.6.35 + 2.13?
Comment 3 Daniel Vetter 2010-12-03 14:28:18 UTC
Well, I've written the kms xv code for i8xx and I've never bothered to check it with anything else than 32 bit depth (the default). But now that somebody actually cares I'll see whether I can fix it. First noob question (o.k. just laziness): How do you set 16 bit depth? xorg.conf snippet preferred ...
Comment 4 sh29112911 2010-12-04 03:44:24 UTC
@Chris: Hard to say, I upgraded from xorg-server 1.6 and xf86-video-intel 2.7 or so. Later versions of the driver were quite unstable on 855 so I did not test them that much.

@Daniel: I usually start X from the command line: "startx -- -depth 16". The following snippet in xorg.conf should also do the trick:

Section "Screen"
        DefaultDepth 16
EndSection
Comment 5 Julien Cristau 2010-12-04 04:27:24 UTC
> --- Comment #3 from Daniel Vetter <daniel@ffwll.ch> 2010-12-03 14:28:18 PST ---
> Well, I've written the kms xv code for i8xx and I've never bothered to check it
> with anything else than 32 bit depth (the default). But now that somebody
> actually cares I'll see whether I can fix it. First noob question (o.k. just
> laziness): How do you set 16 bit depth? xorg.conf snippet preferred ...
> 
Section "Screen"
        Identifier "foo"
        DefaultDepth 16
EndSection
Comment 6 Daniel Vetter 2010-12-04 09:27:36 UTC
I've just tested it on my i855 and it works here. Unfortunately there are a few unfixed i855 overlay bugs that I can't reproduce and have no other clue as to their cause.

Maybe-related: #29574

A few question:
- is this a regression for you?
- anything reported in dmesg or Xorg.log?
- can you try a few odd sizes/fullscreen/external (2nd) monitor/different output formats? If it's not broken all the time for 16 bit, this might give a hint.
Comment 7 sh29112911 2010-12-06 07:08:06 UTC
Created attachment 40829 [details]
dmesg
Comment 8 sh29112911 2010-12-06 07:09:36 UTC
Created attachment 40830 [details]
Xorg.log
Comment 9 sh29112911 2010-12-06 07:10:09 UTC
Created attachment 40831 [details]
xorg.conf
Comment 10 sh29112911 2010-12-06 07:11:23 UTC
Yes, this is a regression, xv on 16 bit was working for me (although on a rather ancient release of the driver + server). It is not a major inconvenience since xv is working fine for 24 bit.

A copy dmesg and Xorg.log attached after playing video with MPlayer. No messages appear on the logs during or after playback. 

The format of video does not seem to affect the result, neither does fullscreen or trying different sizes. I have no access to external display at the moment, but trying different values for xvattr -a XV_PIPE did not have any effect.

I tried this with also version 2.12 of the driver and the result was the same - only a blue rectangle is shown on 16 bit mode.
Comment 11 Daniel Vetter 2010-12-13 10:48:00 UTC
> --- Comment #10 from sh29112911@gmail.com 2010-12-06 07:11:23 PST ---
> Yes, this is a regression, xv on 16 bit was working for me (although on a
> rather ancient release of the driver + server). It is not a major inconvenience
> since xv is working fine for 24 bit.

If the old working version was also using kms, could you perhaps try to
bisect this regression? And don't have any idea what could be wrong, and
it seems to work here ...

If this hasn't ever worked for you with kms bisecting is pointless,
because it's a totally new codebase.
Comment 12 sh29112911 2010-12-14 11:41:43 UTC
(In reply to comment #11)
> > --- Comment #10 from sh29112911@gmail.com 2010-12-06 07:11:23 PST ---
> 
> If this hasn't ever worked for you with kms bisecting is pointless,
> because it's a totally new codebase.

This is the case - previously things were working on non-kms setup only.
Comment 13 Eugeni Dodonov 2011-09-08 15:56:03 UTC
This issue is affecting a hardware component which is not being actively worked on anymore.

Moving the assignee to the dri-devel list as contact, to give this issue a better coverage.
Comment 14 Chris Wilson 2012-06-27 04:09:12 UTC
Worksforme with kernel 3.4.0, and xf86-video-intel.git (with sna enabled).


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.