[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Our systems contain an Intel 8260, 7260, or 3165 Wifi card, and this bug affects all 3 cards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Confirmed Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
This affects the entire System76 product line, including: Lemur 6, Lemur 7, Gazelle 10, Gazelle 11, Kudu 2, Kudu 3, Serval 10, Bonobo 10, Bonobo 11, Meerkat 2, Sable 6, Ratel 5, and other desktop hardware with additional wifi cards added. To reproduce: - Install Ubuntu in OEM mode - Prepare for shipping to end user - Power off system - Power on system. - Go through user setup - Either join or don't join a Wifi during user setup, does not change outcome - Log into user account - Try to join a WiFi network No wifi networks will be shown. This affects Ubuntu 16.04.1 and 16.10, including the following kernels: 4.8.0-26-generic 4.8.0-22-generic 4.4.0-35-generic 4.4.0-47-generic Looking at log messages, there may be a race condition present that a fresh boot does not have. On first boot: [8.824974] iwlwifi :03:00.0 wlp3s0: renamed from wlan0 [9.133313] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [9.206671] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [9.324861] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready On reboot: [3.515363] iwlwifi :03:00.0 wlp3s0: renamed from wlan0 [4.386126] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [4.610799] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [4.712271] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [7.614299] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link becomes ready It appears that the system gives up/times out trying to make the device ready when being booted the first time, but the process happens much faster on later reboots. This is solved by either rebooting, or restarting network-manager, as indicated above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Confirmed Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Changed in: mesa (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Released Status in System76: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in llvm-toolchain-3.8 source package in Xenial: Fix Released Status in mesa source package in Xenial: Invalid Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note: "Download updates while installing Ubuntu" doesn't currently seem to be working. If after installing 16.04 on effected Skylake hardware you find that Unity/Compiz is broken, switch to a VT with Control+Alt+F1, login, and then run: sudo apt-get update sudo apt-get dist-upgrade You should see the `libllvm3.8` package get updated. After a reboot, Unity/Compiz should be working. == In detail == The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
