[Bug 224069] X, text console and suspend/resume fail

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 17 Jan 2025 01:49:27 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224069

--- Comment #14 from Stefan B. <sblachmann@gmail.com> ---
(In reply to Jason W. Bacon from comment #12)
I didn't follow much the FreeBSD development since mid-2022, as I went to a
sabbatical.
When back in mid-2023, I found that all graphics drivers except Intel and AMD
had been intentionally made dysfunctional.
The users' pressure was big enough to have at least the nv driver re-enabled,
and after being shown that these chipsets are dominating the server market, the
guy responsible finally re-instated the Matrox and aspeed drivers, which he
originally wanted to have deleted together with all drivers not belonging to
the Intel-AMD oligopoly.

The next stages announced were to replace xorg with Wayland, and removing the
SC console driver (which would make suspend/resume dysfunctional on Nvidia
systems).

That was enough for me.
I abandoned FreeBSD for Linux. I need reliable systems, for servers as well as
for workstations. And here electricity is very expensive, and has recently
become even more expensive, so S3 suspend is no real option.

There is no way around hibernate, which Linux is mastering since decades.
We do not know whether FreeBSD ever will implement hibernate, even though the
basic work already has been implemented by Kim Jung-Uk.

And now to your question:
The VESA module has been removed from the default kernel some times ago in
response to this PR, I think it was with 13.0.
Then, the question is, does the MacBook implement a full VESA feature set, or
do they leave out the state save/restore functions like Nvidia cards do? I
don't know.

I will now unsuscribe to the PR, as I am no longer part of the FreeBSD
community.

-- 
You are receiving this mail because:
You are the assignee for the bug.