[fsull]

Hi Y'all
Well, here goes...
I had win98 installed prior to my Redhat 8.0 install. I let it (8.0) go ahead and use up any free space (at least 10G over my primary and extended DOS partitions. 8.0 only wanted to use my number 5 partition.
I made 8.0 the default OS after startup, figuring I could always boot Win98 with a floppy if I got a 'non system error' message .
It installed ok.
I had the BIOS boot sequence set to 'CDROM, ...' for the install.
Maybe I didn't change it, but it shouldn't matter.
I configured the monitor in 8.0. Maybe that was stupid , not only because 8.0 gets the best display anyway, but I had recently installed a new driver to overcome a display problem that I was having after my Win98 install.
Ok, at that point I started the 8.0 Internet Connection Wizard, just to check if it would see a recent 56k modem install. I knew that I would most likely had to put in a 2nd modem that was Linux compatable. But I thought that it would simply kick back some kind of message. I was going to go out and look for some drivers.
Anyway, then it happened!
Total monitor shutdown, with the computer just running.
When I tried to do a boot after a shutdown, forget it...not even a beep.
I've since tried unplugging the CDROM and floppy to get a boot off the hard drive. It, the hard drive, runs on a power up, but that's it. I don't know BIOS runs, nor if the sytem is initializing.Here's the symptoms:
Power ON;
monitor goes into OFF mode;
no system boot;
CDROM drive LED flashes;
floppy drive LED stayS OFF;
hard disk is running.
Well, I would really appreciate some help on this. I'm using a friend's laptop till I solve it.
For any help, advice. suggestions, etc...thanks in advance.
I hope to return the favor to another newsgrouper sometime.
thx
-fsull

[codejockey]

Sounds like you are booting to Linux, with whatever problems that has. You mentioned that you were prepared to boot Windoze from a floppy -- have you tried that? My guess is that your X-windows configuration is not right, and that you have configured RedHat to present a GUI login. Since you boot Linux by default, you end up with a black screen. You will need to: (1) boot Windoze from a floppy, in order to determine that everything is OK in your Windoze partition(s) and (2) boot Linux without a GUI environment (possibly from your installation CD or a bootable floppy if you made one during installation). After that, you can start sorting things out.

Hope this helps -- any additional info appreciated.

[fsull]

Hi
thx for the reply.
well, yeah, i'm probably still booting to linux, since i set it as the default.
i tried booting from win98's floppy.
yeah, redhat's set for the gui login as opposed to a command line(i haven't yet taken a course in linux)
i have both boot floppies, but to no avail, i don't even get a 'beep'
well, once again, thx for the reply
i'm working from my friend's laptop that he so graciously let me borrow to help resolve my desktop's probs (inexpensively?)
if there's a way that i can do some kind of link, between his laptop and my desktop, that you might be aware of, i'd really appreciate hearing any ideas that you might have, or any other angles re: that matter
my thoughts are that if i can get into my desktop's BIOS, i could reconfigure the boot sequence, and it'll quit looking to the CDROM, and go to a:>, where the windoze boot floppy'll be waiting. maybe that's lame, but it's all i can come up with for now.
please get back with any ideas
once again, thx
-fsull

[codejockey]

Oh. Looks like I didn't read carefully enough (sorry). Have you tried using a different monitor and/or video card to see if your display re-appears? It is possible to damage hardware with incorrect configuration values (over-driving your monitor, for example), and this may be what happened (or not -- monitors die for all sorts of reasons). Anyway, if you can get video, then you can get to the BIOS to reconfigure it to include the floppy in the boot sequence (which I gather is not now in the boot sequence). From there, you should be able to boot either Windoze or Linux. Note that you will want to work from the command line in Linux, since X-windows will still be using the settings from your last configuration.

Hope this helps -- and feel free to post again with additional results.

[fsull]

yeah, how's it goin?
well, i think that i can say with certainty that the monitor's ok.
it, (the monitor) shuts down on startup on my desktop ( it won't boot), but, it's (the monitor) ok on a friend's laptop, (which i'm so graciously being allowed to use).
anyway, like i said, the monitor shuts down when i startup the desktop.
also, the desktop won't boot.
remember, the problem started after i installed a linux redhat 8.0
i reconfigured the monitor settings
then i did a 'internet connection wizard'
then it crashed
thx again for any feedback
-fsull

[codejockey]

So what happens if you try re-booting with the RedHat installation CD in the CDROM? Do you have video? Even if your RedHat installation were using incorrect monitor settings, the boot CD uses its own defaults, and so should not be affected. If you can boot the RedHat installation CD and get to a shell prompt, you should be able to modify your /etc/inittab file to specify a non-GUI default run-level, which would then allow you to boot into Linux (where you can sort out the problem). As a last resort, if you can get video booting the RedHat CD, you can always re-install (drastic last resort).

Keep that info coming! (8-))

[fsull]

yeah Codeguy:
How's it goin.
Well, I tried booting with the 8.0 CD...no cigar.
I tried wih the startup floppy I made during the install...no-go.
I disconnected the drives to attempt a 'brute force' boot...nothing.
The monitor maybe goes into off mode cuz its not gettin initialized.
I'd be happy to get as far as in the scenario you described.
But, it looks like I'll pull the board, give it a good looksie, salvage the parts.
What the heck, I'll probably be happier with a faster bus, right?
Hey, thanks again.
-fsull

[codejockey]

Sounds like either the video card (or onboard video) ate itself. Any spare video cards around? If so, you might install one and try the text mode solution to salvage things ... or just use this as a reason to upgrade (hey, sometimes life nudges us, and we have to respond! ).

Anyway, good luck -- and let us know what happens if you decide to attempt a salvage.

[fsull]

how's it goin
well, i went over to the soyo site;
and, I'm gonna go through their steps;
now, this is of course OS independent;
but, what the heck...
they do suggest some basic troubleshooting moves
like switching the JP5 jumper from pins 1&2 over to pins 2&3 for a little bit to 'clear' the CMOS...
I like it
I'll get back with any new developments
thx
-fsull

[fsull]

Codejockey:
Here's the route I'm goin as a last ditch effort:



Article Number S1067
I get No beep, no post and nothing on the screen when turning the
computer ON.


No beep, and no post means the CPU, and the board are not
transferring any signal codes. in this case follow these steps:
1.Please be sure CPU is seated properly.

2.Please be sure JP5 is set on Pins 1-2. System will not work if JP5
is set on 2-3.

3. Check jumper setting for CPU (if applicable) , try lower CPU
frequency if possible(e.g. set a 500MHz CPU to 450MHz to see the
results).

4.Try remove all unrelated hardware from the computer such as sound
card, modem, NIC, SCSI, and etc...., only leave CPU, CPU FAN (Be
sure CPU fan is connected to CPU Fan #1 if applicable), Chassis
speaker, and the ATX power plug and the power on/off switch(PWRBT).
For P4 users in addition to the mentioned diagnostics make sure that
your power supply is a P4 Certified, which contains both the main(20
Pin), and the 12V(4 Pin) connectors. also please make sure that both
connectors are properly connected and are generating the necessary
power to the board.

5. Turn system on. Check for beeps or any voices(on some boards
only). If it beeps then the CPU and the motherboard is
communicating, look up the beeps code in the Assistance Guides to
determine the problem. If no beep or voice then CPU may be defective
provided that the speaker is good. Try next step.

6.Try clear the CMOS via JP5 (make sure power is removed from the
board) , move jumper cap from pins 1-2 to pins 2-3 and let it sit
there for about 10 seconds, after that move the cap back to it's
original place(pins 1-2). then try turning the system ON again and
check for beep.

7.Pull the board out from the case and isolate it from the case. and
try steps1~6 again. If still no beeps then check make sure the power
is coming on and CPU fan is turning. If fans are not turning it
means power switch or the power supply could be faulty. Try replace
power supply first.

8. if the above mentioned steps fail, please try a different
processor. it is very much possible that your processor, is
defective, or damaged during installation.
Products


Comments / Feedback about this article


Have any feedback or comments about this article?


Copyright © 2001 - 2003 SOYO® Group, Inc. All right reserved.
Contact Us | Site Map | Disclaimer
I do know that it isn't the cpu, I' just have to get another mobo...eh, at least the bus'll be an upgrade!
Well, it's been real...I'll keep the posts up
thx
-fsull

[codejockey]

It could definitely be your motherboard (although the timing is a bit coincidental), especially since you get no beeps, etc. when you boot up (the infamous "will not POST" symptom). Worth checking out, although the Soyo guide is not terribly sophisticated.

Hope things work out well.