Bryan Ware wrote:
I used to have Core 1 as my OS, but upgraded my system so I went with
Core 3. I didn't have this issue in core 1 and didn't have it in the
rc.local file. I tried to copy the old modules.conf entries for ivtv to
the modprobe.conf file but it didn't like the add lines..

Bry

On Thu, 2004-12-23 at 08:26 -0500, Andrew Plumb wrote:

If it works manually, search the mythtv-users archives for "rc.local".
That's what many of us had to do to get ivtv (and lircd) to load at
boot.

Andrew.

On Thu, 23 Dec 2004 07:35:48 -0500, Bryan Ware <[EMAIL PROTECTED]> wrote:

Ok,
       I installed Myth using the great Jarod's guide, and I have one little
issue, i can't figure out the modprobe.conf file for the ivtv drivers to
have them load at bootup. I have to manually start them and then restart
mythbackend. If I don't I have no sound. Below is my modprobe.conf
file..

[snip]

I am at the stage in Jarod's guide where I am about to get the PVR 350 to display the X desktop via the ivtv_fb driver, but in addition to adding 'modprobe ivtv' to rc.local, I shall be following the advice gleaned from http://bugzilla.atrpms.net/show_bug.cgi?id=345 and bugid's 319 and 320 as well. At the present time, I can manually load ivtv and run mplayer /dev/video0 (albeit with no sound, sigh). I will let you know how it goes, as this is my second attempt at getting the 350 to display X on the TV.

One other thing I have observed with a clean Fedora Core 3 install followed by a dist-upgrade from atrpms 'stable' is that the current FC3 SELinux policy seems to kill off syslogd if set to 'enforced', so I have to back off to 'permissive' to get logs. Found that out only this morning. I hope to have this thing up and running by Christmas, as befits a present to myself :-)

Les
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to