How to get Plymouth working with LUKS encryption after NVIDIA driver installation? The 2019 Stack Overflow Developer Survey Results Are In Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar ManaraHow to fix plymouth (splash screen) in all Ubuntu releases!Why is the resolution incorrectly set on boot after installing the Nvidia drivers?How to install proprietary Nvidia driver in 12.04?Text gets displayed during boot after Nvidia installtionNvidia 840M driver installation Acer E5-571Cannot get right resolution with Nvidia driverUbuntu 16.04 - switching from nouveau to closed source driver, after LUKS auth purple screenCorrect steps to install NVidia driver + CUDA after fresh install of Ubuntu Desktop 16.04.02 LTSHow to enable text-mode LUKS passphrase prompt on boot?Ubuntu won't boot after upgrade to 18.04Using nvidia driver combined with encrypted system drive in Ubuntu 18.04
One-dimensional Japanese puzzle
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?
Drawing vertical/oblique lines in Metrical tree (tikz-qtree, tipa)
Is an up-to-date browser secure on an out-of-date OS?
How to make Illustrator type tool selection automatically adapt with text length
Can I visit the Trinity College (Cambridge) library and see some of their rare books
Single author papers against my advisor's will?
Did the new image of black hole confirm the general theory of relativity?
How to determine omitted units in a publication
Store Dynamic-accessible hidden metadata in a cell
Why are PDP-7-style microprogrammed instructions out of vogue?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
Circular reasoning in L'Hopital's rule
Identify 80s or 90s comics with ripped creatures (not dwarves)
How do spell lists change if the party levels up without taking a long rest?
How to handle characters who are more educated than the author?
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
Could an empire control the whole planet with today's comunication methods?
Button changing its text & action. Good or terrible?
What was the last x86 CPU that did not have the x87 floating-point unit built in?
Do warforged have souls?
How did passengers keep warm on sail ships?
What do I do when my TA workload is more than expected?
How to get Plymouth working with LUKS encryption after NVIDIA driver installation?
The 2019 Stack Overflow Developer Survey Results Are In
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraHow to fix plymouth (splash screen) in all Ubuntu releases!Why is the resolution incorrectly set on boot after installing the Nvidia drivers?How to install proprietary Nvidia driver in 12.04?Text gets displayed during boot after Nvidia installtionNvidia 840M driver installation Acer E5-571Cannot get right resolution with Nvidia driverUbuntu 16.04 - switching from nouveau to closed source driver, after LUKS auth purple screenCorrect steps to install NVidia driver + CUDA after fresh install of Ubuntu Desktop 16.04.02 LTSHow to enable text-mode LUKS passphrase prompt on boot?Ubuntu won't boot after upgrade to 18.04Using nvidia driver combined with encrypted system drive in Ubuntu 18.04
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
When I first set my computer up with LUKS encryption, during boot, right after Grub2, Plymouth takes over and you get a nice graphical screen with the prompt to enter the passphrase. And that screens remain until the Ubuntu desktop opens.
Once I installed the NVIDIA driver for my video card, that graphical screen is gone, and right after Grub2, there is a text screen for passphrase entry, then once decryption takes place, the NVIDIA logo comes up. And on shutdown/restart, it also dumps into a text screen.
I've seen some solutions on fixing Plymouth after an NVIDIA driver is installed, but not sure if that works with LUKS encryption, and I don't want to risk screwing things up and not being able to decrypt the partition.
This is for Xubuntu 14.04.4
nvidia plymouth luks
asked Jul 3 '16 at 22:41
jubjub
1116
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
When I first set my computer up with LUKS encryption, during boot, right after Grub2, Plymouth takes over and you get a nice graphical screen with the prompt to enter the passphrase. And that screens remain until the Ubuntu desktop opens.
Once I installed the NVIDIA driver for my video card, that graphical screen is gone, and right after Grub2, there is a text screen for passphrase entry, then once decryption takes place, the NVIDIA logo comes up. And on shutdown/restart, it also dumps into a text screen.
I've seen some solutions on fixing Plymouth after an NVIDIA driver is installed, but not sure if that works with LUKS encryption, and I don't want to risk screwing things up and not being able to decrypt the partition.
This is for Xubuntu 14.04.4
nvidia plymouth luks
asked Jul 3 '16 at 22:41
jubjub
1116
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I tried the fix presented here: askubuntu.com/questions/362722/… It did bring back the graphical screen, but the resolution was off even though I specified my laptop's resolution of 1600x900. Also there was an error once the desktop was launched: late resume failure [non-free: nvidia] I reverted to the snapshot I took just before trying this. Still looking for a working solution to this issue.
– jub
Jul 4 '16 at 2:46
add a comment |
When I first set my computer up with LUKS encryption, during boot, right after Grub2, Plymouth takes over and you get a nice graphical screen with the prompt to enter the passphrase. And that screens remain until the Ubuntu desktop opens.
Once I installed the NVIDIA driver for my video card, that graphical screen is gone, and right after Grub2, there is a text screen for passphrase entry, then once decryption takes place, the NVIDIA logo comes up. And on shutdown/restart, it also dumps into a text screen.
I've seen some solutions on fixing Plymouth after an NVIDIA driver is installed, but not sure if that works with LUKS encryption, and I don't want to risk screwing things up and not being able to decrypt the partition.
This is for Xubuntu 14.04.4
nvidia plymouth luks
asked Jul 3 '16 at 22:41
jubjub
1116
When I first set my computer up with LUKS encryption, during boot, right after Grub2, Plymouth takes over and you get a nice graphical screen with the prompt to enter the passphrase. And that screens remain until the Ubuntu desktop opens.
Once I installed the NVIDIA driver for my video card, that graphical screen is gone, and right after Grub2, there is a text screen for passphrase entry, then once decryption takes place, the NVIDIA logo comes up. And on shutdown/restart, it also dumps into a text screen.
I've seen some solutions on fixing Plymouth after an NVIDIA driver is installed, but not sure if that works with LUKS encryption, and I don't want to risk screwing things up and not being able to decrypt the partition.
This is for Xubuntu 14.04.4
nvidia plymouth luks
nvidia plymouth luks
asked Jul 3 '16 at 22:41
jubjub
1116
asked Jul 3 '16 at 22:41
jubjub
1116
asked Jul 3 '16 at 22:41
jubjub
1116
asked Jul 3 '16 at 22:41
jubjub
1116
asked Jul 3 '16 at 22:41
jubjub
1116
1116
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I tried the fix presented here: askubuntu.com/questions/362722/… It did bring back the graphical screen, but the resolution was off even though I specified my laptop's resolution of 1600x900. Also there was an error once the desktop was launched: late resume failure [non-free: nvidia] I reverted to the snapshot I took just before trying this. Still looking for a working solution to this issue.
– jub
Jul 4 '16 at 2:46
add a comment |
I tried the fix presented here: askubuntu.com/questions/362722/… It did bring back the graphical screen, but the resolution was off even though I specified my laptop's resolution of 1600x900. Also there was an error once the desktop was launched: late resume failure [non-free: nvidia] I reverted to the snapshot I took just before trying this. Still looking for a working solution to this issue.
– jub
Jul 4 '16 at 2:46
I tried the fix presented here: askubuntu.com/questions/362722/… It did bring back the graphical screen, but the resolution was off even though I specified my laptop's resolution of 1600x900. Also there was an error once the desktop was launched: late resume failure [non-free: nvidia] I reverted to the snapshot I took just before trying this. Still looking for a working solution to this issue.
– jub
Jul 4 '16 at 2:46
I tried the fix presented here: askubuntu.com/questions/362722/… It did bring back the graphical screen, but the resolution was off even though I specified my laptop's resolution of 1600x900. Also there was an error once the desktop was launched: late resume failure [non-free: nvidia] I reverted to the snapshot I took just before trying this. Still looking for a working solution to this issue.
– jub
Jul 4 '16 at 2:46
add a comment |
1 Answer
1
active
oldest
votes
This worked: How to fix plymouth (splash screen) in all Ubuntu releases!
The mistake I made when I first tried it is not using the correct resolution. I used the native resolution of my monitor, 1600x1200. But apparently Grub and Plymouth can have a different max resolution than the monitor and video card.
Since hwinfo is not available on Ubuntu 14.04, I booted into Grub2, dropped to command line and ran vbeinfo. Max resolution listed was 1280x800x32.
So with that info, the solution is:
sudo apt-get install v86d
sudo gedit /etc/default/grub
Find this line:
#GRUB_GFXMODE=640x480
leave commented out and add:
GRUB_GFXMODE=1280x800x32 (use max resolution found using vbeinfo)
GRUB_GFXPAYLOAD_LINUX=keep
Save file, then in terminal:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u
sudo update-grub
This gave me the 'correct' looking resolution for Plymouth both at startup and shutdown. Everything looks like it did before installing the nvidia driver, apart from a brief flash of the nvidia logo between Plymouth and the desktop launching.
I think the 'late resume failure' error report is unrelated, as I did not encounter this error report this time around.
edited Apr 13 '17 at 12:23
Community♦
1
answered Jul 5 '16 at 16:09
jubjub
1116
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f794472%2fhow-to-get-plymouth-working-with-luks-encryption-after-nvidia-driver-installatio%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This worked: How to fix plymouth (splash screen) in all Ubuntu releases!
The mistake I made when I first tried it is not using the correct resolution. I used the native resolution of my monitor, 1600x1200. But apparently Grub and Plymouth can have a different max resolution than the monitor and video card.
Since hwinfo is not available on Ubuntu 14.04, I booted into Grub2, dropped to command line and ran vbeinfo. Max resolution listed was 1280x800x32.
So with that info, the solution is:
sudo apt-get install v86d
sudo gedit /etc/default/grub
Find this line:
#GRUB_GFXMODE=640x480
leave commented out and add:
GRUB_GFXMODE=1280x800x32 (use max resolution found using vbeinfo)
GRUB_GFXPAYLOAD_LINUX=keep
Save file, then in terminal:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u
sudo update-grub
This gave me the 'correct' looking resolution for Plymouth both at startup and shutdown. Everything looks like it did before installing the nvidia driver, apart from a brief flash of the nvidia logo between Plymouth and the desktop launching.
I think the 'late resume failure' error report is unrelated, as I did not encounter this error report this time around.
edited Apr 13 '17 at 12:23
Community♦
1
answered Jul 5 '16 at 16:09
jubjub
1116
add a comment |
This worked: How to fix plymouth (splash screen) in all Ubuntu releases!
The mistake I made when I first tried it is not using the correct resolution. I used the native resolution of my monitor, 1600x1200. But apparently Grub and Plymouth can have a different max resolution than the monitor and video card.
Since hwinfo is not available on Ubuntu 14.04, I booted into Grub2, dropped to command line and ran vbeinfo. Max resolution listed was 1280x800x32.
So with that info, the solution is:
sudo apt-get install v86d
sudo gedit /etc/default/grub
Find this line:
#GRUB_GFXMODE=640x480
leave commented out and add:
GRUB_GFXMODE=1280x800x32 (use max resolution found using vbeinfo)
GRUB_GFXPAYLOAD_LINUX=keep
Save file, then in terminal:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u
sudo update-grub
This gave me the 'correct' looking resolution for Plymouth both at startup and shutdown. Everything looks like it did before installing the nvidia driver, apart from a brief flash of the nvidia logo between Plymouth and the desktop launching.
I think the 'late resume failure' error report is unrelated, as I did not encounter this error report this time around.
edited Apr 13 '17 at 12:23
Community♦
1
answered Jul 5 '16 at 16:09
jubjub
1116
add a comment |
This worked: How to fix plymouth (splash screen) in all Ubuntu releases!
The mistake I made when I first tried it is not using the correct resolution. I used the native resolution of my monitor, 1600x1200. But apparently Grub and Plymouth can have a different max resolution than the monitor and video card.
Since hwinfo is not available on Ubuntu 14.04, I booted into Grub2, dropped to command line and ran vbeinfo. Max resolution listed was 1280x800x32.
So with that info, the solution is:
sudo apt-get install v86d
sudo gedit /etc/default/grub
Find this line:
#GRUB_GFXMODE=640x480
leave commented out and add:
GRUB_GFXMODE=1280x800x32 (use max resolution found using vbeinfo)
GRUB_GFXPAYLOAD_LINUX=keep
Save file, then in terminal:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u
sudo update-grub
This gave me the 'correct' looking resolution for Plymouth both at startup and shutdown. Everything looks like it did before installing the nvidia driver, apart from a brief flash of the nvidia logo between Plymouth and the desktop launching.
I think the 'late resume failure' error report is unrelated, as I did not encounter this error report this time around.
edited Apr 13 '17 at 12:23
Community♦
1
answered Jul 5 '16 at 16:09
jubjub
1116
This worked: How to fix plymouth (splash screen) in all Ubuntu releases!
The mistake I made when I first tried it is not using the correct resolution. I used the native resolution of my monitor, 1600x1200. But apparently Grub and Plymouth can have a different max resolution than the monitor and video card.
Since hwinfo is not available on Ubuntu 14.04, I booted into Grub2, dropped to command line and ran vbeinfo. Max resolution listed was 1280x800x32.
So with that info, the solution is:
sudo apt-get install v86d
sudo gedit /etc/default/grub
Find this line:
#GRUB_GFXMODE=640x480
leave commented out and add:
GRUB_GFXMODE=1280x800x32 (use max resolution found using vbeinfo)
GRUB_GFXPAYLOAD_LINUX=keep
Save file, then in terminal:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
sudo update-initramfs -u
sudo update-grub
This gave me the 'correct' looking resolution for Plymouth both at startup and shutdown. Everything looks like it did before installing the nvidia driver, apart from a brief flash of the nvidia logo between Plymouth and the desktop launching.
I think the 'late resume failure' error report is unrelated, as I did not encounter this error report this time around.
edited Apr 13 '17 at 12:23
Community♦
1
answered Jul 5 '16 at 16:09
jubjub
1116
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
1
answered Jul 5 '16 at 16:09
jubjub
1116
answered Jul 5 '16 at 16:09
jubjub
1116
answered Jul 5 '16 at 16:09
jubjub
1116
1116
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f794472%2fhow-to-get-plymouth-working-with-luks-encryption-after-nvidia-driver-installatio%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I tried the fix presented here: askubuntu.com/questions/362722/… It did bring back the graphical screen, but the resolution was off even though I specified my laptop's resolution of 1600x900. Also there was an error once the desktop was launched: late resume failure [non-free: nvidia] I reverted to the snapshot I took just before trying this. Still looking for a working solution to this issue.
– jub
Jul 4 '16 at 2:46