Currently, there is no ebuild in which to install ivtv tools/utilities when running gentoo-sources-2.6.26 with ivtv kernel module build into kernel. Reproducible: Always Steps to Reproduce: 1.Install Gentoo-sources 2.6.26 2.Attempt to emerge ivtv. 3. Actual Results: ivtv fails due to kernel being 2.6.26. I'm using built-in module for ivtv, however need the utils/test piece. Expected Results: ivtv ebuild should have detected built-in kernel modules and installed the util/test programs. Since all of the kernel modules are now integrated into the kernel, it makes sense to have an ebuild for ivtv-utils. I have created one that has it working, but you may want to tweak it a bit. I'll attach it below. ------------------------------------------------------------------------------- # Copyright 1999-2008 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/media-tv/ivtv/ivtv-1.3.0_alpha.ebuild,v 1.2 2008/07/24 18:22:10 armin76 Exp $ inherit eutils linux-mod versionator subversion DESCRIPTION="ivtv driver for Hauppauge PVR PCI cards" HOMEPAGE="http://www.ivtvdriver.org" ESVN_REPO_URI="http://ivtvdriver.org/svn/ivtv/trunk" SRC_URI="" SLOT="0" LICENSE="GPL-2" KEYWORDS="~amd64 ~ppc x86" IUSE="perl" RDEPEND=">=sys-fs/udev-103" DEPEND="app-arch/unzip" PDEPEND="media-tv/pvr-firmware perl? ( dev-perl/Video-Frequencies dev-perl/Video-ivtv dev-perl/Config-IniFiles virtual/perl-Getopt-Long dev-perl/perl-tk )" pkg_setup() { CONFIG_CHECK="EXPERIMENTAL KMOD HAS_IOMEM FW_LOADER I2C I2C_ALGOBIT VIDEO_DEV VIDEO_CAPTURE_DRIVERS VIDEO_V4L1 VIDEO_V4L2 VIDEO_HELPER_CHIPS_AUTO VIDEO_IVTV" if ! ( kernel_is 2 6 26 ); then eerror "Each IVTV driver branch will only work with a specific" eerror "linux kernel branch." eerror "" eerror "You will need to either:" eerror "a) emerge a different kernel" eerror "b) emerge a different ivtv driver" eerror "" eerror "See http://ivtvdriver.org/ for more information" die "This only works on 2.6.26 kernels" fi ewarn "" ewarn "Make sure that your I2C and V4L kernel drivers are loaded as" ewarn "modules, and not compiled into the kernel, or IVTV will not" ewarn "work." ewarn "" BUILD_PARAMS="KDIR=${KV_DIR}" ewarn ${KV_DIR} } src_unpack() { subversion_src_unpack } src_compile() { cd "${S}" emake INCDIR="${KV_DIR}/include" || die "failed to build utils " } src_install() { cd "${S}" make DESTDIR="${D}" PREFIX="/usr" install || die "failed to install utils" use perl && dobin utils/perl/*.pl cd "${S}" dodoc README* doc/* ChangeLog* use perl && dodoc utils/perl/README.ptune } pkg_postinst() { elog "" elog "This version of the IVTV driver contains only ivtv utilities" elog "The driver itself in integral within the kernel" ewarn "" ewarn "IMPORTANT: In case of problems first read this page:" ewarn "http://www.ivtvdriver.org/index.php/Troubleshooting" ewarn "" ewarn "If any of these conditions match your setup, you may want to look at the" ewarn "README in /usr/share/doc/${PF}/" ewarn "" ewarn " - Using MythTV, a PVR-350 and the ivtvfb module" ewarn " - Using the ivtv X driver and the ivtvfb module" ewarn " - You want to manually build ivtv against v4l-dvb" ewarn "" ewarn "Also, the ivtv package comes with lots of documentation regarding setup," ewarn "proper use and debugging utilities." ewarn "They are also located in /usr/share/doc/${PF}/" ewarn "" ewarn "For more information, see the IVTV driver homepage at:" ewarn "http://www.ivtvdriver.org/" }
Created attachment 162913 [details] ebuild for ivtv svn to allow install of ivtv utils on kernel 2.6.26 This ebuild may need some minor tweaking, but as is installs everything I need.
Created attachment 165240 [details] ebuild for media-tv/ivtv-utils-1.3.0 bump. mods please reassign to component "ebuilds". Attached new ebuild for stable upstream release (ivtv-utils-1.3.0). Ebuild-Changelog: - Adjusted package description - replaced svn source by regular source - removed svn related stuff - replaced eerror by ewarn when kernel version does not fit - adjusted postinstall messages Further tweaking may be appropriate. Works on x86.
(In reply to comment #2) > Created an attachment (id=165240) [edit] > ebuild for media-tv/ivtv-utils-1.3.0 > > Further tweaking may be appropriate. Works on x86. This ebuild works straight away on amd64 too.
there's an ivtv-utils package in the tree now. give it a whirl.
CONFIG_CHECK="!VIDEO_HELPER_CHIPS_AUTO" made the emerge of this ebuild fail for me, but that's now a valid config option for the in-kernel driver. IMHO the real problem is that all the ivtv driver related stuff (dependencies and config checks) should be removed from this ebuild: they don't apply to these utilites themselves. I can create a patch for that if needed.
Well, from my perspective, as I only have pvr150 boards, it does prompt you to remove some unnecessary drivers from the kernel. I too was using that, but after I got this error, I went back and reconfigured my kernel, removing the video_helper_chips_auto, and I cleared all of the additional modules that were being compiled, except for the IVTV one. I was a bit worried about functionality, but it does work fine. The other devices are unnecessary, unless you have capture cards that are supported only through the helper, BUT, you're probably right, the ebuild really doesn't need to check that.
Created attachment 169572 [details, diff] Fix ebuild description, fix path for perl utils First, here are two small fixes...
(In reply to comment #6) > Well, from my perspective, as I only have pvr150 boards, it does prompt you to > remove some unnecessary drivers from the kernel. I too was using that, but > after I got this error, I went back and reconfigured my kernel, removing the > video_helper_chips_auto, and I cleared all of the additional modules that were > being compiled, except for the IVTV one. I was a bit worried about > functionality, but it does work fine. The other devices are unnecessary, > unless you have capture cards that are supported only through the helper, BUT, > you're probably right, the ebuild really doesn't need to check that. > I have a pvr-250 and an another less known ivtv card (club3d zap-tv). They need the saa7115, msp3400, cx25840, cx23416 helper modules. However, selecting ivtv now forces all of them to be built regardless of VIDEO_HELPER_CHIPS_AUTO, so I admit it does not makes much sense, but it does (or should) not do any harm either. Instead of fixing just that check, I still propose a more radical ebuild surgery. Patch follows shortly...
Created attachment 169576 [details, diff] Remove unneeded stuff
Are there any plans for ivtv-utils unmasking?
This ebuild prevents the new linux-headers-2.6.27-r2 from being merged, due to "collisions". >>> Completed installing linux-headers-2.6.27-r2 into /var/tmp/portage/sys-kernel/linux-headers-2.6.27-r2/image/ >>> Installing sys-kernel/linux-headers-2.6.27-r2 * checking 591 files for package collisions * Messages for package sys-kernel/linux-headers-2.6.27-r2: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/include/linux/ivtv.h * /usr/include/linux/ivtvfb.h * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * media-tv/ivtv-utils-1.3.0 * /usr/include/linux/ivtv.h * /usr/include/linux/ivtvfb.h * * Package 'sys-kernel/linux-headers-2.6.27-r2' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. Result of "portageq owners / /usr/include/linux/ivtv.h /usr/include/linux/ivtvfb.h" media-tv/ivtv-utils-1.3.0 /usr/include/linux/ivtv.h /usr/include/linux/ivtvfb.h
