One more question about this. When I do the 'make ivtv' in the v4l archive, how does v4l know what version of ivtv to download, since it is kernel-version dependent? Is there a way to make it point to a local copy instead?
Thanks, MIke On 2/3/07, Michael Wisniewski <[EMAIL PROTECTED]> wrote:
Thank you for the information in the readme. Ever since the birth of the wiki, I really stopped reading the README's and just followed the wiki's. Finally....something that actually makes some sense! So far, things have been working pretty well. I haven't really given it a workout yet, but at least the pvr-150 works and the kworld hd card works, along with myth....well, besides the error messages about the firmware unresponsive. I think I'll probably keep it how it is for now, until a few days pass, just so that things have a chance to cool down and I can get back to my normal life. Thank you very much for the information and it's very helpful! Thanks, Mike On 2/3/07, Hans Verkuil <[EMAIL PROTECTED]> wrote: > > On Saturday 03 February 2007 06:38, Michael Wisniewski wrote: > > Hi! > > > > I posted a message the other day with some problems with ivtv and > > firmware unresponsive. Well, I wiped my system and decided to put > > Ubuntu Feisty Fawn on. Yeah, I know it's beta, but I was having a > > hell of a time trying to get Dapper and Edgy to work with my cards. > > > > So now, I'm running 2.6.20-6-generic kernel and everything seems > > to be recognized, but I still get the errors. As far as I know, the > > kernel is built with ivtv, so I didn't have to install it. But why > > is it that I have so many headaches trying to get this firmware > > unresponsive message to go away!?! Argh. Oh well, there are many > > smart people out there and I'm sure one of them will be nice enough > > to help. :) > > You can't use ivtv with kernel 2.6.20 yet. Once the kernel is released > I'll have a new ivtv available within a few days. > > I've just checked in a README on how to compile ivtv together with > v4l-dvb. I'll reproduce it below. Using those instructions might be > your best bet. You'll get the latest ivtv version (which I'll release > later today as a release candidate). > > If you still have problems, then first test outside MythTV, e.g. > simple 'cat /dev/video0 > x.mpg' tests. That makes it much easier to > isolate the problem. > > Regards, > > Hans > > >From the README.v4l-dvb: > > The latest video4linux repository is available from www.linuxtv.org. > If you have other video hardware that is only supported in that > repository and hasn't yet been included in the kernel, then you need > these build instructions in order to build both v4l-dvb and ivtv at the > same time. > > First obtain the v4l-dvb repository. See these instructions: > > http://www.linuxtv.org/v4lwiki/index.php/How_to_build_from_mercurial > > In order to include ivtv you need one extra step: before building the > v4l-dvb module (the 'make' step) call 'make ivtv'. This will retrieve > the ivtv sources from the ivtv subversion trunk repository and merge > them into the v4l-dvb directory tree. 'make' will now make ivtv in > addition to all the other v4l-dvb modules. > > Note that both the v4l-dvb and the ivtv trunk repositories contain > bleeding edge code, so there are no guarantees that it will always > work. > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users >
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
