Chances are it's failing to load the virtualbox kernel module since it's now included in the ISO. It won't prevent system booting though, it should just load the module when Solus is the guest.
Solus 4 Budgie Live USB Fails
I ran the command in the last screenshot (journalctl) on the live media and I am not seeing the same thing but even after i install a working (on the machine) 3.99 Mate ISO and update lightdm ... i am stuck on the login screen on my old 2003-ish era desktop ... I was going to (why i am posting this here vs making a new thread) just wipe and install 4.0 but i can only get to a text login with that too .. though i am not having it go to a "blank cursor" issue ...
Tried using the 3.99 ISO (install + Recommended + security updates + even the kernel and xorg updates = still getting to a GUI) ... I KNOW i left the lightdm update unchecked.
NOT intending to hijack this thread, but I am noticing recent issues on my old machine related to lightdm too
- Edited
Yeah, I have a very similar issue to cerebrix and @Ricofizz: the GUI will not work. However, I'm running on integrated Intel graphics and apparently lightdm is running when executing systemctl status lightdm, but it sometimes appears that it failed when executing journalctl -b. I made a thread about my dell not booting to this update, but unfortunately it was marked "solved" as soon as I encountered the problem again.
Output of systemctl status systemd-modules-load.service
Islandscout yeah man. I'm not sure anyone that can help is paying attention to this thread. It sucks, but it is what it is I guess. My hope is they sort this out and push out another iso later.
That's the toughest part. small community distros really don't have a ton of people that get off on "closing tickets" so to speak when it comes to volunteer tech support. That will get fixed eventually. I just wish that it was sooner rather than later. But I still bump into threads on reddit that seem to think this is an abandoned distro when it isn't. So I guess I can't be surprised.
And while I really don't know how many techies Solus dev group has, they still do a good job (at least based on what I see). However, you gotta also remember, they're catching their breath after releasing a milestone. It's been REALLY busy here since Sunday.
dbarron I get it. Like it said, it is what it is. Honestly they really shouldn't even be dealing with stuff like this and just focusing on their work. But like I said before, on big distro, this is a problem solved by tech support nerds that just love "closing tickets".
I'm patient. I'll give it a few months I guess.
anyone has found a solution yet? I really like solus and would like to go back to it. Well atleast I know next time to go Amd... guess I have to wait for 3 years before my 1080ti is useless against the high end of amd..
- Edited
I want to add a workaround to this bug. Really easy,
So when u boot up the live usb and u go get the black screen, just tab the power button once as if u would put it into sleeping mode... the pc/laptop will go to sleep.. Just press again once and it will go out of sleep.. For some reason this gives us the gui fully loaded.
Other discovered, I couldn't install or format my partition of the ssd i wanted to, so instead of using disks use it in gparted and format whole disk at once.. and afterwards I could just install it easily ( however when I had my other hard drives attacked with windows on it solus refused to put the bootloader on the ssd I was gonna install it to, so I turned of the computer, removed the windows hard drive, boot back up and do the "suspend and back awake" and then it had no problems for installing the bootloader also on the ssd.
I hope atleast some people were helped with this.
Have fun guys.
- Edited
the solution is to write the ISO to the USB in DD mode, not Iso mode, but seems current version of Rufus doesn't support Solus, from windows i used USBWritter app my post about the same topic [SOLVED] ... downside of it is that it installs the vbox modules on your host ... it basically copies the entire ISO setup on to your host, and you will have failed load kernel modules in the journalctl until you uninstall them ... overall a great distribution, but in my opinion 4.0 wasn't tested enough as there are quite a few bugs I have found, related to chrome, graphics breaking, the usb iso issue, etc ...
KronikPillow
Hmm, in my case i also got the vbox stuff its just that after it loads it stood at blackscreen, not even tty didnt give anything, unless i usee nomodeset first.
I used gnome multi writer, fedora usb writer, suse image writer.. all did the same.
I stumbled on a workaround per accident while I was trying to hold power button to shut it down but instead just clicked and put it to sleep. I did tap it again and voila instead graphics fully loaded.
I then tested this a few times more to check and it worked this way.
KronikPillow Have those issues been reported?
Johandherdt I never use anything but dd and have never had an issue. Granted it's command line and not for everyone. Someone needs to write a super simple dd interface.
As scary and dangerous as it can be, dd is actually pretty simple, source and target devices, maybe block size, good to go 
- Edited
I signed up to the forum because I may have a fix/workaround for everyone.
From my reddit post:
UEFI/GPT- Alright people.. I purposely broke my first successful install and ended up installing another distro and I just now reinstalled Solus. I decided to take note of the steps I took in hopes it helps others. These are the steps I followed for my set up (intel i7 6700, Gigabyte MOBO, SSD and HDD, and nvidia1050ti)
- â I backed up most of my data and installed Rescatux on USB.
- â Repartitioned everything to GPT using gParted in Rescatux.
- â Went into BIOS, disabled CSM under Windows 8/10 support.
- â I enabled EFI for boot and other devices.
- â I then changed it from Windows 8/10 to Other OS. All options under OS disappear. Save and exit.
- â On BIOS Splash, go to boot options (F12 in my case) and select the usb that Solus is installed on.
You should now be greeted by the Budgie desktop in its full glory. I hope this helps anyone still stuck with this.
BIOS/MBR
Update: Legacy BIOS (MBR)
To boot from USB, I flashed the Solus iso using Rufus in iso mode (didnât work for me in DD).
I pressed TAB as soon as the splash screen counting down appeared.
I deleted the words quiet splash while keeping everything else intact
In that same line I typed nomodeset [nomodeset â]
Once at tty login screen type root for user and root for PW.
At command prompt type sudo eopkg upgrade.
Once the updates are finished press CTRL, ALT and F7 at the same time.
You should now be in the live USB environment and be able to install Solus from USB.
cheers!
PS. Im a Solus newb but lifelong nerd, I like breaking things.
Copypasting this from reddit for 1660Ti users:
Heres how i made it into live desktop with 1660Ti:
Ctrl+alt+F2 into login prompt when you get blinking underscore screen
Login with root/root
eopkg it nvidia-glx-driver-current
systemctl start lightdm
Now you should have desktop
You have to do same again after install but instead of root use your user/password and forget systemctl command just reboot for convenience
jayrivii
EDIT: IMPORTANT! BIOS/MBR -ONLY
Once done with the above you have to update your drivers. Otherwise you will see a black screen after installation.
Once at boot menu and type e.
Find the last line referencing the kernel and before the part that mentions root, type nouveau.modeset= 0 then CTRL + X to boot.
Once at tty input the username and password created during install. Then type sudo eopkg it nvidia-glx-driver-current and reboot.
cheers!
aalhitennf this worked for me on UEFI. The only difference for me was that lightdm would not start. I ended up going with sudo eopkg upgrade and rebooted.
jayrivii thats probably because problem is slightly different because you have 1050Ti (1660Ti is newer Turing architechture and not yet supported by nouveau or kernel at all), but glad to hear you got it solved.