This project is to enable individuals to report issues or request features in regards to the installation of Solus.
Mon, Jan 7
TL;DR : sudo localectl --no-convert set-keymap de-latin1
Sat, Jan 5
Despite what you may think, I'm honestly just tired of closing tasks for things we don't need.
@DataDrake No need for spite. At least we now know how things stand. Which is a good thing. Thanks.
No. We have our own installer for a reason, even if it does have fewer features at the moment.
Wed, Jan 2
Tue, Dec 25
Looking at the current installer sources (https://github.com/getsolus/os-installer) it seems that creating /etc/kernel/cmdline.d/50_keymap.conf would be rather trivial since there is already code to create the resume file here: https://github.com/getsolus/os-installer/blob/master/os_installer2/postinstall.py#L708
Mon, Dec 24
Got it. I opened https://github.com/getsolus/help-center-docs/pull/186 to add some hints to the help center docs in the meantime.
Yes, it's a bug in the installer. It won't be addressed until we rewrite the installer.
This seems to still be an issue on the 3.9999 release. I configured disk encryption and a German keyboard layout in the installer. After finishing the install and rebooting I got the US layout at the password prompt. Manually modifying /etc/kernel/cmdline.d/50_keymap.conf did the trick. Is this a bug with the installer?
Dec 18 2018
I can confirm that blacklisting nouveau fixes this issue.
Dec 12 2018
Dec 11 2018
The easiest way is to just install it on a separate USB drive.
To my knowledge, what you are trying to do requires grub for both BIOS and UEFI installs. We only support GRUB for BIOS installs, not UEFI. So yes, if you want UEFI support it will need to be a separate install.
You can boot from grub, just not on UEFI. We use systemd-boot for UEFI.
We aren't a normal distro so expecting a normal install doesn't make any sense. Solus is intended to be installed on a normally partitioned harddrive. It also doesn't use grub for UEFI installs which is likely part of your issue. Sorry, but what you are asking for is not something we support.
Solus isn't intended to be run as a live system from a USB for everyday use. You can install it to a USB drive that is treated like a normal HDD/SSD. Our live environment is configured significantly differently from other distros which is why you are having so many issues. MultibootUSB installs may be more common in the Linux realm, but they are not as common as you think.
Solus has a helpcenter entry regarding USBiso
Dec 7 2018
We have zero interest in using someone else's installer. Ours is overdue for an overhaul, but I have higher priority projects in my queue.
You can always fix partition errors yourself by moving partitions around (assuming the filesystems contained in them support it). But that's also going to copy everything in the partition around.
Dec 6 2018
Asus and Lenovo SSD equipped laptops here. Important question: whatever fix arrives, will it require a new Solus installation or not? Thanks...
Dec 5 2018
I was making a note for myself on how to fix it. You don't need to do anything :)
I just checked what happens if you have the installer resize a windows partition, and it does the same behavior. It leaves 32 sectors between the partitions, which causes the alignment to be off.
Looks like all we need to do is add:
Nov 26 2018
I am also experiencing this issue on an LVM on LUKS install. Had to manually include in fstab with: /dev/SolusSystem/Swap none swap sw 0 0.
Nov 17 2018
Any updates here?
Nov 9 2018
Not sure if it's the same problem but here's what I have tested:
Nov 8 2018
Is this still an issue with the latest ISO? I have successfully installed EFI full encryption via qemu with it.
Nov 6 2018
I also encountered this issue with the budgie and plasma iso 3.9999. However no problems with the previous iso.
Nov 1 2018
We are no longer adding new functionality to eopkg, I will however take this under advisement for the next package manager.
There are tons of utilities that can do this
Oct 25 2018
Oct 17 2018
Small correction, the only item I was going to work on was getting the I.P. address of the user, which was done previously via a /location endpoint. This was replaced with our new infrastructure. The issue at hand is not explicitly related to geolocation but rather network connectivity. I don't see this being resolved until we have some new installer.
Oct 16 2018
I think this is Low Hanging Fruit for the next ISO.