[gentoo-user] Re: More ivtv problems (I think) (WAS: Re: ivtv-0.4.5 fails to build for kernel 2.6.16-gentoo-r9)

[Michael Sullivan]

On Sun, 2006-06-11 at 08:24 -0500, Michael Sullivan wrote:
> On Sat, 2006-06-10 at 18:30 -0500, Michael Sullivan wrote:
> > I've been trying to build ivtv-0.4.5 for my gentoo-sources
> > kernel-2.6.16-r9 for awhile now, but it keeps failing with the following
> > output:
> >
> > camille ~ # emerge ivtv
> > Calculating dependencies ...done!
> > >>> emerge (1 of 1) media-tv/ivtv-0.4.5 to /
> > >>> md5 files   ;-) ivtv-0.4.0-r3.ebuild
> > >>> md5 files   ;-) ivtv-0.4.2.ebuild
> > >>> md5 files   ;-) ivtv-0.4.5.ebuild
> > >>> md5 files   ;-) ivtv-0.6.2.ebuild
> > >>> md5 files   ;-) files/ivtv
> > >>> md5 files   ;-) files/ivtv-0.4.0-ppc-odw.patch
> > >>> md5 files   ;-) files/digest-ivtv-0.4.0-r3
> > >>> md5 files   ;-) files/digest-ivtv-0.4.2
> > >>> md5 files   ;-) files/ivtv-0.4.0-maxdev.patch
> > >>> md5 files   ;-) files/digest-ivtv-0.4.5
> > >>> md5 files   ;-) files/digest-ivtv-0.6.2
> > >>> md5 files   ;-) files/ivtv-0.6.2-ppc-fix.patch
> > >>> md5 src_uri ;-) ivtv-0.4.5.tar.gz
> > >>> md5 src_uri ;-) pvr_2.0.24.23035.zip
> > >>> md5 src_uri ;-) pvr_1.18.21.22254_inf.zip
> >  * Determining the location of the kernel source code
> >  * Found kernel source directory:
> >  *     /usr/src/linux
> >  * Found sources for kernel version:
> >  *     2.6.16-gentoo-r9
> >  * Checking for suitable kernel configuration options...
> > [ ok ] * Checking for suitable kernel configuration options...
> > [ ok ]>>> Unpacking source...
> > >>> Unpacking ivtv-0.4.5.tar.gz to /var/tmp/portage/ivtv-0.4.5/work
> > >>> Unpacking pvr_2.0.24.23035.zip to /var/tmp/portage/ivtv-0.4.5/work
> > >>> Source unpacked.
> >  * Preparing ivtv module
> > created ivtv-svnversion.h
> > make -C /usr/src/linux
> > M=/var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver modules
> > make[1]: Entering directory `/usr/src/linux-2.6.16-gentoo-r9'
> >   CC [M]  /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.o
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function
> > `saa7127_write':/var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:346: error: structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_vps':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:372: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:384: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_cc':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:407: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:415: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_xds':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:433: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:441: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_wss':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:458: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:467: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_video_enable':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:479: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:483: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_std':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:499: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:503: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_output_type':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:554: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_set_input_type':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:571: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:576: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_command':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:643: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:644: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:645: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:647: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:649: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:650: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: In
> > function `saa7127_attach':
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:734: error:
> > `I2C_CLIENT_ALLOW_USE' undeclared (first use in this function)
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:734: error:
> > (Each undeclared identifier is reported only once
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:734: error:
> > for each function it appears in.)
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:737: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:746: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:762: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:779: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:785: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:790: error:
> > structure has no member named `name'
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c: At top
> > level:
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:842: error:
> > unknown field `name' specified in initializer
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:842:
> > warning: initialization makes integer from pointer without a cast
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:844: error:
> > unknown field `flags' specified in initializer
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:844: error:
> > `I2C_DF_NOTIFY' undeclared here (not in a function)
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:844: error:
> > initializer element is not constant
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:844: error:
> > (near initialization for `i2c_driver_saa7127.class')
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:849: error:
> > unknown field `owner' specified in initializer
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:849:
> > warning: missing braces around initializer
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:849:
> > warning: (near initialization for `i2c_driver_saa7127.driver')
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:849:
> > warning: initialization from incompatible pointer type
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:851: error:
> > initializer element is not constant
> > /var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.c:851: error:
> > (near initialization for `i2c_driver_saa7127.driver')
> > make[2]: ***
> > [/var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver/saa7127.o] Error 1
> > make[1]: ***
> > [_module_/var/tmp/portage/ivtv-0.4.5/work/ivtv-0.4.5/driver] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.6.16-gentoo-r9'
> > make: *** [all] Error 2
> >
> > !!! ERROR: media-tv/ivtv-0.4.5 failed.
> > !!! Function linux-mod_src_compile, Line 515, Exitcode 2
> > !!! Unable to make                                  KDIR=/usr/src/linux
> > all.
> > !!! If you need support, post the topmost build error, NOT this status
> > message.
> >
> >
> > Should I submit this as a bug, or is it just my system?  If it is my
> > system, how can I fix it?  Here's my uname info, if it would be helpful:
> >
> > camille ~ # uname -a
> > Linux camille 2.6.16-gentoo-r9 #1 SMP Wed Jun 7 09:20:49 CDT 2006 i686
> > Intel(R) Celeron(R) CPU 2.66GHz GNU/Linux
> >
>
> I got an email from bugs.gentoo.org this morning about using ivtv-0.6.2
> with 2.6.16 kernels.  I unmasked it in /etc/portage/package.unmask and
> emerged it.  I then rebooted with my 2.6.16-gentoo-r9 kernel.
> Everything loaded to my satisfaction on startup, but when I run
> mythfrontend and ask to Watch Live TV, the screen flashes once, and puts
> me back at the menu.  This happens every time I ask to watch live tv
> with the current kernel and ivtv-0.6.2  I'm not sure if this is the
> kernel's fault or ivtv or something else.  /var/log/mythtv/mythbackend
> had no useful information - It just says "Starting up as the master
> server."  /var/log/messages has nothing.  dmesg has some information,
> but everything seems right to me:
>
> camille ~ # dmesg | grep 'ivtv'
> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.6.2 (tagged release) loading
> ivtv:  Linux version: 2.6.16-gentoo-r9 SMP 486 gcc-3.4
> ivtv:  In case of problems please include the debug info between
> ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
> ivtv:  any module options, when mailing the ivtv-users mailinglist.
> ivtv0: Autodetected Hauppauge WinTV PVR-250 card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> tda9887 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
> saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv0: Encoder revision: 0x02050032
> ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB
> total)
> ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB
> total)
> ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB
> total)
> ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB
> total)
> ivtv0: Create encoder radio stream
> ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
> ivtv:  ====================  END INIT IVTV  ====================
>
> What should I do?  Until this is fixed, I'll have to use my 2.6.15-r1
> kernel with ivtv-0.4.5 .  We record a lot of stuff with MythTV, so I
> hope we can resolve this soon.  Thank you in advance for your help!

Nevermind.  ivtv-0.6.2 has been declared unstable and the bug has been
reopened...

-- 
gentoo-user@g.o mailing list