Startup issues with Linux Mint

O

Omnifitense

Member
Joined
Apr 18, 2026
Messages
42
Reaction score
11
Credits
410
Back in February, I switched from Win 11 to Linux Mint on my Alienware laptop. It's working very well, apart from a very strange bug I'm encountering on bootup.

It hangs on the Mint logo for a while, and in the background (when I press Escape) it's displaying the following error message, which I'm transcribing from a screenshot because the iPod linkage currently isn't working:

ACPI BIOS Error (bug): Could Not Resolve symbol [\_SB.PC00.XHCI.RHUB.SSO3], AE_NOT_FOUND (20250404/DSWLOAD2 -162)
ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20250404/psobject -220)
ACPI BIOS Error (bug): Could Not Resolve symbol [\_SB.PC00.XHCI.RHUB.SSO4], AE_NOT_FOUND (20250404/DSWLOAD2 -162)
ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20250404/psobject -220)
ACPI Error: Missing argument for method [TUPC] (20250404/dsmethod-486)
ACPI Error: Aborting method \_SB.PC09.TXHC.RHUB.SS02._UPC due to previous error (AE_AML_UNINITIALIZED_ARG) (20250404)
ACPI Error: Missing argument for method [TUPC] (20250404/dsmethod-486)
ACPI Error: Aborting method \_SB.PC09.TXHC.RHUB.SS02._UPC due to previous error (AE_AML_UNINITIALIZED_ARG) (20250404)
/dev/nvme0n1p2: clean, 816377/62400384 files, 44318018/249919744 blocks
[!!!!!!] Failed to start up manager.
system[1]: Freezing execution.

Sometimes it takes multiple restarts, but I AM able to get into the OS and it works just fine.
 


ACPI errors are related to the Advanced Configuration and Power Interface, which helps the operating system manage hardware components and power. These errors can often be ignored if they do not affect system performance, you can try updating your BIOS or kernel parameters which may help resolve them, but sometimes they do not

The main issue here is "Failed to start up manager"

Please boot with systemd.log_level=debug set in kernel cmdline and attach the logs. There's currently too little information for any investigation.
 
To boot with systemd.log_level=debug set in the kernel command line, follow the steps for your specific bootloader. This parameter overrides the LogLevel= setting in your systemd configuration file.

@GatorsFan
Do these instructions look right to you?

Code: 
Restart your computer.
When the GRUB menu appears, highlight your current kernel (usually the first option) and press e to edit.

    If the menu doesn't appear, hold the Shift key (for BIOS/Legacy) or tap Esc (for UEFI) during startup.

Use the arrow keys to find the line starting with linux, linux16, or linuxefi.
Move to the end of that line and add a space followed by: systemd.log_level=debug.

    Tip: For maximum verbosity, also add systemd.log_target=kmsg and log_buf_len=1M.

Press Ctrl + x or F10 to boot immediately with these settings.

These are temporary changes for one single session.
 
Also after one to episodes do this in a terminal
Code: 
systemd-analyze -blame
post results back here.
 
kc1di said:
Also after one to episodes do this in a terminal
Code: 
systemd-analyze -blame
post results back here.
Click to expand...
5.555s NetworkManager-wait-online.service
1.622s systemd-tmpfiles-setup.service
1.043s NetworkManager.service
756ms thermald.service
167ms boot-efi.mount
163ms blueman-mechanism.service
156ms lm-sensors.service
150ms dev-nvme0n1p2.device
117ms [email protected]
110ms systemd-journal-flush.service
91ms upower.service
88ms gpu-manager.service
86ms accounts-daemon.service
83ms lvm2-monitor.service
81ms systemd-udev-trigger.service
79ms lightdm.service
78ms plymouth-quit-wait.service
77ms udisks2.service
76ms rsyslog.service
72ms ubuntu-system-adjustments.service
71ms gnome-remote-desktop.service
68ms apparmor.service
64ms power-profiles-daemon.service
 
Last edited:
GatorsFan said:
ACPI errors are related to the Advanced Configuration and Power Interface, which helps the operating system manage hardware components and power. These errors can often be ignored if they do not affect system performance, you can try updating your BIOS or kernel parameters which may help resolve them, but sometimes they do not

The main issue here is "Failed to start up manager"

Please boot with systemd.log_level=debug set in kernel cmdline and attach the logs. There's currently too little information for any investigation.
Click to expand...
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Linux version 6.17.0-20-ge>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Command line: BOOT_IMAGE=/>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: KERNEL supported cpus:
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Intel GenuineIntel
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: AMD AuthenticAMD
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Hygon HygonGenuine
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Centaur CentaurHauls
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: zhaoxin Shanghai
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: x86/split lock detection: >
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-provided physical RAM>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000001>
lines 1-23...skipping...
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Linux version 6.17.0-20-generic (buildd@lcy02-amd64-120) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #20~24.04.1-Ubuntu SMP PREEMPT_DYNAMI>
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=51879ee2-445d-4046-96a2-e968d1683b5d ro quiet splash
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: KERNEL supported cpus:
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Intel GenuineIntel
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: AMD AuthenticAMD
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Hygon HygonGenuine
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Centaur CentaurHauls
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: zhaoxin Shanghai
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-provided physical RAM map:
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000061514fff] usable
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000061515000-0x0000000065510fff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000065511000-0x0000000065d71fff] ACPI NVS
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000065d72000-0x0000000065ffefff] ACPI data
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000065fff000-0x0000000065ffffff] usable
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000066000000-0x00000000787fffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000f9ffffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000027fffffff] usable
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: NX (Execute Disable) protection: active
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: APIC: Static calls initialized
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: efi: EFI v2.7 by Dell
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: efi: ACPI=0x65ffe000 ACPI 2.0=0x65ffe014 SMBIOS=0x61da5000 TPMFinalLog=0x65c78000 ESRT=0x61d27018 MEMATTR=0x54ea8018 MOKvar=0x61d71000 INITRD=0x54e74018 RNG=0x65f2e018 TPMEventLog=0x65f1f018
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: random: crng init done
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: efi: Remove mem104: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: efi: Remove mem105: MMIO range=[0xf8000000-0xf9ffffff] (32MB) from e820 map
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: e820: remove [mem 0xf8000000-0xf9ffffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: efi: Remove mem107: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: SMBIOS 3.6 present.
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: DMI: Alienware Alienware m16 R2/0P9YG5, BIOS 1.16.0 09/22/2025
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: DMI: Memory slots populated: 1/2
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: secureboot: Secure boot enabled
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: tsc: Detected 3000.000 MHz processor
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: tsc: Detected 2995.200 MHz TSC
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: last_pfn = 0x280000 max_arch_pfn = 0x400000000
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: MTRR map: 8 entries (3 fixed + 5 variable; max 23), built from 10 variable MTRRs
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: x2apic: enabled by BIOS, switching to x2apic ops
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: last_pfn = 0x66000 max_arch_pfn = 0x400000000
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: esrt: Reserving ESRT space from 0x0000000061d27018 to 0x0000000061d270a0.
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: Using GB pages for direct mapping
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: secureboot: Secure boot enabled
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: RAMDISK: [mem 0x4b06c000-0x5023dfff]
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: Early table checksum verification disabled
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: RSDP 0x0000000065FFE014 000024 (v02 ALWARE)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: XSDT 0x0000000065F30228 00017C (v01 ALWARE Dell Inc 00000002 01000013)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: FACP 0x0000000065FDA000 000114 (v06 ALWARE Dell Inc 00000002 01000013)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: DSDT 0x0000000065F5C000 07AC6C (v02 ALWARE Dell Inc 00000002 01000013)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: FACS 0x0000000065CA2000 000040
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FFC000 00038C (v02 PmaxDv Pmax_Dev 00000001 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FFB000 000689 (v02 PmRef Cpu0Ist 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FFA000 000603 (v02 PmRef Cpu0Hwp 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FF9000 0001AB (v02 PmRef Cpu0Psd 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FF8000 000540 (v02 PmRef Cpu0Cst 00003001 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FF6000 001BAF (v02 PmRef ApIst 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FF4000 001620 (v02 PmRef ApHwp 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FF2000 001349 (v02 PmRef ApPsd 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FF1000 000FBB (v02 PmRef ApCst 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FED000 003BC8 (v02 CpuRef CpuSsdt 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: DTPR 0x0000000065FEC000 000088 (v01 00000000 00000000)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FEA000 001E8C (v02 ALWARE AWCCTABL 00001000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FE6000 00306A (v02 INTEL PDatTabl 00001000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FE5000 000A3D (v02 INTEL IgfxSsdt 00003000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: SSDT 0x0000000065FDB000 009B64 (v02 INTEL TcssSsdt 00001000 INTL 20210930)
Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: ACPI: HPET 0x0000000065FD9000 000038 (v01 ALWARE Dell Inc 00000002 01000013)
 
In the BIOS Security section there is a checkbox:

Intel Software Guard Extension (SGX)

Set it to Enable (instead of Disable or Software defined
 
Disabled Secure Boot, and I could not find Intel Software Guard Extension. Updated the BIOS over-air, no change in any regard.
 
====== ACPI Errors ======
Created Thursday 02 February 2023
If you want to stop seeing these ACPI errors flash by on startup, do this:
(from : https://www.linux.org/threads/acpi-...resolve-symbol-yadda-yadda.58522/#post-281580 )

1) Open the grub file at /etc/default/grub. I use the text editor Pluma, so in terminal:
sudo pluma /etc/default/grub
If you use a different editor, change "pluma" to whatever you use.

2) Find the line: GRUB_CMDLINE_LINUX_DEFAULT="quiet" .
Change it to read: GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 splash"
Save and exit.

3) Then run: sudo update-grub

Source: https://easylinuxtipsproject.blogspot.com/p/faq-3.html#ID19
(This website focuses on Mint and Ubuntu, but a lot of the advice given on it works on most Linux distros.)

NOTE: It might be a good idea to make a backup copy of the grub file before making changes.

============================================
 
Last edited:
Hi @Condobloke more than likely he will be using xed as the text editor and the best command to use with that is this.
Code: 
xed admin:///etc/default/grub
Then edit as you said. Save and
Code: 
sudo update-grub
@Omnifitense those acpi error are not normally hurtful to the running of the system and can usually be ignored. they systemd-analyze out put does not look bad actually so do as @Condobloke said and hide the messages and enjoy the system.
 
There is this as well

Apr 18 08:56:57 omnifitense-Alienware-m16-R2 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

I do not know much about Split Locks but from what I am to understand is when the kernel encounters a split lock, it may crash or warn about it, particularly in user-space applications, to maintain system stability and performance - I believe you can check dmesg to see if it gives any more info - this can be disabled

sudo split_lock_detect=off
Click to expand...
If if does not work you can re-enable it
sudo split_lock_detect=on
Click to expand...
 
kc1di said:
Hi @Condobloke more than likely he will be using xed as the text editor and the best command to use with that is this.
Code: 
xed admin:///etc/default/grub
Then edit as you said. Save and
Code: 
sudo update-grub
@Omnifitense those acpi error are not normally hurtful to the running of the system and can usually be ignored. they systemd-analyze out put does not look bad actually so do as @Condobloke said and hide the messages and enjoy the system.
Click to expand...
I was able to do this, as well as the Split Locks mentioned above, and while an initial restart for a Linux kernel went very well, subsequent restarts did not, reverting to form.
 
Omnifitense said:
I was able to do this, as well as the Split Locks mentioned above, and while an initial restart for a Linux kernel went very well, subsequent restarts did not, reverting to form.
Click to expand...
Did changing the string in the /etc/default/grub file from this
GRUB_CMDLINE_LINUX_DEFAULT="quiet" .

To this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 splash"

Help?
 
Just my two cents worth...
I notice you're using Kernel 6.17...it's know to cause problems...I would go with Kernel 6.8 which is supported till 2029.

Before you install Mint...always disable secure boot. When I install Linux Mint to my SSD...I always install it to the whole Drive...select Erase Disk and Install Linux Mint...the Mint installer creates two Partitions...Boot and Root...that's all you need.

I've been using Linux Mint for 11 years without problems...I have two Mint Distros in Virtualbox and Mint Cinnamon 22.3 on another SSD plus Mint xfce on my 14 year old Laptop.
All Boot normally...it also could be a Drive problem...are you using a HDD or SSD...maybe something else to check.
1776820726276.gif
 
You must log in or register to reply here.

Similar threads

BoneCream
Solved Lenovo Ideapad 1 15" display | Kali Linux Purple
Replies
5
Views
785
BoneCream
BoneCream
BoneCream
Lenovo Ideapad 1 BIOS error
Replies
6
Views
848
Brickwizard
Brickwizard
Goatmilk
ACPI BIOS Error (bug): Could not resolve symbol yadda yadda
Replies
7
Views
2K
Condobloke
Condobloke
E
Hi, I have a serious problem when I try to start the computer.
2
Replies
29
Views
15K
wizardfromoz
wizardfromoz
D
Linux Mint Cinnamon 22.3 live Boot Repair freezing and becoming non-responsive
Replies
3
Views
598
Condobloke
Condobloke


Follow Linux.org

Members online

Total: 4,674 (members: 3, guests: 4,671)

Latest posts

Top