Linux Throws Error: Can't read CTR while intializing i8042?
my install of linux throws the following errors upon boot:
efi: requested map not found. esrt: ESRT header is not in the memory map. i0842: Can't read CTR while initializing i8042.
Would these errors be indicative factors of disk corruption? Thanks!
boot encryption
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
add a comment |
my install of linux throws the following errors upon boot:
efi: requested map not found. esrt: ESRT header is not in the memory map. i0842: Can't read CTR while initializing i8042.
Would these errors be indicative factors of disk corruption? Thanks!
boot encryption
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
efi relates to (U)EFI vs. legacy BIOS boot. ESRT is probably some ACPI area. i8042 is the PS/2 keyboard/mouse controller. None of this points to disk corruption, unless your kernel image is corrupted. But it looks more like it's a UEFI boot problem.
– dirkt
Jul 20 '17 at 21:55
add a comment |
my install of linux throws the following errors upon boot:
efi: requested map not found. esrt: ESRT header is not in the memory map. i0842: Can't read CTR while initializing i8042.
Would these errors be indicative factors of disk corruption? Thanks!
boot encryption
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
my install of linux throws the following errors upon boot:
efi: requested map not found. esrt: ESRT header is not in the memory map. i0842: Can't read CTR while initializing i8042.
Would these errors be indicative factors of disk corruption? Thanks!
boot encryption
boot encryption
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
asked Jul 20 '17 at 21:17
Joe DoeJoe Doe
612
612
efi relates to (U)EFI vs. legacy BIOS boot. ESRT is probably some ACPI area. i8042 is the PS/2 keyboard/mouse controller. None of this points to disk corruption, unless your kernel image is corrupted. But it looks more like it's a UEFI boot problem.
– dirkt
Jul 20 '17 at 21:55
add a comment |
efi relates to (U)EFI vs. legacy BIOS boot. ESRT is probably some ACPI area. i8042 is the PS/2 keyboard/mouse controller. None of this points to disk corruption, unless your kernel image is corrupted. But it looks more like it's a UEFI boot problem.
– dirkt
Jul 20 '17 at 21:55
efi relates to (U)EFI vs. legacy BIOS boot. ESRT is probably some ACPI area. i8042 is the PS/2 keyboard/mouse controller. None of this points to disk corruption, unless your kernel image is corrupted. But it looks more like it's a UEFI boot problem.
– dirkt
Jul 20 '17 at 21:55
efi relates to (U)EFI vs. legacy BIOS boot. ESRT is probably some ACPI area. i8042 is the PS/2 keyboard/mouse controller. None of this points to disk corruption, unless your kernel image is corrupted. But it looks more like it's a UEFI boot problem.
– dirkt
Jul 20 '17 at 21:55
add a comment |
2 Answers
2
active
oldest
votes
Your modern motherboard has no i8042 controller chip, but the most of board has (green, purple, round) PS/2 keyboard, mouse port for legacy BIOS compatibility.
Usually, the (U)EFI/BIOS controls keyboard and mouse via USB as HID device default.
But, very old hardware and OS detect i8042 controller and search keyboard and mouse on boot, and display the error above.
The error is no relation with hard disks, and can be ignored unless you cannot use the keyboard and mouse.
answered Jul 21 '17 at 5:09
minishminish
21615
add a comment |
I had a similar error message. In my case, the keyboard and the trackstick/touchpad didn't work. (Thinkpad W541, Opensuse 15.0, Kernel 4.12.14).
I fixed it by removing the kernel opts acpi=off and apm=off in the grub-setup.
answered 3 mins ago
wvrnwvrn
1
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f379834%2flinux-throws-error-cant-read-ctr-while-intializing-i8042%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
Your modern motherboard has no i8042 controller chip, but the most of board has (green, purple, round) PS/2 keyboard, mouse port for legacy BIOS compatibility.
Usually, the (U)EFI/BIOS controls keyboard and mouse via USB as HID device default.
But, very old hardware and OS detect i8042 controller and search keyboard and mouse on boot, and display the error above.
The error is no relation with hard disks, and can be ignored unless you cannot use the keyboard and mouse.
answered Jul 21 '17 at 5:09
minishminish
21615
add a comment |
Your modern motherboard has no i8042 controller chip, but the most of board has (green, purple, round) PS/2 keyboard, mouse port for legacy BIOS compatibility.
Usually, the (U)EFI/BIOS controls keyboard and mouse via USB as HID device default.
But, very old hardware and OS detect i8042 controller and search keyboard and mouse on boot, and display the error above.
The error is no relation with hard disks, and can be ignored unless you cannot use the keyboard and mouse.
answered Jul 21 '17 at 5:09
minishminish
21615
add a comment |
Your modern motherboard has no i8042 controller chip, but the most of board has (green, purple, round) PS/2 keyboard, mouse port for legacy BIOS compatibility.
Usually, the (U)EFI/BIOS controls keyboard and mouse via USB as HID device default.
But, very old hardware and OS detect i8042 controller and search keyboard and mouse on boot, and display the error above.
The error is no relation with hard disks, and can be ignored unless you cannot use the keyboard and mouse.
answered Jul 21 '17 at 5:09
minishminish
21615
Your modern motherboard has no i8042 controller chip, but the most of board has (green, purple, round) PS/2 keyboard, mouse port for legacy BIOS compatibility.
Usually, the (U)EFI/BIOS controls keyboard and mouse via USB as HID device default.
But, very old hardware and OS detect i8042 controller and search keyboard and mouse on boot, and display the error above.
The error is no relation with hard disks, and can be ignored unless you cannot use the keyboard and mouse.
answered Jul 21 '17 at 5:09
minishminish
21615
answered Jul 21 '17 at 5:09
minishminish
21615
answered Jul 21 '17 at 5:09
minishminish
21615
answered Jul 21 '17 at 5:09
minishminish
21615
21615
add a comment |
add a comment |
I had a similar error message. In my case, the keyboard and the trackstick/touchpad didn't work. (Thinkpad W541, Opensuse 15.0, Kernel 4.12.14).
I fixed it by removing the kernel opts acpi=off and apm=off in the grub-setup.
answered 3 mins ago
wvrnwvrn
1
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I had a similar error message. In my case, the keyboard and the trackstick/touchpad didn't work. (Thinkpad W541, Opensuse 15.0, Kernel 4.12.14).
I fixed it by removing the kernel opts acpi=off and apm=off in the grub-setup.
answered 3 mins ago
wvrnwvrn
1
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I had a similar error message. In my case, the keyboard and the trackstick/touchpad didn't work. (Thinkpad W541, Opensuse 15.0, Kernel 4.12.14).
I fixed it by removing the kernel opts acpi=off and apm=off in the grub-setup.
answered 3 mins ago
wvrnwvrn
1
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had a similar error message. In my case, the keyboard and the trackstick/touchpad didn't work. (Thinkpad W541, Opensuse 15.0, Kernel 4.12.14).
I fixed it by removing the kernel opts acpi=off and apm=off in the grub-setup.
answered 3 mins ago
wvrnwvrn
1
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 3 mins ago
wvrnwvrn
1
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 3 mins ago
wvrnwvrn
1
answered 3 mins ago
wvrnwvrn
1
1
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
wvrn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f379834%2flinux-throws-error-cant-read-ctr-while-intializing-i8042%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
efi relates to (U)EFI vs. legacy BIOS boot. ESRT is probably some ACPI area. i8042 is the PS/2 keyboard/mouse controller. None of this points to disk corruption, unless your kernel image is corrupted. But it looks more like it's a UEFI boot problem.
– dirkt
Jul 20 '17 at 21:55