Date: Sat, 25 Feb 2023 16:05:58 -0800 From: Mark Millard <marklmi@yahoo.com> To: Mike Karels <mike@karels.net> Cc: Mitchell Horne <mhorne@FreeBSD.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: reboot broken on RPi4 on main [breaks at git: e6cf1a0826c9 - main - physmem: add ram0 pseudo-driver] Message-ID: <B659E221-9DA7-4121-A283-FD26AC55C2DA@yahoo.com> In-Reply-To: <5E055A77-24DB-44D3-89F8-5113555283EA@karels.net> References: <D3367B4A-AFDC-4C75-8B99-3F6CB5E18360@karels.net> <A2E6D3E1-A8C3-41BB-9E23-B2BC73CEC5BD@yahoo.com> <9EA91B94-87E4-47B8-A4E2-60D556E64276@yahoo.com> <4FCD4987-6DAF-4889-B684-B6E464F41144@yahoo.com> <D2521F92-9529-4244-8B86-848E1D13CCD3@yahoo.com> <EB0DE309-66ED-423E-B5A7-466A11871370@yahoo.com> <5E055A77-24DB-44D3-89F8-5113555283EA@karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 25, 2023, at 08:09, Mike Karels <mike@karels.net> wrote: > I verified that the current kernel can reboot if it was booted > with hint.ram.0.disabled=3D=E2=80=9C1=E2=80=9D in /boot/device.hints. My boot media that are used with RPi*'s also boot other types of systems --and I use them that way at times. So far, I do not see a way to limit hint.ram.0.disabled use to RPi*'s other than just remembering to adjust /boot/device.hints every time I move the media to or from a RPi* from or to some other type of system. More likely hint.ram.0.disabled will end up just always being used for media that can boot RPi*'s, at least as long as "shutdown -r now" would otherwise be broken on the RPi* 's. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B659E221-9DA7-4121-A283-FD26AC55C2DA>