On Tue, Sep 9, 2008 at 21:28, John Allman <[EMAIL PROTECTED]> wrote: > On Tue, Sep 9, 2008 at 7:40 PM, Sander Sweers <[EMAIL PROTECTED]> wrote: > > Thanks for the reply Sander. To be clear, X starts fine - this happens > only when attempting to play back video.
It starts on the pvr-350 tv-out, right? >> This drm/via related, does this come up immediatly or after you tried >> to start X? >> > > Only after I start playback. I don't understand why via stuff is > involved at all unless it's something on the motherboard - the via > graphics adapter really shouldn't be involved that I understand. The via stuff is for the onboard video card the drm is what makes direct rendering (accelerated opengl for example) possible. Mythtv for example can use opengl to render it's ui. >> Please make sure you are using the correct device. cat /proc/fb will tell >> you. > > Hmm > > [EMAIL PROTECTED]:~$ cat /proc/fb > 0 cx23415 TV out Ok, /dev/fb0 it is :-) > But this doesn't surprise me - X is starting using the tv out on the > pvr 350. One thing I have noticed that is different between this > install and the previous install is that I get console output to the > tv before X starts. I don't know if this is relevant (nor do I know > how to disable it). Not really, it just means it get's loaded earlier. In kernel 2.6.24 (it was merged in this release) you can have output from the start if you compile it into the kernel! The xdriver only supports xvideo and no direct rendering like the via onboard graphics card does. My best guess, and this is a bit out of scope for this list ;-), is that the media player software is trying to use direct rendering for playback on the via card. Can you try and use mplayer with switch: -vo xv or -vo x11? Does this also cause the oops? Greets Sander _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
