• SupportHardware

  • Problem with iiyaam G-Master, « no signal » after sleep or stop button

Problem with my new screen iiyama 31.5" G-Master GB 3271 QSUB1 Red Eagle monitor

The screen starts up well with the computer. (french below)
But if the screen goes to sleep or if the screen is stopped by its stop button, then afterwards it is impossible to find again the image, there is a loss of signal and the screen does not come back (no signal), it remains black,
And sometimes, in operation, rarely, there is briefly a loss of signal (black screen) and it comes back.

Computer, with :

  • SOLUS 4,3 fortitude
  • Asus Geforce GT 1030 LP 2 GB graphics card
  • connected via hdmi
  • Native Linux card driver
  • Screen was 165 Hz and 2560x1440
  • Motherboard: Gigabyte B450 AORUS PRO

Connecting the screen to other computers with other systems works normally:
A laptop with Win7
A tower computer with Win10 or Mint (older graphics card)
They all have Nvidia drivers
Linux Mint has Nvidia-driver-390 (version 390.144-Oubuntu 0.20.04.1 – Metapackage)

So the problem is not the screen.

What to do?
-Switch Solus to the Nvidia driver installable via DoFlicky? Is this risky? Reversible in case of problems?
-Change the graphics card?

  • other ideas?

Another remark, with my old Asus screen, I have on SOLUS 4,3 fortitude "tears" of image sometimes (parts of the screen image that shift) when scrolling, especially for long html pages.
Could this also be improved by installing the Nvidia driver?

Thanks a lot for helps.

Problème avec mon nouvel écran iiyama 31,5’’ G-Master GB 3271 QSUB1 Red Eagle

L’écran démarre bien avec l’ordinateur.
Mais si l’écran se met en veille ou si arrêt de l’écran par son bouton d’arrêt, alors après impossible de retrouver l’image, il y a perte de signal et l’écran ne revient pas (no signal), il reste noir,
Et parfois, en fonctionnement, rarement, il y a brièvement une perte de signal (écran noir) et ça revient.

Ordinateur, avec SOLUS 4,3 fortitude
carte graphique Asus Geforce GT 1030 LP 2 go
branchée en hdmi
Pilote de carte Linux natif
Ecran était en 165 Hz et 2560x1440
Carte mère : Gigabyte B450 AORUS PRO

En branchant l’écran sur d’autres ordinateurs avec d’autres systèmes ça marche normalement :
Un portable avec win7
Un ordinateur tour avec Win10 ou Mint (carte graphique plus ancienne)
Ils ont tous des pilotes Nvidia
Linux Mint a Nvidia-driver-390 (version 390.144-Oubuntu 0.20.04.1 – Metapaquet)

Donc le problème ne vient pas de l’écran.

Que faire ?
-Basculer Solus sur le pilote Nvidia installable via DoFlicky ? Est-ce que c’est risqué ? Réversible en cas de problème ?
-Changer de carte graphique ??

  • autres pistes ?

Autre remarque, avec mon ancien écran Asus, j’ai sur SOLUS 4,3 fortitude des « déchirures » d’image parfois (parties de l’image écran qui se décalent) au défilement, surtout pour des pages html longues.
Est-ce que là aussi ça pourrait s’améliorer avec l’installation du pilote Nvidia ?

Merci beaucoup pour les conseils.

5 days later

Actually I have install the nvidia Drivers with DoFlicky (instead of the linux "nouveau"), and restart the computer.
It works well, but ...same problem: when I shut down the iiyama screen it's impossible to find back the picture (no signal, screen remain black).
So I really don't know what to do.
If you have any helps thank you very much.

I would prefer not send back the screen to seller, because In don't know if another iiyama monitor would work better than this one with my computer and graphics card...
Maybe I could call the seller to see if they have already see this problem?

The seller of the screen couldn't help me because Linux is too unknown for him. Technical staff said that it may be a problem with the driver...

17 days later

Still have no solution.
Actually, I have to plug or unplug a second screen (with DVI, it works even is this screen is not plug on sector) to get back the signal on the Iiyama screen (after I shut down it)...
Not very "modern" ;-)

    David26 There should be a kernel update incoming some time in the near future, which might fix issues like yours. After that I think an xorg-server update will also happen soon.

    Until then, one last thing you could try is installing the nvidia-beta-driver packages, restart and see if those fix your problem.

    sudo eopkg it nvidia-beta-driver-common nvidia-beta-driver-current nvidia-beta-driver-32bit

      Just to be sure, you're running a fully updated system?

      You could try switching to a different branch of Nvidia drivers (and reboot after doing so for the drivers change to take effect) and see If the issue persists.

      There are 3 driver branches applicable to your card: the main one, the developer branch and the beta branch.


      To install the developer branch, you can execute these commands.

      If you're on the current (non-lts) kernel branch (it's the default one in Solus):

      sudo eopkg it -y nvidia-developer-driver-current nvidia-developer-driver-common nvidia-developer-driver-32bit

      or, If you're on the lts kernel:

      sudo eopkg it -y nvidia-developer-driver nvidia-developer-driver-common nvidia-developer-driver-32bit


      To install the beta branch (for the current kernel):
      sudo eopkg it -y nvidia-beta-driver-current nvidia-beta-driver-32bit nvidia-beta-driver-common

      or, to install the beta branch If you're on the lts kernel:

      sudo eopkg it -y nvidia-beta-driver nvidia-beta-driver-32bit nvidia-beta-driver-common


      To go back to the default driver branch (current kernel):
      sudo eopkg it -y nvidia-glx-driver-current nvidia-glx-driver-common nvidia-glx-driver-32bit

      or, if you're on the lts kernel:
      sudo eopkg it -y nvidia-glx-driver nvidia-glx-driver-common nvidia-glx-driver-32bit


      The -y parameter is for making the installation command remove conflicting packages (which will be the previous driver version, you don't want to have 2 branches installed at the same time).

      If you're not sure on which kernel branch you are, you can check it with the uname -a command.


      Also, just as a small tidbit, I've been told by repair technicians that it's healthier for monitors / TVs If you don't power them off completely (don't use the power off button), and instead let it go to standby mode (where the monitor is still on, but doesn't display anything, and wakes up upon turning on the PC).

      If you get in the habit of powering it off completely, you'll shorten the lifespan of the monitor's power supply by a few years, and you'll then have to repair the monitor (replace its power supply).

        Junglist Also, just as a small tidbit, I've been told by repair technicians that it's healthier for monitors / TVs If you don't power them off completely (don't use the power off button), and instead let it go to standby mode (where the monitor is still on, but doesn't display anything, and wakes up upon turning on the PC).

        If you get in the habit of powering it off completely, you'll shorten the lifespan of the monitor's power supply by a few years, and you'll then have to repair the monitor (replace its power supply).

        that's more than a 'small tidbit,' it's valuable info. thx.

          Junglist Thanks for helps.
          I'm running a fully updated system, I have install the last updates today.
          Thanks to advice "don't power them off completely (don't use the power off button)", because I didn't know that.

          Now, I had let the screen go alone to sleep this time, and when I come back to wake-up it (computer was not sleeping, only screen), the signal come back normally! :-) (a few weeks before it doesn't)
          Maybe because of the last updates, or because just before I tried to check the box "idek Iiyam" instead of auto, inside the Nvidia settings panel / Xvideo Settings?

          So it's ok now, just have to let the screen go to sleep alone.

          Maybe it can be marked "solve"?

            5 days later

            Now the signal for screen is coming back after sleep, nice.
            But I still have sometimes short black screens..., during one or two seconds, and after it's coming back.
            I do nothing special at these moments.
            Screen have problem, or it's driver problem?