Description of problem: Upon installation of Mageia 5, I have no wireless, and came to find out that it is not supported in Mageia 5. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Try to install Windows driver with ndiswrapper from Mageia Control Center 2. A dialog box comes up asking to install the Windows driver 3. Choose this option, direct it to the netathrx.inf (which is the file required along with its .sys, which is in the same folder) 4. Another dialog box pops up saying "Unable to load the ndiswrapper interface." There is also a thread on this at the Mageia forums; it began at bjoernvold. I admittedly did not understand a lot of what was said in the thread at the Mageia forum to do. I had asked for a simple fix, and for me it is not simple, what happened in that thread, as these are things I have never had to deal with before, and on top of it since it has been a good three years since I've been able to use Linux, have lost some skills. I have come to find out that this driver is unsupported in the out of the box kernel for Mageia 5. I have tried testing distros with 4.0-4.2 kernels, and they did not yet support this chipset. The Qualcomm Atheros QCA6X74 is also bluetooth. Wireless is all I have to connect with, and can do so fine in Windows 8.1, where I am now filing this. There is an upstream bug on this particular wireless module at https://bugzilla.kernel.org/show_bug.cgi?id=101651. I have commented there but could not give specifics, such as outputs from cli, or the like, as I was on Windows. I have tried several things: 1) install windows driver via ndiswrapper -i optional - check if driver was installed and if ndiswrapper sees the actual wireless device via ndiswrapper -l 2) add the modprobe alias via ndiswrapper -m 3) actually load the wrapped driver via modprobe ndiswrapper When I tried ndiswrapper -i, there was an error, so I ran it again and it said that the device was already present. When I ran ndiswrapper -l, there was no output at all. When I ran modprobe ndiswrapper, the output stated that the alias had already been made. Then, I went to drakconnect to make the connection for the wireless, and a dialog box popped up, and asked for the Windows driver for ndiswrapper, I pointed it to where the Windows driver was, continued on, and the dialog box came up stating that it was unable to use the ndiswrapper interface. I am wondering why drakconnect asked for the Windows driver when I had already installed it via ndiswrapper -i, and it stated that the device was present in the first place? Since that process did not work, I went to kvalo and downloaded the drivers there,and placed them in their corresponding directories in /lib/firmware and rebooted. There was still no wireless, and I still could not make a connection in drakconnect. ndiswrapper gave me no outputs at all, other than when I would try ndiswrapper -i again, which still states that the device is present. From the Mageia forum thread: [root@localhost ~]# ndiswrapper -l netathrx : driver installed device (168C:003E) present [root@localhost ~]# [root@localhost ~]# lsmod | grep ndis [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# iwconfig enp2s0 no wireless extensions. lo no wireless extensions. [root@localhost ~]# I have no output now when I run: journalctl -ab | grep -iE "ath10k|atheros" I am unsure as to if I'm having issues with ndiswrapper itself; my own contention is that I am, but I do not know what to do with them. The kernel patch for this (*I think* at kvalo?) I do not understand how to use at all. Appreciating any help that can be offered here. I would like to see this chipset supported in Mageia, but from what I understand they are close upstream, but still not "there" to where the drivers can be placed yet packaged with a distribution. A fair part of this is my own confusion of things. Reproducible: Steps to Reproduce:
Severity: normal => major
CC: (none) => dedanna1029
That hw (going by the pci ids) should be supported by the 4.1.8 kernel released last week, but QCA has not pushed the needed older firmwares upstream... So you could try to remove your ndiswrapper configuration, then download: https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/10.1/firmware-2.bin_10.1.467.3-1 and save it as: /lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin And download: https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/10.2/firmware-3.bin_10.2.2.39.6-1 and save it as: /lib/firmware/ath10k/QCA988X/hw2.0/firmware-3.bin After that reboot and see if you can configure the wireless connection. If not, please provide bootlogs and lspcidrake by doing (as root): journalctl -b >journal-bug16915 lspcidrake -v >lspcidrake-bug16915 and then attach journal-bug16915 and lspcidrake-bug16915 to this bugreport
CC: (none) => tmbAssignee: bugsquad => tmbSource RPM: kernel => kernel, kernel-firmware-nonfree
This is going to sound ignorant or dumb, but I really don't know. How do I remove the ndiswrapper configuration? Thanks!
going by the ndiswrapper -l output above I think: ndiswrapper -e netathrx would do it....
Created attachment 7094 [details] journal-bug16915 I ran the ndiswrapper -e netathrx, and then proceeded to do the rest you asked for in order. I'm still running into issues. Thanks!
Created attachment 7095 [details] lspcidrake-bug16915
(In reply to Thomas Backlund from comment #1) > That hw (going by the pci ids) should be supported by the 4.1.8 kernel > released last week, but QCA has not pushed the needed older firmwares > upstream... > > So you could try to remove your ndiswrapper configuration, > > then download: > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/10.1/firmware-2. > bin_10.1.467.3-1 > > and save it as: > /lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin > > And download: > https://github.com/kvalo/ath10k-firmware/blob/master/QCA988X/10.2/firmware-3. > bin_10.2.2.39.6-1 > > and save it as: > /lib/firmware/ath10k/QCA988X/hw2.0/firmware-3.bin > > > After that reboot and see if you can configure the wireless connection. > > If not, please provide bootlogs and lspcidrake by doing (as root): > > journalctl -b >journal-bug16915 > lspcidrake -v >lspcidrake-bug16915 > > and then attach journal-bug16915 and lspcidrake-bug16915 to this bugreport After doing this and rebooting, I still could not create a wireless connection with drakconnect. Again, it asked for the Windows driver for ndiswrapper, so I cancelled out of it and took the logs.
Your logs show you are still running the 3.19.8-3 release kernel. You need to update your system and especially the 4.1.8-1 kernel
(In reply to Thomas Backlund from comment #7) > Your logs show you are still running the 3.19.8-3 release kernel. > > You need to update your system and especially the 4.1.8-1 kernel That's the problem. I can't atm. Wireless is all I have. I've been reporting here via Windows. The system is dual-booted.
(In reply to Kim Garren from comment #8) > (In reply to Thomas Backlund from comment #7) > > Your logs show you are still running the 3.19.8-3 release kernel. > > > > You need to update your system and especially the 4.1.8-1 kernel > > That's the problem. I can't atm. Wireless is all I have. I've been reporting > here via Windows. The system is dual-booted. I've been told there is a kernel patch to try, but I'm confused on that part as to where it is on the inet.
Is there a way to download the needed kernel and dependencies from one of the mirrors to a flash stick, and update the kernel at least from it? I can set the flash stick to an update source in MCC "Set sources". Or would I have to update the whole system in order to do so? Thanks.
Created attachment 7096 [details] journal-bug16915-1, with kernel 4.1.8-desktop-1 I was able to get updates enough to update the kernel and everything it needed. kernel-firmware as well.
Created attachment 7097 [details] lspcidrake-bug16915-1 Again, with kernel 4.1.8.
Created attachment 7098 [details] drakconnect We are getting closer. At least now drakconnect asks for either the Windows driver or the driver that's been placed. Thanks!
ok, so that hw actually needs different firmware, so: create missing firmware dir: mkdir -p /lib/firmware/ath10k/QCA6174/hw2.1 then download theese: https://github.com/sumdog/ath10k-firmware/raw/5faf5bb7c7413f9bb332693179de54cca6fff58e/ath10k/QCA6174/hw2.1/board.bin https://github.com/sumdog/ath10k-firmware/raw/5faf5bb7c7413f9bb332693179de54cca6fff58e/ath10k/QCA6174/hw2.1/firmware-4.bin and copy them to: /lib/firmware/ath10k/QCA6174/hw2.1/ and reboot the system and see if it works. if it still not works, try to do: echo "options ath10k_core skip_otp=y" >/etc/modprobe.d/ath10k.conf and reboot again and see if it works then
Created attachment 7099 [details] drakconnect2 Just to be sure all was well, when I was through making the directory and copying the files over, I ran: [root@localhost ~]# ls -r /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin board.bin [root@localhost ~]# Then rebooted. I then tried drakconnect via command line, and this is what came up. See the next screenshot as well. [root@localhost ~]# drakconnect Ignore the following Glib::Object::Introspection & Gtk3 warnings Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257. Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296.
Created attachment 7100 [details] drakconnect3 Note: It is complaining about the /interface/, not about the driver.
Please see notes on the attachments this time. Thanks.
Comment on attachment 7100 [details] drakconnect3 It's complaining about the interface, but was there one that was supposed to be with the driver? Or is this a drakconnect issue?
Created attachment 7101 [details] journal-bug16915-3 Oops! Apologies, I'd forgotten to run these again too.
Created attachment 7102 [details] lspcidrake-bug16915-3
It seems to have issues with otp did you do the: echo "options ath10k_core skip_otp=y" >/etc/modprobe.d/ath10k.conf and reboot ?
Created attachment 7104 [details] drakconnect4 This is the first time I've honestly smiled in weeks! I had indeed got in a rush and not done the last step there. All I need do now is get my wireless information, and plug it in there, I didn't have it handy. You sir, are a genius. Thank you! Please explain to me before we close this bug out, about otp and the board.bin file? Thank you again! :)
otp is a security feature "One Time Pasword" being implemented, but it is still work in progress, so upstream added support to disable it if needed as it can fail and block the proper hw init. board.bin is sort of a "map of the hw layout" / "adapter" so the firmware knows how to handle the hardware. that way, you can technically re-use most of firmware on more hw, just update board.bin to match the hw
OK, thank you for the explanation. The interface is obviously working; but the testing point fails of the connection configuration. my connection is WPA2-PSK [AES]. I do not have option for this. I only have option for WPA/WPA2 Enterprise for WPA. So, we may not be closed out yet. Will I need to do this via iwconfig (cli)? If so, with what options? Thanks!
since it drakconnect reports "unlisted"... is that true ? is your wireless name (ssid) hidden ? Can you connect to a fully open wireless network ? (either by changing your ap configuration temporarily, os if you have a mobile phone that can act as an ap)
CC: (none) => doktor5000
(In reply to Thomas Backlund from comment #25) > since it drakconnect reports "unlisted"... is that true ? > > is your wireless name (ssid) hidden ? > > Can you connect to a fully open wireless network ? > > (either by changing your ap configuration temporarily, os if you have a > mobile phone that can act as an ap) Hidden? No. That part got me too. I wondered as well why it came up unlisted. This is the connection my ISP set me up with. Windows detected it automatically, all I had to do was put the password in. The same with my android phone. Insofar as a fully open wireless network, I am not sure. I've had the computer for just over a month, haven't had it out and around yet. I can take it out however to see, but it would be a couple or even few days. I have noticed on boot: [INFO] Network Manager is not currently running... ... and that Mageia-wait-online could not run. [DEPEND] (Can't remember the rest, but it came up right after the [INFO] part)
Another note: I just logged in to my router, and "Enable SSID Broadcast" is turned on.
I do believe I've *maybe* found the issue with this. When I updated to the new kernel via usb (I'd downloaded all updates from Sept. 17-Sept. 23), it de-installed btrfs-progs and os-prober stating that they were in conflict with the new kernel, therefore I can't get back to Windows from grub, there is no entry. When I try to add it, it corrupts the bootloader beyond repair. My / partition is btrfs, I'm not so sure how this impacts things on the whole with the wireless situation, among other things, so I'm going to reinstall (again, I went through this whole process once already today) using reiserfs, and try everything again. If that doesn't do it for grub, then I'll file a bug on this. I'm not sure how it will impact things here. I can say that I've already been through the same steps you've given in Comment #14 once again to no avail. I get the same manual entry request. This is on a fresh install and update of the kernel. Will be back later, and let you know if I get anywhere with the kernel situation and this. Thanks.
Created attachment 7105 [details] upgrade kernel error What do I need to download and install so I can fix this, and from where, so I can move on to upgrading the kernel to 4.1.8 and continue with this bug? Thanks.
(In reply to Kim Garren from comment #29) > Created attachment 7105 [details] > upgrade kernel error > > What do I need to download and install so I can fix this, and from where, so > I can move on to upgrading the kernel to 4.1.8 and continue with this bug? > > Thanks. The funny thing is, I just reinstalled with reiserfs all the way for / and /home.
Created attachment 7108 [details] journal-bug16915-4 This is on a fully manually-updated system (still no wifi), which went swimmingly.
Created attachment 7109 [details] lspcidrake-bug16915-4 On a fully updated Mageia system as well.
Created attachment 7110 [details] Current code run You may find interesting things here, maybe not. I do know that there is no board.bin in /lib/firmware/ath10k/QCA988X/hw2.0/ anywhere.
(In reply to Kim Garren from comment #31) > Created attachment 7108 [details] > journal-bug16915-4 > > This is on a fully manually-updated system (still no wifi), which went > swimmingly. ok, so hw seems to get initialized: kernel: ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32 ifplugd(wlp3s0)[1189]: Using interface wlp3s0/B8:86:87:47:28:81 with driver <ath10k_pci> (version: 4.1.8-desktop-1.mga5) is wpa_supplicant installed ? And what does theese commands show: iw list iw dev wlp3s0 scan
(In reply to Thomas Backlund from comment #34) > (In reply to Kim Garren from comment #31) > > Created attachment 7108 [details] > > journal-bug16915-4 > > > > This is on a fully manually-updated system (still no wifi), which went > > swimmingly. > > ok, so hw seems to get initialized: > > kernel: ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw > killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32 > > ifplugd(wlp3s0)[1189]: Using interface wlp3s0/B8:86:87:47:28:81 with driver > <ath10k_pci> (version: 4.1.8-desktop-1.mga5) > > is wpa_supplicant installed ? > > And what does theese commands show: > > iw list > > iw dev wlp3s0 scan [root@localhost ~]# rpm -qa | grep supplicant wpa_supplicant-2.3-3.mga5 [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# iw list Wiphy phy0 max # scan SSIDs: 16 max scan IEs length: 195 bytes Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0x1 RX 0x1 Configured Antennas: TX 0x1 RX 0x1 Supported interface modes: * IBSS * managed * AP * AP/VLAN * monitor * P2P-client * P2P-GO * P2P-device Band 1: Capabilities: 0x19e3 RX LDPC HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 8 usec (0x06) HT TX/RX MCS rate indexes supported: 0-7 VHT Capabilities (0x339011b2): Max MPDU length: 11454 Supported Channel Width: neither 160 nor 80+80 RX LDPC short GI (80 MHz) TX STBC SU Beamformee MU Beamformee RX antenna pattern consistency TX antenna pattern consistency VHT RX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 0 Mbps VHT TX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 0 Mbps Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (disabled) * 2472 MHz [13] (disabled) * 2484 MHz [14] (disabled) Band 2: Capabilities: 0x19e3 RX LDPC HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 8 usec (0x06) HT TX/RX MCS rate indexes supported: 0-7 VHT Capabilities (0x339011b2): Max MPDU length: 11454 Supported Channel Width: neither 160 nor 80+80 RX LDPC short GI (80 MHz) TX STBC SU Beamformee MU Beamformee RX antenna pattern consistency TX antenna pattern consistency VHT RX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 0 Mbps VHT TX MCS set: 1 streams: MCS 0-9 2 streams: not supported 3 streams: not supported 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 0 Mbps Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 5180 MHz [36] (17.0 dBm) (no IR) * 5200 MHz [40] (17.0 dBm) (no IR) * 5220 MHz [44] (17.0 dBm) (no IR) * 5240 MHz [48] (17.0 dBm) (no IR) * 5260 MHz [52] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5280 MHz [56] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5300 MHz [60] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5320 MHz [64] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5500 MHz [100] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5520 MHz [104] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5540 MHz [108] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5560 MHz [112] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5580 MHz [116] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5600 MHz [120] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5620 MHz [124] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5640 MHz [128] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5660 MHz [132] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5680 MHz [136] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5700 MHz [140] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 234 sec) DFS CAC time: 60000 ms * 5745 MHz [149] (30.0 dBm) (no IR) * 5765 MHz [153] (30.0 dBm) (no IR) * 5785 MHz [157] (30.0 dBm) (no IR) * 5805 MHz [161] (30.0 dBm) (no IR) * 5825 MHz [165] (30.0 dBm) (no IR) Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * new_mpath * set_mesh_config * set_bss * authenticate * associate * deauthenticate * disassociate * join_ibss * join_mesh * remain_on_channel * set_tx_bitrate_mask * frame * frame_wait_cancel * set_wiphy_netns * set_channel * set_wds_peer * probe_client * set_noack_map * register_beacons * start_p2p_device * set_mcast_rate * channel_switch * Unknown command (104) * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0x40 0xb0 0xc0 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-device: 0x40 0xd0 software interface modes (can always be added): * AP/VLAN * monitor valid interface combinations: * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{ P2P-device } <= 1, #{ AP } <= 7, total <= 8, #channels <= 1, STA/AP BI must match HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing Device supports TX status socket option. Device supports HT-IBSS. Device supports SAE with AUTHENTICATE command Device supports scan flush. Device supports per-vif TX power setting Driver supports a userspace MPM Driver/device bandwidth changes during BSS lifetime (AP/GO mode) Device supports static SMPS [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# iw dev wlp3s0 scan command failed: Network is down (-100) [root@localhost ~]# And I'm still unable to make a connection. I still don't have option to make a WPA2-PSK [AES] connection.
ok, so iw seems to be happy... What if you open "Mageia Control Center" -> "Network & Internet" -> "Network Center" Do you see a "Wireless (Wi-Fi)" menu ? If so... can you expand it ? Do you see the network you want? Can you try to connect to it? Does it suggest WPA/WPA2 PSK ?
(In reply to Thomas Backlund from comment #36) > ok, so iw seems to be happy... > > What if you open "Mageia Control Center" -> "Network & Internet" -> "Network > Center" > > Do you see a "Wireless (Wi-Fi)" menu ? > If so... can you expand it ? > Do you see the network you want? > Can you try to connect to it? > > Does it suggest WPA/WPA2 PSK ? I've already tried it, and to the rest, the answer is No to all of the above. Per my last comment: "And I'm still unable to make a connection. I still don't have option to make a WPA2-PSK [AES] connection." I still only have option for WEP or WPA/WPA2 Enterprise. My connection is neither of the two.
(In reply to Kim Garren from comment #37) > (In reply to Thomas Backlund from comment #36) > > ok, so iw seems to be happy... > > > > What if you open "Mageia Control Center" -> "Network & Internet" -> "Network > > Center" > > > > Do you see a "Wireless (Wi-Fi)" menu ? > > If so... can you expand it ? > > Do you see the network you want? > > Can you try to connect to it? > > > > Does it suggest WPA/WPA2 PSK ? > > I've already tried it, and to the rest, the answer is No to all of the above. > > Per my last comment: "And I'm still unable to make a connection. I still > don't have option to make a WPA2-PSK [AES] connection." > > I still only have option for WEP or WPA/WPA2 Enterprise. My connection is > neither of the two. I do have a menu, but it still sees the connection as unlisted; I have to enter it manually, and when I do, I don't have the option for my connection that I need.
ok, seems there are some issues with the 4.1 series kernels ... something that atleast for some are fixed in 4.2+ kernels. and now QCA only have official firmware-5 files for that hw. I will look into backporting newer ath10k support
One other thing to test is to remove any configuration in Mageia Control Center for the wireless network, then enable NetworkManager service and reboot. after reboot, see if you can connect with networkmanager
(In reply to Thomas Backlund from comment #40) > One other thing to test is to remove any configuration in Mageia Control > Center for the wireless network, then enable NetworkManager service and > reboot. > > after reboot, see if you can connect with networkmanager I haven't had chance yet to figure out systemd as I've been away from Linux for the last two to three years until recently wherein I walked straight into this. I'm out of "practice" if you will. Before that I never had to worry about it. Would you please walk me through enabling Network Manager? There is no configuration. I've cancelled every time because it would have been wrong. Thanks!
(In reply to Thomas Backlund from comment #39) > ok, seems there are some issues with the 4.1 series kernels ... something > that atleast for some are fixed in 4.2+ kernels. > > and now QCA only have official firmware-5 files for that hw. > > I will look into backporting newer ath10k support I would so much appreciate this! You have no idea how badly I want to get back to running Linux solely.
(In reply to Kim Garren from comment #41) > Would you please walk me through enabling Network Manager? > There is no configuration. I've cancelled every time because it would have > been wrong. "Mageia Control Center" -> "System" -> "Manage system services..." Enable "On boot" for: NetworkManager NetworkManager-wait-online Disable "On boot" for: network and reboot. You should then see a "wireless icon" in notification area that you can use to configure the wireless
(In reply to Thomas Backlund from comment #43) > (In reply to Kim Garren from comment #41) > > > Would you please walk me through enabling Network Manager? > > There is no configuration. I've cancelled every time because it would have > > been wrong. > > > "Mageia Control Center" -> "System" -> "Manage system services..." > > Enable "On boot" for: > NetworkManager > NetworkManager-wait-online > > Disable "On boot" for: > network > > and reboot. > > You should then see a "wireless icon" in notification area that you can use > to configure the wireless They both very unfortunately fail on boot, and in the desktop. :( Perhaps there's more info in dmesg: [dedanna@localhost ~]$ dmesg | grep fail [ 0.355471] pci 0000:04:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] [ 3.816669] usb: failed to peer usb2-port3 and usb1-port4 by location (usb2-port3:none) (usb1-port4:usb2-port2) [ 3.816671] usb usb2-port3: failed to peer to usb1-port4 (-16) [ 3.816945] usb: failed to peer usb2-port4 and usb1-port4 by location (usb2-port4:none) (usb1-port4:usb2-port2) [ 3.816947] usb usb2-port4: failed to peer to usb1-port4 (-16) [ 3.855005] nouveau E[ DRM] failed to create 0x00000080, -22 [ 3.855126] nouveau: probe of 0000:04:00.0 failed with error -22 [ 8.499781] hdaps: driver init failed (ret=-19)! [ 11.494534] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2 [ 15.692920] hdaps: driver init failed (ret=-19)! [dedanna@localhost ~]$
I don't know what else is needed here. I'm happy to give whatever outputs are needed, to try whatever procedures. I know now that I picked the wrong chipset for a new computer, but would like to resolve this one way or another, as it could help others with the same chipset. If it can't be done for right now, it can't be done, but I'd still like to try. Thank you.
Hi, I have been busy this weekend with mageia infrastructure work, so no movement on this yet... I hope to have a working backport of the driver in ~1 week
(In reply to Thomas Backlund from comment #46) > Hi, > > I have been busy this weekend with mageia infrastructure work, so no > movement on this yet... > > I hope to have a working backport of the driver in ~1 week Cool, no worries, I understand. The problem being, it's not working yet on this thing.
Hey Mr. Backlund! We are *almost* there! :D The last thing you had me do here was to enable Network Manager and Network Manager Wait Online on boot, and disable Network, which I did do at the time. Today, I had to get into the boot services for another reason, and noticed that Network Manager and Wait Online both were unticked, and stopped. I was like, "Wait, what???" so I looked at Network, and it was ticked! The settings hadn't stuck! So, I started Network Manager and Wait Online and re-ticked them, stopped Network, and unticked it, and guess what? This thing now sees the wireless connections around me but sees my connection as WPA/WPA2 Pre-Shared Key. It's not a pre-shared key, so I'm letting you know that but will try it anyway, will get the encryption key from router.net. Thanks for your patience with me - this has been very trying. I'm wondering what it will take to get the correct settings to stick in Boot Services?
(In reply to Kim Garren from comment #48) > Hey Mr. Backlund! We are *almost* there! :D > > The last thing you had me do here was to enable Network Manager and Network > Manager Wait Online on boot, and disable Network, which I did do at the time. > > Today, I had to get into the boot services for another reason, and noticed > that Network Manager and Wait Online both were unticked, and stopped. I was > like, "Wait, what???" so I looked at Network, and it was ticked! The > settings hadn't stuck! > > So, I started Network Manager and Wait Online and re-ticked them, stopped > Network, and unticked it, and guess what? This thing now sees the wireless > connections around me but sees my connection as WPA/WPA2 Pre-Shared Key. > It's not a pre-shared key, so I'm letting you know that but will try it > anyway, will get the encryption key from router.net. > > Thanks for your patience with me - this has been very trying. I'm wondering > what it will take to get the correct settings to stick in Boot Services? Sorry, I meant to mention that according to the bug on this at kernel.org, there's been a new commit as of just a few days ago. I am thinking that's the one you mentioned earlier. https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=aab28b04bcae237f871f4594bbc654da0cf36b50 Should I be using this instead?
Except I'm not finding an encryption key for my connection, because it's not WPA/WPA2 Pre-shared key or WPA/WPA2 Enterprise.
Ok, new stuff to test: move away the older firmwre files you have tested so they dont interfere: mv /lib/firmware/ath10k/QCA6174/hw2.1 /root/ then download the new rpms: firmware: http://mirrors.kernel.org/mageia/distrib/5/x86_64/media/nonfree/updates_testing/kernel-firmware-nonfree-20151018-1.mga5.nonfree.noarch.rpm kernel: http://mirrors.kernel.org/mageia/distrib/5/x86_64/media/core/updates_testing/kernel-desktop-4.1.11-1.mga5-1-1.mga5.x86_64.rpm install them and reboot... Does it work at all / any better / any difference ?
(In reply to Kim Garren from comment #50) > Except I'm not finding an encryption key for my connection, because it's not > WPA/WPA2 Pre-shared key or WPA/WPA2 Enterprise. Then what is it... usually the detection works ? How did you connect on the windows side ?
And since you atleast now can "see" the networks, please show the output of: iw list iw dev wlp3s0 scan
(In reply to Thomas Backlund from comment #52) > (In reply to Kim Garren from comment #50) > > Except I'm not finding an encryption key for my connection, because it's not > > WPA/WPA2 Pre-shared key or WPA/WPA2 Enterprise. > > > Then what is it... usually the detection works ? > > How did you connect on the windows side ? Per a below comment (it's a ways back), Windows found it, I clicked up the connection, the dialog asked for the password, I put it in, that was all she wrote. I'll try the rest. Thanks.
(In reply to Kim Garren from comment #54) > (In reply to Thomas Backlund from comment #52) > > (In reply to Kim Garren from comment #50) > > > Except I'm not finding an encryption key for my connection, because it's not > > > WPA/WPA2 Pre-shared key or WPA/WPA2 Enterprise. > > > > > > Then what is it... usually the detection works ? > > > > How did you connect on the windows side ? > > Per a below comment (it's a ways back), Windows found it, I clicked up the > connection, the dialog asked for the password, I put it in, that was all she > wrote. > > I'll try the rest. Thanks. Oh, and "my connection is WPA2-PSK [AES]"
Well, that was... "interesting"... I installed the new kernel, and the output was: [root@localhost ~]# urpmi /run/media/dedanna/389D-17DA/Take3/kernel-desktop-4.1.11-1.mga5-1-1.mga5.x86_64.rpm installing kernel-desktop-4.1.11-1.mga5-1-1.mga5.x86_64.rpm from /run/media/dedanna/389D-17DA/Take3 Preparing... ############################################# 1/1: kernel-desktop-4.1.11-1.mga5 ############################################# cannot get info for device (5:0:0:1) at /usr/lib/libDrakX/detect_devices.pm line 272. Creating: target|kernel|dracut args|basicmodules You should restart your computer for kernel-desktop-4.1.11-1.mga5 [root@localhost ~]# Then, I started getting graphics glitches like mad, and couldn't do anything else. On the desktop, my workspaces started randomly and very quickly scrolling (there were eight). I tried at the panel to set the workspaces to just one row and one workspace, but then on the desktop it started randomly and very quickly cycling between windows; I had two open at the time and I finally got the firmware to install, but the cycling didn't stop. I tried rebooting into previous kernel, but got the same thing so I rebooted and came back to Windows. I did manage to get one of the commands you asked for run afterwards but it's still cycling bad, and difficult to deal with.
Created attachment 7159 [details] iw list On the other command you gave me to run, it told me command failed, device or resource busy, and I knew why, but couldn't do anything about it because of the graphics glitches. I did get screenshots of the process of trying to create the connection by being really fast, I'll post them next.
It's not allowing me to post the screenshots here; says they're too big. I'll try converting to .jpg and upload them then if they're not too big then. The interesting thing was the second screenshot wherein it referred to the RealTek, then said the connection was disconnected.
Created attachment 7160 [details] Requested output. I removed the new kernel, rolled back kernel-firmware to where it was, and set /lib/firmware/ath10k/QCA6174/hw2.1 back to the way it last was, from the backup in /root.
Created attachment 7161 [details] iw dev (requested).
Created attachment 7162 [details] Current journal -b.
Created attachment 7163 [details] Current lspcidrake -v It's doing everything but actually connecting. The connection fails. I know the password is right; I've been going with WPA/WPA2 Pre-Shared Key this morning.
(In reply to Kim Garren from comment #56) > Well, that was... "interesting"... > > I installed the new kernel, and the output was: > > [root@localhost ~]# urpmi > /run/media/dedanna/389D-17DA/Take3/kernel-desktop-4.1.11-1.mga5-1-1.mga5. > x86_64.rpm > > > installing kernel-desktop-4.1.11-1.mga5-1-1.mga5.x86_64.rpm from > /run/media/dedanna/389D-17DA/Take3 > Preparing... > ############################################# > 1/1: kernel-desktop-4.1.11-1.mga5 > > ############################################# > cannot get info for device (5:0:0:1) at /usr/lib/libDrakX/detect_devices.pm > line 272. > Creating: target|kernel|dracut args|basicmodules > You should restart your computer for kernel-desktop-4.1.11-1.mga5 > [root@localhost ~]# > > Then, I started getting graphics glitches like mad, and couldn't do anything > else. That's weird... simply installing a kernel should not affect anything.. Did you install the kernel-firmware-nonfree first ? If so, could you try to only install the new kernel and boot into that. Then if that works, try move remove the files in: /lib/firmware/ath10k/QCA6174/hw2.1/ and add theese there instead (or extract them from the already downloaded kernel-firmware-nonfree): https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/ath10k/QCA6174/hw2.1/board.bin https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/ath10k/QCA6174/hw2.1/firmware-5.bin And see if it works... (In reply to Kim Garren from comment #55) > > Oh, and "my connection is WPA2-PSK [AES]" (In reply to Kim Garren from comment #61) > Created attachment 7162 [details] > Current journal -b. Hm, this one reports no security needed: <info> (wlp3s0): Activation: (wifi) connection 'System MyCharterWiFi2c-2G (wlp3s0)' requires no security. No secrets needed. <info> Config: added 'ssid' value 'MyCharterWiFi2c-2G' <info> Config: added 'scan_ssid' value '1' <info> Config: added 'key_mgmt' value 'NONE' <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) complete. <info> Config: set interface ap_scan to 1 <info> (wlp3s0): supplicant interface state: disconnected -> scanning <warn> (wlp3s0): Activation: (wifi) association took too long, failing activation <info> (wlp3s0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53] But lets take one step at a time... Could you configure your AP to be fully open first and test if it connects properly then... Then try to set WEP, try again, then WPA and so on so we can figure out where it breaks down... also try to set as simple password as possible, for example only numbers in password and so on
(In reply to Thomas Backlund from comment #63) > (In reply to Kim Garren from comment #56) > > Well, that was... "interesting"... > > > > I installed the new kernel, and the output was: > > > > [root@localhost ~]# urpmi > > /run/media/dedanna/389D-17DA/Take3/kernel-desktop-4.1.11-1.mga5-1-1.mga5. > > x86_64.rpm > > > > > > installing kernel-desktop-4.1.11-1.mga5-1-1.mga5.x86_64.rpm from > > /run/media/dedanna/389D-17DA/Take3 > > Preparing... > > ############################################# > > 1/1: kernel-desktop-4.1.11-1.mga5 > > > > ############################################# > > cannot get info for device (5:0:0:1) at /usr/lib/libDrakX/detect_devices.pm > > line 272. > > Creating: target|kernel|dracut args|basicmodules > > You should restart your computer for kernel-desktop-4.1.11-1.mga5 > > [root@localhost ~]# > > > > Then, I started getting graphics glitches like mad, and couldn't do anything > > else. > > That's weird... simply installing a kernel should not affect anything.. > > Did you install the kernel-firmware-nonfree first ? > > If so, could you try to only install the new kernel and boot into that. > > Then if that works, try move remove the files in: > /lib/firmware/ath10k/QCA6174/hw2.1/ > > and add theese there instead (or extract them from the already downloaded > kernel-firmware-nonfree): > https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ > plain/ath10k/QCA6174/hw2.1/board.bin > https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ > plain/ath10k/QCA6174/hw2.1/firmware-5.bin > > And see if it works... > > > (In reply to Kim Garren from comment #55) > > > > > Oh, and "my connection is WPA2-PSK [AES]" > > > (In reply to Kim Garren from comment #61) > > Created attachment 7162 [details] > > Current journal -b. > > Hm, this one reports no security needed: > > <info> (wlp3s0): Activation: (wifi) connection 'System MyCharterWiFi2c-2G > (wlp3s0)' requires no security. No secrets needed. > <info> Config: added 'ssid' value 'MyCharterWiFi2c-2G' > <info> Config: added 'scan_ssid' value '1' > <info> Config: added 'key_mgmt' value 'NONE' > <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) complete. > <info> Config: set interface ap_scan to 1 > <info> (wlp3s0): supplicant interface state: disconnected -> scanning > <warn> (wlp3s0): Activation: (wifi) association took too long, failing > activation > <info> (wlp3s0): device state change: config -> failed (reason > 'ssid-not-found') [50 120 53] > > > But lets take one step at a time... > > Could you configure your AP to be fully open first and test if it connects > properly then... > > Then try to set WEP, try again, then WPA and so on so we can figure out > where it breaks down... > > also try to set as simple password as possible, for example only numbers in > password and so on I installed the kernel first, that's when it started up; then I barely got the kernel-firmware installed. It could be that I also on the 4.1.8 have the kernel-devel installed and nvidia-current-kernel for my Nvidia 840M? Which should be installed first?
I also just use the password and info that my ISP gave me to use. The password they gave is letters and numbers, pretty simple. In router settings, we do have option to have a guest connection, but it's turned off. How do you mean "fully open first"? I already tried those files btw, on boot it didn't find them because it expected firmware-4.bin. So, I changed the filename to firmware-4.bin, and rebooted, it went nowhere at all. There was no connection seen at all. This was after I had removed the new kernel from testing. So, I put the other files we had in place back - that's the closest we've got to anything.
OK, this is without the new kernel or the new files from git. It's from the last configuration we had set up. I booted into the desktop, and went to su - in terminal, ran drakconnect. I tried it with None for encryption, the connection failed. I tried it with Open WEP which required a key, I gave it the password I have, the connection failed. This happened with every other option to, Restricted WEP, and WPA/WPA2 Pre-Shared Key. I could not use the WPA/WPA2 Enterprise option however, as I don't have anywhere near that much information it requires for my connection. At the end of each one that I could try, up came a dialog box saying: "Problems occurred during the network connectivity test. This can be caused by invalid network configuration, or problems with your modem or router. You might want to relaunch the configuration to verify the connection settings." CLI output from running it was: [root@localhost ~]# drakconnect Ignore the following Glib::Object::Introspection & Gtk3 warnings Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257. Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296. -->Failed to connect to non-global ctrl_ifname: (null) error: Success I ran dmesg: [dedanna@localhost ~]$ dmesg | grep fail [ 0.357446] pci 0000:04:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] [ 3.858030] usb: failed to peer usb2-port3 and usb1-port4 by location (usb2-port3:none) (usb1-port4:usb2-port2) [ 3.858034] usb usb2-port3: failed to peer to usb1-port4 (-16) [ 3.858400] usb: failed to peer usb2-port4 and usb1-port4 by location (usb2-port4:none) (usb1-port4:usb2-port2) [ 3.858403] usb usb2-port4: failed to peer to usb1-port4 (-16) [ 3.883104] nouveau E[ DRM] failed to create 0x00000080, -22 [ 3.883268] nouveau: probe of 0000:04:00.0 failed with error -22 [ 9.045032] hdaps: driver init failed (ret=-19)! -->[ 12.874081] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2 -->[ 13.545743] hdaps: driver init failed (ret=-19)! -->[ 17.086732] hdaps: driver init failed (ret=-19)! -->[ 19.271006] hdaps: driver init failed (ret=-19)! [ 19.381388] systemd[1]: Unit fedora-loadmodules.service entered failed state. [ 19.391403] systemd[1]: fedora-loadmodules.service failed. -->[ 26.679796] hdaps: driver init failed (ret=-19)! -->[ 26.698014] hdaps: driver init failed (ret=-19)! -->[ 27.122900] applesmc: driver init failed (ret=-19)! -->[ 27.135492] applesmc: driver init failed (ret=-19)! -->[ 31.121605] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168g-3.fw failed with error -2 The last line doesn't make sense to me at all; it is the wired RealTek and so far that hasn't failed on boot. I then uninstalled dkms-nvidia-current (I think it was called, could have been dkms-current-nvidia), and installed the new kernel. That's where the graphics glitches were coming from, was the dkms-nvidia. I now need to try with the new board.bin and firmware-5.bin but that will have to wait for tomorrow, I'm out of time today.
Sorry to flood here. I went ahead and just did it up. New kernel installed - check. New board.bin and firmware-5.bin placed in /lib/firmware/ath10k/QCA6174/hw2.1 - check. Computer shut down performed - check. Reloaded into desktop, exact same results as last post here. [dedanna@localhost ~]$ su - Password: [root@localhost ~]# uname -a Linux localhost.localdomain 4.1.11-desktop-1.mga5 #1 SMP Fri Oct 23 21:13:44 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# dmesg | grep fail [ 0.350546] pci 0000:04:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] [ 3.849059] usb: failed to peer usb2-port3 and usb1-port4 by location (usb2-port3:none) (usb1-port4:usb2-port2) [ 3.849061] usb usb2-port3: failed to peer to usb1-port4 (-16) [ 3.849324] usb: failed to peer usb2-port4 and usb1-port4 by location (usb2-port4:none) (usb1-port4:usb2-port2) [ 3.849325] usb usb2-port4: failed to peer to usb1-port4 (-16) [ 3.876181] nouveau E[ DRM] failed to create 0x00000080, -22 [ 3.876316] nouveau: probe of 0000:04:00.0 failed with error -22 [ 8.799599] hdaps: driver init failed (ret=-19)! [ 11.704217] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2 [ 12.017133] hdaps: driver init failed (ret=-19)! [ 13.101092] hdaps: driver init failed (ret=-19)! [ 16.233694] hdaps: driver init failed (ret=-19)! [ 16.275752] systemd[1]: Unit fedora-loadmodules.service entered failed state. [ 16.285737] systemd[1]: fedora-loadmodules.service failed. [ 26.477343] hdaps: driver init failed (ret=-19)! [ 26.672431] applesmc: driver init failed (ret=-19)! [ 26.683224] applesmc: driver init failed (ret=-19)! [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# drakconnect Ignore the following Glib::Object::Introspection & Gtk3 warnings Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257. Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296. Failed to connect to non-global ctrl_ifname: (null) error: Success [root@localhost ~]# [root@localhost ~]# rpm -qa | grep firmware alsa-tools-firmware-1.0.28-1.mga5 ralink-firmware-20150824-1.mga5.nonfree firmware-tools-2.1.15-6.mga5 rtlwifi-firmware-20150824-1.mga5.nonfree alsa-firmware-1.0.28-2.mga5 bluez-firmware-1.2-12.mga5.nonfree -->kernel-firmware-20150722-1.mga5 -->kernel-firmware-nonfree-20151018-1.mga5.nonfree radeon-firmware-20150824-1.mga5.nonfree [root@localhost ~]#
CC: (none) => bequimao.de
On advice of the bjoernvold forum, some information that I thought prudent to give here first, before there (http://bjoernvold.com/forum/viewtopic.php?p=21876#p21876), some things I was given to try. I thought it strange that everything seemed to be "there" to make the connection fly, and mentioned in that thread that I thought I was doing something wrong. It turns out that everything isn't as "there" as I thought: [root@localhost dedanna]# lspci -v 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Lenovo Device 3987 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 381c Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at c2000000 (64-bit, non-prefetchable) [size=16M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Lenovo Device 3987 Flags: bus master, fast devsel, latency 0, IRQ 58 Memory at c4310000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Lenovo Device 3987 Flags: bus master, medium devsel, latency 0, IRQ 48 Memory at c4300000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Lenovo Device 3987 Flags: bus master, fast devsel, latency 0, IRQ 59 Memory at c431a000 (64-bit, non-prefetchable) [size=32] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: mei_me Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Lenovo Device 3987 Flags: bus master, fast devsel, latency 64, IRQ 49 Memory at c4314000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: a0100000-a02fffff Prefetchable memory behind bridge: 00000000a0300000-00000000a04fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Lenovo Device 3987 Capabilities: [a0] Power Management version 3 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00004000-00004fff Memory behind bridge: c4200000-c42fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Lenovo Device 3987 Capabilities: [a0] Power Management version 3 Capabilities: [100] #00 Capabilities: [200] L1 PM Substates Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: c4000000-c41fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Lenovo Device 3987 Capabilities: [a0] Power Management version 3 Capabilities: [100] #00 Capabilities: [200] L1 PM Substates Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: c3000000-c3ffffff Prefetchable memory behind bridge: 00000000b0000000-00000000c1ffffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Lenovo Device 3987 Capabilities: [a0] Power Management version 3 Capabilities: [100] #00 Capabilities: [200] L1 PM Substates Kernel driver in use: pcieport Kernel modules: shpchp 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03) Subsystem: Lenovo Device 3987 Flags: bus master, medium devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: Lenovo Device 3987 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 46 I/O ports at 5088 [size=8] I/O ports at 5094 [size=4] I/O ports at 5080 [size=8] I/O ports at 5090 [size=4] I/O ports at 5060 [size=32] Memory at c4318000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03) Subsystem: Lenovo Device 3987 Flags: medium devsel, IRQ 18 Memory at c4319000 (64-bit, non-prefetchable) [size=256] I/O ports at 5040 [size=32] Kernel modules: i2c_i801 -->02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) Subsystem: Lenovo Device 3819 Flags: bus master, fast devsel, latency 0, IRQ 60 I/O ports at 4000 [size=256] Memory at c4204000 (64-bit, non-prefetchable) [size=4K] Memory at c4200000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169 -->03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 20) Subsystem: Lenovo Device 3044 Flags: bus master, fast devsel, latency 0, IRQ 50 Memory at c4000000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit- Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [178] Latency Tolerance Reporting Capabilities: [180] L1 PM Substates Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci 04:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2) Subsystem: Lenovo Device 381c Flags: fast devsel, IRQ 16 Memory at c3000000 (32-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at c0000000 (64-bit, prefetchable) [size=32M] I/O ports at 3000 [size=128] Expansion ROM at <ignored> [disabled] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel modules: nvidiafb, nouveau [root@localhost dedanna]# [root@localhost dedanna]# dmesg | grep ath10k [ 10.725675] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 -->[ 11.150508] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2 [ 12.895424] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw WLAN.RM.1.1-00141 api 5 htt 3.1 wmi 4 cal otp max_sta 32 [ 12.895427] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs 0 testmode 0 [ 17.551211] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0 [root@localhost dedanna]# "[root@localhost dedanna]# inxi -n Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp2s0 state: down mac: 68:f7:28:d0:14:46 Card-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter driver: ath10k_pci IF: wlp3s0 state: down mac: b8:86:87:47:28:81 Card-3: Atheros IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A [root@localhost dedanna]# [root@localhost dedanna]# ls /sys/class/net enp2s0@ lo@ wlp3s0@ [root@localhost dedanna]# [root@localhost dedanna]# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 68:f7:28:d0:14:46 brd ff:ff:ff:ff:ff:ff 3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether b8:86:87:47:28:81 brd ff:ff:ff:ff:ff:ff [root@localhost dedanna]# If I run: "ip link set wlp3s0 up or down" I get no output whatsoever. However, I pushed on anyway: [root@localhost dedanna]# ip link show dev wlp3s0 3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether b8:86:87:47:28:81 brd ff:ff:ff:ff:ff:ff [root@localhost dedanna]# [root@localhost dedanna]# systemctl status network systemd-netorkd.service ââ network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: inactive (dead) ââ systemd-netorkd.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) [root@localhost dedanna]# [root@localhost dedanna]# systemctl start network systemd-netorkd.service Failed to start systemd-netorkd.service: Unit systemd-netorkd.service failed to load: No such file or directory. [root@localhost dedanna]# [root@localhost dedanna]# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN [root@localhost dedanna]# I hope this is helpful to you.
(In reply to Kim Garren from comment #68) > On advice of the bjoernvold forum, some information that I thought prudent > to give here first, before there > (http://bjoernvold.com/forum/viewtopic.php?p=21876#p21876), some things I > was given to try. I thought it strange that everything seemed to be "there" > to make the connection fly, and mentioned in that thread that I thought I > was doing something wrong. It turns out that everything isn't as "there" as > I thought: > > [root@localhost dedanna]# lspci -v > 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) > Subsystem: Lenovo Device 3987 > Flags: bus master, fast devsel, latency 0 > Capabilities: [e0] Vendor Specific Information: Len=0c <?> > > 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated > Graphics (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Lenovo Device 381c > Flags: bus master, fast devsel, latency 0, IRQ 47 > Memory at c2000000 (64-bit, non-prefetchable) [size=16M] > Memory at d0000000 (64-bit, prefetchable) [size=256M] > I/O ports at 5000 [size=64] > Expansion ROM at <unassigned> [disabled] > Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [d0] Power Management version 2 > Capabilities: [a4] PCI Advanced Features > Kernel driver in use: i915 > Kernel modules: i915 > > 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) > Subsystem: Lenovo Device 3987 > Flags: bus master, fast devsel, latency 0, IRQ 58 > Memory at c4310000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [50] Power Management version 2 > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI > Controller (rev 03) (prog-if 30 [XHCI]) > Subsystem: Lenovo Device 3987 > Flags: bus master, medium devsel, latency 0, IRQ 48 > Memory at c4300000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [70] Power Management version 2 > Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > > 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI > Controller #1 (rev 03) > Subsystem: Lenovo Device 3987 > Flags: bus master, fast devsel, latency 0, IRQ 59 > Memory at c431a000 (64-bit, non-prefetchable) [size=32] > Capabilities: [50] Power Management version 3 > Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Kernel driver in use: mei_me > Kernel modules: mei_me > > 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition > Audio Controller (rev 03) > Subsystem: Lenovo Device 3987 > Flags: bus master, fast devsel, latency 64, IRQ 49 > Memory at c4314000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [50] Power Management version 3 > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port > #1 (rev e3) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > I/O behind bridge: 00002000-00002fff > Memory behind bridge: a0100000-a02fffff > Prefetchable memory behind bridge: 00000000a0300000-00000000a04fffff > Capabilities: [40] Express Root Port (Slot+), MSI 00 > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [90] Subsystem: Lenovo Device 3987 > Capabilities: [a0] Power Management version 3 > Kernel driver in use: pcieport > Kernel modules: shpchp > > 00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port > #3 (rev e3) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 > I/O behind bridge: 00004000-00004fff > Memory behind bridge: c4200000-c42fffff > Capabilities: [40] Express Root Port (Slot+), MSI 00 > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [90] Subsystem: Lenovo Device 3987 > Capabilities: [a0] Power Management version 3 > Capabilities: [100] #00 > Capabilities: [200] L1 PM Substates > Kernel driver in use: pcieport > Kernel modules: shpchp > > 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port > #4 (rev e3) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 > Memory behind bridge: c4000000-c41fffff > Capabilities: [40] Express Root Port (Slot+), MSI 00 > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [90] Subsystem: Lenovo Device 3987 > Capabilities: [a0] Power Management version 3 > Capabilities: [100] #00 > Capabilities: [200] L1 PM Substates > Kernel driver in use: pcieport > Kernel modules: shpchp > > 00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port > #5 (rev e3) (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 > I/O behind bridge: 00003000-00003fff > Memory behind bridge: c3000000-c3ffffff > Prefetchable memory behind bridge: 00000000b0000000-00000000c1ffffff > Capabilities: [40] Express Root Port (Slot+), MSI 00 > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [90] Subsystem: Lenovo Device 3987 > Capabilities: [a0] Power Management version 3 > Capabilities: [100] #00 > Capabilities: [200] L1 PM Substates > Kernel driver in use: pcieport > Kernel modules: shpchp > > 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev > 03) > Subsystem: Lenovo Device 3987 > Flags: bus master, medium devsel, latency 0 > Capabilities: [e0] Vendor Specific Information: Len=0c <?> > Kernel driver in use: lpc_ich > Kernel modules: lpc_ich > > 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller > [AHCI Mode] (rev 03) (prog-if 01 [AHCI 1.0]) > Subsystem: Lenovo Device 3987 > Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 46 > I/O ports at 5088 [size=8] > I/O ports at 5094 [size=4] > I/O ports at 5080 [size=8] > I/O ports at 5090 [size=4] > I/O ports at 5060 [size=32] > Memory at c4318000 (32-bit, non-prefetchable) [size=2K] > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [70] Power Management version 3 > Capabilities: [a8] SATA HBA v1.0 > Kernel driver in use: ahci > > 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03) > Subsystem: Lenovo Device 3987 > Flags: medium devsel, IRQ 18 > Memory at c4319000 (64-bit, non-prefetchable) [size=256] > I/O ports at 5040 [size=32] > Kernel modules: i2c_i801 > > -->02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) > Subsystem: Lenovo Device 3819 > Flags: bus master, fast devsel, latency 0, IRQ 60 > I/O ports at 4000 [size=256] > Memory at c4204000 (64-bit, non-prefetchable) [size=4K] > Memory at c4200000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [40] Power Management version 3 > Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Capabilities: [70] Express Endpoint, MSI 01 > Capabilities: [b0] MSI-X: Enable- Count=4 Masked- > Capabilities: [d0] Vital Product Data > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Virtual Channel > Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 > Capabilities: [170] Latency Tolerance Reporting > Capabilities: [178] L1 PM Substates > Kernel driver in use: r8169 > Kernel modules: r8169 > > -->03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless > Network Adapter (rev 20) > Subsystem: Lenovo Device 3044 > Flags: bus master, fast devsel, latency 0, IRQ 50 > Memory at c4000000 (64-bit, non-prefetchable) [size=2M] > Capabilities: [40] Power Management version 3 > Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit- > Capabilities: [70] Express Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting > Capabilities: [148] Virtual Channel > Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00 > Capabilities: [178] Latency Tolerance Reporting > Capabilities: [180] L1 PM Substates > Kernel driver in use: ath10k_pci > Kernel modules: ath10k_pci > > 04:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2) > Subsystem: Lenovo Device 381c > Flags: fast devsel, IRQ 16 > Memory at c3000000 (32-bit, non-prefetchable) [size=16M] > Memory at b0000000 (64-bit, prefetchable) [size=256M] > Memory at c0000000 (64-bit, prefetchable) [size=32M] > I/O ports at 3000 [size=128] > Expansion ROM at <ignored> [disabled] > Capabilities: [60] Power Management version 3 > Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ > Capabilities: [78] Express Endpoint, MSI 00 > Capabilities: [100] Virtual Channel > Capabilities: [250] Latency Tolerance Reporting > Capabilities: [258] L1 PM Substates > Capabilities: [128] Power Budgeting <?> > Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> > Capabilities: [900] #19 > Kernel modules: nvidiafb, nouveau > > [root@localhost dedanna]# > > > [root@localhost dedanna]# dmesg | grep ath10k > [ 10.725675] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode > 0 reset_mode 0 > -->[ 11.150508] ath10k_pci 0000:03:00.0: Direct firmware load for > ath10k/cal-pci-0000:03:00.0.bin failed with error -2 > [ 12.895424] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000, > 0x003405ff) fw WLAN.RM.1.1-00141 api 5 htt 3.1 wmi 4 cal otp max_sta 32 > [ 12.895427] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs 0 > testmode 0 > [ 17.551211] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0 > [root@localhost dedanna]# > > > "[root@localhost dedanna]# inxi -n > Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet > Controller > driver: r8169 > IF: enp2s0 state: down mac: 68:f7:28:d0:14:46 > Card-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter > driver: ath10k_pci > IF: wlp3s0 state: down mac: b8:86:87:47:28:81 > Card-3: Atheros > IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A > [root@localhost dedanna]# > > > [root@localhost dedanna]# ls /sys/class/net > enp2s0@ lo@ wlp3s0@ > [root@localhost dedanna]# > > > [root@localhost dedanna]# ip link > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode > DEFAULT group default > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state > DOWN mode DEFAULT group default qlen 1000 > link/ether 68:f7:28:d0:14:46 brd ff:ff:ff:ff:ff:ff > 3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN > mode DORMANT group default qlen 1000 > link/ether b8:86:87:47:28:81 brd ff:ff:ff:ff:ff:ff > [root@localhost dedanna]# > > > If I run: "ip link set wlp3s0 up or down" I get no output whatsoever. > However, I pushed on anyway: > > > [root@localhost dedanna]# ip link show dev wlp3s0 > 3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN > mode DORMANT group default qlen 1000 > link/ether b8:86:87:47:28:81 brd ff:ff:ff:ff:ff:ff > [root@localhost dedanna]# > > > [root@localhost dedanna]# systemctl status network systemd-netorkd.service > ââ network.service - LSB: Bring up/down networking > Loaded: loaded (/etc/rc.d/init.d/network) > Active: inactive (dead) > > ââ systemd-netorkd.service > Loaded: not-found (Reason: No such file or directory) > Active: inactive (dead) > [root@localhost dedanna]# > > > [root@localhost dedanna]# systemctl start network systemd-netorkd.service > Failed to start systemd-netorkd.service: Unit systemd-netorkd.service failed > to load: No such file or directory. > [root@localhost dedanna]# > > > [root@localhost dedanna]# cat /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > [root@localhost dedanna]# > > > I hope this is helpful to you. Code correction: [root@localhost dedanna]# systemctl status network systemd-networkd.service ââ network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: inactive (dead) ââ systemd-networkd.service - Network Service Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled) Active: active (running) since Tue 2015-10-27 10:51:36 MDT; 4min 18s ago Docs: man:systemd-networkd.service(8) Main PID: 1060 (systemd-network) Status: "Processing requests..." CGroup: /system.slice/systemd-networkd.service ââââââ¬1060 /usr/lib/systemd/systemd-networkd [root@localhost dedanna]# Which makes "systemctl start network systemd-netorkd.service" moot, I'm figuring?
Sorry, I had missed some needed fixes for the api 5 firmware, could you try the new kernel: http://mirrors.kernel.org/mageia/distrib/5/x86_64/media/core/updates_testing/kernel-desktop-4.1.12-1.mga5-1-1.mga5.x86_64.rpm
I got the same thing. :( When I get logged in, I get a popup in the lower right of the screen telling me that wireless connections are available, but when I try to connect, I get "Connection failed." every time. :( This is on all of the settings. None, Open WEP, Restricted WEP, and on WPA/WPA2 Pre-shared key. I don't know if it's the AES part of all this that's doing it or what, but it's like we're so close. So close, we're there with it, and then it says "Oops, not really." :(
Where are you trying the "None, Open WEP, Restricted WEP, and on WPA/WPA2 PSK" ? It's the AP you are trying to connect to that needs to be changed to the different modes so we can see if your system can auto-detect / connect to any of them. That's why I suggested to try to connect to an open network, either at home or if you know of some open wifi anywhere near you as we need to confirm that basic connection works before trying encryption.
In drakconnect-->Encryption, and in Network Manager, where we choose the type of encryption, is where I'm trying it. I set it to "None" for the fully open. I'll have chance to try it today on a public wireless connection at the library. Although my connection, I've found, would be Pre-shared key (at home). Although when you said my home connection should work as fully open, I set encryption to "None" and when that didn't work I tried the rest.
It works on McDonald's wireless! :)
I'll be trying the library later on today.
Hello from the library's open connection! On Mageia! Now just need to make my home connection work. *sigh
Created attachment 7179 [details] To show the applets in the tray. Thomas! You did it! I'm connected at home! I was using the wrong applet to try to connect with! I had two applets in my systray. The one I was using I thought was the NetworkManager Applet, but it was a different one. It's the same one that's used in MCC, and it wasn't working there either (I'd tried it several times). Just a few minutes ago I thought, "I wonder what would happen if I try to use the other one?" So, I right-clicked it and chose to connect to my home connection, and it gave my connection as an option so I clicked it. Up popped a dialog box asking for my password, I put it in and off it went! I'm so sorry, I thought I had been using the NetworkManager Applet, but I looked in "About" of this one and it said NetworkManager Applet (the one with the arrow on the right in the screen shot)! Thank you so so much! I'm now typing this from Mageia 5 Firefox, on my home connection! :) I don't know if you can tell which one's which, but I was using the applet that is where the left arrow is. The one I just tried is the one that has the arrow on the right. Thank you so much again! You did it, you did it you did it! Yes!!! :D
Just a heads up, it is doing the "up down up down" thing that I've read about on the connection. I read that people were complaining even after they got their wireless working, because the connection would come up and only be up for a very few minutes, then go back down again. For me, it does stay up longer than what these people are saying. It stays up on my home connection for a good hour or so, sometimes even a bit longer, but then it drops, and won't reconnect. With this being said, it is only on my home connection, which is WPA/WPA2 Pre-shared key. It doesn't do this on a fully open connection, say from the library or other places around town. On my home connection, I end up having to reboot, and then hope and pray that it will come up even then. Sometimes it won't even after a reboot. I know it's not the connection because it doesn't go down for anyone else in the house. I've noticed also that Network Manager will crash here and there; the connection went down completely night before last because Network Manager had crashed. It did this to me a couple of other times as well.
Created attachment 7184 [details] Screen shot of attempt to connect with Network Manager I'm in a situation here. I've reinstalled Mageia to shrink Windows some more, and can't get the connection going no matter what I do. I'm beginning to wonder if Network Manager might be buggy or something. It doesn't matter what applet I use, it doesn't matter anything. I still get this (note the bottom right of the screen) while it's trying to connect, and then I get "Connection failed". I have no clue what to do here? http://bjoernvold.com/forum/viewtopic.php?p=22107#p22107 Thanks.
Created attachment 7185 [details] journalctl and lspcidrake outputs along with things I've tried. On the outputs.txt file, it starts out OK, but as I went on with the next command things started going downhill.
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGASA-2015-0435.html
I'll download the updates with Cygwin/wget again and see if they work. I'm hoping they do.
Updates got it. :) Thank you so much for listening to me and working with me on this! Good work! Closing as "fixed" with updates. Take care!
Sorry didn't know I had to mark this resolved with a comment.
Status: NEW => RESOLVEDResolution: (none) => FIXED
I realize this is out of "line" in a way but I want you to know that it looks like Mageia is the only distro now supporting this hardware. I've just tried the development version of Manjaro and there is absolutely no support for it in it (touting the 4. kernel). I've also tried openSUSE Leap, and Fedora 23. None of the other major players are supporting my hardware. Excellent job! I'm locked into Mageia for a distro now because of this and I don't mind a bit. You've enabled me to run Linux again.
(In reply to Kim Garren from comment #85) > I realize this is out of "line" in a way but I want you to know that it > looks like Mageia is the only distro now supporting this hardware. > > I've just tried the development version of Manjaro and there is absolutely > no support for it in it (touting the 4. kernel). > > I've also tried openSUSE Leap, and Fedora 23. None of the other major > players are supporting my hardware. > > Excellent job! I'm locked into Mageia for a distro now because of this and I > don't mind a bit. You've enabled me to run Linux again. *4.3 kernel