I have an ASUS A7V system running SuSE8.2. I had to power it down last night because of a power failure that the UPS couldn't endure. This morning, when I turn it on, all the lights come on as normal and the fans start up, I hear the drive whir, but after about 1sec, it all stops and the power LED just blinks. I think this indicates sleep mode. I don't know why the system would power up and go right into sleep mode, and I'm hoping that perhaps someone on this list might have a clue. Could the power supply be choking on the load and the system panics into sleep mode? The PS is a StarTech and little over a year old, so it should be okay. Could apcupsd somehow have put the system into sleep mode and that's where it's going to go when it powers up? Could the BIOS be hosed? If that's possible, is there a way to reset it? Any help at all would be appreciated. I don't think the system croaked overnight (while it was off), so I don't want to replace it now. There's got to be a way to determine what might be wrong... Thanks! -Michael --- [This E-mail scanned for viruses by Declude Virus]
On Monday 24 November 2003 06:33 am, Michael George wrote:
I have an ASUS A7V system running SuSE8.2. I had to power it down last night because of a power failure that the UPS couldn't endure.
This morning, when I turn it on, all the lights come on as normal and the fans start up, I hear the drive whir, but after about 1sec, it all stops and the power LED just blinks. I think this indicates sleep mode.
Michael, it could be almost anything! It could be something as simple as you didnt reset the UPS charging circuit! Check its circuit breaker then I would suspect power supply/fan first, then maybe a memory or video problem. Think of it like you do a car. If you turn a switch and nothing happens, you dont replace the muffler first, you check the battery.
Could the power supply be choking on the load and the system panics into sleep mode? The PS is a StarTech and little over a year old, so it should be okay.
It's not all that uncommon for things to go south on startup. The biggest load on the power supply is on starting all that stuff. If you happen to have a small ps, turnon could be to much for it. If you have a voltmeter check the line voltage. Make sure all the fans start up when you apply power.
Could apcupsd somehow have put the system into sleep mode and that's where it's going to go when it powers up?
It's possible. unplug the connection or go directly to the wall socket and see what happens.
Could the BIOS be hosed? If that's possible, is there a way to reset it? Any help at all would be appreciated. I don't think the system croaked overnight (while it was off), so I don't want to replace it now. There's got to be a way to determine what might be wrong...
It's not likely the BIOS. The troubleshooting sequence is a matter of personal experience/preference. Some will check the same things but in a different sequence. The challenge is to not introduce more problems than you start with. Just take it step by step. Looking for the obvious first. If nothing works I would start removing loads to see if that is a problem. BUT a word of caution, If you disconect a cable or remove a card, make sure you put it back correctly. Being careless in reconnecting cables can create even more troubles. All my machines run contnuously so when they die it's usually a fan or ps. And the ps is usually a bad fan, too. If you can't turn a fan with very little pressure it's probably bad. All you need to get a machine to start is a video, memory and the powersupply. Whenever I have this kind of problem I first check all the fans to see that they rotate freely. Then pull all the boards except the video, disconnect the drives, then turn it on. If the powr stays on, then I start adding stuff back beginning with the floppy. If it won't come up with just the vid, and mem, then I put in another supply. If that doesnt work then I substitute a new memory chip. If that fails, then I look next at the video card. Most often it's the ps or a fan. If a fan craps out it can take a cpu with it. Anyway, you should have a few things to look at now. Good luck, richard
Michael I accidentally deleted your response, please resend it directly to me. Look at this url for a hint on verifying your atx ps: http://www.sysopt.com/articles/troubleshoot/ Richard
Richard
Michael I accidentally deleted your response, please resend it directly to me.
Folks, *PLEASE* either keep the discussion on the list or completely off it! It doesn't do the list members any good if they only read one half of the discussion because the other part is done via private mail. Philipp
On Monday 24 November 2003 03:53 pm, Philipp Thomas wrote:
Folks, *PLEASE* either keep the discussion on the list or completely off it!
It doesn't do the list members any good if they only read one half of the discussion because the other part is done via private mail.
Philipp
C'mon Philipp, he responded to the list and I deleted my copy accidentally. Do you really think everyone needed to see the same thing again? Get real Richard
Richard
C'mon Philipp, he responded to the list and I deleted my copy accidentally. Do you really think everyone needed to see the same thing again?
At least I only see his original posting and no reply. Philipp
On Monday 24 November 2003 06:16 pm, Philipp Thomas wrote:
Richard
[Mon, 24 Nov 2003 17:36:01 -0600]: C'mon Philipp, he responded to the list and I deleted my copy accidentally. Do you really think everyone needed to see the same thing again?
At least I only see his original posting and no reply.
Philipp
Sorry if there has been a misunderstanding. His query came via the maillist and I use the reply to list for these things. When I was trying to edit his later answer I hit delete by mistake. Unfortunately Kmail doesnt send deletions to the trash so accidents can be recovered easily. Not wanting to create more traffic than necessary I requested he resend it directly to me. After looking at my sent mail box, I see that only one of my messages and one of his have NOT gone to the maillist. Ah, now I see what is going on! With Kmail, if you click Reply to List and the message did not come from a list, it sends it to the original sender. I guess that makes sense. Seems to me trying to send to a list when there is none in the message header should generate some kind of error. But it sure doesn't.. Like they say, no good deed goes unpunished! So that noone feels left out, here's his reply; Begin forwarded message:
From: Michael George
Date: November 24, 2003 10:48:50 AM EST To: ratcheson@earthlink.net Subject: Re: [SLE] After shutdown, system won't boot On Nov 24, 2003, at 10:21 AM, Richard wrote:
On Monday 24 November 2003 06:33 am, Michael George wrote:
I have an ASUS A7V system running SuSE8.2. I had to power it down last night because of a power failure that the UPS couldn't endure.
This morning, when I turn it on, all the lights come on as normal and the fans start up, I hear the drive whir, but after about 1sec, it all stops and the power LED just blinks. I think this indicates sleep mode.
Michael, it could be almost anything! It could be something as simple as you didnt reset the UPS charging circuit!
Check its circuit breaker then I would suspect power supply/fan first, then maybe a memory or video problem. Think of it like you do a car. If you turn a switch and nothing happens, you dont replace the muffler first, you check the battery.
Other things on the UPS are fine and I've moved the system to a direct wall socket. Needed to eliminate the UPS from the equasion...
Could the power supply be choking on the load and the system panics into sleep mode? The PS is a StarTech and little over a year old, so it should be okay.
It's not all that uncommon for things to go south on startup. The biggest load on the power supply is on starting all that stuff.
I know, I HATE powering down my linux boxes!
If you happen to have a small ps, turnon could be to much for it. If you have a voltmeter check the line voltage. Make sure all the fans start up when you apply power.
Don't have a voltmeter on hand, I'll have to borrow one. The PS is only about 1yr old, and a brand name, so I doubt that's it.
I've also unplugged everything from it down to the vid, kbd (even tried w/o that), speaker and 1 RAM DIMM...
Could apcupsd somehow have put the system into sleep mode and that's where it's going to go when it powers up?
It's possible. unplug the connection or go directly to the wall socket and see what happens. Done.
Could the BIOS be hosed? If that's possible, is there a way to reset it? Any help at all would be appreciated. I don't think the system croaked overnight (while it was off), so I don't want to replace it now. There's got to be a way to determine what might be wrong...
It's not likely the BIOS.
The troubleshooting sequence is a matter of personal experience/preference. Some will check the same things but in a different sequence. The challenge is to not introduce more problems than you start with.
Just take it step by step. Looking for the obvious first. If nothing works I would start removing loads to see if that is a problem. BUT a word of caution, If you disconect a cable or remove a card, make sure you put it back correctly. Being careless in reconnecting cables can create even more troubles.
Yeah, I've popped nearly everything out. The weird thing is that it starts all the fans for <1s and then the power LED blinks like it's in sleep mode.
All my machines run contnuously so when they die it's usually a fan or ps. And the ps is usually a bad fan, too. If you can't turn a fan with very little pressure it's probably bad.
Checked, all fans turn very easily. I've also has the infamous PS failures... That's usually what it is.
All you need to get a machine to start is a video, memory and the powersupply.
Whenever I have this kind of problem I first check all the fans to see that they rotate freely. Then pull all the boards except the video, disconnect the drives, then turn it on. If the powr stays on, then I start adding stuff back beginning with the floppy. If it won't come up with just the vid, and mem, then I put in another supply. If that doesnt work then I substitute a new memory chip. If that fails, then I look next at the video card. Most often it's the ps or a fan. If a fan craps out it can take a cpu with it.
Thanks for the help. All good advice! Unfortunately, after all of it, I'm still down... :( I'm trying to locate a friend w/ a 300W PS that I can drop in there to see if that might be the problem. Please, God, let it be the PS!
Anyway, you should have a few things to look at now. Good luck, richard
Thanks for you very detailed response!
-Michael Am I forgiven my transgressions against the List?? Richard
[This E-mail scanned for viruses by Declude Virus]
The Monday 2003-11-24 at 21:27 -0600, Richard wrote:
Yeah, I've popped nearly everything out. The weird thing is that it starts all the fans for <1s and then the power LED blinks like it's in sleep mode.
My guess is a power failure of some sort, or some self protection system firing. Examples: a short circuit or excessive power drain; voltage incorrect; the CPU fan not functioning, or otherwise the thermal protection of the CPU activating (for example, because the heat sink is loose or heat compound bad). Heating on the PSU itself (damaged component). That on the "bad" side. It could be as simple as the "sleep" contact been permanently on the sleep position.
Am I forgiven my transgressions against the List??
:-) -- Cheers, Carlos Robinson
The Monday 2003-11-24 at 17:36 -0600, Richard wrote:
C'mon Philipp, he responded to the list and I deleted my copy accidentally.
No, he did not. I can not see it, at least on this thread.
Do you really think everyone needed to see the same thing again?
You can retrieve an old mail from the list server easily... -- Cheers, Carlos Robinson
<SNIP> I've had a couple of 'always on' machines barf at startup because of dust build up on contacts and connectors. When the machine is on, the temperature inside keeps the dust and fluff dry, but when it gets switched off for a while moisture can be soaked up into the dust making it gungy and conductive. So, you might try cleaning inside the case and checking all power and data connections. Failing that, strip the machine down to it's minimum - no sound or network card, no CD or DVD, no secondary hard drives... and see what happens then. If it's OK then you can add components back one by one. HTH Dylan -- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg
participants (5)
-
Carlos E. R.
-
Dylan
-
Michael George
-
Philipp Thomas
-
Richard