Not able to boot to arch because of acpi bios error [closed]
As the topic says I am not been able to boot to my arch. It shows some acpi bios error. I am attaching the image of it.
It may happen due to xf86-input-mtrack I installed from AUR package. After that I followed this tutorial "https://howchoo.com/g/mdy0ngziogm/the-perfect-almost-touchpad-settings-on-linux-2" from second point. And then I used this command in terminal
sudo systemd restart gdm.service
, as much as I can remember. After that screen flashes for long time , so I force shut down my laptop. From then it is giving this problem.
Though it used to show these ACPI errors before, but I was able to boot into the OS.
linux arch-linux acpi bios
closed as unclear what you're asking by jasonwryan, Jeff Schaller, DarkHeart, Mr Shunz, schily Dec 17 at 16:12
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
As the topic says I am not been able to boot to my arch. It shows some acpi bios error. I am attaching the image of it.
It may happen due to xf86-input-mtrack I installed from AUR package. After that I followed this tutorial "https://howchoo.com/g/mdy0ngziogm/the-perfect-almost-touchpad-settings-on-linux-2" from second point. And then I used this command in terminal
sudo systemd restart gdm.service
, as much as I can remember. After that screen flashes for long time , so I force shut down my laptop. From then it is giving this problem.
Though it used to show these ACPI errors before, but I was able to boot into the OS.
linux arch-linux acpi bios
closed as unclear what you're asking by jasonwryan, Jeff Schaller, DarkHeart, Mr Shunz, schily Dec 17 at 16:12
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
If you are sure its from xf86-input-mtrack , Boot from a Arch Live, chroot and undo what ever you have done, and reboot.
– Severus Tux
Oct 11 '17 at 1:56
add a comment |
As the topic says I am not been able to boot to my arch. It shows some acpi bios error. I am attaching the image of it.
It may happen due to xf86-input-mtrack I installed from AUR package. After that I followed this tutorial "https://howchoo.com/g/mdy0ngziogm/the-perfect-almost-touchpad-settings-on-linux-2" from second point. And then I used this command in terminal
sudo systemd restart gdm.service
, as much as I can remember. After that screen flashes for long time , so I force shut down my laptop. From then it is giving this problem.
Though it used to show these ACPI errors before, but I was able to boot into the OS.
linux arch-linux acpi bios
As the topic says I am not been able to boot to my arch. It shows some acpi bios error. I am attaching the image of it.
It may happen due to xf86-input-mtrack I installed from AUR package. After that I followed this tutorial "https://howchoo.com/g/mdy0ngziogm/the-perfect-almost-touchpad-settings-on-linux-2" from second point. And then I used this command in terminal
sudo systemd restart gdm.service
, as much as I can remember. After that screen flashes for long time , so I force shut down my laptop. From then it is giving this problem.
Though it used to show these ACPI errors before, but I was able to boot into the OS.
linux arch-linux acpi bios
linux arch-linux acpi bios
edited Dec 16 at 22:05
Rui F Ribeiro
38.9k1479129
38.9k1479129
asked Oct 6 '17 at 16:27
Piyush Bansal
212
212
closed as unclear what you're asking by jasonwryan, Jeff Schaller, DarkHeart, Mr Shunz, schily Dec 17 at 16:12
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by jasonwryan, Jeff Schaller, DarkHeart, Mr Shunz, schily Dec 17 at 16:12
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
If you are sure its from xf86-input-mtrack , Boot from a Arch Live, chroot and undo what ever you have done, and reboot.
– Severus Tux
Oct 11 '17 at 1:56
add a comment |
If you are sure its from xf86-input-mtrack , Boot from a Arch Live, chroot and undo what ever you have done, and reboot.
– Severus Tux
Oct 11 '17 at 1:56
If you are sure its from xf86-input-mtrack , Boot from a Arch Live, chroot and undo what ever you have done, and reboot.
– Severus Tux
Oct 11 '17 at 1:56
If you are sure its from xf86-input-mtrack , Boot from a Arch Live, chroot and undo what ever you have done, and reboot.
– Severus Tux
Oct 11 '17 at 1:56
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you are sure its from xf86-input-mtrack , Boot from a Arch Live, chroot and undo what ever you have done, and reboot.
– Severus Tux
Oct 11 '17 at 1:56