I just ran some comparisons of the iwm(4) and the iwlwifi(4) drivers for my FreeBSD 15.1-RELEASE Lenovo X1 Carbon (gen 6).

After three tests of each driver the results suggest that:

1) iwlwifi is a more reliable connection (across jitter, latency and drops).
2) iwlwifi download is 200%+ higher than iwm
3) iwm upload is 350%+ higher than iwlwifi
4) iwm connects at 54Mbps 802.11a
5) iwlwifi connects at 802.11ac 80 MHz (VHT/80+)

Really promising improvements so far.

#FreeBSD #iwlwifi #iwm

LinuxKPI: 802.11: add support for suspend/resume · freebsd/freebsd-src@11d69a4 : r/freebsd

https://www.reddit.com/r/freebsd/comments/1tne7yu/linuxkpi_80211_add_support_for_suspendresume/

If you need the iwlwifi driver and mobility – a laptop, for example:

― FreeBSD-STABLE will be more useful than FreeBSD 15.1-RELEASE.

#FreeBSD #WiFi #wireless #iwlwifi #Intel

Home-lab WiFi yak shaving rabbit hole from hell.

1. UAP-AC-Pro only negotiates 100baseT on an 8m cable with PoE injector
2. I re-crimp both ends of the cable, multiple times
3. I replace the switch with an RB4011, move the (48V) PoE injector in front of the switch
4. Still 100baseT, but the AP is now resetting when it gets warm
5. I replace the UAP with a hAP AC
6. The hAP negotiates GbE, but iwlwifi (AX200) firmware crashes on connect: https://bugzilla.kernel.org/show_bug.cgi?id=221360

#MikroTik #Unifi #WiFi #iwlwifi

Working on a Buildroot OS with kernel 6.18 + PREEMPT_RT on an Intel AX210 WiFi (iwlwifi QuZ firmware). With dynamic preempt everything works, but RT causes firmware init errors and the device disappears. Maybe bleeding-edge RT kernels aren’t always the best choice. Curious if others hit similar issues or found workarounds. Open to discussion.

#Linux #Buildroot #Kernel #RealTime #PREEMPTRT #iwlwifi #IntelAX210 #EmbeddedLinux #FOSS #CyberSecurity

Huh, looks like I hurried to sign praises for iwlwifi in the FreeBSD 15.0  With wlan0 (Intel Dual Band Wireless-AC 8260) added to the aggregate interface lagg0, I receive "general protection fault while in kernel mode" if laptop booted with connected Ethernet cable, or if I connect the cable after the system boot.

#FreeBSD #FreeBSD150RELEASE #iwlwifi

#iwlwifi broke after a recent NixOS upgrade (firmware/kernel issue, not really distro-specific), but being forced #offline finally got me to work on my #OrgRoam memex.  
Linked a bunch of lonely nodes together.
Once I got the network back online I even wrote some #Elisp to replace old link that point to files with UUID ones.
And yeah, I needed a search engine for that, because the built-in docs for #Emacs - while often handy - are lacking in examples and assume a bit too much up-front knowledge. I'm still not sure what the heck org-element-context returns and why I should need a special function to index it. Say what you will about the complexity of #JavaScript or #Python, having built-in data types for lists, sets, and maps makes it a lot easier to poke at data.
But at least I could hack together about half of it from offline sources.

One issue that surprised me is that default setup for editing ELisp in #DoomEmacs is still not entirely user friendly. Lots of things work out of the box, which is really cool, but some simple things like automatic indentation are not really consistent.
When I saved the file, it got reformatted in a way that broke its structure.
When I tried to de-indent a line, it deleted too much whitespace, instead of just going back a single level, so I had to use C-x TAB, which is unnecessarily many keystrokes for such a common operation.

All in all, I'm impressed at how productive I can be with it and I hope that the jankiness will be less of an issue once I've gained some Elisp experience.