Description of problem: KDE is installed using a cable After the first re-boot the ethernet cable works, but the Wi-Fi does not work. Version-Release number of selected component (if applicable): The net-install ISO from June 12th. How reproducible: Steps to Reproduce: 1. 2. 3.
Created attachment 8043 [details] journalctl -xb > journalctl-xb.txt Maybe it can tell why the Wi-Fi does not work.
CC: (none) => bjarne.thomsen
Did it worked previously? Please attach (not paste) the /tmp/pci.txt file resulting from running the following command: lspcidrake -v>/tmp/pci.txt From what I saw, you just need to enable wifi (look at rfkill messages)
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud, tmbSource RPM: (none) => kernel?
Created attachment 8050 [details] Output from lspcidrake -v As requested.
Created attachment 8051 [details] Output from ifup wlp3s0 What does it mean to be associated? I did try to configure Wi-Fi from the MCC: Please select your network: "blank spaces" It did not show any of my 2 access points. Would this have been an "association", if it had worked? Another thing: the network applet does not show my IP-address. It only shows: net_applet. Finally: after the latest updates I cannot start MCC from the menue. The Wi-Fi and the applet used to work.
(In reply to Bjarne Thomsen from comment #4) > Created attachment 8051 [details] > Output from ifup wlp3s0 > > What does it mean to be associated? That your network card has successfully authenticated with the desired access point. > I did try to configure Wi-Fi from the MCC: > Please select your network: "blank spaces" > It did not show any of my 2 access points. What Thierry most likely meant when he said (in comment #2) > > From what I saw, you just need to enable wifi (look at rfkill messages) is that you should try to unblock your wlan card, see: https://wiki.mageia.org/en/Setup_wireless_networking#rfkill Please follow the instructions there and report back here what you see and whether you manage to unblock the device.
CC: (none) => marja11
rfkill list: 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 2: phy: Wireless LAN Soft blocked: no Hard Blocked: yes It works with Windows 10. I am confused at a higher level! Are there 2 wireless devices? How can Windows use it? There is NO switch on the outside of the Notebook. Any ideas?
Seeing "two" devices is normal, for the rest I don't have a clue, especially not because it works in Windows 10. Assigning to tmb
Assignee: bugsquad => tmb
Btw, does it still work with older Mga versions? (Assuming wlan worked with them before)
It is quite new. I have only had it for a few days. I have only installed mga6 from cauldron. I am not sure that it worked before. I was occupied solving another problem: I accidentally erased the Windows10 boot-loader from the EFI partition. This has now been restored.
The Fedora24 installer tells me that WiFi is not available. I looks as if Asus has made an anti-linux Notebook. Apparently only an Asus driver works.
The E-handbook for X302U identifies the functioning of all Fn+Fx combinations apart from Fn+F3 and Fn+F4. However, they have no apparent effect. Fn+F2 flips between hard block and soft block of WiFi. How can Windows-10 work? The driver has the same name in Windows and mga6: rlt8723be Maybe there is a driver option telling the driver to ignore the lock?
Created attachment 8141 [details] dmesg for Asus X302U I forgot to attach dmesg. Here it is. rltwifi: Wireless switch is on. So, which switch? Soft og hard?
Suddenly after a new netinstall from the ISO of July 7 the wireless hard blocked was no, and Wi-Fi works! But why?
Not so fast. After a reboot the WiFi is again hardware blocked.
I tried to blacklist asus_nb_wmi in the mga-file for modprobe. Now it produces a lot of errors, but Wi-Fi is no longer blocked. There is also a asus_wmi driver that I did not blacklist. This is probably not the right way to solv the problem, but it might be an indication.
The solution seems to be: create the file /etc/modprobe.d/asus_nb_wmi.conf with this single line options asus_nb_wmi wapf=4 I found this prescription, but I have no idea why it works. The many PCIe Bus Errors are stil there. They must be unrelated.
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
Upgrade of Windows 10 had overwritten something, so I had to re-install mga6. Wi-Fi did not work, and I had forgotten what I did. I had to look it up in this bug-report. /etc/modprobe.d/asus_nb_wmi.conf: options asus_nb_wmi wapf=4
This fix still works.
I guess someone should write a patch similar to https://patchwork.kernel.org/patch/7113541/ with the right IDs for your model
CC: (none) => pterjan
please attach the output of dmidecode so we can match the hw
Created attachment 9488 [details] dmidecode >x302u-dmidecode.txt Output from dmidecode.
Ok, I hoped it was actually an X302UA (which the dmidecode confirms) wich alredy have a patch upstream merged a few months ago and backported that. So there is now a kernel-4.9.37-1.mga6 (currently building) heading to updates_testing that should allow you to remove (or move away) the /etc/modprobe.d/asus_nb_wmi.conf and have it still working. Noth that you should install microcode-0.20170707-1.mga6 from nonfree updates_testing before you install this kernel
Also, in order to properly test this fix, please remove/move away the /etc/modprobe.d/asus_nb_wmi.conf before installing the new kernel so it does not end up in the initrd.
Keywords: NEEDINFO => (none)
Note that kernel-4.9.37-1.mga6 failed building tonight, so you'll need to wait a bit to test Thomas' suggested fix.
After having removed asus_nb_wmi.conf and installed kernel-4.9.37-1.mga6 followed by a reboot, Wi-Fi is now working.
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2017-0234.html
Status: NEW => RESOLVEDResolution: (none) => FIXED