|
SageTV Linux Discussion related to the SageTV Media Center for Linux. Questions, issues, problems, suggestions, etc. relating to the SageTV Linux should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#21
|
|||
|
|||
This error only occured after the installation of MythTV. I had installed it to try and isolate the original problem. What and where is the rendering system? I had made no changes other than installing MythTV and It's dependancies.
|
#22
|
|||
|
|||
If you have installed using mode 2 the rendering system uses opengl. You could try to run glxgears and glxinfo to see if they can still run fine.
_Demo_ |
#23
|
|||
|
|||
glxgears and glxinfo work with SageTV. They will not after MythTV is installed.
|
#24
|
|||
|
|||
There must some conflict with the nvidia drivers.
_Demo_ |
#25
|
|||
|
|||
I tested ivtv with ivtv-ptune and got the exact same result. This makes me think it's a problem with ivtv. Can I just remerge ivtv or nvidia to a different version for further testing? I see all the shared objects in the /opt/sagetv/app directory which really confuses me. I'm not sure how all this works together and where everything is installed to.
|
#26
|
|||
|
|||
I think I got it! here is what I did.
# rmmod ivtv # modprobe ivtv tuner=57 # echo ivtv tuner=57 >> /etc/modules.autoload.d/kernel-2.6 # ptune.pl --input /dev/video0 -c 2 # cat /dev/video0 > /var/media/videos/vid0.mpg ctrl+c to quit Now the created file shows the video it recorded. How do I get SageTV to do this too? |
#27
|
|||
|
|||
You could try to replace the modprobe in /opt/sagetv/app/startsage by adding the tuner= argument.
_Demo_ |
#28
|
|||
|
|||
ok, the modprobe thingy did not change much but I did get a signal from the component input when choosing inputs in the SageTV setup. I am unable to test s-video at the moment and the tuner is still black. I tried to test the inputs with ivtvctl but the command was not found. Do I have to recompile or reinstall ivtv? When trying to emerge nividia-kernel or ivtv I get an error "Could not find usable .config in the kernel source directory".
|
#29
|
|||
|
|||
You can find the kernel config file in another thread. One thing you could try is compare the output of dmesg between the two versions to see if it detects the tuner properly.
_Demo_ |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|