Newly installed UbuntuMATE 18-04 does not boot
dreadpiratejeff at gmail.com
Tue Jun 12 19:42:35 UTC 2018
On Thu, Jun 7, 2018 at 4:20 PM, Bret Busby <bret.busby at gmail.com> wrote:
> On 04/06/2018, Ralf Mardorf <silver.bullet at zoho.com> wrote:
>> The first steps of troubleshooting could be
>> 1. Run a LINUX from a live media, e.g. an Ubuntu Mate 18.04 live DVD,
>> by choosing the option to test Ubuntu Mate without installing it.
>> 2. After the session started, open a terminal.
>> 3. Run
>> sudo gparted
>> 4. In the right upper corner of the gparted window is a selection box.
>> Select one drive after the other, perhaps you could see, that
>> something already is installed.
>> 5. Run
>> 5. Mount all partitions, caja does provide mount options, but you not
>> necessarily get access to all directories, since the live DVD default
>> user might have UID 1001 and the /home/* of the installed user might
>> be owned by 1000, but there's no need to access /home/*. However, if
>> you want to acess it, run
>> sudo caja
>> sudo -i
>> and take a look by using command line only.
>> If you should see an installed Linux, e.g. run
>> cat /media/u*mate/*/etc/os-release
>> cat /mount/point/etc/os-release
>> the next step could be installing grub (not the packages, but the bootloader
>> to the drive).
>> ubuntu-users mailing list
>> ubuntu-users at lists.ubuntu.com
>> Modify settings or unsubscribe at:
> I have (I think) found the answer (by accident).
> This new and weird(-ish) computer has the means within the BIOS
> settings, so, I set the boot order in there, and (in the first
> instance, anyway) it seems to work.I have not encountered that before,
> where the boot sequence of the installed operating systems, is set and
> controlled within the BIOS (on a UEFI machine).
All EFI systems work like that. The OS installer, in general terms,
writes its bootloader somewhere and then writes an EFI boot entry into
the EFI tables. Then when the system boots, EFI loads (EFI is a whole
OS environment based on TianoCore) and presents the boot options it's
aware of or has scanned, you choose an option or it times out and
executes the default, EFI unloads and hands off to whatever boot
option you've chosen, be it an on-disk boot loader like Grub or
Windows Loader, or the Network card for a PXE boot, or to boot the
When you set those things in the System Settings, you're likewise
modifying the EFI variables that the OS installers write to.
BIOS has been deprecated in favor of EFI and while there are still
millions of devices that support both, within the next 10 years pretty
much anything sold will be EFI only.
If you're multi-booting, by the way, I'd suggest installing rEFInd and
using that to write the EFI options. http://www.rodsbooks.com/refind/
Here's also a decent explanation (long-winded, though) of EFI and how
it works: https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/
> Bret Busby
> West Australia
> "So once you do know what the question actually is,
> you'll know what the answer means."
> - Deep Thought,
> Chapter 28 of Book 1 of
> "The Hitchhiker's Guide to the Galaxy:
> A Trilogy In Four Parts",
> written by Douglas Adams,
> published by Pan Books, 1992
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
More information about the ubuntu-users