Lose DRI after exit/restart fluxbox

bioe007 · 02-24-2007, 06:24 PM

Hi,

problem 1
I am losing DRI when I 'Exit' and restart (startx) fluxbox. (Not the fluxbox 'restart' command)

I think I have figured out from lsmod that once X starts up, two modules [ drm and radeon ]are loaded, then remain so. Which seems to be the problem with DRI, because if I exit fluxbox and then rmmod the modules and re-startx I get DRI working again. Which is a bit of a pain.

I'd like to automate this module unloading. I see at least two logical places to do it but I'm not sure which is better or if there is a more appropriate way, i'm hoping for some advice on this:

#1) make a rmmod script and configure the fluxbox 'exit' menu option to rmmod before exiting.
- This could be potentially bad though if I ever get a console FB and DRI working. (-radeon would be a problem?)
- Also, I can't find the syntax for exiting fluxbox? my .fluxbox/menu has this entry:

Code:

[exit] (Exit)

I'm not sure how to send exit to the X11 server?

#2) have ~/.xinitrc rmmod right before starting up? Im not sure how/where to do that though.
something like:
rmmod -f radeon
rmmod -f drm
startfluxbox

<edit-later- i tried adding the above with /sbin/rmmod to ~/.xinitrc and it doesnt seem to work)

problem 1.b
For what I'd like a script to do from the I need root access from the script.

I can not seem to figure out sudo ?? I have visudo'd my sudoers file:

Code:

# User alias specification
User_Alias LOCAL = perry

# User privilege specification
root    ALL=(ALL) ALL
LOCAL   ALL=NOPASSWD:ALL
perry   ALL=NOPASSWD:/usr/bin/chvt, /sbin/lspci

but never gotten any results from it, the perry line above was to be for a 'suspend to ram' script but I always get errors from sudo: 'must be setUID to root' or something like that.

please don't RTFM me - I have read the man sudo pages. I think am perhaps a 'special needs sudoer', 'cause I am not getting it.

thanks for any help.

H_TeXMeX_H · 02-24-2007, 07:31 PM

Where do those modules that cause the problem get loaded (drm and radeon) ? It might be in '/etc/X11/xorg.conf', why don't you check and comment them out if they are in there (assuming they are causing the problem).

As for getting root access for a script ... I have never been able to set up sudo properly with all the man pages and how-to's and all ... it just won't work. Instead, you could just set the SUID bit for the permissions of the script as well as chown to root (when the script is run, it gains root permissions).

bioe007 · 02-24-2007, 09:56 PM

Quote:

Originally Posted by H_Tex_Mex_H

Where do those modules that cause the problem get loaded (drm and radeon) ? It might be in '/etc/X11/xorg.conf', why don't you check and comment them out if they are in there (assuming they are causing the problem).

It is indeed from xorg.conf (drm anyway, and radeon, by way of being my graphics driver). I need them to properly do 3D, but they must be modular, else I get no DRI.

So when I exit an X session, they are still loaded, but for some reason if they are loaded already when an X session starts - I get no acceleration.

Quote:

Originally Posted by H_Tex_Mex_H

set the SUID bit for the permissions of the script as well as chown to root (when the script is run, it gains root permissions)

Sounds good, I will try that.

Any tips on how to 'exit' the x-session from a script?

many thanks.

H_TeXMeX_H · 02-25-2007, 12:41 AM

Quote:

Originally Posted by bioe007

It is indeed from xorg.conf (drm anyway, and radeon, by way of being my graphics driver). I need them to properly do 3D, but they must be modular, else I get no DRI.

So when I exit an X session, they are still loaded, but for some reason if they are loaded already when an X session starts - I get no acceleration.

Well, what I would do (now this is a bit unorthodox), edit '/usr/X11/bin/startx' (back it up before you do), rmmod at the beginning, modprobe at the end.

For exiting X-server ...

Code:

killall X

dracolich · 02-25-2007, 02:20 PM

Quote:

have ~/.xinitrc rmmod right before starting up? Im not sure how/where to do that though.
something like:
rmmod -f radeon
rmmod -f drm
startfluxbox

That would be better than

Quote:

Well, what I would do (now this is a bit unorthodox), edit '/usr/X11/bin/startx' (back it up before you do), rmmod at the beginning, modprobe at the end.

Quote:

<edit-later- i tried adding the above with /sbin/rmmod to ~/.xinitrc and it doesnt seem to work)

That's because modprobe and rmmod need root access. You can try again to get sudo working, or in the ~/.xinitrc change your rmmod lines to look like this

Code:

su -c "rmmod -f radeon ; rmmod -f drm"

Afterward the startx command should prompt you for a password. Use the root password. The root access will apply only to the commands in "" on the su -c line. The startx command that follows will be run by your user.

bioe007 · 02-26-2007, 12:06 AM

Thanks all, I have it working now.. my solution?

Well I chose (.. er, uhm.. defaulted to after numerous other attempts

) a 'combination' approach. I created script, that has the rmmod commands, made it executable, and placed it in my /etc/X11 directory. This coupled with ?properly editing my sudoers file has it working.

Now in ~/.xintirc I call this script and it unloads the offending modules.

Thanks for all your help!