• Support

  • X doesn't start after latest update

Ryzen 7 1700 and AMD Radeon 590 gpu
same problem here. If I hit ESC on boot, I can get 5.6.13-153 or 5.6.18–55 to display login screen, but after login, flash of desktop, then black screen, then CPU fan goes full speed. If I try to boot normally, or boot from lts kernel, I get blinking cursor, then odd rainbow line about an inch down the monitor, and then black screen and top speed cpu fan.
third time in a year and a half on Solus that an update has completely pooched my system. If no easy fix from this point, next OS I will install will NOT be Solus 🙁

kaktuspalme
Thanks for the info. I don't have any virtualbox packages installed so I assume this must be unrelated.

    @Drewfus Your issue sounds identical to the one presented in this thread. Look at my solution posted there please.

    If no easy fix from this point, next OS I will install will NOT be Solus

    That is neither helpful or productive. If my solution linked doesn't resolve your issue, you'll need to provide logs using same steps listed below.

    @camtron I'm afraid @DataDrake and I are gonna need to see some logs so we can look into your issue. Please log in via the TTY (steps provided in my comment) and do:

    1. sudo eopkg install haste-it
    2. dmesg | haste-it
    3. sudo journalctl --boot=-1 > log && cat log | haste-it
    4. sudo journalctl --boot > log-2 && cat log-2 | haste-it

    Provide the links (for dmesg output and journalctl respectively).

    Edit: Fixed commands.

      JoshStrobl I can neither get to gui, cli or tty/ssh into machine, and my boot drive is an nvme ssd, so I don’t have the option to even connect the drive to another pc I have to access the boot drive and edit it. I will attempt to access the drive by booting a live distro and doing it from there when I have the time. Thanks.
      I did not mean to disrespect the devs, but simply express my disappointment and frustration at the moment. My bad.

        camtron What GPU do you have? From what I can tell, there are a number of bus errors and no video devices are showing up.

            As requested in another thread I am also posting the logs here:
            dmesg -> https://hastebin.com/pupexugezu
            journalctl (1) -> https://hastebin.com/azubijuyul
            journalctl (2) -> https://hastebin.com/kedijosega (it reports cat: log-2: No such file or directory

            I must say I think this could be a hardware issue... I dual boot windows and while in Windows I experienced almost the same problem a few minutes ago. I opened up my laptop and cleaned the fans, but oh well... Hopefully the logs do shine some light on the problem.

            Thank you all for your help <3

            EDIT: just as a reference this was my other thread: https://discuss.getsol.us/d/4877-system-crash-after-jun-12-update

              AlienTux
              The listed command sudo journalctl --boot > log && cat log-2 | haste-it seems to have a typo.
              It should be sudo journalctl --boot > log-2 && cat log-2 | haste-it
              The > directs output from journalctl into a file in this case named log-2. Then cat will output the log-2 file and | pipes that to the haste-it command. Since the original used log instead of log-2 there is no file for cat to read from.

                  Just to try to rule out any sudden hardware weirdness, I tried booting a live Solus Gnome ISO and it started up fine.

                  Update:
                  After reading this thread I tried removing the LTS kernel manually by mounting the EFI partition and deleting the relevant files. It now boots up normally again. Hopefully this helps pinpoint the root causes.
                  Thanks everyone for your help

                  I actually also have an update. The problem I was having was that the screen would scramble and the computer would freeze: https://u.pcloud.link/publink/show?code=XZT4FOkZClAEnUub4hfeAcNlAQ8P4jXgs5By

                  I thought it could be the GPU drivers because of the update, but then it also happened in Windows (I dual-boot).

                  After some tinkering and almost crying I thought maybe the SSD, where both my Operating Systems are installed, could be damaged. I managed to run the BIOS diagnostics, but the issue happened there too. The problem occurred when the diagnostics tool was testing the memory so I thought maybe that was the problem. I took out one of my RAM sticks and it worked 🙂 I installed the second one (I swapped their positions) and now everything seems to be working fine.

                  All in all I'm still not entirely sure this was the problem, but so far so good.

                  internal bios batteries and memory seating are 2 big problems (any addon card that plugs in for matter of fact falls into the same category) or the fingers need cleaned reseating can fix temp but sometimes doesnt last Dont just clean with anything ppl overlook alot when they throw away a computer that doesnt work.lol both are cheap to fix. (I just fixed an apple g5 that had memory seating problems runs great was free..lol) Prob should run memory test just to make sure (30 year tech) I would suggest if they need cleaned a good comptuer shop would know if they dont run fast..lol