public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] mplayer directfb permissions?
Date: Tue, 26 Apr 2011 20:03:02 +0100	[thread overview]
Message-ID: <201104262003.20100.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20110426133404.GA7426@gaurahari>

[-- Attachment #1: Type: Text/Plain, Size: 2198 bytes --]

On Tuesday 26 April 2011 14:34:05 Indi wrote:
> On Tue, Apr 26, 2011 at 12:30:02AM +0200, Mick wrote:
> > On Monday 25 April 2011 23:38:04 Indi wrote:
> > > On Mon, Apr 25, 2011 at 05:50:01PM +0200, Indi wrote:
> > > > ...using the directfb for vo gives
> > > > sterling results, with the worst files playing happily in sync just
> > > > like I always dreamed -- but only as root!
> > > > 
> > > > Obviously there's a permissions issue somewhere...
> > > 
> > > Oh jeepers, I've made a silly error -- the reason videos were playing
> > > so well as root is that root had no .mplayer/config, :)
> > > Apparently I just needed to clean up my config file and now it works
> > > just fine again with x11 driver. Didn't realize defining a couple of
> > > audio and video filters would impact performance that much but
> > > apparently it really does, at least with avi and mkv files. Sorry for
> > > the noise!
> > > 
> > > For other reasons though it might still be nice to know how to give a
> > > user directfb permission.
> > > 
> > > :)
> > 
> > Just an idea.
> > 
> > Not sure if it uses svgalib - in which case setuid it to root before you
> > fire it up as a plain user.
> > 
> > Alternatively, run strace as a plain user and see at what point it fails
> > to access the files it needs.
> 
> Thanks for the suggestions.
> Was going to look into that just now but after updating the system
> (and runing revdep-rebuild and python updater and --depclean) the
> directfb driver doesn't display properly anymore for some reason.
> Everything else seems fine, and videos are playing in sync with the x11
> driver and all that. I have a feeling from what Ive read STFW that this
> is going to come down to my ATI Mobility 9600 chipset's incomplete kernel
> support and may not be practically solvable to the point of being worth
> pursuing.
> 
> I may pursue it anyway at some point in the future but for right
> now it's been moved to the back burner for a bit.

Are you running KMS in the kernel and have you emerged x11-drivers/radeon-
ucode (not sure if your card needs it) as per:

http://www.gentoo.org/doc/en/xorg-config.xml
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-04-26 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gLBPk-b8-23@gated-at.bofh.it>
     [not found] ` <gLCs2-1ja-21@gated-at.bofh.it>
2011-04-26 13:34   ` [gentoo-user] mplayer directfb permissions? Indi
2011-04-26 19:03     ` Mick [this message]
     [not found] <gLQEG-8s3-3@gated-at.bofh.it>
     [not found] ` <gLQEG-8s3-5@gated-at.bofh.it>
     [not found]   ` <gLQEG-8s3-1@gated-at.bofh.it>
     [not found]     ` <gLVO2-ut-27@gated-at.bofh.it>
2011-04-26 20:40       ` Indi
2011-04-25 22:38 Indi
2011-04-25 22:17 ` Mick
  -- strict thread matches above, loose matches on Subject: below --
2011-04-25 16:45 Indi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201104262003.20100.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox