2013-10-10, 23:44
The white screen issue affects me too on a Shuttle XS35GSv3 with AMD Seymour, but I can wait for a proper fix too. Thanks for all the great work!
2013-10-10, 23:52
Thanks... I was having the white screen issue too, but reverting the commit as suggested by antares81 got my vdpau working nicely again!
I'm running gentoo and was getting the git's.
I'm running gentoo and was getting the git's.
2013-10-11, 01:27
@antares81
I'm going to have to wait for the ppa update. Thanks for the info though. I may give it a try.
I'm going to have to wait for the ppa update. Thanks for the info though. I may give it a try.
2013-10-11, 05:22
according to the launchpad page:
=== Using VDPAU/XvMC accelerated video ===
Supported XvMC drivers: softpipe, r300, r600, radeonsi, nouveau
Supported VDPAU drivers: softpipe, r300, r600, radeonsi, nouveau
how do I know that I'm using the radeonsi drivers? is there an *. so file for that or is this the default? for the /XvMCConfig file?
=== Using VDPAU/XvMC accelerated video ===
Supported XvMC drivers: softpipe, r300, r600, radeonsi, nouveau
Supported VDPAU drivers: softpipe, r300, r600, radeonsi, nouveau
how do I know that I'm using the radeonsi drivers? is there an *. so file for that or is this the default? for the /XvMCConfig file?
2013-10-11, 06:50
(2013-10-10, 19:31)antares81 Wrote: The commit causing it seems to be http://cgit.freedesktop.org/mesa/mesa/co...31a06199c3 . Reverting just that one fixed the white screen for me
Same here. A8-5500.
2013-10-11, 07:14
Yeah I discussed this commit with the oss vdpau devs. It is a permission issue and the Interop patch needs rebasing / adaption. I mailed Christian about it. Yeah such things might happen more often in the future as vdpau oss is still heavily in develpment and as long as the interop patch is not in mainline master.
Edit: Can you verify that one helps: https://gist.github.com/grigorig/6927130 ?
Edit: Can you verify that one helps: https://gist.github.com/grigorig/6927130 ?
2013-10-11, 08:49
How do I build the mesa on my own?
I have the ppa installed atm.. Should I just leave them installed,, remove the ppa and build mesa and install.. and if so.. how to build it? I have cloned it and reverted the commit.
I have the ppa installed atm.. Should I just leave them installed,, remove the ppa and build mesa and install.. and if so.. how to build it? I have cloned it and reverted the commit.
2013-10-11, 09:45
I apologize in advance for my obvious and annoying n00bery, but can I use that patch on the ppa-installed mesa package? And, if yes, how would I go about doing such a thing? Is there a how-to-patch-an-ubuntu-package anyone could point me to?
2013-10-11, 10:15
(2013-10-11, 07:14)fritsch Wrote: Yeah I discussed this commit with the oss vdpau devs. It is a permission issue and the Interop patch needs rebasing / adaption. I mailed Christian about it. Yeah such things might happen more often in the future as vdpau oss is still heavily in develpment and as long as the interop patch is not in mainline master.
Edit: Can you verify that one helps: https://gist.github.com/grigorig/6927130 ?
confirmed, the patch fixes it for me. No need to revert the other commit anymore. Thank you!
2013-10-11, 10:20
2013-10-11, 10:46
just do a
in the source directory. If you want to add it to your repo, use git add/git commit afterwards.
Code:
patch -Np1 -i $patchfile
2013-10-11, 10:50
Code:
$ patch -Np1 -i 32de663ae6a03ea40f307160ea6c6926d70ca18d.patch
patching file src/gallium/winsys/radeon/drm/radeon_drm_winsys.c
patch: **** malformed patch at line 17: /* Enable/disable feature access for one command stream.?
2013-10-11, 10:56
looks like something got messed up while doing copy/paste. Did you use the "Download Gist" button on the left?
2013-10-11, 11:16
I downloaded it again, used the default name.
Code:
$ patch -Np1 -i gistfile1.txt
patching file src/gallium/winsys/radeon/drm/radeon_drm_winsys.c
patch unexpectedly ends in middle of line
Hunk #4 succeeded at 618 with fuzz 1.