New AB350 ITX - is it ryzen 2000 ready??

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   ... and the adventure nears its end....
Wardog... The issue isn't with video AFTER the OS boots up (I have tried Linux (Manjaro, Ubuntu/Linuxmint) and Win10).  The issue is at BIOS boot up.  No display with 'out of range' on the Asus and HP displays.  If, in the future I need to access the bios ... I don't get the splash so I can enter the bios.

I did some additional testing with my old LG monitor... Using a DVI-I to HDMI adapter on the monitor and the same HDMI cables I am using with the Asus and HP - the monitor and MoBo negotiate and I have a display that shows the Bios.  My intention is to Craigslist my old displays so this is not a good solution for me.

So... per the MFG, I returned the ASRock Fatal1ty AB350 mITX/AC and picked up the comparable Gigabyte unit.  It has an HDMI and Displayport outputs.

My findings.. Using the Asus display (my intended Primary):
	Connected via HDMI port - 'out of range'
	Connected via Displayport - SUCCESS
	Connected via Displayport using Passive DP to HDMI - 'out of range'
	Connected via Displayport using Active DP to HDMI - SUCCESS

It appears to be a negotiation issue over HDMI with the Ryzen 5 2400G and the B350 chipset (as this is the only configuration I have tested).  It does NOT appear to be MFG related.

This has been tested on the ASRock Fatal1ty AB350 mITX/AC, ASRock AB350M Pro4 and the Gigabyte GA-AB350N Gaming Wifi  with the AMD Ryzen 5 2400G.  It appears the negotiation over HDMI for the signal is not being accomplished properly (if at all) on newer monitors with HDMI inputs.

I hope this helps...

I am a HUGE ASRock fan, however for my mITX build I have to go with the competition due to my equipment (monitors) being used.

MD

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
hitekagpilot Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 Mar 2018 Location: DENVER Status: Offline Points: 3	Post Options Post Reply Quote hitekagpilot Report Post Thanks(0) Quote Reply Posted: 09 Mar 2018 at 11:30pm
	... and the adventure nears its end.... Wardog... The issue isn't with video AFTER the OS boots up (I have tried Linux (Manjaro, Ubuntu/Linuxmint) and Win10). The issue is at BIOS boot up. No display with 'out of range' on the Asus and HP displays. If, in the future I need to access the bios ... I don't get the splash so I can enter the bios. I did some additional testing with my old LG monitor... Using a DVI-I to HDMI adapter on the monitor and the same HDMI cables I am using with the Asus and HP - the monitor and MoBo negotiate and I have a display that shows the Bios. My intention is to Craigslist my old displays so this is not a good solution for me. So... per the MFG, I returned the ASRock Fatal1ty AB350 mITX/AC and picked up the comparable Gigabyte unit. It has an HDMI and Displayport outputs. My findings.. Using the Asus display (my intended Primary): Connected via HDMI port - 'out of range' Connected via Displayport - SUCCESS Connected via Displayport using Passive DP to HDMI - 'out of range' Connected via Displayport using Active DP to HDMI - SUCCESS It appears to be a negotiation issue over HDMI with the Ryzen 5 2400G and the B350 chipset (as this is the only configuration I have tested). It does NOT appear to be MFG related. This has been tested on the ASRock Fatal1ty AB350 mITX/AC, ASRock AB350M Pro4 and the Gigabyte GA-AB350N Gaming Wifi with the AMD Ryzen 5 2400G. It appears the negotiation over HDMI for the signal is not being accomplished properly (if at all) on newer monitors with HDMI inputs. I hope this helps... I am a HUGE ASRock fan, however for my mITX build I have to go with the competition due to my equipment (monitors) being used. MD

Brandon Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Apr 2017 Status: Offline Points: 22	Post Options Post Reply Quote Brandon Report Post Thanks(0) Quote Reply Posted: 09 Mar 2018 at 11:36pm
	The AB350 FATALITY K4 with 4.70 bios and a 2400G has the cstates stuck on. No way to set a static CPU speed.

Thenightstalker Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 03 Mar 2018 Status: Offline Points: 57	Post Options Post Reply Quote Thenightstalker Report Post Thanks(0) Quote Reply Posted: 12 Mar 2018 at 8:38pm
	Interesting ... I'm curently using my old Philips 47" LCD TV over HDMI and there's no problem. Or let's say it works now after some confusion and trial and error. After building the System (and it wasn't my first one) I double checked everything and fired it up. The RGB leds in my case started to pulse red (which was just coincidencial as I noticed later) and the fans spin up and then nothing else happened. TV says no signal .... I tried about 5-10 times, remounted the RAM modules becaus I knew from earlier builds they sometimes have bad contact because you can't or don't dare to push them in that hard :-) but nothing. I also hook up a PC speaker just to hear any error codes but it kept silent. I clear CMOS and did all I could think of, which wasn't much because there's literally nothin in the case that could make troubles lol. I can't tell what was wrong but after several tries with pushing the reset button and power button and reconnecting power plug it came to live. I heard the CPU fan increasing rpm and thought hm something changed so I waited and after a few seconds I had a post and it went to uefi! Which was intended because I had no drives installed yet. However, your report concerns me a little bit, what if I connect a newer monitor ... I'll soon try it with my LG OLED TV (2017 model, HDMI 2.0) because the system is meant to be a HTPC / Console like device. Hopefully it will run there as intended otherwise ... hm dunno. But this issue sounds like it should be fixable via BIOS update, doesn't it?