05:30:25 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? 05:32:11 yes 05:32:38 I really don't even know where to begin 05:33:03 my hardware is a decade old, so normally everything just runs fine on it 05:33:19 so whats the issue again? 05:33:39 fix it, then make a pull request 05:34:40 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 05:34:52 did you debug it? 05:34:54 on 14.3-RELEASE or 15-CURRENT either one 05:35:13 I have not, because I have no idea how to do such a thing 05:35:21 then start ther 05:41:35 your moving into major versions, so its going to break things 05:43:06 (A minor version bump 14.2 to 14.3 (usually) shouldn't break things) 05:45:22 I'm going to right the image of 14.2-RELEASE on a stick and see if it boots consistently 05:45:46 if not, some of the few hardware changes I have made since then, I will try to revert the best I can 05:46:39 aye, did you try to go from 14.2 to 15...then 14.2 to 14.3? 05:48:06 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 05:49:33 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 05:50:05 when I can get it to boot up, even in safe mode, all of this hardware works fine 05:50:20 its a decade old and has an nvme drive? 05:50:39 MrHAPPY: Yes, X99 from 2015 05:50:47 Gen 3 nvme support 05:51:13 ahh, what year is it 05:51:28 we are currently in 2025 05:51:37 jhc 05:51:59 He died a Long time ago 05:52:09 i just did also 05:56:25 do you have a silly keyboards with lights 05:57:29 Yes, Logitech G910. But I swapped it out for a regular Cherry Silent Keyboard and that didn't resolve anything 05:57:51 firmware mailware 05:59:14 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 06:00:36 your entire system is compromised 06:21:05 Seems it is just Limited to running Linux now 06:22:47 Try booting with ACPI disabled 06:23:07 divlamir: it doesn't even go past the boot loader with that. already been tried 06:23:18 most of the time it will boot up on "safe mode" though 06:23:23 even that isn't 100% 06:24:24 I tried taking out the 10G Intel NIC and that didn't help either 06:24:45 don't have the energy to swap out chips (the processor). Might try that tomorrow though, just for shits and giggles 06:41:25 Looks like "safe mode" doesn't do much more setting a few variables: https://github.com/freebsd/freebsd-src/blob/main/stand/lua/core.lua#L176-L181 06:41:54 Maybe try setting them one by one and see which one lets your system boots 06:47:16 divlamir: much appreciated. I will bookmark that and start looking into it 11:14:34 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. 12:12:08 how can i see what versions of libssl are installed on the OS? 13:07:27 pkg which /usr/local/lib/libssl.so 13:30:07 ahh ok ty 13:34:27 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 13:34:46 usually ports OpenSSL is not used unless you explicitly request it in ports that support that 13:47:57 ahh 13:48:41 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 14:10:06 yeah, when you cross compile it wouldn't know where to look for it 14:17:38 if you're cross-compiling you need OpenSSL for the target, not the FreeBSD version 14:17:55 so build/find a version of OpenSSL for Linux musl and put that in the compiler path (or whatever Rust uses) 16:28:17 divlamir: would those settings go into /boot/loader.conf /etc/sysctl.conf or some other place (rc.conf) ? 16:29:47 okay the LLM/AI says loader.conf 16:30:33 Or just set them at the boot prompt for testing 18:29:48 1 18:30:06 I hope the issue isn't with SMP, and it is just some lesser thing like DMA 19:27:07 Sure enough it is SMP lol 19:27:22 divlamir: thanks again for your help 19:48:36 Really wish it was anything else lol 22:24:58 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 22:56:42 wipt: Did you copy the right .efi file over? 22:57:18 wipt: Likely /boot/loader.efi ...? 23:22:42 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... 23:37:33 alright, altroot= 23:41:31 *crossing fingers 23:42:33 nope, that didn't do it. panics when you try to boot multiuser 23:42:52 or something like that, reboots fast 23:44:33 At this point, maybe a live system to grab configs and the little data off and reinstall. Just a lot of hassle, though.