Because my programing skills aren't l33t enough to take on this job, yet I think that it should be simple enough anyone can do it, i come to the forums with it.
The Action:
It shall switch from one video driver, to another (in xorg). Not exactly on the fly because ctrl+alt+backspace still needs to be pressed.
Why:
FGLRX does not take Suspend2 or Hibernate for that matter. By being able to easily, and quickly switch from fglrx > ati and then back to fglrx will let us, ati users hibernate without first editing the xorg.conf by hand.
How it will work (user end):
The script should execute by double clicking an icon on the desktop, or a quick launch button on the kicker / gnome-panel. Then a xterm will come up with something like
the user inputs the option (1 or 2) and the script does its thing. Now its safe for user to hibernate, or when they come out of hibernate, to get their 3d back (after resetting x or relogging in). Maybe even a step better, if the user pics to go to fglrx, the script will automatically reset xorg and bring up kdm or gdm login screen. And if the user pics ati, it won't do that since when you hibernate and then get out of sleep xorg resets anyway... so there is no point in extra resets.
maybe even a little later down the road somebody can write a front end for it so that the user has 2 radio buttons (ati and radeon) and then the "OK" button and "Cancel".
How it will work (the guts of the code):
There will be 2 xorg.conf files. xorg.conf and xorg.conf_alt. They are exactly identical except for the device being fglrx in one, and ati in another. Doesn't really matter which. Since xorg reads only the "xorg.conf" named file, thus rendering xorg.conf_alt useless, what will happen is the script will just rename the files.
for example. by default we start with
xorg.conf = fglrx
xorg.conf_alt = ati
user has fglrx loaded and wants to go to hibernate, thus turn on ati.
script renames files:
xorg.conf = ati
xorg.conf_alt = fglrx
user hibernates
user reloads system
user runs script to load fglrx:
files get renamed:
xorg.conf = fglrx
xorg.conf_alt = ati
xorg resets. kdm or gdm loads.
user logs in.
session continues.
---------------------
really just a rough idea, if somebody was to write this i am sure it would probably be worked out a tad better.
i know this may look messy, but at least for now (until ati gets their act together) it will make standby a little bit more managable for ati users
(unless i am missing something and there is already a proggy (or a fix) out there to make ati standby possible).
The Action:
It shall switch from one video driver, to another (in xorg). Not exactly on the fly because ctrl+alt+backspace still needs to be pressed.
Why:
FGLRX does not take Suspend2 or Hibernate for that matter. By being able to easily, and quickly switch from fglrx > ati and then back to fglrx will let us, ati users hibernate without first editing the xorg.conf by hand.
How it will work (user end):
The script should execute by double clicking an icon on the desktop, or a quick launch button on the kicker / gnome-panel. Then a xterm will come up with something like
Quote:
|
Originally Posted by
|
maybe even a little later down the road somebody can write a front end for it so that the user has 2 radio buttons (ati and radeon) and then the "OK" button and "Cancel".
How it will work (the guts of the code):
There will be 2 xorg.conf files. xorg.conf and xorg.conf_alt. They are exactly identical except for the device being fglrx in one, and ati in another. Doesn't really matter which. Since xorg reads only the "xorg.conf" named file, thus rendering xorg.conf_alt useless, what will happen is the script will just rename the files.
for example. by default we start with
xorg.conf = fglrx
xorg.conf_alt = ati
user has fglrx loaded and wants to go to hibernate, thus turn on ati.
script renames files:
xorg.conf = ati
xorg.conf_alt = fglrx
user hibernates
user reloads system
user runs script to load fglrx:
files get renamed:
xorg.conf = fglrx
xorg.conf_alt = ati
xorg resets. kdm or gdm loads.
user logs in.
session continues.
---------------------
really just a rough idea, if somebody was to write this i am sure it would probably be worked out a tad better.
i know this may look messy, but at least for now (until ati gets their act together) it will make standby a little bit more managable for ati users
(unless i am missing something and there is already a proggy (or a fix) out there to make ati standby possible).
