Re: No GENERIC.hints for aarch64 (arm64?), armv7, and more; also /sys/ based paths are referenced but seem to not be universally standard; also which ARCH standard in path?

On Feb 18, 2025, at 16:04, Warner Losh wrote: > On Tue, Feb 18, 2025 at 4:57 PM Mark Millard wrote: >> On Feb 18, 2025, at 14:01, Warner Losh wrote: >> > >> > On Tue, Feb 18, 2025 at 2:56 PM Warner Losh wrote: >> >> >> >> On Sat, Feb 15, 2025 at 10:04 AM Mark Millard wrote: >> >>> [This see

Re: No GENERIC.hints for aarch64 (arm64?), armv7, and more; also /sys/ based paths are referenced but seem to not be universally standard; also which ARCH standard in path?

On Tue, Feb 18, 2025 at 4:57 PM Mark Millard wrote: > On Feb 18, 2025, at 14:01, Warner Losh wrote: > > > > On Tue, Feb 18, 2025 at 2:56 PM Warner Losh wrote: > >> > >> On Sat, Feb 15, 2025 at 10:04 AM Mark Millard > wrote: > >>> [This seems likely to not be limited to main [so: 15 as stands].

Re: No GENERIC.hints for aarch64 (arm64?), armv7, and more; also /sys/ based paths are referenced but seem to not be universally standard; also which ARCH standard in path?

On Feb 18, 2025, at 14:01, Warner Losh wrote: > > On Tue, Feb 18, 2025 at 2:56 PM Warner Losh wrote: >> >> On Sat, Feb 15, 2025 at 10:04 AM Mark Millard wrote: >>> [This seems likely to not be limited to main [so: 15 as stands]. >>> But I'm using main as the example for the issue.] >>> >>> In

Re: No GENERIC.hints for aarch64 (arm64?), armv7, and more; also /sys/ based paths are referenced but seem to not be universally standard; also which ARCH standard in path?

On Tue, Feb 18, 2025 at 2:56 PM Warner Losh wrote: > > > On Sat, Feb 15, 2025 at 10:04 AM Mark Millard wrote: > >> [This seems likely to not be limited to main [so: 15 as stands]. >> But I'm using main as the example for the issue.] >> >> In: >> >> # man 5 device.hints >> DEVICE.HINTS(5)

Re: No GENERIC.hints for aarch64 (arm64?), armv7, and more; also /sys/ based paths are referenced but seem to not be universally standard; also which ARCH standard in path?

On Sat, Feb 15, 2025 at 10:04 AM Mark Millard wrote: > [This seems likely to not be limited to main [so: 15 as stands]. > But I'm using main as the example for the issue.] > > In: > > # man 5 device.hints > DEVICE.HINTS(5) FreeBSD File Formats Manual > DEVICE.HINTS(5) > > NAME > de

Re: Quieter startup + working experience by overriding VT_CONSWINDOW (and consequences)

> On 18. Feb 2025, at 13:31, Steven Harms (High-Security Mail) > wrote: > > Greetings, > > As per previous thread, I am still interested in a quieter fbsd experience: > ideally no kernel / rc output on startup and no console messages on default > TTY after login. > > As I was trying to se

Quieter startup + working experience by overriding VT_CONSWINDOW (and consequences)

Greetings, As per previous thread, I am still interested in a quieter fbsd experience: ideally no kernel / rc output on startup and no console messages on default TTY after login. As I was trying to see if I could extend boot_mute, I came across another approach: - set the default console to

Two issues with 571df2c64a3c1a

I'm running -current on my primary laptop (T14sG2Intel), which cramps my style when it comes to getting to the bottom of these two issues. 1. Panic when TB3 dock is unplugged. uhub0: detached ugen1.1: <(0x1b73) XHCI root HUB> at usbus1 (disconnected) Fatal trap 9: genera