security to this address.
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
On Saturday, March 29th, 2025 at 8:46 PM, Steven Harms (High-Security Mail)
wrote:
> Hey folks,
>
> I tried building current from source and when I boot, I get a panic after the
> fina
Hey folks,
I tried building current from source and when I boot, I get a panic after the
final Autoloading module (pchtherm, in my case) loads. Comparing to the stable
14.2 kernel, the next step is for "Setting up harvesting," "Feeding entropy,"
and starting wpa_supplicant.
To be clear, this c
Well, Warner and Manu, it's been quite an education I've gotten myself into! If
anything, it confirms that my sense of C isn't as bad as I thought it was and I
was indeed looking at a ball of knots.
I'll tried Warner/Manus's suggestion re: boot_mute="YES" and a specified
splash="" value does not w
nguage / versioning in the man pages, but will update later today after I
install the world.
On Sat, Mar 22, 2025 at 03:02, Emmanuel Vadot
<[m...@bidouilliste.com](mailto:On Sat, Mar 22, 2025 at 03:02, Emmanuel Vadot
< wrote:
> Hi,
>
> On Fri, 21 Mar 2025 22:13:29 +0000
> "Ste
Folks,
I am attempting to figure out what boot_mute wants me to do. I'm trying to make
a "laptop guide" and I'm confused. I'm not a C programmer at this scale of
sophistication so there's a decent chance I'm foolishly making an error, but
current is not doing what I expect.
- boot_mute doesn't
Folks,
The docs say:
All compositors using Wayland will need a runtime directory defined in the
environment. Since FreeBSD 14.1, this is created and defined automatically. For
previous versions, this is achieved with the following command in the bourne
shell:
% export XDG_RUNTIME_DIR=/var/run
Folks,
I built a GENERIC kernel "hot off the presses" as of the commits cited above. I
am surprised that I'm still getting error messages in dmesg​ about:
- Firmware errors
- i915/skl_dmc_ver1_27.bin: could not load binary firmware
/boot/firmware/i915/skl_dmc_ver1_27.bin either (repeats)
- drm
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
e:
>>
>>> Remember that quiet/silent != fast. You might as well ask for a "pretty"
>>> splash screen instead of the dizzying text scroll.
>>>
>>> On Mon, Feb 3, 2025, 12:05 Gleb Smirnoff < gleb...@freebsd.org> wrote:
>>>
>>>
On Sunday, February 2nd, 2025 at 2:38 PM, Tomek CEDRO wrote:
> One "black box" scenario that came to my mind we did not mention is
> some embedded system that we really do not want to show anything OS
> related just the final login prompt.. or was that the initial idea?
That wasn't one of my mai
> Okay, I am sorry, I mixed the general idea with detailed PR that aims
> just updating routing and devmatch parts with user selectable option
> not changing a defaults, thus my previous remarks are invalid and
> updated, I apologize! :-)
A goal of this PR was to flush out dialogue around whether
Greetings,
I have created https://github.com/freebsd/freebsd-src/pull/1582 in an effort to
quiet down some of the chattiness of module linking and network diagnostics on
startup. I'm used to working in a git-based workflow and saw no action on the
PR, so I thought I would notify here. If that's
12 matches
Mail list logo
