Incorrect display of information when loading the computer?

Question

Iron

There is a system: mother - H55M-D2H (2 slots for RAM), I3 560 (for socket 1156), and GTX1050 Expedition OC video card.
Two monitors, HP Compaq LA2405wq and ASUS VW220D.
Asus monitor only has 1 VGA connector. It connects to the video card via an active adapter to HDMI. It is impossible to connect a conventional adapter from VGA to DVI, p.ch. The video card has a DVI-D connector.
An HP monitor is connected via Displayport.
Now the problem itself:
When the system starts, all information is displayed on the ASUS screen in an incorrect way. Those. 1 system message (displaying the name of the motherboard, how much RAM is in the system and other information) the monitor does not have time to display (displays the message No signal. Then, according to the canon, in the upper left corner, the message Loading operating system ... familiar to everyone is displayed as always. Further, when it comes to GRUB (ubuntu 17 and w7 are installed), the screen becomes the background color of GRUB (normal color fill). And there are no fields for choosing the OS, the system does not respond to any keys. You have to call ctrl + alt + for help del, holding them for 5-10 seconds (just the time it takes for the auto-selection of the OS. By default, ubuntu) After rebooting, GRUB displays all the OCs, and allows you to already select the one you need. (But strangely, the whole picture, as it were, increased by 2-3 times, compared to the original). And after that, the OS boots up and everything works fine and without problems. (Ps sometimes, when booting GRUB looks like thishttps://photos.app.goo.gl/PFQe2m1KGFrv20Wr2 ).
If you connect an HP monitor via VGA, through the same converter, then nothing is displayed on the HP monitor, absolutely nothing. Until the OS boots up. The OS booted up and the image appeared.
As a result, the whole problem is in the converter.
The question is: how to make the system output information when booting to an HP monitor, via a display port cable, and not to an ASUS monitor via a converter and VGA?
Previously, there was a gt240 video card, there were no such problems. HP was connected via simple DVI, and ASUS directly via VGA. (the first time, when I installed the 2nd monitor, the image again went to ASUS. But after 2-3 days, it automatically switched to HP. I didn’t touch any settings. It’s on its own :) )
How to be, comrades?
Pss first tried to connect an hp monitor, boot with it (and yes, everything was displayed well on it. Except for GRUB, it seemed to be increased by 2-3 times compared to what it should be). Then I connected the 2nd monitor and check. Info went to the Asus monitor again...

Answer 1

This problem is most likely related to the EDID of the monitor, especially through the adapter, the video system cannot determine the monitor parameters correctly.
Solution, edit GRUB menu.lst
I had such a problem on Android x86, which I put on a laptop without a screen (I decided to make a TV box), the picture was output only to the internal LVDS port, and I needed HDMI. In general, editing these files helped me, android x86 is similar
to Linux, so you will have all the same files brackets optional parts:
: Port, for example DVI-I-1, HDMI-1, TV-1, VGA-1, SVIDEO-1... The names of the ports available on your computer can be found in /sys/class/drm/
x: Resolution
-: Color depth, in our case always 16
@: Refresh rate
Next, one of the port status options is indicated:
e - port enabled
d - port disabled
D - digital port enabled (DVI-I, HDMI)
Example, output setting by HDMI: video=HDMI-1:[email protected]Switching image output to external monitor: video=LVDS-1:d video=VGA-1:1920x1080(you can make a separate item in menu.lst)
If the image needs to be displayed on several ports at once, then video is specified once for each port. It is useful to disable unused ports: video=TV-1:d
_______________________________________________________________________________
snippet

{
    set_property debug.drm.mode.force [email protected]
}

function do_init()
in system/etc/init.sh solves the screen resolution issue. Before breaking everything in the init.sh file, you can check this: alt + f1, write stop, then setprop debug.drm.mode.force [email protected] (custom values), after - start. Then be sure to make a copy of the file! Find the function do_init() line, add what is missing above, specifying your resolution before the dog and frequency after