Jump to content

New build help? Motherboard not connecting to peripherals...

Troup

So, started a new build and just powered on. Unfortunately, the monitor (connected to the GPU), keyboard, and mouse do not seem to be connecting. 

Everything is connected and has power, as the RGB would indicate. 

 

Would anyone have an idea of what I might be missing? 

 

I've tried swapping out the GPU and ensured all cables are in place, so I fear the problem might be the motherboard. 

 

Trying to give as a gift for Christmas,  so I'm scrambling! Thank you for any help.

 

For reference,  the build:

https://pcpartpicker.com/list/GVxYXv

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

It seems to be a boot issue, based on the orange LED on the motherboard...

Link to comment
Share on other sites

Link to post
Share on other sites

Try booting with one stick of memory in all the slots. Just to ensure the memory and slots are all working.

Have you also tried letting it try booting for a couple minutes? I have heard people in the past say sometimes Ryzen systems need to a bit of time to boot.

 

Are there are debug LEDs on the board turned on? Those are in the top right of the board.

Please also ensure the monitor you're using is on the right input.

"We're all in this together, might as well be friends" Tom, Toonami.

 

mini eLiXiVy: my open source 65% mechanical PCB, a build log, PCB anatomy and discussing open source licenses: https://linustechtips.com/topic/1366493-elixivy-a-65-mechanical-keyboard-build-log-pcb-anatomy-and-how-i-open-sourced-this-project/

 

mini_cardboard: a 4% keyboard build log and how keyboards workhttps://linustechtips.com/topic/1328547-mini_cardboard-a-4-keyboard-build-log-and-how-keyboards-work/

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Troup said:

It seems to be a boot issue, based on the orange LED on the motherboard...

Try booting the system with no drives installed (M.2, SATA, USB or otherwise) on top of what I suggested above.

"We're all in this together, might as well be friends" Tom, Toonami.

 

mini eLiXiVy: my open source 65% mechanical PCB, a build log, PCB anatomy and discussing open source licenses: https://linustechtips.com/topic/1366493-elixivy-a-65-mechanical-keyboard-build-log-pcb-anatomy-and-how-i-open-sourced-this-project/

 

mini_cardboard: a 4% keyboard build log and how keyboards workhttps://linustechtips.com/topic/1328547-mini_cardboard-a-4-keyboard-build-log-and-how-keyboards-work/

Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, minibois said:

Try booting with one stick of memory in all the slots. Just to ensure the memory and slots are all working.

Have you also tried letting it try booting for a couple minutes? I have heard people in the past say sometimes Ryzen systems need to a bit of time to boot.

 

Are there are debug LEDs on the board turned on? Those are in the top right of the board.

Please also ensure the monitor you're using is on the right input.

Wow. That was easy! Just one RAM stick fixed it- I am in BIOS. Thank you for your promptness and thoroughness! 

 

Now to configure... 

Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, Troup said:

Wow. That was easy! Just one RAM stick fixed it- I am in BIOS. Thank you for your promptness and thoroughness! 

 

Now to configure... 

Now to check though.. Is it a RAM or board issue :o 

Easiest way to check that is with these two tests:

Test 1: place your known working stick of RAM in the possibly dead slot. Does it work?

Test 2: place the possibly dead stick of RAM in the known working slot: Does it work?

 

If test 1 fails: the slot on the board is dead.

If test 2 fails: the stick of RAM is dead

If both fail: possibly dead RAM and slot I guess

 

If neither fail:

tenor.gif?itemid=9239559

/s

That shouldn't happen I think :P 

"We're all in this together, might as well be friends" Tom, Toonami.

 

mini eLiXiVy: my open source 65% mechanical PCB, a build log, PCB anatomy and discussing open source licenses: https://linustechtips.com/topic/1366493-elixivy-a-65-mechanical-keyboard-build-log-pcb-anatomy-and-how-i-open-sourced-this-project/

 

mini_cardboard: a 4% keyboard build log and how keyboards workhttps://linustechtips.com/topic/1328547-mini_cardboard-a-4-keyboard-build-log-and-how-keyboards-work/

Link to comment
Share on other sites

Link to post
Share on other sites

2 hours ago, minibois said:

Now to check though.. Is it a RAM or board issue :o 

Easiest way to check that is with these two tests:

Test 1: place your known working stick of RAM in the possibly dead slot. Does it work?

Test 2: place the possibly dead stick of RAM in the known working slot: Does it work?

 

If test 1 fails: the slot on the board is dead.

If test 2 fails: the stick of RAM is dead

If both fail: possibly dead RAM and slot I guess

 

If neither fail:

tenor.gif?itemid=9239559

/s

That shouldn't happen I think :P 

Like magic, it worked just plugging the RAM back in! 

 

Only thing left is to figure out how to work all the RGB...

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×