Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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
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.
Originally posted by tarballedtux 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"
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)?
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).
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)
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