03-07-2020, 12:00 AM
(03-02-2020, 08:41 AM)danielt Wrote: I haven't experimented with removing the maxcpus= workaround yet but I have updated to v2.0 in the latest (2020-03-02) release. See first post for other changes.
After running v2.0 with your 5.5-1 build for a while I can say that without maxcpus= workaround it takes between 10 and 15 seconds for me to see screen come to life after pressing power button. If the price of not having workarounds with nasty security implications is a mere 10 seconds of extra boot time I'm perfectly fine with paying it.