00:09:46 There it is 00:12:09 scoobybejesus_tl: thaks for tip 00:12:13 thanks 00:13:10 jails are so cool 00:13:48 * rtj mumbles 'not the county jails' 00:21:51 https://cgit.freebsd.org/doc/commit/?id=319892a75b6c8c37f3ebe4bf28b60e3703d95bab High-flying FreeBSD release. 00:22:34 my bhyve vm is getting shutdown (when i go to sleep) on 15-RELEASE 00:23:30 not sure its related to 15-REL, but only now this is happening 00:25:38 hernan604: That sounds like a HV setting on what to do on sleep. save state or shutdown? 00:28:44 skered: hmm could be maybe ? it also coincides with my recent switch to kde-plasma after 15-REL install... and i dont know if kde-plasma sleeps or does some weird thing... 00:28:53 i only used i3/dwm for decades 00:37:58 Oh, we got the announcement a day early. Unless they meant December 2nd UTC. 00:38:13 mason: I think everything is UTC. 00:38:36 Makes sense. 00:41:12 That's how we do it in amateur radio. So all the logs match up. 00:45:05 Thanks for another release 00:54:08 so, 3 or 4 days ago, i upgraded from 15-RC2 to 15-RELEASE ... how an i know i did get the final 15-REALEASe ? 00:57:55 hernan604: You should be able to use freebsd-update for it. 00:58:01 RC2 should be known. 00:58:01 There are checksums in the announcement. use sha256sum and or sha512sum to check the image you downloaded matches. 00:58:36 Oh, never mind. I misread. 00:58:54 hernan604: "freebsd-update -r 15.0-RELEASE upgrade" should do it, IIRC 00:59:28 hernan604: Even better: https://www.freebsd.org/releases/15.0R/installation/#upgrade-binary 01:01:16 mason: hey man how you doing? 01:07:29 The 15.0-Release release notes are live. 01:11:13 scottpedia: Doing well! Got to go snag dinner, and we're going to take in a podcast on a system we recently moved to FreeBSD. We're using FreeBSD for more workstations here, which is nice. That it's suitable for that nowadays is great. 01:12:22 right good for you man mason 01:34:15 The jail(8) command now supports the zfs.dataset parameter to attach a list of ZFS datasets to a jail. e0dfe185cbca wow awesome 01:35:10 It sure is! 01:35:11 i was using nullfs 01:35:28 I still use nullfs, but there are times when that would come in handy, for sure. 01:35:59 i kept trying to force it to use dataset. before i rtfm 01:50:44 Is there a way with pf to basically say "listen on port 443. if it is SSH traffic, redirect to localhost:22. If it is HTTPS traffic, check the SNI and redirect to the appropriate jail/ipaddress". I want to replace what SSLH does because it seems to be crashing lately, leaving me remotely locked out from the home system, and I can't seem to find out why SSLH has been crashing. 02:05:32 mns: is there any reason as to why you can't use separate ports? 02:16:09 DarkUranium: port 22 would be blocked from work, so I use 443 to connect to home 02:17:26 not just at work, but when I'm travelling, many places block of most ports and just keep 80 and 443 open 02:18:21 I don't think pf is gonna be able to distinguish between protocols like that, you would want to write a service tha does the switch for you 02:18:36 like SSLH... 02:18:47 mns: closest thing might be an authenticated https proxy, then configure your ssh client to use it 02:28:01 LxGHTNxNG: sslh or haproxy would be the other choice. 02:28:46 zi: might look into that as well 02:32:03 Nice artice on Phronix about Sylve. :) 02:32:17 I have not messed with that one yet. 02:36:29 vm-bhyve works fine for my simple setup. Huge user base for point and click though. I love how slim Sylve is while providing a GUI. 03:04:49 rtj: no you dont 03:08:38 cpet: hi 03:08:49 hi 03:12:01 hey all, I'm just introducing a young programmer to the joys of IRC. anyone around to say hello? 03:15:20 anybody running a mastodon server on freebsd? is that even possible? 03:16:34 Macer: you should check out https://bsd.cafe 03:17:08 and http://bsd.network 03:17:50 oh. yeah i know they have their own fediverse servers.. but that doesn't necessarily mean they're running them on fbsd. i just figured there would be a bunch of awkward requirements that you may only find in linux 03:20:04 https://wiki.freebsd.org/Ports/net-im/mastodon 03:20:07 that seems a bit dated 03:21:19 TIL of Sylve, I'll have to try it. 03:21:53 I assumed that bsd.cafe is on freebsd, and bsd.network is on openbsd. And http://illumos.cafe is smartos in a freebsd bhyve vm 03:22:14 josephholsten: not sure 03:22:32 maybe on freebsd.. in bhyve... running linux :) 03:22:54 i wonder what version is in the ports tree now 03:23:15 mastodon-4.3.6_1 03:23:30 so i guess they must be... albeit a slightly older version 03:24:30 mastodon lifespans for minor versions last forever though. i am pretty sure they still do updates for 4.2 which is fairly old nowadays 03:25:41 Countdown to the end of life for Mastodon 4.1.x - this version will no longer receive updates (including for security issues) after April 8, 2025. 03:25:52 i guess 4.1 was obsoleted in february 03:44:04 is using freebsd-update to go from 13.5-RELEASE-p7 to 15.0-RELEASE expected to work? The relnotes say "Systems running 14.3-RELEASE can…", does that suggest other versions cannot? 03:53:34 congrats on 15R! 04:06:26 Macer: I run my Mastodon on FreeBSD. 04:07:30 Although from source, not from the port. 04:15:28 ˜/39 04:30:48 entrop: my gut is telling me.. that would be a big leap and would recommend not doing.. especially if it does not say it explictly 04:38:19 Hm. If I have a webcam and webcamd is detecting it, but it's not in /dev/sndstat, is there a proper way to deal with that? 05:01:02 Weird, another FreeBSD box, and it shows up. Going to compare everything I can. 05:02:09 entrop: Upgrade to 14, then to 15. 05:13:07 Figured it out. It was the cargo cult zapping me. devmatch_enable="NO" 05:20:20 With devmatch enabled, the camera is able to bind to both ugen *and* uaudio, whereas with devmatch disabled it only bound to ugen. 05:39:05 entrop: you have to go from 13.x to 14.x to 15.0 05:56:50 ok I file 4 zpools on this machine. I boot the 15.0 installer and use manual partitioning where I get a shell and run zpool import and none of my zpools are listed 05:56:53 odd 05:58:51 why not just update it using freebsd-update, or src 06:03:06 cpet, I don't want to update, I want to create a whole new fs and install on that. I want a totally clean install with no artifacts, and I want to be able to look at the old root filesystem from within the new one (I also do one FS for / /usr /var, all my data is on a separate fs) 06:04:06 the installer will create a new pool for you 06:07:13 I don't want a new pool, I want a new fs on an existing pool 06:09:16 why 06:09:18 15R is feeling smooth here. upgraded and reinstalled to a bunch of machines no problems 06:09:54 kerneldove: had some sisues with firmwares but that was resolved by removing all gpu-* and having fwget install it 06:10:20 did an upgrade or fresh install? 06:10:26 src install 06:10:30 ah 06:10:43 i build world in like 25 mins so 06:10:49 i rather build than use freebsd-update 06:11:36 I don't want a new pool I have enough pools and I have space on an existing pool and I don't want a new install to have left over files from a previous install that weren't touched by this install, my root fs is throwaway, all my data is elsewhere 06:12:38 Well then. 15.0 has some bugs. I'm taking notes and will start opening them tomorrow. 06:13:45 you may need to install updated boot code or upgrade the pool before you can use it on 15.0 06:14:52 figured it out, when importing, the / partition on the zpool was mounting over the installer root 06:16:52 look at you doing some googling 06:18:17 nope, it just dawned on me 06:18:30 yeap google can do that as well 06:18:33 Pirates can work around that.... ARrrrrrrr! (-R) 06:20:14 i like these videos that make building a computer like rocket science when I buitl my first computer at around 12 years old back when you actually had to know a little about the computer and imply adding in ram pretty much failed each time 06:21:10 thing that gets mne every time are the power, and IO connectors always backwards ;/ 06:30:01 so, direct 13.5 -> 15 with freebsd-update worked fine 06:31:19 living on the edge good for you man 06:33:58 In general probably the most important thing would be to update the bootcode so that it will boot from an upgraded storage array especially if it is zfs. 06:34:49 rwp: i gave up after he kept on saying i want i want and i want heh 06:40:59 when doing an install what are the "optional" packages? 06:41:26 none really kde was rtemoved 06:41:46 you can install vim 06:42:23 that is if you want ' 06:44:01 I'm not talking about the packages you can install after installation but when you install systems components like base/debug/devel/kernel-dbg/lib32/optional/src/test 06:44:11 all of them are clear except optional 07:01:15 https://cgit.freebsd.org/src/tree/release/packages/sets/optional.ucl 07:01:19 heh doesnt say much 07:07:32 You can download the other optional components from https://download.freebsd.org/releases/amd64/14.3-RELEASE/ and then unpack them. 07:08:37 on a 15.0 system ? 07:10:23 Do I have to do all of the work? Sigh. https://download.freebsd.org/releases/amd64/15.0-RELEASE/ 07:10:44 * rwp must relocate here, it's past midnight and time for me to head home 07:11:34 pkgbase optional packages differ than the ones in that ftp dir 08:44:53 s/differ than/differ from/ 08:50:47 why do we need 15 FreeBSDs? wouldn't 2 or 3 be enough? i don't understand why the project is endorsing such conspicuous consumption 08:54:53 ^ Good alliteration 08:55:17 Does FreeBSD support UAS/UASP for external USB hard drives? 08:55:23 ant-x: no 08:55:46 ant-x: there were some concerns around patents that discouraged implementation of UASP, meanwhile, no one implemented UASP 08:56:03 Not even Linux? 08:56:08 ? 08:56:15 i mean no one implemented it on FreeBSD 08:56:21 we can't take code from Linux, the license is wrong 08:56:31 OK. 08:56:37 Any other BSD? 08:56:42 no idea 08:57:35 OK. In my case, a UASP HDD works with FreeBSD, but quote slowly, and takes about 30 seconds to mount. 08:58:00 if it works with FreeBSD, it's using umass(4), and taking 30 seconds to mount is a bug in something not related to UASP 08:58:10 you should post to a mailing list about this, probably fs@ or stable@ 08:58:15 A fallback protocol. 08:58:32 yes, most UASP devices can fall back to USB Mass Storage 08:58:37 The same UASP HDD is taking 30 seconds to mount on my Windows XP box. 08:58:41 but that doesn't mean they take 30 seconds to mount, that's clearly wrong 08:58:57 OK, will report a bug. 08:58:58 unless it waits 30 seconds before offering USB mass storage, which... i suppose could be a thing... 09:01:43 Several times I have observed it lose data: shall I umount it before ejecting, unlike usual USB sticks I use with the Automount udev daemon: ? 09:02:11 ivy, re: wait before defaulting to USB mass storage: seems likely. 09:02:40 i have never heard of a USB storage device which does that but vendors do do weird things so i wouldn't be surprised 09:03:13 Hardly the same bug in FreeBSD and Windows XP. 09:03:31 (on different hardware) 09:10:00 it seems when adding: echo 'FreeBSD: { url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest" }' > /usr/local/etc/pkg/repos/FreeBSD.conf on aarch64 freebsd-update -f fails 09:10:11 on 15-RELEASE 09:10:35 CrypticSquared: can you be more specific? how does it fail? freebsd-update doesn't usually care about your pkg configuration 09:10:55 pkg: Repository FreeBSD has a wrong packagesite, need to re-create database 09:11:05 that's normal, just run pkg update 09:11:21 that's what i get when i run pkg update 09:11:43 it prints that ever time you run it? please paste the full output somewhere 09:12:38 in a sec. just running it again 09:13:06 incidentally, you should not have a repo called 'FreeBSD' in 15.0 09:13:24 the repos are called 'FreeBSD-base', 'FreeBSD-ports' and 'FreeBSD-kmods'; see /etc/pkg/FreeBSD.conf 09:13:31 i'm not sure if that's the cause of your issue, though 09:14:26 sorry, FreeBSD-ports-kmods, not FreeBSD-kmods 09:14:34 Hrm. I got disconnected from my colo server. No biggie. SSH back in, but... screen -r doesn't find any screen sessions. 09:14:40 Even though I can see it in ps 09:14:55 https://pastebin.com/8ywqquLh 09:15:01 Alver: did you upgrade from screen 4.x to 5.x? this is normal behaviour (according to upstream), you should have killed your screen 4 session first 09:15:29 CrypticSquared: right, the problem is you're trying to set the URL for 'FreeBSD' but there is no such repository in 15.0 09:15:33 ivy: ah - that might be it, yes. Let me check 09:15:53 ivy i'm following the directions in the handbook for adding latest repo 09:16:02 CrypticSquared: then the handbook is outdated 09:16:15 CrypticSquared: look at /etc/pkg/FreeBSD.conf, find the repo you're trying to modify, and use the actual name 09:16:24 ivy ok 09:17:20 Right, indeed. Nice. Okay, nothing to see here, carry on. :°) 09:17:26 CrypticSquared: if you're trying to switch from quaterly to latest, then you probably want 'FreeBSD-ports' as the repo name 09:17:35 (still no tor .21 available - that is not good) 09:17:39 Alver: bit shitty behaviour though, especially since they don't warn you beforehand 09:18:31 ivy: somewhat. But eh, it is what it is. I'm already happy it's not voodoo happening. 09:19:29 I do wonder why there is no updated package for tor yet - it hit ports a week ago, I believe 09:19:48 it usually takes 2-3 weeks for the builder to rebuild ports 09:20:16 i think the amd64 builder did get upgraded recently, at least for 15.0 09:20:38 but still, a week is not very long 09:23:27 Ah, heh. Okay 09:23:47 I was imagining that once a package hits ports, it would take a day or two for builders to churn the pkg out 09:23:54 heh, if only 09:24:22 serious freebsd users either 1) build their own ports (using poudriere) or 2) do not use ports 09:24:34 this is an ongoing issue that we currently have no good solution for 09:24:34 Not enough builder capacity? Or is it more complicated than that 09:24:59 I always end up needing something that wasn't enabled :-( 09:25:05 Alver: it's somewhat more complicated in that we can only scale the builders so far before you literally can't put any more CPUs into the computer 09:25:21 Alver: the real solution will be to make builds distributed, but that requires someone to actually have the time to do that 09:25:34 I was just going to say. :°) 09:25:50 If it's single machine then yes, you hit a wall somewhat quickly 09:26:54 i personally think we should prioritise builds for the 5% of ports people actually use and let the 95% of other ports lag behind a bit 09:27:02 but again, that requires someone to actually implement that 09:27:24 like, it should not take 2 weeks to publish a fixed security update for Apache, or whatever 09:29:49 True. 09:30:26 Or yes, at least make a distinction between "urgent for CVEs" and "version bump without further ado" 09:30:51 yeah, but it's more complicated than that because the build tool can only take a full ports tree and build it 09:31:00 I figured. Easy it is not 09:32:10 Could always ask around if anyone has a spare SGI UV to donate. :°) 10:41:27 Is anyone working on FreeBSD support for the Framework Desktop? 10:41:38 I found this: https://github.com/FrameworkComputer/freebsd-on-framework/tree/main 10:42:56 OK yes so looks like various pieces missing, some of which are being actively worked on. 10:58:30 Are there any major changes in 15.0 that require an upgrade in the boot code/ EFI partition? 11:13:25 s2r: ZFS was upgraded, if you upgrade your root pool, you should also upgrade the EFI loader 11:58:46 and it is not a guarantee it will boot, even after bootloader update 12:35:32 4.19T resilvered, 77.02% done, 23:46:25 to go 12:35:41 well... at least i finally made it to the same day lol 12:36:29 expand: expansion of raidz2-0 in progress since Thu Nov 27 22:35:46 2025 12:36:31 12.2T / 69.2T copied at 34.2M/s, 17.63% done, paused for resilver or clear 12:36:38 i still have that lingering in the background too 12:38:53 Alver: I was gonna say I could try to donate a machine and then I realized its 15 years old lmao 12:40:29 SGI UV is probably a ridiculously high priced collectible 12:41:39 Is there a RISC/V port of FreeBSD ? 12:42:20 <[tj]> yes, freebsd was the first operating system with a riscv port 12:46:21 risc architecture is going to change everything ... hackers (1995) 12:47:30 i don't know how it didn't work out yet. they had p6 chips that were triple the speed of the pentium. 12:49:13 Every time I hear the word Pentium, im reminded of that time I put Linux on a really old laptop and sent a system info screenshot to my friends and one said "blimey! A Pentium!" 13:25:31 if im running 14.3 without pkgbase, should i run pkgbasify before upgrading to 15.0 or after? 13:30:37 been on a pkgbase install through the betas. now i get "pkg: No trusted public keys found" ... not sure if that's a problem, or if the pkg servers just haven't all synced up yet for the release 13:31:12 there's a note about it 13:31:40 https://www.freebsd.org/releases/15.0R/relnotes/#upgrade 13:31:51 thanks 13:36:18 Macer: bro that film is quite unrealistic 13:36:38 ultra-superficial 13:58:27 i have zfs running raid10 over 4 SAS drives. zpool status reports all online. but just to be sure everything is ok, what smartctl command can i run to check if any of the drives have failed or are experiencing errors? 14:00:03 is it smartctl -a /dev/drv0 ? 14:19:35 https://www.freebsd.org/releases/15.0R/announce/ 14:20:46 my freebsd VM is happily on 15.0R now :D 14:21:00 first time doing a release upgrade 14:21:04 great job folks! 14:25:49 ariadna, was it difficult, or did you follow the Handbook to the letter and succeed? 14:26:34 I followed the handbook 14:26:46 I mean, I'm not as fluent in this OS as I am in Linux 14:27:05 I just can't upgrade the ports though 14:28:44 hello 14:29:45 Anyone know what happens between "Loading splash ok" and "---<>---" during a system startup? Since the last RC4 update (not RC4 itself, but the last pkgbase update to it), and now on 15R, my system hangs after the splash message. 14:29:47 I was wondering if it is possible to upgrade from 14.3-RELEASE to 15.0-RELEASE with pkgbase? do I need to run the pkgbasify command? 14:30:53 ok, it's solved, I just had to remove the reference to the 'latest' repo and revert to 'quarterly' 14:33:19 * Alver looks at belspo.be and wonders if there still is some hope for Belgian governmental services after all :°) 14:35:03 ahah .. Belgium is "complicated" 14:44:22 I'm in that funny spot where the question is: what's simpler/faster? troubleshoot my issue, or just reinstall and restore ... hmm 14:44:55 markmcb: use bectl and go back? 14:45:19 markmcb: boot with verbose and look for more info 14:48:54 i'm in a be now, so that works. when i ran into the RC4 issue, i booted a BE and copied the RC4 kernel from the installer image and that seemed to make things work ... i'll try verbose mode, haven't done this before but sounds easy 14:49:20 I'm on 14.3, mod_perl with p5-libapreq2-2.17 and I'm getting ld-elf.so.1: /usr/local/lib/perl5/site_perl/mach/5.42/auto/APR/Request/Apache2/Apache2.so: Undefined symbol "apreq_handle_apache2" 14:49:47 markmcb: if you troubleshoot the issue, you are guaranteed to learn something, assuming you have the time/energy to dedicate to it. 14:49:54 it's never worked on this VM, I've trying reinstalling and even compiling from ports, no joy 14:51:28 markmcb: ah yeah, EFI isn't covered by bectl. i always rename current boot images to .old, before replacing 14:55:17 just tried "boot -v" from the loader ... nothing new. 14:55:39 Demosthenex: yes, I renamed to .old before copying the new one over 14:56:45 https://pastebin.com/Q6P5u4hw 15:06:38 mage: that's an impressive understatement there :°) 15:23:51 so if I read and understand well a 14.3-RELEASE should run pkgbasify before attempting pkgbase upgrade to 15.0-RELEASE.. correct? 15:26:28 does pkgbasify will be part of BASE someday? 15:36:48 mage It's not mandatory to use pkgbase on 15 so you don't _have_ to pkgbasify 14 before upgrading to 15 15:37:30 perhaps it will come to ports tree firts 15:45:19 cavokz: yeah I know :) I have tons of jails and I was awaiting pkgbase with great hope of speeding up upgrades 15:45:25 CrypticSquared, you got it working right? It was in the release notes, like 10 lines from the bottom. 15:46:02 having to freebsd-update -j ... -r xy-RELEASE on many many jails is painfully slow 15:49:33 mage: when i tried 14.3 -> pkgbase -> 15 i did not have a good time 15:49:57 but then i didn't see a documented update path 17:13:41 rtprio: I am not a big BSD expert. I went from 12.1 to 14.3 using this last ~7 years: https://paste.rs/6aeyy.txt 17:14:01 how long does buildworld usually take 17:14:27 approximately :) 17:14:39 it never broke my system, never failed to boot... 17:17:12 Thank goodness for mobile tethering... The WiFi decided to not cooperate after upgrading to 15 (not blaming fbsd here, I probably had a PEBKAC moment) 17:18:36 JetpackJackson: its likely freebsd 17:18:39 wifi breaks all the damn time 17:19:56 hell i'm running ghostbsd on a thinkpad E440 (based on 14.2 iirc) and the wifi stopped cooperating after suspend & resume. 17:20:30 good learning experience before installing freebsd though \o/ 17:22:17 Ah 17:23:09 polarian: on thinkpad t480 with i7 cpu buildworld ( from scratch ) takes around 6 hours. with META_MODE and CCACHE it takes significantly less with consequent builds. unless llvm bumped or/and FreeBSD version bumped then buildworld is being rebuilt again fully. ( but with CCACHE again it is much faster. 17:24:33 more cores = faster builds as usual. there is no definite time for it. 17:24:56 angry_vincent: ah fuck me 17:25:12 T480 is probably 2-3 times faster than my laptop 17:25:18 so I should expect around 12 hours 17:25:31 it is not like that 17:25:34 maybe I should look into building on a build server and moving it over 17:25:36 angry_vincent: I know :P 17:25:45 it is not linear thing 17:25:56 I am aware 17:26:23 maybe I should have kept a core to use my laptop while it compiles :P 17:26:31 mehh scheduler should sort it out 17:27:50 wonder if I could tarball the obj and then move it over :P 17:28:01 then I can buildworld on a more powerful device 17:28:04 yes, you can 17:28:13 as well as share it over NFS 18:23:16 angry_vincent: link to docs? 18:23:32 oh you mean yes I can just tarball obj and copy it :P 18:32:37 dvl: the question is right, I was also curious if such a scenario is doable, please let us know if you will find the soltion 18:59:47 mzar: The multiple zroot boot problem? https://dan.langille.org/2025/12/02/how-to-recover-when-booting-to-multiple-zroots/ 19:00:18 yes, this one 19:05:35 Hmm looks like the WiFi driver is crashing 19:29:02 JetpackJackson: which driver 19:31:28 Uh 19:31:35 One of the rtw 19:32:31 ah realtek 19:32:34 cant help ya 19:32:40 Ah 19:32:49 #freebsd-wifi on efnet might be able to though 19:33:03 or submitting a bug to bugzilla 19:33:46 How come the channels are on two different networks? Historical reasons? 19:35:03 freebsd is a fan of efnet lol 19:35:06 idk 19:35:13 the docs channel is there too 19:39:25 Ah ok 19:39:46 How can I check my specific WiFi chip before I go yap in another IRC channel lol 19:47:19 Oh fun I rebooted and it can't find the kernel 19:47:26 I think I botched my pkgbasify 19:47:36 At least this is a test laptop 19:51:56 Hmm can't tether 19:51:58 Shucks 19:56:53 JetpackJackson, I'd "grep rtw /var/run/dmesg.boot". 19:57:40 Moot at this point cause I can't access the system 19:59:05 Time to boot into an installer image and use the live option? 19:59:11 Oh true 19:59:18 Was gonna just reinstall 19:59:19 Yep. Should be a quick, easy recovery. 19:59:31 God I hope 20:00:47 Hmm 20:00:53 Lemme try a different usb 20:01:02 https://share.katzenmue.de:9270/file_share/0692f457-97bc-7500-bc47-a727328cd847/20251202_150042.jpg 20:01:15 JetpackJackson: You should be able to recovery from that even without a live boot. Just using single-user mode. 20:01:33 Boot the old kernel and make your changes and try again. 20:02:34 OK booting, a bunch of modules say mismatch in multi user 20:02:35 Assuming the loader can find the old kernel. That's not clear from the report. 20:02:42 Single user can't find kernel 20:03:03 Wait now both can't find kernel 20:03:31 Wait I had to press 6 a couple times 20:03:34 One sec 20:04:00 Can't log in. Lemme try again 20:04:26 https://share.katzenmue.de:9270/file_share/0692f464-1b38-728c-b26a-c32176e14b5a/20251202_150410.jpg 20:04:38 OK I'm here. What next 20:05:42 JetpackJackson: Mount your FS and make your changes. 20:06:00 What changes do I make to get it to see the kernel 20:06:17 .eou 20:06:19 Also I can't WiFi tether so I can't do anything that needs internet 20:07:22 JetpackJackson: Are you using bectl to create snapshots? 20:07:30 Well, are you making any snapshots at all? 20:07:49 No... But Theres nothing Important on here 20:08:13 Its just for testing 20:08:36 Maybe I shouldn't have used pkgbasify since I managed to mess up somehow 20:08:47 :( mad at myself for being a dumbdumb 20:09:00 "can't see the kernel" -> that's a little concerning 20:09:31 Should I boot a live ISO and try to fix things thru there? 20:09:38 you can still fix things from single-user 20:09:57 define 'cannot find the kernel' -- loader fails to load it entirely? 20:10:07 is it trying to load a `kernel` kernel, or? 20:10:10 Yeah 20:10:13 Kernel kernel 20:10:26 (I thought I had fixed it to not propose `kernel` if it didn't exist, unless you have a custom `kernels` setting in loader.conf) 20:11:49 I did something dumb on my end dont worry 20:11:59 Youre fine 20:12:02 well, probably not, but 20:12:19 I'm in the live system iso 20:12:24 What should I do next 20:12:35 unfortunately I have to run, but for now you could set `kernel="kernel.GENERIC"` in loader.conf to at least get loader doing the right thing out of the box 20:12:41 To fix my messed up 15+pkgbasify mess 20:12:43 Ok 20:12:55 as for the wifi driver, hmm 20:13:12 you probably want to use devmatch blacklisting to avoid loading it, but you have to grab the name first 20:13:24 I'm not worried about that now. Wanna fix the whole not booting thing 20:15:08 OK mounted drive in live system to mnt and chrooted in 20:15:24 How do I fix the kernel 20:16:09 /boot/kernel is empty 20:16:39 /boot/kernel.old/ has a bunch of stuff 20:18:10 did you look in /boot/loader.conf? and set the thing as suggested above? 20:18:46 OK now I did 20:19:06 https://share.katzenmue.de:9270/file_share/0692f49b-1f88-7178-b7c7-b645e2f8fb3f/20251202_151852.jpg 20:19:47 https://share.katzenmue.de:9270/file_share/0692f49d-d0b5-75e8-958e-f3da92f51b60/20251202_151935.jpg 20:23:49 JetpackJackson: Check out https://docs.freebsd.org/en/books/handbook/boot/ 20:24:14 Specifically, the "15.2.3. Stage Three" section. 20:24:41 Should give you an idea of what to look for as far as unloading any current kernel and booting an old (or different kernel). 20:26:16 I'm also quite sure pkgbasify does create a snapshot (if you're using ZFS). Which you should be able to put right back into place and reboot to the old snapper. 20:26:34 I'm.not using zfs but I should have 20:27:09 I think I accidentally Ctrl c'd at some point. I shouldn't have even asked in here cause its my fault 20:27:18 I would certainly suggest ZFS. It's quite handy. 20:27:38 I wanna fix it but I can't convert ufs to zfs and I dont wanna give up and reinstall 20:27:59 Cause I should fix it instead of giving up 20:28:20 When you boot into single-user mode, can you not "unload /boot/kernel" and then "load /boot/kernel.old" and then "boot"? 20:29:05 Well, I suppose that'll depend on kernel names. But, I'd guess you understand the gist of it. It should be simple if you have the kernel names. 20:29:50 OK booting old kernel 20:29:53 In single user 20:30:22 How do I fix the kernel now so that things go back to how they were 20:32:02 Just (re)move /boot/kernel and copy /boot/kernel.old to /boot/kernel. 20:32:30 that's proven to work 20:32:44 Again, I'd suggest ZFS in the future. :) 20:32:59 Yeah it was just a test 20:33:10 I agree. ZFS is worth it. 20:33:18 ZFS is better, but TBH we have not official way of downgrading kernel 20:33:19 OK rebooting and getting module errors 20:33:38 Live and learn! Good decisions come from learning from mistakes. Mistakes come from bad decisions. There's nothing wrong with learning. 20:33:48 Um ok I can't log in 20:34:58 JetpackJackson: Might need to edit /boot/loader.conf to not load modules that aren't built for the current (old) kernel. 20:35:41 yes, we always realn from mistakes, that's righ and efficient method 20:35:46 You can still boot single-user and boot kernel.old (provided you just copied it to /boot/kernel). Actually, you can likely just boot single-user and boot the current kernel and make your changes to the modules. 20:36:12 remove the spurious module 20:36:39 it's also proven to work, 100% reliable duct tape fix 20:37:06 does it bring panic ? 20:37:32 Its a bunch of modules 20:37:40 that's odd 20:37:45 But j can't log in.what module would do that 20:37:58 I botched my pkgbasify thats how 20:39:07 I'm trying to not let this get me into a bad mood but its hard 20:39:25 I kinda wanna reinstall with zfs and figure out snapshots 20:39:45 This is why I backup my files before any big update... 20:39:51 your mood is important, please take it easy, it's only OS 20:39:59