| 1 |
On Wed, Jul 6, 2011 at 3:00 PM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> Mark Knecht wrote: |
| 3 |
>> |
| 4 |
>> If I had to guess I'd say, since this followed a power failure where |
| 5 |
>> the machine was live and operating (if I've understood the thread |
| 6 |
>> through a quick scan) that some file on disk has gotten corrupted and |
| 7 |
>> it's that corruption that's causing the problem. You've checked |
| 8 |
>> memory. Let's assume that te processor and MB weren't damaged by this |
| 9 |
>> event. If that's the case - and unfortunately I don't know of any way |
| 10 |
>> to ensure it hasn't as it requires one to have a bit-accurate image of |
| 11 |
>> the machine before the power failure - there's probably no way to |
| 12 |
>> eliminate this as a possibility short of an emerge -e @world. |
| 13 |
>> |
| 14 |
>> It's not where I'd start. I'd probably look for core dump files or |
| 15 |
>> very carefully do experiment s trying to isolate exactly what part of |
| 16 |
>> KDE is firing off the problem. re-emerging the NVidia driver is a |
| 17 |
>> no-brainer as it takes no more than 1-2 minutes to test things. |
| 18 |
>> Rebuilding the machine is certainly more involved. |
| 19 |
>> |
| 20 |
>> If you have lots of disk space you might rsync the whole machine to a |
| 21 |
>> new partition to do the work, then using something other than KDE |
| 22 |
>> which doesn't crash rebuild the copy from a chroot which leaves the |
| 23 |
>> machine usable while the rebuild is going on. |
| 24 |
>> |
| 25 |
>> None of this sounds like fun... |
| 26 |
>> |
| 27 |
>> - Mark |
| 28 |
>> |
| 29 |
>> |
| 30 |
>> |
| 31 |
> |
| 32 |
> I did something similar at least. I have two drives in here that are for my |
| 33 |
> OS. I have a third that is for data, videos, audio stuff and documents. |
| 34 |
> The data drive is a 750Gb. The old main OS drive is a 160Gb and the spare |
| 35 |
> OS drive is a 250Gb. I downloaded a stage3 tarball. I then set up the |
| 36 |
> spare OS drive and mounted the partitions basically following the docs. I |
| 37 |
> then copied over /etc, disfiles and the world file. After that, I did a |
| 38 |
> emerge -e world which installed everything that I had before. It also has a |
| 39 |
> slightly newer kernel as well. |
| 40 |
> |
| 41 |
> So, after running my memtest this morning while I took a nap, I booted into |
| 42 |
> the new install. I checked with the mount command to make sure I was in the |
| 43 |
> new install too. I deleted EVERYTHING KDE in my home directory. After |
| 44 |
> that, I logged into KDE. A box popped up that composite was disabled. It |
| 45 |
> said I could hit shift alt F12 to enable. After I started Firefox, it |
| 46 |
> locked up complete with my keyboard lights blinking again. |
| 47 |
> |
| 48 |
> What does Fluxbox use as opposed to KDE? Both use the Nvidia drivers right? |
| 49 |
> I use KDM for my login screen and I think nvidia is loaded when it starts |
| 50 |
> and it uses nvidia thereafter. So, if it was the driver, would it not mess |
| 51 |
> up in Fluxbox too? What makes Fluxbox work and KDE fail? |
| 52 |
> |
| 53 |
> Could my video card be having issues? I may take the sides off and unplug |
| 54 |
> replug everything and give it all a once over. Maybe just a bad connection |
| 55 |
> or something. Maybe? |
| 56 |
> |
| 57 |
> If one of you guys were me, would you order a video card and try that? Keep |
| 58 |
> in mind, I have surge protection inside the UPS on the wall side. I also |
| 59 |
> have a surge protector strip that my modem, router, puter and monitor plugs |
| 60 |
> into. It's kind of hard to imagine that a surge could make it through all |
| 61 |
> that and not at least smell up the place a bit. I'm not saying it couldn't |
| 62 |
> but just hard to imagine. I got surge protection coming out the ears here. |
| 63 |
> |
| 64 |
> Thoughts? |
| 65 |
> |
| 66 |
> Dale |
| 67 |
|
| 68 |
And this is your newer machine machine, correct? The one you built a |
| 69 |
few months ago IIRC? |
| 70 |
|
| 71 |
Sounds like you've takn the right steps to eliminate lots of problem |
| 72 |
sites and it just isn't working. What a drag! |
| 73 |
|
| 74 |
A machine lockup can come from almost anything not working. Bad |
| 75 |
software is the easy one, but it could be hardware. |
| 76 |
|
| 77 |
As for fluxbox vs KDE that's apples and oranges. They probably use |
| 78 |
totally different parts of X and do it in very different ways. However |
| 79 |
if fluxbox works perfectly for weeks then it wouldn't seem likely to |
| 80 |
be a hardware issue unless it's a really unlikely corner case, but you |
| 81 |
wouldn't think KDE would hit is every time and fluxbox never hits it. |
| 82 |
|
| 83 |
Have you tried the most up to date ~amd64 drivers? |
Archives