Fedora Account System
Red Hat Associate
Red Hat Customer
Hi, this is basically the same report as bug 1529696 (https://bugzilla.redhat.com/show_bug.cgi?id=1529696). Our customer experiences it on all their Lenovo G50 and Z50 laptops. They've tested a few with Ubuntu 18.04.1 LTS and they can connect just fine to 5GHz AP's on the same hardware with that. Definitely seems related to the Fedora kernel/firmware thus. Awaiting log files from the customer. Another person (Bogumił) has responded to the old bug with the same issues as well. Seriously doubt it's a defect in the hardware of the original reporter. In our case it definitely isn't. -- We create a bootable distro entirely based on Fedora with which exams are taken (locked down client). My next steps are to install Ubuntu 18.04.1 somewhere, compare the firmware that uses, replace the firmware with those in our initrd if not identical and see if that alleviates the issue. Hope to be back with additional details soon.
From bug 1529696 : > In any case I can fairly easy determine if the firmware differs. Will do > that shortly, kernel itself might be another story however. Not a low-level > programmer and not well versed with all the stuff that might be related to > it. Understood. First of all check if this is a firmware issue (e.g. copy the relevant firmware files from the working Ubuntu version) do not forget to copy both the wifi and the bluetooth files, since bluetooth bugs might interfer with wifi. If this is a firmware issue, please file a bug for this upstream following these instructions: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging If this is not a firmware issue, I expect this to be an upstream kenrel issue. To test this pick a Fedora kernel with the same base version as the Ubuntu kernel then that will hopefully work (we typically do not carry any patches to the iwlwifi driver, I don't know about Ubuntu). To install a Fedora kernel of the same base version (e.g. if Ubuntu uses 4.17.5, pick a Fedora 4.17.5 kernel) go to: https://koji.fedoraproject.org/koji/packageinfo?packageID=8 You probably need to click next-page a couple of times to get to the older kernels. Then click on a build with the right version (it does not matter for which Fedora (27/28/29) it was build) and follow these instructions to install: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt Note since these are official builds I think you can ignore the instruction to disable secure-boot. If this fixes things, it would be good if you can figure out which kernel broke it. E.g. if 4.17.5 works, try the latest 4.17.z if that breaks, try different 4.17.z versions until you've found the first one which breaks. If 4.17.5 works and the latest 4.17.z works, try 4.18.0 if 4.18.0 does not break try the latest 4.18.z, then either find the first broken, or move to 4.19.0, etc. Note all kernel versions here are examples I'm not saying that 4.17.5 will work. Once you've pinpointed this as being introduced in kernel version x.y.z, please file a bug for this upstream following these instructions: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging And add a note there about which kernel version this was introduced.
Hi Hans/others, I've gotten the logs from the customer. Unfortunately the iwlwifi output isn't very informative to me. The only, to me rather useless, thing it outputs with regards to the firmware is this line: iwlwifi 0000:02:00.0: loaded firmware version 17.948900127.0 op_mode iwlmvm That doesn't tell me anything about the files it loads however, and there's quite a few. To compare I've copied /lib/firmware/iwlwifi-3160* from both Ubuntu 18.04.1 fully updated and our Fedora 28 initrd into directories (u for ubuntu, f for fedora): ./f: total 5704 -rw-r--r--. 1 ferry ferry 609892 Nov 21 13:53 iwlwifi-3160-10.ucode -rw-r--r--. 1 ferry ferry 683996 Nov 21 13:53 iwlwifi-3160-12.ucode -rw-r--r--. 1 ferry ferry 688616 Nov 21 13:53 iwlwifi-3160-13.ucode -rw-r--r--. 1 ferry ferry 918212 Nov 21 13:53 iwlwifi-3160-16.ucode -rw-r--r--. 1 ferry ferry 918268 Nov 21 13:53 iwlwifi-3160-17.ucode -rw-r--r--. 1 ferry ferry 670484 Nov 21 13:53 iwlwifi-3160-7.ucode -rw-r--r--. 1 ferry ferry 667284 Nov 21 13:53 iwlwifi-3160-8.ucode -rw-r--r--. 1 ferry ferry 669872 Nov 21 13:53 iwlwifi-3160-9.ucode ./u: total 5704 -rw-r--r--. 1 ferry ferry 609892 Nov 21 13:53 iwlwifi-3160-10.ucode -rw-r--r--. 1 ferry ferry 683996 Nov 21 13:53 iwlwifi-3160-12.ucode -rw-r--r--. 1 ferry ferry 688616 Nov 21 13:53 iwlwifi-3160-13.ucode -rw-r--r--. 1 ferry ferry 918212 Nov 21 13:53 iwlwifi-3160-16.ucode -rw-r--r--. 1 ferry ferry 918268 Nov 21 13:53 iwlwifi-3160-17.ucode -rw-r--r--. 1 ferry ferry 670484 Nov 21 13:53 iwlwifi-3160-7.ucode -rw-r--r--. 1 ferry ferry 667284 Nov 21 13:53 iwlwifi-3160-8.ucode -rw-r--r--. 1 ferry ferry 669872 Nov 21 13:53 iwlwifi-3160-9.ucode [ferry@bcld-builder3 c]$ diff -r u f Binary files u/iwlwifi-3160-17.ucode and f/iwlwifi-3160-17.ucode differ So there's at least 8 firmware files, it might load ones that don't have 3160 in the name as well. Of these 8 files, which might not be the entire picture, only 1 differs. I've ran grep -nr 948900127 /lib/firmware In hopes of finding (part of) the version number in one of the files, but it's probably encoded in some format, because there are no hits whatsoever (did this on the full firmware directory, not just the 8 files with iwlwifi-3160 in the name). Tried running strings on several of them as well, but didn't see anything useful in the output. Do you have any idea how I can determine what firmware files it actually loads?
Created attachment 1507681 [details] Log files on one of the laptops
The iwlwifi-3160-17.ucode differs between FC29 and Ubuntu 18.04.1. It however is identical to FC28 in the original image we have. Latest tests have been done with updated kernel/firmware and then the difference exists, but not the original one in which the issue also exists. Creating an initrd now with the entire /lib/firmware from Ubuntu 18.04.1. If that doesn't help we'll ask them to ship the hardware to us for testing. Also asked to use parameters 'debug iwlwifi.debug=0xf', perhaps that will provide something useful. Thanks for the aid so far!
The wifi driver is not loaded in the initrd, so you need to update the rootfs /lib/firmware, not the initrd's one.
Normally it isn't, but in our case it is. We put the entire filesystem in initrd and run it from RAM.
I'm having the same issue using an Intel 7260 card in a Thinkpad T440s. 5ghz is very flaky, if it connects at all.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.