From owner-freebsd-questions Thu Jan 27 22:33:24 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 1624E15019 for ; Thu, 27 Jan 2000 22:33:22 -0800 (PST) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2iveajk.dialup.mindspring.com [165.247.42.116]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id BAA11352; Fri, 28 Jan 2000 01:33:13 -0500 (EST) Message-ID: <389137E4.CA0879F4@confusion.net> Date: Fri, 28 Jan 2000 01:32:04 -0500 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: R Joseph Wright Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Why Doesn't XFree86 Upgrade Properly References: <3.0.32.20000128074338.00740384@idx.com.au> <3890AF42.21F5F672@nwlink.com> <20000128100929.H3290@jonc.logisticsoftware.co.nz> <3890FF00.53D88D7C@confusion.net> <3891315C.9BD4FB66@nwlink.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a friend who had some ram go bad two weeks after he bought it. It turned out someone had needed electrical work done, so the ground line was ungrounded for some bizarre reason (bad electrician I'd guess). He touched his case and felt a little static shock, and for reasons beyond me this somehow managed to get to a simm and break it, or at least that's his best guess. Bad set of coincidences I suppose. The first thing to do is try removing one of the simms/dimms/whateveryou'vegot and compiling with the rest. Do this until you get it to build, that's probably the bad RAM. Another good sign is if the build doesn't always fail at the same place. YMMV It's hard to say if the ram has gone bad so quickly, and why can often be guesswork. Try building other big ports (KDE, emacs come to mind) or building world. The upshot of all this is that ram is cheap, so you might be able to get more than you're losing. IMHO the best part of my friend losing ram was that the replacement came with a reusable air bag that could be inflated with a straw, and we (being the morons that we are) had a good time throwing computer equipment at walls. We threw some SOHOware 5 port hub out a six story window, and it came out working fine. Thrills for idiots I suppose. But I digress...... Just My $1.95 (no way I'd make you read all that for mere pennies) Laurence R Joseph Wright wrote: > > Laurence Berland wrote: > > > > Logical and oft-quoted extension: If you think you've got a hardware > > problem, try building something big. Too many people report panics on > > make buildworlds only to find it's the first sign of the death of their > > RAM. > > The funny thing is, I've never had a panic on a make world, only big > ports. And my ram is virtually brand new, could it die within 6 months > of buying it? > > -- > R Joseph Wright > > *I merely took the energy it takes to pout > and wrote some blues --Duke Ellington* > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Laurence Berland, Stuyvesant HS Debate <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 2000 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message