Xubuntu automatically boots into initramfs [Firmware Bug]: TSC_DEADLINE disabled due Errata [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
The full error text given is
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due Errata;
please update microcode to version: 0x52 (or later).
What I could find in a similar question is to update my Intel microcode with sudo apt-get install intel-microcode, the problem is that I can't do that within initramfs. I can't find anyway to get inside my system and do this update.
Greatly appreciate any help!
linux initramfs intel xubuntu firmware
edited Apr 12 at 7:38
chaos
33.6k767112
asked Apr 11 at 20:32
Rakota
112
closed as off-topic by Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil Apr 14 at 8:13
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil
add a comment |Â
up vote
-1
down vote
favorite
The full error text given is
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due Errata;
please update microcode to version: 0x52 (or later).
What I could find in a similar question is to update my Intel microcode with sudo apt-get install intel-microcode, the problem is that I can't do that within initramfs. I can't find anyway to get inside my system and do this update.
Greatly appreciate any help!
linux initramfs intel xubuntu firmware
edited Apr 12 at 7:38
chaos
33.6k767112
asked Apr 11 at 20:32
Rakota
112
closed as off-topic by Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil Apr 14 at 8:13
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil
That error shouldn’t prevent you from booting; are there no other errors?
– Stephen Kitt
Apr 11 at 20:59
That's the only error mentioned when I get thrown into initramfs. If I try the command "exit" I do get another error" Gave up waiting for root device. Common problems: ..." And then I also receive the alert" ALERT! UUID=.... does not exist. Dropping to a shell!" And then I am back where I started.
– Rakota
Apr 11 at 21:03
When running "dmesg|grep -I error" I get 2 errors "ACPI Error : thread ... Cannot release mutex [PATM] acquired by thread...". And " ACPI Error : Method parse/execution failed _SB.PCIO.LPCB.ECDV._Q66, AE_AML_NOT_OWNER"
– Rakota
Apr 11 at 22:37
I suspect the real reason you’re dumped to the initramfs prompt is the absent root device. You need to either figure out why that’s happening, or edit your question to include all the messages you’re seeing...
– Stephen Kitt
Apr 12 at 20:12
The error occurred when my BIOS settings were changed during an update, I answered my question to highlight this. Thank you for helping.
– Rakota
Apr 12 at 22:40
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
The full error text given is
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due Errata;
please update microcode to version: 0x52 (or later).
What I could find in a similar question is to update my Intel microcode with sudo apt-get install intel-microcode, the problem is that I can't do that within initramfs. I can't find anyway to get inside my system and do this update.
Greatly appreciate any help!
linux initramfs intel xubuntu firmware
edited Apr 12 at 7:38
chaos
33.6k767112
asked Apr 11 at 20:32
Rakota
112
The full error text given is
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due Errata;
please update microcode to version: 0x52 (or later).
What I could find in a similar question is to update my Intel microcode with sudo apt-get install intel-microcode, the problem is that I can't do that within initramfs. I can't find anyway to get inside my system and do this update.
Greatly appreciate any help!
linux initramfs intel xubuntu firmware
edited Apr 12 at 7:38
chaos
33.6k767112
asked Apr 11 at 20:32
Rakota
112
edited Apr 12 at 7:38
chaos
33.6k767112
edited Apr 12 at 7:38
chaos
33.6k767112
edited Apr 12 at 7:38
chaos
33.6k767112
33.6k767112
asked Apr 11 at 20:32
Rakota
112
asked Apr 11 at 20:32
Rakota
112
asked Apr 11 at 20:32
Rakota
112
112
closed as off-topic by Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil Apr 14 at 8:13
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil
closed as off-topic by Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil Apr 14 at 8:13
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Stephen Kitt, Rui F Ribeiro, Isaac, Jesse_b, Vlastimil
That error shouldn’t prevent you from booting; are there no other errors?
– Stephen Kitt
Apr 11 at 20:59
That's the only error mentioned when I get thrown into initramfs. If I try the command "exit" I do get another error" Gave up waiting for root device. Common problems: ..." And then I also receive the alert" ALERT! UUID=.... does not exist. Dropping to a shell!" And then I am back where I started.
– Rakota
Apr 11 at 21:03
When running "dmesg|grep -I error" I get 2 errors "ACPI Error : thread ... Cannot release mutex [PATM] acquired by thread...". And " ACPI Error : Method parse/execution failed _SB.PCIO.LPCB.ECDV._Q66, AE_AML_NOT_OWNER"
– Rakota
Apr 11 at 22:37
I suspect the real reason you’re dumped to the initramfs prompt is the absent root device. You need to either figure out why that’s happening, or edit your question to include all the messages you’re seeing...
– Stephen Kitt
Apr 12 at 20:12
The error occurred when my BIOS settings were changed during an update, I answered my question to highlight this. Thank you for helping.
– Rakota
Apr 12 at 22:40
add a comment |Â
That error shouldn’t prevent you from booting; are there no other errors?
– Stephen Kitt
Apr 11 at 20:59
That's the only error mentioned when I get thrown into initramfs. If I try the command "exit" I do get another error" Gave up waiting for root device. Common problems: ..." And then I also receive the alert" ALERT! UUID=.... does not exist. Dropping to a shell!" And then I am back where I started.
– Rakota
Apr 11 at 21:03
When running "dmesg|grep -I error" I get 2 errors "ACPI Error : thread ... Cannot release mutex [PATM] acquired by thread...". And " ACPI Error : Method parse/execution failed _SB.PCIO.LPCB.ECDV._Q66, AE_AML_NOT_OWNER"
– Rakota
Apr 11 at 22:37
I suspect the real reason you’re dumped to the initramfs prompt is the absent root device. You need to either figure out why that’s happening, or edit your question to include all the messages you’re seeing...
– Stephen Kitt
Apr 12 at 20:12
The error occurred when my BIOS settings were changed during an update, I answered my question to highlight this. Thank you for helping.
– Rakota
Apr 12 at 22:40
That error shouldn’t prevent you from booting; are there no other errors?
– Stephen Kitt
Apr 11 at 20:59
That error shouldn’t prevent you from booting; are there no other errors?
– Stephen Kitt
Apr 11 at 20:59
That's the only error mentioned when I get thrown into initramfs. If I try the command "exit" I do get another error" Gave up waiting for root device. Common problems: ..." And then I also receive the alert" ALERT! UUID=.... does not exist. Dropping to a shell!" And then I am back where I started.
– Rakota
Apr 11 at 21:03
That's the only error mentioned when I get thrown into initramfs. If I try the command "exit" I do get another error" Gave up waiting for root device. Common problems: ..." And then I also receive the alert" ALERT! UUID=.... does not exist. Dropping to a shell!" And then I am back where I started.
– Rakota
Apr 11 at 21:03
When running "dmesg|grep -I error" I get 2 errors "ACPI Error : thread ... Cannot release mutex [PATM] acquired by thread...". And " ACPI Error : Method parse/execution failed _SB.PCIO.LPCB.ECDV._Q66, AE_AML_NOT_OWNER"
– Rakota
Apr 11 at 22:37
When running "dmesg|grep -I error" I get 2 errors "ACPI Error : thread ... Cannot release mutex [PATM] acquired by thread...". And " ACPI Error : Method parse/execution failed _SB.PCIO.LPCB.ECDV._Q66, AE_AML_NOT_OWNER"
– Rakota
Apr 11 at 22:37
I suspect the real reason you’re dumped to the initramfs prompt is the absent root device. You need to either figure out why that’s happening, or edit your question to include all the messages you’re seeing...
– Stephen Kitt
Apr 12 at 20:12
I suspect the real reason you’re dumped to the initramfs prompt is the absent root device. You need to either figure out why that’s happening, or edit your question to include all the messages you’re seeing...
– Stephen Kitt
Apr 12 at 20:12
The error occurred when my BIOS settings were changed during an update, I answered my question to highlight this. Thank you for helping.
– Rakota
Apr 12 at 22:40
The error occurred when my BIOS settings were changed during an update, I answered my question to highlight this. Thank you for helping.
– Rakota
Apr 12 at 22:40
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
The source of my problem was that the BIOS had updated and in the process reverted my settings back to using RAID, which was causing me this boot error. Going into my BIOS and changing back to the previous settings solved my issue.
answered Apr 12 at 22:39
Rakota
112
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The source of my problem was that the BIOS had updated and in the process reverted my settings back to using RAID, which was causing me this boot error. Going into my BIOS and changing back to the previous settings solved my issue.
answered Apr 12 at 22:39
Rakota
112
add a comment |Â
up vote
1
down vote
The source of my problem was that the BIOS had updated and in the process reverted my settings back to using RAID, which was causing me this boot error. Going into my BIOS and changing back to the previous settings solved my issue.
answered Apr 12 at 22:39
Rakota
112
add a comment |Â
up vote
1
down vote
up vote
1
down vote
The source of my problem was that the BIOS had updated and in the process reverted my settings back to using RAID, which was causing me this boot error. Going into my BIOS and changing back to the previous settings solved my issue.
answered Apr 12 at 22:39
Rakota
112
The source of my problem was that the BIOS had updated and in the process reverted my settings back to using RAID, which was causing me this boot error. Going into my BIOS and changing back to the previous settings solved my issue.
answered Apr 12 at 22:39
Rakota
112
answered Apr 12 at 22:39
Rakota
112
answered Apr 12 at 22:39
Rakota
112
answered Apr 12 at 22:39
Rakota
112
112
add a comment |Â
add a comment |Â
That error shouldn’t prevent you from booting; are there no other errors?
– Stephen Kitt
Apr 11 at 20:59
That's the only error mentioned when I get thrown into initramfs. If I try the command "exit" I do get another error" Gave up waiting for root device. Common problems: ..." And then I also receive the alert" ALERT! UUID=.... does not exist. Dropping to a shell!" And then I am back where I started.
– Rakota
Apr 11 at 21:03
When running "dmesg|grep -I error" I get 2 errors "ACPI Error : thread ... Cannot release mutex [PATM] acquired by thread...". And " ACPI Error : Method parse/execution failed _SB.PCIO.LPCB.ECDV._Q66, AE_AML_NOT_OWNER"
– Rakota
Apr 11 at 22:37
I suspect the real reason you’re dumped to the initramfs prompt is the absent root device. You need to either figure out why that’s happening, or edit your question to include all the messages you’re seeing...
– Stephen Kitt
Apr 12 at 20:12
The error occurred when my BIOS settings were changed during an update, I answered my question to highlight this. Thank you for helping.
– Rakota
Apr 12 at 22:40