1 |
Alan McKinnon wrote: |
2 |
> On Monday 04 July 2011 19:12:50 Jesús J. Guerrero Botella did opine |
3 |
> thusly: |
4 |
> |
5 |
>> 2011/7/4 Dale<rdalek1967@×××××.com>: |
6 |
>> |
7 |
>>> Hi, |
8 |
>>> |
9 |
>>> What mine does: It sort of varies but usually when I login, it |
10 |
>>> may last a couple minutes, usually less, then the Caps Lock and |
11 |
>>> Scroll Lock LED's blink. The Num Lock key is off if that means |
12 |
>>> anything. I tried the SysReq keys but it doesn't do anything |
13 |
>>> at all. According to the messages at the next boot, it doesn't |
14 |
>>> sync or umount either. The mouse pointer no longer moves |
15 |
>>> either. At this point, I hit the reset button which causes |
16 |
>>> steam to come out my ears. I HATE using that button. |
17 |
>>> |
18 |
>>> I'm fairly sure this is not hardware. |
19 |
>>> |
20 |
>> You can never be sure about that. |
21 |
>> |
22 |
>> |
23 |
>>> Right now, I am in Fluxbox and it |
24 |
>>> works fine. I also booted to single user and compiled a bunch |
25 |
>>> of stuff and also tried a different kernel too. I think if it |
26 |
>>> was hardware, it would have had some kind of hick-up during the |
27 |
>>> compile. I did check temps and all is nice and cool, very cool |
28 |
>>> since my A/C is on full blast. I think the oven is outside on |
29 |
>>> full blast instead of in the kitchen. lol It's HOT here, |
30 |
>>> steamy hot. |
31 |
>>> |
32 |
>> You can try turning off the compositing system altogether. You can |
33 |
>> do that by disabling the desktop effects in systemsettings. If |
34 |
>> lockups stop then it's probably something to do with your graphics |
35 |
>> driver and if that's the case you might have better luck with an |
36 |
>> alternative driver. |
37 |
>> |
38 |
> I get frequent crashes that seem to be related to nouveau. |
39 |
> When I used nvidia drivers, they seemed to have a mind of their own |
40 |
> when it came to memory usage and segfaults. |
41 |
> And the entire abomination that shall not be suffered to live called |
42 |
> "kdepim" *definitely* has a mind of it's own. |
43 |
> |
44 |
> |
45 |
> |
46 |
>> |
47 |
>>> I checked messages and the only thing I saw was about a bad |
48 |
>>> option for hp-systray. Surely that wouldn't cause a crash? |
49 |
>>> I'm going to unmerge and test it tho, just to be sure. |
50 |
>>> |
51 |
>> I don't think so. |
52 |
>> |
53 |
|
54 |
Well, I tried a different kernel. Same thing. I tried reseting the |
55 |
BIOS and lurking around in there for a bit as well. Same thing. So, |
56 |
right now I'm chewing on a emerge -e kde-meta. After I remembered the |
57 |
power failure the other day, I suspect a corrupt file somewhere. I'm |
58 |
just glad I have Fluxbox on here. I'm in it right now and it works OK. |
59 |
I just wish the little bar at the bottom was larger. So far, nothing I |
60 |
click changes that. Tough on my eyes too. Teeny tiny stuff down |
61 |
there. o_o |
62 |
|
63 |
Thinking back, I should have booted the CD and run file system checks. |
64 |
Crap, the one thing I didn't think of. < sighs > |
65 |
|
66 |
I still use Nvidia's driver here. it has worked well for me at least. |
67 |
I don't use any fancy hardware or play any serious games so it works |
68 |
well, so far at least. That may change next week. lol You know me. |
69 |
Something new pretty regular. |
70 |
|
71 |
I don't guess I use kdepim stuff. It's installed so who knows. Any |
72 |
relation to pam? |
73 |
|
74 |
Dale |
75 |
|
76 |
:-) :-) |