Bug 60577 - WiFi doen't work on Intel WiMAX/WiFi Link 5150
Summary: WiFi doen't work on Intel WiMAX/WiFi Link 5150
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-18 13:18 UTC by Arthur Sudneko
Modified: 2014-05-08 05:43 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.9.9-1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lspci -vv (11.70 KB, text/plain)
2013-07-18 13:18 UTC, Arthur Sudneko
Details
modinfo iwlwifi (10.76 KB, text/plain)
2013-07-18 13:25 UTC, Arthur Sudneko
Details
sudo lspci -xxx (17.16 KB, text/x-log)
2013-07-18 14:36 UTC, Arthur Sudneko
Details
dmesg (58.30 KB, text/x-log)
2013-07-18 14:38 UTC, Arthur Sudneko
Details
fix for missing NIC (1.28 KB, patch)
2013-07-18 16:14 UTC, Emmanuel Grumbach
Details | Diff
fix for missing NIC (1.28 KB, patch)
2013-07-18 16:16 UTC, Emmanuel Grumbach
Details | Diff

Description Arthur Sudneko 2013-07-18 13:18:43 UTC
Created attachment 106926 [details]
lspci -vv

I have notebook Dell 11z with WiMAX/WiFi adapter Intel Link 5150. 
When I tried to list network interfaces, i didn't see any WiFi interfaces.

>ifconfig

enp0s29f7u5: flags=129<UP,NOARP>  mtu 1400
        ether 00:1d:e1:1b:40:a2  txqueuelen 20  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
enp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:26:b9:c8:83:86  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 212  bytes 18372 (17.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 212  bytes 18372 (17.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

BTW: enp2s0  - ethernet, enp0s29f7u5 - WiMax 

Module for my WiFi adapter named iwlwifi.
> lsmod | grep iwlwifi

iwlwifi    173477 0
cfg        510937 1 iwlwifi


But, when i tried to list pci devices (lspci -vv), i didn't see string  "driver in use: iwlwifi" string in this:

08:00.0 Network controller: Intel Corporation WiMAX/WiFi Link 5150
        Subsystem: Intel Corporation Device 1326
        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 11
        Region 0: Memory at f0600000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: <access denied>

(the full "lspci -vv" in the attachment)
Comment 1 Arthur Sudneko 2013-07-18 13:22:42 UTC
> rfkill list all

0: compal-wifi: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: compal-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: i2400m-usb:2-5:1.0: WiMAX
	Soft blocked: yes
	Hard blocked: no



I tried to install Debian 6 with 2.6.* kernel and iwlagn-module for intel wifi cards but met the same problem.
Comment 2 Arthur Sudneko 2013-07-18 13:25:42 UTC
Created attachment 106927 [details]
modinfo iwlwifi
Comment 3 Emmanuel Grumbach 2013-07-18 14:00:25 UTC
I need sudo lspci -xxx

and dmesg
Comment 4 Arthur Sudneko 2013-07-18 14:36:54 UTC
Created attachment 106930 [details]
sudo lspci -xxx
Comment 5 Arthur Sudneko 2013-07-18 14:38:13 UTC
Created attachment 106931 [details]
dmesg
Comment 6 Arthur Sudneko 2013-07-18 14:39:54 UTC
(In reply to Arthur Sudneko from comment #5)
> Created attachment 106931 [details]
> dmesg

in attach
Comment 7 Emmanuel Grumbach 2013-07-18 16:14:18 UTC
Created attachment 106936 [details]
fix for missing NIC

This will fix the issue
Comment 8 Emmanuel Grumbach 2013-07-18 16:16:11 UTC
Created attachment 106937 [details]
fix for missing NIC

sorry - take this one.
Comment 9 Arthur Sudneko 2013-07-24 16:06:31 UTC
(In reply to Emmanuel Grumbach from comment #8)
> Created attachment 106937 [details]
> fix for missing NIC
> 
> sorry - take this one.

Thank You! After patching the kernel in the output of "lspci -vvv" has item: 

Kernel driver in use: iwlwifi

But in ifconfig, or iwconfig dows not find a WiFi interface (
Comment 10 Emmanuel Grumbach 2013-07-24 16:21:40 UTC
Do you have the supplicant running?
Comment 11 Emmanuel Grumbach 2013-07-24 16:22:05 UTC
did you do ifconfig wlan0 up?
what with ifconfig -a?

dmesg output?
Comment 12 Arthur Sudneko 2013-07-24 16:32:59 UTC
(In reply to Emmanuel Grumbach from comment #10)
> Do you have the supplicant running?

no. i use network-manager

(In reply to Emmanuel Grumbach from comment #11)
> did you do ifconfig wlan0 up?
> what with ifconfig -a?
> 
> dmesg output?

> ifconfig wlan0 up

wlan0: ERROR while getting interface flags: No such device

> ifconfig -a 
enp0s29f7u5: flags=129<UP,NOARP>  mtu 1400
        ether 00:1d:e1:1b:40:a2  txqueuelen 20  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:26:b9:c8:83:86  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


> dmesg 
http://pastebin.com/Fwpe1XdE
Comment 13 Emmanuel Grumbach 2013-07-24 17:39:06 UTC
please send your config file
Comment 14 Arthur Sudneko 2013-07-24 18:00:03 UTC
(In reply to Emmanuel Grumbach from comment #13)
> please send your config file

What config do you mean?
Comment 15 Emmanuel Grumbach 2013-07-24 18:09:45 UTC
config file of the kernel
Comment 16 Arthur Sudneko 2013-07-24 18:31:02 UTC
(In reply to Emmanuel Grumbach from comment #15)
> config file of the kernel

http://pastebin.com/hP716sk1
Comment 17 Emmanuel Grumbach 2013-07-24 18:33:36 UTC
can you add debug?

modprobe iwlwifi=0xffffffff
Comment 18 Emmanuel Grumbach 2013-07-24 18:38:28 UTC
did you edit your config file manually?
Comment 19 Emmanuel Grumbach 2013-07-24 18:40:12 UTC
Can you please run
make oldconfig and recompile your kernel?
Comment 20 Arthur Sudneko 2013-07-24 18:46:29 UTC
(In reply to Emmanuel Grumbach from comment #17)
> can you add debug?
> 
> modprobe iwlwifi=0xffffffff

modprobe: FATAL: Module iwlwifi=0xffffffff not found.

> modprobe iwlwifi = 0xffffffff

When I run this command, no information has emerged.

(In reply to Emmanuel Grumbach from comment #18)
> did you edit your config file manually?

No I didn't.


(In reply to Emmanuel Grumbach from comment #19)
> Can you please run
> make oldconfig and recompile your kernel?

Ok. But it will take two to three hours (((
Comment 21 Arthur Sudneko 2013-07-24 18:52:26 UTC
(In reply to Emmanuel Grumbach from comment #18)
> did you edit your config file manually?

No i didn't. I have compiled a new kernel using this guide: http://fedoraproject.org/wiki/Building_a_custom_kernel and applied your patch in file kernel.spec.
Comment 22 Emmanuel Grumbach 2013-07-24 19:02:23 UTC
(In reply to Arthur Sudneko from comment #20)
> (In reply to Emmanuel Grumbach from comment #17)
> > can you add debug?
> > 
> > modprobe iwlwifi=0xffffffff
> 
> modprobe: FATAL: Module iwlwifi=0xffffffff not found.
> 
> > modprobe iwlwifi = 0xffffffff
> 
> When I run this command, no information has emerged.
> 


Err...

modprobe -r iwlwifi

modprobe iwlwifi debug=0xffffffff
Comment 23 Arthur Sudneko 2013-07-24 19:06:08 UTC
(In reply to Emmanuel Grumbach from comment #22)
> (In reply to Arthur Sudneko from comment #20)
> > (In reply to Emmanuel Grumbach from comment #17)
> > > can you add debug?
> > > 
> > > modprobe iwlwifi=0xffffffff
> > 
> > modprobe: FATAL: Module iwlwifi=0xffffffff not found.
> > 
> > > modprobe iwlwifi = 0xffffffff
> > 
> > When I run this command, no information has emerged.
> > 
> 
> 
> Err...
> 
> modprobe -r iwlwifi
> 
> modprobe iwlwifi debug=0xffffffff

Tried it. No messages.
Comment 24 Johannes Berg 2013-07-24 19:06:50 UTC
Emmanuel, I think you got a bit confused -- IWLWIFI_OPMODE_MODULAR doesn't exist on 3.9.x, only starting later. I don't think rebuilding the kernel will do anything. I just did an oldconfig with Arthur's config on stock 3.9.9 and nothing really changed.
Comment 25 Johannes Berg 2013-07-24 19:10:26 UTC
Does anything change if you 'modprobe iwldvm'?
Comment 26 Arthur Sudneko 2013-07-24 19:15:23 UTC
(In reply to Johannes Berg from comment #25)
> Does anything change if you 'modprobe iwldvm'?

It's work!!! After this command i have a new interface wlp8s0 and it's my wifi)))

Thank you!
Comment 27 Johannes Berg 2013-07-24 19:23:17 UTC
Ok? So I guess something is wrong with module loading on your distro.
Comment 28 Arthur Sudneko 2013-07-24 19:28:01 UTC
(In reply to Johannes Berg from comment #27)
> Ok? So I guess something is wrong with module loading on your distro.

mmm i tried many others: arch, debian 6, debian 7, ubuntu and mint) But they were without the patch from Emmanuel )) Maybe I'll try Arch Linux when I have some free time.
Comment 29 Arthur Sudneko 2013-07-24 19:39:01 UTC
Tried 'modprobe iwldvm' on an unpatched kernel.  The WiFi interface does not appear. )))

Emmanuel and Johannes! Than you very much!

Note You need to log in before you can comment on or make changes to this bug.