Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK. let me try to do so, and after that I should have to do one thing, to copy for which files into my VTC 1000.
Is that vmlinuz-3.x , initrd.img-3.x, System.map-3.x abi-3.x config-3.x???
No, you should copy the linux-image-*.deb you created to the VTC1000 and then install it using dpkg.
Could you specific more about the command
After that I should do
Code:
make modules install
make install
I got confused!
I have _never_ suggested that you do the above. I gave my recommended approach in post #10. Modified for cross compiling, and starting with some existing config it would be something like:
Code:
cd /usr/src
tar xjf linux-source-3.xx.tar.bz2
cd linux-source-3.xx
cp /from/somewhere/.config-foo .config
export DEB_HOST_ARCH=i386
make oldconfig
make menuconfig
fakeroot make-kpkg clean
fakeroot make-kpkg --arch i386 --append-to-version="-vtc1000" --revision="1.0" --initrd kernel-image kernel-headers modules-image
I have _never_ suggested that you do the above. I gave my recommended approach in post #10. Modified for cross compiling, and starting with some existing config it would be something like:
Code:
cd /usr/src
tar xjf linux-source-3.xx.tar.bz2
cd linux-source-3.xx
cp /from/somewhere/.config-foo .config
export DEB_HOST_ARCH=i386
make oldconfig
make menuconfig
fakeroot make-kpkg clean
fakeroot make-kpkg --arch i386 --append-to-version="-vtc1000" --revision="1.0" --initrd kernel-image kernel-headers modules-image
what kernel is the vtc1000 currently running? In an earlier post I think you said you got your initial .config from a standards Ubuntu kernel. Is that the same kernel that the vtc100 is currently running?
what kernel is the vtc1000 currently running? In an earlier post I think you said you got your initial .config from a standards Ubuntu kernel. Is that the same kernel that the vtc100 is currently running?
Evo2.
I used the kernel running in my personal PC. Which is Ubuntu 12.04 , kernel 3.6.11(Oh~ I think I take the previous compile well
kernel, because I successed done upgrade the kernel in my personal PC)
I think I got to reinstall the Ubuntu 12.04 and do it all again~ Because my kernel was change for so many times.
I used the kernel running in my personal PC. Which is Ubuntu 12.04 , kernel 3.6.11(Oh~ I think I take the previous compile well
kernel, because I successed done upgrade the kernel in my personal PC)
I think I got to reinstall the Ubuntu 12.04 and do it all again~ Because my kernel was change for so many times.
Ok, but when you build a new kernel it is probably best to start with the config from working kernel on the machine that you are trying to build the new kernel for. Also, please don't do the "make install" or "make modules install" etc. Stick to building and installing the deb packages. This way you will be able keep your old kernels installed next to the new kernel.
Ok, but when you build a new kernel it is probably best to start with the config from working kernel on the machine that you are trying to build the new kernel for. Also, please don't do the "make install" or "make modules install" etc. Stick to building and installing the deb packages. This way you will be able keep your old kernels installed next to the new kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.