| 1 |
On Tue, Jul 5, 2011 at 2:23 PM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> Dale wrote: |
| 3 |
>> |
| 4 |
>> Well, I tried a different kernel. Same thing. I tried reseting the BIOS |
| 5 |
>> and lurking around in there for a bit as well. Same thing. So, right now |
| 6 |
>> I'm chewing on a emerge -e kde-meta. After I remembered the power failure |
| 7 |
>> the other day, I suspect a corrupt file somewhere. I'm just glad I have |
| 8 |
>> Fluxbox on here. I'm in it right now and it works OK. I just wish the |
| 9 |
>> little bar at the bottom was larger. So far, nothing I click changes that. |
| 10 |
>> Tough on my eyes too. Teeny tiny stuff down there. o_o |
| 11 |
>> |
| 12 |
>> Thinking back, I should have booted the CD and run file system checks. |
| 13 |
>> Crap, the one thing I didn't think of. < sighs > |
| 14 |
>> |
| 15 |
>> I still use Nvidia's driver here. it has worked well for me at least. I |
| 16 |
>> don't use any fancy hardware or play any serious games so it works well, so |
| 17 |
>> far at least. That may change next week. lol You know me. Something new |
| 18 |
>> pretty regular. |
| 19 |
>> |
| 20 |
>> I don't guess I use kdepim stuff. It's installed so who knows. Any |
| 21 |
>> relation to pam? |
| 22 |
>> |
| 23 |
>> Dale |
| 24 |
>> |
| 25 |
>> :-) :-) |
| 26 |
>> |
| 27 |
> |
| 28 |
> Well, I got rid of openldap. It runs longer but still crashes so I am back |
| 29 |
> to Fluxbox again, which works fine. I also started with a fresh .kde4 |
| 30 |
> directory. That seemed to help more than anything else. It lasted a LOT |
| 31 |
> longer after that. I don't know if it was a coincidence or what but it did |
| 32 |
> lock up once when I logged into Konsole as root. |
| 33 |
> |
| 34 |
> I started a emerge -e world this time. This thing has 4 cores so it won't |
| 35 |
> take to long. Any ideas on what else I can try? If this emerge doesn't |
| 36 |
> help, it has to be a config file somewhere. |
| 37 |
> |
| 38 |
> Again, I'm pretty sure it is not hardware. It runs fine when compiling in a |
| 39 |
> console and I have run from systemrescue stick as well. Hardware seems to |
| 40 |
> work fine. |
| 41 |
> |
| 42 |
> Ideas? |
| 43 |
|
| 44 |
It's a long shot, but since you're using nvidia, I had random lockups. |
| 45 |
It turned out to be due to faulty handling of the on-by-default |
| 46 |
aggressive power savings mode of my Nvidia card. It was solved by |
| 47 |
placing this undocumented incantation, pieced together from various |
| 48 |
Google searches, in my xorg.conf device section for my video card: |
| 49 |
|
| 50 |
Section "Device" |
| 51 |
Identifier "nVidia GT 240" |
| 52 |
Driver "nvidia" |
| 53 |
Option "RegistryDWords" "PowerMizerEnable=0x1; |
| 54 |
PerfLevelSrc=0x3322; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1" |
| 55 |
EndSection |
| 56 |
|
| 57 |
After that, everything works wonderfully. |
| 58 |
|
| 59 |
You can also use nvidia-settings to change the power saving mode at |
| 60 |
run-time, but it does not save it and you must do it every time you |
| 61 |
log into X, which is annoying. The xorg.conf method above requires no |
| 62 |
further action. |
| 63 |
|
| 64 |
Your card may not even support PowerMizer, who knows? I thought I'd |
| 65 |
mention it just in case. |
Archives