Is there anything else I can do to help solve this problem? I just tried the last daily iso with firmware with no luck.
Also I've discussed the problem with GRUB inserting an entry in the EFI boot automatically which overrides user setting in BIOS. That means if I last booted into Debian I will go directly to Debian without having the ability to press F2 (or whatever key is needed to access BIOS settings).. I mentioned that this caused a problem on a multi system boot, especially for those of us who cannot see well, but also for everyone because the only way to change this is either to open up the computer or laptop and reset the BIOS by pressing a rubber domed switch which I suppose grounds the capacitor is there to holds a voltage on the computer CMOS to keep settings, pushing the little switch puts the voltage to zero and restore the factory settings. There is a problem and I'm trying to get someone to fix it. It's probably an unfortunate consequence of this "feature" - GRUB would work just right without this feature, and I cannot think of any reason that this "feature" exists. It appears to be a bug. It's certainly understandable to those who who must now take extraordinary measures to reset their BIOS by resetting the CMOS. For blind persons who have already obtained sighted help to et up their BIOS the way they want it, to boot from USB HD - a USB stick, it's totally unwanted and very inconvenient. I have no idea if GRUB is aware of this bug. I believe even if GRUB is intended to do this, it shouldn't, it seems to be be an unfortunate consequence of their work. Even if it can be overridden, it is much too complicated for the average computer user. (Some kind member of this list sent me instructions to override this new behavior of GRUB, but they are extremely complicated. If anything this "feature" should be enabled only as an option. I've just subscribed to GRUB bugs list to tell them of this, hopefully it can be fixed because it overrides the user's BIOS settings. Best wishes to all, David On Tue, Jan 4, 2022 at 2:54 PM D.J.J. Ring, Jr. <n...@arrl.net> wrote: > I have already done that, did it not go through? I did receive a message > saying that the message I sent because it didn't mention a package would be > disregarded. > It would have been sent from n...@arrll.net - any way of checking > further? Darn it, I should have BCC it to you, Samuel. > > Thanks, > > David > > On Tue, Jan 4, 2022 at 3:53 AM Samuel Thibault <sthiba...@debian.org> > wrote: > >> Hello, >> >> As already mentioned, please do this: >> >> install with the Buster image, and use reportbug to send the >> installation information, just like you did with Bullseye on Mon, 3 Jan >> 2022 14:18:39 -0500. >> >> Really, do please do that. >> >> Samuel >> >
