DebianThis forum is for the discussion of Debian Linux.
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.
I just build a kernel 2.6.10 using make-kpkg.
Everything went fine, except that i have a athlon cpu (and of course i tilled this on the processor type) and the package built by make-kpkg has the 396 suffix...
Where does make-kpkg get this 386 variable?
In the man, it speaks about setting ARCH variable but only for crosscompiling. I also says that the processor type should be autamically found...
The package you create automatically has "_10.00.Custom_i386" appended to it, even if you selected 586, 686, k7, etc. as the processor type. It doesn't mean anything and it doesn't show up on the kernel name. For example, my package name is:
Code:
kernel-image-2.6.7-w4ldeb_10.00.Custom_i386.deb
and uname -r gives:
Code:
2.6.7-w4ldeb
and if I check my configuration, it is configured for a k7 processor.
i was just wondering why it does't end up with
k7.deb
as you can find it onto the debian package for k7 you can get on the official testing repository.....
I tried to pass option
--arch_in_name
as it says in the manpage : it should add the subarchitecture in the package name but it didn't change anything for me...
Hmph, you have to compile using make-kpkg and create the initrd as well. Debian uses initrd to boot (it's a ramdisk where it loads the drivers, especially for the filesystems). You can try compiling the kernel with built-in (not module) support for whatever filesystems you are using for root partition (ext2, ext3, reiser?).
Since I haven't tried the above step myself, you can always read the sticky topic on Debian forum here (the one about compiling Linux kernel). It shows the crucial steps to compile kernel with initrd for debian. And it works with mine! =)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.