00:02:35 it was totally because i fat fingered the binary paty 00:02:38 it was totally because i fat fingered the binary path 01:01:14 hi deimosBSD 01:01:20 glad you figured it out :D 01:02:55 it turns out /usr/localbin/binary doesn't work ;) 02:27:50 FreeBSD 15 hardware supported wifi drivers list says that my wlan card is supported by the kernel but when I installed FreeBSD the wifi didn’t work 02:28:11 Realtek 8852BE Wi-Fi 6 (RTL8852BE) Is my wifi card 02:31:02 spaciouskarter78: I dont remember any 802.11ax cards being supported 02:31:24 even if they were supported, 802.11ax isnt within the ieee80211 stack 02:31:37 so it would only be able to use 802.11ac 02:33:27 the latest driver support was iwlwifi but thats intel, and rtwn is only for 802.11n/ac realtek cards 02:36:41 polarian https://www.freebsd.org/releases/15.0R/hardware/#wlan 02:38:24 riceandbeans: wow, as common as sshd is I would think it crashing often for many folks would be something fixed quickly 02:38:39 wow err 02:38:44 they really did LinuxKPI a lot 02:39:07 spaciouskarter78: is there anything under dmesg 02:39:12 did you kldload if_rtw89 02:39:37 it should automatically load 02:39:43 but make sure 02:39:48 and check for any errors within dmesg 02:40:12 polarian should I run the command named “dmesg”? 02:40:16 oh wait I saw it 02:40:18 nvm 02:40:20 its because of missing firmware 02:40:22 As well as kldload? 02:40:24 Oh 02:40:28 How do I fix it? 02:40:32 pkg install net/wifi-firmware-rtw89-kmod 02:40:38 and then reboot 02:40:44 Thanks a lot I’ll try that now and see if it works 02:41:52 running fwget should also fetch it 02:41:59 or so the man page says 02:42:06 but installing the port would definitely work 02:43:59 polarian and for connecting to the wifi on kde what should I use? Networkmgr or wifimgr? 02:44:10 those are Linuxisms 02:44:20 wifi on freebsd is done via wpa_supplicant usually 02:44:29 the freebsd handbook goes over it 02:44:53 personally what I do is "ifconfig wlan0 scan" when you are looking for ssids 02:45:36 then "wpa_passphrase ", then enter the passphrase, and then write it to /etc/wpa_supplicant.conf 02:45:58 then you can "pkill -HUP wpa_supplicant" (as root, use doas/sudo otherwise) and it will reload the config 02:46:12 I think there was a wifi gui being developed for GSOC but I dont know much about it 02:46:28 thats how I do wifi, it works well, but I know it isn't very user friendly 02:46:47 for the most part I avoid wifi though, and just use ethernet 02:47:19 Ssid is the name of the wifi? 02:47:59 Sorry I never interacted with networks at such a low level before 02:48:47 spaciouskarter78: sorry yes ssid is the "wifi name" 02:49:03 someone else might be able to provide a more elegant solution, or KDE settings might be able to handle it for you 02:49:22 I dont use KDE though, I just i3 with xorg, and my setup is very minimalist 02:49:42 so I urge you to try connecting through KDE first, see if its GUI can do it all for you, otherwise what I explained above works but is not user friendly 02:52:29 polarian the wifi card somehow got detected automatically 02:53:01 spaciouskarter78: well considering this is new to 15.0 I dont expect it to be the most stable 02:53:09 I stick to 802.11n cards for that reason 02:53:12 they just work (mostly) 02:53:21 plus I run an old laptop 02:53:55 I ran ifconfig wlan0 scan but it doesn’t return anything 02:57:24 I tried installing the port you mentioned let’s see what happens 02:57:27 Restarting rn 02:59:21 Nope no luck 03:03:50 polarian found the problem 03:04:07 The entire system crashes when I attempt to scan for wifi 03:04:26 I tried ifconfig wlan0 up scan and my pc crashed 03:26:03 spaciouskarter78: by "crash" do you mean a panic? 03:26:24 if you get get the logs I can relay it to the wifi nerds 03:26:25 it freezes up when i run the command and just restarts after making loud beep noises 03:26:39 what logs can i provide? 03:32:45 i just opened a bug report on bugzilla about this: bugs.freebsd.org/bugzilla/show_bug.cgi?id=294429 07:26:33 FreeBSD has handbook for free for quick setup, printed more detailed guides on amazon and even books detailing its internals. This is amazing 11:06:26 yep the documentation is amazing 11:08:11 How's your wifi? 11:12:48 has anyone experienced niri crashing frequently? 11:47:14 joepublic: i just usb tether a s4 mini running lineageos :D 12:43:34 Hi, how can I enable xf86 multimedia keys on freebsd? `xev` recognizes that something is being pressed but doesn't differnetiate between the keys 12:44:43 Not even all of the buttons generate an event 12:50:59 Ah, the xev window didn't have focus. The keys now generate an event but they all have the same keycode and is reported as XF86PowerOff. 12:51:18 No matter which function key I press. 14:02:21 howdy folks, having some issue with not able to torify, anyone can take a look at this and shed some light on https://dpaste.com/6WNAFHLAX 14:16:07 Bushmaster: looks like you need to install net/torsocks 14:17:14 the dependencies of torsocks seems really light, not sure why the tor port doesn't just slap a RUN_DEPENDS on it for this functionality 14:17:15 hey kevans thanks for returning 14:17:30 well i did pkg install torsocks and it did install it 14:17:58 but not sure why it is not letting me connected to other servers 14:18:47 i know nothing beyond just inteerpreting the error you're getting 14:19:32 if you know how to resolve the issue, that would cool 14:55:30 kevans, i resolved it, it just needed torsocks 16:18:48 The installer does not see my Intel dual band wireless AC 8260 wifi card in my laptop, even though it's on the list at https://www.freebsd.org/releases/15.0R/hardware/#wlan - is there anything special I need to do? 16:45:33 joepublic: you need to load the iwm8000Cfw firmware https://man.freebsd.org/cgi/man.cgi?iwm(4) 16:47:28 Thank you, on it 16:57:48 kde wayland on nvidia is a big no 23:12:52 runxiyu: I dont use niri, nor Wayland, but I keep having xorg crash afrer S3 sleep 23:12:56 which wasn't happening before 23:13:09 is S3 involved, or does it crash in use? 23:39:35 polarian: crash in use 23:39:40 hmm 23:39:40 polarian: probably different 23:47:06 runxiyu: yeah 23:47:47 runxiyu: maybe try changing compositor 23:47:55 see if its a wayland issue or a niri issue? 23:48:01 and if its a niri issue, then you can report it upstream 23:48:08 if its a wayland issue, then it needs to go to bugzilla