post the output of
and

Output:
Output:

Hi,

colorpurple21859:
Looks like the resume setting isn't there at this stage... I see what you're looking for here..

Klaas:

If I'm correct and you do indeed have a "squiffy" partition table then I strongly recommend wiping the drive.

Do you have any other external USB storage available?? Even another flashdrive of sufficient capacity would do.
You could sacrifice and reuse the upgraded Mint flashdrive if that's better for you.

I recommend this action for two reasons:

If the kernel can see three ms partitions then the firmware will see them also. Without disassembling your firmware, I can't categorically state that there is no interaction between the firmware and what it "thinks" is contained in these ms partitions.

A manual re-creation of your partition structure will **guarantee** that there is nothing "screwy" here.

What I propose is this:

If you have an external USB HDD that you use for Linux (with a Linux filesystem on it) then we can use this directly.
If you want to use a flashdrive then format it to EXT4 and copy the contents of the system and EFI partitions across. You don't need to copy the swap partition as we'll just recreate it.
I'll give info so you can boot from the flashdrive Mint installation.

Next, use gparted to create a GPT drive and to create and format the required three partitions on the eMMC drive.

Finally, copy everything back, set a few flags and alter the UUID's in the fstab and initial grub.cfg.

I think this has arisen from your early experimentation with creating partition types using AntiX..

I'll give a step by step list of instructions for you to follow if you want me to..

How do you wish to proceed?

Bodge99

The rootdelay is at the grub menu, press e for edit and add it to the line that starts with linux

That may fix the partition oddness seen during boot

I just tried, but the tablet does not detect the Mint flash USB drive. I tried the AntiX one, and it does detect it, so I don't know what is going on with the Mint one.

I am going to be busy with something completely different for the next few days so will not be able to spend a lot of time on this. Therefore, rather than doing it in a distracted way, I'd rather get back on this next week.

BTW, this new procedure to start from scratch, as I understand it, seems simple compared to what we went through over the past week. Out of interest: with the benefit of hindsight and 20-20 vision, could we have followed this proposed procedure 1st?

I would really like to implement this, but if you look at my comment #262 you'll see that I explained to Bodge99 that I cannot alter anything in that screen. Please read that comment.
Is there another way to get at it.

Wow, that would be great. Like I said in my previous reply to you, I cannot enter grub from its menu. Is there another way to access it e.g. from within Mint itself?

Hi,
Klaas:
This is the kind of totally misinformed rubbish that the Linux community has to endure.. (Not you.. the article!! I've seen this stuff before.).
I think what they are referring to is this. When Bay Trail hardware was first released, Microsoft couldn't come up with a 64bit UEFI firmware in time for the product launch dates. Yes, MS couldn't manage to write (or buy in) a tiny bit of code in time!! They forced the hardware manufacturers to use a 32bit UEFI firmware. This is why the early windows tablets etc. ran 32bit windows 8.

Of course you can run 64bit software on a Bay Trail.. You can even run a 64bit OS on a machine with a 32bit UEFI firmware.. I know this as I've done it!..

Bodge99

I think it is /boot/grub/grub.cfg but not for sure
or at the grub menu press c for a grub prompt

Klaas:

Sorry, I edited post regarding booting the Mint installed flashdrive.. Of course.. there is no populated EFI partition. Sorry for the confusion.

Bodge99

Hi,

I see what colorpurple21859 is looking at.. I don't think that a boot delay will affect how the kernel sees the eMMC here.

You can add kernel parameters to the Grub configuration files from within Mint. If they happen to cause problems then you would have to bypass them from your Grub menu (which you cannot do yet) or boot from your flashdrive and edit files manually.

Bodge99

Maybe true, but I like to say afterward, "At least I know what it isn't"

Yes!! This!! Nice one!

Bodge99

for the resume problem Boot into your mint system open a terminal
[CODE]sudo touch /etc/initramfs-tools/conf.d/resume
sudo echo RESUME=UUID=de9d2a53-48e1-43d7-b6e2-ddc5e3e9d5cf >> /etc/initramfs-tools/conf.d/resume
sudo update-initramfs -u
reboot