00:44:08 <polarian> hmmm
00:44:23 <polarian> I have serial working via a com port on the motherboard now
00:44:28 <polarian> getty works on /dev/ttyu0
00:44:38 <polarian> now trying to get this to work with loader I am struggling with
00:45:05 <polarian> https://bpa.st/KGXA
00:45:08 <polarian> thats what I got so far
00:45:11 <polarian> nothing shows up until getty
00:45:20 <polarian> I wonder if its due to the wrong port address, lemme check what the manual says
01:07:47 <polarian> uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
01:07:54 <polarian> from dmesg
01:08:05 <polarian> maybe its because im bios booting!?!?
01:08:26 <polarian> loader.efi shows:            COM1                0x3f8                   /dev/uart0
01:08:33 <polarian> and the addresses match up fine
01:10:24 <rdr> is there an easy way to go from 15.0p10 to 15.1?
01:11:01 <rdr> pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 update -f -r FreeBSD-base
01:11:15 <rdr> is what gemini says, is that a reasonable first step?
01:15:26 <polarian> https://http.icebound.dev:443/httpfileupload/CXKNoxkD2ODjJ2Z3ZWdwnaVYw2U/0a380969-f476-4e91-addb-cf2ebac51403.png
01:15:28 <polarian> alright progress
01:15:30 <polarian> I think this is stage 2
01:15:44 <polarian> terminal is working in stage 2 and stage 3 (I assume)
01:15:53 <polarian> I cant decrypt geli via terminal though
01:19:11 <kevans> polarian: right, geli prompt happens before... there's a way to salvage this, though
01:19:14 <kevans> one second
01:19:27 <polarian> wait this isnt even possible?
01:19:51 <kevans> it's your root fs that's encrypted, right?
01:19:57 <polarian> yes
01:20:12 <kevans> yeah, so your loader.conf that describes the serial port settings is in there
01:20:15 <polarian> if you are going to send me the rootfs within a rootfs thingy thats not what I want
01:20:35 <polarian> so theres no way for geli to be done via serial?
01:20:36 <kevans> but there's a way to specify some config vars on the ESP instead
01:20:49 <polarian> the boot.config?
01:20:59 <kevans> /efi/freebsd/loader.env
01:21:27 <kevans> you can't do module_load type stuff there, but you should be able to set the console esettings
01:21:34 <kevans> er, /boot.config for bios boot, yes
01:21:42 <polarian> im bios booting
01:21:46 <polarian> wait wtf am I meant to stick in there?
01:21:58 <polarian> -Dh -S115200
01:22:00 <polarian> this?
01:23:07 <kevans> this parser is... fun
01:23:19 <kevans> -S115200 at the very least, yes
01:24:05 <polarian> -Dh is serial and internal console
01:24:11 <polarian> and -S115200 is probably redundant
01:25:05 <kevans> boot2 and later seem to default to 115200, yes
01:25:07 <polarian> welp added it to /boot.config
01:25:19 <polarian> lemme see if this does anything
01:25:41 <polarian> the joys of a multi-stage loader
01:25:56 <polarian> yeah err... nothing
01:26:02 <polarian> blank serial console
01:26:13 <polarian> I wonder what happens if I send the password via it though
01:26:20 <kevans> you're killing my buzz here. one second
01:26:22 <kevans> :-p
01:26:46 <polarian> I have to leave for a conf in 1.5 hrs
01:26:48 <polarian> lol
01:26:54 <polarian> oh shit I really should pack and get ready
01:27:01 <polarian> I so want this to work before I go though
01:28:08 <polarian> well the boot.config did one thing
01:28:21 <polarian> 5. Cons: Video
01:28:25 <polarian> says serial and video
01:28:32 <polarian> so it did something on level 2
01:28:36 <polarian> stage 2
01:29:14 <kevans> I think you might just want -P in /boot.config?
01:30:13 <polarian> will try
01:30:48 <polarian> moment of truth :p
01:31:09 <kevans> oh, hmm. that should do the same as -Dh, I guess, it just also probes for a keyboard(?) so that it cn tell you if one is there
01:31:17 <polarian> nah no dice
01:31:38 <polarian> ugh so infuriating
01:31:41 <polarian> so close but so far...
01:33:32 <kevans> oh, heh, where is /boot.config?
01:36:58 <polarian> ifk
01:37:07 <polarian> https://docs.freebsd.org/en/books/handbook/serialcomms/
01:37:09 <polarian> idfk*
01:37:23 <polarian> > When FreeBSD starts, the boot blocks echo the contents of /boot.config to the console. For example:
01:37:27 <kevans> generally the rootfs for bios boots, so on the other side of encryption
01:37:53 <kevans> there's no equivalent to the ESP and nowhere better that we can set boot args, I think
01:39:13 <polarian> > Create boot.config in the root directory of the a partition on the boot drive.
01:39:33 <polarian> wtf is the a partition
01:39:35 <polarian> lol
01:40:11 <polarian> > This file instructs the boot block code how to boot the system. In order to activate the serial console, one or more of the following options are needed. When using multiple options, include them all on the same line:
01:40:22 <polarian> well seems like I need to figure out where I am meant to stick this mysterious file
01:40:44 <polarian> on that note I shall return in 10-20 mins :p
01:40:58 <kevans> you only get 4(?) partitions in mbr, so historically you use a bsdlabel slice and the 'a' partition of that is ufs
02:10:41 <polarian> kevans: ah right disklabels
02:10:52 <polarian> I knew this idk why it slipped out of my brain
02:17:19 <polarian> well I dont know how this would work for zfs
02:17:21 <polarian> im stumped
02:17:56 <polarian> just gonna have to return to this on Monday when I am back from cybersec conf
03:42:58 <entrop> hmmm, should pfctl -t blocklistd -sr show me all of the blocks currently in place?
03:46:36 <entrop> hmm, probably pfctl -a blocklistd -sr (but i still don't get anything)
03:48:12 <entrop> pfctl -a blocklistd/22 -t port22 -T show
05:19:48 <rafe> Hmm, I'm having some issues as a result of D56390
05:20:22 <rafe> my jails can no longer modify their pf rules for their wireguard interfaces
05:20:44 <rafe> Only workaround is to reduce the jail's securelevel, which is not ideal
09:31:24 <polarian> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204969
09:31:26 <polarian> hmmm
11:24:11 <kerneldove> within a jail we can't run freebsd-update fetch install?
11:28:12 <kerneldove> i ran sudo freebsd-update fetch from within my jails and that ran, but the followup sudo freebsd-update install failed with operation not permitted. did i mess it up?
11:51:39 <n30> this is from my rc.conf https://pastebin.com/eAnMrc5c is there any wrong with this? because it wont set main ip address and ipv6 route since i upgraded to 15.1 alias ip except alias0 is configured
11:53:41 <n30> its on boot it wont do it...
11:53:53 <n30> i can enter it manually over ILO
11:56:57 <dnp1> n30: Just curious, any errors in dmesg or /var/log/messages
11:57:56 <n30> dnp1: nope not what i have found ... that would give me some direction to troubleshoot :(
12:21:15 <dnp1> n30: Looks like you might be able to get some debug with rc_debug="YES"
13:40:52 <darkling> I've just installed FreeBSD for the first time, and my first problem is that I'm having trouble getting a (wired) network up.
13:41:00 <darkling> I installed with the "mini" installer, so it managed to use the network for that, via DHCP.
13:41:08 <darkling> Now I'm out of the installer, dhclient is just sitting there firing off DHCPDISCOVER packets and not receiving any offers.
13:41:26 <darkling> However, I can see a (short, ~30s) lease for the machine cropping up in my DHCP server when dhclient does that. The machine isn't getting (or recognising) those packets.
13:41:52 <darkling> I've tried manually setting properties with "ifconfig re0 inet 10.0.0.36/24 up", and can see that setting in the output of ifconfig, but I still can't ping the LAN.
13:41:59 <darkling> Any suggestions on where to look next?
13:42:36 <darkling> (I'm a 30-year user of Linux, so I'm happy with a lot of the concepts, but it's been a long time since I had to debug a network setup at this sort of level)
13:46:12 <dnp1> Odd that it worked during install, but not after.
13:46:46 <glenny2> darkling: when you did the network setup during install, did you let the installer autoconfigure the network setup or did you manually do it?
13:46:51 <darkling> Yeah, I thought that.
13:46:58 <darkling> glenny2: Autoconfigure.
13:47:17 <darkling> Although I had to supply the DNS server address(es) myself.
13:48:57 <glenny2> darkling: I had network issues as well doing auto configure.  The only way to fix it was to reinstall and manually configure the network setup instead.  I also had to avoid doing anything with ipv6
13:49:26 <darkling> No IPv6? Ouch. :(
13:50:55 <darkling> Well, I'll try the install again and see where I get to.
13:52:28 <glenny2> It was weird.  Wifi kept auto connecting to some network i never configured it for and it kept ignoring any changes made in wpa_supplicant.conf
13:53:13 <glenny2> Thing is everything worked fine during install.
13:53:32 <darkling> This machine is a tower desktop, so there's no wireless at all.
13:54:35 <boru> All of these issues sound very bizarre. What's in your rc.conf and netstat -r?
13:55:12 <boru> Should just be set and forget in the installer. Did you set up ipfw/pf or anything?
13:56:23 <darkling> Too late, I just wiped the drive and started again. But I didn't set up *anything* yet.
13:58:16 <boru> Did you verify the checksum of the image? And then after writing it to whatever medium you used to boot from?
13:58:49 <darkling> I verified after download, but not after writing to the USB stick.
13:59:22 <boru> Worth ruling out stuck bits in the flash. Especially if it's NAND.
13:59:32 <glenny2> darkling: did you do the USB image or just burn the regular iso to the USB?
14:00:17 <darkling> USB image: FreeBSD-15.1-RELEASE-amd64-mini-memstick.img
14:07:28 <glenny2> darkling: that's what I did as well.  Huh.  Maybe something is up with network autoconfig and that image?
14:09:26 <darkling> I've compared the USB stick and the image (with cmp -n 678842880 Downloads/FreeBSD-15.1-RELEASE-amd64-mini-memstick.img /dev/sda) and they're the same.
14:10:05 <darkling> (Running sha512sum /dev/sda wouldn't give the same result, because it's bigger than the image)
14:13:47 <boru> That rules out that, then.
14:14:22 <boru> Then it's back to the routes above.
14:15:28 <darkling> I just set up manually in the installer, and did a ping, and I got one packet back from 22 sent.
14:15:47 <darkling> So this might be hardware? But if it's that bad, why did the first install succeed?
14:16:55 <boru> What are you pinging? Your gateway? Something else on the LAN?
14:17:22 <darkling> I'm pinging another machine on the LAN.
14:18:20 <darkling> re0 has "inet 10.0.0.36 netmask 0xffffff00 broadcast 10.0.0.255", and I'm pinging 10.0.0.17
14:19:42 <boru> Can you tcpdump on the other machine and see what it's receiving from that host, if anything at all?
14:20:10 <boru> Or download mtr-nox11 on another machine, transfer it to the problem machine and install it, and them mtr the other machine on the LAN.
14:22:28 <boru> Still though, odd that it works fine during installation, and then fails thereafter. Haven't seen that before.
14:22:39 <darkling> It's having trouble in installation now, too.
14:23:16 <darkling>  
14:23:24 <boru> Tried another cable/port?
14:23:40 <darkling> Yes.
14:23:57 <boru> Is this Ethernet all the way to your gateway? Is it going over MoCa or anything like that?
14:24:30 <boru> What does netstat -r say?
14:24:31 <darkling> Bog standard 1G ethernet all the way.
14:26:33 <darkling> Now the machine's not booting at all. I think it is, like me, too hot.
14:27:10 <boru> Sounds like there's something up with this hardware.
14:28:15 <boru> Might be worth running memtest86 on it in case the RAM is dying.
14:28:21 <darkling> The hardware had been running perfectly well for well over 5 years, so it's got a good history. Granted, something might have gone pop in the last year or so while it's been off, but it seems unlikely.
14:29:02 <boru> Its history is irrelevant here. Hardware can fail.
14:29:28 <boru> If it's not POST'ing, I'd start with memtest86.
14:30:20 <darkling> If it's not POSTing, I can't run anything at all. :)
14:30:37 <boru> > Now the machine's not booting at all
14:30:56 <boru> What does this mean? It POSTs and doesn't boot FreeBSD?
14:31:13 <darkling> I mean I hit the power button and all I get is a black screen.
14:32:34 <boru> Then it sounds like hardware failure or a BIOS problem. If you have a multimeter, might be worth checking the PSU, as well.
14:32:39 <darkling> And 5 minutes later, it's now starting the install from the USB stick.
14:32:44 <darkling> So I think it's just the heat.
14:57:35 <dnp1> If things are running too hot, you are going to continue having odd issues.
15:09:53 <darkling> I've got another machine that I could use, with better cooling, so I might try that in a few days' time.
15:24:58 <MelanieUrsidino> Speed up the fans if ou can.
15:29:13 <darkling> More likely on that machine, it just needs the dust in the heatsink blowing out. I just don't have a compressed-air can right now.
15:30:18 <CuriosTiger> darkling: If you have that need more than occassionally, a static-safe vacuum is a wonderful tool. So is an air compressor. The latter is probably not static-safe, but I haven't had a problem. :P
15:33:19 <kerneldove> within a jail we can't run freebsd-update fetch install it seems. can we run freebsd-update -j <jail> fetch install on multiple jails at the same time if they have different base paths?
16:18:27 <pertho> Anyone here set up mysql in a jail with a /var/db/mysql ZFS data set with recordsize=16K? If so, do you tweak mysql to use skip-innodb_doublewrite and other options?
22:03:54 <dacav> clear
22:04:56 <ant-x> msg Nickserv identiry ant-x al;dkfjaldksfja
22:08:25 <Gedge> ant-x: oops
22:08:43 <ant-x> Gedge, I was kidding decav.