You are not logged in.
Pages: 1
I have a Dell XPS 13 9360 with an Intel 8260 WiFi/Bluetooth wireless card. Wifi works well but bluetooth not. Bluetooth works on Windows, so it's not a hardware issues.
uname -r
4.17.6-1-ARCHlspci | grep -i network
3a:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:670c Microdia
Bus 001 Device 002: ID 8087:0a2b Intel Corp. #the intel bluetooth device?
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubrfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: nodmesg | egrep -i 'blue|firm'
[ 0.023333] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 0.278491] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 1.592126] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 1.598802] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 1.671876] iwlwifi 0000:3a:00.0: loaded firmware version 36.e91976c0.0 op_mode iwlmvm
[ 2.652095] Bluetooth: Core ver 2.22
[ 2.652111] Bluetooth: HCI device and connection manager initialized
[ 2.652114] Bluetooth: HCI socket layer initialized
[ 2.652116] Bluetooth: L2CAP socket layer initialized
[ 2.652121] Bluetooth: SCO socket layer initialized
[ 2.659200] Bluetooth: hci0: Firmware revision 0.0 build 118 week 50 2016
[ 2.660267] Bluetooth: hci0: Found Intel default device address (00:03:19:9e:8b:00)
[ 3.131967] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.131968] Bluetooth: BNEP filters: protocol multicast
[ 3.131971] Bluetooth: BNEP socket layer initialized
[ 26.390370] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 26.394357] Bluetooth: hci0: Device revision is 5
[ 26.394361] Bluetooth: hci0: Secure boot is enabled
[ 26.394365] Bluetooth: hci0: OTP lock is disabled
[ 26.394368] Bluetooth: hci0: API lock is enabled
[ 26.394370] Bluetooth: hci0: Debug lock is disabled
[ 26.394375] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 26.394378] Bluetooth: hci0: No device address configured
[ 26.396466] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 26.405840] Bluetooth: hci0: Failed to send firmware data (-38)
[ 36.937257] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 36.940352] Bluetooth: hci0: Device revision is 5
[ 36.940354] Bluetooth: hci0: Secure boot is enabled
[ 36.940354] Bluetooth: hci0: OTP lock is disabled
[ 36.940355] Bluetooth: hci0: API lock is enabled
[ 36.940356] Bluetooth: hci0: Debug lock is disabled
[ 36.940357] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 36.940357] Bluetooth: hci0: No device address configured
[ 36.940569] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 38.422416] Bluetooth: hci0: Waiting for firmware download to complete
[ 38.423243] Bluetooth: hci0: Firmware loaded in 1451567 usecs
[ 38.423339] Bluetooth: hci0: Waiting for device to boot
[ 38.434252] Bluetooth: hci0: Device booted in 10705 usecs
[ 38.434489] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[ 38.439293] Bluetooth: hci0: Applying Intel DDC parameters completedbluetoothctl:
[bluetooth]# devices
No default controller availableThe issue seems on:
[ 26.405840] Bluetooth: hci0: Failed to send firmware data (-38)I find the similar output of dmesg in https://bbs.archlinux.org/viewtopic.php?id=208328, but I'm not using laptop-mode.
and
modprobe -r btusb
modprobe btusbalso not work.
I've been searching for related issues, but haven't been able to find anything helpful.
Anyone also have this issue on 8260 or any Intel Wireless Card? Any help is appreciated! Thanks.
Last edited by FireZ (2018-07-18 13:39:55)
Offline
This is likely to be power saving related.
If you're using tlp or laptop-mode-tools or other, you may want to look at blacklisting either the device id or btusb from any USB autosuspend. It's also possible, but less likely - as it's a laptop - that there's some bios configuration for this too.
Offline
You should also double check that the bluetooth service is actually enabled too. Possibly unrelated, but I was getting issues where it would mostly not work, but randomly work often enough to confuse me until I realised. Think I was getting a race condition to do with networkmanager that meant it actually ended up starting via dbus.
Offline
After a "warm" reboot, I found a error output in dmesg
Found Intel default device addressAnd in kernel source `drivers/bluetooth/btintel.c` around 60 line:
/* For some Intel based controllers, the default Bluetooth device
* address 00:03:19:9E:8B:00 can be found. These controllers are
* fully operational, but have the danger of duplicate addresses
* and that in turn can cause problems with Bluetooth operation.
*/
if (!bacmp(&bda->bdaddr, BDADDR_INTEL)) {
bt_dev_err(hdev, "Found Intel default device address (%pMR)",
&bda->bdaddr);
set_bit(HCI_QUIRK_INVALID_BDADDR, &hdev->quirks);
}It seems like that the bt devices have a invalid address. I comment it and rebuild this module (btintel), the bluetooth works after a reboot. But it still not work from a hard reboot (power off and on).
Last edited by FireZ (2018-07-20 10:55:45)
Offline
That would indicate to me https://git.kernel.org/pub/scm/linux/ke … 17.8#n1393 is not working as expected.
Offline
I have a Dell XPS 15 9550, originally this had a Broadcom module but I recently switched to this one. I am having exactly the same bluetooth issue with default address detected and the device not being configured. To get around it, I am using the btmgmt utility and using the public-addr command to add the mac address. The device then configures. I have to do this on boot and after suspend and wake as well to get it up and running. I'm going to script this up to automate. Just wanted to report another way to get it up.
[b@bbpc ~]$ sudo btmgmt
[sudo] password for b:
[mgmt]# info
Index list with 0 items
[mgmt]# config
Unconfigured index list with 1 item
hci0: Unconfigured controller
manufacturer 2
supported options: public-address
missing options: public-address
[mgmt]# public-addr 00:03:19:9e:8b:00
hci0 Set Public Address complete, options:
hci0 removed (unconfigured)
hci0 added
hci0 new_settings: ssp br/edr
hci0 new_settings: ssp br/edr le
hci0 new_settings: ssp br/edr le secure-conn
hci0 name changed: bbpc
hci0 new_settings: bondable ssp br/edr le secure-conn
[mgmt]# info
Index list with 1 item
hci0: Primary controller
addr 00:03:19:9E:8B:00 version 8 manufacturer 2 class 0x000000
supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr
current settings: bondable ssp br/edr le secure-conn
name bbpc
short name
hci0: Configuration options
supported options: public-address
missing options:
[mgmt]# exitOffline
I have very similar problem, however in my case hci device is not even created...
# uname -r
4.17.14-arch1-1-ARCH# lspci -knnvv -d 8086:24f3
06:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 38
NUMA node: 0
Region 0: Memory at fb100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00438 Data: 0000
Capabilities: [40] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L1, Exit Latency L1 <8us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE#
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
AtomicOpsCtl: ReqEn-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [140 v1] Device Serial Number a4-34-d9-ff-ff-95-d1-43
Capabilities: [14c v1] Latency Tolerance Reporting
Max snoop latency: 0ns
Max no snoop latency: 0ns
Capabilities: [154 v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=30us PortTPowerOnTime=18us
L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
T_CommonMode=0us LTR1.2_Threshold=0ns
L1SubCtl2: T_PwrOn=10us
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi# systool -v -m iwlwifi
Module = "iwlwifi"
Attributes:
coresize = "327680"
initsize = "0"
initstate = "live"
refcnt = "1"
srcversion = "01D9DE205A51B845347CF4A"
taint = ""
uevent = <store method only>
Parameters:
11n_disable = "0"
amsdu_size = "0"
antenna_coupling = "0"
bt_coex_active = "Y"
d0i3_disable = "Y"
d0i3_timeout = "1000"
debug = "0"
disable_11ac = "N"
fw_monitor = "N"
fw_restart = "Y"
lar_disable = "N"
led_mode = "0"
nvm_file = "(null)"
power_level = "0"
power_save = "N"
swcrypto = "0"
uapsd_disable = "3"
Sections:
.altinstr_replacement= "0xffffffffc0af2a4d"
.altinstructions = "0xffffffffc0b0f658"
.bss = "0xffffffffc0b13ec0"
.data.once = "0xffffffffc0b128f0"
.data = "0xffffffffc0b10300"
.exit.text = "0xffffffffc0af2a3c"
.gnu.linkonce.this_module= "0xffffffffc0b13b80"
.init.text = "0xffffffffc0b22000"
.note.gnu.build-id = "0xffffffffc0af3000"
.orc_unwind = "0xffffffffc0b08d21"
.orc_unwind_ip = "0xffffffffc0b04e05"
.parainstructions = "0xffffffffc0b0f7d8"
.ref.data = "0xffffffffc0b12d00"
.rodata = "0xffffffffc0af35c0"
.rodata.str1.1 = "0xffffffffc0aff23b"
.rodata.str1.8 = "0xffffffffc0b00ed8"
.smp_locks = "0xffffffffc0b0f674"
.strtab = "0xffffffffc0b2fdc8"
.symtab = "0xffffffffc0b23000"
.text = "0xffffffffc0ad1000"
.text.unlikely = "0xffffffffc0af2a55"
__bpf_raw_tp_map = "0xffffffffc0b12900"
__bug_table = "0xffffffffc0b120b0"
__jump_table = "0xffffffffc0b10000"
__kcrctab = "0xffffffffc0af3490"
__kcrctab_gpl = "0xffffffffc0af34a0"
__ksymtab = "0xffffffffc0af3030"
__ksymtab_gpl = "0xffffffffc0af3070"
__ksymtab_strings = "0xffffffffc0b04870"
__mcount_loc = "0xffffffffc0b0ebd0"
__param = "0xffffffffc0b0f3b0"
__tracepoints_ptrs = "0xffffffffc0b0f8f8"
__tracepoints_strings= "0xffffffffc0b0f9c0"
__tracepoints = "0xffffffffc0b13540"
_ftrace_events = "0xffffffffc0b12c20"And here rfkill fails:
# rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no# journalctl -k | egrep -i 'iwl|btintel|blue|firmw'
Aug 15 15:47:41 arch-box kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb000020 (or later)
Aug 15 15:47:41 arch-box kernel: [Firmware Bug]: TSC ADJUST: CPU0: -99503475057608 force to 0
Aug 15 15:47:41 arch-box kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors
Aug 15 15:47:41 arch-box kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Aug 15 15:47:41 arch-box kernel: DMAR: [Firmware Bug]: RMRR entry for device 05:00.0 is broken - applying workaround
Aug 15 15:47:42 arch-box kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Aug 15 15:47:42 arch-box kernel: iwlwifi 0000:06:00.0: loaded firmware version 36.e91976c0.0 op_mode iwlmvm
Aug 15 15:47:42 arch-box kernel: iwlwifi 0000:06:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
Aug 15 15:47:42 arch-box kernel: iwlwifi 0000:06:00.0: base HW address: a4:34:d9:95:d1:43
Aug 15 15:47:42 arch-box kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
Aug 15 15:47:42 arch-box kernel: iwlwifi 0000:06:00.0 wlp6s0: renamed from wlan0
Aug 15 15:58:51 arch-box kernel: Bluetooth: Core ver 2.22
Aug 15 15:58:51 arch-box kernel: Bluetooth: HCI device and connection manager initialized
Aug 15 15:58:51 arch-box kernel: Bluetooth: HCI socket layer initialized
Aug 15 15:58:51 arch-box kernel: Bluetooth: L2CAP socket layer initialized
Aug 15 15:58:51 arch-box kernel: Bluetooth: SCO socket layer initializedNote that at 15:58:51 I have manually inserted the btintel module, however rfkill still doesn't show anything...
# modprobe btintel
# lsmod | egrep 'iwl|btintel|blue'
btintel 24576 0
bluetooth 638976 1 btintel
ecdh_generic 24576 1 bluetooth
iwlmvm 430080 0
mac80211 925696 1 iwlmvm
iwlwifi 327680 1 iwlmvm
cfg80211 778240 3 iwlmvm,iwlwifi,mac80211
led_class 16384 2 input_leds,iwlmvm
rfkill 28672 3 bluetooth,cfg80211
crc16 16384 2 bluetooth,ext4# systool -v -m btintel
Module = "btintel"
Attributes:
coresize = "24576"
initsize = "0"
initstate = "live"
refcnt = "0"
srcversion = "B978516D847A719EA755825"
taint = ""
uevent = <store method only>
version = "0.1"
Sections:
.data.once = "0xffffffffc0f42188"
.data = "0xffffffffc0f42060"
.gnu.linkonce.this_module= "0xffffffffc0f421c0"
.note.gnu.build-id = "0xffffffffc0f40000"
.orc_unwind = "0xffffffffc0f40f12"
.orc_unwind_ip = "0xffffffffc0f40b92"
.rodata = "0xffffffffc0f408e0"
.rodata.str1.1 = "0xffffffffc0f40777"
.rodata.str1.8 = "0xffffffffc0f40188"
.smp_locks = "0xffffffffc0f408d4"
.strtab = "0xffffffffc0f45d68"
.symtab = "0xffffffffc0f45000"
.text = "0xffffffffc0f3e000"
__bug_table = "0xffffffffc0f420d0"
__jump_table = "0xffffffffc0f42000"
__kcrctab_gpl = "0xffffffffc0f40140"
__ksymtab_gpl = "0xffffffffc0f40030"
__ksymtab_strings = "0xffffffffc0f40a28"
__mcount_loc = "0xffffffffc0f41458"
__verbose = "0xffffffffc0f420e0"# rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: noWireless obviously works without a problem, I'm only having this issue with the bluetooth.
# iw phy
Wiphy phy0
max # scan SSIDs: 20
max scan IEs length: 422 bytes
max # sched scan SSIDs: 20
max # match sets: 11
max # scan plans: 2
max scan plan interval: 65535
max scan plan iterations: 254
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x11ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT Max RX data rate: 300 Mbps
HT TX/RX MCS rate indexes supported: 0-15
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (22.0 dBm)
* 2417 MHz [2] (22.0 dBm)
* 2422 MHz [3] (22.0 dBm)
* 2427 MHz [4] (22.0 dBm)
* 2432 MHz [5] (22.0 dBm)
* 2437 MHz [6] (22.0 dBm)
* 2442 MHz [7] (22.0 dBm)
* 2447 MHz [8] (22.0 dBm)
* 2452 MHz [9] (22.0 dBm)
* 2457 MHz [10] (22.0 dBm)
* 2462 MHz [11] (22.0 dBm)
* 2467 MHz [12] (22.0 dBm)
* 2472 MHz [13] (22.0 dBm)
* 2484 MHz [14] (22.0 dBm)
Band 2:
Capabilities: 0x11ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT Max RX data rate: 300 Mbps
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x038071b0):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformee
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180 MHz [36] (22.0 dBm)
* 5200 MHz [40] (22.0 dBm)
* 5220 MHz [44] (22.0 dBm)
* 5240 MHz [48] (22.0 dBm)
* 5260 MHz [52] (22.0 dBm)
* 5280 MHz [56] (22.0 dBm)
* 5300 MHz [60] (22.0 dBm)
* 5320 MHz [64] (22.0 dBm)
* 5340 MHz [68] (22.0 dBm)
* 5360 MHz [72] (22.0 dBm)
* 5380 MHz [76] (22.0 dBm)
* 5400 MHz [80] (22.0 dBm)
* 5420 MHz [84] (22.0 dBm)
* 5440 MHz [88] (22.0 dBm)
* 5460 MHz [92] (22.0 dBm)
* 5480 MHz [96] (22.0 dBm)
* 5500 MHz [100] (22.0 dBm)
* 5520 MHz [104] (22.0 dBm)
* 5540 MHz [108] (22.0 dBm)
* 5560 MHz [112] (22.0 dBm)
* 5580 MHz [116] (22.0 dBm)
* 5600 MHz [120] (22.0 dBm)
* 5620 MHz [124] (22.0 dBm)
* 5640 MHz [128] (22.0 dBm)
* 5660 MHz [132] (22.0 dBm)
* 5680 MHz [136] (22.0 dBm)
* 5700 MHz [140] (22.0 dBm)
* 5720 MHz [144] (22.0 dBm)
* 5745 MHz [149] (22.0 dBm)
* 5765 MHz [153] (22.0 dBm)
* 5785 MHz [157] (22.0 dBm)
* 5805 MHz [161] (22.0 dBm)
* 5825 MHz [165] (22.0 dBm)
* 5845 MHz [169] (22.0 dBm)
* 5865 MHz [173] (22.0 dBm)
* 5885 MHz [177] (22.0 dBm)
* 5905 MHz [181] (22.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* tdls_mgmt
* tdls_oper
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
* add_tx_ts
* set_multicast_to_unicast
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 20 patterns of 16-128 bytes,
maximum packet offset 0 bytes
* can do GTK rekeying
* wake up on GTK rekey failure
* wake up on EAP identity request
* wake up on 4-way handshake
* wake up on rfkill release
* wake up on network detection, up to 11 match sets
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 3, #channels <= 2
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports per-vif TX power setting
P2P GO supports CT window setting
P2P GO supports opportunistic powersave setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device adds DS IE to probe requests
Device can update TPC Report IE
Device supports static SMPS
Device supports dynamic SMPS
Device supports WMM-AC admission (TSPECs)
Device supports configuring vdev MAC-addr on create.
Device supports TDLS channel switchingLast edited by nrz (2018-08-15 23:57:40)
Offline
Pages: 1