green screen when switching to livetv in myth

I've uploaded a package which contains a possible fix to the mythbuntu-testing PPA. Version number is 0.21.0+fixes18337-0ubuntu1~ppa4

https://launchpad.net/~mythbuntu-testing/+archive

Can you please verify if this package fixes it for you ASAP? We'd like to have that uploaded before beta freeze :)

Sorry.. was two weeks on holidays and when I tried it today (I now not really asap, but got no notification mail about an update !?), there was no such package available any more.
The actual state is also still the same.
At the moment the version
0.21.0+fixes18379
is installed which shows the green screen :(

Metzelmaennchen schrieb:
> Sorry.. was two weeks on holidays and when I tried it today (I now not really asap, but got no notification mail about an update !?), there was no such package available any more.
> The actual state is also still the same.
> At the moment the version
> 0.21.0+fixes18379
> is installed which shows the green screen :(
>
>
I'll upload another build soon and let you know here.

Hey,

sorry for the delay. I've uploaded mythtv 0.21.0+fixes18692-0ubuntu1~ppa2 to my PPA: https://launchpad.net/~laga/+archive

It should be built in a few hours. Please let me know how it goes soon :)

> sorry for the delay. I've uploaded mythtv 0.21.0+fixes18692-0ubuntu1~ppa2 to my PPA: https://launchpad.net/~laga/+archive
>
>It should be built in a few hours. Please let me know how it goes soon :)

Hey no prob :)
I'm watching the thread every day now. Hoping to see something different than a green swamp soon ;)
So let's see... got a problem with the provided package.. its for hardy :(
But my hardy doesn't show the problem, it's the intrepid one.

Just to let you guys know: I have the same problem on Ubuntu Intrepid, Kernel 2.6.27-7 with an analog Bt878 card.

Hope this is fixed in the final ;)

Metzelmaennchen,

try my PPA again. I've copied the packages from Hardy to Intrepid.

Sorry but nope, it doesn't seem to change anything :(
Installed all the provided packages via dpkg --force-depends and doesn't have cared about the liblame and libx264 warnings... but still green in livetv...
Got following warning from backend log
VIDIOCMCAPTURE0: Device or resource busy
VIDIOCMCAPTURE1: Device or resource busy

Okay, I've uploaded a proper build (mythtv - 0.21.0+fixes18692-0ubuntu1~ppa3) for Intrepid to my PPA. Maybe that'll work. Please add my PPA to your sources.list and upgrade.

I just upgraded and it now works.

Thank you.

This bug was fixed in the package mythtv - 0.21.0+fixes18722-0ubuntu1

---------------
mythtv (0.21.0+fixes18722-0ubuntu1) intrepid; urgency=low

  * Sync against release-0-21-fixes branch. Fixes:
    - (LP: #260429)
  * Update 24_fix_h264_frame_counting.dpatch to incorporate changeset
    18542 from trunk <http://svn.mythtv.org/trac/changeset/18542>
  * debian/patches/:
    - drop 27_disable_deinterlacing_in_guide.dpatch because it's been
      committed upstream
    - add 28_fix_v4l.dpatch (LP: #259321)
  * Add debian/mythtv-frontend.dirs back in (LP: #280792)
  * Add kdesudo to list of graphical sudo providers in
    debian/dialog_functions.sh to account for KDE 4 in Intrepid (LP: #274602)

 -- Michael Haas <email address hidden> Wed, 15 Oct 2008 23:56:53 +0200

Just got home from work and wanted to test it. But you cleaned up the ppa :(
So I'm waiting for the upstream and will post here if the fix also works for me.

Metzelmaennchen, the patch is in the Intrepid archives now. Just update your system - it's in the mythtv package 0.21.0+fixes18722-0ubuntu1 and newer.

Yes, you were right :)
Sometimes I'm really stupid... sorry for this. But I can commit, it works for me, too.
Can watch LiveTV again :) No green screen anymore.

Thanks for your support&great work

Kind greetings from Germany
Das Metzelmaennchen

Marking Released since it looks like this was released in intrepid:

mythtv (0.21.0+fixes18722-0ubuntu1) intrepid; urgency=low

    - add 28_fix_v4l.dpatch (LP: #259321)
(among other things)

I'm experiencing this same behaviour under Ubuntu Karmic 9.10 kernel 2.6.31-17-generic with a Prolink PixelView PlayTV MPEG2 PV-M4900 analog card and a ATI Radeon 9600 for video output. I've tried all sorts of configurations using bttv with different cards/tunners as well as several MythTV channel, Recording and Playback profiles configurations.

Here is my lspci with relevant stuff:

00:0e.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:0e.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon 9600]
01:00.1 Display controller: ATI Technologies Inc RV350 AR [Radeon 9600] (Secondary)

Here is my bttv output:

hlm@suite:~$ dmesg | grep bttv
[ 14.963747] bttv: driver version 0.9.18 loaded
[ 14.963756] bttv: using 8 buffers with 2080k (520 pages) each for capture
[ 14.963885] bttv: Bt8xx card found (0).
[ 14.963940] bttv 0000:00:0e.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 14.963958] bttv0: Bt878 (rev 17) at 0000:00:0e.0, irq: 17, latency: 32, mmio: 0xaf800000
[ 14.974167] bttv0: using: Prolink PixelView PlayTV MPEG2 PV-M4900 [card=139,insmod option]
[ 14.974178] IRQ 17/bttv0: IRQF_DISABLED is not guaranteed on shared IRQs
[ 14.974266] bttv0: gpio: en=00000000, out=00000000 in=00afc0ff [init]
[ 14.978467] bttv0: tuner type=59
[ 15.207477] bttv0: audio absent, no audio device found!
[ 15.400448] bttv0: registered device video0
[ 15.400503] bttv0: registered device vbi0
[ 15.400541] bttv0: registered device radio0
[ 15.400565] bttv0: PLL: 28636363 => 35468950 .. ok
[ 15.433360] input: bttv IR (card=139) as /devices/pci0000:00/0000:00:0e.0/input/input5
[ 2784.539721] bttv0: PLL can sleep, using XTAL (28636363).

Only MythTV LiveTV and LiveTV recording are affected. TVTime, VLC, mplayer are working fine, which leads me into thinking MythTV is improperly initializing the video capture card.

There are all sorts of references out there on the web of people having this very same issue, none of them seem to be conclusive about a solution