elfprince including lots of skipped checks. So, something is wrong.
Pretty sure some skipped checks are normal in a chroot environment. Not 100% sure about this though.
elfprince By the way, is Virtual Box an essential/vital part of Solus OS? Why is it mentioned??
VirtualBox service configuration is a part of usysconf
's functions. Since running usysconf run -f
forces ALL actions to execute, even those that aren't indicated necessary by the usual checks, it of course also executes the VirtualBox action.
My partitioning was GPT for the entire disc, and so, following the Solus Help advice, I did not install via UEFI method.
Were does it say that in the Solus Help Center? The only similar info I'm aware of is the following:
"Legacy (BIOS) must use MBR partition table while Unified EFI (UEFI) must use GPT partition table."
which is almost the exact opposite advice.
Or do you just mean the step of creating a FAT32 EFI partition? (which of course you already have according to your first screenshot) Edit: Nevermind, those were just the labels set by you.
elfprince I wish the UEFI disk partitioning procedure was automated by the SOLUS Team, it is not for the casual/average home user to play with GParted.
Just to be clear, when you install Solus on the whole disk that process is entirely automated.
elfprince Specifying boot order in bios, or using F10 (boot order) does not help.
So selecting the disc with Solus on it just does nothing and it continues to boot from the Ubuntu disk, is that right?
elfprince Your command gave me an error:
/usr/sbin/grub-mkconfig: 275: cannot create /boot/grub2/grub.cfg.new: Directory nonexistent
Under Ubuntu you should be able to simply run sudo update-grub
, which should find the right files and directories automatically.