dostana
Well 5.0.5 is in unstable right now and unstable repo is synced to to stable once a week on Friday / Saturday~ depending on where you live unless there are issues that hold it back. So.. Wait a day or two and update as you normally would.

    thanks, but make menuconfig is not accepted. Is the following process right or to be different in solus? I'm basic user testing my laptop to be on edge. thanks
    cp /boot/config-$(uname -r) .config
    make menuconfig
    sudo make -j 4 && sudo make modules_install -j 4 && sudo make install -j 4
    sudo update-initramfs -c -k XXXXXXX
    sudo update-grub

    Just for curiosity, Can i not compile a kernel from source downloaded locally? Just have a look ....here. If possible guidance appreciated... thanks

    root@dost /home/dostana/Downloads/linux-5.0.6 # sudo make -j 4 && sudo make modules_install -j 4 && sudo make install -j 4
    ./scripts/gcc-version.sh: line 26: gcc: command not found
    ./scripts/gcc-version.sh: line 27: gcc: command not found
    make: gcc: Command not found
    /bin/sh: gcc: command not found
    HOSTCC scripts/basic/fixdep
    /bin/sh: gcc: command not found
    make[2]: *** [scripts/Makefile.host:90: scripts/basic/fixdep] Error 127
    make[1]: *** [Makefile:476: scripts_basic] Error 2
    make: *** [Makefile:634: include/config/auto.conf] Error 2
    root@dost /home/dostana/Downloads/linux-5.0.6 #

      dostana
      You should know that Solus doesn't target people who want the "bleeding edge" its an opinionated, curated, rolling release with sane defaults. If something breaks on your unsupported setup, pretty sure official Solus support won't care (If you didn't know, changing the kernel is kinda a big deal, you need to understand things such as the nvidia driver for example if you need it, is built against the kernel, change the kernel and don't rebuild the driver against it, you boot to a blank screen).

      I take no responsibility if you brick you system.

      But having said that, your errors are because gcc isn't installed. If you're going to mess around you'll want some build tools, this is Solus equivalent of debian build essentials:
      sudo eopkg install -c system.devel

      Also replace sudo update-grub with sudo clr-boot-manager update
      On UEFI installs grub won't even be there and on legacy boot installs, you still update in this manor as far as I'm aware.

      I don't know beyond that, havn't built a kernel myself since slackware 8 maybe? You are now ready to brick your system 😛

          Yeah, I think last time I ran a kernel build was 4.0. Why bother anymore ? (imo)

            Harvey
            thanks for advice, i shall not try it. Used to working with ubuntu then settled with Deepin for months and later found performance issues then came Solus4. Kernel update from main stream is easy and no system break occur. Precaution is better then cure. My system AMD A9 is faster then ever but slow during boot up and initial start of some applications. Is 60 to 100 seconds boot up normal?.

                @dostana
                Probably not the best person to ask. My system is from 2010. My bios takes that long to detect all my hard drives (not really, but it does take awhile). Ask me again when zen 2 is out... money is burning a hole in my pocket. Launch already!

                You can run:
                systemd-analyze blame

                To see what the hold up is.

                  Harvey
                  I like your humble words. Thanks dude, Have a good time> If problems befall i'll knock at your door in forum and others. chau

                    dbarron
                    I think working in virtual machine and doing messy things is fine. But boxes in Solus4 do have some issues or i'm impatient.

                      With both my previous i5 4590 and current R5 2600, my boot time is around 5-6 seconds from turning on the PC on Solus. In fact it is the fastest boot up experience I have ever experienced including Windows. so 60-100 seconds do sound extremely high to me. If you are using a VM then I don't know though. Ran other distributions on VMs but never Solus.

                      • [deleted]

                      • Post #12
                      • Edited

                      Startup finished in 12.694s (firmware) + 512ms (loader) + 893ms (kernel) + 1.533s (initrd) + 1.069s (userspace) = 16.703s
                      graphical.target reached after 817ms in userspace

                      dostana Make sure your fstab is alright. Also if you've got multiple distros make sure your swap partition's UUID hasn't changed.

                          Yeah, 60-100 seconds is way too long. Even my old Frankenstein system (thankfully now retired) booted faster than that with Solus.

                            Staudey

                            I think it got fixed by a surprise. Re-installed though not a right way to do so had to install other applications. Need to be too careful here as Software Center opens a lot of tools too tempting to try look alike tools then end up into a mess.

                            hope this is fixed & considered solved but need to keep all options on table.