okay did all that, but makes no difference. I think it is possibly hardware related. It did appear after an update, but I think it’s coincidental. What is notable is the BIOS can also not be seen, regardless of which display monitor is used, external monitor or built-in one.
Yes… I thinks that’s a fair assessment. If the BIOS setup screen is not displayed that pretty much rules out grub as the cause… in fact it rules out all OS software, as the display at that point is pre bootloader.
Maybe worth asking on the Acer forums Home - Acer Community perhaps someone there has experienced the problem.
Hi
Reset the BIOS? In the interim let it boot to openSUSE, then if need to get to windows, use efibootmgr -n <nnn>, (where <nnn> is the number from efibootmgr pointing at the windows efi file) to use the boot next option.
I had a similar problem (screen wouldn’t wake until KDE started) when I bought a new cheap screen (Philips TV that is good enough for Skyrim). I looked everywhere online for a week or so and all I found was that some hdmi ports don’t wake the screen up, especially on older (or certain?) cards. And all this was on Windows forums.
I saw someone a couple of months ago on Endeavour’s forum have this happen after a motherboard UEFI update.
In my case, months after the new screen, I replaced an Nvidia 1050Ti with an AMD 270 and my cheap screen now wakes up immediately. And both cards were using HDMI (I haven’t checked the versions on either of them).
So, it could be a firmware update on the motherboard that caused it, or a ‘wrong’ o/p on your graphics card, or a ‘wrong’ input on your monitor/tv.
Sorry I can’t offer better help, this is all I could find.
I suspect my case is something like that… There were a lot of firmware updates around the time it stopped working. I can still boot into Windows if I just ‘guess’ where it is by pressing the down arrow to where I think it is and hitting enter, I never keep more than one older kernel version for openSUSE.
Yeah, I got used to it and simply always booted to my main OS 1st and rebooted (with grub now visible) to do anything else. And I could go into firmware setup with:
systemctl reboot --firmware-setup
But I didn’t find what ‘they’ had done to the firmware and/or the HDMI standards, I guess this problem will simply phase out over time.
well, I can live with this for now. I think I’ll just get a new machine.
Try GRUB_GFXMODE=“auto”.
It was auto already, when the fault first started to occur, then I changed that.