Had the same issue with the new Ryzen 4000 series laptop. Ended up installing Solus 4.1 on 16G usb stick (using the other computer), fully updating it and then dd'ing usb drive to the laptop ssd.
It worked surprisingly fine. The most painful and slow process was waiting for eopkg up on usb stick.
Couple of notes:
- In order to create a separate bootloader on usb stick, I had to physically unplug boot drive of my PC, which was used to install Solus on usb stick. On the page where you choose the name for the system during installation process, there will be drop-down box for the location of bootloader. For me the only option was my existing bootloader, until I unplugged that drive.
- After installation on usb, doing
eopkg up was more painful then usual.
- During package download it hanged for a long time on some package, so I just
Ctrl-C that, restarted update and it kept going.
- I initially ran
eopkg up from terminal in DE, but during update the OS tried to go to sleep and I could not login back to DE. And since I did not forward output of eopkg up to any file, I was unable to determine if it was doing anything or hanged up again. So I killed eopkg from tty, rebooted, and now was unable to login into DE at all.
- So from tty
eopkg check and eopkg rdb indicated that all installed packages were fine, but eopkg up failed with the same error as in https://discuss.getsol.us/d/4996-help-with-ssl-certificate-error.
- After running the command from the issue
eopkg up continued, but after everything was installed, it stuck on Syncing filesystems. I read somewhere, that this might be due to some issues with removable devices, and suggested workaround was to plug/unplug those devices. But my OS was on the "removable" device.
- So I killed
eopkg again and rebooted. But eopkg up now said that all packages are up to date, so I tried installing some package (e.g. eopkg it neofetch) and then it installed and finished all that stuff that it didn't do during system update -- properly updating kernel, users etc.
Maybe someone will find this troubleshooting experience helpful. In the future I think I'll just be doing initial eopkg up from tty to avoid some of the encountered issues.
The good thing is that the new kernel 5.10 should be released soon, which is the only remaining task in https://dev.getsol.us/T8629 at the moment. So hopefully we will get the new Solus 4.2 image soon.
