On bluetoothctl, anything I do returns with "No default controller available". I have tried bluetoothctl No default controller available but it doesn't help.
hcitool dev shows nothing:
Devices:
output of btmgmt power on:
Set Powered for hci0 failed with status 0x03 (Failed)
hciconfig hci0 up doesn't work either:
Can't init device hci0: cannot assign requested address(99)
I'm using bluez 5.50.
I tried rfkill list, but bluetooth was not blocked. Here is the output of dmesg | grep Blue :
[ 6.417329] usb 1-7: Product: Bluetooth Radio
[ 8.468387] Bluetooth: Core ver 2.22
[ 8.468409] Bluetooth: HCI device and connection manager initialized
[ 8.468413] Bluetooth: HCI socket layer initialized
[ 8.468416] Bluetooth: L2CAP socket layer initialized
[ 8.468423] Bluetooth: SCO socket layer initialized
[ 9.634178] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.634180] Bluetooth: BNEP filters: protocol multicast
[ 9.634187] Bluetooth: BNEP socket layer initialized
[ 10.560211] Bluetooth: hci0: command 0x1001 tx timeout
[ 18.656216] Bluetooth: hci0: HCI_OP_READ_LOCAL_VERSION failed (-110)
[ 356.544055] Bluetooth: hci0: command 0x1001 tx timeout
[ 364.735232] Bluetooth: hci0: HCI_OP_READ_LOCAL_VERSION failed (-110)
[ 496.555828] Bluetooth: RFCOMM TTY layer initialized
[ 496.555836] Bluetooth: RFCOMM socket layer initialized
[ 496.555844] Bluetooth: RFCOMM ver 1.11```
Related
I am trying connect Ubuntu pc with device. While command entered, it returns various error including rfcomm connect address already in use 、 host is down 、 rfcomm connect now in progress.
Device environment and procedure as below
Device environment
Linux 3.4
Bluez 5.19
bt addr xx:xx:xx:xx:38:A4
PC environment
Ubuntu 14.04
bluez 4
bt addr xx:xx:xx:xx:CF:F0
steps
device
insmod rfcomm.ko rtk_btusb.ko
dbus-daemon --config-file=/etc/dbus-1/system.conf
bluetoothd -C &
hciconfig hci0 up
hciconfig hci0 piscan
sdptool add SP
bluetoothctl scan on
bluetoothctl agent on
bluetoothctl default-agent
bluetoothctl trust xx:xx:xx:xx:CF:F0
bluetoothctl pair xx:xx:xx:xx:CF:F0
rfcomm bind 0 xx:xx:xx:xx:CF:F0 1
chmod 666 /dev/rfcomm0
rfcomm connect 0 xx:xx:xx:xx:CF:F0 1
PC
sdptool add SP
rfcomm bind 0 xx:xx:xx:xx:38:A4 1
chmod 666 /dev/rfcomm0
rfcomm watch 0 1
Device show Can't connect RFCOMM socket: Host is down
hciconfig -a output
hci0: Type: BR/EDR Bus: USB
BD Address: 5C:F3:70:1B:38:A4 ACL MTU: 820:8 SCO MTU: 255:16
UP RUNNING PSCAN ISCAN
RX bytes:6888 acl:88 sco:0 events:230 errors:0
TX bytes:4341 acl:84 sco:0 commands:87 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ 5.19'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0xe2f
LMP Version: 4.0 (0x6) Subversion: 0x9f73
Manufacturer: Realtek Semiconductor Corporation (93)
Is any step missed in my procedure?
below steps works for me.
PC side
sdptool add SP
rfcomm -i hci0 watch 0 1 ./picocom /dev/rfcomm0
Device side
sdptool add SP
rfcomm connect 0 xx:xx:xx:xx:xx:F0 1 &
picocom /dev/rfcomm0
reference
I am running a buildroot-generated linux image (kernel 4.11.2) on a nanopi NEO air board, and I struggle to connect to my ruwido remote control.
I can see it when I scan the devices using hcitool :
# hcitool lescan
LE Scan ...
<snip>
5C:F8:21:85:8E:67 ruwido
<snip>
But I cannot get a connection (it acts like the remote is not here) :
# hcitool cc 5C:F8:21:85:8E:67
Can't create connection: Input/output error
The only thing I can do is get some information about it :
# hcitool leinfo 5C:F8:21:85:8E:67
Requesting information ...
Handle: 64 (0x0040)
LMP Version: 4.0 (0x6) LMP Subversion: 0x140
Manufacturer: Texas Instruments Inc. (13)
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
I also cannot use bluetoothctl since it doesn't detect my interface, even though it's initialized, bluetoothd is running and the modules are loaded :
# lsmod
Module Size Used by
bnep 20480 2
hci_uart 61440 1
btbcm 16384 1 hci_uart
btqca 16384 1 hci_uart
btintel 16384 1 hci_uart
bluetooth 348160 12 hci_uart,btintel,btqca,bnep,btbcm
brcmfmac 245760 0
brcmutil 16384 1 brcmfmac
sunxi_cir 16384 0
# ps -e | grep bluetooth
553 root /usr/sbin/bluetoothd
731 root grep bluetooth
# sudo hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: F7:93:3E:74:CF:62 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:12593 acl:7 sco:0 events:292 errors:0
TX bytes:2050 acl:4 sco:0 commands:155 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'NanoPi-NEO-Air'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x0
LMP Version: 4.1 (0x7) Subversion: 0x2209
Manufacturer: Broadcom Corporation (15)
# bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available
My question is, how do I get the remote paired and connected to the board ? It doesn't matter if it's through hcitool, bluetoothctl or another tool.
Update
Thanks to Prabhakar Lad's comment, bluetoothctl is now detecting the interface, however the problem still remains and the problem seems to have narrowed :
# rfkill unblock all
# hciconfig hci0 up
# hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: AA:AA:AA:AA:AA:AA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1930 acl:0 sco:0 events:101 errors:0
TX bytes:1587 acl:0 sco:0 commands:103 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'BlueZ 5.47'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x0
LMP Version: 4.1 (0x7) Subversion: 0x2209
Manufacturer: Broadcom Corporation (15)
# bluetoothctl
[NEW] Controller F7:93:3E:74:CF:62 BlueZ 5.47 [default]
[NEW] Device 5C:F8:21:85:8E:67 ruwido
Agent registered
[bluetooth]# agent on
Agent is already registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller F7:93:3E:74:CF:62 Discovering: yes
<snip>
[NEW] Device 5C:F8:21:85:8E:67 ruwido
<snip>
[bluetooth]# scan off
<snip>
[CHG] Device 5C:F8:21:85:8E:67 RSSI is nil
<snip>
[CHG] Controller F7:93:3E:74:CF:62 Discovering: no
Discovery stopped
[bluetooth]# pair 5C:F8:21:85:8E:67
Attempting to pair with 5C:F8:21:85:8E:67
[CHG] Device 5C:F8:21:85:8E:67 Connected: yes
[ruwido]# [ 501.424858] Bluetooth: hci0 unexpected SMP command 0x0b from 5c:f8:21:85:8e:67
[CHG] Device 5C:F8:21:85:8E:67 Connected: no
[bluetooth]# pair 5C:F8:21:85:8E:67
Attempting to pair with 5C:F8:21:85:8E:67
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
The SMP error seems to be related to bluetooth low-energy security, so am I supposed to use a different tool for pairing ?
Additional information
I actually use the busybox init system with bluetooth init scripts I found in the manufacturer's image (which is nanopi-neo-air_FriendlyCore-Xenial_4.11.2_20171113.img) and adapted so that they could be used with busybox init (the init system on the image is systemd/upstart).
So I have two files :
/etc/init.d/S35brcm_patchram_plus : patches firmware (the card uses an AMPAK ap6212 bluetooth/wifi combo module)
/etc/init.d/S38bluetooth : starts bluetoothd
I use bluez 5.47 with the following options in buildroot 2017.08.1 :
BR2_PACKAGE_BLUEZ_TOOLS=y
# BR2_PACKAGE_BLUEZ_UTILS is not set
BR2_PACKAGE_BLUEZ5_UTILS=y
BR2_PACKAGE_BLUEZ5_UTILS_OBEX=y
BR2_PACKAGE_BLUEZ5_UTILS_CLIENT=y
BR2_PACKAGE_BLUEZ5_UTILS_DEPRECATED=y
# BR2_PACKAGE_BLUEZ5_UTILS_EXPERIMENTAL is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_HEALTH is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_MIDI is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_NFC is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_SAP is not set
BR2_PACKAGE_BLUEZ5_UTILS_TEST=y
# BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL is not set
You didnt go through my complete post, you need to perform following
steps after you have done with rfkill and service restart:
a] bluetoothctl
Start the tool, this should detect the controller
b] [bluetooth]# agent on
Turn on the pairing agent
c] [bluetooth]# scan on
Let bluez detect your device, look in my post it should print you baddr (5C:F8:21:85:8E:67)
d] [bluetooth]# scan off
Turn off scanning once your device is discovered
e] [bluetooth]# pair 5C:F8:21:85:8E:67
Now pair to the device
It should now be paired.
Note: you cannot pair a device until the bluez has scanned it.
I have a Yocto/Open Embedded Linux build for a Gumstix Overo Y COM which I am trying to integrate bluetooth into (using Bluez4).
When I boot my image, the onboard bluetooth module (wilink 8) is unresponsive. Is the configuration I outline below sufficient? If not, what is missing?
The kernel, linux-firmware and bluez4 recipe append are from the meta-gumstix repo [fido] branch (https://github.com/gumstix/meta-gumstix) - one change I have made is the system uses sysvinit instead of systemd.
3.18 kernel with all patches and the defconfig:
meta-gumstix/recipes-kernel/linux/linux-gumstix_3.18.bb
meta-gumstix/recipes-kernel/linux/linux-gumstix-3.18/
Firmware append recipe:
meta-gumstix/recipes-kernel/linux-firmware_git.append
meta-gumstix/recipes-kernel/linux-firmware/linux-firmware/
Bluez4 recipe append:
meta-gumstix/recipes-connectivity/bluez/bluez4_4.101.bbappend
meta-gumstix/recipes-connectivity/bluez/files/
When I boot, this is all hcitool can tell me:
hcitool dev:
parallels#ubuntu:~$ hcitool dev
Devices:
root#overo:~# hcitool scan
Device is not available: No such device
root#overo:~# /usr/sbin/hciattach -n ttyO1 texas
Initialization timed out.
If I start Bluez:
root#overo:~# dmesg | grep -i bluetooth
root#overo:~# bluetoothd -d
root#overo:~# rfcomm bind all
root#overo:~# dmesg | grep -i bluetooth
[ 62.131408] Bluetooth: Core ver 2.19
[ 62.131622] Bluetooth: HCI device and connection manager initialized
[ 62.132080] Bluetooth: HCI socket layer initialized
[ 62.132141] Bluetooth: L2CAP socket layer initialized
[ 62.132263] Bluetooth: SCO socket layer initialized
[ 62.190826] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 62.190856] Bluetooth: BNEP filters: protocol multicast
[ 62.190917] Bluetooth: BNEP socket layer initialized
[ 71.641448] Bluetooth: RFCOMM TTY layer initialized
[ 71.641540] Bluetooth: RFCOMM socket layer initialized
[ 71.641601] Bluetooth: RFCOMM ver 1.11
Then dbus tells me:
root#overo:~# dbus-send --system --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames
method return sender=org.freedesktop.DBus -> dest=:1.2 reply_serial=2
array [
string "org.freedesktop.DBus"
string ":1.0"
string "org.bluez"
string ":1.1"
string ":1.2"
]
root#overo:~#
(root#overo:~# cat introspect_bt.py
#!/usr/bin/env python
import dbus
from xml.etree import ElementTree
def rec_intro(bus, service, object_path):
print(object_path)
obj = bus.get_object(service, object_path)
iface = dbus.Interface(obj, 'org.freedesktop.DBus.Introspectable')
xml_string = iface.Introspect()
for child in ElementTree.fromstring(xml_string):
if child.tag == 'node':
if object_path == '/':
object_path = ''
new_path = '/'.join((object_path, child.attrib['name']))
rec_intro(bus, service, new_path)
bus = dbus.SystemBus()
rec_intro(bus, 'org.bluez', '/org/bluez')
root#overo:~#
)
root#overo:~# python introspect_bt.py
/org/bluez
/org/bluez/1309
/org/bluez/1309/any
I would expect bluez to list an adapter such as /org/bluez/1309/hci0. As neither hcitool or bluez seem to be able to locate my bluetooth module, am I missing something in the setup / configuration?
I'm more than happy to edit this to include any extra information that you might find useful.
Thanks!
Edited with further info:
#parthiban-n -
Bringing the adapter up doesn't work
root#overo:~# hciconfig hci0 up
Can't get device info: No such device
& I don't know where the adapter sits (I think this is the root problem - bluez doesn't seem to know anything about the hardware and doesn't have an adapter for it). Is this something that I can configure myself, or should bluez automatically recognise the module?
I used bluez5 initially with the same results, before downgrading to bluez4 (I'm loath to change back as switching bluez version is a complete delete-cache & rebuild, around 6 hours!). I imagine that as hciconfig & hcitool can't communicate with the BT module the problem was unlikely to be with bluez, AFAIK hci**** don't use bluez for their operation.
#aksonlyaks -
The module is not USB connected, it's an onboard combined WIFI/BT module - the Wilink8 WL1831MOD which seems to use a combined driver for WIFI & BT. The WIFI works fine, so I think it's OK from the driver side of things. Here's some output from /proc/modules & dmesg which looks good to me, but I've posted it up in case there is anything obviously missing:
root#overo:~# cat /proc/modules
rfcomm 34100 0 - Live 0xbf2d3000
bnep 10602 2 - Live 0xbf2cc000
bluetooth 300191 8 rfcomm,bnep, Live 0xbf270000
ipv6 367991 16 [permanent], Live 0xbf1ff000
ctr 3441 2 - Live 0xbf1fb000
ccm 7252 2 - Live 0xbf1f6000
ft6206 3532 0 - Live 0xbf1f2000 (O)
arc4 1688 2 - Live 0xbf1ee000
wl18xx 81650 0 - Live 0xbf1d1000
wlcore 177003 1 wl18xx, Live 0xbf198000
mac80211 478003 2 wl18xx,wlcore, Live 0xbf0fb000
cfg80211 408851 3 wl18xx,wlcore,mac80211, Live 0xbf06a000
rfkill 19564 4 bluetooth,cfg80211, Live 0xbf060000
wlcore_sdio 3947 0 - Live 0xbf058000
twl4030_madc 9173 0 - Live 0xbf052000
industrialio 27152 1 twl4030_madc, Live 0xbf045000
fpgaDrv352 13275 2 - Live 0xbf03e000 (O)
usb_f_ecm 8379 1 - Live 0xbf037000
pwm 6671 0 - Live 0xbf031000 (O)
fpgaCfgDrv 5623 0 - Live 0xbf02c000 (O)
g_ether 3375 0 - Live 0xbf027000
usb_f_rndis 21372 2 g_ether, Live 0xbf01c000
u_ether 14284 3 usb_f_ecm,g_ether,usb_f_rndis, Live 0xbf014000
libcomposite 46775 3 usb_f_ecm,g_ether,usb_f_rndis, Live 0xbf000000
I think wl18xx & wlcore are the main driver components for the WL1831MOD.
root#overo:~# dmesg | grep -i wl
[ 2.430389] twl 0-0048: PIH (irq 23) chaining IRQs 339..347
[ 2.430999] twl 0-0048: power (irq 344) chaining IRQs 347..354
[ 2.437225] twl_rtc 48070000.i2c:twl#48:rtc: Power up reset detected.
[ 2.437805] twl_rtc 48070000.i2c:twl#48:rtc: Enabling TWL-RTC
[ 2.442840] twl_rtc 48070000.i2c:twl#48:rtc: rtc core: registered 48070000.i2c:twl#48 as rtc0
[ 2.511505] twl4030_gpio twl4030-gpio: gpio (irq 339) chaining IRQs 355..372
[ 2.513275] gpiochip_add: registered GPIOs 492 to 511 on device: twl4030
[ 2.524597] twl4030_usb 48070000.i2c:twl#48:twl4030-usb: Initialized TWL4030 USB module
[ 2.531158] input: twl4030_pwrbutton as /devices/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl#48:pwrbutton/input/input0
[ 2.534881] twl4030_keypad 48070000.i2c:twl#48:keypad: OF: linux,keymap property not defined in /ocp/i2c#48070000/twl#48/keypad
[ 2.547119] twl4030_keypad 48070000.i2c:twl#48:keypad: Failed to build keymap
[ 2.554748] twl4030_keypad: probe of 48070000.i2c:twl#48:keypad failed with error -2
[ 2.760864] twl_rtc 48070000.i2c:twl#48:rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 8.107849] twl4030_madc 48070000.i2c:twl#48:madc: clk disabled, enabling
[ 11.101715] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[ 11.224395] wlcore: loaded
[ 19.257476] wlcore: PHY firmware version: Rev 8.2.0.0.195
[ 19.375305] wlcore: firmware booted (Rev 8.8.0.0.13)
[ 23.282714] wlan0: authenticate with 30:b5:c2:66:4c:04
[ 23.306152] wlan0: send auth to 30:b5:c2:66:4c:04 (try 1/3)
[ 23.327819] wlan0: authenticated
[ 23.338958] wlan0: associate with 30:b5:c2:66:4c:04 (try 1/3)
[ 23.345367] wlan0: RX AssocResp from 30:b5:c2:66:4c:04 (capab=0x431 status=0 aid=5)
[ 23.390258] wlan0: associated[ 23.624877] wlcore: Association completed.
It looks like the driver comes up and then there are some wlan related messages, nothing specific to bluetooth operation or intialisation that I can see.
I have two Bluetooth adapters, an old internal adapter and a new Bluetooth 4.0 adapter.
I am writing an application that uses a socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_L2CAP) to connect to a Bluetooth LE device on Linux. When I call connect() with a sockaddr_l2 {.l2_family = AF_BLUETOOTH, .l2_bdaddr = {...}, .l2_cid = L2CAP_CID_ATT, .l2_bdaddr_type = BRADDR_LE_PUBLIC}, connect fails with errno=0x38000000=939524096 Unknown error, because Linux arbitrarily chooses the old adapter that only supports Bluetooth 2.1, not Bluetooth 4.0. The solution is to bind the socket to the bd_addr of the adapter that supports Bluetooth 4.0.
Question: How to tell which adapter is the Bluetooth 4.0 adapter? hciconfig does not tell which one is the one to use; they both say BR/EDR and not LE.
$ hciconfig
hci1: Type: BR/EDR Bus: USB
BD Address: 00:25:00:F6:97:F0 ACL MTU: 1021:5 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1074 acl:0 sco:0 events:56 errors:0
TX bytes:1462 acl:0 sco:0 commands:56 errors:0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:02:72:D6:A0:BF ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:146505 acl:328 sco:0 events:4189 errors:0
TX bytes:6213 acl:215 sco:0 commands:83 errors:0
$ modinfo bluetooth | grep ^version:
version: 2.17
$ modinfo btusb | grep ^version:
version: 0.6
$ lsb_release --description
Description: Ubuntu 14.04.1 LTS
$ uname --kernel-release
3.13.0-40-generic
To answer your question there is btmgmt info which will list the HCI version (on the same line as addr), you will have to look into Host Controller Interface Assigned numbers for the meaning of the numbers, version 6 below mean Bluetooth 4.0.
# btmgmt info
hci0: Primary controller
addr 5C:F3:70:XX:XX:XX version 6 manufacturer 15 class 0x1c010c
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: powered bondable ssp br/edr le secure-conn
name BlueZ 5.47
short name
If you need to know if the adapter support LE, you will have to look for le in Supported settings: because LE is not mandatory in bluetooth 4.0/4.1.
Try: hciconfig hci[0|1] version
I use dual boot for linux/windows.
I'm trying to install wireless driver on Debian_3.16-0.bpo.3-amd64 (bpo is for backport) Wheezy for my MSI laptop (MSI GP60 2PE Leopard).
I made lspci -nn to find reference about my network controller:
Network controller [0280]: Intel Corporation Device [8086:08b3] (rev 83)
So on the website of linux Wireless
My driver must be this one : iwlwifi
I installed it,
apt-get install firmware-iwlwifi
modprobe iwlwifi
but it doesn't work...
During the boot, there are some errors :
Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 4.847284] Copyright(c) 2003- 2014 Intel Corporation
[ 4.847449] iwlwifi 0000:05:00.0: irq 50 for MSI/MSI-X
[ 4.877181] mei_me 0000:00:16.0: irq 51 for MSI/MSI-X
[ 4.923823] iwlwifi 0000:05:00.0: firmware: failed to load iwlwifi-3160-9.ucode (-2)
[ 4.923877] iwlwifi 0000:05:00.0: Direct firmware load failed with error -2
[ 4.923878] iwlwifi 0000:05:00.0: Falling back to user helper
[ 4.940971] Bluetooth: Core ver 2.19
[ 4.940987] NET: Registered protocol family 31
[ 4.940988] Bluetooth: HCI device and connection manager initialized
[ 4.940996] Bluetooth: HCI socket layer initialized
[ 4.940998] Bluetooth: L2CAP socket layer initialized
[ 4.941006] Bluetooth: SCO socket layer initialized
If this can help you, I made modinfo iwlwifi and this is the output :
http://pastebin.com/s8ycnBwu
To make sure that Aptitude package firmware-iwlwifi contains drivers for your device, lookup drivers from chip manufactor web sites...
I recommend to compare Kernel version and intel iwlwifi driver version, from: http://www.intel.com/support/wireless/wlan/sb/CS-034398.htm
and how to guides can be found on: http://wireless.kernel.org/en/users/Drivers/iwlwifi
With these links I hope you can find your own iwlwifi package, if it's supported.
You can check chipset via Windows Device Management...