Question No signal on Viewsonic

[rh71]

Just bought 2 of the 27" Viewsonic for the kids (at $225), and having a problem with "no signal" (on both monitors/different cables) when connecting via HDMI to a new PC build with an RX 580 card. The CPU is an i5-9400F (no native graphics) if that matters. RX 580 PC hooked into an old monitor - works fine through boot. The Viewsonic monitor also works fine when connecting to another PC (same cables) with a GTX 1650S card.

What's strange is that the Viewsonic works fine on the RX 580 PC if it's already booted into Windows. If I reboot, then again no signal through BIOS/bootup. I then hook it up to an old monitor, and the signal is fine through the whole restart. Then hot-swap HDMI to Viewsonic monitor and it's fine since it's already in Windows. Already loaded latest Radeon drivers.

Don't have a displayport cable to test with. Any ideas?

 

[VirtualLarry]

This is using an HDMI cable to connect? And the Viewsonic works when you hot-swap from your other monitor, after it has booted, but not if booting from the Viewsonic?

Sounds like something is FUBAR with the detection of the monitor when booting, so it doesn't turn that display output on.

1) I know that this sounds dumb, but you ARE plugging the HDMI cable into the CARD, right, and not the MOBO I/O panel?

2) Check UEFI/CSM settings, and Secure Boot. Possibly you need to disable Secure Boot, or play with CSM settings, sometimes the video BIOS on the card, or UEFI GOP, doesn't get executed at boot due to Secure Boot or CSM/UEFI boot settings.

Some RX 580 cards, as opposed to most NVidia cards, have a UEFI-only BIOS, whereas most NVidia cards like the GTX 1650 have a Hybrid BIOS that works at boot with either Legacy or UEFI.

Try disabling CSM boot, and disable Secure Boot.

Edit: Another thing to try, is HDMI Link Assurance (Enabled) in Radeon Adrenaline 2020 drivers, under Display.

It sounds also like maybe this monitor is "quirky" with it's HDMI detection, and maybe needs a driver-level workaround / patch to support it. I've had monitors (new models) in the past that had similar issues (no HDMI audio detection, when booted, but when plugged/unplugged/powered-off/powered-on it would detect, once booted). Some displays are just "quirky". Though I didn't have any problem with the primary display showing up.

Are these a new model display, that they might not have added workaround to the drivers to support it yet? It sometimes takes six months, and it helps if you report it to AMD's driver team too, although if you don't see POST on it either, then it's probably a CSM/UEFI/Secure Boot thing.

 

[rh71]

Thanks for that write-up... I went to attack the problem just now and just trying a simple reboot, it came back no problem (wasn't the case yesterday). Then I did a full shutdown and it also came back with no problem. I didn't do anything prior other than update Windows to the latest everything. Just gotta love intermittent / random issues like this. I'll keep the above in mind regardless - thx.

 

[cyberthereaper]

@rh71 hello.I think I know what your problem is. If an operating system is installed on your computer, you cannot see the windows opening screen, but after the windows are fully opened, the monitor suddenly opens and shows the desktop. In addition, when you want to enter the bios section, you will see a "no signal" warning and the screen will never open. The solution to this is related to your motherboard's bios settings. now follow the steps below.

1 : ) connect the computer case to a television with hdmi connection.

2 : ) Press the delete button repeatedly to enter the bios section.

3 : ) Asus motherboards have an option called "Fastboot: Disabled" in the bios section. Change this option to ultrafast.also there is an option called "UEFI Setup Prompt Timeout" on asus motherboards. probably 1 second is set as default. Replace this value with 10 or a longer number.

4 : ) save these settings and exit.

5 : ) Remove the computer case that we connected to the TV and connect it to the monitor.

6 : ) Start your computer and press the delete button repeatedly to enter the bios screen.

As a result of the above actions, you will see that the monitor has work. thanks ; )

 

[VirtualLarry]

Asus motherboards have an option called "Fastboot: Disabled" in the bios section. Change this option to ultrafast.

Pending some research, I would actually advise against that. My understanding is setting Fastboot to Enabled, or UltraFast, actually locks-out the boot hotkeys (Boot Menu, BIOS access, etc.), which I think wouldn't be desirable. But I'm not so sure about the UEFI setup timeout, maybe that extends the boot-time hotkey availability after UltraFast shortens it?

Interesting technique, non-the-less.

I'm guessing, the idea is to get the BIOS to initialize quickly, but then give the HDMI time to sync, and the monitor time to power-on?

I've noticed, at times, ESPECIALLY with Gigabyte AM4 mobos, but also others, that sometimes, when you reboot your rig, and then hit Del to enter BIOS, you're left with a blank monitor screen, like there's basically "no signal". What I've found is, that you actually ARE sitting at the BIOS screen, but the HDMI has not synced after the reboot, in BIOS.

IOW, the Windows-level drivers, have "HDMI Link Assurance", which will retry multiple times to make sure that the HDMI is synced, when changing display modes, but the BIOS does not, and it's kind of hit-or-miss with some displays, whether or not the BIOS ever syncs with the display card or mobo. Turning the display off and on again, or changing the input selector, often gets it to re-sync, at least for me.

 

[Stuka87]

Pending some research, I would actually advise against that. My understanding is setting Fastboot to Enabled, or UltraFast, actually locks-out the boot hotkeys (Boot Menu, BIOS access, etc.), which I think wouldn't be desirable. But I'm not so sure about the UEFI setup timeout, maybe that extends the boot-time hotkey availability after UltraFast shortens it?

Interesting technique, non-the-less.

I'm guessing, the idea is to get the BIOS to initialize quickly, but then give the HDMI time to sync, and the monitor time to power-on?

I've noticed, at times, ESPECIALLY with Gigabyte AM4 mobos, but also others, that sometimes, when you reboot your rig, and then hit Del to enter BIOS, you're left with a blank monitor screen, like there's basically "no signal". What I've found is, that you actually ARE sitting at the BIOS screen, but the HDMI has not synced after the reboot, in BIOS.

IOW, the Windows-level drivers, have "HDMI Link Assurance", which will retry multiple times to make sure that the HDMI is synced, when changing display modes, but the BIOS does not, and it's kind of hit-or-miss with some displays, whether or not the BIOS ever syncs with the display card or mobo. Turning the display off and on again, or changing the input selector, often gets it to re-sync, at least for me.

Any motherboard that I have used that supports FastBoot also has a little utility that you can run to reboot into EFI. The only time this would not work is if there was an issue that preventing logging in to windows, or if the user only had linux installed I suppose.