Page MenuHomeSolus

Bugs found after clean install
Open, LowPublic

Description

Hi guys,

Finally I have the plasma edition from patreon and I must say this is going to be the best KDE distro ever. However, I had trouble trying to install and configure my system. Here is a list of troubles I had:

1.- Whenever I tried to install Solus in /dev/sda5 as my second OS, the BIOS entry never showed up. My disk had this structure:

sda 
   ├─ sda1 (W. Reserved)
   ├─ sda2 (EFI)
   ├─ sda3 (W. Rescue)
   ├─ sda4 (Windows)
   └─ sda5 (Solus)

I didn't have this problem with the old installer whatsoever. Also, another thing I noticed is that every time I tried to reinstall from this iso another UEFI entry was added in my USB when I checked in my BIOS.

I had to erase my entire disk in order to install Solus properly. After a full update, I checked the EFI partition and "BOOTX64.EFI" was missing from my previous attempts.

2.- I think there's still a locale issue. In this pic (https://imgur.com/a/99mIj) Places is pointing the wrong path. My locale is es_ES and I should point to ~/Música, which btw is now created automatically.

3.- In system preferences, I can't set 144hz even though I select it. Everytime I go to screen settings, 119hz is selected by default. My monitor is a ViewSonic XG2401.

inxi -F shows --> Resolution: 1920x1080@143.85hz
xrandr shows --> 1920x1080 119.98 + 143.85*

I wanted to know if this was a KDE issue or Solus's, so I installed openSUSE in another partition. Using that distro I noticed 3 things. The first one: I could easly set 144hz. Second one: the frame rates were correctly sorted and showed (in solus was kinda messy... 30hz on top, 60hz at the bottom and 144 in the middle).

And the third and most important one: Solus performance is waaay superior than SUSE's. Keep up the good work, guys. Thank you and congratulations, this a beautiful thing.

PS. My hardware specs: https://hastebin.com/iqexizobed.sql

Edit 1: Added more info about monitor

Event Timeline

mrkucho created this task.Feb 10 2018, 12:26 PM
Herald removed sunnyflunk as the assignee of this task. · View Herald TranscriptFeb 10 2018, 12:26 PM
Herald added a subscriber: sunnyflunk.
mrkucho updated the task description. (Show Details)Feb 10 2018, 12:34 PM

Hi @mrkucho, sorry I won't be able to help with your first issue, I don't have UEFI nor know much about it. Hopefully @sunnyflunk or someone else will have some ideas on that.

  1. I believe this is one of timing. The test ISO didn't set the locale properly, and when one synced the updates with the fixes I believe the user directory fix was applied before the locale one. You can check by looking at ~/.config/user-dirs.dirs and user-dirs.locale. I'm guessing they probably have the English ones, and that's what Dolphin reads when it's first started. Let us know if they do still have the English versions.
  1. Could you check and see if there's a ~/.local/share/kscreen folder, and a file in it with a bunch of letters and numbers for a name? If it does exist, open it with an editor and look for the line "refresh:", tell me what it says. If you want you can just copy and paste the whole file into a code block here.

@folcred Thanks for your quick reply

  1. I changed the locale manually, so I have no problems with that. I was just pointing out the issue.
  1. Yes, it does. It shows:
"refresh": 143.85479736328125

It seems that the refresh rates is just showing up incorrectly and is not sorted either.

The installer hasn't really changed much since Solus 3, outside of some plasma icons, changing to systemd-boot and integrating usysconf properly.

The directory shortcuts needs testing on a fresh ISO. Having the shortcuts is something I've patched in somewhere, which was definitely not done with thoughts of multilingual installation.

@sunnyflunk I didn't have the problem with the old installer (Solus Budgie iso from august). I do not think the problem was my usb nor bios, cause I tried other KDE distros before installing Solus.

Whenever I tried to install Solus in /dev/sda5 as my second OS, the BIOS entry never showed up.

I don't know about Gigabyte but on ASUS when you keep slamming F8 during boot and the menu will appear, choose Linux Boot Manger.
For permanent solution you can alter boot order in UEFI.

Unknown Object (User) added a subscriber: Unknown Object (User).Feb 11 2018, 9:59 PM

@mrkucho When you installed Solus I see you did not create a second EFI partition of 512MB, and because of that later you will be having problems with updating clear-boot-manager. Because the windows EFI only has about 100MB. What is in the manual is to create an fat32 and flag as ESP/Boot and make it 512MB and that should be sda5. Then create ext4 which will be sda6. Then when installing choose manual mount and mount the sda6 to / and press next and it will automatically create bootloader to sda5. Then after install you can choose efi either windows or Solus but solus will be default.

Unknown Object (User) added a comment.Feb 11 2018, 10:06 PM

@mrkucho Also if you need swap you can create a swap file and in this link is an easy cut and paste setup. https://support.rackspace.com/how-to/create-a-linux-swap-file/

DataDrake triaged this task as Low priority.Oct 16 2018, 7:01 PM