Re: X server blocked by SecureBoot
On Sun, Nov 3, 2024 at 4:04 PM Christian <chris@argonautx.net> wrote:
> [...]
> Well yes, and it's pretty confusing because I disabled secure boot, and
> the problems remained. Which makes me really clueless, because there is
> not much information left on the dmesg. Maybe its something with BIOS or
> ACPI? By adding loglevel=3 to the cmdline I got something more:
>
> [ 0.277298] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.SADX], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277301] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277304] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.SADS], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277306] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277306] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.277307] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14._DSM], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277308] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277309] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.277310] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.BTRT], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277311] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277312] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x5B84)
> [ 0.277325] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.DBTR], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277326] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277327] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x5B84)
> [ 0.277328] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14._PRR], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277329] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277329] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.277330] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.BRDY], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277331] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277334] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.BGAP], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277335] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277337] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.BRDS], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277338] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277339] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.277340] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.ECKY], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277341] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277342] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.ECKV], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277343] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277344] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.277345] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.GPCX], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277346] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277349] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.GPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277350] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277351] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.277352] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.GLAX], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277352] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277355] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.GLAI], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277356] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277356] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.277357] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.BTLY], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277358] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277360] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PC00.XHCI.RHUB.HS14.BTLC], AE_ALREADY_EXISTS (20220331/dswload2-326)
> [ 0.277361] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
> (20220331/psobject-220)
> [ 0.277362] ACPI: Skipping parse of AML opcode: OpcodeName
> unavailable (0x0014)
> [ 0.278459] ACPI: 12 ACPI AML tables successfully acquired and loaded
> [ 0.284491] ACPI: Dynamic OEM Table Load:
> [ 0.284496] ACPI: SSDT 0xFFFF913A02036600 0001AB (v02 PmRef Cpu0Psd
> 00003000 INTL 20200717)
> [ 0.284906] ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
>
> But most hits at $SEARCHENGINE showed this is nothing to worry. And I
> need to start a new thread anyway.
>
> Has anyone any more successions ?
I don't think the ACPI errors are related to your original complaint.
But I could be wrong.
ACPI errors are usually benign, but they can manifest themselves as
problems with power management. In particular, the S3 and S4 power
states. S3 and S4 are related to sleep and hibernate.
The ACPI errors usually can be fixed by updating the UEFI. I can only
say "can be" because the OEM has to provide the update, and there
might not be one.
Also see <https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/16_Waking_and_Sleeping/initialization.html>.
Jeff
Reply to: