▲ 9 ▼ New on mint. My pc started up in this screen isntead of the login screen. What shoul I do ? (thelemmy.club) submitted 3 months ago* (last edited 2 months ago) by Homo_Erectus@lemmy.zip to c/linuxmint@lemmy.ml 15 comments fedilink hide all child comments Edit: Thanks everyone that tried to help. I will reinstall the OS, sinse the problemm looks a bit more complex then I initially thought 🥲
[–] Adverse_Reaction@anarchist.nexus 2 points 3 months ago (3 children) What is the output of this command: sudo dmesg -l err permalink fedilink source parent hideshow 3 child comments replies: [–] apftwb@lemmy.world 3 points 3 months ago* (last edited 3 months ago) OP, FYI You can still get to terminal by changing you tty session permalink fedilink source parent [–] Homo_Erectus@lemmy.zip [S] 1 point 3 months ago* (1 child) ACPI ERROR ACPI BIOS ERROR Also; sry for the late permalink fedilink source parent hideshow 1 child comment replies: [–] Adverse_Reaction@anarchist.nexus 2 points 3 months ago* ACPI errors are typically not important. Are you sure there are no other errors above or below your screenshot? FWIW, you can use the following command to see what BIOS version you currently have, then check with the manufacturer to see what version is most up-to-date and install that. It may quiet down your dmesg/log output if nothing else. Be warned, there is a certain risk to updating the BIOS. Things can go wrong or even create new problems, but in general it is advisable to keep the BIOS up-to-date. The command to determine what BIOS version you have installed is: sudo dmidecode -s bios-version Also, you should try to boot with nothing unnecessary connected to the PC, to see if it behaves differently. A poorly initialized hardware device can cause any number of strange behavior. USB/Bluetooth devices are easily overlooked/forgotten/ignored as inconsequential, but can hang a system up. Also check the cable connections if it's a desktop PC. On top of all that I would run fsck on your drive to make sure you aren't dealing with file corruption of some kind. This can be done during boot via the recovery console. Reboot and hold the Shift key during boot. This will get you to the GRUB menu, even if it is not normally shown. Select “Advanced options” Select “Recovery mode” for the kernel version you are normally using. In the recovery menu, select “fsck“ When prompted to remount the root filesystem, select “Yes“ When fsck completes, “Resume” will continue the boot process normally. I hope this helps. If not, you may want to consider restoring from backup, assuming you have made a working backup via Timeshift or similar. Barring that, you either need to dig much deeper into the logs and boot process, or simply reinstall the OS. Testing the hardware by booting a live USB session is also advisable - that can be done via the same USB image you probably used to install the OS to begin with. If the problem persists, then you know something has gone wrong with a hardware component. Good luck, and keep us posted on your outcome. permalink fedilink source parent
[–] apftwb@lemmy.world 3 points 3 months ago* (last edited 3 months ago) OP, FYI You can still get to terminal by changing you tty session permalink fedilink source parent
[–] Homo_Erectus@lemmy.zip [S] 1 point 3 months ago* (1 child) ACPI ERROR ACPI BIOS ERROR Also; sry for the late permalink fedilink source parent hideshow 1 child comment replies: [–] Adverse_Reaction@anarchist.nexus 2 points 3 months ago* ACPI errors are typically not important. Are you sure there are no other errors above or below your screenshot? FWIW, you can use the following command to see what BIOS version you currently have, then check with the manufacturer to see what version is most up-to-date and install that. It may quiet down your dmesg/log output if nothing else. Be warned, there is a certain risk to updating the BIOS. Things can go wrong or even create new problems, but in general it is advisable to keep the BIOS up-to-date. The command to determine what BIOS version you have installed is: sudo dmidecode -s bios-version Also, you should try to boot with nothing unnecessary connected to the PC, to see if it behaves differently. A poorly initialized hardware device can cause any number of strange behavior. USB/Bluetooth devices are easily overlooked/forgotten/ignored as inconsequential, but can hang a system up. Also check the cable connections if it's a desktop PC. On top of all that I would run fsck on your drive to make sure you aren't dealing with file corruption of some kind. This can be done during boot via the recovery console. Reboot and hold the Shift key during boot. This will get you to the GRUB menu, even if it is not normally shown. Select “Advanced options” Select “Recovery mode” for the kernel version you are normally using. In the recovery menu, select “fsck“ When prompted to remount the root filesystem, select “Yes“ When fsck completes, “Resume” will continue the boot process normally. I hope this helps. If not, you may want to consider restoring from backup, assuming you have made a working backup via Timeshift or similar. Barring that, you either need to dig much deeper into the logs and boot process, or simply reinstall the OS. Testing the hardware by booting a live USB session is also advisable - that can be done via the same USB image you probably used to install the OS to begin with. If the problem persists, then you know something has gone wrong with a hardware component. Good luck, and keep us posted on your outcome. permalink fedilink source parent
[–] Adverse_Reaction@anarchist.nexus 2 points 3 months ago* ACPI errors are typically not important. Are you sure there are no other errors above or below your screenshot? FWIW, you can use the following command to see what BIOS version you currently have, then check with the manufacturer to see what version is most up-to-date and install that. It may quiet down your dmesg/log output if nothing else. Be warned, there is a certain risk to updating the BIOS. Things can go wrong or even create new problems, but in general it is advisable to keep the BIOS up-to-date. The command to determine what BIOS version you have installed is: sudo dmidecode -s bios-version Also, you should try to boot with nothing unnecessary connected to the PC, to see if it behaves differently. A poorly initialized hardware device can cause any number of strange behavior. USB/Bluetooth devices are easily overlooked/forgotten/ignored as inconsequential, but can hang a system up. Also check the cable connections if it's a desktop PC. On top of all that I would run fsck on your drive to make sure you aren't dealing with file corruption of some kind. This can be done during boot via the recovery console. Reboot and hold the Shift key during boot. This will get you to the GRUB menu, even if it is not normally shown. Select “Advanced options” Select “Recovery mode” for the kernel version you are normally using. In the recovery menu, select “fsck“ When prompted to remount the root filesystem, select “Yes“ When fsck completes, “Resume” will continue the boot process normally. I hope this helps. If not, you may want to consider restoring from backup, assuming you have made a working backup via Timeshift or similar. Barring that, you either need to dig much deeper into the logs and boot process, or simply reinstall the OS. Testing the hardware by booting a live USB session is also advisable - that can be done via the same USB image you probably used to install the OS to begin with. If the problem persists, then you know something has gone wrong with a hardware component. Good luck, and keep us posted on your outcome. permalink fedilink source parent
