Re: [orca-list] Slint Demo/Tutorial, Part 2: The Post-install--first steps



Now that I think about it again, I am unsure if you booted (or tried to)
the Slint installer in EFI mode or Legacy mode. Anyway I suggest that
you tried the other mode, whichever it was.

As an aside, when a Linux system is running this command:
ls /sys/firmware
will tell you in which mode the machine runs: if there is "efi" in the
output it's in EFI mode else in Legacy mode.

Best,

Didier

On 16/10/2019 00:36, Didier Spaier wrote:
Hello,

On 15/10/2019 02:34, Andy Borka via orca-list wrote:
Sighted help told me that when the image boots, the diagnostics/recovery system tools appear. We get put into 
a 'file explorer' type window that simulates Windows 10's file explorer. In this window is an error code that 
is larger than 128 characters long. Directions on the bottom of the screen tell us to use up/down arrows to 
select an option, then press ENTER to make a choice. Press F10 to enter BIOS, and press F2 or press the power 
button to restart normally. Pressing ENTER on this rather large error code results in a Linux terminal window 
with the prompt:

<EFI>


I didn't explore much past that because I didn't want to break something.


Indeed the installer should be able to boot in either both EFI and Legacy mode.

Here is the boot manager contents...

Boot mode is EFI

Choose 1 from the list below.

Ubuntu 19.10

EFI USB drive


>Secure boot is not provided by the Slint installer as is.
It shouldn't make that much of a difference because I have SB turned off in BIOS. However, is the system 
looking for a kernel that at least supports it?

Which system? the BIOS no, a you said, neither GRUB. So, no.

>Did you check the integrity of the ISO image with its sha256 checksum as indicated here:
Everything checks out as expected.

>Do you have other system(s) installed on this machine, and which one(s)?

Ubuntu 19.10


>Do yu know the exact model (number) of this machine, and its firmware?
No.

If possible please send me privately pictures showing the errors displayed by the BIOS and itd various menyu 
(especially the Settings that you probably display pressing F10, and the Start menu if separate).

You could try this:
1. But the BIOS (aka the firmware) in Legacy mode (not EFI)
2. Try to run the Slint installer. If that works, do not install GRUB from the installer when asked (we will 
reconfigure GRUB from Ubuntu later, see below)
3. When all installation and configuration steps of Slint are performed, reboot.
4. Probably you will need to put back the BIOS in EFI mode to boot Ubuntu as its installer installed GRUB 
only for this mode.
5. From Ubuntu, re-configure GRUB (probably typing "grub-mkconfig -o /boot/grub/grub.cfg" or just 
"update-grub"). If all goes well it will find Slint and add stanzas for it in the GRUB boot menu. Probably Slint will 
be after Ubuntu in this menu.
6. Of all that succeeded you should be able to boot either Ubuntu or Slint (I assume that's what you plan to 
do. Please confirm).
7. Please let us know the outcome

PS Uploading now in the Slint repos and should be available in a few hours, as I wrote in the ChangeLog:


Wednesday 16 October 2019
bluefish-2.2.10-x86_64-1slint: Added.
  GTK-based HTML Editor
libreoffice-6.2.7-x86_64-1slint: Upgraded.
locales/libreoffice-help_<locale>-6.2.7-x86_64-1slint: Added/Upgraded
   65 packages (help packs for LibreOffice)
locales/libreoffice-l10n_<locale>-6.2.7-x86_64-1slint: Added/Upgraded
   115 packages (language packs for LibreOffice)
locales/mozilla-firefox-l10n-<locale>-52esr-x86_64-1slint: Removed
   51 packages removed. These language packs do not fit the Firefox
   version currently shipped and language packs can be installed from
   the Preferences GUI of Firefox.
tintin-2.01.91-x86_64-1slint
   Console MUD client
   The executable is /usr/bin/tt++
   Cf.:  /usr/doc/tintin-2.01.91/docs/help.html

Thanks for the suggestions/requests <smile>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]