No Signal Input on monitor

Heinz 57 / Build
January 29, 2009 at 19:12:13
Specs: none installed, Intel/256x2 ddr
I am attempting to build a PC from scratch, parts from other computers. I got and old case from an Emachines c2160, put in a motherboard, which I am sure is OK,installed a psu,same. I connected all the wires from the PS to the motherboard, and HDD,floppy, and dvd. When I hook up a monitor, that I know is good, I get a message on my screen saying "no signal input. I am fairly new to building so please be gentle :)

See More: No Signal Input on monitor

Report •


#1
January 29, 2009 at 19:37:49
That means that it's not even going through the POST. Did you buy a compatible processor with the motherboard or did you try to use the original? The same question goes for the memory.

Report •

#2
January 30, 2009 at 16:25:17
Thanks for the response.
The motherboard came with the processor, and there was 1 stick of DDR400 256MB RAM installed, so I put in another of the same.

Report •

#3
January 30, 2009 at 16:44:34
Are you sure that the memory isn't mismatched? Try one stick by itself.

Report •

Related Solutions

#4
January 30, 2009 at 17:24:36
When I read your reply, I thought that you might think there was a connection between the RAM and the no signal, so I removed both sticks and tried them one at a time. Slot closest to the CPU right ?
Still no Joy

Report •

#5
January 30, 2009 at 17:47:04
Let's go back to the memory for a minute. You can't use any of the memory from the old motherboard unless is the exact same mobo as the new one.

Report •

#6
January 30, 2009 at 17:55:12
Back to basics. To get a successful POST all you need is PSU, Motherboard, CPU with Heatsink/fan, ram, keyboard and graphics.

Disconnect any drives. What model motherboard?
Do you get any POST beep when you try to startup? Leave out the ram. Do you get a bios beep error when you try to startup?

A failed CPU will mean no beeps at all and you would get the "No Signal" error. If the graphics card (onboard) has failed you might get the "No Signal" error but still get at least a bios beep error

Goin' Fishin' (Some day)


Report •

#7
January 30, 2009 at 19:08:04
Hi quapo, sorry for the mis-communication. There is no new motherboard, the one that I installed already had the CPU, and the RAM in it.

Hi Richard59,
Disconnecting the power to the drives will do?
I am not sure on the model of the motherboard, cannot see any make or model. I will pull it out to see.

I already have it in the case.
Hindsight 20/20, I should have hooked it all up before putting in the case. DOH

As for the beeps, I haven't connected the front speaker, or the power on yet. The old case had a connector to the mother board that was a one piece connector, 18 pins.
The case that I have now has 3 seperate leads, green white, red white, and black white. I don't know where they go on the 18 pins of the MB, so i used the old 18 pin wires from the old case and am using it to power up the comp.


Report •

#8
January 30, 2009 at 20:15:34
Disconnecting the power and data cables to the drives will prove that they are not the cause of the boot failure. I have had systems where a faulty harddrive or optic drive completely prevented bootup. Similarly I have seen faulty PCI cards such as NIC or modem or sound card also prevent bootup. Without any kind of peizo or speaker connected you cannot determine whether the board is even getting to POST.
Since this is being built from used components how do you know the CPU is working?

Recently I took off a heatsink/fan assembly to clean it & renew the thermal compound. When I re-assembled the thing it would not boot. The CPU died and only by testing a known good CPU was I able to confirm that as the problem rather than motherboard or some other component.

As to the front wiring connectors, you should identify the motherboard and download the appropriate manual. Did this motherboard originally come from the case you are using to power it up? If not there is no guarantee the 18 pin connector is configured correctly for that board.

Goin' Fishin' (Some day)


Report •

#9
January 31, 2009 at 13:40:49
Richard59,
Do you remember the thrill that you got when you to build you first computer, AND IT WORKED. You just gave that to me, Thank you !!!

So, I unhooked everything like you suggested.
Powered up and nothing :(
Took off the fan to the cpu, popped out the cpu to see if I had the same one in my computer I am on now, wasn't the same.
Reinstalled above, powered up again and it worked. I have the following message on my monitor.

256 MB
512-Chassis not detected.
162-System Options Not Set.
Your system configuration has been changed since your last boot (addition of a hard drive, etc), or a loss of power to the Real Time Clock has occured. The Real Time clock will lose power if the onboard battery is not functioning correctly. Pressing F1 will record the new configuration. If this message persists, you may need to replace the onboard battery.

Initializing Intel(R) Boot Agent Version 4.1.08 PXE 2.1 Build 083 (WfM 2.0), RPL V2.74

Restoring the default configuration. The system will restart when complete.

The following configurayion options were automatically updated:

Memory: 256MB

CMOS checksum invalid, default values loaded.

Compaq Evo D510 CMT
F1 Save Changes "highlighted in blue"

WHEW, I really have to buy a camera, HAAAA !!

I am tempted to hit F1, and then hook up HHDD, etc one at a time but we have come this far...


Report •

#10
January 31, 2009 at 15:59:34
Well there's one mystery partly solved. The motherboard came out of a compaq system.
Go ahead and connect your peripherals. And yes I do remember the thrill I got when my first build fired up.

Goin' Fishin' (Some day)


Report •

#11
February 1, 2009 at 10:34:39
OK, I've connected all the peripherals, and now get this.

256 MB
512-Chassis not detected.
162-System Options Not Set.
Your system configuration has been changed since your last boot (addition of a hard drive, etc), or a loss of power to the Real Time Clock has occured. The Real Time clock will lose power if the onboard battery is not functioning correctly. Pressing F1 will record the new configuration. If this message persists, you may need to replace the onboard battery.

The following configuration options were automatically updated:

Memory: 256MB
Diskette Drive:A:
CD-ROM: CD-RW IDE 4816
CD-ROM: DVD-ROM BDV 316C
Disk 80.0 GB Samsung SP0802NP

If you are running Unix, you need to configure your system using the Computer Setup Utility (F10)
CMOS checksum invalid, default values loaded.

F1 Save Changes.


I have gone past this point but, wanted you to see the messages as the come up.

Thanks


Report •

#12
February 1, 2009 at 10:44:58
You need to enter the BIOS (setup) screens and reset the date, time and many other items, including the boot order.

Sounds like the CMOS battery has died. That is the flat silver coin shaped battery on the motherboard. You should be able to use the battery from the other board. If you leave the power cord connected and just shut down the commputer from the start button you don't need to immediately relace that battery. It only store BIOS settings when all power is interrupted. ATX motherboards always have power, if the computer is plugged into a hot outlet.


Report •

#13
February 1, 2009 at 12:24:54
Hi OtherHill, went into BIOS setup this morning, set, date, time etc. Checked boot sequence, cd 1st to boot. Save and exit. If I try to boot again I get a screen that shows a flashing cursor on the top, right hand side of the screen. Seems im in some BIOS loop and every time I have to power off the PC I have to start again.
I think my best move is to get a new battery first. To at least get rid of that problem and move on from there.

Report •

#14
February 1, 2009 at 12:57:24
That is OtheHill

Are you remembering to SAVE upon exit. Usually F10. As I explained, if the computer stays plugged in and you aren't using a wall switch or power strip the values will hold even with a dead battery.

As far as the NO SIGNAL goes, are you connecting to onboard video or and add in card? If there is an add in video card the onboard is automatically disabled so, don't try connecting to it. If there are TWO ports then try the other one.


Report •


Ask Question