15:56:47 <khorben> I'm trying to find how to have new entries show up in /dev/gpt after partitioning a new disk with gpart -t GPT
15:57:01 <khorben> any ideas? I looked at gpart, glabel, geom...
15:57:24 <CrtxReavr> khorben, they should just appear if the partitions are on the device.
15:58:21 <khorben> mmh they don't... but thanks I'll keep looking
16:00:01 <yuripv> khorben: did you add the actual labels to partitions?
16:00:09 <isley> isn't that only for labels? you have to add the label. also doesn't update when mounted iirc
16:00:14 <khorben> no I didn't set labels
16:00:24 <yuripv> what isley said, it's for labels
16:01:02 <khorben> the first disk show as gptboot0 swap0 zfs0, I assumed creating freebsd-zfs etc types would show up as gptboot1 etc
16:01:28 <khorben> I can try again
16:01:55 <yuripv> those labels were added by installer
16:02:46 <khorben> ah I see them in gpart list
16:03:11 <yuripv> gpart show -l as well
16:03:14 <khorben> I expected gpart show to look like the output of gpart list, and gpart list to look like gpart show
16:03:36 <khorben> yes that works too
16:03:37 <khorben> thanks!
16:04:43 <khorben> now zpool attach zroot /dev/gpt/zfs0 /dev/gpt/zfs1 works, cool
16:06:58 <KingShark> Hi. Any way to hide hardware devices from pulseaudio? Tried in pavucontrol but it wont allow me to disable devices. Cant block them on a kernel level either (by not loading drivers) because the devices i want and the ones i dont want seem to be the same hardware :/
16:07:13 <khorben> through permissions?
16:08:25 <yuripv> KingShark: why exactly do you want to "hide" it?
16:09:41 <KingShark> yuripv, just some OCD thing about seeing a list of devices that i dont want to see when i want to change output device in the xfce pulseaudio plugin :))
16:10:03 <KingShark> i would prefer this list to show only the exact two that i regulary use xD
16:10:06 <KingShark> i know its silly
16:12:50 <yuripv> makes sense :D
18:01:49 <crb> when using bhyve where/how does one configure the MAC address of the virtual machine?
18:02:13 <crb> never mind I think I found it
18:03:02 <meena> crb: and, how?
18:03:56 <crb> meena, not sure I understand you what did you mean?
18:08:48 <fraxamo> Has the location for EuroBSDCon 2024 been announced yet?
18:12:53 <meena> fraxamo: according to https://bsd.network/@EuroBSDCon "EuroBSDCon 2024 will be held in Dublin, Ireland, September, 2024."
18:22:49 <fraxamo> meena: Excellent, thank you!
20:07:49 <FUZxxl> Updates on my nvidia-driver oddyssey
20:08:04 <FUZxxl> I found a configuration that works now.  There were three isues in total:
20:08:19 <FUZxxl> (a) I couldn't get nvidia-driver without nvidia-drm to work.  nvidia-drm must be used.
20:08:52 <FUZxxl> (b) nvidia-driver copes poorly with being used with legacy mode boot.  EFI boot must be used.
20:09:11 <FUZxxl> (c) nvidia-driver requires swap to wake up succesfully from suspend-to-ram.  Swap must be enabled.
20:12:36 <meena> how did you figure these things out?
20:13:08 <FUZxxl> lots of trial and error
20:13:18 <FUZxxl> and a hunch as to what could be the problem
20:13:45 <FUZxxl> the general intuition is: "what is different between my system and a normal system that could cause the problem?"
20:25:59 <FUZxxl> The most annoying thing about debugging this is that I was unable to find any report of issues online that were even remotely similar.
21:46:11 <dch> meena: expect incoming ;-)
21:46:36 <dch> FUZxxl: I'm using nvidia-drm, would be great if suspend now works. good to know!
21:47:21 <FUZxxl> dch: it does!  Does it work for you?
21:47:34 <dch> I'll try tonight and report back
21:47:42 <dch> need to save a bit of work first just in case
21:47:54 <dch> are you using drm-515-kmod or the other one?
21:47:59 <FUZxxl> the other one
21:48:05 <FUZxxl> drm-515-kmod is for freebsd 14 and newer
21:48:08 <FUZxxl> I'm still on 13.2
21:48:15 <dch> ok, I'm on newer here
21:56:01 <FUZxxl> I'm waiting for the ZFS issue to be resolved before upgrading.
21:59:09 <dch> is there a way (from shell + other userland tools) to tell if random/dir is actually a fs mountpoint?
21:59:18 <dch> other than running mount and parsing output
21:59:27 <FUZxxl> yes
22:00:19 <FUZxxl> [ `statd -f %d $dir` = `stat -f %d $dir/..` ]
22:00:30 <FUZxxl> if this returns true, $dir is not a mountpoint
22:00:41 <FUZxxl> [ `stat -f %d $dir` = `stat -f %d $dir/..` ]
22:01:21 <dch> clever
22:01:51 <FUZxxl> note that this fails if $dir is / or if $dir is not linked (e.g. it has recently been removed but is still accessible through pwd)
22:02:00 <FUZxxl> so you may need to build some hardening around it
22:02:28 <dch> nah this is just throwing in a makefile to make it accommodate being re-run
22:02:41 <FUZxxl> ok
22:02:52 <dch> thats going to be good enough thanks!
22:02:58 <FUZxxl> have fun
22:04:18 <FUZxxl> historically, you would do this by checking if the inode is 2 as that's the root dir of a ufs file system
22:04:27 <FUZxxl> but this no longer holds true with other file systems
22:04:56 <dch> would be nice if test(1) could do this
22:25:45 <meena> it be nice if we had Linux' mountpoint(1)
22:30:47 <FUZxxl> meena: implement the command and submit it as a feature!
22:31:49 <dch> FUZxxl: kernel panic in process, suspend definitely not working here
22:32:09 <FUZxxl> oh noez
22:32:12 <FUZxxl> which gpu do you have?
22:32:19 <FUZxxl> also do you use nvidia-drm?
22:33:12 <dch> yeah its the drm flavour
22:33:22 <dch> geforce 1650 IIRC
22:34:24 <FUZxxl> ok
22:34:29 <FUZxxl> I have an nvidia Quadro M2200
22:34:37 <FUZxxl> laptop GPU on an MXM card
22:57:01 <meena> FUZxxl:  busy with virtio right now