There are so many issues with the 4.1 installer. It always get stuck examining local storage devices. The few times it has gotten past that point the install never actually begins when I confirm it. The one and only time it actually finished installing everything locked up and my pc became unusable when I went restart. I did force power down with by holding the power button and there was no bootable solus on the disk.

I am installing this on a separate ssd from my windows installation. I have installed solus on this pc in the past using the 4.0 installer and never had any of these issues with the installer. From reading the forum I am not the only person who is having these issues with the 4.1 installer.

None of these issues have anything to do with the installer. It has barely changed between 4.0 and 4.1. Everything else is up to changes with the utilities and libraries it relies on, which we don't develop. Not to mention kernel, mesa, and systemd updates in the time between.

    Not to mention the fact that Josh and I are the sole software developers on the team and we have full-time jobs that have to come first. Patches and Pull Requests welcome.

    DataDrake No worries, this is the one distro I want to use and now that all the pieces of the puzzle have finally fallen in place. There is literally no way for me to install this distro now. No other installer I have used has these problems. Its bumming me out because I want to help and learn to package with you guys try and be more involved. That is kind of hard to do when you cant even install the the operating system.

        swagglepuff
        Just reinstalled solus to a platter and have had install issues in the past.
        2 cents:

        • when I make my live iso I don't color outside the lines of this: https://getsol.us/articles/installation/
        • in my experience sometimes you have to trick the install dialogue out. experiment with checking and unchecking. I wish I took notes since I don't know what half my install options really mean--and that's only my fault--but all successful installs for me have come from abandoning what I thought I wanted and doing the opposite🙂

          DataDrake So I found an old 4.0 installer in one of the threads with the same issues as me. It installs solus perfectly except for my system cant see the systemd-boot on my efi partition. One thing I have noticed is that the installer literally only allows me to install to my efi partion that is on a completely separate windows ssd. I tried the following instructions that I got from another thread with this issue and my system was still unable to find the systemd-boot. Which is odd because I use systemd-boot with manjaro. Pop_os also uses systemd-boot with no issues on my system.

          Boot into the live iso and install efibootmgr: sudo eopkg it efibootmgr

          Run efibootmgr with no arguments. You should see an entry for Linux Boot Manager, which for some reason doesn't show up in your actual boot menu but does here. There's a number listed for that entry. Delete it with sudo efibootmgr -b [num] -B

          Now you can recreate it. If your EFI partition is /dev/efi location then do this: sudo efibootmgr -c -d /dev/efi location -p 1 -l "\EFI\systemd\systemd-bootx64.efi" -L "Linux Boot Manager"

          I figured that I would go into gparted and manually create my partitions. I went and made a partition of 512Mib formatted to fat32 and set the flags boot, esp and then created / partition and swap. When I go to install the installer only allows for me to select the efi partition on my windows disk.

          I am beginning to think that this will never actually work on this computer which it has in the past.

            The installer will use the first EFI partition. So the easiest is to use only one EFI partition, just make sure it is large enough (512Mb). If you want to use multiple boot partitions, you may have to fix things manually using rEFInd or efibootmgr.

            Another possible workaround that I have never tested is to remove the boot flag from all the EFI partitions you don't want the installer to check, install Solus, then set back the boot flag on these partitions.

              kyrios I made that EFI partition 1gb just to make sure I have no issues with size for running multiple OS and multiple kernels. EFI boot manager does show Linux Boot Manager but on boot I still can't select it. I am going to try and chroot into my install and run efibootmgr from there instead of the install media and see if it will add properly to the efi partition on the other disk. If that doesn't work then I plan on installing Clover EFI in windows and setting it to boot first.

                Well I guess if you just keep trying and trying the install eventually works haha. My system was able to finally see systemd-boot after install of 4.0. The update from the 4.0 install image to current is only 1.02gb. The only issue was the system didnt actaully restart so I had to force power down and and back on and everything loaded nicely!!!

                I just find it incredibly odd that the 4.1 installer won't actually install solus but the old 4.0 does.

                  swagglepuff

                  swagglepuff The only issue was the system didnt actaully restart so I had to force power down and and back on and everything loaded nicely!!!

                  That is because of a massive change of systemd which happened after Solus 4.0.

                      That makes sense. So happy to be back and excited!! Out of all the 15+ distros I have tried solus just hits that sweet spot for me.