I took the new Zorin version (17.2) for a test drive before installing it my mom's tablet (ASUS EeeBook). It worked well, so I installed it from the thumb-drive. No dual-boot option, no fancy specifications.
I allowed the installation program do its recommended checks and there were no issues.
During installation, I got the following error message (in a pretty red window): "Executing 'grub-install/dev/mmcblk2' failed. This is a fatal error."
Upon reboot, without the thumb drive, I go directly to the BIOS set-up screen (yes, I had disabled the Secure Boot earlier; but I cannot find the Fast Boot feature??). Nothing appears unusual there.
This also happened after my 2nd installation. During this installation, it asks me if I want a 2nd partition separate from the Zorin 17 partition already installed.
If I leave the Thumb drive in the USB port, I can test drive or reinstall (thus my previous point). If I test drive, all seems to work as it should.
From the test drive desktop, I ran the "Boot Loader" Utility as suggested elsewhere (Repair the Boot Loader - Zorin Help). It was unable to correct the issue.
From the Boot Loader, I did download a system snapshot and error listing, found here: [Ubuntu Pastebin] (Ubuntu Pastebin)
This listing probably tells me exactly what i need to fix, BUT I don't understand it.
Can anyone hold my hand and help me out please? A little knowledge is a dangerous thing and I have reached my limit.
Thanks, JT. 20/04/2025
From what it looks like to me, Ubuntu 20.04 (And therefor Zorin OS 16) include the 32bit EFI bootloader.
In Ubuntu 22.04 (Zorin OS 17), this was removed by Canonical, likely due to continued dropping of 32bit support. That, however, is fallacious, since the architecture of the bootloader is not necessarily the same as the Operating system.
To correct this:
Boot using your Live USB on the computer you installed Zorin OS 17 to.
In the LiveUSB, enable networking, open a terminal and run:
Other options include using MXLinux or Linux Mint, which do still contain the grub-efi-ia32 package, despite Ubuntu taking it out. (Mint put it back in and MXLinux uses a different non-Ubuntu base).
Thank you for this.
I will wait until tomorrow morning to see if I can implement (strike that, understand and implement) your instructions. A night's rest can only help.
After running that command (looked like English to me at the time), I got:
"Some packages could not be installed. This may mean that you requested an impossible situation......
The following packages have unmet dependencies:
shim-signed : Depends : grub-efi-amd64-signed (>= 1.87.2~) but it is not going to be installed or
grub-efi-arm64-signed (>= 187.2~) but is not installable
E: Error, pkgProblemResolver::Resolve generative breaks, this may be caused by held packages."
.... so, proving once again that a little knowledge is a dangerous thing, I opened the file manager (correct name??). Clicking away furiously, I got to:
Computer (aka usr?)/lib/grub
In this directory, I see the following sub-directories (sub/directories?):
/i386-pc
/x86_64-efi
/x86_64-efi-signed
as well as the following 2 files:
grub-mkconfib_lib
grub-multi-install
That first sub/directory looks close to what it's looking for, so when I open it, I see a whack-load (sorry, technical finance term) ending in *.mod.
When you see a sequence of commands the following commands most often depend on the previous commands successfully running.
In your case, the first command failed. At this point, we stop entering commands due to needing to address that before proceeding.
You got that error that it does not exist - because the install failed, causing it to not exist on your computer.
Secure boot must be disabled in your BIOS Settings.
Secure boot is incompatible with the grub-efi-ia32 package - Microsoft has not and will not sign off on it.
After Disabling Secure Boot in the BIOS, load the system again as before and
remove any files that may have installed before proceeding:
There were a whole bunch of error messages after the purge command, but I went to this one anyway. Needless to say, error messages again.
I will shut down (full power off) and reboot w/o the USB stick. If that doesn't work, I'll redo the test drive boot.
Stay tuned! JT
I will await an update. eMMC is something that has partial support in GnuLinux. We will try, but in the end - you may need to install an Earlier Distro than Zorin OS 17 that retains 32 bit efi support in its .iso.
Update: No go; same old, same old. Just pops me back to the BIOS menu.
I see Zorin still has version 16 available, but if you have the time & patience, I am willing to try GnuLinux.. because who wouldn't??
If I have to go to Version 16 (which is fine, Mom just uses her tablet for iNet and messages), would we run into the same issues if I updated to Ver 17 from a running V16? (Academic question only at this stage)
With a bit of work and by manually locking in the 32bit efi stub, it could be done. But I would recommend against it.
Zorin OS 17 is set by default to recognize only 64bit efi.
That Zorin OS includes later firmware and kernels, also may cause more headaches.
So while it may be possible, it might also just bring new headaches and it may not last.
It also may be possible only in principle, and still fail.
I suspected as much, but curiosity always wins out.
Should we try the GnuLinux thing?
If I do go V16 (assuming no good Gnus), I will need clear direction on avoiding accidentally updating to v17 (or newer). It's never as easy as one hopes, is it? JT
There is no harm in testing installing Zorin OS 16.
Do not worry about accidentally upgrading. That is a rather long and drawn out process facilitated by use of a Specific Tool - the Zorin OS Upgrader Tool.
It has several checks along the way. And... you could just uninstall that tool.
Took a while last night, then I went out of town for the day. I'm b-a-c-k now and tried to install Zorin 16.3 once more; sticking to the installation defaults.
I get to the "Who are you?" (woo hoo, woo hoo ... Sorry, channelling The Who) screen. Put in Mom's name: "MT Toupin", accept the default Computer Name: "MT-X205TA" and default User Name: "mt" .
If I input a fair password ("fiston.12" for example) the screen doesn't allow me to hit "Continue" (i.e. it's greyed out).
Same effect if I select "Log in automatically" w/o a password.
At this stage, my only way out even after waiting a lllooong time is to hit the power button- even the "three-finger salute (Ctrl-End-Del) doesn't work. That doesn't power off the tablet, but does bring the "Back" button to life and it takes me back to the "Where are you?" screen, though now it thinks I am in Newfoundland rather than Alberta (at least it still has the right country). Reset the time zone, hit "Continue", repeat whole "Who are you?" scenario described above.
So, what gives !?!?!
Thx, JT (If we don't get it tonight, you'll not hear from me for a few days, as I will be driving home on Thurs. Bringing the infamous tablet with me because I am a glutton for punishment. jt) Man, I wish I knew what I was doing!!!
A screenshot might help. You might be giving your attention to the password, but there likely is something else there that needs an entry that you are missing.
jt