Hi

I thought you might have booted from flashdrive as you stated "file not found" when using:
Yet, uname returned
Re: The fast scrolling text. I do think that this actually is the same as the video. The guy there was running Linux in a virtual environment which will be much slower.. but don't worry about this for now.

Re: The 5.2.6 kernel. At the moment, this is the default kernel.. unless the boot delay is set to zero, you should get the Grub menu.

You could try this: Install grub-customizer as you did earlier (from the PPA). Run it when it's installed and set an earlier kernel as the default.
In "General Settings" under "visibility", check that the "Boot default entry" is set to 10 seconds and that "Predefined" under "default entry" is set to "first entry".

Now reboot to the earlier default kernel. Run ukuu and uninstall kernel 5.2.6 completely. Now reinstall it.

How are you running ukuu ?

Try running ukuu-gtk in a terminal as root. Keep an eye on the terminal as the kernel is installing. Look for any messages involving "cannot find.." or "cannot delete" etc. If I see these I cancel the installation and start it again. The second time normally works fine. I think that comes from link error to the Ubuntu site.

I'm going to be busy for a couple of hours.. I'll check here when I can.

Bodge99

Hi,

Re: The grub.cfg backup.. I'll explain more fully later..

Bodge99

When you boot and let the text scroll by, can you eventually log in, and if so what works and what doesn't?

[QUOTE=bodge99;6022011]Hi
I thought you might have booted from flashdrive as you stated "file not found" when using:
No, I was and still am running Mint from the eMMC drive.

OK, I shan't worry about it for now, although I would very much like to get that sorted out eventually, if at all possible.

I have not touched the boot delay, so theoretically it should still be at default, which something like 10 secs if I am not mistaken. But it is what it is, and I don't get to see it.

No !!! I don't want to do that as it is really advised against:
You can read the full article here: https://easylinuxtipsproject.blogspo...ustomizer.html
Is there any other way?

I have it installed on the eMMC. I looked at the settings and there is an option to set the Grub menu timeout. The check box was empty, so I checked it and set the time to 10 secs, shut down the computer and did a cold boot. The menu did not appear and it went into the flashing logo/text vomit endlessly, I eventually forced the shutdown.

After letting the computer sit I powered on again, and got the Grub menu. Advanced options, clicked on 5.2.4 generic. Unfortunately it went into the flashing logo/text vomit endlessly again, so I eventually forced the shutdown.

I let it sit powered off again for a few minutes, powered on, got the Grub menu, clicked on 5.2.4 and it booted into Mint. I removed 5.2.6 with UKUU.

1. It seems to me the flashing logo/text vomit endlessly indicates a loop it cannot break out of to go to the next step of the boot process, although sometimes it does, given enough cool off time, or so it seems.

2. What is the advantage of trying to force 5.2.6 to work? In my modest opinion, I think I should forget about 5.2.6 and stay with 5.2.4.

No, I cannot log in, I have to force a shutdown.

What I have noticed is when the text scroll does stop and it boots into Mint, the Super key works in that pressing it brings up the menu. In the menu I can use the search box to find an app/setting. But when I put the computer in Suspend, then bring it out of Suspend the Super key does not bring up the menu, that can only be done by clicking on the LM logo in the bottom left corner, and the search box does not work anymore.

In fact, the keyboard does not work anymore after coming out of Suspend.

With the 5.2.4. kernel and after all the updates/upgrades and xfce reinstall are you still having this problem

Thanks for checking. No, I do not have that problem anymore.

If everything works with the 5.2.4 kernel, I would suggest using it for the time being.
The grub menu entry for each kernel, is there anything different other than the kernel version on the Linux line?

1 members found this post helpful.

You may recall the difficulty I had with getting AntiX off the eMMC, with (part of) the reason being that other distros I tried, incl. Mint, did not detect the eMMC card.

Bodge99 then found out by doing an experiment on a computer/tablet that's virtually exactly the same as mine, that the kernel in those distros was not up-to-date enough to be able to detect the eMMC, and that only a latest stable release as shown by UKUU would do the job. I picked up the latest from UKUU, but there have subsequently 2 newer versions: 5.2.5, which I missed, and 5.2.6.

But now that I have Mint installed on the eMMC, I wonder if the normal Linux line kernel would not work too.

BTW, not everything works with the 5.2.4 kernel: I have a post-suspense problem - see my comment #245. And that IS a serious problem.

Are you talking about kernel 4.15?Try it and see what happens

1 members found this post helpful.

add this to the Linux line of grub menuentry and see if it fixes the suspend problem

1 members found this post helpful.

Hi

Backing up grub.cfg:

Performing this is totally up to you.. The Grub tools don't automatically make a backup of the grub.cfg file.

Although it's quite easy to recreate the grub.cfg using the normal tools, it's not a one command operation if you cannot boot normally..

Consider this scenario: You've updated your kernel (either by using ukuu or by using the Mint kernel update tools..) Something goes wrong and you find that you now cannot access your Grub menu.

Now, O.K. this is normally very unlikely to happen on your main laptop, for example, or on any other "stable" computer.
If this was to happen, you could simply boot from a flashdrive and replace the current grub.cfg with your "known good" backup.
Simple to do and very quickly done.

At this stage, I'd view your Lenovo as "work in progress". You've made significant progress in getting Mint onto the system. It seems to be booting reasonably O.K. but it looks like it now needs a little "fettling".

This is solely due to the fact that the SOC/CPU and some of the associated hardware is slightly "non-mainstream" at the moment.
Your computer has slight hardware quirks that are down to the computer manufacturer's hardware choices and their specific design implementation of these.

I'll give a recent example:

When the Bay Trail SOC/CPU packages were first released, Intel released technical information that included a standard reference main board design.
The kernel guys added early Linux support using technical data from this "standard reference design" and other technical documentation to provide support by the kernel.

Of course, some manufacturer's deviated from the "standard", meaning that some parts of the hardware wouldn't work at all with the then current Linux kernels (audio, wifi & bluetooth are examples). Basically manufacturer hardware changes "broke" specific kernel support for some of the hardware.

Once these quirks are known about, kernel support can be improved. It often is, fairly quickly..

In other cases, particular hardware has to set up in a specific way to suit some of these hardware "quirks". Some changes can be viewed as "workarounds" and some become the "de facto" method for setting up this hardware properly.

We now need to look at the video configuration and tweak things to suit.

On cold boot, the firmware provides basic video hardware configuration. When Grub boots, the video hardware configuration may be changed.. (video modes etc.).
When the kernel starts, further changes **may** be made.. Finally, Xorg will auto-detect and apply settings that should work with your display..
All of these process should ideally "sync" so that the handover from one stage to another is totally seamless to the user.

I think it shows the good work that the kernel and Xorg guys do, as **most** of the time the whole process is just about flawless.

Bodge99

H,

I've just seen your last post.. The suspend problem **may** be down to this:
Some of the specific Bay Trail problems have been fixed in the later kernels whereas others have to be addressed by "workarounds".
I'd suggest that you try the kernel options as suggested by Colorpurple21859 . If these don't help then there are others that should..

Bodge99

It does not work: it does not get beyond the scrolling flashing text vomit stream.So that settles it. Bodge99 was right.

Hi,

Klaas, Re. post #244:
I understood that you had installed kernel 5.2.6 . As the command I gave returned "file not found" this meant that you had either typed the wrong command or that kernel 5.2.6 had not been properly installed. This could also be the reason why you couldn't boot kernel 5.2.6 .

Grub-customizer: I was aware that the utility make changes to the Grub config files. I agree that it would be much better if it didn't, but your linked article is a little OTT IMHO. Nothing in Linux is "set in stone". You have multiple copies of these files available to you anyway. They are on your flashdrive Mint installation and on your other Mint laptop. Grub is a standard set of packages in Ubuntu or Mint etc. You could **easily** replace these files using the Mint Software Manager or by using the apt tool in a terminal.

I use grub-customizer in Mint (I don't run any version of Ubuntu at all... personal preference reasons) as it is a useful, quick tool. I run Mint as I recommend it to new starters and my Wife and Daughter use it.

Ukuu and kernel 5.2.6: I'm of the opinion that your current installation of kernel 5.2.6 is incomplete. Uninstalling and reinstalling it with Ukuu would be the easiest and quickest way to find out..

By all means, stay with kernel 5.2.4 if you wish.. It's your computer after all.. Folk here are trying to help you by giving suggestions.. Some will work, others may not due to your specific hardware. With a great deal of these things, the quickest or only way to find out if something works or helps with a particular situation **is to try it**.

As I've said before.. It appeared that your reply to "cat /boot/grub/grub.cfg | grep vmlinuz-5.2.6" indicated the the specific kernel file "vmlinuz-5.2.6-050206-generic" was not contained within the searched grub.cfg . This **looked like** either the kernel version had not been properly installed or that your grub.cfg had not been properly updated.

Bodge99