I've now booted into 3.19.0-64 and everything seems okay again. But obviously I don't want to get stuck on an out-of-date version, so I'm hoping to get this sorted ASAP.
When you were doing the update, before the restart, did you get a popup asking you to "Disable UEFI Secure Boot"?
I did. So did the person who asked this askubuntu.com question yesterday. But he* doesn't seem to have had any adverse effects, unlike me. (He doesn't mention his hardware or kernel version.) The first comment on that question links to this other question, where the answer by Majal suggests signing some 'kernel modules'. I'm wondering whether that will work for me so that I can go back up to 3.19.0-65
I had to uninstall the last kernel (3.19.0-65) with Synaptic Package Manager to be able to boot with the previous one. If the same problem happens again, is there another way to select a kernel to boot with ?
In order to access 3.19.0-64, I used the grub menu. (I used the answer by "Vojtech Trefny".)
But using 64 is only a temporary solution.
It seems that 65 contains a fix for this security bug. For most people that bug may not be too serious. But what about the next security bug to be found and fixed - perhaps in 66 (for example)? It might be a very serious bug.
So we need to make sure that our problem with 65 is resolved as part of 66 / by the time 66 is released.
Please could everyone who had the problem let me know; when you were doing the update that contained 65, some time before the restart, did you get a popup asking you to "Disable UEFI Secure Boot"? Or was it just me who got that? (And what hardware are you on?)
I've got the "Disable UEFI Secure Boot" popup after installing the mokutil package during an early update. Later on, I've installed the '65' kernel and the wifi has disappeared.... The two phenomena are not linked.
fropus
5 Posts
4482
1
Posted July 14th, 2016 23:00
Same problem here with xps 13 9350 DE (intel wireless) Bluetooth device not recognized either.