build kernel with make-kpkg wrong processor type

stockerz · 02-01-2005, 03:41 PM

hi,

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...

What's wrong with it?

Here is the beginning og the compiling process:

make-kpkg -rev bla.1 kernel_image
/usr/bin/make \
ARCH=i386 oldconfig
make[1]: Entering directory `/usr/src/linux-2.6.10'
scripts/kconfig/conf -o arch/i386/Kconfig

and this :

* Processor type and features
*
Subarchitecture Type
> 1. PC-compatible (X86_PC)
2. AMD Elan (X86_ELAN)
3. Voyager (NCR) (X86_VOYAGER)
4. NUMAQ (IBM/Sequent) (X86_NUMAQ)
5. SGI 320/540 (Visual Workstation) (X86_VISWS)
choice[1-5]: 1
Processor family
1. 386 (M386)
2. 486 (M486)
3. 586/K5/5x86/6x86/6x86MX (M586)
4. Pentium-Classic (M586TSC)
5. Pentium-MMX (M586MMX)
6. Pentium-Pro (M686)
7. Pentium-II/Celeron(pre-Coppermine) (MPENTIUMII)
8. Pentium-III/Celeron(Coppermine)/Pentium-III Xeon (MPENTIUMIII)
9. Pentium M (MPENTIUMM)
10. Pentium-4/Celeron(P4-based)/Pentium-4 M/Xeon (MPENTIUM4)
11. K6/K6-II/K6-III (MK6)
> 12. Athlon/Duron/K7 (MK7)

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...

Thanks

m_yates · 02-01-2005, 05:14 PM

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.

stockerz · 02-01-2005, 05:23 PM

alright,

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...

Anyway, i gonna install it and test it.

Guillaume

stockerz · 02-01-2005, 06:04 PM

shit!

Kernel panic!

not syncing: VFS: unable to mount root fs on unknown block (0,0)

I'm tired, i'm going to sleep

By!

ch_music · 02-03-2005, 11:14 PM

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! =)

Cheers,
Chris