Thanks! This is from THE machine. The bootup would stop after showing that ACPI error message. I have to go into the GRUB edited the line of LINUX by adding nomodeset and acpi=off to make the bootup complete.
Q1: where do I go to add that command line?
Q2: How can I add “nomodeset” and “acpi=off” into GRUB permanently?
Thanks, Dan!
Solved! Thanks! It’s been a good lesson
A recently updated distro for both 64 and 32 bit CPUs is MX Linux.
BTW when installing any Linux distro the HHD or SSD does not need to be preformatted. This is done automatically after specifying to install the distro on the whole disk .
The latest Ubuntu ecosystem distros including Ubuntu ,Linux Mint, Zorin are no longer available for 32bit systems.
Frank in County Wicklow -Ireland
That is OK for a whole disk install.
If you have other Linux distros or data partitions on the disk, it is safer to preformat the partition you are going to use for the install.
Yes 32bit is getting rare
Cheers
Neville
Hi, Y’all!
Somehow I managed to have corrupted the grub file and could only boot from the recovery. Can someone tell me the different between the following 2 grubs, first one does NOT work, second DOES(this is the recovery mode)
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root=‘hd0,msdos1’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 41d75fa5-764b-4f6c-aa6b-8a58c93ebc92
else
search --no-floppy --fs-uuid --set=root 41d75fa5-764b-4f6c-aa6b-8a58c93ebc92
fi
linux /boot/vmlinuz-5.17.5-76051705-generic root=UUID=41d75fa5-764b-4f6c-aa6b-8a58c93ebc92 ro quiet splash nomodeset acpi=off $vt_handoff
initrd /boot/initrd.img-5.17.5-76051705-generic
The Recovery one
recordfail
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 41d75fa5-764b-4f6c-aa6b-8a58c93ebc92
else
search --no-floppy --fs-uuid --set=root 41d75fa5-764b-4f6c-aa6b-8a58c93ebc92
fi
echo 'Loading Linux 5.17.5-76051705-generic ...'
linux /boot/vmlinuz-5.17.5-76051705-generic root=UUID=41d75fa5-764b-4f6c-aa6b-8a58c93ebc92 ro recovery nomodeset dis_ucode_ldr
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.17.5-76051705-generic
In recovery mode, everything seems OK. But it is, after all, not a smooth bootup, in spite of getting a Grub Customizer and making the recovery go first.
Thanks in advance.
You should use a diff tool for comparing text content for in such situations.
https://www.howtogeek.com/410532/how-to-compare-two-text-files-in-the-linux-terminal/
When I compared both, the main difference I noticed was that the recovery one lacks the gfxmode directive.