LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices



Reply
 
Search this Thread
Old 08-12-2004, 02:35 PM   #1
Bamse123
Member
 
Registered: Apr 2003
Location: Rovaniemi, Finland
Distribution: Slackware
Posts: 69

Rep: Reputation: 15
Question Kernel Panic: No init found. Try passing init=option to Kernel


I really wanna know what caused this. Doing a Google search on this topic gives thousands of results but aren't of any help.

I'm on ZipSlack, the most recent one, downloaded from /slackware-current/ (so its 10.0). What I did was compiled a 2.6.7 kernel *after configuring it properly* and did all the necessary procedures. This because Slackware still uses the 2.4.26 kernel that's running in my compie right now (I could recover my OS) and I wanted to go 2.6.x.

So when I boot ZipSlack, I use loadlin.exe from DOS, and just pass "root=/dev/hda5" (the root partition). Then "rw". Everything works with 2.4.x, but when I replace vmlinuz with my newly compiled one, this happens. The kernel panics and the whole thing gets stuck there.

Like I already said I think the configuration was proper. The only thing I remember compiling as a module was my sound card and APM my old computer uses so I can modprobe it and shutdown my machine. Filesystems, harddrive stuff etc. were compiled to the kernel.

So... what is it? What did I do wrong?

Regards,
Bamse
 
Old 08-12-2004, 02:52 PM   #2
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 14.1
Posts: 1,141

Rep: Reputation: 55
This may or may not help but did you include a support for initrd support in your kernel? If you included support for initrd and you didnt make an initrd.2.6.7.img in your /boot partition, it may be causing problems.

Also your filesystem cannot be module or else you'll need a init ram disk.

Sorry if this doesnt help,
Tux
 
Old 08-13-2004, 01:16 AM   #3
Bamse123
Member
 
Registered: Apr 2003
Location: Rovaniemi, Finland
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: 15
Quote:
If you included support for initrd and you didnt make an initrd.2.6.7.img in your /boot partition...
Yeah that's what causes it, I guess.

So I need
this .

It's tough to remember your kernel configuration by heart. But I guess the config is still stored in the folder for the kernel source is/was, or? Maybe I included initrd support, maybe not.

My filesystem is not a module, is compiled to the kernel.

About the boot partition... I'm not quite sure about that since ZipSlack doesn't have partitions. So if I put initrd in /boot, will it be able to find it? I hope so...

Quote:
Kernel Panic: No init found. Try passing init=option to Kernel
How about the init= option, do I need that then?

This thread belongs to the Slackware forum...

Thanks...

Regards,
Bamse
 
Old 08-13-2004, 05:56 AM   #4
Bamse123
Member
 
Registered: Apr 2003
Location: Rovaniemi, Finland
Distribution: Slackware
Posts: 69

Original Poster
Rep: Reputation: 15
Conclusion: I guess I can't run 2.6.x kernel on ZipSlack unless I compile it myself and use some quirky tweaks to get it working with a umsdos filesystem. I grabbed the generic 2.6.7 kernel with modules and all the stuff from the Slackware FTP but it doesn't work with ZipSlack. Am I right when I say that the precompiled kernel can't be used with ZipSlack? I think I should get a real operating system -- only if I had CD-RW.

Regards,
Bamse
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel Panic: No init found. Try passing init=option to Kernel ridak Fedora 5 09-08-2004 02:25 AM
Kernal Panic: No init found. Try passing init= option to kernel raees Linux - General 12 03-19-2004 12:10 AM
Kernel Panic: No Init Found Try Passing Init=option To Kernel Bakame Linux - Newbie 4 03-10-2004 07:08 AM
error "Kernel panic: No init found. Try passing init= option Anauj0101 Linux - Newbie 3 05-06-2003 11:18 PM
Compiled own kernel and got: Kernel panic: No init found. Try passing init= option to fbl Linux - General 12 01-14-2003 04:38 AM


All times are GMT -5. The time now is 11:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration