- WLUG - wlug.mailman3.com

Announce: Meeting November 14th 7PM, WPI Higgins Labs 230
by Chuck Anderson Nov. 14, 2012

Nov. 14, 2012

Sorry I'm going to be missing the meeting this month, and thanks to Henrique for taking care of the room. -Chuck On Tue, Nov 13, 2012 at 03:14:34PM -0500, Henrique wrote: > Hey! > > I just talked to Chuck, and he is a bit busy. I got WLUG the same room as > last time Higgins Labs, Room 230, > (HL230<https://maps.google.com/maps?q=42.274129,-71.808384&num=1&vpsrc=0&ie=UTF8&l…>), > if you have any problem locating or getting into the building, just send me > a message at (631) 316-8142. I also already got a better room for next > month. > > Do we have a topic? > > Cheers, > Henrique "nican" Polido.

1 0

help diagnosing PC issue: suspect power supply
by Brett Russ Nov. 7, 2012

Nov. 7, 2012

Hi, I'm trying to diagnose a home built PC running fine since 2007 but lately starting to act odd. Here are the system specs: Intel Core 2 Duo 1.8GHz cpu Asus P5B Deluxe mobo Nvidia 7900GS graphics card Kingston KHX6400 2x1GB DDR2 memory Sparkle ATX 400W power supply 3x 1TB SATA HDDs 1x SATA DVD-RW $ uname -a Linux spider 3.0.0-25-generic #41-Ubuntu SMP Mon Aug 13 17:58:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=11.10 DISTRIB_CODENAME=oneiric DISTRIB_DESCRIPTION="Ubuntu 11.10" $ uname -a Linux spider 3.0.0-25-generic #41-Ubuntu SMP Mon Aug 13 17:58:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux What recently changed: i) replaced monitor, last one died ii) (carefully) vacuumed the dust from inside. Kept hand on case chassis, didn't touch any PCB/chips, etc. Here are the symptoms: 1) first started seeing BIOS claims of bad CMOS checksum at boot time. Immediately suspected the CMOS battery, replaced it and reset CMOS settings but I continue to see this. This is the one symptom that I can't yet place, unless it's simply a bad replacement battery. 2) next started seeing the monitor fail to wake up after entering power save 3) powering on the PC shows issues: 3a) often the monitor won't wake at boot 3b) the bios often doesn't finish POST, gets stuck at splash screen 3c) bios settings often don't survive across power cycles (possibly related to #1--battery issue?) 3d) bios doesn't always give the affirmative beep (likely same symptom as 3a, 3b) 3e) a cold power on or reset can take several "tries" before the system stays on. I.e. fans will spin up, then spin down, one to three times before staying on. When this happens it's pretty much guaranteed that it won't boot successfully. 4) system will freeze to user input while up. I.e. once I get Linux booted, as long as I disable monitor power save it will stay running for a while, but I observed it stopped responding to KB and mouse input earlier this morning. Here's what I've tried: a) reseated both DIMMs, reproduced issues; tried with just one DIMM, repro'd; tried other DIMM, repro'd b) reseated graphics card, repro'd; removed graphics card (now headless), repro'd problem 3e c) reseated CMOS battery (CR2032), repro'd d) pulled all non-essential cables and internal connections, including power and SATA cables from all drives, repro'd e) updated BIOS to latest version, repro'd Unfortunately I don't have another ATX power supply to try, but was thinking of buying one. I might also try an old PCI video card, but I suspect due to repro (b) above that it's not the cause. Anyone have any other insights or agree it sounds like a bad PS? I still can't explain symptom (1), will probably buy another battery to be sure. Five years seems like an old PC, but I'm not a gamer so this suits me fine. Thanks, Brett

10 17

Next meeting on the 14th?
by Tim Keller Nov. 1, 2012

Nov. 1, 2012

Hey Gang, Firstly, I presume that the next meeting is going to be on the 14th? Secondly, do we have a topic? Later, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

1 0

Free hardware: Internal IDE CD drives
by joel d Oct. 26, 2012

Oct. 26, 2012

Could anyone use some internal CD drives? Just found a box full of them. They are "bare" IDE CD readers with no cables, drivers or manuals. Will gladly bring as many as people want to the next meeting. Don't be shy, I probably have 30 of them, and all are guaranteed to be worth every penny of free! Please kindly reply to me via e-mail directly if interested (to not clog up the WLUG e-mail). Thank you, Joel joelgroup(a)gmail.com

1 0

Monitoring for a network
by Eric Martin Oct. 24, 2012

Oct. 24, 2012

I'm trying to get a better handle on what's happening on my network at work. I'm currently using Nagios to monitor the big things (Server health, switch health, etc), but I'd like more granular statistics (how much data is coming and going, are any links saturated, etc). A quick glance shows that MRTG, Cricket, and RRD are good things to start playing with. I'm staring to play around with MRTG, but I'm hearing rumors of scalability issues and I don't want to get deep into MRTG if I should be putting resources elsewhere. A quick sketch of the network is a few internet connections, our router, and a few switches for networking along with a few switches for VoIP as well as our PBX. I don't want to monitor every port all the time, I instead want to monitor the uplinks of the switches to have a good idea, and look at the switch if something looks awry. My question to the group is, what do you use / recommend, and do you have anything that sticks out in your head about any of these packages (good or bad)? Thanks in advance, -- Eric Martin

6 6

I presume we're meeting the 10th of Oct?
by Tim Keller Oct. 10, 2012

Oct. 10, 2012

Hey Gang! I presume we're having a meeting on the 10th? Does anybody have a topic/idea? Thanks, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

4 8

Possible problem with demo tomorrow...
by Tim Keller Oct. 9, 2012

Oct. 9, 2012

There's that old adage, when it rains it pours... Work critical stuff has made it hard for me to focus on getting the demo to work completely. I can do two things... 1. I can do my presentation without the demo. 2. I can do my presentation next month, giving me time to get the demo working right, etc. What do you guys want me to do? Thanks, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

2 1

Re: [Wlug] help diagnosing PC issue: suspect power supply
by joel d Oct. 9, 2012

Oct. 9, 2012

> From: Brett Russ <bruss(a)alum.wpi.edu> > Subject: Re: [Wlug] help diagnosing PC issue: suspect power supply > To: Worcester Linux Users Group <wlug(a)mail.wlug.org> > Message-ID: > <CAGcHgFN4odSRHmS=jjYuvEDy1myRMOgKEYxy0bWu9e4-3V9i7A(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Mon, Oct 1, 2012 at 7:57 AM, Brett Russ <bruss(a)alum.wpi.edu> wrote: >> On Sat, Sep 29, 2012 at 6:19 PM, Chuck Anderson <cra(a)wpi.edu> wrote: >>> I agree that the power supply is suspect. You can measure the voltage >> >>> Alternatively, it may be easier to just try a replacement. >> >> I have a new one on the way. I'll reply here with the results. > > Well, brand new power supply and the system behaves the same > problematic way as before. > > So next try is the memory, as another list reply suggested. I've had > memtest86 running against both DIMMs for 47+ hours and counting, 70 > total passes so far, and 0 errors. Remember I'd already tried > removing first one DIMM, then the other, and the problem repro'd > either way. So by these measures it'd seem the memory is OK? I know > some mem problems take days to show up so I'll just leave this running > for a couple more days anyway. > > Not much more I can do here, as I've seen repros with most everything > else unplugged so I'm now thinking it must be the motherboard. > Perhaps I will try reseating the CPU--haven't done that yet. > > Recall the system is having trouble POST'ing: it hangs at various > points before BIOS POST completes, i.e. I don't get a confirming > 'beep' at end of POST and in some cases the monitor won't wake, other > cases the BIOS splash screen stays splashed, etc. The full original > email is here: > http://mail.wlug.org/pipermail/wlug/2012-September/008059.html > > Anyway, if anyone has other ideas here I'd welcome them. > > Thanks again, > Brett > Hi Brett, You sound pretty convinced this is a PC hardware problem. I think I missed the earlier discussion, but how exactly do you know this is hardware at fault (vs anything not hardware at fault) and how certain are you? Have you tried running a "bootable operating system" via a CD or DVD drive as a diagnostic step (will it boot Ubuntu or another from the optical drive)? If CD/DVD boot is out, there are thumb drive bootable images also. I would start here and rule out everything that is not hardware. As a test, if a different O.S. than Ubuntu 11.10, runs well (except slower) from an optical drive, your hardware is likely fine (and instead have an Ubuntu 11 or app or driver problem). Step only takes a few minutes and is very telling (and well worth it IMHO). This step will likely tell you if it is hardware vs everything else. So if you can assure yourself it is hardware 100% ... All the PC hardware I have worked on in the past years is pretty much self diagnosing/reporting. In this case, your job if you choose to accept it, is to "read and decipher what the motherboard is telling you at boot up". To speak the language of your motherboard, you need to check for any of the following information: External to case, Rear facing LEDs (often have many and are multi-colored) On motherboard LEDs, viewable only inside Beep tones heard at boot up Error or other messages displayed quickly at bootup You need to read the "diagnostics" page of your model's specific PC or motherboard vendor's manual for this specific PC/motherboard to decipher what it is seeing at bootup (based upon lights/beeps/LEDS/etc). Sounds like: You either have two bad power supplies, or this is not the problem. You could have bad memory DIMM(s) that do pass MemTest86 (these test help, but I have seen them pass on bad chips it is a bit of a long shot though). You have changed the motherboard battery and flashed the latest BIOS. Don't rule out a new BIOS being a problem (glitch in install or wrong one or BIOS version problem) You still have a problem that could be hardware or not. You could have an Ubuntu 11 playing well with your motherboard, thus a test of another OS and version... If it was my PC I would next rule out the following in this order: Test and work on whatever the motherboard manufacturer is telling you via lights/beeps/LEDs/boot messages. Ubuntu V11.10, not because I don't like it but trying something else for 15 minutes could tell you something. The current version of CMOS you flashed to the motherboard

1 0

Announce: WLUG Meeting Wed 10/10 7PM: OpenStack
by Chuck Anderson Oct. 9, 2012

Oct. 9, 2012

Hi folks, The next Worcester Linux Users' Group (WLUG) monthly meeting will be held on Wednesday, October 10, at 7PM. The location will be WPI Higgins Labs, room 230 (computer lab). Wednesday, October 10, 7:00 - 9:00 PM WPI Higgins Labs, room 230 (computer lab) WLUG member Tim Keller will be giving a presentation on OpenStack, open source software for building private and public clouds. Afterwards, we will go out for pizza and continue our discussions. See you there, Chuck President, Worcester Linux Users' Group http://www.wlug.org/

1 0

Re: [Wlug] Wlug Digest, Vol 107, Issue 13
by Karl Lind Oct. 1, 2012

Oct. 1, 2012

Hi Brett, First off, CMOS checksum errors during boot refer to MEMORY not the BIOS. Also almost all your symptoms point to a possible memory issue. Do Chuck's stuff to verify that you don't have a power drain that's causing a memory issue. Get a Memory Test utility and find out which DIMM is causing the problem. Carefully remove the DIMM and using a #2 pencil eraser, clean the contacts and replace the DIMM (The rubber removes oxidation that prevents contact) and don't forget to keep grounded! (You, not the DIMM). Cheers Karl On Sun, Sep 30, 2012 at 12:00 PM, <wlug-request(a)mail.wlug.org> wrote: > Send Wlug mailing list submissions to > wlug(a)mail.wlug.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.wlug.org/mailman/listinfo/wlug > or, via email, send a message with subject or body 'help' to > wlug-request(a)mail.wlug.org > > You can reach the person managing the list at > wlug-owner(a)mail.wlug.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Wlug digest..." > > > Today's Topics: > > 1. help diagnosing PC issue: suspect power supply (Brett Russ) > 2. Re: help diagnosing PC issue: suspect power supply > (Chuck Anderson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 29 Sep 2012 14:32:05 -0400 > From: Brett Russ <bruss(a)alum.wpi.edu> > Subject: [Wlug] help diagnosing PC issue: suspect power supply > To: Worcester Linux Users Group <wlug(a)mail.wlug.org> > Message-ID: > <CAGcHgFNRd2jLrywD977a0jZChqEREnNBt529abY0= > fh2OU5FAA(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I'm trying to diagnose a home built PC running fine since 2007 but lately > starting to act odd. Here are the system specs: > Intel Core 2 Duo 1.8GHz cpu > Asus P5B Deluxe mobo > Nvidia 7900GS graphics card > Kingston KHX6400 2x1GB DDR2 memory > Sparkle ATX 400W power supply > 3x 1TB SATA HDDs > 1x SATA DVD-RW > > $ uname -a > Linux spider 3.0.0-25-generic #41-Ubuntu SMP Mon Aug 13 17:58:59 UTC 2012 > x86_64 x86_64 x86_64 GNU/Linux > > $ cat /etc/*release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=11.10 > DISTRIB_CODENAME=oneiric > DISTRIB_DESCRIPTION="Ubuntu 11.10" > > $ uname -a > Linux spider 3.0.0-25-generic #41-Ubuntu SMP Mon Aug 13 17:58:59 UTC 2012 > x86_64 x86_64 x86_64 GNU/Linux > > > What recently changed: > > i) replaced monitor, last one died > > ii) (carefully) vacuumed the dust from inside. Kept hand on case chassis, > didn't touch any PCB/chips, etc. > > > Here are the symptoms: > > 1) first started seeing BIOS claims of bad CMOS checksum at boot time. > Immediately suspected the CMOS battery, replaced it and reset CMOS settings > but I continue to see this. This is the one symptom that I can't yet > place, unless it's simply a bad replacement battery. > > 2) next started seeing the monitor fail to wake up after entering power > save > > 3) powering on the PC shows issues: > > 3a) often the monitor won't wake at boot > > 3b) the bios often doesn't finish POST, gets stuck at splash screen > > 3c) bios settings often don't survive across power cycles (possibly related > to #1--battery issue?) > > 3d) bios doesn't always give the affirmative beep (likely same symptom as > 3a, 3b) > > 3e) a cold power on or reset can take several "tries" before the system > stays on. I.e. fans will spin up, then spin down, one to three times > before staying on. When this happens it's pretty much guaranteed that it > won't boot successfully. > > 4) system will freeze to user input while up. I.e. once I get Linux > booted, as long as I disable monitor power save it will stay running for a > while, but I observed it stopped responding to KB and mouse input earlier > this morning. > > > Here's what I've tried: > > a) reseated both DIMMs, reproduced issues; tried with just one DIMM, > repro'd; tried other DIMM, repro'd > > b) reseated graphics card, repro'd; removed graphics card (now headless), > repro'd problem 3e > > c) reseated CMOS battery (CR2032), repro'd > > d) pulled all non-essential cables and internal connections, including > power and SATA cables from all drives, repro'd > > e) updated BIOS to latest version, repro'd > > > Unfortunately I don't have another ATX power supply to try, but was > thinking of buying one. I might also try an old PCI video card, but I > suspect due to repro (b) above that it's not the cause. > > Anyone have any other insights or agree it sounds like a bad PS? I still > can't explain symptom (1), will probably buy another battery to be sure. > Five years seems like an old PC, but I'm not a gamer so this suits me fine. > > > Thanks, > Brett > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://mail.wlug.org/pipermail/wlug/attachments/20120929/8959d06a/attachmen… > > ------------------------------ > > Message: 2 > Date: Sat, 29 Sep 2012 18:19:47 -0400 > From: Chuck Anderson <cra(a)WPI.EDU> > Subject: Re: [Wlug] help diagnosing PC issue: suspect power supply > To: Worcester Linux Users Group <wlug(a)mail.wlug.org> > Message-ID: <20120929221947.GH12327(a)angus.ind.WPI.EDU> > Content-Type: text/plain; charset=us-ascii > > On Sat, Sep 29, 2012 at 02:32:05PM -0400, Brett Russ wrote: > > Sparkle ATX 400W power supply > > Anyone have any other insights or agree it sounds like a bad PS? I still > > can't explain symptom (1), will probably buy another battery to be sure. > > Five years seems like an old PC, but I'm not a gamer so this suits me > fine. > > I agree that the power supply is suspect. You can measure the voltage > on a spare power supply hard drive connector, there should be 12v from > black to yellow, and 5v from black to red. If that checks out, you > should measure from the motherboard ATX connector as some of the other > voltages may be out of spec. You can find the standard ATX pinouts > and voltages online. Finally, you can test with the power supply > completely disconnected from the PC. Again, you can find instructions > online for how to do that, as it requires a jumper wire for the power > supply to power on. > > Alternatively, it may be easier to just try a replacement. > > > ------------------------------ > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > > End of Wlug Digest, Vol 107, Issue 13 > ************************************* >

1 0