Gentoo Forums :: View topic - Cannot play video in full screen mode

Cannot play video in full screen mode

View unanswered posts
View posts from last 24 hours

Goto page Previous 1, 2

Gentoo Forums Forum Index

Multimedia

View previous topic :: View next topic

Author

Message

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W

Posted: Sun Jun 25, 2017 3:00 pm Post subject:

deltamalloc, VDPAU_DRIVER does not appear in your environment. I suppose that's expected as you don't know what to set it to. It explains the nvidia though, as that's the hard coded default. Your mplayer was built with USE=-xvmc. You probably want that on. Its X Video Motion Compensation. _________________ Regards, NeddySeagoon Computer users fall into two groups:- those that do backups those that have never had a hard drive fail.

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W

Posted: Sun Jun 25, 2017 3:35 pm Post subject:

I've fired up a rarely used system with a radeon card.

Its Xorg.0.log shows

Code:

[ 8.445] (II) LoadModule: "dri2"
[ 8.445] (II) Module "dri2" already built-in
[ 8.445] (II) Loading sub module "glamoregl"
[ 8.445] (II) LoadModule: "glamoregl"
[ 8.445] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[ 8.467] (II) Module glamoregl: vendor="X.Org Foundation"
[ 8.467] compiled for 1.19.3, module version = 1.0.0
[ 8.467] ABI class: X.Org ANSI C Emulation, version 0.4
[ 8.467] (II) glamor: OpenGL accelerated X.org driver based.
[ 8.990] (II) glamor: EGL version 1.4 (DRI2):
[ 9.003] (II) RADEON(0): glamor detected, initialising EGL layer.
...
[ 9.042] (II) RADEON(0): [DRI2] Setup complete
[ 9.042] (II) RADEON(0): [DRI2] DRI driver: r600
[ 9.042] (II) RADEON(0): [DRI2] VDPAU driver: r600

It seems to work without a VDPAU_DRIVER= too.

Your log mentions

Code:

[ 242.980] (II) glamor: EGL version 1.4 (DRI2):
[ 242.980] EGL_MESA_drm_image required.
[ 242.982] (EE) RADEON(0): glamor detected, failed to initialize EGL.

My global USE settings are

Code:

USE="X a52 aac aacplus aalib acl acpi aften alaw alsa amd64 amr apng audio audiofile avformat bash-completion berkdb bluetooth bluray bzip2 cairo caps cddb cli consolekit cracklib crypt css cups cvs cxx dbus dirac dri expat extras faac ffmpeg flac fortran gdbm gegl gif glamor gnome-keyring gpm graphite gsm gtk gudev hwdb iconv icu idn ipv6 jpeg jpeg2k libkms libmpeg2 libsamplerate lirc lzo mad mmx mmxext modules mp3 mpeg ncurses nls nptl ogg opengl openmp pam pcre pcre16 pdf perl pie png policykit postscript pulseaudio readline rtmp sdl seccomp session smp smpeg speex sse sse2 sse4a ssl ssp ssse3 startup-notification subversion svc svg tcpd theora threads thunar tiff unicode upcall usb v4l1 v4l2 vdpau vorbis winbind x264 xattr xkb xorg xv xvmc zlib"

You have USE=egl missing, which may be a contributing factor.

Fix your USE flags to include egl and xvmc, update everything that's affected, reboot to test.
Restarting Xorg would be enough.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

deltamalloc
Apprentice

Joined: 18 Jan 2013
Posts: 279

Posted: Tue Jun 27, 2017 11:07 pm Post subject:

NeddySeagoon wrote:

I've fired up a rarely used system with a radeon card.

Its Xorg.0.log shows

Code:

It seems to work without a VDPAU_DRIVER= too.

Your log mentions

Code:

[ 242.980] (II) glamor: EGL version 1.4 (DRI2):
[ 242.980] EGL_MESA_drm_image required.
[ 242.982] (EE) RADEON(0): glamor detected, failed to initialize EGL.

My global USE settings are

Code:

You have USE=egl missing, which may be a contributing factor.

Fix your USE flags to include egl and xvmc, update everything that's affected, reboot to test.
Restarting Xorg would be enough.

I've now done the following:

* Recompiled mplayer with +xvmc.
* Added egl and xvmc to my global USE flags.
* emerge --update --changed-use --deep @world
* Rebooted.

This is what happens when I try to play a media file with mplayer:

Code:

Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory

So the problem persists.

Don't you find it strange that ldd nor the strings utility can find this libvdpau_nvidia.so file within the program that asks for it?

I don't understand what you mean by "hardcoded". Do you mean that libvdpau_nvidia.so is statically linked into libvdpauinfo? In that case, it would never complain about it being missing, it would be part of the binary. If it was dynamically loaded, it would show up with ldd. But I assume you mean that the environment variable VDPAU_DRIVER has a default value. Such that, when VDPAU_DRIVER is not set at all then it defaults to "nvidia" for the purposes of emerging/compiling the correct version of vdpauinfo, mplayer, etc.

However, this still doesn't explain why libvdpau_nvidia.so is not referenced as a shared object dependency.

Moreover, I have no idea how to fix my current problem. I greatly appreciate your support, sorry for the delay in replying to this thread.

My global USE flags are now:

Code:

USE="egl xvmc bindist mmx mmxext popcnt sse sse2 sse3 ssse3 sse4_1 sse4_2 vdpau threads -pulseaudio -gnome -kde -minimal -qt4 -libav dbus jpeg lock session startup-notification thunar udev X alsa xinerama"

I still unfortunately get this in my Xorg log:

Code:

[ 32.366] (EE) RADEON(0): glamor detected, failed to initialize EGL.

I've tried to fix this to no end by looking at among other things the radeon guide: https://wiki.gentoo.org/wiki/Radeon#Glamor_does_not_load

Quote:

"If you see errors like "glamor detected, failed to initialize EGL.", then try enabling USE="gbm egl gles2 llvm" in the mesa builds."

But I already have those USE flags in my mesa build.

I have this in my dmesg:

Code:

[ 0.795482] radeon 0000:02:00.0: Invalid PCI ROM header signature: expecting
0xaa55, got 0xffff
[ 0.795661] ATOM BIOS: Tahiti

While ALL of this may be relevant and maybe (?) should ideally be fixed, isn't it even more disturbing that it still asks for libvdpau_nvidia.so? It wouldn't help fixing all of this as long as it will still simply attempt to use the nvidia backend.

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W

Posted: Wed Jun 28, 2017 2:29 pm Post subject:

deltamalloc,

Things that do not appear in logs are often as telling as those that do. Its therefore important that you pastebin entire logs.
Its the only way that helpers can detect what should be there but is missing. Its much harder to spot that sort of thing from log fragments.

Your full global USE settings only appear in

Code:

emerge --info

since many USE options are inherited from your profile.
That will fit into a post.

Your Xorg.0.log needs to go to a pastebin.

"hardcoded" means that if VDPAU_DRIVER is not in the environment, the nvidia VDPAU is assumed. Nothing is linked.
However, my working example does not have VDPAU_DRIVER set anywhere I can see and still loads the correct driver.

Your

Code:

[ 32.366] (EE) RADEON(0): glamor detected, failed to initialize EGL.

is interesting.
Why did it fail?

Post your

Code:

emerge --info

and entire /var/log/Xorg.0.log.
dmesg is worth reviewing always too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

deltamalloc
Apprentice

Joined: 18 Jan 2013
Posts: 279

Posted: Wed Jun 28, 2017 3:43 pm Post subject:

NeddySeagoon wrote:

Code:

emerge --info

Code:

[ 32.366] (EE) RADEON(0): glamor detected, failed to initialize EGL.

is interesting.
Why did it fail?

Post your

Code:

emerge --info

and entire /var/log/Xorg.0.log.
dmesg is worth reviewing always too.

Sorry about that:

emerge --info: https://paste.pound-python.org/show/Vh3oXul9eAjG6oPe40sN/
Xorg.0.log: https://paste.pound-python.org/show/DOZMq5IiBHeDCGmsFXMn/
dmesg: https://paste.pound-python.org/show/4yU4Ola7VjyopzLyOp6O/

As for why EGL fails to initialize, I don't know. I've tried to search for this issue and followed the radeon guide to the letter, rebooted multiple times between attempts.

steveL
Watchman

Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

Posted: Wed Jun 28, 2017 4:22 pm Post subject:

NeddySeagoon wrote:

My global USE settings are

Code:

You have USE=egl missing, which may be a contributing factor.

Hmm, I can't see "egl" in your flag list, only "opengl" (which is what I'd expect.)

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W

Posted: Wed Jun 28, 2017 4:46 pm Post subject:

deltamalloc,

You have the X11 overlay.

Code:

x11
location: /var/lib/layman/x11
masters: gentoo
priority: 50

Which packages ho you use from there, if any?
The why doesn't really matter, I'm just curious.
Anything like mesa, xorg-server, mplayer or any of the input or video drivers could case subtle issues like this due to part from different repos not playing nicely together.

Your emerge --info looks good.

From Xorg.0.log

Code:

[ 32.365] (II) glamor: EGL version 1.4 (DRI2):
[ 32.365] EGL_MESA_drm_image required.
[ 32.366] (EE) RADEON(0): glamor detected, failed to initialize EGL.

It appears that a version of mesa without EGL support is being used.

Code:

[ 32.083] (--) PCI:*(0:2:0:0) 1002:6798

Is a Radeon HD 7970/8970 according to Google.
That's a Southern Islands chipset.

Code:

eselect mesa list

should show the gallium software renderer set. None of the

Code:

r300 (Radeon R300-R500)
r600 (Radeon R600-R700, Evergreen, Northern Islands)

drivers are for your card. Feel free to try them.
Its make a selection, restart Xorg, check the log.

Check that mesa has been built with USE=egl.

dmesg looks good too.

Your Xorg.0.log is missing the section where Xorg determines the driver for your chipset.
This tells that somewhere in

Code:

/etc/X11/xorg.conf.d

you have a file that selects the radeon driver. It may do other things too.
Move it to somewhere harmless, like /home/<user> and let the automatics do their thing.
You will get a USA keymap. Its possible you have an option here you don't need.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

deltamalloc
Apprentice

Joined: 18 Jan 2013
Posts: 279

Posted: Wed Jun 28, 2017 9:35 pm Post subject:

NeddySeagoon wrote:

deltamalloc,

You have the X11 overlay.

Code:

x11
location: /var/lib/layman/x11
masters: gentoo
priority: 50

Code:

[ 32.365] (II) glamor: EGL version 1.4 (DRI2):
[ 32.365] EGL_MESA_drm_image required.
[ 32.366] (EE) RADEON(0): glamor detected, failed to initialize EGL.

It appears that a version of mesa without EGL support is being used.

Code:

[ 32.083] (--) PCI:*(0:2:0:0) 1002:6798

Is a Radeon HD 7970/8970 according to Google.
That's a Southern Islands chipset.

Code:

eselect mesa list

should show the gallium software renderer set. None of the

Code:

r300 (Radeon R300-R500)
r600 (Radeon R600-R700, Evergreen, Northern Islands)

Code:

/etc/X11/xorg.conf.d

The graphics card is actually a "Sapphire Radeon R9 280X", but these are very similar to 7970, if memory serves me right.

What packages do I use from that overlay?

I tried first:

Code:

# equery has repository ${x11}
!!! Fatal error: Used ENV_VAR without match_expression or --package

Then:

Code:

# eix --installed-from-overlay x11
[I] x11-libs/libvdpau-va-gl [1]
Available versions: (~)0.3.4 **9999 {test}
Installed versions: 0.3.4(12:40:58 AM 06/22/2017)(-test)
Homepage: https://github.com/i-rinat/libvdpau-va-gl/
Description: VDPAU driver with VA-API/OpenGL backend.

[1] "x11" /var/lib/layman/x11

Seems like only x11-libs/libvdpau-va-gl is being used.

Code:

# eselect mesa list
64bit i915 (Intel 915, 945)
64bit i965 (Intel GMA 965, G/Q3x, G/Q4x, HD)
64bit r300 (Radeon R300-R500)
[1] gallium *
64bit r600 (Radeon R600-R700, Evergreen, Northern Islands)
[1] gallium *
64bit sw (Software renderer)
[1] classic
[2] gallium *
32bit i915 (Intel 915, 945)
32bit i965 (Intel GMA 965, G/Q3x, G/Q4x, HD)
32bit r300 (Radeon R300-R500)
[1] gallium *
32bit r600 (Radeon R600-R700, Evergreen, Northern Islands)
[1] gallium *
32bit sw (Software renderer)
[1] classic
[2] gallium *

Should I change any of this?

Mesa is definitely built with egl:

Code:

# equery uses mesa
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for media-libs/mesa-17.0.6:
U I
+ + abi_x86_32 : 32-bit (x86) libraries
+ + bindist : Disable patent-encumbered ARB_texture_float,
EXT_texture_shared_exponent, and EXT_packed_float
extensions.
+ + classic : Build drivers based on the classic architecture.
- - d3d9 : Enable Direct 3D9 API through Nine state tracker.
Can be used together with patched wine.
- - debug : Enable extra debug codepaths, like asserts and
extra output. If you want to get meaningful
backtraces see https://wiki.gentoo.org/wiki/Project
:Quality_Assurance/Backtraces
+ + dri3 : Enable DRI3 support.
+ + egl : Enable EGL support.
...

As for stuff in /etc/X11/xorg.conf.d:

This is what I have:

Code:

xorg.conf.d # ls
10-glamor.conf 30-keyboard.conf 42-dvi-monitor.conf 51-extensions.conf
20opengl.conf 41-dvi-monitor.conf 50-video.conf 60-flags.conf
xorg.conf.d # cat *
Section "Module"
Load "dri2"
Load "glamoregl"
EndSection
Section "Files"
EndSection
Section "InputClass"
Identifier "keyboard-all"
Driver "evdev"
Option "XkbLayout" "no"
Option "XkbRules" "xorg"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
MatchIsKeyboard "on"
EndSection
Section "Monitor"
Identifier "DFP11"
Option "LeftOf" "DFP10"
EndSection
Section "Monitor"
Identifier "DFP10"
EndSection
Section "Device"
Identifier "Radeon"
Option "Monitor-DFP10" "DFP10"
Option "Monitor-DFP11" "DFP11"
Driver "radeon"
# Driver "fglrx"
Option "SWcursor" "off"
Option "EnablePageFlip" "on"
Option "AccelMethod" "glamor"
Option "RenderAccel" "on"
Option "ColorTiling" "on"
Option "AccelDFS" "on"
EndSection
Section "Extensions"
# Option "Composite" "Disable"
EndSection
Section "ServerFlags"
Option "DontZap" "false"
EndSection

As you can see I do specify "radeon" in my 50-video.conf file.

I should also point out that this has all worked perfectly fine before. It stopped working when there was a messy world update where packages failed to build. I had to remove some use flags to make them compile successfully. Although this is now many weeks ago and I don't recall which.

Gusar
Advocate

Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

Posted: Thu Jun 29, 2017 9:35 am Post subject:

Your VIDEO_CARDS should include radeonsi. Or just be VIDEO_CARDS="radeonsi", it's enough. Because right now your mesa does not have support for your GPU. That's why glamor fails, that's why everything else fails too. So set VIDEO_CARDS and then recompile at least mesa and xorg-drivers, I think that should do. PS. xvmc is entirely outdated and obsolete, you won't miss anything if you disable that flag. vdpau and/or vaapi is what matters nowadays, both will work for you once you set VIDEO_CARDS appropriately (and add vaapi to your USE flags, right now you only have vdpau there).

steveL
Watchman

Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

Posted: Fri Jun 30, 2017 10:40 am Post subject:

Good catch, Gusar. /still not happy about all this egl hoopla..

Gusar
Advocate

Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

Posted: Fri Jun 30, 2017 2:08 pm Post subject:

steveL wrote:

/still not happy about all this egl hoopla..

EGL is a good thing. Much better than being stuck with GLX. The mesa ebuild has it enabled by default for a reason.

steveL
Watchman

Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

Posted: Sat Jul 01, 2017 11:43 am Post subject:

Gusar wrote:

EGL is a good thing. Much better than being stuck with GLX. The mesa ebuild has it enabled by default for a reason.

I could have sworn it meant "embedded GL" (from Kronos iirc) as opposed to standard OpenGL.
I realise it's being touted as the next best thing since sliced-bread, and that.

Gusar
Advocate

Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia

Posted: Sat Jul 01, 2017 2:01 pm Post subject:

steveL wrote:

I could have sworn it meant "embedded GL" (from Kronos iirc) as opposed to standard OpenGL.

That would be OpenGL ES (the gles1 and gles2 flags in the mesa ebuild; enabling gles2 gives you ES 3 too, with drivers that support it). That one was originally for embedded, though it can very well be used on desktops too.

EGL is a bridge between your application and the windowing system. It was meant to eliminate platform specific initialization in applications, so that instead of your app needing GLX, WGL, AGL etc. code, it'd just have EGL code. It does't quite work out like that in practice, but it's nevertheless a good step forward.

An example of a neat trick that EGL allows is hardware video decoding and rendering on the linux console, no X or Wayland necessary:

Code:

mpv --hwdec=vaapi --opengl-backend=drm somefile.mp4

The above only works on Intel GPUs currently, because only they implement VAAPI/EGL interop, but support in other drivers should appear at some point (the drm opengl backend works already, but without vaapi interop you'll get software decoding). On other platforms, just adjust the backend option, --opengl-backend=x11egl or --opengl-backend=wayland.

deltamalloc
Apprentice

Joined: 18 Jan 2013
Posts: 279

Posted: Sat Jul 01, 2017 4:39 pm Post subject:

Gusar wrote:

Your VIDEO_CARDS should include radeonsi. Or just be VIDEO_CARDS="radeonsi", it's enough. Because right now your mesa does not have support for your GPU. That's why glamor fails, that's why everything else fails too. So set VIDEO_CARDS and then recompile at least mesa and xorg-drivers, I think that should do.

PS. xvmc is entirely outdated and obsolete, you won't miss anything if you disable that flag. vdpau and/or vaapi is what matters nowadays, both will work for you once you set VIDEO_CARDS appropriately (and add vaapi to your USE flags, right now you only have vdpau there).

Thanks, that did it. I don't know how I missed that. I had "radeon radeonsi" before.

steveL
Watchman

Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

Posted: Thu Jul 06, 2017 5:00 pm Post subject:

steveL wrote:

I could have sworn it meant "embedded GL" (from Kronos iirc) as opposed to standard OpenGL.

Gusar wrote:

Yeah, but EGL was originally for embedded, too (Kronos site was still mentioning it as an interface to OpenGL ES the other day.)

I see what you're saying, that it's now the "portable" API to access OpenGL and other contexts.
I don't have any experience of OpenGL coding, though, so no idea whether, or to what extent, the type of context dictates later interface usage.

Thanks for the info; mpv looks very useful.

Display posts from previous:

	Gentoo Forums Forum Index Multimedia	All times are GMT Goto page Previous 1, 2
Page 2 of 2

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy