| Summary: | Intel Wireless 7260 doesn't easily connect with wlp4s0 as drakx-net-applet still prefers to use enp5s0 when logging in to KDE | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | ftg, lovaren, mageia, marja11 |
| Version: | 5 | ||
| Target Milestone: | Mageia 6 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-net-applet | CVE: | |
| Status comment: | |||
| Attachments: |
Result of the journalctl command
Content of the ifcfg-wlp4s0 Output of modinfo iwlwifi Output of find /etc/systemd Output from drakconnect |
||
|
Kristoffer Grundström
2016-07-25 01:17:15 CEST
Priority:
Normal =>
High Are you absolutely sure that NM isn't running and trying to control the wifi device ? Try "journalctl -a -b -u NetworkManager" to see if NM is running and what it's doing. Also, check the /etc/sysconfig/network-scripts/ifcfg-xxx file to see if the wifi is being controlled by NM ("auto" probably equals "yes").
The difference in your scenario may be that by the time it works NM may have given up and net-applet has successfully taken over. Prior to that, lt may be a case of "duelling banjos" as NM and net-applet slug it out.CC:
(none) =>
ftg Created attachment 8255 [details]
Result of the journalctl command
Created attachment 8256 [details]
Content of the ifcfg-wlp4s0
I haven't had this issue at all in Ubuntu 15.04 and newer versions so I'd like to know how they've solved it. lspci -k shows: 04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Kernel driver in use: iwlwifi Kernel modules: iwlwifi dmesg | grep firmware shows: [ 9.830818] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2 [ 11.183140] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq [ 11.335335] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 20.449321] r8169 0000:05:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2 [ 69.883791] iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 80.446909] r8169 0000:05:00.0 enp5s0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-11) I'm no expert, but I think this issue exists in Arch Linux since January, look here: https://bbs.archlinux.org/viewtopic.php?id=207816 That thread mentions to check the kernel git and as I went there I saw that Mageia lacks of a binary called iwlwifi-7265D-22.ucode. Not sure if that really solves the issue, but urpmq -y ucode gives me following hits: iwlwifi-3945-ucode iwlwifi-4965-ucode iwlwifi-agn-ucode The first number (4 as an example) matches the card models serie that the binary is made for. Am I wrong? Here's some more information that might be relevant as well: https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi#About_iwldvm_support_and_known_issues Created attachment 8257 [details]
Output of modinfo iwlwifi
Seems like there is no matching firmware for my card.
Created attachment 8258 [details]
Output of find /etc/systemd
The wpa_supplicant version that Mageia 5 has seems to be a bit old. Maybe an update would do the trick? (In reply to Kristoffer Grundström from comment #9) > The wpa_supplicant version that Mageia 5 has seems to be a bit old. Maybe an > update would do the trick? https://w1.fi/releases/wpa_supplicant-2.5.tar.gz is the latest stable version. But if the problem is missing firmware, how do you account for the workaround in comment#1 working ? Maybe one firmware can be set to act as another firmware. I don't know. My bad! I just found this: [root@localhost ~]# modinfo iwlwifi | grep 7260 firmware: iwlwifi-7260-13.ucode 13 is still to old. 22 is the latest. Created attachment 8263 [details]
Output from drakconnect
Is ifplugd the cause of the fail?
Marja Van Waes
2016-07-27 22:47:39 CEST
CC:
(none) =>
mageia, marja11 I believe that this can now be closed as wpa_supplicant has been updated to 2.5 in Cauldron. I haven't test it yet, but I will. (In reply to Kristoffer Grundström from comment #15) > I believe that this can now be closed as wpa_supplicant has been updated to > 2.5 in Cauldron. I haven't test it yet, but I will. Closing then Status:
NEW =>
RESOLVED |
Description of problem: I recently installed Mageia 5 without using Backports and Testing medias. I choose to install GNOME, KDE, Cinnamon and MATE as desktop environments and when I log in to KDE wlp4s0 isn't started and/or connected. I know I gave the right password for the WiFi and somehow it feels like something is preventing me to connect to my connection. I did check rfkill list if anything is blocked and it isn't blocked at all. I'm not letting NetworkManager to control wlp4s0 as that hasn't either been much successful and I choose to tick the box only for wlp4s0 to be used at reboot. lspcidrake shows: r8169 : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (rev: 0c) iwlwifi : Intel Corporation|Wireless 7260 [NETWORK_OTHER] (rev: 6b) in case the names of both card types is needed. lshw says this about my computer model: product: N550JK (ASUS-NotebookSKU) vendor: ASUSTeK COMPUTER INC. Version-Release number of selected component (if applicable): 2.24.2 How reproducible: Every installation. Steps to Reproduce: 1. Install Mageia 5 without Testing medias or Backports medias. 2. Choose to install MATE, KDE, GNOME and Cinnamon. 3. Boot the 4.4.13-desktop-1.mga5 kernel and log in to KDE. 4. Make sure you're fully up-to-date and install any missing drivers (if any) when checking with harddrake2. 5. Untick the box for enp5s0 so that it won't be used after reboot and tick the box for wlp4s0 to be used after reboot. 6. The connection manager/setup guide will fail to up the wlp4s0 interface and it will also fail at reboot. 7. I don't have any cable connected to the Ethernet card, but net-applet still discovers it as a the main interface to connect with. The only temporary working solution to this is: Delete the wlp4s0 interface and recreate it by opening drakconf and clicking Create a new connection interface and when it fails to add the new WiFi interface rightclick the net-applet icon and change from Discover automatically to wlp4s0 and then also rightclick net-applet again and click wlp4s0 and it will start to work.