Edit: Thanks everyone thar tried to help. I will install the OS, sinse the problemm looks a bit more complex then I initially thought 🥲
Looks like you may have, or your computer thinks you have two screens, unplug or simply reboot. You do have a graphical session with top bar with date etc. implying you are not hitting am error.
Ha, good catch on the top bar. I didn’t even see it.
It’s probably not an error, since I can use terminal mode just fine. But its kinda uneficient
compu9thinks jnplug Uoubdo am
How does anyone manage to fuck up writing that badly and somehow not notice? Do you not read what you write?
Because of short attention and lack of time to re-read and motivation to fix previous message because my brain is focused on next task in a short time to dedicate to Lemmy.
First thing would be to unplug any peripherals such as USB drives, etc. and reboot. It’s possible that the boot sequence was interrupted/redirected to a HDD partition other than the one you want.
I think thats may be the problem. I’ve done this but didn’t work, allways back in this gray screen.
Also update drives in this mode, but doesn’t work also
Since you have the terminal, either use it to browse your drive or drives to see which files are there and identify it. You may also install a nice file manager to do it graphically. Maybe it is just your graphical desktop that got any package uninstalled or has a fallback config or something. Or you installed an extra lightweight desktop without noticing or remembering. Deaktop or even session manager.
Please give more details is it just new installed system or are u loading from usb thumb?
Idk what more can I say. I was using normaly, few days ago, put into charge and started up in this screen
What is the output of this command:
sudo dmesg -l err
ACPI ERROR
ACPI BIOS ERROR
Also; sry for the late
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-versionAlso, 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.
@Homo_Erectus Try hitting enter. If the system does not respond, type “exit” them hit enter. You may be stuck on a grub shell screen that is not displaying, and typing exit will close it and should move along to either a full grub menu or the boot screen (depending on your PC set-up). One of my PCs does this to me so I can’t reboot it remotely. It is an annoyance, but easy enough to work around once you know what to type at the grub shell prompt.
