Problem running newly compiled kernel (2.6.39)...

[scuzzy]

I have been trying to build linux from source code and run it from my machine (intel platform). Here's what I did:

$make defconfig
$make
$make modules
#make modules_install
#make install
#update-grub

I am using Grub2. When I rebooted the new kernel was in the grub list all right. But booting from that kernel fails with no errors or warning. The screen just goes blank. The disk usage indicator LED also doesn't glow which I guess means that the kernel isn't being read from the disk. I rebooted using my older kernel and it booted properly. Then, when I listed my /boot directory, I noticed that there was no initrd.img for 2.6.39. kernel in there, which I think is the problem. Any suggestions?

[scuzzy]

I tried to make the init ramdisk manually:
#update-initramfs -c -k 2.6.39
#update grub

On rebooting, the same problem occured. So I tried booting in recovery mode. I worked. Although, the shell prompt is strange

(initramfs)

Also, the directory structure is weird and there is no /boot or /home and a /root directory is present. vi editor is not present. Is this normal for manually compiled kernels? And why is it booting only in recovery mode? I am new to this so kindly help.

[Rubberman]

What was your previous kernel before you tried to build/install 2.6.39? And is this 32-bit or 64-bit? I also assume (possibly incorrectly) that you are running an Intel processor?

[dE_logics]

I fail to understand how did you start the new kernel when you did not copy it to /boot.

[rrl]

What was your previous kernel before you tried to build/install 2.6.39? And is this 32-bit or 64-bit? I also assume (possibly incorrectly) that you are running an Intel processor?

I have been trying to build linux from source code and run it from my machine (intel platform).

Whenever you assume, there is always the possibility of being wrong.

[scuzzy]

I fail to understand how did you start the new kernel when you did not copy it to /boot.

make install does that

[scuzzy]

I fail to understand how did you start the new kernel when you did not copy it to /boot.

make install does that

[scuzzy]

2.6.35-22. intel 32-bit

[dE_logics]

make install does that

It does not unless the sources are modified (I've never seen such kernel sources). You have to do it manually.

[scuzzy]

It does not unless the sources are modified (I've never seen such kernel sources). You have to do it manually.

The kernel image vmlinuz is being created there. The only problem is with initrd.img.