Announcement

Collapse
No announcement yet.

yv12 ,xvideo support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by mlau View Post
    Do the OpenGL output modes of mplayer, xine work?
    e.g. mplayer -vo gl <file>
    xine -V gl <file>

    (post the _complete_ xorg.log too, please)
    xine -V gl file the file worked but with following msg

    This is xine (X11 gui) - a free video player v0.99.4.
    (c) 2000-2004 The xine Team.
    Xlib: extension "XFree86-DRI" missing on display ":0.0".
    video_out_opengl: compiled for BGRA output, but missing extension.
    [mpeg4 @ 0x2aaab03230e0]header damaged
    [mpeg4 @ 0x2aaab03230e0]header damaged

    Comment


    • #12
      i receive error when i try to post the complete log of
      cat /var/log/Xorg.0.log

      so i will post only last lines

      fglrx(0): DPMS enabled
      (II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
      Screen to screen bit blits
      Solid filled rectangles
      Solid Horizontal and Vertical Lines
      Offscreen Pixmaps
      Setting up tile and stipple cache:
      32 128x128 slots
      32 256x256 slots
      16 512x512 slots
      (II) fglrx(0): Acceleration enabled
      (WW) fglrx(0): Option "VendorName" is not used
      (WW) fglrx(0): Option "ModelName" is not used
      (II) fglrx(0): Direct rendering disabled
      (==) fglrx(0): Using hardware cursor
      (WW) fglrx(0): Textured Video not supported without DRI enabled.
      (WW) fglrx(0): Video Overlay not supported on AVIVO based graphics cards. For XVideo support use Option "TexturedVideo".
      (==) RandR enabled
      (II) Initializing built-in extension MIT-SHM
      (II) Initializing built-in extension XInputExtension
      (II) Initializing built-in extension XTEST
      (II) Initializing built-in extension XKEYBOARD
      (II) Initializing built-in extension XC-APPGROUP
      (II) Initializing built-in extension SECURITY
      (II) Initializing built-in extension XINERAMA
      (II) Initializing built-in extension XFIXES
      (II) Initializing built-in extension XFree86-Bigfont
      (II) Initializing built-in extension RENDER
      (II) Initializing built-in extension RANDR
      (II) Initializing built-in extension COMPOSITE
      (II) Initializing built-in extension DAMAGE
      (II) Initializing built-in extension XEVIE
      (II) Loading local sub module "GLcore"
      (II) LoadModule: "GLcore"
      (II) Loading /usr/lib64/xorg/modules/extensions/libGLcore.so
      (II) Module GLcore: vendor="X.Org Foundation"
      compiled for 7.1.1, module version = 1.0.0
      ABI class: X.Org Server Extension, version 0.3
      (II) GLX: Initialized MESA-PROXY GL provider for screen 0
      (**) Option "CoreKeyboard"
      (**) Keyboard0: Core Keyboard
      (**) Option "Protocol" "standard"
      (**) Keyboard0: Protocol: standard
      (**) Option "AutoRepeat" "500 30"
      (**) Option "XkbRules" "xorg"
      (**) Keyboard0: XkbRules: "xorg"
      (**) Option "XkbModel" "pc105"
      (**) Keyboard0: XkbModel: "pc105"
      (**) Option "XkbLayout" "us"
      (**) Keyboard0: XkbLayout: "us"
      (**) Option "CustomKeycodes" "off"
      (**) Keyboard0: CustomKeycodes disabled
      (**) Option "Protocol" "IMPS/2"
      (**) Mouse0: Device: "/dev/input/mice"
      (**) Mouse0: Protocol: "IMPS/2"
      (**) Option "CorePointer"
      (**) Mouse0: Core Pointer
      (**) Option "Device" "/dev/input/mice"
      (**) Option "Emulate3Buttons" "yes"
      (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
      (**) Option "ZAxisMapping" "4 5"
      (**) Mouse0: ZAxisMapping: buttons 4 and 5
      (**) Mouse0: Buttons: 9
      (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
      (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
      (II) Mouse0: ps2EnableDataReporting: succeeded

      Comment


      • #13
        Try pasting it to some Pastebin service.

        The only useful line there is that DRI is disabled.

        Alternatively, try posting the output of "cat /var/log/Xorg.0.log | grep EE && cat /var/log/Xorg.0.log | grep WW".

        Comment


        • #14
          Originally posted by SheeEttin View Post
          Try pasting it to some Pastebin service.

          The only useful line there is that DRI is disabled.

          Alternatively, try posting the output of "cat /var/log/Xorg.0.log | grep EE && cat /var/log/Xorg.0.log | grep WW".
          cat /var/log/Xorg.0.log | grep EE && cat /var/log/Xorg.0.log | grep WW


          (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
          (II) Loading extension MIT-SCREEN-SAVER
          (EE) Failed to load module "v4l" (module does not exist, 0)
          (EE) Failed to load module "TexturedVideo" (module does not exist, 0)
          (EE) fglrx(0): GART is not initialized, disabling DRI
          (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
          (WW) The core pointer device wasn't specified explicitly in the layout.
          (WW) Warning, couldn't open module v4l
          (WW) Warning, couldn't open module TexturedVideo
          (WW) fglrx: No matching Device section for instance (BusID PCI:6:0:1) found
          (WW) fglrx(0): Failed to open DRM connection
          (WW) fglrx(0): board is an unknown third party board, chipset is supported
          (WW) fglrx(0): No DRM connection for driver fglrx.
          (WW) fglrx(0): ***********************************************
          (WW) fglrx(0): * DRI initialization failed! *
          (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
          (WW) fglrx(0): * 2D acceleraton available (MMIO) *
          (WW) fglrx(0): * no 3D acceleration available *
          (WW) fglrx(0): ********************************************* *
          (WW) fglrx(0): Option "VendorName" is not used
          (WW) fglrx(0): Option "ModelName" is not used
          (WW) fglrx(0): Textured Video not supported without DRI enabled.
          (WW) fglrx(0): Video Overlay not supported on AVIVO based graphics cards. For XVideo support use Option "TexturedVideo".

          Comment


          • #15
            Seems like you are missing video for linux. What linux distribution are you using?

            Comment


            • #16
              Originally posted by glussier View Post
              Seems like you are missing video for linux. What linux distribution are you using?
              i use fedora core 6

              uname -a
              Linux deep 2.6.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:05:34 EST 2007 x86_64 x86_64 x86_64 GNU/Linux

              Comment


              • #17
                Originally posted by localizer View Post
                cat /var/log/Xorg.0.log | grep EE && cat /var/log/Xorg.0.log | grep WW

                ...
                (WW) Warning, couldn't open module v4l
                (WW) Warning, couldn't open module TexturedVideo
                (WW) fglrx: No matching Device section for instance (BusID PCI:6:0:1) found
                (WW) fglrx(0): Failed to open DRM connection
                (WW) fglrx(0): board is an unknown third party board, chipset is supported
                (WW) fglrx(0): No DRM connection for driver fglrx.
                (WW) fglrx(0): ***********************************************
                (WW) fglrx(0): * DRI initialization failed! *
                (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
                (WW) fglrx(0): * 2D acceleraton available (MMIO) *
                (WW) fglrx(0): * no 3D acceleration available *
                (WW) fglrx(0): ********************************************* *
                (WW) fglrx(0): Option "VendorName" is not used
                (WW) fglrx(0): Option "ModelName" is not used
                (WW) fglrx(0): Textured Video not supported without DRI enabled.
                (WW) fglrx(0): Video Overlay not supported on AVIVO based graphics cards. For XVideo support use Option "TexturedVideo".
                You can see the problem right above. You need to install, correctly, the fglrx drivers. It is possible that you upgraded your kernerl without rebuilding the fglrx drivers. I am about to post cautions about this on my website. In the meantime, make sure that your kernel and the fglrx modules match. Once you do that, post the output of the errors you are receiving.

                HTH,

                Partha

                Comment


                • #18
                  Originally posted by partha View Post
                  You can see the problem right above. You need to install, correctly, the fglrx drivers. It is possible that you upgraded your kernerl without rebuilding the fglrx drivers. I am about to post cautions about this on my website. In the meantime, make sure that your kernel and the fglrx modules match. Once you do that, post the output of the errors you are receiving.

                  HTH,

                  Partha
                  www.partha.com
                  i've just updated the kernel

                  Linux deep 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:00:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

                  what should i do exactly now ?

                  Comment


                  • #19
                    Originally posted by localizer View Post
                    i've just updated the kernel

                    Linux deep 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:00:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

                    what should i do exactly now ?
                    Short answer, look at my website where I posted about just this dilemma.

                    Long answer, you will need to use Michael's script to recreate the fglrx driver and update the kernel module corresponding to your current kernel. Then you will have to install this kernel module and restart X.

                    As per Michael, you should be able to do this with the new driver as well.

                    HTH,

                    Partha

                    Comment


                    • #20
                      Originally posted by partha View Post
                      Short answer, look at my website where I posted about just this dilemma.

                      Long answer, you will need to use Michael's script to recreate the fglrx driver and update the kernel module corresponding to your current kernel. Then you will have to install this kernel module and restart X.

                      As per Michael, you should be able to do this with the new driver as well.

                      HTH,

                      Partha
                      www.partha.com
                      the script fglrx-f7t1-builder.sh is using
                      fglrx 8.33.6 drivers , and i've just downloaded ati-driver-installer-8.34.8-x86.x86_64.run

                      is that script is still valid ?

                      Comment

                      Working...
                      X