On Sun, 24 Mar 2002 21:39, DaZZa wrote:
> OK, I'm about at the end of my tether with this damn pile of junk.
>
> My previous problems {mentioned in the past} with compiling kernels have
> been expended - now I can't compile _anything_.
>
> Something is badly broken, and I don't know what.
>
> I get error 139 when compiling. I think the thing with ncurses
> was a furfy. Everything I can find on error 139 points to
>
> 1) Bad RAM
> 2) Bad compiler
> 3) Bad swap {maybe}I had a similar problem years ago, but that was giving me SIG11's and also confusing the compiler so code was breaking as it was compiling. Not sure what an error 139 is so this may not be relevant. Anyway, basically it was due to my CPU overheating. I pulled the CPU and found no heatsink grease. dabbed a bit on and also down clocked it. It worked without fault for years afterwards. Another thing to note. You didn't mention whether or not you ran memtest again after removing the 128 DIMM. May be well worth rechecking now.. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
