Dale wrote:
You have a good point but there is a problem. Some of the kernels I
tried ran on this machine with uptimes of several weeks and not one
lock up. It could be some upgrade that affected this but who knows
what that was since I have updated a lot. As for nvidia, I tried both
versions that work with my card that are in portage. I got the same
with that no matter what I tried.
As for .39 kernels, I mentioned in this mess somewhere that I had
upgraded but ran into problems with that series so I deleted them. I
may just be adding to the problems I am having if I do upgrade again.
But since I got to try something, I'll try the latest .39 and see what
it does.
I remember having this type of problem once before. It turned out to
be a gcc problem if I recall correctly. I went back a version of gcc
and then did a emerge -e world. After that, things worked fine.
Thing is, I have had the same gcc since I built this rig according to
genlop.
Weird.
Dale
:-) :-)
I tried the latest .39 kernel. It does the exact same thing as a .38
kernel. I also tried a kernel that was the first one I made when I
built this rig. It locked up as well. It appears to me that either
every single kernel, including ones that worked fine before, are either
broke or it is not related to the kernel itself. I'm starting to bet on
the last one.
I did notice one thing tho. When I tried to emerge the nvidia drivers
for the .39 kernel, emerge wanted to DOWNGRADE glibc. This ain't my
first trip to Linux land. Can someone explain to me why the heck emerge
wants to do something as crazy as that? I think every one here knows
that is a really bad thing to even think of much less actually try. Is
it possible that something in glibc is causing trouble and this is
someone's wet dream to fix it?
Thanks.
Dale
:-) :-)
