Date: Wed, 6 Dec 2023 08:18:13 -0800 From: Mark Millard <marklmi@yahoo.com> To: Nuno Teixeira <eduardo@freebsd.org>, "Elmar K. Bins" <elmi@4ever.de> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: [Raspi4 13.2] Keyboard woes Message-ID: <52369F28-36F2-4B1A-A76A-8978B29E403A@yahoo.com> In-Reply-To: <CAFDf7UKXZbyja7A56evKOGbQAqR-YO7ZMq3K3Pi5Nk=RkxWOXA@mail.gmail.com> References: <ZXA-t6Q8c7OyVzSS@noir.de> <CAFDf7U%2BzSqch0wr6rxbVSA4dqh7=6CbsLxrp1B=v299_FOQ_3A@mail.gmail.com> <CAFDf7UKXZbyja7A56evKOGbQAqR-YO7ZMq3K3Pi5Nk=RkxWOXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 6, 2023, at 04:34, Nuno Teixeira <eduardo@freebsd.org> wrote: > (...) > > https://lists.freebsd.org/archives/freebsd-arm/2023-July/002810.html > . . . While not directly related to keyboards, I'll note that I had text reporting: QUOTE initial_turbo=60 [It appears that with modern EEPROM context, the RPi* is dynamically adjusting the frequency/voltage combinations even during early booting. The initial_turbo use delays that for the indicated number of seconds (up to 60 sec). FreeBSD seems to not handle the variability and the above gives FreeBSD a stable context for such properties for early booting.] END QUOTE I later discovered that initial_turbo=60 was not sufficient for "boot -s" (single user mode) because the stable frequency/voltage can not be made to last long enough. I use force_turbo=1 to deal with wanting to "boot -s". I'll also note that using a serial console would be another way to get to a prompt for typing "boot -s". (It is how I normally operate for such so I do not normally notice any USB keyboard handling issues for that time frame.) Handling early boot problems without a serial console can be problematical. === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52369F28-36F2-4B1A-A76A-8978B29E403A>