** Also affects: shim (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xorg (Ubuntu)
Status: Confirmed => Invalid
** Changed in: shim (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim
This bug should be mentioned in the release notes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574732
Title:
Regression: Kernel Update in 16.04 from last days renders
** Tags added: bios-outdated-2.40
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574732
Title:
Regression: Kernel Update in 16.04 from last days renders nvidia
driver
** Changed in: xorg (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
First of all, thank you for your fast response! It is amazing!
Yes, there was a question about secure boot, but - just as other users
who experienced the same problem - I was not aware about the significant
change in the handling of secure boot and the consequences thereof.
Formerly Ubuntu worked
That is the goal. I'm surprised that you didn't get a dialog on upgrade
that requested a decision on secure boot mode. You might if you remove
and reinstall the nVidia driver.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thank you for this description. But it seems to be rather complicated
for a normal desktop user, who has been locked out from his system after
the upgrade to 16.04 (unity refuses to start without 3D-Acceleration!).
Couldn't this be done automatically for modules installed as ubuntu
packages?
--
Here is a rough example for how to support 3rd party modules in a secure
boot environment. Note that you have to have Xenial linux 4.4.0-22.38 or
better.
https://docs.google.com/document/d
/1Z1_jR3MmxuvqolQH4PORkJCgENkb2Tlw4FVA-sHqdMw
--
You received this bug notification because you are a
The problem seems to be due to uefi secure boot option now checking also the
keys of modules, which the nvidia driver obviously does not provide. Disabling
secure boot solved the problem for me, but completely disabling it just because
there is no signature for the nvidia driver seems to be a
I just upgraded to 16.04 and can't log in any longer with the latest
(default) kernel 4.4.0-21. If i select an older kernel (4.2.0-35)
everything works fine. Trying to load nvidia drivers manually say
something like 'required key missing' (i would have to reboot with the
latest kernel to see the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Package changed: livepatch-linux-4.4.0-21.37-generic-2 (Ubuntu) =>
ubuntu
** No longer affects: ubuntu
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
What does a manual "modprobe nvidia" (or whatever the failing driver is
called) say.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574732
Title:
Regression: Kernel Update
13 matches
Mail list logo
