My Linux install bricked itself (ACPI, Couldn't get size: 0x800000000000000e and PKCS#7)
up vote
0
down vote
favorite
I woke up today, pressed power button and got this screen.
I did some research and uninstalled nvidia drivers, which caused pkcs errors to go away. More research, and enabling secure boot caused uefi thing to go away. So it looks like this now.
I have no clue what's going on, I just migrated to Linux from Windows a week ago and I am upset it bricked itself.
I can type startx and go to desktop as root but internet does not work and I don't really know what to do. (startx would not boot to desktop before I removed nvidia drivers which was version 390 by the way).
I am using kubuntu 18.04.1.
Some help would be nice.
(specs: Asus z170i pro gaming, i5-6400, evga gtx 1060)
nvidia uefi acpi
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
asked Dec 6 at 17:58
Kyuunex
236
add a comment |
up vote
0
down vote
favorite
I woke up today, pressed power button and got this screen.
I did some research and uninstalled nvidia drivers, which caused pkcs errors to go away. More research, and enabling secure boot caused uefi thing to go away. So it looks like this now.
I have no clue what's going on, I just migrated to Linux from Windows a week ago and I am upset it bricked itself.
I can type startx and go to desktop as root but internet does not work and I don't really know what to do. (startx would not boot to desktop before I removed nvidia drivers which was version 390 by the way).
I am using kubuntu 18.04.1.
Some help would be nice.
(specs: Asus z170i pro gaming, i5-6400, evga gtx 1060)
nvidia uefi acpi
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
asked Dec 6 at 17:58
Kyuunex
236
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I woke up today, pressed power button and got this screen.
I did some research and uninstalled nvidia drivers, which caused pkcs errors to go away. More research, and enabling secure boot caused uefi thing to go away. So it looks like this now.
I have no clue what's going on, I just migrated to Linux from Windows a week ago and I am upset it bricked itself.
I can type startx and go to desktop as root but internet does not work and I don't really know what to do. (startx would not boot to desktop before I removed nvidia drivers which was version 390 by the way).
I am using kubuntu 18.04.1.
Some help would be nice.
(specs: Asus z170i pro gaming, i5-6400, evga gtx 1060)
nvidia uefi acpi
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
asked Dec 6 at 17:58
Kyuunex
236
I woke up today, pressed power button and got this screen.
I did some research and uninstalled nvidia drivers, which caused pkcs errors to go away. More research, and enabling secure boot caused uefi thing to go away. So it looks like this now.
I have no clue what's going on, I just migrated to Linux from Windows a week ago and I am upset it bricked itself.
I can type startx and go to desktop as root but internet does not work and I don't really know what to do. (startx would not boot to desktop before I removed nvidia drivers which was version 390 by the way).
I am using kubuntu 18.04.1.
Some help would be nice.
(specs: Asus z170i pro gaming, i5-6400, evga gtx 1060)
nvidia uefi acpi
nvidia uefi acpi
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
asked Dec 6 at 17:58
Kyuunex
236
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
asked Dec 6 at 17:58
Kyuunex
236
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
edited Dec 6 at 18:38
SurvivalMachine
1,1923717
1,1923717
asked Dec 6 at 17:58
Kyuunex
236
asked Dec 6 at 17:58
Kyuunex
236
asked Dec 6 at 17:58
Kyuunex
236
236
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
From what I can glean, the kernel is finding a known bug, since it cites the errata and asks you to modify microcode with a newer version.
I would need to know more from kernel and about your hardware and software configs.
What device is that? Sound card? Power interface, I had some problems a while ago with my Lenovo.
This might relate: Ubuntu 17.10 [Firmware Bug]: TSC_DEADLINE
Consensus looks to indicate you need to load new microcode:
https://wiki.archlinux.org/index.php/microcode
I see, this looks akin to your issue:
ACPI Errors - Ubuntu 16.04/17.04 can not be installed
Looks like you can get grub to hang in there longer and allow more ACPI errors and still boot.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_rev_override=5"
Is this an answer?
– George Udosen
Dec 6 at 18:06
You tell me. Was there a question in it?
– user900446
Dec 6 at 18:08
i remember removingintel-microcodepackage because it caused a problem with something else but that was a week ago and it worked fine for a week. maybe an update that depended on it got installed and it bricked it self.
– Kyuunex
Dec 6 at 18:09
Sounds right. Thanks for that askubuntu.com/users/464666/kyuunex
– user900446
Dec 6 at 18:09
installingiucode-toolandintel-microcodemade that firmware bug message disappear but other messages are still there.
– Kyuunex
Dec 6 at 18:24
|
show 6 more comments
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',
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%2f1098986%2fmy-linux-install-bricked-itself-acpi-couldnt-get-size-0x800000000000000e-and%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
up vote
2
down vote
accepted
From what I can glean, the kernel is finding a known bug, since it cites the errata and asks you to modify microcode with a newer version.
I would need to know more from kernel and about your hardware and software configs.
What device is that? Sound card? Power interface, I had some problems a while ago with my Lenovo.
This might relate: Ubuntu 17.10 [Firmware Bug]: TSC_DEADLINE
Consensus looks to indicate you need to load new microcode:
https://wiki.archlinux.org/index.php/microcode
I see, this looks akin to your issue:
ACPI Errors - Ubuntu 16.04/17.04 can not be installed
Looks like you can get grub to hang in there longer and allow more ACPI errors and still boot.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_rev_override=5"
Is this an answer?
– George Udosen
Dec 6 at 18:06
You tell me. Was there a question in it?
– user900446
Dec 6 at 18:08
i remember removingintel-microcodepackage because it caused a problem with something else but that was a week ago and it worked fine for a week. maybe an update that depended on it got installed and it bricked it self.
– Kyuunex
Dec 6 at 18:09
Sounds right. Thanks for that askubuntu.com/users/464666/kyuunex
– user900446
Dec 6 at 18:09
installingiucode-toolandintel-microcodemade that firmware bug message disappear but other messages are still there.
– Kyuunex
Dec 6 at 18:24
|
show 6 more comments
up vote
2
down vote
accepted
From what I can glean, the kernel is finding a known bug, since it cites the errata and asks you to modify microcode with a newer version.
I would need to know more from kernel and about your hardware and software configs.
What device is that? Sound card? Power interface, I had some problems a while ago with my Lenovo.
This might relate: Ubuntu 17.10 [Firmware Bug]: TSC_DEADLINE
Consensus looks to indicate you need to load new microcode:
https://wiki.archlinux.org/index.php/microcode
I see, this looks akin to your issue:
ACPI Errors - Ubuntu 16.04/17.04 can not be installed
Looks like you can get grub to hang in there longer and allow more ACPI errors and still boot.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_rev_override=5"
Is this an answer?
– George Udosen
Dec 6 at 18:06
You tell me. Was there a question in it?
– user900446
Dec 6 at 18:08
i remember removingintel-microcodepackage because it caused a problem with something else but that was a week ago and it worked fine for a week. maybe an update that depended on it got installed and it bricked it self.
– Kyuunex
Dec 6 at 18:09
Sounds right. Thanks for that askubuntu.com/users/464666/kyuunex
– user900446
Dec 6 at 18:09
installingiucode-toolandintel-microcodemade that firmware bug message disappear but other messages are still there.
– Kyuunex
Dec 6 at 18:24
|
show 6 more comments
up vote
2
down vote
accepted
up vote
2
down vote
accepted
From what I can glean, the kernel is finding a known bug, since it cites the errata and asks you to modify microcode with a newer version.
I would need to know more from kernel and about your hardware and software configs.
What device is that? Sound card? Power interface, I had some problems a while ago with my Lenovo.
This might relate: Ubuntu 17.10 [Firmware Bug]: TSC_DEADLINE
Consensus looks to indicate you need to load new microcode:
https://wiki.archlinux.org/index.php/microcode
I see, this looks akin to your issue:
ACPI Errors - Ubuntu 16.04/17.04 can not be installed
Looks like you can get grub to hang in there longer and allow more ACPI errors and still boot.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_rev_override=5"
From what I can glean, the kernel is finding a known bug, since it cites the errata and asks you to modify microcode with a newer version.
I would need to know more from kernel and about your hardware and software configs.
What device is that? Sound card? Power interface, I had some problems a while ago with my Lenovo.
This might relate: Ubuntu 17.10 [Firmware Bug]: TSC_DEADLINE
Consensus looks to indicate you need to load new microcode:
https://wiki.archlinux.org/index.php/microcode
I see, this looks akin to your issue:
ACPI Errors - Ubuntu 16.04/17.04 can not be installed
Looks like you can get grub to hang in there longer and allow more ACPI errors and still boot.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_rev_override=5"
edited Dec 6 at 23:38
answered Dec 6 at 18:03
user900446
Is this an answer?
– George Udosen
Dec 6 at 18:06
You tell me. Was there a question in it?
– user900446
Dec 6 at 18:08
i remember removingintel-microcodepackage because it caused a problem with something else but that was a week ago and it worked fine for a week. maybe an update that depended on it got installed and it bricked it self.
– Kyuunex
Dec 6 at 18:09
Sounds right. Thanks for that askubuntu.com/users/464666/kyuunex
– user900446
Dec 6 at 18:09
installingiucode-toolandintel-microcodemade that firmware bug message disappear but other messages are still there.
– Kyuunex
Dec 6 at 18:24
|
show 6 more comments
Is this an answer?
– George Udosen
Dec 6 at 18:06
You tell me. Was there a question in it?
– user900446
Dec 6 at 18:08
i remember removingintel-microcodepackage because it caused a problem with something else but that was a week ago and it worked fine for a week. maybe an update that depended on it got installed and it bricked it self.
– Kyuunex
Dec 6 at 18:09
Sounds right. Thanks for that askubuntu.com/users/464666/kyuunex
– user900446
Dec 6 at 18:09
installingiucode-toolandintel-microcodemade that firmware bug message disappear but other messages are still there.
– Kyuunex
Dec 6 at 18:24
Is this an answer?
– George Udosen
Dec 6 at 18:06
Is this an answer?
– George Udosen
Dec 6 at 18:06
You tell me. Was there a question in it?
– user900446
Dec 6 at 18:08
You tell me. Was there a question in it?
– user900446
Dec 6 at 18:08
i remember removing
intel-microcode package because it caused a problem with something else but that was a week ago and it worked fine for a week. maybe an update that depended on it got installed and it bricked it self.– Kyuunex
Dec 6 at 18:09
i remember removing
intel-microcode package because it caused a problem with something else but that was a week ago and it worked fine for a week. maybe an update that depended on it got installed and it bricked it self.– Kyuunex
Dec 6 at 18:09
Sounds right. Thanks for that askubuntu.com/users/464666/kyuunex
– user900446
Dec 6 at 18:09
Sounds right. Thanks for that askubuntu.com/users/464666/kyuunex
– user900446
Dec 6 at 18:09
installing
iucode-tool and intel-microcode made that firmware bug message disappear but other messages are still there.– Kyuunex
Dec 6 at 18:24
installing
iucode-tool and intel-microcode made that firmware bug message disappear but other messages are still there.– Kyuunex
Dec 6 at 18:24
|
show 6 more comments
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1098986%2fmy-linux-install-bricked-itself-acpi-couldnt-get-size-0x800000000000000e-and%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
