You are not logged in.
Pages: 1
Hello everyone!
I cannot install arch "normally" (nor Ubuntu or manjaro, I tried only with these so far) on my brand new PC, the installation gets stuck at the beginning, right after I select install arch. It's supposed to reboot, which I think my PC does, but the screen freezes and I can't do anything.
I managed to install the OS with modifying the kernel parameters with acpi=off. This is the only parameter change that works, I think I tried most I found that might relate to this issue. Naturally, this came with other issues and I can't really use the PC this way. The installed OS can also only be booted with the acpi=off parameter.
I am relatively new to the linux world, so probably I just don't know where to look for the solution.
Somewhere I read that my hardware might be too new and there is no support for it yet? I can list the parts if necessary.
Since then, I installed a windows on the PC so I can actually use it, but I would gladly try to install it on another drive (first, and if it works then it can replace windows) if that would give more information.
Thank you for any kind of help in advance.
Edit #1:
PC:
Motherboard: GIGABYTE X870 AORUS ELITE WIFI7 ICE
CPU: AMD Ryzen 7 9800X3D
RAM: Kingston FURY 32GB KIT DDR5 6000MT/s CL36
GPU: NVIDIA RTX 3080 TI
PSU: Be quiet! PURE POWER 12 M 1000W
Default BIOS (latest version, F3g), secure boot disabled.
Last edited by itstomforsure (2024-11-26 15:03:10)
Offline
There is a number of kernel parameters you could try. https://www.kernel.org/doc/Documentatio … meters.txt
There is no one size fits all solution to your problem. To help you, we need more information about your hardware. However, turning off secure boot should be the first thing you do in the BIOS/UEFI. Meanwhile, post as much information about your hardware as possible.
Offline
The secure boot was the first thing I changed, even before I started the installation (I have installed arch on my previous PC just before I first tried to install it onto the new system.)
Thanks for the link, I'll look into it in a bit.
Motherboard: GIGABYTE X870 AORUS ELITE WIFI7 ICE
CPU: AMD Ryzen 7 9800X3D
RAM: Kingston FURY 32GB KIT DDR5 6000MT/s CL36
GPU: NVIDIA RTX 3080 TI
PSU: Be quiet! PURE POWER 12 M 1000W
The only thing I changed in the BIOS other than the secure boot is I set the EXPO2 ram profile to run at the desired clockspeed (5600MT/s).
Offline
You might want to try the BIOS defaults minus secureboot. I had issues with those and Linux on my own AORUS (different model).
Offline
I changed it back to BIOS defaults with secure boot disabled but still the same.
I also tried the following:
acpi=on
acpi=strict
acpi=noirq
acpi=rsdt
None of them helped. Will continue checking the parameters.
Offline
Especially the acpi_osi= parameter seems to be involved in a lot of fixed. You could try and spoof Windows https://learn.microsoft.com/en-us/windo … inacpi-osi
Offline
I tried acpi_osi="Windows 2000" acpi_osi=! together as the kernel parameter man page mentions, nothing. I also tried multiple windows version, with and without the acpi_osi=!, still nothing.
Offline
The new kernel version 6.12.1 did not solve the issue yet.
Offline
Since your testing linux kernels, how about linux-lts?
My understanding is you can get the arch ISO to boot with acpi=off and actually install the system, but it won't boot after installation without the acpi=off parameter, which I agree is not ideal.
Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.
Offline
I tried with the lts kernel but it had no effect. I also tried with zen and it also behaved the same way as the default one and the lts.
Your understanding is right, and yes, it isn't. I've contacted the gigabyte support, maybe they have information that can help.
Thanks for the suggestion!
Offline
Instead of acpi=off add "ignore_loglevel debug earlyprintk=vga,keep nomodeset" (and certainly remove the quiet parameter) and see whether that leaves you w/ any output reg. the failure.
Then in doubt make a photo of your screen and link it.
Offline
Pages: 1