[SOLVED] Cannot replace AntiX with other distro

Klaas Vaak · 08-07-2019, 10:49 AM

Quote:

Originally Posted by colorpurple21859

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
sudo update-initramfs -u

reboot

After doing this, this is the output I got:

Quote:

update-initramfs: Generating /boot/initrd.img-5.2.7-050207-generic
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915
I: The initramfs will attempt to resume from /dev/mmcblk0p3
I: (UUID=de9d2a53-48e1-43d7-b6e2-ddc5e3e9d5cf)
I: Set the RESUME variable to override this.

What do I need to do?

Klaas Vaak · 08-07-2019, 11:08 AM

Quote:

Originally Posted by colorpurple21859

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

Code:

Linux (hd0,2)/vmlinuz root=/dev/mmcblk0p2 rootdelay=5 splash quiet
initrd (hd0,2)/initrd.img

Like I said, I cannot make amendments, neither with "c" nor with "e", in the grub menu from that initial black screen showing the menu.
I looked at the /boot/grub/grub.cfg file, and assuming it is a line or lines to be amended, I did not find either of them.

If they are lines to be added, you'll have to tell me exactly where to add them in that file.

BTW, should splash quiet not read quiet splash? And should there not be double quotation marks (") before quiet and after splash?

colorpurple21859 · 08-07-2019, 11:39 AM

go to the line that begins with menuentry that matches the grub menu entry that you boot, go to the line that begins with Linux below it and add the rootdelay=5

colorpurple21859 · 08-07-2019, 11:48 AM

Quote:

What do I need to do?

nothing for this, that was just informational text.

bodge99 · 08-07-2019, 01:19 PM

Klaas: You've done all of this before.. You shouldn't have any significant problems.. Just ask if anything is worrying you.

Worked example: Recreate a clean partition structure without losing anything:

I'll assume here that you are going to use a flashdrive for this:

Prepare flashdrive: Perform this action from your main computer:
Insert flashdrive and run gparted.
If there are any partitions shown, right click on each one in turn and "Unmount" (or "Swapoff" if there is a swap partition present).
In gparted, select the flashdrive. Now under "Device" click on "Create Partition Table". A partition table type of MSDOS is fine.
Click "Apply".
Under "Partition", "New" create an EXT4 partition for the capacity of the flashdrive (the default).
Under "Edit", "Apply All Operations" and click on "Apply" to confirm.. Let the flashdrive format.. and click on "Close"
Close Gparted.

Use your File Manager to find the allocated flashdrive designation. Hover your cursor over the flashdrive icon to see the flashdrive identity.
I'll assume it's sdb1.
In a terminal, as root:

Code:

mount /dev/sdb1 /mnt
touch /mnt/backuplocation.txt

The touch command creates an empty file in the named location.

At this stage you have prepared the flashdrive for use as your backup device. It is formatted EXT4 and you have created a zero length "marker file"
You'll see why I've done this later.
Now in your terminal, cursor up to the "mount ... " command
Cursor to the beginning of the line and add a letter "u" and press enter when ready. You are now using the bash shell command history.
The line should now be this:

Code:

umount /dev/sdb1 /mnt

This unmounts the flashdrive partition. Remove the flashdrive from the computer.

Backup the Leonovo eMMC:
Boot the computer from your AntiX flashdrive. When the system is ready, insert your backup flashdrive.
Find your backup flashdrive partition designation: I'll assume here it's sdd1. Use your file manager to access this partition and check that you can see the "marker file" backuplocation.txt . This proves that you are looking at the correct partition.
Open a terminal and, as root:

Code:

mkdir /mnt1 /mnt2 /mnt3
mount /dev/mmcblk0p1 /mnt1
mount /dev/mmcblk0p2 /mnt2
mount /dev/sdd1 /mnt3

Here, the eMMC EFI partition is on /mnt1. The eMMC system partition is on /mnt2 and the flashdrive partition is on /mnt3

Code:

cp -a /mnt2/. /mnt3/              
mkdir /mnt3/myEFI
cp -a /mnt1/. /mnt3/myEFI/
umount /mnt1 /mnt2

Ignore any "permissions" warnings..
Here, we've copied the system drive (mmcblk0p2) to the flashdrive. You then created a directory in which you have placed the contents of the eMMC EFI partition (mmcblk0p1). Finally you've unmounted the two eMMC partitions.

Wipe and recreate eMMC partitions:

Run Gparted. Select the eMMC drive and in turn (as before), ensure that each partition is unmounted (use "swapoff" if required).

Now under "Device" click on "Create Partition Table". Choose a partition table type of GPT.
Click "Apply".

(Sizes are approximate, I've just used the sizes from your gparted screenshot of your existing layout.)
Under "Partition", "New" create a Fat32 primary partition 255MiB in size. Click on "Add"
Under "Partition", "New" create an EXT4 primary partition 26.84GiB in size. Click on "Add"
Under "Partition", "New" create a Linux-swap partition using the remaining space. Click on "Add"

Under "Edit", "Apply All Operations" and click on "Apply" to confirm.. Let the eMMC format..
Now click on "Close".

Now Right click on the Fat32 partition and select "Manage Flags". Here, select "boot" and "esp" and click on "close". The boot flags are now set.

Close Gparted.

Create a list of your UUID's:

Code:

blkid | grep mmcblk0p > newUUIDs.txt

This file will be created in your current working directory.

Copy everything back:

Code:

mount /dev/mmcblk0p1 /mnt1
mount /dev/mmcblk0p2 /mnt2

Your backup flashdrive partition should still be mounted on /mnt3 .

Code:

cp -a /mnt3/. /mnt2/
cp -a /mnt3/myEFI/. /mnt1/

Ignore any "permissions" warnings..
**Remember to delete /myEFI and contents when the system has booted.**
At this stage, you have copied back everything to the system and EFI partitions.

Modify configuration files:
If you want to use xed, start it from another terminal with

Code:

sudo xed

Inital grub.cfg: Currently at /mnt1/EFI/ubuntu/grub.cfg
Change the UUID to the new UUID of mmcblk0p2. Copy & paste from the newUUIDs.txt file.

Sample /mnt1/EFI/ubuntu/grub.cfg

Code:

search.fs_uuid {your mmcblk0p2 UUID here.} root hd0,gpt2 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

Replace the main grub.cfg (currently at /mnt2/boot/grub/grub.cfg) with

Code:

insmod gzio
insmod part_gpt
insmod ext2
menuentry "Mint 19.2 update me" {
        set root='hd0,gpt2'
        linux   /boot/vmlinuz-5.2.4-050204-generic root=UUID={your mmcblk0p2 UUID here} ro $vt_handoff
        initrd  /boot/initrd.img-5.2.4-050204-generic }

Use the kernel version that you are most happy with at the moment.

Modify fstab: Currently at /mnt2/etc/fstab

Code:

# / was on /dev/mmcblk0p2 during installation
UUID={Your mmcblk0p2 UUID here} /               ext4    noatime,errors=remount-ro 0       1
# /boot/efi was on /dev/mmcblk0p1 during installation
UUID={Your mmcblk0p1 UUID here}  /boot/efi      vfat    umask=0077                0       1
# swap was on /dev/mmcblk0p3 during installation
UUID={Your mmcblk0p3 UUID here} none            swap    sw                        0       0

Nearly there.. Now to add the resume settings: Thanks to colorpurple21859 for reminding me of this.
In your first terminal:

Code:

touch /mnt2/etc/initramfs-tools/conf.d/resume

Now edit /mnt2/etc/initramfs-tools/conf.d/resume and add the line

Code:

RESUME=UUID={your mmcblk0p3 UUID here.}

Save the file and close the editor.
The system should use the default swap partition for this automatically, but it's often a good idea to manually force this.
I don't use any resume functionality at all, but I appreciate that others do.

Now power down and remove any connected flashdrives.
Restart, and the system should boot from the temporary grub.cfg

Update Grub:
Open a terminal and run:

Code:

sudo update-grub2

Restart again, this time you have a fully updated grub.cfg.

Good luck!

Bodge99

colorpurple21859 · 08-07-2019, 02:00 PM

Quote:

Now edit /mnt2/etc/initramfs-tools/conf.d/resume and add the line

That is what the echo command suppose to do in post 285/286, must had a brain-fart when I posted 285 went back and edited it.

Code:

sudo echo RESUME=UUID={your mmcblk0p3 UUID here.} >> /etc/initramfs-tools/conf.d/resume

bodge99 · 08-07-2019, 02:09 PM

colorpurple21859:

Quote:

...must has a brain-fart when I posted...

Been there.. done that... ;>)

Bodge99

Klaas Vaak · 08-08-2019, 07:51 AM

Quote:

Originally Posted by colorpurple21859

go to the line that begins with menuentry that matches the grub menu entry that you boot, go to the line that begins with Linux below it and add the rootdelay=5

I looked at /boot/grub/grub.cfg, and at the top of the file it says that this file should not be edited. Nevertheless, if we are trying out something you might tell me to do so anyway as an experiment.

I have attached a copy to this comment, and please indicate where I should add the rootdelay=5 line, considering I am using kernel 5.2.4.

Klaas Vaak · 08-08-2019, 08:03 AM

Quote:

Originally Posted by colorpurple21859

That is what the echo command suppose to do in post 285/286, must had a brain-fart when I posted 285 went back and edited it.

Code:

sudo echo RESUME=UUID={your mmcblk0p3 UUID here.} >> /etc/initramfs-tools/conf.d/resume

I redid this command, and after the next command

Code:

sudo update-initramfs -u

this is the output

Quote:

W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915

Last time you said I don't need to do anything, but is that still correct? If something is missing should it not be added?

bodge99 · 08-08-2019, 08:10 AM

Hi,

Klaas: If you want to add kernel parameters to Grub then edit /etc/default/grub

At (around) line 10, you'll see a line then starts with:

Code:

GRUB_CMDLINE_LINUX_DEFAULT=

Add your kernel options at the end of this line, after the existing parameters but before the final quote.

Save the file and run

Code:

update-grub

Re: Missing firmware message. This is just notification that a firmware file **might** be missing.
This particular firmware file doesn't apply to your hardware. You can add it if you so wish..

It is obtainable from many sources, just google for it.
One example: http://anduin.linuxfromscratch.org/s...firmware/i915/
Download the file and manually copy it to

Code:

/lib/firmware/i915

Bodge99

Klaas Vaak · 08-08-2019, 08:20 AM

Quote:

Originally Posted by bodge99

Hi,

Klaas: If you want to add kernel parameters to Grub then edit /etc/default/grub

At (around) line 10, you'll see a line then starts with:

Code:

GRUB_CMDLINE_LINUX_DEFAULT=

Add your kernel options at the end of this line, after the existing parameters but before the final quote.

Save the file and run

Code:

update-grub

Hey Bodge, before this comment, I had added this to GRUB_CMDLINE_LINUX_DEFAULT=

Code:

atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1

which now looks as follows:
GRUB_CMDLINE_LINUX_DEFAULT="atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 quiet splash"
just to see the effect as per Colorpurple's suggestion. I got nothing to lose, right?

So, are you saying that, if I want to add root delay, it will look like this:

Quote:

GRUB_CMDLINE_LINUX_DEFAULT="atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 rootdelay=5 quiet splash"

Forgot to mention: after I added atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 I forgot to do sudo update-grub before closing down. I did sudo update-grub after rebooting, does that matter? I guess not, but then the change will only take place after the next reboot, correct?

bodge99 · 08-08-2019, 08:27 AM

Klaas:

Looks O.K.

Just one point, It's a good habit to place the new parameters after the existing ones.. i.e. "quiet splash" first.
It actually doesn't matter here, but there will be occasions where the order of certain parameters is important.

If you ever come across these, specific information will be given when required.

Bodge99

Klaas Vaak · 08-08-2019, 08:30 AM

Quote:

Originally Posted by bodge99

Klaas:

Looks O.K.

Just one point, It's a good habit to place the new parameters after the existing ones.. i.e. "quiet splash" first.
It actually doesn't matter here, but there will be occasions where the order of certain parameters is important.

If you ever come across these, specific information will be given when required.

Bodge99

Good point. So, the order of parameters between the quotation marks does not matter. Correct?
Also, please see the added last paragraph (re: sudo update-grub) to my previous reply to you

bodge99 · 08-08-2019, 09:11 AM

Klaas:
You can edit /boot/grub/grub.cfg directly if you so wish.. It's not normal practice and the "Do not edit this file, or we'll eat your first born" message is because this file is automatically overwritten every time "update-grub" is run or the kernel is upgraded. Any changes made are lost.

The update process here takes its kernel parameter list from the " GRUB_CMDLINE_LINUX_DEFAULT=..." line in /etc/default/grub .
To actually add the parameters to the working /boot/grub/grub.cfg you have to manually run "update-grub". The system won't "see" any changes until this is done.

When you are at the stage where you can use the edit mode in your Grub menu, you can then edit a particular boot entry and add the parameters there. Press F10 to continue the boot.. This is a way to temporarily test any kernel parameters.. The changes are lost on the next reboot.

One other parameter to try.. "nomodeset". With a newer kernel, GPU initialisation is not done by Xorg, but by the kernel. The "nomodeset" tells the kernel not to initialise the GPU, but leave it alone. Xorg then initialises the GPU. Sometimes (mostly) it's better to let the kernel do the job, sometimes Xorg will be better. It depends..

If you try a kernel parameter that (for example) leaves you with an unusable screen or other problem then the normal way to recover from this is to use edit mode in your Grub menu to remove the problematic parameter. This will allow you to boot. You would then remove the parameter from /etc/default/grub and run "update-grub" to correct your /boot/grub/grub.cfg file.

If you cannot use the edit mode in Grub and as the system isn't booting properly (don't forget to try your virtual terminals Ctrl+Alt+F1) then you would have to boot from a flashdrive and edit the /{mount location}/boot/grub/grub.cfg to remove the parameter from the relevant line in grub.cfg .
This is why I recommended keeping a copy of the working grub.cfg in the same directory. You then only need to overwrite the existing grub.cfg with your copy.
A little quicker and easier to do.

Bodge99

colorpurple21859 · 08-08-2019, 09:12 AM

The changes made in /etc/default/grub do not take place until sudo update-grub is run.