Hi Michal, On 2-Jun-25 15:28, Michal Schorm wrote: > I maintain a fleet of very old 64-bit laptops in various conditions > for events for youth. > I use a set of custom installation and configuration scripts to > install Fedora + Cinnamon DE. > > When debugging an issue on two machines, I discovered that using > 'acpi=off' as a kernel parameter breaks every BIOS installation I > have, and some UEFI too. > > Some UEFI installations just have low resolution, or respond noticeably > slower. > Some UEFI and some BIOS installations freeze somewhere during the boot > sequence. (haven´t examined more closely) > > And most of the BIOS installations boot, but fail to display the GUI. > The TTY1 ends in some non-interactive state, but not frozen (still can > display incoming systemd journal messages etc.). I can switch to other > TTYs, where there is a TUI login prompt and the system is normally > accessible from there. > > I carefully examined the kernel messages and systemd journal, both > with extra verbosity levels. > Nothing seems wrong there. The multi-user.target was reached, all > services are fine, none related errors or unusual warnings, all > necessary packages seem to be installed, ... > > My first question is whether it is expected that 'acpi=off' will > prevent the BIOS installations from displaying GUI. Or if any of you > can reproduce at all. > > My second question is how to further debug and where to look. > Most of the BIOS systems work completely normal when 'acpi=off' is NOT > specified. > I fixed one machine by setting 'acpi=on' (which leads to a different > result than not specifying the acpi kernel option value at all) and I > have one machine that shows the exact same symptom, but the cause > doesn't seem to be 'acpi=...' related, as any possible value won't > help.
I'm not sure why you are specifying apci=off in the first place? Most modern (even old modern) systems all need ACPI for various reasons. Generally speaking passing any extra kernel commandline options other then the default "root=... ro rhgb quiet" is a bad idea unless you have a very specific reason for doing this; or were asked to try a kernel cmdline option by a kernel-developer while debugging some option. As for acpi=on helping, "on" is not a valid value for acpi="val", so that likely is some false positive related to no longer specifying acpi=off. TL;DR: do not use acpi=off, actually do not use any special kernel commandline arguments at all. Regards, Hans -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
