iwlwifi(4): interface does not exist

/etc/rc.conf includes the lines at the foot of this e-mail. wlan2 does not exist after I start the system. Is my system a little too old? % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #120 main-n252255-78beb051a26: Fri Jan  7 07:09:23 GMT 2022 root@mowa219-

iwlwifi(4): interface does not exist: because net.wlan.devices: iwn0

On 11/01/2022 20:51, Graham Perrin wrote: Is my system a little too old? No. I'm simply not paying attention! % sysctl net.wlan.devices net.wlan.devices: iwn0 % Honestly, I thought I was previously using iwm(4) because I had a commented out line to that effect in my rc.conf ... the iwm

[iwlwifi] FreeBSD 13.1-RC4: installer repeatedly found no networks

On Thursday, March 31st, 2022 at 11:33, Patrick Mackinlay wrote: I am using a matebook pro x 2021 (AX201) with FreeBSD 13 stable … On 31/03/2022 14:34, jbo@insane.engineer wrote: … Intel AX201 as well … Here: FreeBSD-13.1-RC4-amd64-dvd1.iso written to a USB flash drive, installed to an H

Wi-Fi: netif restart wlan0: name resolution

Recent experience, in a nutshell: 1.boot with no connectivity (no known Wi-Fi network within range) 2.use WiFi Networks Manager to configure the OS for an available network 3./etc/rc.d/netif restart wlan0 (the 'Save and Reconnect' button in WiFi Networks Manager) 4.ifconfig wlan0 (observe a connec

Wi-Fi: netif restart wlan0: name resolution: resolvconf.conf(5)

On 11/09/2022 13:36, Graham Perrin wrote: % grep -v \#/etc/resolvconf.conf % To clarify: the file exists, it comprises lines that are commented out (mostly, lines that are used only in static environments). The name resolution problem was with DHCP.

Wi-Fi: netif restart wlan0: name resolution: dhclient

On 12/09/2022 11:35, David Wolfskill wrote: ... The name resolution problem was with DHCP. Right -- re-connecting (e.g., via "service netif restart wlan0") should be starting "dhclient wlan0". ... I'm as certain as I can be that dhclient does run. (I would have noticed the absence of an IP

Wi-Fi: netif restart wlan0: name resolution

On 11/09/2022 13:36, Graham Perrin wrote: ... As far as I recall: /etc/resolv.conf lacked what was required. I tried various approaches to populating the file -- excluding /etc/resolvconf.conf -- none worked. ... From more recent incidents, I suspect that my recollection (above) was

266656 – tuning(7): with some variations from default sysctl values, starts of mail/thunderbird are slow, and kernel panics may occur

With FreeBSD 13.1-RELEASE-p2 and the three non-default values at , might any of the modules below be partially associated with a kernel panic? if_iwlwifi.ko if_iwm.ko iwm7265Dfw.ko There's not yet information from a core dump, from t

Re: 266656 – tuning(7): with some variations from default sysctl values, starts of mail/thunderbird are slow, and kernel panics may occur

On 30/09/2022 20:17, Bjoern A. Zeeb wrote: On Wed, 28 Sep 2022, Graham Perrin wrote: With FreeBSD 13.1-RELEASE-p2 and the three non-default values at <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266656#c0>, might any of the modules below be partially associated with a kernel

devd(8), loading, attaching …

Re: 266656 – tuning(7): with some variations from default sysctl values, starts of mail/thunderbird are slow, and kernel panics may occur On 02/10/2022 23:13, Bjoern A. Zeeb wrote: … in cases where if_iwlwifi is not in rc.conf(5) and if_iwlwifi.ko is loaded, … Likely devd has loaded it on PCI

iwn(4): problems following unexpected disconnection

This morning, I lost Internet connectivity, then realised that the wlan0 file was missing from: /var/run/resolvconf/interfaces/ Without checking logs: I tried a few things to regain name resolution with Wi-Fi, failed. I resorted to a wired connection. After restarting the OS, I checked /var/

Re: iwn(4): problems following unexpected disconnection

On 26/11/2022 16:41, Bjoern A. Zeeb wrote: On Sat, 26 Nov 2022, Graham Perrin wrote: This morning, I lost Internet connectivity, then realised that the wlan0 file was missing from: /var/run/resolvconf/interfaces/ Without checking logs: I tried a few things to regain name resolution with

(207557) (283015) (283027) iwlwifi, 7260

To not risk adding off-topic noise to 7260-related and Is either of the two links below relevant, in any way? 207557 – Intel

Re: iwm(4) occasionally troublesome since main-n274579-50c1e179b584 (2025-01-05)

On 10/01/2025 04:19, Adrian Chadd wrote: … Can you provide a "this is good" and "this is broken" pair of commit hashes from all of your build environments? … No recent build environment, I use pkgbase. So, realistically, the closest that I can get is this pair of lines from my previous

iwm(4) occasionally troublesome since before main-n274579-50c1e179b584

Subject line changed; _before_ main-n274579-50c1e179b584. I first encountered trouble with 50c1e179b584 (<50c1e179b584f43ba82e9afc91b25ec4831b58ef>, 2025-01-05) with eduroam, on my first day back at work after the Christmas break. Boot environment named 1500030-005-base. Today, with a clone

Intel Wi-Fi: scope of iwx(4) on FreeBSD

Yesterday's mentions support for many recent cards. Should we assume that all less recent hardware is out of scope? Alternatively, is my rc.conf file mis-configured? The wlan4 lines below. Thanks root@m

Re: Intel Wi-Fi: scope of iwx(4) on FreeBSD

On 01/04/2025 06:37, Graham Perrin wrote: … is my rc.conf file mis-configured? The wlan4 lines below. … I had two create_args_wlan4 lines, I didn't notice the mistake until I commented out all four wlan4 lines. Other replies noted, with thanks.

iwlwifi kernel panics, Wireless 7260, main-n275833-136c5e17b61a (2025-03-07)

136c5e17b61a from pkgbase base_latest. First panic today, Saturday 2025-03-08 02:18, in response to service netif restart wlan1 at home with ssid 'piano5'. Photographed five minutes after the command (whilst the computer was visibly fr

Re: iwlwifi kernel panics, Wireless 7260, main-n275833-136c5e17b61a (2025-03-07)

On 08/03/2025 09:20, Graham Perrin wrote: … core.txt.14 (02:42, for a panic at 02:28) might contain enough for me to match it to something in Bugzilla. … I could not easily find a match. Attached: an extract from core.txt.14. root@mowa219-gjp4-zbook-freebsd:/var/crash # cat info.14 Dump