#iwlwifi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #iwlwifi, aggregated by home.social.
-
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 -
@kedara if you're not already on 15 or 16, upgrade the base OS. STABLE will be better than RELEASE, if you have no special requirement for RELEASE. Use pkgbase.
If you are already on 15-STABLE or 16-CURRENT, you should find that iwm(4) is more stable, but less performant, than iwlwifi(4).
No mention of devmatch_blocklist anywhere in the FreeBSD Handbook or the documentation portal. You'll find it in the third manual page below. Good luck.
<https://man.freebsd.org/cgi/man.cgi?query=iwlwifi&sektion=4&manpath=freebsd-current>
<https://man.freebsd.org/cgi/man.cgi?query=iwm&sektion=4&manpath=freebsd-current>
<https://man.freebsd.org/cgi/man.cgi?query=rc.conf&sektion=5&manpath=freebsd-current>
#FreeBSD #documentation #Handbook #devmatch #WiFi #iwlwifi #iwm
-
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
-
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
-
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
-
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
-
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 :drgn_sigh: 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.
-
#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. :neofox_uwu:
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.
-
From the #FreeBSD mailing lists for all #laptop users out there:
"Before updating your system please run #fwget(8) or build
wifi-firmware-iwlwifi-kmod (or the appropriate flavor) from ports if you
are using #iwlwifi(4) or #iwx(4).You can do it any time as the extra firmware files will do no harm until
your next reboot at least." -
From the #FreeBSD mailing lists for all #laptop users out there:
"Before updating your system please run #fwget(8) or build
wifi-firmware-iwlwifi-kmod (or the appropriate flavor) from ports if you
are using #iwlwifi(4) or #iwx(4).You can do it any time as the extra firmware files will do no harm until
your next reboot at least." -
From the #FreeBSD mailing lists for all #laptop users out there:
"Before updating your system please run #fwget(8) or build
wifi-firmware-iwlwifi-kmod (or the appropriate flavor) from ports if you
are using #iwlwifi(4) or #iwx(4).You can do it any time as the extra firmware files will do no harm until
your next reboot at least." -
From the #FreeBSD mailing lists for all #laptop users out there:
"Before updating your system please run #fwget(8) or build
wifi-firmware-iwlwifi-kmod (or the appropriate flavor) from ports if you
are using #iwlwifi(4) or #iwx(4).You can do it any time as the extra firmware files will do no harm until
your next reboot at least." -
From the #FreeBSD mailing lists for all #laptop users out there:
"Before updating your system please run #fwget(8) or build
wifi-firmware-iwlwifi-kmod (or the appropriate flavor) from ports if you
are using #iwlwifi(4) or #iwx(4).You can do it any time as the extra firmware files will do no harm until
your next reboot at least." -
「… alternatively, the FreeBSD project gets a subproject going which brings in the WiFi drivers from OpenBSD twice a year or something.」
Smart thinking. +100 to reuse of code, collaboration, and the like.
You're not the first person to ask about OpenBSD. The brief answer, from <https://wiki.freebsd.org/WiFi/Iwlwifi#openbsd>:
「There were other people looking into this.
When I started there was limited support for various chipsets already supported by iwlwifi, … mangled so that comparing to the original code was no longer possible in an automated way … goals listed above … another driver to change and support (in addition to iwm).」
-
They joys of bugs in hardware or firmware[1]:
A user reported updating to #Linux #kernel 6.4.y broke #iwlwifi on a Intel 3165 NIC. Bisection identified 5fc3f6c90cc ("r8169: consolidate disabling ASPM before EPHY access") as culprit.
Turns out it was not a faulty bisection, as it seems enabling #ASPM on some #Realtek chips supported by #r8169 can harm other PCI devices. 🥴 🤨
https://bugzilla.kernel.org/show_bug.cgi?id=217635#c27
[1] or maybe it one day turns out that this is caused by a bug somewhere in the #LinuxKernel
-
@herrbischoff
For me #FreeBSD 13.1 #iwlwifi supported the #AX200 for the first time in my #Dell #XPS 13.Generally you might want to check https://wiki.freebsd.org/WiFi/Iwlwifi