Did you select a input.
You will have to use a command like v4l!??! sorry about the completion. It's a
memory call ;))

Take a look around this.


>
>       Well, I managed to find the missing kernel options in my new
> kernel, and now the drivers load without any error messages at all!!
>
>       The only problem is that I still cannot get anything when I cat
> /dev/video0 > test.mpg.  File size remains zero no matter what I try.
>
>       I've tried using ivtv-tune -c3 to change the channel, and it
> gives me a signal detected message, but still a zero bit file size.
>
>       xawtv's hardware scan (xawtv -hwscan) finds the PVR150 and says
> /dev/video0 is "OK"  but display nothing but a blank sceen when I tell
> it to display device /dev/video0
>
>       As the /var/log/messages and /var/log/syslog are all clear of
> errors, I'm not sure what to do next :(
>
>       Please help.
>
>       Greatly appreciated.
>
> j
>
> On Thu, Nov 23, 2006 at 10:06:48AM -0800, Jadel wrote:
> >
> >     Try as I may, I cannot get anything but "i2c addr 0x44 not found
> > for command 0xc0cc5605!" when I try to capture anything with my new
> > Hauppauge PVR-150 (MCE).
> >
> >     I am running a brand new compile of 2.6.18.3 on a slackware 10.2
> > system.  All the Video Adapters are set to modules in Device Drivers,
> > Multimedia Devices, Video Capture Adapters.  Along with this, I am
> > running ivtv 0.8.1.
> >
> >     I tried to follow the HotTo on the ivtvdriver.org site, but
> > found the instructions to be slightly dated.  Even so, I tried to follow
> > them and the resulting dmesg (after modprobe ivtv) is as follows:
> >
> >
> > ivtv:  ==================== START INIT IVTV ====================
> > ivtv:  version 0.8.1 (tagged release) loading
> > ivtv:  Linux version: 2.6.18.3 mod_unload K7 REGPARM gcc-3.3
> > 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 card (cx23416 based)
> > ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> > ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> > tveeprom 6-0050: Hauppauge model 26582, rev F0B2, serial# 10076677
> > tveeprom 6-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
> > tveeprom 6-0050: TV standards NTSC(M) (eeprom 0x08)
> > tveeprom 6-0050: audio processor is CX25843 (idx 37)
> > tveeprom 6-0050: decoder processor is CX25843 (idx 30)
> > tveeprom 6-0050: has no radio, has no IR remote
> > ivtv0: Autodetected Hauppauge WinTV PVR-150
> > tuner 6-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > ivtv0: Encoder revision: 0x02050032
> > ivtv0: Registered device video0 for encoder MPEG
> > ivtv0: Registered device video32 for encoder YUV
> > ivtv0: Registered device vbi0 for encoder VBI
> > ivtv0: Registered device video24 for encoder PCM audio
> > tuner 6-0061: type set to 50 (TCL 2002N)
> > ivtv0: i2c hardware 0x00000001 (cx2584x) not found for command 0xc008561c!
> > ivtv0: i2c addr 0x44 not found for command 0x4008646f!
> > ivtv0: i2c hardware 0x00000020 (wm8775) not found for command 0x4008646d!
> > ivtv0: i2c hardware 0x00000001 (cx2584x) not found for command 0x4008646d!
> > ivtv0: i2c hardware 0x00000001 (cx2584x) not found for command 0xc008561c!
> > ivtv0: i2c hardware 0x00000001 (cx2584x) not found for command 0xc008561c!
> > ivtv0: i2c hardware 0x00000001 (cx2584x) not found for command 0xc008561c!
> > ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> > ivtv:  ====================  END INIT IVTV  ====================
> >
> >     After changing my I2C to a module in my kernel config, lsmod
> > reveals:
> >
> > Module                  Size  Used by
> > tuner                  62184  0
> > ivtv                  178448  0
> > cx2341x                 9796  1 ivtv
> > tveeprom               13712  1 ivtv
> > videodev               22528  1 ivtv
> > v4l1_compat            12484  2 ivtv,videodev
> > v4l2_common            20416  4 tuner,ivtv,cx2341x,videodev
> > i2c_nforce2             5952  0
> >
> >     I spent 8 hours yesterday reading mailing list archives and
> > searching the net for anything that might help, and found that perhaps
> > this error has to do with the v4l drivers built into the kernel?  Oh, I
> > don't know, please help :)
> >
> >     Greatly Appreciated.
> >
> > j
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>


_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to