Author |
Message |
Jet_Jaguar
|
Posted: Thu Nov 11, 2004 1:07 pm |
|
Joined: Thu Oct 07, 2004 12:56 am
Posts: 26
Location:
Central California, USA
|
I can't tell, from reading the docs, the wiki, and this forum, how much configuration I should do for setting up a PVR 350. I have an old WinTV card, which also resides in the same box, and I can watch TV using it and xawtv (but not in MythTV, one question at a time, though.)
I've looked through /etc/mythtv/modules/ivtv, and it appears to be okay.
Also, all of the docs seem to be for TV out, do I *need* to set it up for TV out?
|
|
Top |
|
 |
ceenvee703
|
Posted: Thu Nov 11, 2004 2:06 pm |
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
If you don't use the 350 for TV out, it becomes very easy, almost brain-dead easy, easy enough for me to do it. At that point it's basically just a 250, and KnoppMyth detects it automagically and it pretty much works right out of the box.
The hard stuff comes when you try to use it for TV out. It looked like enough of a hassle that I never tried it, although many of the threads here and on the wiki look very helpful.
|
|
Top |
|
 |
Jet_Jaguar
|
Posted: Sat Nov 13, 2004 7:24 pm |
|
Joined: Thu Oct 07, 2004 12:56 am
Posts: 26
Location:
Central California, USA
|
Well, it isn't. I've recompiled the ivtv drivers, run searches here, and on the ivtv and MythTV mailing lists, and I've really come up with nothing.
So I'm asking for help in Troubleshooting. There's a lot of little things I think I'm missing:
For example: 1) I can use xawtv to quickly see what's up with the WinTv (BTTV) card. Can I do this with the 350 and the ivtv drivers?
2) How can I quickly tell which /dev/video the drivers have mapped to which video card? (I would kill for something like Device Manager in Windows - does KnoppMyth have something similar?)
3) is there any way to unload and reload the driver modules without rebooting?
4) Also, much like the guy in this other post, when I run
Code: modprobe tveeprom dmesg|grep idx
I get " tvee: tuner=<unknown> (idx=68, type=-1) " Now, according to spectro, I will need to patch Video for Linux. How can I do this? I read some docs, but my attempts failed.
|
|
Top |
|
 |
cesman
|
Posted: Sat Nov 13, 2004 9:03 pm |
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
1. No.
2. If you're not using bootspalsh (or use verbose mode it you are), our scripts will tell you what card(s) it found. The order of the card tell what /dev/videoX it is... Code: dmesg | more as well.
3. ?
_________________ cesman
When the source is open, the possibilities are endless!
|
|
Top |
|
 |
Jet_Jaguar
|
Posted: Sat Nov 13, 2004 9:32 pm |
|
Joined: Thu Oct 07, 2004 12:56 am
Posts: 26
Location:
Central California, USA
|
Okay, so now I've taken out the WinTV card, and I'm getting snow on the 350. Well ... that's something, anyway.
cesman wrote: 2. If you're not using bootspalsh (or use verbose mode it you are), our scripts will tell you what card(s) it found. The order of the card tell what /dev/videoX it is... Code: dmesg | more as well. I using knoppmyth, so whatever comes with that. I do get some output during startup, though, so I'll check that out. The output of dmesg isn't exactly plain, though. Right now, it looks as though several "tuners" are being loading, I'm assuming that's because of the 350s various inputs. cesman wrote: 3. ?
Back in the old days of Netware 3.x, you could load and unload drivers in that OS. So if you had, say, three network cards in a system, you could unload the drivers for one, then reload it with different options. It could be the first, second, whatever. Of course, this was in the days of EISA, not at all recent. I really find it strange that so much functionality has been lost with "modern" systems, though.
Can anyone walk me through patching the kernel for Video for linux? As you can tell, I'm a linux Newbie (mostly.) I got the hardware I'm using, such as the 350, the chaintec 7nif2 motherboard, etc. particularly because all the docs said it would be auto-detected, and it's been a disappointing experience so far.
|
|
Top |
|
 |
cesman
|
Posted: Sat Nov 13, 2004 10:59 pm |
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
I know what you meant on question 3 (long drawn out answer related to ivtv)... rmmod will remove a module. You need to remove multiple modules in order to completely remove ivtv. If you search the forum (sorry, that is what I'd have to do), you'll find posts on installing the latest v4l. You can also go to here for info on v4l. Everything on the motherboard should work, the 350 should work... I cannot help that the tuner type has changed. Nor can you expect a 2 person development team to keep up on all the hardware and software changes. I'm not picking on you, just stating the realty of the situation.
_________________ cesman
When the source is open, the possibilities are endless!
|
|
Top |
|
 |
Jet_Jaguar
|
Posted: Sun Nov 14, 2004 12:35 am |
|
Joined: Thu Oct 07, 2004 12:56 am
Posts: 26
Location:
Central California, USA
|
Thank you for your support. It does help to know that someone is at least reading my message.
So I've been working on this all night, and I've finally, finally got both cards on the system. Haven't tested recording, though.
But his is what I've done:
I've followed the instructions at the KnoppMythWiki on installing the driver for the 350, but I replaced the url in the wget line in order to download a release candidate for ivtv, found here:
http://67.18.1.101/~ckennedy/ivtv/ivtv- ... 0-rc2j.tgz
I did the make install thang, and from there, I experimented with /etc/mythtv/modules/ivtv file. I ended up with the following file:
Code: alias char-major-81 videodev alias char-major-61 lirc_i2c options ivtv debug=1 #options ivtv tuner type=2 #options ivtv tuner type=44 #options ivtv tuner type=47
#options ivtv tuner type=39 options tuner type=39 #options ivtv tuner type=50 #options ivtv tuner type=68 options msp3400 once=1 simple=1 add below ivtv msp3400 saa7115 tuner add above ivtv lirc_dev lirc_i2c post-install ivtv /usr/local/bin/ivtvctl -d /dev/video1 -u 0x3000 post-install ivtv /usr/local/bin/ivtvctl -d /dev/video16 -u 0x3000 post-install ivtv /usr/local/bin/ivtvctl -d /dev/video32 -u 0x3000 post-install ivtv /usr/local/bin/ivtvctl -d /dev/video224 -u 0x3000
I don't really know what the last four lines do, but I believe that they set different inputs to different /dev files. Also, not the I used the options tuner type=39 line as opposed to options ivtv tuner type=39 because it didn't work with ivtv in there.
Edit: I forgot one thing: I had to play PCI musical chairs with the cards. As it stands now, I have the WinTV card in slot 1 (the one next to the AGP slot,) slot 2 is empty, and I have the 350 in slot 3.
|
|
Top |
|
 |