Bug 201647 - Intel Wireless card 3165 does not get detected but bluetooth works
Summary: Intel Wireless card 3165 does not get detected but bluetooth works
Status: CLOSED WILL_NOT_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: Intel Linux
: P1 high
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-09 10:10 UTC by Mert Arguc
Modified: 2019-03-22 13:40 UTC (History)
4 users (show)

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


Attachments
Contains outputs of dmesg and lspci (18.41 KB, application/gzip)
2018-11-09 10:10 UTC, Mert Arguc
Details
dmesg (v4.19) (63.72 KB, text/plain)
2018-11-09 18:46 UTC, Bjorn Helgaas
Details
lspci (7.18 KB, text/plain)
2018-11-09 18:47 UTC, Bjorn Helgaas
Details
lspci -vv (30.40 KB, text/plain)
2018-11-10 11:43 UTC, Mert Arguc
Details
Kernel .config file (216.99 KB, text/plain)
2018-11-30 13:36 UTC, Mert Arguc
Details
Windows 10 Device Manager info (34.12 KB, image/jpeg)
2018-12-11 11:55 UTC, Mert Arguc
Details
Windows 10 Hardware IDs (99.38 KB, image/jpeg)
2018-12-11 19:10 UTC, Mert Arguc
Details
sudo lspci -A intel-conf1 (2.07 KB, text/plain)
2018-12-12 22:32 UTC, Mert Arguc
Details
lsmod (6.70 KB, text/plain)
2018-12-12 23:32 UTC, Mert Arguc
Details
Aida 64 hardware dump (610.79 KB, text/html)
2018-12-13 12:14 UTC, Mert Arguc
Details
sudo acpidump (521.97 KB, text/plain)
2018-12-14 17:33 UTC, Mert Arguc
Details

Description Mert Arguc 2018-11-09 10:10:44 UTC
Created attachment 279385 [details]
Contains outputs of dmesg and lspci

This bug affects most of the devices with a Celeron N4000 and an Intel wifi 3165 Ac adapter.

When using Linux wifi is not working however, Bluetooth is working fine.
Also, Bluetooth part of this chip is connected via btusb and the wifi part of this chip is connected via PCIe.

I have contacted the Linux wireless team of Intel, which suggested me to report this bug as a PCIe bug.
Comment 1 Bjorn Helgaas 2018-11-09 18:46:45 UTC
Created attachment 279395 [details]
dmesg (v4.19)
Comment 2 Bjorn Helgaas 2018-11-09 18:47:05 UTC
Created attachment 279397 [details]
lspci
Comment 3 Mert Arguc 2018-11-10 11:43:07 UTC
Created attachment 279405 [details]
lspci -vv
Comment 5 Emmanuel Grumbach 2018-11-24 15:25:21 UTC
Bjorn, I can't see the wifi device in lspci so we can't do much here. Do you have an idea?
Comment 6 Mert Arguc 2018-11-24 22:35:24 UTC
Do you need any outputs/screenshots from Windows 10 or Linux?
Pictures of the Intel wifi 3165(it`s soldered on the mainboard)?
The Networkadapter works perfect on Windows 10, maybe take a look at the Windows driver of this device?

http://www.trekstor.de/produkte/notebook/detail-notebook/product/SURFBOOK%20A13B-PO%20GEM.html?file=files/userFiles/products/surfbook_A13B/Surfbook-A13B_2018-07-19.zip
Comment 7 Mert Arguc 2018-11-30 13:36:56 UTC
Created attachment 279757 [details]
Kernel .config file
Comment 8 Mert Arguc 2018-12-11 11:55:03 UTC
Created attachment 279949 [details]
Windows 10 Device Manager info
Comment 9 Mert Arguc 2018-12-11 19:10:45 UTC
Created attachment 279955 [details]
Windows 10 Hardware IDs
Comment 10 Emmanuel Grumbach 2018-12-11 21:51:06 UTC
Can you please attach the output of:

sudo lspci -A intel-conf1


Thanks.

PS: I am taking this back to wireless even I am not sure what we can do from there, but it'll be easier for me to track it this way. Since Bjorn said he can't do anything on his side, it won't help to let it stay on PCI anyway.
Comment 11 Mert Arguc 2018-12-12 22:32:38 UTC
Created attachment 279973 [details]
sudo lspci -A intel-conf1
Comment 12 Emmanuel Grumbach 2018-12-12 23:07:24 UTC
Ok thanks. Unfortunately, still no luck.

What I do see is that your device is on PCI Slot2. Maybe it is because of that?

Out of curiosity: if you do this as root:

echo 1 > /sys/bus/pci/rescan

Does it change the lspci output?
Comment 13 Mert Arguc 2018-12-12 23:16:52 UTC
No,the Output is still the same.
Comment 14 Emmanuel Grumbach 2018-12-12 23:21:16 UTC
You say the bug affects most of the devices.... What is the difference between the devices that do work and those that don't?
Additionally, please attach the output of lsmod.
Comment 15 Mert Arguc 2018-12-12 23:32:53 UTC
Created attachment 279975 [details]
lsmod
Comment 16 Mert Arguc 2018-12-12 23:43:11 UTC
Well, working devices do have the m.2 3165 or just another Wi-Fi chip. 
But a larger number of not working devices like my Trekstor A13B, Teclast F5 and other cheap(mostly Chinese) laptops do have a SOLDERED 3165.
I don't know if this is relevant but I cannot find any another difference between these devices.
Comment 17 Emmanuel Grumbach 2018-12-13 06:44:50 UTC
Can you try to pass pci=noacpi to the kernel?

That may cause other issues. But I noticed that the WiFi device is on another PCI slot: PCI Slot 2.
This can very well be the reason. BIOSes can sometimes hide devices from non Windows OSes...
Comment 18 Mert Arguc 2018-12-13 11:57:55 UTC
No, it is still not working.
Well, it created issues like M.2 ssd not working or trackpad not working but bluetooth on the 3165 still worked fine.
Comment 19 Emmanuel Grumbach 2018-12-13 12:08:15 UTC
Care to send the lspci in that config?

Although I guess it'll be the same.
Comment 20 Mert Arguc 2018-12-13 12:14:34 UTC
Created attachment 279991 [details]
Aida 64 hardware dump

Raw hex dump inside
Comment 21 Mert Arguc 2018-12-13 12:26:54 UTC
The output of lspci is the same nothing changed.
Comment 22 Len Brown 2018-12-14 17:20:19 UTC
please attach the output from acpidump  eg.

 # acpidump > attach-this-file
Comment 23 Mert Arguc 2018-12-14 17:33:10 UTC
Created attachment 280023 [details]
sudo acpidump
Comment 24 Emmanuel Grumbach 2018-12-17 11:58:43 UTC
Personally, I really don't know how to make any progress here.
I'll keep this open, but remove the assignment on my team.

@Len, if you think you can do something with the acpidump, please go ahead.
Comment 25 Thymidin 2019-03-22 13:40:45 UTC
Hi,
I use the Ezbook x1 which basically have the exact same problem and have heard about a BIOS update (AMI bios) that solved this problem on the teclast F5. I don't know how to send it but I have the two versions of the BIOS if that can help solving this problem.

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