Am 08.02.23 13:06 schrieb Stuart Henderson: > On 2023-02-08, Michael Hekeler <[email protected]> wrote: > > Am 04.02.23 17:48 schrieb Daniele B.: > >> Sorry if I bother you again with the thread. > >> > >> The minipc will be on business from tomorrow and I will use it > >> together with a little student of mine: it is enough critical that the > >> "not configured" hello! doesn't reppresent anything "risky". > >> Eg: I tried to tweak the custom bios of Fujitsu for a more perfomant > >> fan/cpu but the machine started litterally to fly while booting. > >> Precautially > >> I hanged manually the booting process. > >> > >> The part of dmesg I'm wondering about is the following: > >> > >> "FUJ02E3" at acpi0 not configured > >> > >> "PNP0C14" at acpi0 not configured > >> "PNP0C32" at acpi0 not configured > >> "PNP0C14" at acpi0 not configured > >> > >> "PNP0C0B" at acpi0 not configured > >> "PNP0C0B" at acpi0 not configured > >> "PNP0C0B" at acpi0 not configured > >> "PNP0C0B" at acpi0 not configured > >> "PNP0C0B" at acpi0 not configured > >> > >> acpicpu0 at acpi0: C1(@1 halt!), PSS > >> acpicpu1 at acpi0: C1(@1 halt!), PSS > >> acpicpu2 at acpi0: C1(@1 halt!), PSS > >> acpicpu3 at acpi0: C1(@1 halt!), PSS > > > > If you just want to stop these messages from filling your logs you can > > boot into UKC mode by entering -c at the boot prompt: > > UKC> disable acpi > > UKC> quit > > > > > > ...(not a real solution but more a quick fix) > > > > > > This is bad advice. ACPI may be needed for thermal management, interrupt > routing, and maybe other things. These "not configured" > devices are unlikely to be a problem.
indeed this is NOT a good advice of mine. @Daniele B. please ignore my last message.
