[opensuse] Settings to have wifi up and running after boot
Hi all, This is a long standing problem for me. Now I have an ASUS K501 UX laptop with Leap 42.2 and KDE. Tha laptop possibly does not matter, since this was the situation with 42.1 on this laptop and 42.1 on a Lenovo and on another kind of ASUS with 42.2. The symptoms: When I boot, wired connection gets initialized, and usable when I plug in the cord. I would expect that if and when the network cable is not plugged, the wifi starts working automatically. This is not the case and rfkill says wireless is hard blocked. I can only get wifi running if I put the system to sleep (with fn+Zz or mains switch), and then wake it up (with Esc or mains switch). Sometimes this should be done twice. There is another twist: boot+put to sleep + waking always works on one condition: the mains (or battery charger) is plugged. In this case closing the lid suspends the system and opening the lid wakes it up. When the charger is not plugged the above sequence sometimes works and sometimes (mostly) not. Closing the lid suspends the laptop, opening the lid either wakes it up or causes reboot. I do not know and understand how and why these phenomena are connected. What the charger plugged in state has to do with wifi start or reboot. It is mysterious why the things sometimes at least partly work and sometimes why not. And the basic question is: why the configured wifi does not start after or during bootup. Any kind of hints or tips are welcome. Regards, Albert
Albert, Oszkó wrote:
When I boot, wired connection gets initialized, and usable when I plug in the cord. I would expect that if and when the network cable is not plugged, the wifi starts working automatically.
I would expect the wifi to work independently of other interfaces. I don't think there is any way to tie them together, except perhaps with NetworkManager?
This is not the case and rfkill says wireless is hard blocked. I can only get wifi running if I put the system to sleep (with fn+Zz or mains switch), and then wake it up (with Esc or mains switch). Sometimes this should be done twice.
I have a bugreport open on wicked not working with my Intel 3160 wireless, also seems related to booting up with rfkill on. -- Per Jessen, Zürich (3.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/29/2017 08:07 AM, Per Jessen wrote:
I would expect the wifi to work independently of other interfaces. I don't think there is any way to tie them together, except perhaps with NetworkManager?
Why would you want them to be tied together? It's entirely possible the WiFi and Ethernet connections are to entirely different networks. In the event they're on the same one, routing should give priority to Ethernet. In my work, I have set up several business systems, with a backup connection via the cell network. That connection is always up, but used only when the main connection fails. Same thing could apply with WiFi. On my home network, I normally use WiFi for my notebook computer, but will use Ethernet when I want to download a lot of data etc.. It just works that way. I'm on 42.2, but was on 13.1 for quite a while. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-29 15:41, James Knott wrote:
On 01/29/2017 08:07 AM, Per Jessen wrote:
I would expect the wifi to work independently of other interfaces. I don't think there is any way to tie them together, except perhaps with NetworkManager?
Why would you want them to be tied together? It's entirely possible the WiFi and Ethernet connections are to entirely different networks. In the event they're on the same one, routing should give priority to Ethernet.
I expect the wifi to disconnect on connection of the wire, but this does not happen on my laptop on Linux (it does on Windows), I have switch it off manually. Else they collide, the logs fills with martians. However, in the case of the OP it says "wireless is hard blocked", so I expect the user would have to push some button to activate it. Most laptops have one. Albert, your problems seem to be hardware related, but maybe you said that it happened to you on other laptops? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 01/29/2017 09:53 AM, Carlos E. R. wrote:
On 2017-01-29 15:41, James Knott wrote:
On 01/29/2017 08:07 AM, Per Jessen wrote:
I would expect the wifi to work independently of other interfaces. I don't think there is any way to tie them together, except perhaps with NetworkManager? Why would you want them to be tied together? It's entirely possible the WiFi and Ethernet connections are to entirely different networks. In the event they're on the same one, routing should give priority to Ethernet. I expect the wifi to disconnect on connection of the wire, but this does not happen on my laptop on Linux (it does on Windows), I have switch it off manually. Else they collide, the logs fills with martians.
However, in the case of the OP it says "wireless is hard blocked", so I expect the user would have to push some button to activate it. Most laptops have one.
Albert, your problems seem to be hardware related, but maybe you said that it happened to you on other laptops?
I just set up a connection to my home network via Ethernet and tethered to my cell phone via WiFi. "ip route show" lists both, with the Ethernet showing a metric of 100 and WiFi, 600. This metric is what is used to give Ethernet priority when both are connections are up. In Windows 10, I also have both connections up, with metric of 35 for Ethernet and 55 for WiFi. In general, routers can select a route based on "cost". This cost may include metrics for interface bandwidth, hop count, load and more. It is also possible to assign a cost, so that one interface is always favoured over another. This is why the Ethernet port has a lower metric than WiFi. It's preferred when both are available. Otherwise WiFi is used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-29 16:37, James Knott wrote:
On 01/29/2017 09:53 AM, Carlos E. R. wrote:
I just set up a connection to my home network via Ethernet and tethered to my cell phone via WiFi. "ip route show" lists both, with the Ethernet showing a metric of 100 and WiFi, 600. This metric is what is used to give Ethernet priority when both are connections are up.
In Windows 10, I also have both connections up, with metric of 35 for Ethernet and 55 for WiFi.
In general, routers can select a route based on "cost". This cost may include metrics for interface bandwidth, hop count, load and more. It is also possible to assign a cost, so that one interface is always favoured over another. This is why the Ethernet port has a lower metric than WiFi. It's preferred when both are available. Otherwise WiFi is used.
In my case, with both interfaces up (connected to the same router) it doesn't work right. I don't remember now if I get successful connectivity or not. What I remember is that the log fills wit martian packages reports, so things are not right. I have to remember to kill the Wi-Fi with the switch. The other day I configured both interfaces to assume the same IP. After all, I want to access ssh by name to the laptop, regardless of interface, using the same name. This is a recent change, the problem observed in the previous paragraph has been going on for years. My observation on Windows is that the WiFi automatically disconnects (light is up, interface is down in network properties) when I plug in the cable. This is the behaviour I want in Linux. I have no intention to route between interfaces. But this is not the OP problem. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 01/30/2017 08:50 AM, Carlos E. R. wrote:
In my case, with both interfaces up (connected to the same router) it doesn't work right. I don't remember now if I get successful connectivity or not. What I remember is that the log fills wit martian packages reports, so things are not right.
I have never seen that and I have been running WiFi here for over 15 years.
I have to remember to kill the Wi-Fi with the switch.
The other day I configured both interfaces to assume the same IP. After all, I want to access ssh by name to the laptop, regardless of interface, using the same name. This is a recent change, the problem observed in the previous paragraph has been going on for years.
That could cause problems. I use DHCP, so that each interface gets a unique address.
My observation on Windows is that the WiFi automatically disconnects (light is up, interface is down in network properties) when I plug in the cable. This is the behaviour I want in Linux. I have no intention to route between interfaces.
Not on my computer running Windows 10. I do this all the time at work on W7. The WiFi is connected to the office network and I often have the Ethernet port connected to some equipment I'm configuring or testing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-30 14:50, Carlos E. R. wrote:
On 2017-01-29 16:37, James Knott wrote:
On 01/29/2017 09:53 AM, Carlos E. R. wrote:
...
In my case, with both interfaces up (connected to the same router) it doesn't work right. I don't remember now if I get successful connectivity or not. What I remember is that the log fills wit martian packages reports, so things are not right.
I have to remember to kill the Wi-Fi with the switch.
The other day I configured both interfaces to assume the same IP. After all, I want to access ssh by name to the laptop, regardless of interface, using the same name. This is a recent change, the problem observed in the previous paragraph has been going on for years.
And now it works. With both interfaces in the same IP, it simply works. No "martians". However, the command "route" takes a minute to finish. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
James Knott wrote:
On 01/29/2017 08:07 AM, Per Jessen wrote:
I would expect the wifi to work independently of other interfaces. I don't think there is any way to tie them together, except perhaps with NetworkManager?
Why would you want them to be tied together? It's entirely possible the WiFi and Ethernet connections are to entirely different networks.
Obviously.
In the event they're on the same one, routing should give priority to Ethernet.
I doubt if that is the case on openSUSE, but I am prepared to be surprised.
In my work, I have set up several business systems, with a backup connection via the cell network. That connection is always up, but used only when the main connection fails. Same thing could apply with WiFi.
It could, I just don't know of such a setup in openSUSE. Maybe with NetworkManager (which I don't know very well at all).
On my home network, I normally use WiFi for my notebook computer, but will use Ethernet when I want to download a lot of data etc.. It just works that way.
I'll have to try it out. Did you need any special setup? Is it with wicked or NetworkManager? -- Per Jessen, Zürich (5.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/29/2017 10:11 AM, Per Jessen wrote:
On my home network, I normally use WiFi for my notebook
computer, but will use Ethernet when I want to download a lot of data etc.. It just works that way. I'll have to try it out. Did you need any special setup? Is it with wicked or NetworkManager?
I use NetworkManager on my notebook. As I mentioned in another note, each interface has a metric that is used to select the preferred connection, when both are available. It works in a similar manner in both Linux and Windows, as that has long been part of routing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/29/2017 10:11 AM, Per Jessen wrote:
On my home network, I normally use WiFi for my notebook
computer, but will use Ethernet when I want to download a lot of data etc.. It just works that way. I'll have to try it out. Did you need any special setup? Is it with wicked or NetworkManager?
I use NetworkManager on my notebook. As I mentioned in another note, each interface has a metric that is used to select the preferred connection, when both are available.
Cool - I rarely use NetworkManager, just never got used to it.
It works in a similar manner in both Linux and Windows, as that has long been part of routing.
What does your route table look like when you have both interfaces active (presumably on the same network) ? Just being curious. -- Per Jessen, Zürich (2.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
extra note - you might also check asus website and see if your running the latest bios. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/29/2017 12:53 PM, Per Jessen wrote:
James Knott wrote:
On 01/29/2017 10:11 AM, Per Jessen wrote:
On my home network, I normally use WiFi for my notebook
computer, but will use Ethernet when I want to download a lot of data etc.. It just works that way. I'll have to try it out. Did you need any special setup? Is it with wicked or NetworkManager?
I use NetworkManager on my notebook. As I mentioned in another note, each interface has a metric that is used to select the preferred connection, when both are available. Cool - I rarely use NetworkManager, just never got used to it.
It works in a similar manner in both Linux and Windows, as that has long been part of routing. What does your route table look like when you have both interfaces active (presumably on the same network) ? Just being curious.
Here it is with both Ethernet & WiFi connected to my local network:
ip route show default via 172.16.1.1 dev eth0 proto static metric 100 default via 172.16.1.1 dev wlan0 proto static metric 600 172.16.1.0/24 dev eth0 proto kernel scope link src 172.16.1.42 metric 100 172.16.1.0/24 dev wlan0 proto kernel scope link src 172.16.1.40 metric 600
And again, with WiFi connected to my cell phone:
ip route show default via 172.16.1.1 dev eth0 proto static metric 100 default via 192.168.43.1 dev wlan0 proto static metric 600 172.16.1.0/24 dev eth0 proto kernel scope link src 172.16.1.42 metric 100 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.244 metric 600
Note the metric values for each interface. At 600, WiFi has a higher cost than Ethernet (100). This means Ethernet will be the preferred connection. The exception would be to a network that's available only via WiFi, which is the 192.168.43.0 network on my cell phone. In a computer, the metric is assigned, but might also take bandwidth into consideration. Routers use routing protocols, such as OSPF, EIGRP, RIP etc., to automagically calculate a metric based on factors such as bandwidth, hop count, traffic load, etc., in addition to assigned metrics. BTW, the addresses listed above are secret, so tell anyone about them. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/29/2017 02:29 PM, James Knott wrote:
The exception would be to a network that's available only via WiFi, which is the 192.168.43.0 network on my cell phone.
Perhaps I should have phrased that differently. The computer "knows" the connection to that network is via WiFi, so it won't bother trying the default route, which would be via Ethernet. The default route is used only when the path to the desired network is not known. It is also possible to specify the preferred connection with the route command. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
there are better experts on here, but: - i have tumbleweed + same wifi and works fine, have you thought of upgrading the kernel? - you havnt said if your using NM or wicked etc - you should give the results of sudo dmesg | grep iwlwifi - your not clear if this is suspend to ram or disk (lid action etc are configurable) - do you have any reports from journal during wake up? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2017-01-29 14:42 keltezéssel, nicholas írta:
there are better experts on here, but: - i have tumbleweed + same wifi and works fine, have you thought of upgrading the kernel? - you havnt said if your using NM or wicked etc - you should give the results of sudo dmesg | grep iwlwifi - your not clear if this is suspend to ram or disk (lid action etc are configurable) - do you have any reports from journal during wake up?
Thank you for the contributions so far. As to the questions: I did not find yet a physical button (yet) which enables wifi. There is a panel that can be called from the tray (with wifi and airplane mode) but I cannot enable wifi by clicking into the square. And I forgot to mention that the system comes up with the airplane mode control lamp on. I use network manager The result of the command: berci@linux-sst0:~> sudo dmesg | grep iwlwifi root's password: [ 11.452551] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2 [ 11.452606] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2 [ 11.452641] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2 [ 11.485762] iwlwifi 0000:03:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 12.236329] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210 [ 12.236404] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 12.236595] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 12.327878] Modules linked in: tpm_crb(+) elan_i2c iwlmvm(+) snd_pcm int3403_thermal ablk_helper pcspkr mac80211 mei_me(+) mei intel_lpss_pci(+) intel_lpss_acpi intel_lpss snd_timer pinctrl_sunrisepoint pinctrl_intel processor_thermal_device int3402_thermal int3400_thermal intel_soc_dts_iosf int340x_thermal_zone acpi_thermal_rel r8169 cryptd i2c_i801 mfd_core mii snd iwlwifi cfg80211 soundcore fjes rfkill shpchp acpi_pad battery thermal processor ac btrfs xor raid6_pq sd_mod hid_generic usbhid crc32c_intel serio_raw nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci libahci xhci_pci drm xhci_hcd libata usbcore usb_common i2c_hid wmi video button sg scsi_mod efivarfs autofs4 [ 25.713394] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio. [ 114.921255] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio. [ 117.491939] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.492132] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.552395] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.552603] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.300107] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.300303] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.359897] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.360086] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled In the settings of energy saving (I do not know the original phrase) closing the lid causes suspend - not knowing whether to RAM or disc. Sorry, but I do not understand the last questions relating to journal. Kernel upgrade? Maybe. Wifi did not work at all with 4.1.x kernel on leap. Now it works - sortof. Regards, Albert
On Sunday, 29 January 2017 18:45:28 CET Albert, Oszkó wrote:
2017-01-29 14:42 keltezéssel, nicholas írta:
there are better experts on here, but: - i have tumbleweed + same wifi and works fine, have you thought of upgrading the kernel? - you havnt said if your using NM or wicked etc - you should give the results of sudo dmesg | grep iwlwifi - your not clear if this is suspend to ram or disk (lid action etc are configurable) - do you have any reports from journal during wake up?
Thank you for the contributions so far.
As to the questions:
I did not find yet a physical button (yet) which enables wifi. There is a panel that can be called from the tray (with wifi and airplane mode) but I cannot enable wifi by clicking into the square. And I forgot to mention that the system comes up with the airplane mode control lamp on.
I use network manager
The result of the command:
berci@linux-sst0:~> sudo dmesg | grep iwlwifi root's password: [ 11.452551] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2 [ 11.452606] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2 [ 11.452641] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2 [ 11.485762] iwlwifi 0000:03:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 12.236329] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210 [ 12.236404] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 12.236595] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 12.327878] Modules linked in: tpm_crb(+) elan_i2c iwlmvm(+) snd_pcm int3403_thermal ablk_helper pcspkr mac80211 mei_me(+) mei intel_lpss_pci(+) intel_lpss_acpi intel_lpss snd_timer pinctrl_sunrisepoint pinctrl_intel processor_thermal_device int3402_thermal int3400_thermal intel_soc_dts_iosf int340x_thermal_zone acpi_thermal_rel r8169 cryptd i2c_i801 mfd_core mii snd iwlwifi cfg80211 soundcore fjes rfkill shpchp acpi_pad battery thermal processor ac btrfs xor raid6_pq sd_mod hid_generic usbhid crc32c_intel serio_raw nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci libahci xhci_pci drm xhci_hcd libata usbcore usb_common i2c_hid wmi video button sg scsi_mod efivarfs autofs4 [ 25.713394] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio. [ 114.921255] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio. [ 117.491939] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.492132] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.552395] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.552603] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.300107] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.300303] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.359897] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.360086] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
In the settings of energy saving (I do not know the original phrase) closing the lid causes suspend - not knowing whether to RAM or disc.
Sorry, but I do not understand the last questions relating to journal.
Kernel upgrade? Maybe. Wifi did not work at all with 4.1.x kernel on leap. Now it works - sortof.
Regards, Albert
so the journal is in yast-menu::systemd-journal its a record of significant events on your pc, so if you where to look around troublesome events you might find some clues (but suspend issues etc might not get recorded) i dont know whats wrong with your wifi but there are a couple of threads with the same issue/solution as presented in https://forums.linuxmint.com/ viewtopic.php?t=234493 if your problems can be fixed then all good, but in general newer hardware runs better on newer kernels. a note - i appear to have same wifi as yours but mine loads at iwlwifi-7265D-22.ucode whilst yours loads 16 - maybe someone wiser than myself will understand why. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2017-01-29 19:59 keltezéssel, nicholas írta:
2017-01-29 14:42 keltezéssel, nicholas írta:
there are better experts on here, but: - i have tumbleweed + same wifi and works fine, have you thought of upgrading the kernel? - you havnt said if your using NM or wicked etc - you should give the results of sudo dmesg | grep iwlwifi - your not clear if this is suspend to ram or disk (lid action etc are configurable) - do you have any reports from journal during wake up? Thank you for the contributions so far.
As to the questions:
I did not find yet a physical button (yet) which enables wifi. There is a panel that can be called from the tray (with wifi and airplane mode) but I cannot enable wifi by clicking into the square. And I forgot to mention that the system comes up with the airplane mode control lamp on.
I use network manager
The result of the command:
berci@linux-sst0:~> sudo dmesg | grep iwlwifi root's password: [ 11.452551] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2 [ 11.452606] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2 [ 11.452641] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2 [ 11.485762] iwlwifi 0000:03:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm [ 12.236329] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210 [ 12.236404] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 12.236595] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 12.327878] Modules linked in: tpm_crb(+) elan_i2c iwlmvm(+) snd_pcm int3403_thermal ablk_helper pcspkr mac80211 mei_me(+) mei intel_lpss_pci(+) intel_lpss_acpi intel_lpss snd_timer pinctrl_sunrisepoint pinctrl_intel processor_thermal_device int3402_thermal int3400_thermal intel_soc_dts_iosf int340x_thermal_zone acpi_thermal_rel r8169 cryptd i2c_i801 mfd_core mii snd iwlwifi cfg80211 soundcore fjes rfkill shpchp acpi_pad battery thermal processor ac btrfs xor raid6_pq sd_mod hid_generic usbhid crc32c_intel serio_raw nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci libahci xhci_pci drm xhci_hcd libata usbcore usb_common i2c_hid wmi video button sg scsi_mod efivarfs autofs4 [ 25.713394] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio. [ 114.921255] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio. [ 117.491939] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.492132] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.552395] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 117.552603] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.300107] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.300303] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.359897] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled [ 3617.360086] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
In the settings of energy saving (I do not know the original phrase) closing the lid causes suspend - not knowing whether to RAM or disc.
Sorry, but I do not understand the last questions relating to journal.
Kernel upgrade? Maybe. Wifi did not work at all with 4.1.x kernel on leap. Now it works - sortof.
Regards, Albert so the journal is in yast-menu::systemd-journal its a record of significant events on your pc, so if you where to look around
On Sunday, 29 January 2017 18:45:28 CET Albert, Oszkó wrote: troublesome events you might find some clues (but suspend issues etc might not get recorded)
i dont know whats wrong with your wifi but there are a couple of threads with the same issue/solution as presented in https://forums.linuxmint.com/ viewtopic.php?t=234493
if your problems can be fixed then all good, but in general newer hardware runs better on newer kernels.
a note - i appear to have same wifi as yours but mine loads at iwlwifi-7265D-22.ucode whilst yours loads 16 - maybe someone wiser than myself will understand why.
Back then, in the 42.1 era, I replaced 4.1.x kernel with a 4.5.x one to have wifi and touchpad. I do not remember, how network was initialized. But I do remember that after a kernel update the laptop was practically unbootable, and had to begin installation from scratch. So I am a bit afraid of going to a newer kernel. I see that some other distros (ubuntu, mint, manjaro) use 4.8 kernels. Think it over- Albert
On 2017-01-29 18:45, Albert, Oszkó wrote:
2017-01-29 14:42 keltezéssel, nicholas írta:
As to the questions:
I did not find yet a physical button (yet) which enables wifi. There is a panel that can be called from the tray (with wifi and airplane mode) but I cannot enable wifi by clicking into the square. And I forgot to mention that the system comes up with the airplane mode control lamp on.
Can you switch airplane mode off?
In the settings of energy saving (I do not know the original phrase) closing the lid causes suspend - not knowing whether to RAM or disc.
If the settings say "suspend" then that is ram. The wording for "to disk" is "hibernate". Anyway, on suspend mode there usually is a blinking light. Another mode is "hybrid". Everything is saved to disk as in hibernate, but it suspends to ram. Recovery is very fast, but if the battery fails and the ram is thus erased, the recovery is made from disk.
Sorry, but I do not understand the last questions relating to journal.
In a terminal: su - journalctl And use the cursor keys or pgup/dn to move around and read the messages. Immediately after recovery from suspend you will see the messages about suspending. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
2017-01-30 15:13 keltezéssel, Carlos E. R. írta:
On 2017-01-29 18:45, Albert, Oszkó wrote:
2017-01-29 14:42 keltezéssel, nicholas írta:
As to the questions:
I did not find yet a physical button (yet) which enables wifi. There is a panel that can be called from the tray (with wifi and airplane mode) but I cannot enable wifi by clicking into the square. And I forgot to mention that the system comes up with the airplane mode control lamp on. Can you switch airplane mode off?
In the settings of energy saving (I do not know the original phrase) closing the lid causes suspend - not knowing whether to RAM or disc. If the settings say "suspend" then that is ram. The wording for "to disk" is "hibernate". Anyway, on suspend mode there usually is a blinking light.
Another mode is "hybrid". Everything is saved to disk as in hibernate, but it suspends to ram. Recovery is very fast, but if the battery fails and the ram is thus erased, the recovery is made from disk.
Sorry, but I do not understand the last questions relating to journal. In a terminal:
su - journalctl
And use the cursor keys or pgup/dn to move around and read the messages. Immediately after recovery from suspend you will see the messages about suspending.
Sorry for not responding, but I did not manage to keep away flu epidemic... I took the risk and tried to install a newer kernel version on another Asus machine, but nothing changed even with 4.10.x kernel I found a.page which gives no solution, but publish complaints about the same symptoms I have. The contributors have mostly Asus and Dell laptops, all equipped with Intel AC 7265 wifi. The distros are also different, opensuse and ubuntu mostly. Windows alway worked. Albert
On Wednesday, 1 February 2017 16:04:37 CET Albert Oszkó wrote:
2017-01-30 15:13 keltezéssel, Carlos E. R. írta:
On 2017-01-29 18:45, Albert, Oszkó wrote:
2017-01-29 14:42 keltezéssel, nicholas írta:
As to the questions:
I did not find yet a physical button (yet) which enables wifi. There is a panel that can be called from the tray (with wifi and airplane mode) but I cannot enable wifi by clicking into the square. And I forgot to mention that the system comes up with the airplane mode control lamp on.
Can you switch airplane mode off?
In the settings of energy saving (I do not know the original phrase) closing the lid causes suspend - not knowing whether to RAM or disc.
If the settings say "suspend" then that is ram. The wording for "to disk" is "hibernate". Anyway, on suspend mode there usually is a blinking light.
Another mode is "hybrid". Everything is saved to disk as in hibernate, but it suspends to ram. Recovery is very fast, but if the battery fails and the ram is thus erased, the recovery is made from disk.
Sorry, but I do not understand the last questions relating to journal.
In a terminal:
su - journalctl
And use the cursor keys or pgup/dn to move around and read the messages. Immediately after recovery from suspend you will see the messages about suspending.
Sorry for not responding, but I did not manage to keep away flu epidemic...
I took the risk and tried to install a newer kernel version on another Asus machine, but nothing changed even with 4.10.x kernel
I found a.page which gives no solution, but publish complaints about the same symptoms I have. The contributors have mostly Asus and Dell laptops, all equipped with Intel AC 7265 wifi. The distros are also different, opensuse and ubuntu mostly. Windows alway worked.
Albert
from a search i found [1] which seems to describe your problems exactly. he references a ubuntu forum post. he presents a ubuntu forum page he indicates as the solution further down. I believe (please check) its the same solution as given in [2] which is echo "options asus-nb-wmi wapf=4" | sudo tee /etc/ modprobe.d/asus-nb-wmi.conf [1] echo "options asus-nb-wmi wapf=4" | sudo tee /etc/modprobe.d/asus-nb- wmi.conf (read senkora) [2] https://forums.linuxmint.com/viewtopic.php?t=234493 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
from a search i found [1] which seems to describe your problems exactly. he references a ubuntu forum post. he presents a ubuntu forum page he indicates as the solution further down. I believe (please check) its the same solution as given in [2] which is echo "options asus-nb-wmi wapf=4" | sudo tee /etc/ modprobe.d/asus-nb-wmi.conf
[1] echo "options asus-nb-wmi wapf=4" | sudo tee /etc/modprobe.d/asus-nb- wmi.conf (read senkora) [2] https://forums.linuxmint.com/viewtopic.php?t=234493
paste error, should read: ref [1] should be https://www.reddit.com/r/linux/ comments/4ud9sz/asus_k501ux_or_similar_for_linux/ (read senkora) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Albert Oszkó -
Albert, Oszkó
-
Carlos E. R. -
James Knott -
nicholas -
Per Jessen