Dale wrote: > Howdy, > > I was trying to re-emerge some packages. The ones I was working on > failed with "internal compiler error: Segmentation fault" or similar > being the common reason for failing. I did get gcc to compile and > install. But other packages are failing, but some are compiling just > fine.
<<<SNIP>>> > Open to ideas. I hope I don't have to move back to the old rig while > sorting this out. O_O Oh, I updated my old rig this past weekend. Not > a single problem on it. Everything updated just fine. > > Thanks. > > Dale > > :-) :-) > Here's the update. Grant and a couple others were right. So was some of my search results, which varied widely. Shortly after my reply to Grant, I shutdown the new rig. I set my old rig back up so I can watch TV. Then I booted the ever handy Ventoy USB stick and ran the memtest included with the Gentoo Live image. Within minutes, rut roh. :-( The middle section of the test screen went red. It spit out a bunch of "f" characters. I took a pic but haven't downloaded it yet but I figure it has been seen before. Pic is to get new memory stick. Figure I need to prove it is bad. Anyway, I removed one stick of memory, it still failed. Then I switched sticks. That one passed the test with no errors. I put the original stick back in but in another slot. Within minutes, it failed the same as before. So, I put the good stick in and booted into the Gentoo Live image. I mounted my OS, chrooted in and did a emerge -ae @system. The bad stick is on my desk. It looks sad. Like me. Once the emerge was done, I booted back into the OS itself. Everything seems to be working but I'm back down to 32GBs of memory. I'm trying to start a emerge -ae world but got to start a new thread first. It claims some weird things that sounds weird but I don't think it is related to the memory issue. I wonder how much fun getting this memory replaced is going to be. o_O Dale :-) :-)
