Decided to implement QT Image Processing in the embedded, installed after VMware, new virtual machine but do not understand how it can not start Fedora13, set the CD-ROM path, is not good, in the CZ students prompt, it turned out that the power supply item was not hooked up. Ah, I haven't done it for a long time. I am not familiar with it, and I have also made such a low-level mistake. Then I went to the installation system and set up the NAT network. At the beginning, the allocated memory was too small for half a day. I thought there was another problem. Shut down and restart, increased the VM memory, and everything went fine. After installing the system, you have to install Virtual Machine Tools. At the beginning,
Decided to implement QT Image Processing in the embedded, installed after VMware, new virtual machine but do not understand how it can not start Fedora13, set the CD-ROM path, is not good, in the CZ students prompt, it turned out that the power supply item was not hooked up. Ah, I haven't done it for a long time. I am not familiar with it, and I have also made such a low-level mistake. Then I went to the installation system and set up the NAT network. At the beginning, the allocated memory was too small for half a day. I thought there was another problem. Shut down and restart, increased the VM memory, and everything went fine.
After installing the system, you have to install the Virtual Machine Tool. At the beginning, you can directly install the one at the end of RPM. After installation, no response is returned. So I just want to install another compression format, and the results have been unable to be decompressed, which is not a problem with permissions. The online files cannot be stored in the Media directory, may be the reason for mounting? Decompress the package in the/tmp directory, but the system prompts that the kernel version does not match during installation. Therefore, you must install GCC to upgrade the kernel.
-------------------------- Split line of others' things ----------------------------------------------------
First install gcc, make, kernel-devel, (the yum Command needs to be accessible)
Yum install gcc
Yum install make
Yum install kernel-devel
Check whether the version of the kernel file matches. if the version does not match, upgrade the file.
Uname-r
Rpm-q kernel-devel
If not, you need to upgrade the Kernel File. After the upgrade, restart the system.
Yum-y upgrade kernel-devel
Find the location of the kernel file (may be required)
Ls-d/usr/src/kernels/$ (uname-r) */include
Then install vmware tools
-------------------------- I started my own ----------------------------------------------------
After the kernel header file is specified, the following message is displayed:
The directory of kernel headers (version @ VMWARE @ UTS_RELEASE) does notmatch your running kernel (version 2.6.33.6-147. fc13.i686 ). even if the module were to compile successfully, it wocould not load into the running kernel.
To continue searching, follow these steps :::::::::::::
Open linux/version. h. The content is
# Define LINUX_VERSION_CODE 132641
# Define KERNEL_VERSION (a, B, c) (a) <16) + (B) <8) + (c ))
2.6.33 kernel = 2 <16 + 6 <8 + 33 = 2*65536 + 6*256 + 33 = 132641
Why is the version incorrect ?! Is the version algorithm different?
Again, the version read by vmware, UTS_RELEASE! Add a line to linux/version. h:
# Define UTS_RELEASE "2.6.33.5-112. fc13.i686"
# Define LINUX_VERSION_CODE 132630
# Define KERNEL_VERSION (a, B, c) (a) <16) + (B) <8) + (c ))
Vmware finally believes that the version of the kernel header file provided by dorainm matches. :::::::::::::::::::::::::::::::::::
The problem I encountered was that I could not find linux/version. h. Find out. In usr/src/kernels/$ (uname-r) */include/linux/version. h. Another reason is that my kernel version is different from that on the Internet. When I add a line, I will change it to my own, save it, reinstall it, and fix it!