tveeprom reads the hauppauge chip which describes the hardware on the card. Tuners have no way of identifying themselves via i2c (generally speaking) so this is needed to tell what sort of tuner you have.
tveeprom was based on an exsiting module called eeprom, which does something similar, but is not made for the PVR cards. ivtv will reqeust that tveeprom be loaded automatically, but if eeprom is loaded before ivtv/tveeprom, then there will be a conflict and tveeprom won't work, and ivtv won't get tuner types, and all you'll see is static :) -tmk --- Wendell <[EMAIL PROTECTED]> wrote: > OK, this make sense. I suspected that error was in > some way > responsible. But since I installed with apt-get, I > didn't know what had > been done to monkey things up. > > Do I not need eeprom at all? I think I heard > something to the effect > that it will be loaded by ivtv automatically, so > perhaps if ivtv is > loaded after tveeprom, then the ordering will be > fine. > > I'll check it out when I get home. Thanks. > > kevin thayer wrote: > > Actually, it looks like you may have a new-enough > > version of ivtv, and you loaded the eeprom module > > before tveeprom. see this error from your post: > > > > Jan 18 20:22:18 localhost kernel: ivtv: Error -19 > > reading Hauppauge eeprom. > > Jan 18 20:22:18 localhost kernel: ivtv: Possible > > causes: the tveeprom module was not loaded, or > > Jan 18 20:22:18 localhost kernel: ivtv: the eeprom > > kernel module was loaded before the tveeprom > module. > > > > > > if you do a 'lsmod' > > and it shows eeprom is loaded, type 'rmmod eeprom' > > > > and try reloading ivtv 'rmmod ivtv;modprobe ivtv' > > > > -tmk > > > > --- John Hare <[EMAIL PROTECTED]> wrote: > > > > > >>I was going along with the Fedora Myth(TV)ology > >>HowTo and hit a wall > >>at the "test the capture card" step. That being, > I > >>can't seem to > >>capture anything but static. Looks exactly like > the > >>static on a TV > >>with no cable hooked in (assuming it's not a newer > >>TV that just shows > >>a blue screen). I actually have two 350s in there > >>and both do the > >>same thing. Although the static doesn't look > >>exactly the same. Hard > >>to explain how static is different. Anyhow, I > >>checked the cable in my > >>VCR and it's definitely not that. I believe I > have > >>the correct input > >>selected on both cards. I fiddled with the > >>/usr/lib/ivtv/ptune-ui > >>script to change channels. No effect. > >> > >>I installed ivtv via: > >> apt-get install ivtv-firmware > >> apt-get install ivtv-kmdl-$KVER > >> apt-get install ivtv > >>$KVER on my system is 2.6.10-1.741_FC3 > >> > >>I then edited /etc/modprobe.conf to include: > >># ivtv modules setup > >>alias char-major-81 videodev > >>alias char-major-81-0 ivtv > >> > >>(The instructions indicated this was for 350 users > >>NOT using the TV > >>out - one thing at a time) > >> > >>Then I did: > >> /sbin/depmod -a > >> /sbin/modprobe ivtv > >>No errors to be seen. > >> > >>But when I tried to capture video (I tried both > >>cards), static. I ran > >>/sbin/lspci -v and it seemed to produce reasonable > >>output: > >>00:08.0 Multimedia video controller: Internext > >>Compression Inc iTVC15 > >>MPEG-2 Encoder (rev 01) > >> Subsystem: Hauppauge computer works Inc. > >>WinTV PVR-350 > >> Flags: bus master, medium devsel, latency > 64, > >>IRQ 11 > >> Memory at d4000000 (32-bit, prefetchable) > >>[size=64M] > >> Capabilities: [44] Power Management version > 2 > >>00:0a.0 Multimedia video controller: Internext > >>Compression Inc iTVC15 > >>MPEG-2 Encoder (rev 01) > >> Subsystem: Hauppauge computer works Inc. > >>WinTV PVR-350 > >> Flags: bus master, medium devsel, latency > 64, > >>IRQ 10 > >> Memory at d8000000 (32-bit, prefetchable) > >>[size=64M] > >> Capabilities: [44] Power Management version > 2 > >> > >>And now the log stuff, which does show some > >>disturbing things: > >> > >>Jan 18 20:22:18 localhost kernel: ivtv: > >>==================== START > >>INIT IVTV ==================== > >>Jan 18 20:22:18 localhost kernel: ivtv: version > >>0.1.10 > >>(0.1.10-49_pre2_ck100zz.rhfc3.at) loading > >>Jan 18 20:22:18 localhost kernel: ivtv: Linux > >>version: > >>2.6.10-1.741_FC3 686 REGPARM 4KSTACKS gcc-3.4 > >>Jan 18 20:22:18 localhost kernel: ivtv: In case of > >>problems please > >>include the debug info > >>Jan 18 20:22:18 localhost kernel: ivtv: between > the > >>START INIT IVTV > >>and END INIT IVTV lines when > >>Jan 18 20:22:18 localhost kernel: ivtv: mailing > the > >>ivtv-devel mailinglist. > >>Jan 18 20:22:18 localhost kernel: ivtv: > Autodetected > >>WinTV PVR 350 card > >>Jan 18 20:22:18 localhost kernel: ivtv: Found an > >>iTVC15 based chip > >>Jan 18 20:22:18 localhost kernel: ACPI: PCI > >>interrupt 0000:00:08.0[A] > >>-> GSI 11 (level, low) -> IRQ 11 > >>Jan 18 20:22:18 localhost kernel: ivtv: > Unreasonably > >>low latency > >>timer, setting to 64 (was 32) > >>Jan 18 20:22:18 localhost kernel: ivtv: pci: VIA > >>detected device: > >>0x3205 vendor: 0x1106 > >>Jan 18 20:22:18 localhost kernel: ivtv: i2c client > >>addr: 0x50 not found! > >>Jan 18 20:22:18 localhost kernel: ivtv: Error -19 > >>reading Hauppauge eeprom. > >>Jan 18 20:22:18 localhost kernel: ivtv: Possible > >>causes: the tveeprom > >>module was not loaded, or > >>Jan 18 20:22:18 localhost kernel: ivtv: the eeprom > >>kernel module was > >>loaded before the tveeprom module. > >>Jan 18 20:22:18 localhost kernel: tuner: chip > found > >>at addr 0xc2 > >>i2c-bus ivtv i2c driver #0 > >>Jan 18 20:22:18 localhost kernel: ivtv: i2c attach > >>[client=(tuner unset),ok] > >>Jan 18 20:22:19 localhost kernel: saa7115: > Ignoring > >>new-style > >>parameters in presence of obsolete ones > >>Jan 18 20:22:19 localhost kernel: saa7115: > starting > >>probe for adapter > >>SMBus Via Pro adapter at 5000 (0x0) > >>Jan 18 20:22:19 localhost kernel: saa7115: > starting > >>probe for adapter > >>ivtv i2c driver #0 (0x10005) > >>Jan 18 20:22:19 localhost kernel: saa7115: > detecting > >>saa7115 client on > >>address 0x42 > >>Jan 18 20:22:19 localhost kernel: saa7115: writing > >>init values > >>Jan 18 20:22:19 localhost kernel: ivtv: i2c attach > >>[client=saa7115[0],ok] > >>Jan 18 20:22:19 localhost kernel: saa7115: status: > >>(1E) 0x48, (1F) 0xc0 > >>Jan 18 20:22:19 localhost kernel: saa7127: > Ignoring > >>new-style > >>parameters in presence of obsolete ones > >>Jan 18 20:22:19 localhost kernel: saa7127: video > >>encoder driver > >>version V 0.3 loaded > >>Jan 18 20:22:19 localhost kernel: saa7127: > Selecting > >>NTSC video Standard > >>Jan 18 20:22:19 localhost kernel: saa7127: > Selecting > >>S-Video+Composite > >>Jan 18 20:22:19 localhost kernel: saa7127: Turn > WSS > === message truncated === ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
