** Description changed: [Impact] - In some cases, the wow is not configured and the + In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). - The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. - But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. - So, the management of wake-on-LAN still is done by NetworkManager. + The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. + But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. + So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] - On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. - Step 1. Enter suspend (s2idle) - Setp 2. Resume from suspend + On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. + Step 1. Enter suspend (s2idle) + Setp 2. Resume from suspend - After resume from suspend, the Wi-Fi functiall still is normal. + After resume from suspend, the Wi-Fi functiall still is normal. - You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: - https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 + You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: + https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] - * No potential regressions. + * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network + won't management the WOW forever. [Other Info] - - * None + + * None
** Description changed: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi functiall still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network - won't management the WOW forever. + won't management the WOW function forever. The WOW function totally + depend on device driver. [Other Info] * None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit Status in OEM Priority Project: New Status in OEM Priority Project focal series: Invalid Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: Incomplete Bug description: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi functiall still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network won't management the WOW function forever. The WOW function totally depend on device driver. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
