00:04:16 <SponiX> Anyone wrote a LOT of data to a Linux ZFS array, and then hooked it up to a FreeBSD machine and imported that pool?
00:57:47 <antranigv> I am confused, what am I doing wrong? I get "dtrace: failed to control pid 37689: process exited with status 1" when doing dtrace -l -n 'pid$target:::entry' -c 'myprogram'
00:58:05 <antranigv> SponiX I have yes, why? around 40TB.
02:44:47 <SponiX> antranigv: Is it pretty straight forward? Just make the ZFS Filesystem on Linux, put data on it, export it, and then hook the drives up to the FreeBSD machine and import the pool = Profit?
06:40:03 <wokko> Hey guys, using "TARGET=amd64" in "make buildworld" just build that target?
06:54:36 <la_mettrie> yes, it doesn't build codes specific for other architecures (than amd64) then
06:55:43 <wokko> la_mettrie: cheers mate
07:58:35 <LXGHTNXNG> SponiX: Can you expound? It should Just Work, as long as the feature flags are supported on the Linux in question.
13:37:14 <wokko> How do we rebuild the kernel modules? I have an issue with dmesg saying "It can't load i915kms becos of unsupported file type"
13:41:10 <luser> (cd /usr/src && make -s kernel)
13:42:29 <wokko> luser: cheers, give it a go
13:51:56 <luser> If it still errors you might need to (cd /usr/ports/graphics/drm-kmod && make install clean clean-depends)
15:42:35 <wokko>  
16:13:12 <mzar> wokko: "pkg upgrade -r FreeBSD-kmods" will fix the issue
16:15:27 <mzar> we need this command in topic: "pkg upgrade -r FreeBSD-kmods" will fix i915kms issues after upgrade to 14.3-R
16:19:02 <wokko> mzar: I downloaded to drm-66-kmod in ports and magically fixed the issue :)
16:19:11 <mzar> OK
16:19:50 <thedaemon> is drm-66-kmod working in 14.3?
16:20:23 <wokko> It's for >15
16:20:34 <thedaemon> yeah that's what I thought
16:20:59 <mzar> thedaemon: not supported on older than 1500031, no kernel support
16:21:15 <thedaemon> just still having drm-61 system freezes :(
16:21:45 <wokko> drm-kmod has been working for a long time until today after an upgrade
16:21:49 <mzar> thedaemon: is it amd ?
16:21:54 <thedaemon> amd 6750xt
16:22:11 <mzar> upgrade to 14.3, it's fixed
16:22:19 <thedaemon> I am on 14.3
16:22:20 <thedaemon> :(
16:22:25 <thedaemon> Mine is still not fixed.
16:22:44 <mzar> so you need new pkg
16:23:04 <thedaemon> I understand, I am not a newbie :) I built from updated port just to be safe
16:23:06 <mzar> upgrade: pkg upgrade -r FreeBSD-kmods"
16:24:03 <mzar> thedaemon: OK, so your issue hasn't been fixed, but problem with memory fragmentation on amdgpu is fixed in 14.3
16:24:13 <thedaemon> that's great!
16:24:28 <thedaemon> Do you know if any fixes have happened 61 vs 66 ?
16:25:17 <mzar> I don't know, I am using 66 on old radeon GPU and it just works
16:25:32 <thedaemon> okay :)
16:26:19 <thedaemon> I'm running this version drm-61-kmod 6.1.128.1403000_4
16:26:29 <thedaemon> looks like 1403 means it's built for 14.3
16:26:49 <thedaemon> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274770
16:26:52 <thedaemon> My bug report
16:27:22 <mzar> ha.. old one
16:28:23 <thedaemon> yeah it plagues me
16:40:22 <SponiX> thedaemon: you get your shit together yet?
16:40:47 <thedaemon> haha no
16:41:16 <thedaemon> I keep on falling in and out, of love, with drm.
16:41:28 <SponiX> chances are you just need to pull the latest version of /usr/ports and then go to graphics/drm-61-kmod and build it from source
16:41:33 <SponiX> it should WORK then
16:42:01 <SponiX> I know there is a kmod repo now, but I've yet to use that. So not 100% sure how reliable it is
16:42:09 <thedaemon> SponiX: I did that :P
16:42:21 <thedaemon> it hates my particular gpu I think
16:51:50 <SponiX> I blame Microsoft
17:00:53 <SponiX> thedaemon: did you make sure to have xf86-video-amdgpu installed also?
17:01:05 <SponiX> If not, do that and try again
17:24:19 <thedaemon> but why? lol
17:25:31 <thedaemon> I have navi22
17:28:55 <burie> How do I get route metric. netstat -rn doesn't show it
17:31:32 <burie> ifconfig has it for each interface
18:29:45 <Linkoid01> Hello all, I have a question: does running the Linux Compatibility mode after installing linux_base-c7 use up a lot of resources? I want to be able to use Visual Studio Code to edit files on my FreeBSD server, and cannot do that unless I get this compatibility layer in, however, the machine is not quite a beefy machine. So am worried if this would
18:29:46 <Linkoid01> have a significant impact on RAM.
18:31:33 <ivy> Linkoid01: the only resources used (other than some kernel bookkeeping data) are the resources used by the Linux program(s) that are running.  that includes glibc and any other libraries it needs.  also, i think there's a native version of VS Code in ports
18:34:24 <Linkoid01> I see. I am on a windows machine; I am aware that there is VS Code in ports but it does not help me connect to FreeBSD machines via VS Code
18:35:56 <Linkoid01> would I need to enable the same compatibility mode in each jail that I run in order to get VS Code to work on each jail?
18:43:54 <jmnbtslsQE> burie: `route -n get $route` . ifconfig metric is something else
19:00:10 <antranigv> Linkoid01 I think there's VSCode in ports.
19:00:25 <antranigv> Last Update: 2025-06-14 06:20:19
19:00:41 <antranigv> Linkoid01 you can do `pkg install vscode`
19:00:56 <Linkoid01> I'm on a windows machine, how does VS Code help me in ports?
19:01:17 <Linkoid01> All I want to do is ssh to the machine like a regular linux machine and be able to edit my files that way
19:01:22 <antranigv> Linkoid01 I think I misunderstood your question :-) I thought you wanted VSCode ON FreeBSD.
19:01:34 <Linkoid01> okay, no worries
19:01:43 <antranigv> Ohhh. that's the VSCode SSH Agent thingie, right?
19:02:10 <Linkoid01> yes, Remote - SSH
19:02:19 <Linkoid01> it's a wonderful tool
19:07:39 <ivy> do you know what vscode actually does?  i.e., is it trying to upload and run a Linux executable?
19:09:21 <ek_> Yeah. VSCode is kind of stupid when it comes to remote edits. It checks the remote OS and determines whether or not it's supported.
19:09:25 <ek_> Linkoid01: https://www.gaelanlloyd.com/blog/how-to-connect-visual-studio-code-to-freebsd-servers/
19:10:37 <ivy> maybe sshfs (or whatever the Windows equivalent is) would be an easier solution, or at least less fragile
19:11:07 <ivy> ek: perhaps the new RL9 packages would fix that particular issue
19:11:11 <ek> ivy: It looks like it requires Linux's BASH to run (again, kinda stupid).
19:11:42 <ek> I'd imagine any linux compat would work.
19:12:30 <Linkoid01> yes, I am aware. My first question is: Does running the linux compatibility take up a lot of resources? this is a 16GB memory machine with a very low powered CPU.
19:12:49 <ek> Linkoid01: Nope. You won't even notice it at all.
19:12:50 <Linkoid01> And do I need to enable the same for each jail?
19:13:04 <Linkoid01> Ok, great to hear that ek
19:14:27 <ek> For anything you'd be connecting to with VSCode, it'll need access to that compat bash. So, you can either mount that compat area to each jail, or install the compat on each jail. I'd think the first would be quickest, easiest, and smallest footprint.
19:19:29 <ek> At least, I'd think that should work. I've very rarely used linux_compat and never used VSCode.
19:29:40 <ek> Linkoid01: If you use RL9 linux compat, this looks interesting: https://github.com/morganwdavis/vscode-server-freebsd
20:34:44 <antranigv> hey Linkoid01 , did you find a solution?
22:02:21 <antranigv> I am getting: KLD i915kms.ko: depends on kernel - not available or version mismatch ; any tips?
22:02:27 <antranigv> I'm on 15-CURRENT
22:02:34 <antranigv> and drm-kmod compiled from ports