v4169sgr
June 10th, 2008, 10:24 PM
Howdy folks,
I'm here hoping someone might be able to shed some light on one or two of the few clouds that have speckled my otherwise pure blue sky ubuntu summer:guitar:
I'm using 8.04 32 bit desktop with an nvidia 6600GE card, on a workstation / server with dual core athlons, 2GB ram etc. This machine provides email, browsing, music, entertainment, photo management etc to my famly users, and a thin client to a rescued PIII in the next room via LTSP. I recently clean installed on a new HDD and migrated over user files from Dapper. Generally, life is good, even great, but for me the #1 killer feature is ease of maintenance.
So here's the small cloud:
I seem to be having some difficulty successfully running Maelstrom, frozen bubble, and neverball, as examples, from the standard repos, without somehow endangering the integrity of the system:
* The game when running will always take 100% of one CPU;
* Graphics run fast and smooth, sound is great, there is no jerkiness or tearing, BUT ... changes in graphics modes almost invariably cause the game to completely lock up requiring a kill -9 from the shell, meanwhile continuing to take 100% of one CPU. This happens when e.g. transitioning from initial menus to main graphics screen [frozen bubble], or when exiting the game [neverball].
* Sometimes the game display fails altogether [frozen bubble in full screen mode] showing 'Cannot display this video mode', requiring use of the console virtual terminals [Alt-F1 etc] to recover.
Needless to say 'this did not happen with dapper':) and therefore an easy target is compiz-fusion, which is the big obvious difference.
I am not looking for a magic wand, or instant answers, but for a strategy or tactic to manage the situation as I find it:
* Am I missing something / doing something wrong - is there a flag or switch I can set somewhere to resolve these problems?
* If this is a known bug / issue with a long time frame to resolve, is there a workaround?
* Must these things be put back in the draw for the duration of this install? Not a massive issue, since embedded video etc all works fine and keeps the users happy. So far, they have not noticed, but its only a matter of time, and for them there would be no obvious get-out other than the Big Red Button *shudder*.
I have tried:
- switching between metacity and compiz;
- installing the Fusion Button [and using it];
- tried:
sudo nvidia-xconfig --add-argb-glx-visuals -d 24;
- changing appearance to 'No Graphics';
None of the above has made the slightest bit of difference, which suggests I am looking in the wrong place.
Suggestions welcome! Surely someone has come across these problems before?
Thanks in advance!:popcorn:
I'm here hoping someone might be able to shed some light on one or two of the few clouds that have speckled my otherwise pure blue sky ubuntu summer:guitar:
I'm using 8.04 32 bit desktop with an nvidia 6600GE card, on a workstation / server with dual core athlons, 2GB ram etc. This machine provides email, browsing, music, entertainment, photo management etc to my famly users, and a thin client to a rescued PIII in the next room via LTSP. I recently clean installed on a new HDD and migrated over user files from Dapper. Generally, life is good, even great, but for me the #1 killer feature is ease of maintenance.
So here's the small cloud:
I seem to be having some difficulty successfully running Maelstrom, frozen bubble, and neverball, as examples, from the standard repos, without somehow endangering the integrity of the system:
* The game when running will always take 100% of one CPU;
* Graphics run fast and smooth, sound is great, there is no jerkiness or tearing, BUT ... changes in graphics modes almost invariably cause the game to completely lock up requiring a kill -9 from the shell, meanwhile continuing to take 100% of one CPU. This happens when e.g. transitioning from initial menus to main graphics screen [frozen bubble], or when exiting the game [neverball].
* Sometimes the game display fails altogether [frozen bubble in full screen mode] showing 'Cannot display this video mode', requiring use of the console virtual terminals [Alt-F1 etc] to recover.
Needless to say 'this did not happen with dapper':) and therefore an easy target is compiz-fusion, which is the big obvious difference.
I am not looking for a magic wand, or instant answers, but for a strategy or tactic to manage the situation as I find it:
* Am I missing something / doing something wrong - is there a flag or switch I can set somewhere to resolve these problems?
* If this is a known bug / issue with a long time frame to resolve, is there a workaround?
* Must these things be put back in the draw for the duration of this install? Not a massive issue, since embedded video etc all works fine and keeps the users happy. So far, they have not noticed, but its only a matter of time, and for them there would be no obvious get-out other than the Big Red Button *shudder*.
I have tried:
- switching between metacity and compiz;
- installing the Fusion Button [and using it];
- tried:
sudo nvidia-xconfig --add-argb-glx-visuals -d 24;
- changing appearance to 'No Graphics';
None of the above has made the slightest bit of difference, which suggests I am looking in the wrong place.
Suggestions welcome! Surely someone has come across these problems before?
Thanks in advance!:popcorn: