Description of problem: I have mageia 6 installed on my notebook since July 2017 and wifi always worked fine. The problem appeared first on October 21 or a few days before that date. When I boot the notebook. I see a message "Failed to start LSB" at the beginning of the boot process even before the boot splash starts. When I'm logged into my desktop there is no wifi connection like there was before. When I try to set up a wifi connection in mcc no wifi networks are shown. LAN is working. But plugging in the ethernet cable has no effect. I have to set up and configure the LAN connection anew in mcc after each boot. Version-Release number of selected component (if applicable): mageia 6 How reproducible: Almost every boot. The weird thing is that sometimes the wifi network works properly after boot. But the last few boots this hasn't been the case. Steps to Reproduce: 1. boot notebook 2. no wifi (and LAN) network connected after login 3. when I want to set up a new wifi network no networks are show
I have to correct something. The first message is "tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]". "Failed to start LSB" comes a bit later.
(In reply to Béat E from comment #1) > I have to correct something. The first message is "tpm_crb MSFT0101:00: > can't request region for resource [mem 0xfed40080-0xfed40fff]". Not sure that error is related to no longer having wifi, afaics one complains about wifi failing in similar bug https://bugzilla.redhat.com/show_bug.cgi?id=1394912 > "Failed to > start LSB" comes a bit later. I see that error, too, yet my network comes up fine later on while booting. Please give the output of: rpm -qa | grep firmware Also, please reboot, become root and run: journalctl -ab > log.txt and _attach_ log.txt to this bug report. Thanks :-)
Keywords: (none) => NEEDINFOCC: (none) => basesystem, kernel, marja11
I have a Asus Zenbook UX490UA-BE012T with Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz. So it looks like I have the same problem as in the Fedora bug report. output of: rpm -qa | grep firmware kernel-firmware-nonfree-20170531-1.mga6.nonfree rtlwifi-firmware-20170531-1.mga6.nonfree ralink-firmware-20170531-1.mga6.nonfree bluez-firmware-1.2-13.mga6.nonfree radeon-firmware-20170531-1.mga6.nonfree kernel-firmware-20170531-1.mga6
Created attachment 9789 [details] output of journalctl -ab > log.txt
I see nov 13 20:00:44 localhost.localdomain network[1095]: rfkill: WLAN soft blocked what is the output of, as root rfkill list If it is indeed soft blocked, can you then try to unblock it (e.g. if the Wireless LAN device is listed after "2: " with, as root, "rfkill unblock 2" and reboot to see whether the network now comes up fine?
output of rfkill list is the following: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no I ran rfkill unlock 1 and afterwards the wifi was working again normally. I always had normal wifi access just after boot so far. I will wait and check whether it will remain this way the coming days.
I just want to add something. There is still the message "tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]" right at the beginning of the booting process. But this doesn't bother me as long as the wifi connection is working.
There are a lot of broken bios implementations out there, and our current kernel 4.9 series does not have workarounds in place for the tpm_crb issue... We will soon-ish switch to 4.14 -longterm kernel that has atleast some improvements for some acpi/tpm/... issues..
CC: (none) => tmb
@ Béat Did the issue (WLAN card getting soft blocked "by itself") occur again, or can this report be closed?
Summary: No wifi anymore: "Failed to start LSB" => No wifi anymore: WLAN was automatically soft blocked
(In reply to Thomas Backlund from comment #8) > There are a lot of broken bios implementations out there, and our current > kernel 4.9 series does not have workarounds in place for the tpm_crb issue... > > We will soon-ish switch to 4.14 -longterm kernel that has atleast some > improvements for some acpi/tpm/... issues.. (In reply to Marja Van Waes from comment #9) > @ Béat > > Did the issue (WLAN card getting soft blocked "by itself") occur again, or > can this report be closed? No reply, closing as OLD. Please change the status of this report to RESOLVED - FIXED if you no longer have this issue. Or to REOPENED if you still have it with kernel-4.14.44-2.mga6
Resolution: (none) => OLDStatus: NEW => RESOLVED
The problem didn't occur again. It is fine that you closed this report. Thanks for your support!
(In reply to Béat E from comment #11) > The problem didn't occur again. It is fine that you closed this report. > Thanks for your support! Thanks for the feedback :-) Changing resolution to FIXED
Resolution: OLD => FIXED