Proprietary Driver Issues
MoKSB State
I was able to log in to TTY
using ctrl+alt+F1
, but had no internet access seeing as the driver is proprietary as well.
No Xorg issues were apparent.
I decided to remove the packages when I recieved the MokSB failed
message telling me that it could NOT change the secure boot settings. The notable part is that it prompted me for a password even though it failed.
Secure Boot
Caution: Do NOT just blindly remove your drivers!
A good test to see if it is a Proprietary Driver issue is to turn OFF Secure Boot and boot Ubuntu and attempt to login. If logging in works, then you now know what you're issue is.
Broadcom Drivers and Nvidia Drivers
I removed nvidia packages
sudo apt-get purge nvidia-*
and then I removed the broadcom packages
sudo apt-get purge bcmwl-kernel-source
and rebooted.
I attempted to login again and success!
I saw my desktop!
I rebooted again.
logged in again and everything was set to default.
I rebooted into BIOS
turned off secure boot (not recommended, need a better solution)
booted up ubuntu using grub
logged in and installed the downloaded *.deb file for my wifi driver
installed it using Software Center
and rebooted.
I followed the same procedure for my nvidia drivers seeing as the default video drivers are awful on my card.
Turning Secure Boot On Again
If I turn on Secure Boot again, I see the same issue. Since the drivers are NOT signed, it's not a true Secure Boot and I get locked out.
Personally, I find this to be a very bogus (and annoying) issue.
Alternative Solution?
The most feasible solution I saw was customizing the kernel seeing as I can't simply leave Secure Boot off and turn it On and then Off when I switch OS's. Again, it's just annoying.
UPDATE on Jan 4 2017
According to this article, the Linux Kernel >= 4.6 now officially supports
GeForce GTX 900 series accelerated support in conjunction with signed
firmware images.
This should resolve the secure boot issue caused by using the unsigned firmware images.
sudo ubuntu-drivers devices
, and thensudo apt-get install
the recommended driver. – kabdulla Apr 4 '17 at 7:05/var/log/syslog
and check for any error that might relate to something you did recently. My issue was an error related toflatpak
, which I've installed the day before but ended up not needing it. After uninstalling it, everything went back to normal. – dferrazm Jun 6 '19 at 10:00