[ATrpms-users] Kernel compiled from source with NO changes won't boot

[Jarod Wilson]

On Monday 28 February 2005 16:14, Phill Edwards wrote:
> I downloaded the 2.6.10-1.14 kernel and sources, did make menuconfig
> and loaded the config file that came with it in /boot, exited and
> saved the config file. I then edited out the "custom" part of the
> extra version in Makefile and did:
>
> # make
> # make install
> # make modules
> # make modules_install
>
> Then I rebooted and slected my new kernel. Note that I did not make
> any changes to the kernel config, so this should just boot up without
> any problems. However, on boot I got these errors:
>
> insmod: error inserting 'lib/jbd.ko' : -1 Operation not permitted
> insmod: error inserting 'lib/ext3.ko' : -1 Operation not permitted
> Kernel panic: not syncing: No init found
>
> Is there something wrong with htis version or with the way I compiled
> the kernel? This should just work easy as.

If you take Red Hat's source, from which they were able to generate a working 
kernel, and can't generate a working kernel, 99.999% of the time, its 
operator error. It looks to me like you didn't create an initial ramdisk for 
your kernel build, which is needed to load the ext3 modules at boot time so 
you can get at your / partition, which more likely than not, is ext3 
formatted...

-- 
Jarod Wilson
jarod at wilsonet.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20050228/7d145d25/attachment.bin