| Author |
Message |
|
msfox99
|
 Posted: Mon Aug 08, 2005 9:48 pm |
|
|
Joined: Wed Jun 29, 2005 11:17 am
Posts: 59
Location:
Cherry Hill, NJ
|
Still trying to debug my live tv....
My setup: PVR-250, FX5200, R5A16.
I read at the ivtv wiki to try modprobe tveeprom to see what it says. I get the following errors:
Code: root@mythtv:~# modprobe tveeprom
WARNING: /etc/mythtv/modules/ivtv line 7: ignoring bad line starting with '/sbin/modprobe'
WARNING: /etc/modprobe.d/lirc line 3: ignoring bad line starting with 'lirc_i2c'
My ivtv has in it: Code: alias char-major-81 videodev
alias char-major-61 lirc_i2c
#options ivtv debug=1
#options tuner type=0
options msp3400 once=1 simple=1
install ivtv /sbin/modprobe tuner; /sbin/modprobe msp3400; /sbin/modprobe saa7115; /sbin/modprobe
--ignore-install ivtv
/sbin/modprobe ivtv-fb
remove ivtv /sbin/modprobe -r --ignore-remove ivtv && /sbin/modprobe -r saa7115 && /sbin/modprobe -r msp3400 &&
/sbin/modprobe -r tuner
And my lirc has in it: Code: alias char-major-61 lirc_i2c
install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
lirc_i2c
Can someone lend some assitance as to what is wrong with these lines? Still somewhat of a newbie here. I assume if the modprobe commands aren't working, ivtv won't work properly. My symptom is only getting picture on 2 channels, the rest are static. Also, remote not working.
Thanks,
Mike
|
|
| Top |
|
 |
|
mstralka
|
Posted: Mon Aug 08, 2005 9:53 pm |
|
|
Joined: Sun Jul 31, 2005 6:24 am
Posts: 7
|
Not sure if this will help, but here's my /etc/mythtv/modules/ivtv file. I have R516 and PVR-250
Code: alias char-major-81 videodev
alias char-major-81 ivtv
alias char-major-61 lirc_i2c
#options ivtv debug=1
#options tuner type=2
options msp3400 once=1 simple=1
install ivtv /sbin/modprobe tuner; /sbin/modprobe msp3400; /sbin/modprobe saa7115; /sbin/modprobe --ignore-install ivtv
remove ivtv /sbin/modprobe -r --ignore-remove ivtv && /sbin/modprobe -r saa7115 && /sbin/modprobe -r msp3400 && /sbin/modprobe -r tuner
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Aug 08, 2005 9:59 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
At a guess you cut and pasted these and inadvertently corrupted them or missed warnings about how the long lines had been word wrapped.
After the line that reads:
Code: options msp3400 once=1 simple=1 The should be only two very long lines. One that starts with "install" and one which starts with "remove". Also make sure you get rid of any VT characters. The hexdump of mine looks like this: Code: root@black2:~# hd /etc/mythtv/modules/ivtv
00000000 61 6c 69 61 73 20 63 68 61 72 2d 6d 61 6a 6f 72 |alias char-major|
00000010 2d 38 31 20 76 69 64 65 6f 64 65 76 0a 61 6c 69 |-81 videodev.ali|
00000020 61 73 20 63 68 61 72 2d 6d 61 6a 6f 72 2d 36 31 |as char-major-61|
00000030 20 6c 69 72 63 5f 69 32 63 0a 6f 70 74 69 6f 6e | lirc_i2c.option|
00000040 73 20 6d 73 70 33 34 30 30 20 6f 6e 63 65 3d 31 |s msp3400 once=1|
00000050 20 73 69 6d 70 6c 65 3d 31 0a 69 6e 73 74 61 6c | simple=1.instal|
00000060 6c 20 69 76 74 76 20 2f 73 62 69 6e 2f 6d 6f 64 |l ivtv /sbin/mod|
00000070 70 72 6f 62 65 20 74 75 6e 65 72 3b 20 2f 73 62 |probe tuner; /sb|
00000080 69 6e 2f 6d 6f 64 70 72 6f 62 65 20 6d 73 70 33 |in/modprobe msp3|
00000090 34 30 30 3b 20 2f 73 62 69 6e 2f 6d 6f 64 70 72 |400; /sbin/modpr|
000000a0 6f 62 65 20 73 61 61 37 31 31 35 3b 20 2f 73 62 |obe saa7115; /sb|
000000b0 69 6e 2f 6d 6f 64 70 72 6f 62 65 20 2d 2d 69 67 |in/modprobe --ig|
000000c0 6e 6f 72 65 2d 69 6e 73 74 61 6c 6c 20 69 76 74 |nore-install ivt|
000000d0 76 0a 72 65 6d 6f 76 65 20 69 76 74 76 20 2f 73 |v.remove ivtv /s|
000000e0 62 69 6e 2f 6d 6f 64 70 72 6f 62 65 20 2d 72 20 |bin/modprobe -r |
000000f0 2d 2d 69 67 6e 6f 72 65 2d 72 65 6d 6f 76 65 20 |--ignore-remove |
00000100 69 76 74 76 20 26 26 20 2f 73 62 69 6e 2f 6d 6f |ivtv && /sbin/mo|
00000110 64 70 72 6f 62 65 20 2d 72 73 61 61 37 31 31 35 |dprobe -rsaa7115|
00000120 20 26 26 20 2f 73 62 69 6e 2f 6d 6f 64 70 72 6f | && /sbin/modpro|
00000130 62 65 20 2d 72 20 6d 73 70 33 34 30 30 20 26 26 |be -r msp3400 &&|
00000140 20 2f 73 62 69 6e 2f 6d 6f 64 70 72 6f 62 65 20 | /sbin/modprobe |
00000150 2d 72 20 74 75 6e 65 72 0a |-r tuner.|
00000159
root@black2:~# wc -l /etc/mythtv/modules/ivtv
5 /etc/mythtv/modules/ivtv
When you're done fixing yours it should look the pretty much the same... Notice that "0a" (LF) only occurs 5 times and 0d (CR) and 0b (VT) do not occur at all.
|
|
| Top |
|
|
|
msfox99
|
Posted: Tue Aug 09, 2005 7:52 am |
|
|
Joined: Wed Jun 29, 2005 11:17 am
Posts: 59
Location:
Cherry Hill, NJ
|
|
Thanks for the replies.
I checked the ivtv files, and the lines starting with "install" and "remove" are single long lines, they just got screwed up when I pasted them into my browser for posting here.
I do have an extra line, though, /sbin/modprobe ivtv-fb
That is probably the problem...I see now that it is the 7th line. I guess if it just complaining about the ivtv-fb line, it is probably not my problem. I won't be able to try anything until I get home tonight.
Any thoughts on the lirc_i2c error?
|
|
| Top |
|
|
|
tjc
|
Posted: Tue Aug 09, 2005 6:35 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
msfox99 wrote: I do have an extra line, though, /sbin/modprobe ivtv-fb
What I was trying to tell you is that "line" is supposed to be part of the one before it. That was why I posted the hex dump output, so it would be obvious that there shouldn't be an extra LF (0a) or whatever there. You need to fix that.
- With vi go to the 6th line and use the "join lines" command 'J' (although I can never remember if it joins up or down). This may not work if you've got a really funky character there.
- With nano or emacs go to the 6th line - hit Ctrl-E (to move to the end of the line), Space (if there isn't already one there), and finally Ctrl-D (to delete to the right of the cursor, i.e. the LF or whatever). This should work regardless.
|
|
| Top |
|
|
|
msfox99
|
Posted: Tue Aug 09, 2005 7:53 pm |
|
|
Joined: Wed Jun 29, 2005 11:17 am
Posts: 59
Location:
Cherry Hill, NJ
|
Thanks again for the reply.
Now I am a little confused. Based on earlier posts, I made the ivtv file look exactly like yours and mstralka's, which means I deleted the text noted in the previous post (... ivtv-fb). The lines starting with "install" and "remove" already were single long lines. I don't think you have the ivtv-fb reference in your file.
If you are saying I need to add this back into the file at the end of the "install" line, I tried that too, but it doesn't help. I don't get an error, but I still have only a few channels from my cable, and static on the rest. I have tried both us-cable and us-cable-hrc. Are there any others I should try maybe?
Putting /sbin/modprobe ivtv-fb at the end of the line after "ivtv" doesn't seem to follow the syntax, but I am no expert, obviously 
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Aug 10, 2005 12:23 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Are you still getting the same errors?
Did you use the hd command as shown in the example to make sure that there weren't any funky characters in there? If you don't know what that means, how about post the output here so we can debug it? I don't normally resort to low level file dumps unless I suspect things are not what they appear to be.
What about the rest of your hardware?
You''re not giving us enough feedback, which makes this like trying to determine which circuit breaker in the basement, controls which plugs on the second floor, when the person on the second floor who is supposed to be watching things isn't paying attention.
|
|
| Top |
|
|
|
msfox99
|
Posted: Wed Aug 10, 2005 9:29 am |
|
|
Joined: Wed Jun 29, 2005 11:17 am
Posts: 59
Location:
Cherry Hill, NJ
|
I already did the hex dump, and mine is the same as yours (after I removed the ivtv-fb), except that in the "remove" line you have "-rsaa7115", and mstralka and I have "-r saa7115" which I think is correct.
I am no longer getting the error from the ivtv file once I removed the ivtv-fb reference. I added that line based on a post here on the forum that was talking about the PVR-350 (I have the 250). I see now that the I added it as a seperate line (which caused the error) instead of at the end of the line. I did a search and found that ivtv-fb is for a frame buffer kernel module. I am guessing the the PVR-350 post said it was needed because maybe it is used for the 350's TV out, which I don't have. Only a guess.
So just to summarize: If I choose us-cable in the setup, I get a single TV station repeated on a few upper channels, and static everywhere else. If I choose us-cable-hrc, I get static everywhere. (I am in New Jersey and have Comcast.) Since I do get that one channel, I am guessing that ivtv is basically working, and I am only having some sort of tuning problem. I turned my attention to the ivtv file because I was getting that error, but now I see that I caused it.
My H/W: Althon XP 3000, nForce chipset, 1 GB mem, 250 GB hard drive, nVidia FX5200, PVR-250.
I have done alot of searching both here and over at the ivtv web site and wiki, and haven't been able to come up with anything yet. I feel I am so close 
And, by the way, I am still getting the error from the /etc/modprobe.d/lirc indicated in the first post above (and my remote doesn't work, but I am more interested in getting TV to work 1st  ).
Once again, I really appreciate the help. Thanks for staying with me tjc.
Mike
|
|
| Top |
|
|
|
msfox99
|
Posted: Wed Aug 10, 2005 7:51 pm |
|
|
Joined: Wed Jun 29, 2005 11:17 am
Posts: 59
Location:
Cherry Hill, NJ
|
|
Another note:
I tried tonight mplayer /dev/video and ptune.pl, and it behaves the same way as under MythTV, that is, one channel in a few places, and the rest static.
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Aug 10, 2005 9:45 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Exit the front end and run mythtv-setup (I think Alt-S will do that or you can do it from an xterm).
Under "1) General" on page three make sure you''ve selected NTSC and US-Cable.
Under "2) Capture Cards" chose "MPEG encoder PVR-250..." set your video device to "/dev/video0" and your default input to "tuner 0" - NOTE - This presumes that you're making a direct connection to the cable rather than going through a tuner box or other device!!!
Under "3) Video Sources" (really listings) create one called Cable and choose No.Am. data direct and the default frequency set.
Under "4) Input Connections" make sure you only associate Cable with Tuner 0!!! All the rest should be NONE.
OBTW - Did you verify that the ivtv drivers are correctly recognizing the tuner type and that you don't need a newer versio of the driver? I've posted a sed command around here somewhere for extracting the relevant part of the log file...
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Aug 10, 2005 9:56 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
BTW - Here is the sed command I mentioned...
Code: sed -n '/= START INIT IVTV =/,/= END INIT IVTV =/p' </var/log/messages | more
|
|
| Top |
|
|
|
msfox99
|
Posted: Thu Aug 11, 2005 6:16 pm |
|
|
Joined: Wed Jun 29, 2005 11:17 am
Posts: 59
Location:
Cherry Hill, NJ
|
I tried your setup instructions, but it was already setup that way, and still no good. Here is the boot log:
Code: Aug 11 16:09:59 mythtv kernel: ivtv: ==================== START INIT IVTV ====================
Aug 11 16:09:59 mythtv kernel: ivtv: version 0.2.0 (rc3j) loading
Aug 11 16:09:59 mythtv kernel: ivtv: Linux version: 2.6.11.9-chw-2 SMP preempt 586 gcc-3.3
Aug 11 16:09:59 mythtv kernel: ivtv: In case of problems please include the debug info
Aug 11 16:09:59 mythtv kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when
Aug 11 16:09:59 mythtv kernel: ivtv: mailing the ivtv-devel mailinglist.
Aug 11 16:09:59 mythtv kernel: ivtv: Autodetected WinTV PVR 250 card
Aug 11 16:09:59 mythtv kernel: ivtv: Found an iTVC16 based chip
Aug 11 16:09:59 mythtv kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 19
Aug 11 16:09:59 mythtv kernel: ACPI: PCI interrupt 0000:02:07.0[A] -> GSI 19 (level, high) -> IRQ 19
Aug 11 16:09:59 mythtv kernel: ivtv: XXX PCI device: 0x01e0 vendor: 0x10de
Aug 11 16:09:59 mythtv kernel: ivtv: i2c attach [client=(tuner unset),ok]
Aug 11 16:09:59 mythtv kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
Aug 11 16:09:59 mythtv kernel: msp34xx: ivtv version
Aug 11 16:09:59 mythtv kernel: msp34xx: init: chip=MSP3445G-B8, has NICAM support, simple (D) mode, simpler (G)
no-thread mode
Aug 11 16:09:59 mythtv kernel: msp34xx: $Id$ compiled on: May 24 2005 00:43:28
Aug 11 16:09:59 mythtv kernel: ivtv: i2c attach [client=MSP3445G-B8,ok]
Aug 11 16:09:59 mythtv kernel: saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
Aug 11 16:09:59 mythtv kernel: saa7115: detecting saa7115 client on address 0x42
Aug 11 16:09:59 mythtv kernel: saa7115: writing init values
Aug 11 16:09:59 mythtv kernel: ivtv: i2c attach [client=saa7115[0],ok]
Aug 11 16:09:59 mythtv kernel: saa7115: status: (1E) 0x00, (1F) 0xc0
Aug 11 16:09:59 mythtv kernel: ivtv: i2c attach [client=tveeprom,ok]
Aug 11 16:09:59 mythtv kernel: tveeprom: Hauppauge: model = 32062, rev = C199, serial# = 8054742
Aug 11 16:09:59 mythtv kernel: tveeprom: tuner = <unknown> (idx = 99, type = 0)
Aug 11 16:09:59 mythtv kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
Aug 11 16:09:59 mythtv kernel: tveeprom: audio_processor = MSP3445 (type = 12)
Aug 11 16:09:59 mythtv kernel: ivtv: Tuner Type 0, Tuner formats 0x00001000, Radio: yes, Model 0x008d1659,
Revision 0x00000001
Aug 11 16:09:59 mythtv kernel: ivtv: NTSC tuner detected
Aug 11 16:09:59 mythtv kernel: ivtv: Radio detected
Aug 11 16:09:59 mythtv kernel: ivtv: Encoder revision: 0x02040011
Aug 11 16:09:59 mythtv kernel: ivtv: Configuring WinTV PVR 250 card with 5 streams
Aug 11 16:09:59 mythtv kernel: ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total
Aug 11 16:09:59 mythtv kernel: ivtv: Registered v4l2 device, streamtype 0 minor 0
Aug 11 16:09:59 mythtv kernel: ivtv: Create DMA stream 1
Aug 11 16:09:59 mythtv kernel: ivtv: Registered v4l2 device, streamtype 1 minor 32
Aug 11 16:09:59 mythtv kernel: ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total
Aug 11 16:09:59 mythtv kernel: ivtv: Registered v4l2 device, streamtype 2 minor 224
Aug 11 16:09:59 mythtv kernel: ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total
Aug 11 16:09:59 mythtv kernel: ivtv: Registered v4l2 device, streamtype 3 minor 24
Aug 11 16:09:59 mythtv kernel: ivtv: Create stream 4
Aug 11 16:09:59 mythtv kernel: ivtv: Registered v4l2 device, streamtype 4 minor 64
Aug 11 16:09:59 mythtv kernel: ivtv: Setting Tuner 0
Aug 11 16:09:59 mythtv kernel: tuner 2-0061: type set to 0 (Temic PAL (4002 FH5))
Aug 11 16:09:59 mythtv kernel: saa7115: decoder set input (4)
Aug 11 16:09:59 mythtv kernel: saa7115: now setting Composite input
Aug 11 16:09:59 mythtv kernel: ivtv: Setting audio matrix to input 3, output 1
Aug 11 16:09:59 mythtv kernel: ivtv: Switching standard to NTSC.
Aug 11 16:09:59 mythtv kernel: ivtv: ivtv_enc_thread: pid = 1796, itv = 0xf9158aa0
Aug 11 16:09:59 mythtv kernel: saa7115: decoder set norm NTSC
Aug 11 16:09:59 mythtv kernel: saa7115: set audio: 0x01
Aug 11 16:09:59 mythtv kernel: ivtv: Initialized WinTV PVR 250, card #0
Aug 11 16:09:59 mythtv kernel: ivtv: ==================== END INIT IVTV ====================
I plan to do a little more searching over to the ivtv site since I think that is the problem. How do I find out what version of ivtv I have?
Thanks.
|
|
| Top |
|
|
|
tjc
|
Posted: Thu Aug 11, 2005 7:07 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
This is usually a bad sign... Search for threads about PVR-250 model 980...
Quote: Aug 11 16:09:59 mythtv kernel: tveeprom: tuner = <unknown> (idx = 99, type = 0)
You may be able to configure around it, but you may just have to wait until the drivers catch up...
|
|
| Top |
|
|
|
msfox99
|
Posted: Fri Aug 12, 2005 7:45 pm |
|
|
Joined: Wed Jun 29, 2005 11:17 am
Posts: 59
Location:
Cherry Hill, NJ
|
|
tjc, I think you are right on the money. I went over to the ivtv sight FAQ's, and they recommended peeling the label off of the tuner to see what it actually is. i did that and found, "TCL-2002N-5H." I got my hopes up when I saw "TUNER_TCL_2002N" in the tuner.h file, with a tuner type of 50.
I entered this into the ivtv config file, but it didn't help. I am thinking of downloading the latest version of ivtv. R5A16 comes with 0.2.0-rc3j, which is the latest stable release. They are up to 0.3.3k, with new versions coming very frequently.
I am not sure why it shouldn't work with the current ivtv version if this tuner is in the include file, but who knows.
I find it amazing how many different tuners these guys use on the alleged same model of the 250 card. It makes ours and the guys maintaining ivtv lives a little more challenging.
|
|
| Top |
|
|
|
Khan
|
Posted: Sun Aug 21, 2005 2:02 pm |
|
|
Joined: Sun Mar 06, 2005 9:55 am
Posts: 34
|
msfox99 wrote: tjc, I think you are right on the money. I went over to the ivtv sight FAQ's, and they recommended peeling the label off of the tuner to see what it actually is. i did that and found, "TCL-2002N-5H." I got my hopes up when I saw "TUNER_TCL_2002N" in the tuner.h file, with a tuner type of 50.
Have you been able to get this configuration working yet? I have the EXACT same PVR-250 and have tried several versions of ivtv. None have so far worked. I can't put into words how incredibly angry I am at Happauge.
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
