Guys, If I can get my machine up and running on FreeBSD 14.2-RELEASE. Do you all think you could help me find out why 14.3 and 15-Current don't consistently boot up for me?

yes

I really don't even know where to begin

my hardware is a decade old, so normally everything just runs fine on it

so whats the issue again?

fix it, then make a pull request

well, it hangs on boot right after the ACPI line, but if I turn off ACPI in the boot options it fails to do anything at all, doesn't even go past the boot loader

did you debug it?

on 14.3-RELEASE or 15-CURRENT either one

I have not, because I have no idea how to do such a thing

then start ther

your moving into major versions, so its going to break things

(A minor version bump 14.2 to 14.3 (usually) shouldn't break things)

I'm going to right the image of 14.2-RELEASE on a stick and see if it boots consistently

if not, some of the few hardware changes I have made since then, I will try to revert the best I can

aye, did you try to go from 14.2 to 15...then 14.2 to 14.3?

I've ran 15-CURRENT on this machine off and on for months. I also did an install of 14.2 on it, and ran that for several weeks

I probably have a different nvme drive in it right now than then, a 10G Intel dual Port NIC, and I am on a different keyboard. Everything else is the same

when I can get it to boot up, even in safe mode, all of this hardware works fine

its a decade old and has an nvme drive?

MrHAPPY: Yes, X99 from 2015

Gen 3 nvme support

ahh, what year is it

we are currently in 2025

jhc

He died a Long time ago

i just did also

do you have a silly keyboards with lights

Yes, Logitech G910. But I swapped it out for a regular Cherry Silent Keyboard and that didn't resolve anything

firmware mailware

Okay, going to see if 14.2 will boot up well for me now. Will be back to continue this conversation soon, either from this system, my other system, or my phone

your entire system is compromised

Seems it is just Limited to running Linux now

Try booting with ACPI disabled

divlamir: it doesn't even go past the boot loader with that. already been tried

most of the time it will boot up on "safe mode" though

even that isn't 100%

I tried taking out the 10G Intel NIC and that didn't help either

don't have the energy to swap out chips (the processor). Might try that tomorrow though, just for shits and giggles

Looks like "safe mode" doesn't do much more setting a few variables: github.com/freebsd/freebsd-src/blob/main/stand/lua/core.lua#L176-L181

Maybe try setting them one by one and see which one lets your system boots

divlamir: much appreciated. I will bookmark that and start looking into it

hello, i am working on QEMU FreeBSD Client, as i saw virtio_gpu requires manual compilation. I followed guides on Handbook but compiled binaries doesn't contain virtio_gpu.ko file although its added.

how can i see what versions of libssl are installed on the OS?

pkg which /usr/local/lib/libssl.so

ahh ok ty

kerneldove, divlamir: that's for ports OpenSSL, but the base system also provides OpenSSL, you can use "/usr/bin/openssl version" to find the version

usually ports OpenSSL is not used unless you explicitly request it in ports that support that

ahh

i was building some rust code on freebsd for musl target and debian where i ran it couldn't find openssl.so.12 or smth and i couldn't fix it so what i did was make the rust code build with vendored-openssl so it's built in and now it runs

yeah, when you cross compile it wouldn't know where to look for it

if you're cross-compiling you need OpenSSL for the target, not the FreeBSD version

so build/find a version of OpenSSL for Linux musl and put that in the compiler path (or whatever Rust uses)

divlamir: would those settings go into /boot/loader.conf /etc/sysctl.conf or some other place (rc.conf) ?

okay the LLM/AI says loader.conf

Or just set them at the boot prompt for testing

1

I hope the issue isn't with SMP, and it is just some lesser thing like DMA

Sure enough it is SMP lol

divlamir: thanks again for your help

Really wish it was anything else lol

Hey there! I updated to 14.3R, and updated my zroot... without updating the bootcode. I've booted with the installer and installed the bootcode into the boot section (not ZFS), and now when trying to boot the system it brings up a EFI shell

wipt: Did you copy the right .efi file over?

wipt: Likely /boot/loader.efi ...?

mason: I have not. Looking into that. I'm a bit confused because when I boot from a thumbdrive, import zroot, I'm looking at that as the root FS...

alright, altroot=

*crossing fingers

nope, that didn't do it. panics when you try to boot multiuser

or something like that, reboots fast

At this point, maybe a live system to grab configs and the little data off and reinstall. Just a lot of hassle, though.