You are not logged in.
Pages: 1
The Arch Linux ISO now includes a guided installer. Use this subforum for questions and issues related to this feature.
Support threads related to this installer will be moved here to provide a repository of these issues. Please do not use this subforum for commentary or discussion about the merits of providing this feature.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Is it possible to make this script work under BIOS firmware?
Offline
Is it possible to make this script work under BIOS firmware?
Just to clear this up, it works with BIOS too now days
Offline
i initially used the installer script. my question is, if the script provides you a way to select your preferred DE, after installation you are only in terminal and expected to continue installation to have X and your DE. why asked the DE in the script during install then?
Offline
The Arch Linux ISO now includes a guided installer. Use this subforum for questions and issues related to this feature.
Support threads related to this installer will be moved here to provide a repository of these issues. Please do not use this subforum for commentary or discussion about the merits of providing this feature.
I have avoided using the guided installer due to limits on arch forum support. By using this time-saving feature, I can obtain support on the forum? (Even if the support is limited to this specific thread?)
Offline
It's limited to this entire subforum and mostly to issues directly related to the installer. Do note that it has occasional had bugs with harddisk detection and as mentioned here the general support and relevance of it do extend to getting packaged as is, there are no guarantees for it work on any given iso
Offline
It does not really work good:
Me and a friend of mine, we had an issue after using arch's installerscript. I even had this on two PCs, he had it on one PC:
The boot process is setup wrong under circumstances I cannot specify closer, because after repairing it manually I have a working system.
But the first time the kernel is updated on a system installed using the script, the system reliably and reproduceable won't boot anymore.
There are some UEFI/BIOS shenanigans going on, or systemd-boot is disfunctional by itself, I dont knwo. I solved it by applying the usual old bootloader repair procedure, using the arch install medium, archchroot, mkinitfscüi -P, installing grub and building the grub menu.
It was same for my old system some time, ago. So overall it's even four systems with identical behaviour. I have yet to see a fully working system setup using the installscript.
There still is a way to go
Last edited by Elmario (2024-12-04 21:31:21)
Offline
Please report those issues on https://github.com/archlinux/archinstall/issues
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1