Black screen beteen GRUB and login screen
So i Bought a Lenovo Legion Y530 and installed Ubuntu 18.04 Lts.
So far so good, update nvidia drivers and got everything up and running.
The issue is that i get a black screen for about 20-30 second before the login screen, i hade tried everything. Changing modeset etc but this doesnt go away do you guys know something about this?
I have a m.2 ssd so this long bort shouldnt be happening
boot
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
add a comment |
So i Bought a Lenovo Legion Y530 and installed Ubuntu 18.04 Lts.
So far so good, update nvidia drivers and got everything up and running.
The issue is that i get a black screen for about 20-30 second before the login screen, i hade tried everything. Changing modeset etc but this doesnt go away do you guys know something about this?
I have a m.2 ssd so this long bort shouldnt be happening
boot
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
add a comment |
So i Bought a Lenovo Legion Y530 and installed Ubuntu 18.04 Lts.
So far so good, update nvidia drivers and got everything up and running.
The issue is that i get a black screen for about 20-30 second before the login screen, i hade tried everything. Changing modeset etc but this doesnt go away do you guys know something about this?
I have a m.2 ssd so this long bort shouldnt be happening
boot
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
So i Bought a Lenovo Legion Y530 and installed Ubuntu 18.04 Lts.
So far so good, update nvidia drivers and got everything up and running.
The issue is that i get a black screen for about 20-30 second before the login screen, i hade tried everything. Changing modeset etc but this doesnt go away do you guys know something about this?
I have a m.2 ssd so this long bort shouldnt be happening
boot
boot
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
edited Dec 30 '18 at 17:38
Allamo Olsson
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
asked Dec 30 '18 at 17:24
Allamo OlssonAllamo Olsson
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
To see what is happening during the 20 to 30 seconds use:
sudo -H gedit /etc/default/grub
Find the line that starts with:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
and change it to:
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth
Leave the rest of the line as is.
Now save the file and exit gedit
Run:
sudo update-grub
Now when you reboot you will see the messages scroll by as the kernel boots up. If it gets stuck on one message for more than a second note it and add it to your question.
For a detailed time break down of your boot use:
systemd-analyze blame
The longest running boot commands are listed first. Use Q to exit the command.
Systemd log messages
After completing above steps this error is revealed during boot up:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Arch Linux references this error here.
Unix & Linux describes LVM setup errors here.
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
I get, failed to Connect lvmetad, gamling back to scanning.
– Allamo Olsson
Dec 31 '18 at 6:35
@AllamoOlsson I've updated my answer with your error message. It appears you installed usingLVMoption which isn't required for the average user. It's designed for partitions spanning multiple disks like a server would use. You can reinstall without LVM option if you have a new installation and nothing to loose.
– WinEunuuchs2Unix
Dec 31 '18 at 13:28
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%2f1105647%2fblack-screen-beteen-grub-and-login-screen%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
To see what is happening during the 20 to 30 seconds use:
sudo -H gedit /etc/default/grub
Find the line that starts with:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
and change it to:
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth
Leave the rest of the line as is.
Now save the file and exit gedit
Run:
sudo update-grub
Now when you reboot you will see the messages scroll by as the kernel boots up. If it gets stuck on one message for more than a second note it and add it to your question.
For a detailed time break down of your boot use:
systemd-analyze blame
The longest running boot commands are listed first. Use Q to exit the command.
Systemd log messages
After completing above steps this error is revealed during boot up:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Arch Linux references this error here.
Unix & Linux describes LVM setup errors here.
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
I get, failed to Connect lvmetad, gamling back to scanning.
– Allamo Olsson
Dec 31 '18 at 6:35
@AllamoOlsson I've updated my answer with your error message. It appears you installed usingLVMoption which isn't required for the average user. It's designed for partitions spanning multiple disks like a server would use. You can reinstall without LVM option if you have a new installation and nothing to loose.
– WinEunuuchs2Unix
Dec 31 '18 at 13:28
add a comment |
To see what is happening during the 20 to 30 seconds use:
sudo -H gedit /etc/default/grub
Find the line that starts with:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
and change it to:
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth
Leave the rest of the line as is.
Now save the file and exit gedit
Run:
sudo update-grub
Now when you reboot you will see the messages scroll by as the kernel boots up. If it gets stuck on one message for more than a second note it and add it to your question.
For a detailed time break down of your boot use:
systemd-analyze blame
The longest running boot commands are listed first. Use Q to exit the command.
Systemd log messages
After completing above steps this error is revealed during boot up:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Arch Linux references this error here.
Unix & Linux describes LVM setup errors here.
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
I get, failed to Connect lvmetad, gamling back to scanning.
– Allamo Olsson
Dec 31 '18 at 6:35
@AllamoOlsson I've updated my answer with your error message. It appears you installed usingLVMoption which isn't required for the average user. It's designed for partitions spanning multiple disks like a server would use. You can reinstall without LVM option if you have a new installation and nothing to loose.
– WinEunuuchs2Unix
Dec 31 '18 at 13:28
add a comment |
To see what is happening during the 20 to 30 seconds use:
sudo -H gedit /etc/default/grub
Find the line that starts with:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
and change it to:
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth
Leave the rest of the line as is.
Now save the file and exit gedit
Run:
sudo update-grub
Now when you reboot you will see the messages scroll by as the kernel boots up. If it gets stuck on one message for more than a second note it and add it to your question.
For a detailed time break down of your boot use:
systemd-analyze blame
The longest running boot commands are listed first. Use Q to exit the command.
Systemd log messages
After completing above steps this error is revealed during boot up:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Arch Linux references this error here.
Unix & Linux describes LVM setup errors here.
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
To see what is happening during the 20 to 30 seconds use:
sudo -H gedit /etc/default/grub
Find the line that starts with:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
and change it to:
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth
Leave the rest of the line as is.
Now save the file and exit gedit
Run:
sudo update-grub
Now when you reboot you will see the messages scroll by as the kernel boots up. If it gets stuck on one message for more than a second note it and add it to your question.
For a detailed time break down of your boot use:
systemd-analyze blame
The longest running boot commands are listed first. Use Q to exit the command.
Systemd log messages
After completing above steps this error is revealed during boot up:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Arch Linux references this error here.
Unix & Linux describes LVM setup errors here.
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
edited Dec 31 '18 at 13:27
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
answered Dec 30 '18 at 18:14
WinEunuuchs2UnixWinEunuuchs2Unix
45k1082172
45k1082172
I get, failed to Connect lvmetad, gamling back to scanning.
– Allamo Olsson
Dec 31 '18 at 6:35
@AllamoOlsson I've updated my answer with your error message. It appears you installed usingLVMoption which isn't required for the average user. It's designed for partitions spanning multiple disks like a server would use. You can reinstall without LVM option if you have a new installation and nothing to loose.
– WinEunuuchs2Unix
Dec 31 '18 at 13:28
add a comment |
I get, failed to Connect lvmetad, gamling back to scanning.
– Allamo Olsson
Dec 31 '18 at 6:35
@AllamoOlsson I've updated my answer with your error message. It appears you installed usingLVMoption which isn't required for the average user. It's designed for partitions spanning multiple disks like a server would use. You can reinstall without LVM option if you have a new installation and nothing to loose.
– WinEunuuchs2Unix
Dec 31 '18 at 13:28
I get, failed to Connect lvmetad, gamling back to scanning.
– Allamo Olsson
Dec 31 '18 at 6:35
I get, failed to Connect lvmetad, gamling back to scanning.
– Allamo Olsson
Dec 31 '18 at 6:35
@AllamoOlsson I've updated my answer with your error message. It appears you installed using
LVM option which isn't required for the average user. It's designed for partitions spanning multiple disks like a server would use. You can reinstall without LVM option if you have a new installation and nothing to loose.– WinEunuuchs2Unix
Dec 31 '18 at 13:28
@AllamoOlsson I've updated my answer with your error message. It appears you installed using
LVM option which isn't required for the average user. It's designed for partitions spanning multiple disks like a server would use. You can reinstall without LVM option if you have a new installation and nothing to loose.– WinEunuuchs2Unix
Dec 31 '18 at 13:28
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%2f1105647%2fblack-screen-beteen-grub-and-login-screen%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
