Ubuntu getting struck on purple screen
I replaced Windows 7 with Ubuntu 18.04. After finishing installation and restarting system, Ubuntu is getting struck on purple screen and not proceeding further
18.04 system-installation
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
add a comment |
I replaced Windows 7 with Ubuntu 18.04. After finishing installation and restarting system, Ubuntu is getting struck on purple screen and not proceeding further
18.04 system-installation
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
1
Usually when this happens some daemon is failing to start. Try booting and holding SHIFT key, the GRUB interface should pop up. Press "e" key to edit the default entry and remove "quiet splash". In this way during the boot you'll be able to see logs of what's happening and eventually tell us where it hangs.
– Cristian Vrinceanu
Feb 3 at 22:46
add a comment |
I replaced Windows 7 with Ubuntu 18.04. After finishing installation and restarting system, Ubuntu is getting struck on purple screen and not proceeding further
18.04 system-installation
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
I replaced Windows 7 with Ubuntu 18.04. After finishing installation and restarting system, Ubuntu is getting struck on purple screen and not proceeding further
18.04 system-installation
18.04 system-installation
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
asked Feb 3 at 18:19
Gaurav JainGaurav Jain
1
1
1
Usually when this happens some daemon is failing to start. Try booting and holding SHIFT key, the GRUB interface should pop up. Press "e" key to edit the default entry and remove "quiet splash". In this way during the boot you'll be able to see logs of what's happening and eventually tell us where it hangs.
– Cristian Vrinceanu
Feb 3 at 22:46
add a comment |
1
Usually when this happens some daemon is failing to start. Try booting and holding SHIFT key, the GRUB interface should pop up. Press "e" key to edit the default entry and remove "quiet splash". In this way during the boot you'll be able to see logs of what's happening and eventually tell us where it hangs.
– Cristian Vrinceanu
Feb 3 at 22:46
1
1
Usually when this happens some daemon is failing to start. Try booting and holding SHIFT key, the GRUB interface should pop up. Press "e" key to edit the default entry and remove "quiet splash". In this way during the boot you'll be able to see logs of what's happening and eventually tell us where it hangs.
– Cristian Vrinceanu
Feb 3 at 22:46
Usually when this happens some daemon is failing to start. Try booting and holding SHIFT key, the GRUB interface should pop up. Press "e" key to edit the default entry and remove "quiet splash". In this way during the boot you'll be able to see logs of what's happening and eventually tell us where it hangs.
– Cristian Vrinceanu
Feb 3 at 22:46
add a comment |
2 Answers
2
active
oldest
votes
I, unfortunately, do not have enough reputation to comment, so I am saying this in an answer. Have you tried pressing one of the "function" keys? (f1, f2, f3, etc.) This should bring up the boot output. you can then see if there is anything there to identify the problem.
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
add a comment |
IIRC Windows 7 came out while systems still used legacy bios. As such there may be problems if the installer is confused about how to install the boot loader.
My laptop is uefi capable but has windows 7 installed (upgraded to windows 10) and thus an MBR config on the drive. Ubuntu was installed legacy bios mode to support dual booting and keep windows available.
The earlier suggestion about going into the bios and looking may give you a clue. Ubuntu can boot on either, but some of the bios settings may leave the os to determine which mode ( UEFI or BIOS ) to use for booting and I have seen systems hang unless the setting within the bios actually provided a fixed boot mode setting. If the os boot loader is not installed properly (uefi requires an efi partition, legacy bios does not. Also the boot sector is sized differently.) it will hang when it hits the error.
In my experience the installer is not confused if there is already an os on the drive as it can see the boot mode. With no os to look it may try to install in uefi mode while the drive is partitioned as MBR mode. This could cause the hang.
I have had it happen, and changing the bios setting fixed it for me.
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
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%2f1115326%2fubuntu-getting-struck-on-purple-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I, unfortunately, do not have enough reputation to comment, so I am saying this in an answer. Have you tried pressing one of the "function" keys? (f1, f2, f3, etc.) This should bring up the boot output. you can then see if there is anything there to identify the problem.
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
add a comment |
I, unfortunately, do not have enough reputation to comment, so I am saying this in an answer. Have you tried pressing one of the "function" keys? (f1, f2, f3, etc.) This should bring up the boot output. you can then see if there is anything there to identify the problem.
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
add a comment |
I, unfortunately, do not have enough reputation to comment, so I am saying this in an answer. Have you tried pressing one of the "function" keys? (f1, f2, f3, etc.) This should bring up the boot output. you can then see if there is anything there to identify the problem.
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
I, unfortunately, do not have enough reputation to comment, so I am saying this in an answer. Have you tried pressing one of the "function" keys? (f1, f2, f3, etc.) This should bring up the boot output. you can then see if there is anything there to identify the problem.
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
answered Feb 3 at 20:17
yam-magnateyam-magnate
11
11
add a comment |
add a comment |
IIRC Windows 7 came out while systems still used legacy bios. As such there may be problems if the installer is confused about how to install the boot loader.
My laptop is uefi capable but has windows 7 installed (upgraded to windows 10) and thus an MBR config on the drive. Ubuntu was installed legacy bios mode to support dual booting and keep windows available.
The earlier suggestion about going into the bios and looking may give you a clue. Ubuntu can boot on either, but some of the bios settings may leave the os to determine which mode ( UEFI or BIOS ) to use for booting and I have seen systems hang unless the setting within the bios actually provided a fixed boot mode setting. If the os boot loader is not installed properly (uefi requires an efi partition, legacy bios does not. Also the boot sector is sized differently.) it will hang when it hits the error.
In my experience the installer is not confused if there is already an os on the drive as it can see the boot mode. With no os to look it may try to install in uefi mode while the drive is partitioned as MBR mode. This could cause the hang.
I have had it happen, and changing the bios setting fixed it for me.
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
add a comment |
IIRC Windows 7 came out while systems still used legacy bios. As such there may be problems if the installer is confused about how to install the boot loader.
My laptop is uefi capable but has windows 7 installed (upgraded to windows 10) and thus an MBR config on the drive. Ubuntu was installed legacy bios mode to support dual booting and keep windows available.
The earlier suggestion about going into the bios and looking may give you a clue. Ubuntu can boot on either, but some of the bios settings may leave the os to determine which mode ( UEFI or BIOS ) to use for booting and I have seen systems hang unless the setting within the bios actually provided a fixed boot mode setting. If the os boot loader is not installed properly (uefi requires an efi partition, legacy bios does not. Also the boot sector is sized differently.) it will hang when it hits the error.
In my experience the installer is not confused if there is already an os on the drive as it can see the boot mode. With no os to look it may try to install in uefi mode while the drive is partitioned as MBR mode. This could cause the hang.
I have had it happen, and changing the bios setting fixed it for me.
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
add a comment |
IIRC Windows 7 came out while systems still used legacy bios. As such there may be problems if the installer is confused about how to install the boot loader.
My laptop is uefi capable but has windows 7 installed (upgraded to windows 10) and thus an MBR config on the drive. Ubuntu was installed legacy bios mode to support dual booting and keep windows available.
The earlier suggestion about going into the bios and looking may give you a clue. Ubuntu can boot on either, but some of the bios settings may leave the os to determine which mode ( UEFI or BIOS ) to use for booting and I have seen systems hang unless the setting within the bios actually provided a fixed boot mode setting. If the os boot loader is not installed properly (uefi requires an efi partition, legacy bios does not. Also the boot sector is sized differently.) it will hang when it hits the error.
In my experience the installer is not confused if there is already an os on the drive as it can see the boot mode. With no os to look it may try to install in uefi mode while the drive is partitioned as MBR mode. This could cause the hang.
I have had it happen, and changing the bios setting fixed it for me.
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
IIRC Windows 7 came out while systems still used legacy bios. As such there may be problems if the installer is confused about how to install the boot loader.
My laptop is uefi capable but has windows 7 installed (upgraded to windows 10) and thus an MBR config on the drive. Ubuntu was installed legacy bios mode to support dual booting and keep windows available.
The earlier suggestion about going into the bios and looking may give you a clue. Ubuntu can boot on either, but some of the bios settings may leave the os to determine which mode ( UEFI or BIOS ) to use for booting and I have seen systems hang unless the setting within the bios actually provided a fixed boot mode setting. If the os boot loader is not installed properly (uefi requires an efi partition, legacy bios does not. Also the boot sector is sized differently.) it will hang when it hits the error.
In my experience the installer is not confused if there is already an os on the drive as it can see the boot mode. With no os to look it may try to install in uefi mode while the drive is partitioned as MBR mode. This could cause the hang.
I have had it happen, and changing the bios setting fixed it for me.
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
answered Feb 4 at 0:48
Computer SavvyComputer Savvy
263
263
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%2f1115326%2fubuntu-getting-struck-on-purple-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
1
Usually when this happens some daemon is failing to start. Try booting and holding SHIFT key, the GRUB interface should pop up. Press "e" key to edit the default entry and remove "quiet splash". In this way during the boot you'll be able to see logs of what's happening and eventually tell us where it hangs.
– Cristian Vrinceanu
Feb 3 at 22:46