00:33:57 uskerine, I'd look (specifically) at chapter 3 (quick porting) or the Porter's Handbook. https://docs.freebsd.org/en/books/porters-handbook/quick-porting/ 00:34:15 s/ or / of / 01:06:49 i wish i resilvered at 339M/s 01:35:52 Matt|home: that bread looks delicious 02:08:22 Matt|home: how many folds did you do? 02:08:44 its still quite edible, the high density is less structure to support air/bubbles 02:09:30 building the structure can be in the chemistry of the dough/flour and or the structure built during the mix/folding process 02:10:39 structure == gluten basically 02:51:23 Matt|home: +8 to cooking profession granted 03:21:30 trying to boot 15.0 installer on a epyc CPU server panics: madt_parse_apis: double apic id 241 12:38:41 trying to boot 15.0 installer on a epyc CPU server panics: madt_parse_apis: double apic id 241 14:02:05 kerneldove, did you try disabling ACPI like was suggested yesterday? 14:08:46 ya 14:09:17 i tried set acpi_load="NO" and hint.acpi.0.disabled="1" from installer loader then ran boot 14:09:27 CrtxReavr, ^ 14:11:07 Same results? 14:20:51 ya 14:20:54 same panic 14:36:08 seeing how tied n computers are these days with ACPI half the time that doesn't work 14:36:44 especiallylaptops 14:41:31 ya doesn't surprise me. it's just weird that fbsd chokes on this double id issue instead of mitigating it. freebsd is server focused, this is a epyc server platform, so wtf 14:41:37 and it's 2021 hw too, now too old/new 14:41:54 i went to switch from uefi to bios but the bios didn't support that. PoS 14:42:06 i wonder if i can disable hyperthreading 14:42:29 <[tj]> kerneldove: can you create a bug for this 14:43:42 i don't think i have a bugzilla account. if i collected all of the data together and posted a link would someone else be willing to? i'd remain available to do any testing, with the caveat that i can only try released iso's like 15.0-R because i have to pick from an iso library my host maintains 14:43:52 so i can't like, try patches and stuff sadly 14:44:35 <[tj]> kerneldove: that makes debugging more difficult, it is best if you create the issue, you are the only one who can answer questions about it 14:44:51 ya 14:45:27 :/ 14:57:17 Why are you so hell-bent on 15? 14:58:40 i'm not. there's a 14.3 iso in there too and i tried that too 15:01:51 Same issue with 14.3? 15:04:09 yep 15:37:50 You're not using ventoy by any chance kerneldove ? 15:38:04 no i dunno what that is even 15:39:56 <[tj]> kerneldove: I thought you were quite clear about why things are the way they are 15:40:14 huh? 16:44:36 does anyone know who is working on importing cves into vuxml 16:44:38 (automation) 16:44:45 it was on the mailing list about 6 months ago, I am interested 17:44:27 polarian: vuxml any commiter can edit that database 17:47:55 for some weird reason the xf86-intel drive is very unstable think I fxed my crashes by finally removing that driver and setting the driver to modsetting as the freebsd machine ha sbeen on for 24+ hrs without a freeze 17:51:36 outdated, no longer in use 17:53:18 may have to update to currnt or stable as this mini PC was manu about a month ago and I think its too new for freebsd to run properly 17:53:54 Manufactuer Date: 11/30/2025 18:46:15 cpet: no thats not what I am talking about 18:46:30 there is a team working on automatic vuxml entries from cve databases 18:46:40 it was within the ML but I cant find it now 18:49:36 I thought xuxml was going to be retired and replaced with a more modern database, but maybe I just misunderstood how it would work. 18:51:24 cpet: not hardware but xf86-intel is old, usually modern intel cards work fine with the generic modesetting 18:56:46 o0x1eef: same but I have been told otherwise 18:56:48 soo... 18:56:50 * polarian shrugs 20:30:54 Right, here we go… freebsd pkgbase jail time 21:03:32 Interesting, there appears to be a bug in FreeBSD 15 on aarch64 (arm64) where by default, TCP packets passing through an epair (tun/tap), such as with VNET jails, end up having a bad checksum 21:03:34 https://forums.freebsd.org/threads/no-access-to-external-network-from-vnet-jails-in-15-0-release.100669/ 21:03:55 polarian: none of the status sheets mention it 21:04:06 DaliborFox: so instead of mentioning it here open a PR for it ? 21:04:09 I'm going to try to reproduce it in a virtual machine tomorrow, trying both x86_64, and if it doesn't happen there then aarch64, and open a bug report about it 21:05:32 cpet: I'll take a look, I've figured out what's going on just today :) The upgrade process has been quite a battle 21:08:44 i thought freebsd change where bridges cant have direct IP's or what not 21:10:44 May I kindly request a link to where the change is described? Though in this case, it seems to be a case of a bug in the epair driver, since tcpdump reports packets with a bad tcp checksum, UDP and ICMP are unaffected, and a workaround (described in the forum post) is to disable "TCP checksum hardware offloading" on the driver 21:14:22 The bridge(4) sysctl net.link.bridge.member_ifaddrs now defaults to 0, meaning that interfaces added to a bridge may not have IP addresses assigned. 21:16:15 Yeah, I think that's unrelated, I don't assign IP addresses to the interfaces added to the bridge, just the bridge itself, and then the interfaces "on the other side" of the epairs 21:35:27 what I've learned is that the FreeBSD-runtime and FreeBSD-rc are not enough to get a jail up and running, although I'm not yet clear on what I do need. I might install FreeBSD-base and make sure it runs at all, _then_ try being a smartass 21:36:02 still, fun process: you need the pkg keys in the right place and somewhere to store downloaded files and it's happy 21:45:02 I'm quite looking forward to messing around with pkgbase as well! Hopefully it'll be faster than freebsd-update, since I've spent the last several evenings upgrading from 14.3-RELEASE to 15.0-RELEASE with that 21:46:41 that reminds me, I need to update, and also to complain about freebsd-update again 21:47:59 If you have VNET jails and they stop working, there's a workaround in the above forum thread 21:49:35 thanks, I'll keep that in mind for my VM 21:49:53 also, migrating from Heimdal to MIT Kerberos is a bit of a pain when going from 14.3-RELEASE, I ended up having to set up a chroot with a 14.3-STABLE snapshot and using that to dump the database into a MIT-compatible format 21:50:43 Thankfully I don't have kerberos running on any of my BSD servers :P I kept those on Debian so that I could more easily use those as AD domain controllers 21:50:47 the version in 14.3-RELEASE does not support the transition... and the version in ports / pkg doesn't support the database format used by heimdal in the base system, which is no longer included by default in 15.0-RELEASE :D 21:51:42 Perhaps that could be more prominently mentioned in the release notes, as a warning in the "Userland Configuration Changes" section 21:53:49 fonks: Fair enough! I decided to set up a FreeBSD server on one of those ARM SBCs as my "network centerpiece" :D 21:55:33 the only real mission-critical BSD system I have is a webserver/RTMP streaming target used for one of my local-insertion cable channels :P it recieves the stream, converts it to ASI, and that goes to my modulator rack where it gets processed by multiple times my net worth in Blonder Tongue modules to become a QAM digital channel 21:55:39 Originally I was using Debian too, but when the time came to upgrade my aging old Raspberry Pi to something beefier, I thought I'd try out something new/different 21:56:24 Oooh, that's really neat! 21:57:43 and then like we talked earlier, that gets processed into analog too since it's a hybrid system 21:58:49 Fun! 21:59:59 Mine is mostly just a NAS and an IRC bouncer, though I do plan on eventually using it to host a web page for my project once it gets into a state where it's ready to actually be used by other people. I'm hoping 2026 will be the year of dopl2_composer! :D 22:47:08 I wanted freebsd-minimal-set, not just the runtime 22:47:19 not sure how to get it to neatly bridge with jib; might handle manually 23:16:35 so i have to move some disks around later in the nas and i label them based on position so i can find them when they fail... https://forums.FreeBSD.org/threads/from-device-name-to-gpt-name.87147/post-674122 23:16:37 does that still hold? 23:18:14 can i just gpart modify -i -l F01_R01... then zpool set path=/dev/gpt/F02_R02... pool raidz2-0 23:18:29 i'm not sure what zfs will do once the label just disappears 23:20:14 actually i did that wrong. set path=/dev/gpt/F01_R01...