I’m using BT3 these days, and as for the USE of IT, we all know that I used GRUb4DOS as my desktop computer to launch recently. In recent days, I want to use my laptop to run BT3, but according to the general setting, GRUB shows Error 13: Invalid or unsupported Invalid on startup.
Looking around, it’s almost certain that the vmlinuz and BT3 cores don’t match, but it’s not clear why the same Settings worked on desktop computers.
The solution is as follows
After recompiling the kernel, restarting the system resulted in a GRUB boot error
Grub Error 13: Invalid or unsupported Invalid format
Error clause xp and FC co-existed when kernel/vmlinuzz-2.6.15 ro root= /dev/volgroup00 /LogVol00 RHGB quiet
installation. Restart the system again, enter xp, and search for the solution to Error 13.
use the rescue disk to enter the fc, check the Settings in /etc/grub.conf file, and check the filename in the Settings. It matches the file on your hard drive.
USES Google again to view the explanation of the vmlinuz file. On linuxidc.com, see
. Vmlinuz is the executable Linux kernel. It is located at /boot/vmlinuz and has two ways to build it. First, the kernel is created by “make zImage” when compiling, and then by:
“Cp/usr/SRC/Linux – 2.4/arch/i386/Linux/boot/zImage/boot/called”. ZImage is suitable for small kernels and exists for backward compatibility. The second is the kernel compile time through the command make bzImage created, then through: “cp/usr/SRC/Linux – 2.4/arch/i386/Linux/boot/bzImage/boot/called”.
Because vmlinuz is before compiling the kernel, the original system does not match the system after compiling the kernel, so it cannot be started
. Restart to enter grub, press e to modify, change vmlinuz-version to bzImage, press b to start Linux
to enter Linux. Go to/boot/ and delete the old vmlinuz, then rename the bzImage to vmlinuz-version
and everything will work fine.
appendix: Conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: you have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, Eg.
# root (hd0, 8)
# kernel/called – version ro root =/dev/VolGroup00 LogVol00
# initrd /initrd-version. Img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,8)/grub/splash. Xpg.gz
hiddenmenu
title Fedora Core (2.6.15_FC5)
root (hd0,8)
kernel/vmlinuuz-2.6.15 ro root= /dev/volgroup00 /LogVol00 RHGB quiet
initrd /initrd-2.6.15. Img
title Other
rootnoverify (hd0,0)
chainloader +1
Read More:
- How to solve the problem of error 15: file not found when Linux starts
- Solve boot prompt“ error:unknown filesystem Grub rescue “problem
- Solution to “error: invalid environment block” when Ubuntu starts up
- Virtual environment: error: virtualenv is not compatible with this system or executable
- Win10 system [createfile() error: 5] problem solving
- Error “/run/lvm/lvmetad.socket: connect failed: No such file or directory” – but not Grub related
- Modify grub to solve computer startup error: error 17
- [DRC nstd-1] problem solving of vivado error problem
- SSL appears in foxes_ error_ unsupported_ Version problem
- [How to Fix] error: file ‘/boot/grub/i386-pc/normal.mod’ not found
- Ubuntu starts or restarts SSH service
- Solve the problem of docker error: Unsupported compose file version: 3.2
- Solution of grub loading error 17
- There is no windows solution in dual system Ubuntu grub startup
- npm ERR! Error: CERT_ Untrusted problem solving
- Duplicate class com.xxx.xxx Find in modules problem solving (Aidl interdependence problem)
- Call to undefined function oci_ Connect() problem solving
- Online problem solving analysis
- Problem solving – vs debugging window flash solution
- [unable to calculate item metadata “% (fullpath)” unable to apply item metadata “% (fullpath)” to path] problem solving