|
I got it all fixed. Back up and
running. My ivtv section of modules.conf . The
bottom 3 lines are new. Don’t
know what it does but it works. I thought
the “alias” lines told the kernel to load a module. I pulled this from some newsgroup post and
hacked out the complicated options.
It was from like 1970 or something (I know exaggeration but it was
talking about the .0.1.1 v of the driver) alias char-major-81 videodev alias char-major-81-0 ivtv options saa7127 enable_output=1 output_select=0 add below ivtv msp3400 saa7115 saa7127 tuner add above ivtv ivtv-fb the reason Lirc (and mythbackend for that
matter) was not working was because I just manually created the links in the /etc/rc5.d
directory vs using the command ‘update-rc.d blahblah’ command that
creates the link for you. Also I had
to redirect the paths in the lirc script that I found
in /etc/init.d once I get mythweb reinstalled it be all good again. Also, the rebuild appears to have gotten
rid of my popping and cracking problem and the inability to autoconfigure
the audio standard. I think
it was because, since the 4.0 version would NOT build the tuner module, I was
using the 3.7i tuner module with the other 4.0 drivers. This apparently caused some weirdness. Of course I am getting that msp3400 depmod error.
I don’t think my card in particular uses the msp3400 module so I guess
that doesn’t matter to me. -----Original Message-----
To get ivtv-fb to load on boot, it has to be in your
kernel's initial ram disk. Details on setting this up can be found in
Jarod's guide : Do a find on that page for mkinird-ivtv to find the
section detailing it. Its not easy or painless. Not sure about your lirc problem. Might be a
module order problem. Keith C |
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
