On Sun, Nov 21, 2021 at 04:46:50PM +0100, Felix Zielcke wrote: > Am Sonntag, dem 21.11.2021 um 10:15 -0500 schrieb Antoine Beaupré: > > i would suggest not blocking on the grub deployment. you can probably > > just deploy whatever architecture the package was built from, in any > > case.
> I just added now the GRUB 2 integration and a README.Debian. The integration isn't triggered on the package's install, but it is picked up the next time something else bumps grub. > You can now review it. And I think it would be better to first upload > this to experimental? So a bit more experienced Debian users can test > it first. That sounds like a good idea. And, pcmemtest works for me on new machines, while memtest86* either instantly reboots or locks up. > Note that I mention in README.Debian one nasty bug/issue: > > In EFI mode the keyboard only works if you have the CSM aka legacy boot > also enabled: > > https://github.com/martinwhitaker/pcmemtest/issues/2 This is a nasty one. It seems most new machines lack CSM; no one wants to support and validate 16-bit stuff -- it's effectively expending resources to have two BIOSes instead of one, and the 8086 one has no practical usage. > Upstream doestn't say anything there that this will change. Issue was > closed with the hint it's documented. And it will just run with default > settings. It does, but using just a single thread. There's not exactly many x86 machines with only a single hardware thread that are still in use. What about defaulting to SMP when there's no user input? The UP mode has little purpose for existing -- if concurrent accesses to memory break, they'll also break when running the actual productive task the machine is supposed to do. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ At least spammers get it right: "Hello beautiful!". ⠈⠳⣄⠀⠀⠀⠀
