Bluetooth/Wifi config

wheelsg · 05-13-2016, 02:07 PM

I'm creating a dual-boot UEFI-based beastie and wifi is driving me (pun intended) out of my mind. The machine is a Thinkpad Yoga 11e with installed wired and wireless functionality. Unfortunately, under 14.1 I'm unable to configure the wireless interface. I know enough about the Intel (7260-based) wifi/BT card to know it might want a newer kernel (uses iwlmvm and firmware, both of which are present on the machine) but I also can't get a USB wifi adapter to initialize. Both wifi devices are 802.11ac, so I may have no alternative but to upgrade the kernel. What I'm asking for now is some guidance on massaging the startup routine to at least attempt to load on startup. Here are a few details on the card (lspci with only one 'v.')

Code:

04:00.0 Network controller: Intel Corporation Intel(R) Dual Band Wireless-AC 7260 (rev c3)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7260
	Flags: bus master, fast devsel, latency 0, IRQ 255
	Memory at 90500000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 4c-eb-42-ff-ff-e7-3a-24
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?>

What appears to happen is that the device get initialized as a bluetooth adapter (which can be listed w/ 'rfkill list') but nothing more.

Main question: How can I direct the module (iwlmvm) to the card? I seem to remember a routine that would generate the 70-persistent-net rules for udev. Anyone else remember that, or am I more addled than usual?

Thanks,
Geoff.

onebuck · 05-14-2016, 08:02 AM

Hi,

You could try; 'rm /etc/udev/rules.d/70-persistent-net.rules' to delete that rule then reboot. When you reboot the '/etc/udev/rules.d/70-persistent-net.rules' should be regenerated. Hopefully then you will have a recognized device. Be sure to have the firmware for that device. Look at 'dmesg' or do a 'lspci -vv' to view any device information.

Hope this helps.
Have fun & enjoy!

bassmadrigal · 05-14-2016, 09:53 AM

It looks like it recognizes the card fine. Otherwise, it wouldn't show the model number in the name. What is the output of iwconfig?

Also, I'm not seeing the kernel module being used, so please post the output of

Code:

lspci -k | -iA3 net

wheelsg · 05-14-2016, 01:34 PM

I think I'll only end up with the 70-persistent... I already have, that is, it's pointing to the ethernet port. Since the card is not being initialized, there'll be no discovery possible.

I've opened up 'WLAN0' in rc.inet1.conf, but iwconfig shows no wireless extensions and no 'wlan' device. While kernel modules show up (obviously) for the ethernet slot, no modules are listed as used in the wifi slot. This would explain the wlan0 device not being created.

Can you still 'alias' in rc.local? Even though the ucode is stored properly, modprobing doesn't seem to latch the driver to the card.

wheelsg · 05-14-2016, 01:45 PM

Also, bossmadrigal, what is the piping you listed in the

Code:

lspci -k | -iA3 net

?

Thanks,
Geoff.

wheelsg · 05-14-2016, 01:54 PM

Here's the output of dmesg regarding the two sides of the card...

Quote:

[ 4.964928] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[ 4.966843] Bluetooth: hci0 failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq(-2)
[ 4.975576] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.bseq
[ 4.982923] Bluetooth: hci0: Intel Bluetooth firmware patch completed
--
[ 6.103972] Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 6.103974] Copyright(c) 2003-2013 Intel Corporation
[ 6.107150] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 6.109745] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 6.112351] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 6.114934] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 6.117567] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 6.120334] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

onebuck · 05-14-2016, 04:20 PM

Hi,

Quote:

Originally Posted by wheelsg

I think I'll only end up with the 70-persistent... I already have, that is, it's pointing to the ethernet port. Since the card is not being initialized, there'll be no discovery possible.

I've opened up 'WLAN0' in rc.inet1.conf, but iwconfig shows no wireless extensions and no 'wlan' device. While kernel modules show up (obviously) for the ethernet slot, no modules are listed as used in the wifi slot. This would explain the wlan0 device not being created.

Can you still 'alias' in rc.local? Even though the ucode is stored properly, modprobing doesn't seem to latch the driver to the card.

In your OP you were asking how to regenerate the rule and that is the way to regenerate by removing the rule then reboot.

Plus the correct command would be ' lspci -k | grep -iA3 net' to get;

Code:

lspci -k | grep -iA3 net
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] (rev 34)
        Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
--
0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06)
        Subsystem: Dell Device 04b7
        Kernel driver in use: r8169
        Kernel modules: r8169

Hope this helps.
Have fun & enjoy!

bassmadrigal · 05-14-2016, 06:07 PM

Quote:

Originally Posted by wheelsg

Also, bossmadrigal, what is the piping you listed in the

Code:

lspci -k | -iA3 net

?

Thanks,
Geoff.

Crap, it was supposed to be grep

Code:

lspci -k | grep -iA3 net

wheelsg · 05-26-2016, 03:33 PM

Thank you both, and as stated, iwlmvm does not get hooked in. I suspect the bluetooth gets initialized first and closes the door for anything looking to speak to the adapter. Here's the output of lspci (piped to grep):

Quote:

04:00.0 Network controller: Intel Corporation Intel(R) Dual Band Wireless-AC 7260 (rev c3)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 10)
Subsystem: Lenovo Device 2224
Kernel driver in use: r8169
Kernel modules: r8169

Now, since you've been so kind to hold my hand this far, here's my next question. I didn't pay enough attention when udev hit the scene, but I'm thinking if I blacklist the bluetooth and rename (or delete) the persistent-net file I might have a shot at initializing w/ the 7260 ucode. But, like the Thermos(TM), how will it know? That is, how can I direct the two modules (r8169 & iwlmvm) to their respective slots? I actually did a manual add on another dual nic machine, but I forget how I got to populate the 'fields' of the persistent rule file.

The other way to go might be to roll the iwlmvm support into the kernel. Intel is also stating that a newer version of the ucode works under the "4" series, so an upgrade might solve some of this heartache. I'm not squeamish, I've rolled kernels before, the dual nic machine I mentioned is a PII-Pro with an obscure gfx card so I had _lots_ of fun with that - and more hair before I started. And if I ever figure out how to choose multiple kernels to boot (before you guffaw, I use lilo - well now it's Elilo) given the config and module pointers.

As 'proof of concept,' I'd like to try the blacklist option first. Pointers?

Thanks,
Geoff.