This is more a status report. I have two MythTV backend machines. I tried getting the one using a PVR-150 to work using the masked 0.2.0 ivtv driver but had no luck. I ended up using the ivtv CVS tarball revision 0.3.3k and got good results. If you decide to move the current masked version to stable will you please consider bringing along a new masked version that installs 0.3.3k or higher? I will also report that on my PVR-250 backend system that I built about 6 weeks ago I was unable at that time to get it working with the 0.2.0 version of ivtv from portage but was able to do it with the version from the ivtv site built by hand. I'm still using the CVS version but would like to switch to portage when appropriate. Is it really working now? Thanks Reproducible: Always Steps to Reproduce: 1. NA Actual Results: Just a report and request for 0.3.3k or higher in the future. From the 0.2.0 PVR-250 machine: flash ~ # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r6 i686) ================================================================= System uname: 2.6.11-gentoo-r6 i686 Mobile Intel(R) Pentium(R) 4 CPU 3.06GHzGentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Apr 28 2005, 18:37:46)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.9.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.tucdemonic.org/gentoo/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://mirror.gentoo.gr.jp http://www.zentek-international.com/mirrors/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aalib alsa apache2 apm audiofile avi berkdb bitmap-fonts bonobo caps cdr crypt cups curl dvd dvdr dvdread emboss encode esd fam flac fluidsynth foomaticdb fortran gdbm gif gimp gimpprint gnome gpm gstreamer gtk gtk2 gtkhtml guile i8x0 imagemagick imlib ipv6 jack jack-tmpfs java jpeg kde ladcca ladspa libg++ libwww lirc mad mikmod mjpeg mmx motif mozcalendar mozilla mp3 mpeg mysql mythtv ncurses nls nptl nptlonly ogg oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline real samba sdl slang sndfile spell sse sse2 ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts usb v4l v4l2 vorbis xine xml xml2 xmms xscreensaver xv xvid zlib video_cards_radeon userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS flash ~ # From the ivtv 0.3.3k PVR-150 machine: gandalf ~ # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r9 i686) ================================================================= System uname: 2.6.11-gentoo-r9 i686 AMD Athlon(tm) XP 2500+ Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5,dev-lang/python-2.2.3-r5 [2.3.5 (#1, May 19 2005, 09:16:33)] dev-lang/python: 2.3.5, 2.2.3-r5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.7.9-r1, 1.5, 1.9.5, 1.6.3, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X Xi aalib alsa apache2 audiofile avi berkdb bitmap-fonts bonobo caps cdr crypt cups curl dvd dvdr dvdread eds emboss encode esd fam flac fluidsynth foomaticdb fortran gd gdbm gif gimp gimpprint gnome gpm gstreamer gtk gtk2 gtkhtml guile i8x0 imagemagick imlib ipv6 jack jack-caps jack-tmpfs java jpeg kde ladcca ladspa libg++ libwww lirc mad mikmod mjpeg mmx motif mozcalendar mozilla mp3 mpeg mysql mythtv ncurses nls nptl nptlonly nvidia ogg oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline real scanner sdl slang sndfile spell sse ssl svga tcltk tcpd threads tiff transcode truetype truetype-fonts type1-fonts usb v4l v4l2 vorbis xine xml xml2 xmms xscreensaver xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY gandalf ~ #
ivtv isn't going stable anytime soon, because it's not. And we aren't adding a development branch of an experimental driver to the tree. Sorry. I get enough stuff off what's there. Hopefully, they'll stabilize soon, but I wouldn't hold my breath.
I totally understand. I was just putting the info in for others if they go looking and to say what's working for me. Thanks.
It is on my TODO list which is in the ebuild itself to make the ebuild able to just be copied to another name in the 0.3.x series, and work. I just haven't had the time to do it yet.
*** Bug 95250 has been marked as a duplicate of this bug. ***
I'm glad the bug I files with an actually working ebuild got marked as a duplicate of this bug. The ebuild here should work: https://bugs.gentoo.org/attachment.cgi?id=60733&action=view It should work if you rename it 0.3.3k as well. (0.3.5z seems to work with my Hauppauge 150). It'd be nice to get this ebuild into portage if it works for you (cause it works for me).
Actually your ebuild is missing the line to build the wm8775, but the fact remains that I'm in no mood to field bugs for or track the 0.3.x branch.
This is an ebuild, that with the "wm8775" line would seem to work for a number of people with hauppauge 150/500 cards, who cares about your "mood"?
Let's not go there, OK? I'm sure he cares about his mood. That's cool. :-) I like the idea of having a more recent driver available but for the last few days new 'revisions' have been coming out at the rate of one every few hours. How is anyone supposed to keep up with that? I'm running 0.3.5p on one PVR-150 machine and 0.3.5v on another PVR-250 machine. How is any ebuild supposed to keep up with this rate of new drivers? I started wondering about an ebuild that would somehow ask me which version I wanted to install. Is it possible for an ebuild to ask questions and get answers about some directory out there that has many revisions in it?
Nope not possible Mark. Ebuilds are centered around 0 user interaction once they start running. As far as getting the 0.3.x branch into Portage, won't happen. There's no "footing" for us to even place our feet. Let alone calling it alpha, beta, unstable or even stable. The 0.3.x branch is called experimental and developmental for a reason. It's just way to fluid to even track. Releases come out faster then the Portage rsync cache gets re-generated. Once things settle down, maybe once they move it to a stable-ish 0.4.x branch we'll consider it.
