06:41:24 <dch> loving my newly-discovered ryzen hibernation on my desktop pc
06:41:46 <dch> but when it restarts, I can't type umlauts and other european characters accents anymore
06:42:07 <dch> its easy enough to fix, but I don't really understand why these keyboard mappings should disappear
06:42:12 <dch> anybody know why?
06:42:47 <dch> `setxkbmap us -variant altgr-intl -option compose:menu` is what I need to re-run
06:47:49 <[tj]> ryzen hibernation?
06:48:25 <dch> [tj]: the zzz thing
06:48:44 <dch> it used not to work with my nvidia gpu + this mainboard + cpu
06:48:47 <dch> and now it does
06:49:03 <dch> and given how hot it is, I am very happy about this little win
06:49:20 <[tj]> oh you mean suspend to ram
06:49:46 <[tj]> dch: just move into the cellar
06:49:49 <dch> I guess so, is it not the same?
06:50:00 <[tj]> freebsd doesn't have hibernate support
06:50:01 <dch> does hibernation generally mean suspend to disk
06:50:08 <[tj]> yeah
06:50:11 <dch> huh til
06:50:22 <dch> also my cellar, it has a noisy datacentre in it
06:50:24 <[tj]> we did support bios driven acpi hibernation, but no one has shipped a bios with that for a long time
06:50:50 <[tj]> so there could have been some bios thing I'd never heard of
06:50:58 <dch> my replacement mainboard arrives today
06:51:06 <dch> then I really hope my server works again
06:51:14 <dch> and I can do the network fiddling again
06:51:30 <dch> I still haven't listened to the BSDcan power talk yet, its on my list
06:53:17 <[tj]> it doesn't cover this
06:53:21 <[tj]> hibernate is weird
06:53:39 <[tj]> I'm watching people debug linux hibernate in another irc channel and I'm always confused
06:54:07 <[tj]> linux and openbsd hibernate resume is mostly a normal boot
12:06:13 <RDMengineer> Do I need to build ubldr separately somehow?
13:57:46 <kevans> RDMengineer: what do you find yourself needing ubldr for?
14:17:37 <dch> what might stop a box switching from kernel -> userland on boot?
14:18:25 <dch> it hangs at `start_init: trying /sbin/init` but does respond to ctrl/alt/del, but not ctrl-t or ctrl-c tho
14:46:23 <kevans> dch: are you looking at the "wrong" console?
15:19:19 <regis> dch: some kernel/userland mismatch? Also try ctrl+t for SIGINFO. It may show you what's the process it hands on.
15:19:51 <dch> regis: in the interim I booted off usb and added a fresh pkgbase boot env
15:20:14 <regis> dch: But if it's kernel/userland mismatch and the problem is with /etc/ttys or such, ctrl+t likely also won't work.
15:20:15 <dch> I now have a slow process of moving bits & pieces back in hoping it all works
15:20:27 <dch> ctrl-t definitely hosed
15:21:57 <regis> Oh, you mentioned ctrl+t. Sorry.
15:23:48 <regis> dch: Without moving bits and pieces, maybe make installworld and make distribution would work if you're able to build sources fast. Also maybe chroot from USB-booted live system, which won't run init and will have tty stuff from the live system.
15:32:33 <dch> well the boot env all works now, so its a matter of reinstalling packages and shuffling configs over
15:32:40 <dch> oh and fixing the broken ipmi
15:34:05 <dch> on the upside, I am getting a lot of steps in going from cellar -> 3rd floor and back again, repeatedly
15:34:32 <dch> and its almost certainly userland/kernel mismatch, I can see sbin/init starting and crashing
15:36:56 <Tabmow> No updates needed to update system to 14.3-RELEASE-p1 - yet uname -r even after a reboot returns 14.3-RELEASE - is this normal with binary updates?
15:37:31 <dch> Tabmow: yes there is a difference between userland and kernel
15:38:13 <dch> try `freebsd-version -kru` and `uame -a`
15:38:17 <Tabmow> dch: so it's only if the patch contains a kernel update will it get reflected in uname I guess?
15:39:25 <Tabmow> https://dpaste.org/b3qWA
15:40:44 <dch> Tabmow: yeah that looks fine
15:42:16 <dch> Tabmow: the 2 vulns are xz (userland) and openssh (userland)
15:42:27 <dch> so no need to update kernel
22:32:30 <pike> I'm new to compiling. I noticed that FFMpeg has a cool encoder option on their Wiki https://trac.ffmpeg.org/wiki/Encode/AAC, the most HQ aac_at encoder. Now, n00b as I am, I was expecting that this aac_ac was available in FFMpeg graphical configure as an option. Nope. Joy
22:34:47 <ivy> pike: that seems to rely on Audio Toolbox, which only exists on macOS?
22:38:02 <pike> could be, a bit unclear "normally available only on macOS" key is normally :)
23:02:20 <pike> ivy, I guess you are correct. No idea what their wiki means with 'normally' Noone would do this if it was possible to use aac_at with FFmpeg https://www.andrews-corner.org/qaac.html