The reason for the -ivtv versions is that the ivtv modules are branches from the mainline kernel versions, and other (non-ivtv) hardware uses them. It wouldn't be playing nice to simply remove or overwrite the kernel versions of things with our own.
audio for the [23]50 series cards is handled by the msp3400 driver. make sure you use the ivtv version. it comes up a lot to do alias msp3400 msp3400-ivtv and alias tveeprom tveeprom-ivtv in modules.conf I for one am astounded at the number of people who read the wiki and can't find their solution, but then find it on the mailing-list and do not update the wiki to help others. The whole point of the wiki system is distributed document management and it lets anyone update it. Own your solutions, people :) -tmk --- Zed Shaw <[EMAIL PROTECTED]> wrote: > Hello ivtv people. This is my first post, having > just started working > with your driver today. > > First a bit of background. I work for a company > that does lots, and > lots, and lots of digital video. We are > investigating doing a Linux > version of a solution that was originally intended > as a Windows > solution. If I'm able to implement the Linux > solution then this could > potentialy be a huge win for Linux vs. Windows in > the media area. > > My employer is also interested in hiring people who > are "video experts" > to work on our future chosen platform. At the same > time I'm trying get > our boss to donate something to the various projects > we're using. > Depending on how things go we may look at donating > straight up cash, > hardware, food, whatever I can get as a "thank you" > for all the > wonderful work put into the free stuff we use. I > push for this as the > unofficial open source "evangelist" at our company > and an open source > developer (although a chump change one). > > I'm not promising anything, but it could work out > great if I can pull > off a Linux solution. I'm currently using Fedora > FC3, PVR-250 and/or > PVR-350 with an interest in the PVR-150 cards. > Everything sort of > works, and I've got a decent "ivtv" script for use > in a redhat init.d > (which I'll donate back). > > But, there's a downside to every story, and that > downside is the sudden > appearance of parallel modules in the kernel modules > directory for > tveeprom, msp3400, and tuner all ending in "-ivtv". > Somehow, two > different sets of modules for the ivtv RPMs were > installed. This > frustrated me for the entire week, with absolutely > no explanation from > the card or any idea that the only reason I couldn't > view the Cable feed > off the tuner was simply because I was loading the > wrong tuner module. > More specifically that _modprobe ivtv was loading > the WRONG versions__. > Now that's just wrong, wrong, wrong. > > I've since replicated the problem, believe I have an > initial cause, and > have almost got the cards working again with the > correct drivers. After > 12 hours of frustration I left with the ability to > view video, but still > no audio (I may call on the list lurkers for help > with this). I'm > desperately hoping that my investigation below will > help work out how > this is happening and the problem can be fixed > permanently. > > Here's what I've determined is happening: > > 1. Like everyone else I used Jarod's wonderful > MythTV on Fedora HOWTO > to get everything set up. These machines won't use > MythTV, but his is > the best most detailed description of getting all > the tech setup. > 2. In section 5 of Jarod's instructions he says to > install > atrpms-kickstart, then immediately do a apt-get > update/apt-get > dist-upgrade. This is where things most likely go > wrong. He should > immediately say that you MUST use the testing > settings because that's > where the packages are apparently stored. > 3. People then continue with Jarod's instructions, > but since the > default installation of atrpms-kickstart uses the > stable packages, they > are downloading versions of the ivtv modules and > other packages that are > not compatible with the usual next step... > 4. About two sections later I (and possibly others) > realize that most > of the packages needed to get mythtv working (like > mythtv-suite) are not > in the stable tree, so they switch to testing and > this is where I think > things explode. > 5. The new ivtv packages in testing for some reason > (or maybe just > later upgrades) tack on the -ivtv ending to the > modules, __but don't > remove the other ones__. Somehow the rpms are just > not written > correctly and are either leaving junk, making junk, > not cleaning the old > modules, etc. In addition, the infection may have > happened when I tried > the 2.6.10 kernel and switched back to 2.6.9 (the > current working > kernel). > > I think this is what's happening. > > I would first say that whoever decided on either the > module name change, > rpm change, or other problem which leaves these > parallel modules around > should fess up. :-) It was frustrating to track > through the mailing > lists and find only a fleeting mention of the "alias > tveeprom" trick. > The only reason this is necessary is because there's > all these junk > kernel modules around, which means that there's a > deeper cause > somewhere. > > Second, you should put a mention of this problem on > the front page. > "Check how many tveeprom* files you have." This > would help a lot of > people in the long run. > > Finally, I'm hoping people on the list can help me > narrow down the > problem so I can get the sound and video working > tomorrow. I'll most > likely post a message tomorrow morning with better > details, and > hopefully this message will get some developer on > the track of the > problem. > > Personally, I'm very impressed with the ivtv project > and the quality I > see so far. It's a little embarassing to rave about > you guys and have > something as rediculously stupid as a mis-named > module trip me up for 3 > days. It's silly mistakes like that which really > make it hard to sell > Linux as a solution, so hopefully I can avoid all > these problems in the > future. > > Harsh words, but only meant in an effort to get > better disclosure and to > find a proactive solution so this never happens > again. > > Your comments are welcome. > > -- > Zed A. Shaw > http://www.zedshaw.com/ > > > > ------------------------------------------------------- > 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 > ------------------------------------------------------- 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
