After trying building a new kernel I wasn't able to boot my new box. Below is an excerpt from the boot sequence. Just tell me what other information is needed to solve this problem.

Here's the error I get after the message
"Running LinuxConf hooks"

INIT: Id "1" respawning too fast: disable for 5 minutes.
INIT: Id "2" respawning too fast: disable for 5 minutes.
INIT: Id "3" respawning too fast: disable for 5 minutes.
INIT: Id "4" respawning too fast: disable for 5 minutes.
INIT: Id "5" respawning too fast: disable for 5 minutes.
INIT: no more processes left in this runlevel


--Thanks in advance

You have not compiled something that's important. It's hard to tell you what from this error. I hope you still have the old kernel? Use it and build a new one.

Maybe this is unrelated to the afformentioned problem, I am getting an error that occurs before that about /dev/tty0: not found. Here's the exact messgae.

Loading default keymap (us): /etc/rc.sysinit: /dev/tty0: No such file our directory

I fairly certain that tty's are important so how would enable them in the kernel config. I probabaly left them out of the kernel config since I was trying to cut out parts I didn't think were needed.


--Thanks

Well is /dev/tty0 there or not?

It is there. I types ls /dev | grep tty | more in the old stock kernel.

It looks you have not included Input devices-> Virtual terminal

OK I got the /dev/tty problem fixed but now when I boot it seems like the root / and /boot are being mounted in read-only mode. I don't remember changing anything. Weird thing is, this didn't happen with the other problematic kernel.

--tarballedtux

that is normal, fsck needs to check them, it is only a problem if they don't remount read-only

No, it is a problem. It stays read only and eventually fails to boot. A whole bunch of errors get spit out about "Can't do <such and such> because file-system is read-only"


--tarballedtux

oh sorry man I misunderstood

I must say I'm lost. Which kernel are you talking about? Do you have this problem only with new kernel or also with the old one(this one from your distro)?

OK, this problem is with the new kernel(2.4.18). The old stock kernel is fine(2.4.9-34). Do I have to upgrade something like inittab or rc.sysinit to get the new kernel going?

--tarballedtux

No, all configuration files are the same. When one kernel is booting OK and there are problems only with the other one, it's definitelly a matter of the kernel. I don't remember an option giving such an effect. Maybe check the filesystem part (what you have as modules, what is compiled into your kernel etc).

Here's the transcribed "Filesystem Config)

EXT3 journalling file system support (EXPERIMENTAL) -- built in
JBD (ext3) debugging support -- built in
DOS FAT fs support -- built in
MSDOS fs support -- built in
VFAT (Windows-95) fs support -- built in
Virtual memory file system support (former shm fs) -- built in
ISO 9660 CDROM file system support -- built in
Micosoft Joliet CDROM extentions -- built in
/proc file system support -- built in
/dev file system support -- built in
Automatically mount at boot -- built in (This talking about /dev)
/dev/pts file system for Unix98 PTYs -- built in
Second Extended fs support -- built in
UDF file system support (read-only) -- module

--> Network File Systems
SMB file system support (to mount Windows shares etc.) -- built in

--> Native Language Support
Codepage 437 (United States, Canada)




--tarballedtux

Forget this guess and check operation. I got a generic working config and just modified it (Take out the the crap). I compiled and ran it booted fine I'm happy your happy. Now at least i have a good .config file so I can make oldconfig in the future

--tarablledtux