06:04:06 <V-T60> Hello
06:04:13 <V-T60> Why would my internal microphone work?
06:04:24 <V-T60> i try rec -d test.wav
06:04:37 <V-T60> and there are silence
06:07:59 <V-T60> are those such that can be chosen?  devices: vol, pcm, speaker, mic, rec, ogain
06:08:15 <V-T60> for example i try # mixer =rec ogain
06:08:31 <V-T60> mixer: unknown recording device: ogain
06:08:44 <V-T60> for none of them it worked
06:09:44 <V-T60> but how is that possible that a while ago it was  rec devices: monitor
06:10:56 <V-T60> okay, that was with -f /dev/mixer1, but anyway, can't choose anything there
06:11:32 <V-T60> what is the difference between -f /dev/mixer0 and -f /dev/mixer1?
06:14:35 <V-T60> i found the output from /dev/sndstat
06:15:19 <V-T60> it says that i have pcm0 and pcm1, pcm0: <Conexant CX20561 (Hermosa) (Analog 2.0+HP/2.0)> (play/rec) default
06:15:25 <V-T60> pcm1: <Conexant CX20561 (Hermosa) (Internal Analog Mic)> (rec)
06:15:39 <V-T60> how is that chosen which one recording capability is being used?
06:38:26 <V-T60> how can i choose in SoX which device is used to record audio?
06:51:44 <meena> markmcb: add require statements as needed in services (you may have to do this after every upgrade…). jails ordering works differently. it depends on how you're managing jails
10:53:28 <BraveheartBSD> I'm running FreeBSD 14.0-BETA2. What is the bug report procedure? I tried to follow it, just got lost and went in circles.
10:56:49 <otis> you open bugs.freebsd.org and there you go. what was the problem with bugzilla you've ran into??
10:58:21 <BraveheartBSD> I don't think there is, I've never had to report an issue before.
11:00:25 <otis> ah ok
11:00:49 <otis> https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Base%20System
11:00:51 <VimDiesel> Title: Log in to FreeBSD Bugzilla
11:02:18 <BraveheartBSD> Yeah, I'm in there, searching now.
11:04:49 <BraveheartBSD> FreeBSD 14.0 USB goes into a connect/disconnect loop, seems to go away once dbus is started (sddm)
11:10:52 <BraveheartBSD> I'll sign up and go through the process ....thanks
12:04:41 <KingShark> Hi. This compile times are to much for me :)) Is it possible to reinstall the software on my freebsd system pkg based? system pkg based?
12:05:09 <RhodiumToad> what are you compiling?
12:05:16 <RhodiumToad> base system, or ports?
12:05:26 <KingShark> Ports.. everything pulls in another llvm version and then it takes hours
12:05:40 <RhodiumToad> by all means install packages instead then
12:06:03 <KingShark> Ikr.. but i am not supposed to mix them and installed a bunch using portmaster already.. Could i reinstallthose using pkg?
12:06:13 <RhodiumToad> you shouldn't really need
12:06:15 <RhodiumToad> to
12:06:38 <RhodiumToad> the "not supposed to mix them" isn't that important
12:07:42 <RhodiumToad> the main problem with mixing them is the fact that the pkg repo lags behind the ports tree due to the time taken to build things, and the fact that it'll try and upgrade packages that you built with customized options, replacing them with defaults
12:08:14 <RhodiumToad> if you didn't tweak the options, the packages you build locally are no different from the ones in the repo
12:08:46 <KingShark> I add pulseaudio support on some but after the 10th dialog i justhold enter because i dont care much anyways :)
12:09:15 <KingShark> Sort of defeats the purpose of freebsd as well
12:09:19 <KingShark> Might just not be for me :D
12:09:39 <RhodiumToad> it doesn't defeat any "purpose of freebsd"
12:09:54 <RhodiumToad> the fact that you _can_ compile everything yourself doesn't mean you're required to
12:13:38 <dstolfa> KingShark: look into poudriere. it allows you to build your own local package repository for the ports you modify and have them take priority over upstream packages, but then use upstream packages for everything else
12:13:50 <dstolfa> it's pretty flexible and is the official tool used to build the entire ports tree
12:14:02 <dstolfa> that way you don't mix manually built ports with packages fetched via pkg
12:16:40 <KingShark> thanks :)
14:10:20 <KingShark> Hi. Why would ntpd not synchronize the time? ntdp_enable="YES" is in my /etc/rc.conf and a manual update via ntpdate would work
14:10:44 <RhodiumToad> ntpd_enable?
14:10:52 <RhodiumToad> also ntpd_sync_on_start="YES"
14:11:10 <KingShark> if i run service ntpd start now, should it do a sync?
14:11:29 <RhodiumToad> if ntpd_sync_on_start="YES" is set in rc.conf, yes
14:12:26 <KingShark> thanks seems to work :) time is up to date
14:18:13 <RhodiumToad> ntpd_sync_on_start is required if the clock might not be very close to correct on startup; it allows ntpd's first clock adjustment to exceed the normal step limits
15:06:04 <KingShark> Hi. Something i dont understand: I moved my /usr/home mountpoint to a second zfs pool on another disk. Yet when i check in Thunar, it shows the freespace of the first pool in that directory. Also when i do df -h, it does not show this mountpoint at all. zfs list shows it fine and correct though.
15:07:15 <RhodiumToad> what does zfs list show exactly?
15:07:26 <RhodiumToad> it sounds like you didn't actually mount it from the new pool
15:09:42 <KingShark> here a paste https://bsd.to/DDxK
15:09:43 <VimDiesel> Title: dpaste/DDxK (Plain Text)
15:09:57 <KingShark> zroot is pool#1 and data pool#2
15:10:04 <KingShark> i want /usr/home on pool#2 data :)
15:10:55 <RhodiumToad> so it's not mounted, and the /usr/home you're seeing is the one on zroot
15:13:42 <torindel> hey guys, i installed 14.0-BETA2 to check it out, and there is no portsnap anymore, any ideas how to get fresh ports? (and i didnt bother to get ports at install time as i inteded to use portsnap)
15:14:58 <RhodiumToad> KingShark: check the properties on the new one? perhaps it has canmount=off ?
15:15:18 <RhodiumToad> torindel: git
15:15:35 <torindel> RhodiumToad: git isnt in base either
15:16:32 <torindel> RhodiumToad: any tool to get fresh ports before installing anything via pkg?
15:17:01 <KingShark> RhodiumToad, i now did 'zfs set canmount=on data' and another 'zfs set mountpoint=/usr/home data' and tried to confirm via mount -a; mount but its not showing
15:18:01 <KingShark> 'zfs mount'  not showing it either
15:18:34 <KingShark> maybe the current /usr/home just resides in the /usr mount as a regular folder and blocks the mount?
15:18:44 <torindel> or other question: will portsnap be back in 14.0-RELEASE or is it deprecated?
15:20:31 <RhodiumToad> torindel: afaik it's deprecated
15:29:17 <KingShark> RhodiumToad, 'zfs mount -a'  did the trick lol
15:29:27 <KingShark> How do i make it persistent?
15:30:34 <RhodiumToad> zfs mount -a is run automatically at boot
15:31:01 <RhodiumToad> as long as the properties don't disable it from being mounted, it'll mount at boot
15:31:25 <torindel> KingShark: ensure you got zfs_enable="YES" in /etc/rc.conf and as RhodiumToad said you should be fine
15:32:49 <KingShark> doublechecked, is in rc.conf.. Well. Weird. I did not change much, i set the canmount=on for it (i dont know if it was on before).
15:33:06 <KingShark> seems to work fine now, i unmounted it again,  re-mounted it and copied the files over
15:33:14 <KingShark> Will reboot for a try :)
15:34:59 <KingShark> reboot done; all good
15:35:51 <dstolfa> torindel: portsnap is deprecated, maybe you can fetch(1)? freebsd really needs a tool in base to fetch stuff from git
15:37:26 <torindel> side note: ftp://ftp.freebsd.org/pub/FreeBSD/development/tarballs/ports_main.tar.xz <= how often ports tarball is updated? daily hopefully? or quaterly like older ones?
15:38:28 <RhodiumToad> look at the file dates?
15:38:59 <torindel> same date as ports_2023Q3.tar.xz
15:39:07 <torindel> thats why im asking ;]
15:39:18 <torindel> (and thats today)
15:42:36 <RhodiumToad> the quarterly branch isn't fixed for the whole quarter, it's just updated less than the main one
15:43:36 <torindel> oh ok, thx
17:21:51 <yuripv> torindel: if nothing else works :) https://github.com/freebsd/freebsd-ports/, "code" -> "download zip"
17:33:57 <KingShark> Hi. Is it possible to reduce the screen resolution for tty terminals (ctrl+f1-f8) while keeping the xorg ttv9 untouched? :)
17:34:34 <KingShark> I like the size it has before starting xorg
17:35:04 <KingShark> Or loading the nvidia drivers, i guess thats actually changing the resolution :D
17:40:38 <psionic> Wen will FreeBSD 14 come out
17:40:52 <psionic>  WEN�
17:40:52 <psionic>  WEN��
17:40:53 <psionic>  WEN��
17:40:53 <psionic>   WEN�
17:41:21 <psionic> I hope next week otherwise I install OpenBSD 7.3
17:41:22 <KingShark> vidcontrol -f terminus-b32 seems to work to achieve sort of what i wanted.. making the font bigger instead of the resolution smaller :D
17:42:24 <KingShark> psionic, i see dates up to late october in this https://www.freebsd.org/releases/14.0R/schedule/ . others will know better x)
17:42:25 <VimDiesel> Title: FreeBSD 14.0 Release Process | The FreeBSD Project
17:47:28 <yuripv> psionic: you can install beta and then update it to release when it's out, don't expect to be a lot of changes in there
17:49:54 <psionic> is it having the same issue as netbsd? That after install when you use it for a while and they make a new release it keeps crying that the binary packages were compiled to version xyz, I really don't like that.
17:51:25 <yuripv> it starts crying when the release you are running is EOL
18:06:48 <signalblue> psionic: try out netbsd
18:06:55 <signalblue> we're waiting for netbsd 10 noe
18:06:56 <signalblue> now
18:07:00 <signalblue> from 9.3
18:11:23 <meena> I mean, you can always run NetBSD CURRENT if you don't wanna wait
18:18:59 <signalblue> meena: that *may* have stability issues and I wanted to deploy it on a server :)
18:22:37 * meena usually runs RELEASE or STABLE on servers
18:23:39 <signalblue> meena: NetBSD RELEASE?
18:23:57 <meena> signalblue: FreeBSD.
18:24:02 <signalblue> ah
18:24:09 <signalblue> I usually only run RELeASE
18:24:14 <signalblue> RELEASE sorry
18:24:24 <meena> I'm in too deep in FreeBSD, and not nearly as deep in other BSD
18:24:41 <signalblue> RELEASE is the stablest one
18:24:56 <signalblue> are you deep in Linux/Debian?
18:25:16 <meena> nope. not for a long time by now
18:25:17 <signalblue> FreeBSD is a nice change of pace from that
18:25:37 <meena> I find Linux confusing when looking for source
18:25:52 <meena> (imagine my confusion then, when working on windows)
18:25:52 <signalblue> me too
18:26:01 <signalblue> looking for source?
18:26:05 <signalblue> like as in source code?
18:26:43 <meena> yes
18:26:45 <signalblue> there's also this - nomadbsd.org - never knew of it until now
18:27:19 <meena> having the entire base in one place is really useful
18:27:26 <signalblue> ^^^
18:27:57 <LxGHTNxNG> Unix stuff makes me dizzy. Windows is worse.
18:29:13 <meena> anyway, time to do dishes, then sit down an stare at some documentation, and attempt to write another function for a kernel driver before my brain goes bzzzzzzt
18:31:14 <meena> actually, I just got an idea. I'm gonna turn that driver into boilerplate and debugger code, and see what the client code does.
18:31:30 <meena> gosh, imagine if i had that idea 3 months ago
18:31:44 <meena> I might be half finished by now
18:41:07 <meena> put differently: imagine if I had a brain, or mentorship? I could be… at least mediocre.
18:42:21 <psionic> Can it run the latest Arduino ide 2.x and sketchup?
18:44:37 <meena> psionic: https://www.freshports.org/search.php?query=Arduino%20&search=go&num=500&stype=name&method=match&deleted=excludedeleted&start=1&casesensitivity=caseinsensitive i only see 1.x
19:32:18 <psionic> How is the VirtualBox support is it somewhat degraded compared to linux?
19:32:33 <psionic> Can I for example install a linux in vbox and use that for arduino programming
19:32:45 <psionic> as I recall there was some usb support issue with fbsd
19:43:28 <psionic> VirtualBox� can be configured to pass USB devices through to the guest operating system. The host controller of the OSE version is limited to emulating USB 1.1 devices until the extension pack supporting USB 2.0 and 3.0 devices becomes available on FreeBSD.
19:43:33 <psionic> VirtualBox� can be configured to pass USB devices through to the guest operating system. The host controller of the OSE version is limited to emulating USB 1.1 devices until the extension pack supporting USB 2.0 and 3.0 devices becomes available on FreeBSD.
19:43:52 <psionic> still?
19:47:05 <rogersm> Oracle Cloud FreeBSD successfully upgraded! yey!
19:52:05 <meena> psionic: you could use bhyve and pass through an USB… thing
20:25:05 <markmcb> I may have done a bad thing. I upgraded my zfs pools on beta2 and now I can't even get to the loader on boot. First message is: ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2. Not sure if that's actually an error. Later I see ERROR: cannot open /boot/lua/loader.lua: no such file or directory. Not sure what to do.
20:28:00 <yuripv> markmcb: now you need to update the loader, using efi?
20:28:05 <VVD> markmcb, u need to update boot loader
20:28:19 <markmcb> yes, using efi
20:28:56 <yuripv> boot from 14 iso, mount the esp partition and copy /boot/loader.efi to efi/freebsd/loader.efi on that esp
20:29:31 <markmcb> ok, will give that a shot. thanks!
20:30:21 <yuripv> (note that esp is fat32, use mount_msdosfs)
20:31:53 <markmcb> ok, thanks. and just curious, did i do something wrong? should freebsd-update have done this for me? or is this always a manual step?
20:32:59 <yuripv> don't think freebsd-update does that for you
20:33:55 <yuripv> we now have esp mounted by default in /boot/efi/, still neither installworld nor freebsd-update seem to update the loader
20:34:01 <VVD> freebsd-update doesn't run zpool upgrade and doesn't update loader not in /boot/
20:37:30 <yuripv> zpool(8) really should check if bootfs is set and refuser to continue to upgrade unless --yes-i-really-know-what-im-doing is specified :D
20:37:43 <yuripv> refuse too
20:40:12 <markmcb> i moved loader.efi, but still getting the loader.lua error. copy that too?
20:41:43 <yuripv> moved it where?
20:41:57 <markmcb> efi/freebsd
20:42:08 <markmcb> on the efi partition
20:43:06 <yuripv> may be it's using the default one in efi/boot/bootx64.efi? try to copy /boot/loader.efi to that path as bootx64.efi
20:44:22 <yuripv> (efibootmgr -v would show what entry gets used and the paths)
20:45:36 <markmcb> ok, it is booting now. thanks!!!!
20:45:59 <yuripv> \o/
20:48:51 <markmcb> That was a fun moment of panic. I appreciate the help.
20:52:18 <markmcb> I'm curious, where is that documented? The handbook seems to imply freebsd-update upgrade/install does it all. The updating bootcode section is largely blank.
20:53:24 <markmcb> I see it in loader.efi(8), but seems the handbook should make a bigger callout for it.
21:10:09 <markmcb> not sure what changed, but in 14b2 any time i restart a jail that's using sriov for networking it takes a looooong time for the vf to become available. it effectively breaks "restart" as it simply fails when trying to start again.
21:11:53 <markmcb> seems to take 5-10 minutes on average
21:30:30 <yuripv> markmcb: which nic?
21:31:02 <markmcb> Chelsio T520-SO-CR
21:37:49 <yuripv> and which version worked?
21:51:36 <markmcb> 13.2 would also exhibit delays, but more like 5-30 seconds
21:52:30 <markmcb> seems something is taking even longer to complete and jail restart is unaware of it and considers the stop job complete
21:58:42 <markmcb> fwiw, same behavior from a x710-da2