On Thu, 2019-04-04 at 09:22 +0800, 積丹尼 Dan Jacobson wrote:
> > > > > > "BH" == Ben Hutchings <ben@decadent.org.uk> writes:
>
> BH> The installer normally uses a dumb framebuffer driver (probably efifb
> BH> on this system) that is built into the kernel. This is too low-
> BH> performance for a proper desktop.
>
> OK, the installer could first double check that the framebuffer driver
> it intends to write to the installation really will work, by telling the
> user:
>
> "5 seconds please, while we test your framebuffer ability."
>
> During which it could launch its proposed framebuffer,
> see if /proc/sys/.../{voltage or number of lit pixels, etc.} has
> suddenly dropped to zero, indicating a black screen, and then back out
> of that choice. Or simply ask the user "in a moment you will be asked if
> you saw a black screen".
[...]
There is generally no way to back out of changing the framebuffer
driver, other than to reboot. So we would have to implement some
ability for the installer to checkpoint its progress and then continue
after a reboot. I suspect that that would require a pretty major
architectural change and is unlikely to happen any time soon.
However it might be reasonable to add "nomodeset" to the command line
in GRUB's "recovery" boot menu items.
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.
Attachment:
signature.asc
Description: This is a digitally signed message part