I made a test cnchi-dev-0.14.62-1.
"Systemd-boot" installs without error messages and system reboot properly.
When booting appear systemd v229, then the error message “unable to mount root UUID”. It hangs in the command line and can not perform any operation.
I would like to use Antergos the systemd-boot.
It worked in the last .iso releases and media testing the latest version cnchi version v12.
Now I have to reinstall the system using the latest stable from 21.2. and cnchi v14 after being elected systemd-boot bootloader finishes installing and write on the screen that probably failed to install properly and not boot.
I tried repeatedly and without success.
Finally, I had to go with Grub.
/boot … FAT32
/ … LUKS encrypted EXT4
Do you know where is the mistake? In the last test release it worked without a problem.
Could you please add least link to download a version cnchi v12 and older testing version of the .iso media?
There can not exclude an installation to fail due to the new sysmed v229.
Otherwise use UEFI-GPT
Thank you friends …
I have an AMD CPU a4-5000 (kabini 8330 gpu)
and an external graphics 8570m (Oland - Engineering Names).
These are very low-end harware.
It only uses integrated (kabini - Engineering Names). I’d like the option to switch to an external gpu sometimes using prime.
I use a mesa-git [http://pkgbuild.com/~lcarlier/mesa-git/](link url) repo and I tried now also the latest mesa-git from AUR [https://aur.archlinux.org/packages/mesa-git/](link url) with dri3-enable.
Installation and start a new graphic interface will flawlessly.
According to the site, I tried [https://wiki.archlinux.org/index.php/PRIME](link url)
But it only displays (kabini)
Providers: number : 1
Provider 0: id: 0x84 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 0 name:KABINI @ pci:0000:00:01.0
When I will choose:
DRI_PRIME=1 glxinfo | grep “OpenGL renderer”
It will return a:
OpenGL renderer string: Gallium 0.4 on AMD HAINAN (DRM 2.43.0, LLVM 3.9.0)
In fact, I do not Hainan but I have Oland (Engineering Names)…
This, according temperature sensor displays for about 3 seconds activate external gpu and then turn back to (kabini).
Please Ask me how to properly deploy.
already more than a month trying to install antergos on UEFI with gpt and otherwise work with other systems.
I use SSD.
I tried all cnchi 0.10, 0.11, 0.12 … last release and testing but there is still a problem when creating partitions /boot and /boot/efi.
I have dualboot with windows and create your own partition /boot/efi with fat32, /boot with ext4 and etx4 with luks encryption.
If choose FAT32 /boot/efi will ignore the setup /boot partition and format automatically also with FAT32 and subsequent problems at startup.
I tried to create a FAT32 partition ext4 manually in the windows and then cnchi only mount /boot and /boot/efi without format. Even though there will be some format to FAT32.
It would be possible to make a correction and enforce user settings?
Now I’m trying to install, eighth attempt.
But I have a problem with partitioning, at the last edition of this work.
I have UEFI-GPT with dual boot windows.
Create a FAT32 partition 300-600 megabytes of boot/efi and root / as ext4 …
If I’ll continue with the installation, an error message appears that the partition boot/efi can not be formatted.
After several of experiment, I found that if one section I choose the FAT32 format is changed automatically and fat32 partition to ext4, or conversely.
So if I choose root as ext4, it will overwrite the boot/efi also ext4 and install the very end crashes when setting up the bootloader.
I’m like to install two boot/efi separate partitions for Linux and Windows, it always worked well in previous versions antergos just another distribution.
When I reinstall linux I just format or create a new boot/efi without getting to touch the windows partition.
I tried to create a FAT32 partition, and then only mount during installation. It fits any error message and the installation continues.
At the end of installation, but the error message that no permissions to write to sys /…/ boot / efi partition.