problem compiling custom kernel

quozl

Hi,
I want to compile a custom kernel for my p4 system. I had no difficulties doing this for my old p2-450. But whenever I install a new kernel, the boot hangs at the
checking parititions: stage
of linux startup. (where linux lists the disk partitions, nothing to do with a bootloader)
it lists my hard drives. and then dies before it lists all the partitions inside my extended partition. This is rh 7.2, with 2.4.10 and some higher one I cant remember.
I've tried changing a zillion things in the kernel, any idea what I could be doing wrong? It seems a strange place to hang. BTW my hd have some ntfs, fat32, ext2, ext3, and freebsd partitions in case this matters.
The default rh kernel works. But if I try and compile one from RH kernel sources, nada.
quozl

Typedef

Ok do you have one or two disks?

If you have more than one hard disk does the detection stop @ the first or the second?

Here is a couple of quick fixes you might want to try.
First get >= linux-2.4.16.
Next try making two bzImages one with all partition options turned on, and one with them all turned off.

Next start looking at perhaps some kind of ide or scsi issue. Assuming you have a primary ide hdd partitioned with your *nix distros I would say hmm, perhaps it is the archetecture the kernel has been compiled for I don't know about rh 7.2 but for example it might have compiled the kernel with march=pentium4(if such an option exists). Try compiling for march=i686 or something.

What else. You could try kernel 2.2.20?
I would say compile a conservative kernel, ie one wich has no experimental options and only the minimum drivers ie ppp, ethernet, filesystem, soundcard and omit things like agp etc.

Also if you compiled agp gart into your kernel you should have a look at www.gentoo.org.

Post what happens?

quozl

Originally posted by Typedef
Ok do you have one or two disks?

1 60 gig hd, 1 dvd/cdrw, 1 cd


>Here is a couple of quick fixes you might want to try.
>First get >= linux-2.4.16.
Tried that

>Next try making two bzImages one with all partition options turned on, >and one with them all turned off.
tried making one with all partition types supported, not luck. Shoud'nt matter I think (but I tried just in case) because all its doing is reading the partition tables on the disks at this stage I think? It isnt trying to mount anything yet.

>Next start looking at perhaps some kind of ide or scsi issue
my dvd/cdrw has to uses an ide scsi interface. I make sure thats compiled in, and pass the correct parameters at boot. This is one of the things I think it might well be though. Any other thoughts on a ide cdrw masquerading as a scsi.
.
> with march=pentium4(if such an option exists). Try compiling for >march=i686 or something.
Tried that. I've even compiled a 386 kernel

>What else. You could try kernel 2.2.20?
emm. no

I've compiled some absurdly conservative kernels to test, but nothing works. Any other ideas?
thanks for the reply,
quozl

Typedef

If said zImage crashes out at partition table reading then it is either the reading of the partiton table that doest be crashing the boot or whatever comes after the reading (and might not be being displayed).

I had some wired problems with 2.4.12 and 2.4.13, just never really seemed to compile or when they did, didn't seem to boot properly using gcc3.0.1 or gcc2.95.3 (or the difference between march=i686 and march=athlon) shrug.

If memory does serve then after reading the partiton table 'most' zImages begin to do ide-cdrom things... ergo I would say compile a bzImage with support for ide-cdrom and for ide scsi-emulation. Don't pass the modules as paramteres ie no append="hdc=ide-scsi" or anythign similar other than that, you could try a 2.5.x.

lynchie

BTW my hd have some ntfs, fat32, ext2, ext3, and freebsd partitions in case this matters.
The default rh kernel works. But if I try and compile one from RH kernel sources, nada.

Just a thought,

The default stock kernel with RH7.2 comes with the ext3 code patched into it. If you are compiling with a kernel from kernel.org the ext3 code has not been merged into the main kernel branch yet. You must download the ext3 patch, patch the kernel and then ensure that ext3 code is compiled in if your root partition is ext3