Hi.
FreeBSD home 14.1-BETA2 FreeBSD 14.1-BETA2 releng/14.1-n267613-e3e57ae30ca3 MYGENERIC amd64
xfce
sddm
Brief description of the problem:
After entering S3 mode for the first time (zzz command) and exiting it, problems with the graphics subsystem begin.
When is the problem not reproducible?
- when the system booted after a reboot;
- after restarting Xorg, for example "service sddm restart";
- after logging out and re-entering by entering your login/password;
When does the problem reproduce?
- after the first exit from ACPI S3 mode.
First detection of the problem:
Spring 2023, FreeBSD 13.
Detailed description of the problem:
Video card: Intel HD Graphics 4600.
I have 2 monitors connected via HDMI to the integrated ports on the motherboard.
Monitor1 is an Epson projector, which is always turned off, but is connected via an HDMI cable and is identified. It turns on rarely, for 1-2 hours and then turns off.
Monitor2 is Eizo's main work monitor.
When I work I use the displays configuration:
Monitor1: OFF
Monitor2: ON (Primary display)
When I turn on the projector, the configuration is different:
Monitor1: ON
Monitor2: ON (Primary display)
Mirror
Instead of turning off the computer, I use S3 mode.
After entering S3 mode for the first time (zzz command) and exiting it, problems with the graphics subsystem begin.
Repeated logins and logouts from S3 no longer change anything, the problem remains the same.
When I turn on the projector, my main monitor2 turns black. At the same time, you can use the keyboard and mouse, enter commands, and navigate between applications. You can even see how the shape of the cursor changes when the arrow turns into a vertical stick for entering text, if you point it at the text field (in the blind, on a black screen).
To get rid of this black screen on the main monitor2, I switch to any of the eight TTY consoles, via CTRL+ALT+F1 to F8, and then back CTRL+ALT+F9. After this, you can continue to work on monitor2.
On monitor1 (projector) everything is the same as on monitor2.
While working, I noticed that the output of the vainfo command changed before and after exiting S3.
Output of vainfo before S3 mode:
Vainfo output after S3 mode:
Perhaps this is some useful information.
I did not make any settings in xorg.conf; the xorg.conf file does not exist.
Has anyone encountered this, is it possible to solve this problem?
Or is this a known problem for a long time and it is not being solved?
FreeBSD home 14.1-BETA2 FreeBSD 14.1-BETA2 releng/14.1-n267613-e3e57ae30ca3 MYGENERIC amd64
xfce
sddm
Brief description of the problem:
After entering S3 mode for the first time (zzz command) and exiting it, problems with the graphics subsystem begin.
When is the problem not reproducible?
- when the system booted after a reboot;
- after restarting Xorg, for example "service sddm restart";
- after logging out and re-entering by entering your login/password;
When does the problem reproduce?
- after the first exit from ACPI S3 mode.
First detection of the problem:
Spring 2023, FreeBSD 13.
Detailed description of the problem:
Video card: Intel HD Graphics 4600.
I have 2 monitors connected via HDMI to the integrated ports on the motherboard.
Monitor1 is an Epson projector, which is always turned off, but is connected via an HDMI cable and is identified. It turns on rarely, for 1-2 hours and then turns off.
Monitor2 is Eizo's main work monitor.
When I work I use the displays configuration:
Monitor1: OFF
Monitor2: ON (Primary display)
When I turn on the projector, the configuration is different:
Monitor1: ON
Monitor2: ON (Primary display)
Mirror
Instead of turning off the computer, I use S3 mode.
After entering S3 mode for the first time (zzz command) and exiting it, problems with the graphics subsystem begin.
Repeated logins and logouts from S3 no longer change anything, the problem remains the same.
When I turn on the projector, my main monitor2 turns black. At the same time, you can use the keyboard and mouse, enter commands, and navigate between applications. You can even see how the shape of the cursor changes when the arrow turns into a vertical stick for entering text, if you point it at the text field (in the blind, on a black screen).
To get rid of this black screen on the main monitor2, I switch to any of the eight TTY consoles, via CTRL+ALT+F1 to F8, and then back CTRL+ALT+F9. After this, you can continue to work on monitor2.
On monitor1 (projector) everything is the same as on monitor2.
While working, I noticed that the output of the vainfo command changed before and after exiting S3.
Output of vainfo before S3 mode:
Code:
# vainfo
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 2.4.1
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLDVainfo output after S3 mode:
Code:
# vainfo
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.22.0
libva error: vaGetDriverNames() failed with unknown libva error
vaInitialize failed with error code -1 (unknown libva error),exitPerhaps this is some useful information.
I did not make any settings in xorg.conf; the xorg.conf file does not exist.
Has anyone encountered this, is it possible to solve this problem?
Or is this a known problem for a long time and it is not being solved?
Last edited: