OK, I am willing to try it, but what is the advantage?

I am sad to read a line like that. I have been extremely grateful for the bespoke support you have been giving me, AND the time you invested. I did not want to give the impression I am dismissive; if I ask questions or have a different opinion is because I am trying to understand and learn. I don't even reach your ankles in terms of expertise so I would not allow myself to be smarter than you, a real Linux guru. I sincerely apologise for any misunderstanding.

OK, I'll give it a try.

BTW, I have had to suspend the computer because I needed to step away from it for a while. I have not been able to get it to cold boot into Mint for the past 3 trials, with long minutes between each trial. The text vomit won't stop.
1 positive point: the process does start by showing the Grub menu. Nevertheless, if I don't click on that 1st line in there, it stays on the Grub menu. I know that's not a problem because that can easily be set in the relevant file.

If the same lines of text are repeating, post them.

Yes, they seem to be the same lines, although I cannot read them; I think I could make out FUSE, RFkill, Journal service, ...
How do propose I copy the lines? The text flashes past and there is no cursor.

Thanks for the suggestion. Can you tell me exactly where to add the line you suggest?

Hi,

There may be improved support with a newer kernel.. Without checking the relevant changelogs on https://www.kernel.org/ and any specific Ubuntu changes on https://kernel.ubuntu.com/~kernel-ppa/mainline then the only way to find out is to try it. It's certainly possible that a newer kernel may cause specific problems for you.. A fix or other kernel change for one piece of hardware may have unintentional effects elsewhere. Changes may be reverted if too many people complain..

I certainly don't think this at all.. I do appreciate the difficulties here. I'm also concerned that some of things that I write might be interpreted in the same way. Nothing could be further from what I intend.

The next time the computer boots successfully, could you do this:
If you could attach the file here (it will be quite large) then I'll be able to look at what the kernel is "seeing".

With "looping text", you might have a virtual terminal available..

Try pressing the three keys Ctrl+Alt+F1 (or Ctrl+Alt+F2 etc.) simultaneously. If VT's are available, you'll be taken to a full screen terminal.
You can login here and perform normal terminal actions.. Use Ctrl+Alt+F7 to return to your previous location.
VT's can be useful if Xorg locks up totally and you want to enter "poweroff" manually.

Bodge99

Hi,
I'd suggest **not** adding this as a default addition to your Grub configuration **yet**.
At your grub screen, press the 'e' key to enter edit mode. Now cursor down/across to the line beginning:
At the end of this line, add the suggested kernel parameters, exactly as given.
Make sure that there is a space between the last existing character on the line and what you add.

When you have finished, just press F10 to boot.

These extra kernel parameters are not permanently added to your grub.cfg . They are only used for this boot only. This is a useful way to test potentially useful kernel parameters.

Bodge99

Without wanting to make changes at this stage, as per your instruction, I nevertheless wanted to have a look at what I would be presented with if I pressed "e" - a newbie's curiosity.

I saw code, and indeed the line you mentioned. But at the top of that screen a continuous flow of ")" had started, and when I pushed the down arrow on my keyboard that flow just jumped to the next line and continued.
I forgot to press CTRL+ALT+F1/F2 ..., so I shut down the computer with the power button.

BTW, that was when I was still with kernel 5.2.4. I managed to do a cold boot into Mint (wow!) with kernel 5.2.4, but today there is a new version, 5.2.7, which I installed subsequently.

Like I said to you in the previous reply, today there is a new kernel version again, 5.2.7, and I installed it while on 5.2.4. I then managed to boot into Mint with the new kernel!!
So I have attached a dmesg file of 5.2.4 and one of 5.2.7.

BTW, the post-suspend problem with the keyboard is still there with 5.2.7.
With 5.2.7 I managed to do a cold boot into Mint after a shutdown following the post-suspension keyboard block. I did let the computer sit with power off for 30 mins. Yesterday evening I could not get it to cold boot into Mint with 5.2.4 and only a 10 min. pause. So, perhaps I am not quite comparing like with like, and in any case one should not have to wait for more than say 10 secs between 2 cold boots.

Attached Files

	dmesg4.txt (50.9 KB, 14 views)
	dmesg7.txt (50.9 KB, 10 views)

Hi,

Thanks for the dmesg.txt, very useful..

I've had a quick scan and noticed something strange:

At around 2.89 seconds into the kernel boot the eMMC card is detected. The kernel then detects mmcblk0boot0, mmcblk0boot1 and mmcblk0rpmb .
The first two are related to microsoft secure booting and the last is the replay protected media block (don't ask!!).
These partitions are used with windows 8, 8.1 or 10.

Can you run gparted and see exactly what partitions are shown please..

Also the mmcblk0p1 is shown as requiring a filesystem check. This will be from the forced poweroffs.. Don't worry too much about performing this check just yet..


Bodge99.

Today, I managed to cold boot into Mint, and after a while I shut down the computer via the Menu because I wanted to see if I would shut down without suspending 1st, the computer would cold boot into Mint after a waiting time of some 10 secs.

Well, it did not, the text scrolling continued, but after a while on the lower half of the screen the scrolling stopped, showing the text. I managed to take a photo, which you'll find in the attachment. Hopefully that helps.

Attached Thumbnails

 

See attachment. Also look at my previous post with a screenshot of the scrolling text during booting.

Attached Thumbnails

 

Hi,

Thanks for the images.. The picture of the text at start up seems to be from systemd. I'll look into this later.
The gparted picture indicates that you have the expected three partitions (EFI, system and swap) for a standard Linux installation.
BTW, just ignore the filesystem labels.. you can rename these if you want to.

Can you try this please:
Boot from your AntiX flashdrive and run gparted.. Do the ms partitions show here?

It's possible that the partition table is a "little screwy" at the moment. These other three partitions shouldn't be listed anywhere as they shouldn't exist.
I've seen Bay Trail firmware act a little weird if these partitions are present, even with secure booting disabled.

If these ms partitions exist (even with an "iffy" partition table) then this could account for your booting problems. I think we need to sort this next.
I'm going to be away for about 4 hours shortly (It's currently 10:10 local time here).

More later..

Bodge99.

They do not show up, but for completeness' sake I have attached a screenshot - antix1.
There is also an sda1, even when AntiX was still installed, and it's a fat16 partition - see screenshot antix2.

Following this comment I quickly googled Bay Trail and saw an article about the Bay Trail CPU not being able to support 64-bit apps and not even Linux. MS supposedly provided a patch for Windows. Left me scratching my head, so I decided to leave it to the real expert ;-)
BTW, you know I had Win 8.1 64-bit installed on the tablet, although it was a version for the tablet, I think.

Attached Thumbnails

   

Add to the grub linux line see if that makes any difference

Sorry, which grub linux line do you mean? And where is the file?