[mythtv-users] Almost there
jcw at wilsonet.com
Wed Oct 6 01:26:19 UTC 2004
On Tuesday 05 October 2004 17:54, Matt Hannan wrote:
> OK, I am having some issues getting the television end of things working.
> Let's see if I can present this ala Jarod's Guide:
> First, the software:
> Second, the hardware:
> Abit NF7-S v2 w/ onboard sound
> Third, what makes me unique:
> Running with my personal account (not MythTV account)
> Running on my CRT...no TV
> I think my problems start at about section 10 of Jarod's Guide for FC2
> and has a lot to do with ivtv.
> Here is my modprobe.conf:
> #IVTV Section
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> alias char-major-81-1 ivtv
Keep these lines. Er, wait a sec... You said you have just a PVR-350... Then
yank the 81-1 line, that would be for a second card...
> options ivtv ivtv_debug=1 yuv_buffers=60 mpg_buffers=50
> options tuner type=2
> options saa7127 enable_output=1 output_select=0
> options msp3400 once=1 simple=1
Remove all four of these lines. I'm assuming you're not using the 350's tv
output, judging by the lack of ivtv-fb anywhere in your modprobe.conf.
> ivtv: ==================== START INIT IVTV ====================
> Oct 5 10:46:23 wilbur kernel: ivtv: version 0.1.10
> (0.1.10-48_pre2_ck100zz.rhfc2.at) loading Oct 5 10:46:23 wilbur kernel:
> ivtv: Linux version: 2.6.8-1.541_10.rhfc2.at 686 REGPARM gcc-3.3 Oct 5
> 10:46:23 wilbur kernel: ivtv: In case of problems please include the debug
> info Oct 5 10:46:23 wilbur kernel: ivtv: between the START INIT IVTV and
> END INIT IVTV lines when Oct 5 10:46:23 wilbur kernel: ivtv: mailing the
> ivtv-devel mailinglist. Oct 5 10:46:23 wilbur kernel: ivtv: Autodetected
> WinTV PVR 350 card Oct 5 10:46:23 wilbur kernel: ivtv: Found an iTVC15
> based chip
> Oct 5 10:46:23 wilbur kernel: ivtv: Unreasonably low latency timer,
> setting to 64 (was 32) Oct 5 10:46:23 wilbur kernel: ivtv: pci: PCIBUS
> detected device: 0x01e0 vendor: 0x10de Oct 5 10:46:23 wilbur kernel: ivtv:
> i2c attach [client=tveeprom,ok] Oct 5 10:46:23 wilbur kernel: ivtv:
> Tuner Type 2, Tuner formats 0x00001000, Radio: yes, Model 0x00a93493,
> Revision 0x00000001 Oct 5 10:46:23 wilbur kernel: ivtv: NTSC tuner
> Oct 5 10:46:23 wilbur kernel: ivtv: Radio detected
> Oct 5 10:46:23 wilbur kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv
> i2c driver #0 Oct 5 10:46:23 wilbur kernel: ivtv: i2c attach [Oct 5
> 17:55:45 wilbur kernel: ivtv: VIM Restart Oct 5 17:56:01 wilbur kernel:
> ivtv: i2c attach [client=Hauppauge IR,ok] Oct 5 17:56:32 wilbur kernel:
> ivtv: Switching standard to SECAM.
Aren't you in NTSC land? This is bad. Removing all that excess junk from
modprobe.conf should let this get auto-detected properly.
> Everything looks good, except that i2c client addr bit. What is up with
> that? Googling it only shows it in other peoples logs, but does not show
> how to fix it.
Yank all that stuff, see if things clear up, then come back to this if
problems still exist.
> Also, I do not see anything about msp3400.
Hm... You might not have the merged msp3400 installed, and the old stock
msp3400 definitely won't work, so you may have to manually modprobe
msp3400-ivtv for now... See the ivtv-dev list post from Axel re: recent
Screw it, here's what Axel said:
"There are now new rpms for both v4l and ivtv out:
o today's v4l has fresh changes in the msp3400 code, please give it a
o the ivtv rpms ship again with the msp3400, but it's been renamed to
msp3400-ivtv (in order to coexist with the msp3400 from v4l).
If the default config does not work (which will use v4l's msp3400),
please try to
and check again. If there is improvement it is due to differences in
v4l's vs ivtv's msp3400 code, and it would be good to identify these."
> Can anyone see what I am doing wrong? Don't sweat too much time on it
> tonight (if you are in the USA), because the second debate starts soon.
> But, all the rest of you in the world, have fun and please help.
I'm recording the debates, I'll watch 'em later (still at work anyhow). :-)
In your lsmod output, no msp3400 at all... Definitely try modprobing
msp3400-ivtv. The i2c errors you're seeing may be a result of no msp3400
> MythTV rocks. Nothing else can touch it.
Damn skippy. Been hacking my friend's TiVo for him, first I've touched one. He
thinks its cool as hell. I think its pretty wimpy. :-)
Jarod C. Wilson, RHCE
jcw at wilsonet.com
Got a question? Read this first...
MythTV, Fedora Core & ATrpms documentation:
MythTV Searchable Mailing List Archive
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-users/attachments/20041005/dd556f74/attachment.pgp
More information about the mythtv-users