00:05:11 Is it possible to get fleshed out, human-readable argument lists from ktrace -t c ? 01:11:44 rwp: yah i was just now looking at getting the atheros working 01:12:51 The AR9271 is a single-chip USB 2.0 802.11n solution. It operates in 01:12:53 the 2GHz spectrum and supports a single stream (1T1R). 01:13:57 it looks like the chipset is supported by athn but i couldn't figure out how to get it working out the box and i was having issues getting the ethernet working because i have vlans set up on ports of the wifi router in my living room that i use to do quick work where i need to plug in an ethernet cable 01:14:51 it's too bad the installer doesn't help you go through the wifi motions .. and i'm guessing either my wifi module isn't supported or it just doesn't detect it during install. i bet maybe firmware tomfoolery or who knows what heh 04:19:31 vlans on wifi? i didn't know that was a thing 04:28:14 rtprio: 802.11 allows a VLAN tag in a wireless frame, but i'm not sure that's what OP meant, "ports" probably refers to wired Ethernet ports 07:20:00 so is there no way at all to get drm-510 working on recent 14-STABLE? 07:20:18 515 and 61 are both broken in different ways for me 07:21:12 got a pf question. i don't have "log" in any of my rules, but still when i run tcpdump -e -i pflog0 -l -n -t i still see rules 2 and 6 doing a "pass out ..." 07:21:58 why am i seeing anything if "log" isn't in any of the rules? the default rule is block all, fwiw 07:22:23 515 causes random kernel panics in the LinuxKPI rcu subsystem (iirc), and 61 is at least better than that but I get GPU resets that leave my laptop in an unusable state if I try opening up mpv while I've simultaneously got firefox running 07:26:15 61 seems to have some performance issues as well. I think I'm running into this problem, except FF never triggers it on its own: https://github.com/freebsd/drm-kmod/issues/366 07:27:14 I'd hop on over to current to try out drm-66, but all of the officially published binaries for 15 still have performance degrading debug flags applied, right? 07:29:21 the performance I've been getting out of 14-STABLE lately has basically been making this laptop from 2019 feel like the better part of a decade older than it actually is 07:39:45 I'm wondering at what point the snapshots for 15 will have the full performance of the snapshots for 14. is it when stable/15 gets branched from current in the near future? or is it not until releng/15.0, or later? 10:07:09 Hi 10:07:18 Fixed my internet 10:07:32 let's fix the pkgs now.. 10:09:58 good to hear. Good luck 10:29:28 rtprio: what ivy said. Also. Yes. Multiple WiFi networks on different subnets using vlans is why. But I also assign ports to tag because I have iot things attached to it. 10:30:48 I should get a small managed switch for it and keep the ports on the wifi router u tagged. It’s really just a WiFi bridge and since it is in the living room I attach appliances to the Ethernet ports with one leading to the switch in the basement. 11:23:00 guys should I run "pkg upgrade -f".. notice that all pkgs are already for 13.5 11:52:26 It wouldn't hurt 12:02:19 * Alver mutters foul language about ioctls 12:07:36 divlamir: but not necessary.. right? 12:07:59 hi, all 12:23:47 Retrofan: No, freebsd-update would have told you if it was necessary. But I would do it to be safe if I make a big jump 12:24:16 it didn't tell me.. 12:28:03 Do some testing then, usage will tell if everything is working 12:36:40 yeah 12:36:52 Installed the missing drivers 12:37:10 and I will reboot with x11 13:07:59 I updated the loader 13:08:02 But.. 13:09:24 the drivers still have problem.. 13:20:54 I already installed drm-kmod 13:56:36 Alver: just curious, what is the output of procstat -k for one of your processes that is uninterruptible sleep on the tun operation? 13:59:36 jmnbtslsQE: mi_switch _cv_wait_unlock tun_destroy tun_clone_destroy if_clone_destroyif_flags if_clone_destroy ifioctl kern_ioctl sys_ioctl amd64_syscall fast_syscall_common 14:00:51 er 14:00:59 why are you spreading this tunfd quite so far and wide, anyways? 14:01:17 kevans: hercules emulator. Not my code (un?)fortunately 14:01:18 tuns are generally expected to be driven by just one process 14:01:44 kevans: that is the stack for the one process. 14:02:03 so presumably it's just forking and still holding the file open in other threads? 14:02:34 Possible. It's way beyond my capabilities for now. :/ 14:02:46 got a link to the thing you're working on specifically? 14:04:11 kevans: https://github.com/SDL-Hercules-390/hyperion/blob/f7c6a3db010096aa6e3fcb72aaf7572dfd4bae91/tuntap.c . But that does not have any of my changes in 14:04:38 ... and it doesn't work the least bit out of the box. Looks like no one ever bothered trying to run hercules with QETH on FreeBSD before. 14:05:07 I've written the code for pretty much everything else, but closing a tun created by (my code in) the app is a huge pain. 14:05:56 I can close the file descriptor I get passed, but then the tun just gets dismantled - it remains visible in ifconfig. 14:06:52 Hence my attempt at SIOCIFDESTROY but that's six (seven?) times now that I've screwed over my jail host server with an uninterruptable wait. :°) 14:08:18 If I read the code correctly, on Linux, just closing the last fd to a tun device will automatically tear down and destroy the device too. 14:09:05 yeah, I have a thing to allow ours to do similar 14:09:18 https://reviews.freebsd.org/D44200 14:09:51 Oooh. That would be *very* convenient. 14:10:03 should probably get that in for 15.0 now that you mention it 14:13:00 Alver: oh, you might also be interested in https://reviews.freebsd.org/D39740 14:13:16 I was already reading it :D 14:13:17 that at least lets you ^C ifconfig 14:13:29 or whatever's trying to destroy it 14:13:38 Useful indeed. The chicken-egg situation I have is not very handy 14:14:14 Well, hercules has the capability to create a tun device itself for the duration of its emulation, and you can specify the parameters - tun or tap, ips, netmask, mtu, etc etc. 14:14:53 I can already make it do all that (which in itself was already a kludge due to differences in Linux and FreeBSD ioctls). But the cleanup not yet. 14:15:59 Since it's an emulator I also have very little control over what happens on the tun so I can't even properly reproduce the problems I have. It will segfault, hang, or succeed. 14:16:46 I linked in ASan but that didn't show anything overly obvious. Built with -O2, segfault. Built with -O0, hang. But is it related? Who can tell. 14:27:53 Alver: i don't really have time to help there i'm afraid, but i at least pushed those two tuntap patches for 15.0. I think both are reasonable MFC candidates for 14.4, though transient tunnels may be a little trickier 14:28:06 14.4 might just get interruptible destroy 14:28:40 kevans: thanks for the pointers already. I'll keep an eye out 15:04:46 Hi 15:05:05 My PC is finally working!!! 15:05:15 using chatzilla now 15:06:07 Thank you everyone for help.. FreeBSD community is the best :) 15:10:07 so is the OS 15:12:40 Sure! 15:13:33 Upgrading fixed most of my problems and bugs 15:15:20 and with Linux compatibility layer bugs fixed 15:16:09 But.. some problems with AMD radeon drivers :( 15:17:21 Next.. will be fixing my old ports, fixing drivers, building SeaMonkey native; bec. I really need to leave chrome 15:18:29 * Retrofan Retrofan hates chrome so much! 15:18:54 it's fast.. but doing nothing of my needs 15:20:11 No Plugins, FTP, Gopher, Usenet, IRC, etc.. 15:22:14 Congratulations Retrofan 15:22:34 lots of good has been happening the last few days 15:22:45 I'm sure you'll manage to fix the rest, too 15:23:23 I am really want to bring seamonkey to ports tree again.. 15:23:37 I loved seamonkey as well 15:24:04 autumnblue: thank you :) 15:24:10 are still user of it 15:24:15 :) 15:25:27 My CRT is making some strange signals 15:25:56 those signals make me fell blind.. 15:26:18 haha, some magnet next to it or something perhaps 15:27:01 don't forget to press the degauss button 15:29:17 No magnets 15:29:44 I remember degauss button 15:30:16 this CRT was not powered up for nearly 20 year.. until I begin to use it 15:33:18 Done. 15:35:27 I had a Dell CRT back in the day, using it for nearly 12 years with no need for degaussing 15:36:18 yeah 15:36:23 good times 15:37:25 CRT stuff is so dangerous.. 15:38:03 20kv at the rear of the tube, and that's often where the adjustment rheostats are... 15:38:12 yeah 15:38:24 yeah pretty jolty 15:38:48 I remember someone got a shock from that high voltage transformer 15:39:02 but he is fine now.. 15:39:20 took them a couple decades to be fine? 15:39:34 oh yeah transformer not CRT I see 15:39:51 he got a burn on his hand 15:40:07 20k shock will surly kill someone.. 15:40:21 yeah it's better to be safe 15:45:53 depends on the amps, but yeah, plastic tools ;] 15:48:10 As I know CRT has high amp voltage.. 15:50:40 Oh.. gimp is working again 15:54:35 that remember me when I ported it to Atari sparemint 15:54:51 https://www.atari-forum.com/viewtopic.php?t=41347 15:56:11 er.. chrome removed support for ublock, hate it more than ever.. 16:00:14 https://www.atari-forum.com/viewtopic.php?p=427793 16:00:42 then they continued the rest.. 16:03:40 I use Qubes OS on my workstation, it's easier to keep things separate 16:04:51 Re: my question last night: 16:04:51 but you buy the price with no DMA forwarding and no hyper threading, but it's all for security 16:04:53 Ah, solved. I thought I had to specify -t options and in doing so zapped the defaults, which included "n trace namei(9) translations" 16:05:11 both are enableable options but messes with security 17:00:47 Wait.. 17:01:00 Ghidra is removed from pkgs..? 17:05:19 that's not really how I would characterize it 17:07:18 the port still exists and the license terms don't prevent packaging, there just isn't a package at the moment for whatever reason 17:07:44 yeah understand 17:08:05 it will be a pain to compile a huge software like that :( 17:08:30 I was using on 13.2 17:08:40 pkg search returns ghidra-11.3.1 17:09:13 mine nothing.. 17:09:28 I am on 14.3 17:09:45 is 13.5 more updated than 14.3 ? 17:10:16 I may use the pkg files, I still have them 17:10:21 *old 17:15:00 the ports tree is shared across all releases, but it or one of its dependencies could be failing to build on yours for some reason or another 17:15:42 I faced that alot on old ports 17:15:56 look like time to go.. 17:16:45 And again thanks for help :) 17:27:18 ghidra can just be run from a directory I think, with whatever tarball the nsa provides or equally 17:46:59 last time I saw, it was basically jre -run ghidra.jar or something. 17:47:08 which of course is ages ago