Re: New laptop: AC 9461/9560: iwm or iwlwifi?
- In reply to: Bjoern A. Zeeb: "Re: New laptop: AC 9461/9560: iwm or iwlwifi?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 19 Dec 2022 21:46:03 UTC
On Mon, Dec 19, 2022 at 09:32:49PM +0000, you (Bjoern A. Zeeb) sent the following to [freebsd-wireless] :
> On Mon, 19 Dec 2022, Marco wrote:
>
> > On Mon, Dec 19, 2022 at 08:56:02PM +0000, you (Marco) sent the following to [freebsd-wireless] :
> >> On Sat, Dec 17, 2022 at 10:40:25PM +0000, you (Bjoern A. Zeeb) sent the following to [freebsd-wireless] :
> >>>
> >>> Did you try again to switch back to iwlwifi?
> >>>
> >>> What happens if you are on a running iwm setup and then do the devctl
> >>> detach, set driver dance?
> >
> > So on my current running iwm setup without changing anything else I did
> > the devtl detach, set driver dance which failed as follows:
> >
> > [~] doas pciconf -lBbcevV iwm0
> > iwm0@pci0:0:20:3: class=0x028000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x9df0 subvendor=0x8086 subdevice=0x0030
> > vendor = 'Intel Corporation'
> > device = 'Cannon Point-LP CNVi [Wireless-AC]'
> > class = network
> > bar [10] = type Memory, range 64, base 0xea238000, size 16384, enabled
> > cap 01[c8] = powerspec 3 supports D0 D3 current D0
> > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
> > cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR RO NS
> > max read 128
> > cap 11[80] = MSI-X supports 16 messages
> > Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
> > ecap 0000[100] = unknown 0
> > ecap 0018[14c] = LTR 1
> > ecap 000b[164] = Vendor [1] ID 0010 Rev 0 Length 20
> >
> > [~] kldstat | grep -e wlan -e wi-fi -e wifi -e iwm
> > 3 1 0xffffffff82d4c000 290cc0 iwm9000fw.ko
> > 6 1 0xffffffff82fe6000 3130 wlan_xauth.ko
> > 7 1 0xffffffff82fea000 2e870 if_iwm.ko
> >
> > [~] doas kldload /boot/kernel/if_iwlwifi.ko
> > [~] kldstat | grep -e wlan -e wi-fi -e wifi -e iwm
> > 3 1 0xffffffff82d4c000 290cc0 iwm9000fw.ko
> > 6 1 0xffffffff82fe6000 3130 wlan_xauth.ko
> > 7 1 0xffffffff82fea000 2e870 if_iwm.ko
> > 39 1 0xffffffff85565000 880c8 if_iwlwifi.ko
> >
> > [~] doas devctl detach pci0:0:20:3
> > [~] doas pciconf -lBbcevV iwm0
> > pciconf: Device not found
> >
> > [~] doas devctl set driver pci0:0:20:3 iwlwifi
> > devctl: Failed to set pci0:0:20:3 driver to iwlwifi: Input/output error
>
> You got an error here.
>
> Was there anything else logged?
>
>
>
>
> > [~] ifconfig lagg0
> > lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> > options=800000<>
> > ether f8:75:a4:fa:9d:bf
> > inet6 fe80::fa75:a4ff:fefa:9dbf%lagg0/64 scopeid 0x4
> > inet6 2a10:3781:41f:1:fa75:a4ff:fefa:9dbf/64 autoconf
> > inet6 2a10:3781:41f:1:4df2:19b7:b73e:17bc/64 deprecated autoconf temporary
> > inet6 2a10:3781:41f:1:6ce0:18a5:8fdb:52ab/64 autoconf temporary
> > inet 192.168.3.114/24 broadcast 192.168.3.255
> > laggproto failover lagghash l2,l3,l4
> > laggport: em0 flags=5<MASTER,ACTIVE>
> > groups: lagg
> > media: Ethernet autoselect
> > status: active
> > nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
> >
> > [~] ifconfig wlan0
> > ifconfig: interface wlan0 does not exist
> >
> > My next action could be to define both wlans_ entries in rc.conf and set
> > the devmatch_blocklist to if_iwm and reboot the laptop (without
> > rebuilding world and/or kernel) ?
>
> I think we should first figure out why you get an error above.
>
> If in hte current state you set the driver back to iwm, will that just
> come back and work again?
No unfortunately not
[~] doas devctl detach pci0:0:20:3
devctl: Failed to detach pci0:0:20:3: Device not configured
[~] doas devctl set driver pci0:0:20:3 iwm
devctl: Failed to set pci0:0:20:3 driver to iwm: Device not configured
But then despite the 'device not configured' message pci0:0:20:3 does
seem to have attached itself to iwm0 again:
[~] doas pciconf -lBbcevV iwlwifi0
pciconf: Device not found
[~]
[~] doas pciconf -lBbcevV iwm0
iwm0@pci0:0:20:3: class=0x028000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x9df0 subvendor=0x8086 subdevice=0x0030
vendor = 'Intel Corporation'
device = 'Cannon Point-LP CNVi [Wireless-AC]'
class = network
bar [10] = type Memory, range 64, base 0xea238000, size 16384, enabled
cap 01[c8] = powerspec 3 supports D0 D3 current D3
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[40] = PCI-Express 2 root endpoint max data 128(128) FLR RO NS
max read 128
cap 11[80] = MSI-X supports 16 messages
Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
ecap 0000[100] = unknown 0
ecap 0018[14c] = LTR 1
ecap 000b[164] = Vendor [1] ID 0010 Rev 0 Length 20
/var/log/messages contains:
Dec 19 21:36:18 harbinger kernel: [812136] iwm0: <Intel(R) Dual Band Wireless AC 9560> mem 0xea238000-0xea23bfff irq 16 at device 20.3 on pci0
Dec 19 21:36:18 harbinger kernel: [812136] iwm0: attempting to allocate 1 MSI vectors (1 supported)
Dec 19 21:36:18 harbinger kernel: [812136] msi: routing MSI IRQ 129 to local APIC 2 vector 53
Dec 19 21:36:18 harbinger kernel: [812136] iwm0: using IRQ 129 for MSI
Dec 19 21:36:18 harbinger kernel: [812136] iwm0: Failed to lock the nic
Dec 19 21:36:18 harbinger kernel: [812136] device_attach: iwm0 attach returned 6
Not sure what to expect being in this state though, wlan0 is not present
[~]
[~] ifconfig wlan0
ifconfig: interface wlan0 does not exist
All kernel modules are still loaded:
[~] kldstat | grep -e wlan -e wi-fi -e wifi -e iwm
3 1 0xffffffff82d4c000 290cc0 iwm9000fw.ko
6 1 0xffffffff82fe6000 3130 wlan_xauth.ko
7 1 0xffffffff82fea000 2e870 if_iwm.ko
39 1 0xffffffff85565000 880c8 if_iwlwifi.ko
Should I run: doas service netif restart ? (instead of powercycling)
--
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG fingerprint: A025 D8AA AC1B D2FC 380D 4FC1 8EA0 0BA8 8580 E6CB
"The Tuck Pendleton machine...zero defects."