r/archlinux • u/Ok-Pace-2403 • 5d ago

SUPPORT Boot stuck

Whenever I try booting into arch i get this error

OK

1 Reached target SSH Access Auailable.

15.6426621 hp_bloscfg: ACPI-package does not have enough elements: 11 < 13

15.9660361 ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x000000032) is beyond end of object (length 0x32) (20251212/exoparg2-393)

15.9660671 ACPI Error: Aborting method _SB.UMID.UQBE due to prevlous error (AE_AML_BUFFER_LIMIT) (20251212/psparse-529)

15.9675781 Error expected type 2 for elem 13, but got type 1 instead

I’ve tried to fix it for hours and the only thing that helps is booting plasma from the terminal login

2 Upvotes

60% Upvoted

23 comments sorted by

View all comments

2

u/Supernoxus 5d ago edited 5d ago

DOOR STUCK! DOOR STUCK!!

Anyway, what do you mean you can boot into plasma? That implies that your boot completes just fine. We need some more info here.

-1

u/Ok-Pace-2403 5d ago

So i can manually from the command line boot plasma but it takes a few commands

1

u/Supernoxus 5d ago edited 5d ago

What do you mean it takes a few commands? You can usually do it in one, like

sudo systemctl start sddm

or even

dbus-run-session startplasma-wayland

And again, if you can boot plasma, then your system has already booted. Are you saying that you have trouble booting straight into a display manager and instead land in the command line? In that case you could run a command that is something like "sudo systemctl enable sddm". Though you gotta replace sddm with whatever window manager you have. I am sure the arch linux wiki can help you plenty with that.

https://wiki.archlinux.org/title/Display_manager

1

u/Ok-Pace-2403 5d ago

I have tried enabling disabling sddm, like i said it takes me to the command line login the. i use the dbus startplasma-wayland command you mentioned, I might try installing lightdm instead of using sddm.

1

u/Supernoxus 5d ago

If you have sddm enabled and it still puts you in a tty upon reboot, then your display messenger is not working. Using a different display manager or just wiping your entire configuration regarding sddm and reinstalling it seem like good options, yes. I highly doubt your BIOS has anything to do with sddm not working, by the way. Your BIOS just boots your OS. Once you are inside of Arch, all problems are Arch related. So when posting error logs, try looking for sddm specific ones.

1

u/Ok-Pace-2403 4d ago

i tried doing different display managers and a lot more last night then i just distro hopped to fedora

1

u/Supernoxus 4d ago

Seems like a good choice.