Can someone help me with this?
Trying to compiling kernel 2.6.0
and
I'm getting an error at bootup.
=========================
Mounting root device
Mount: error 19 mounting ext3
pivot-root: pivot-root (sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 232k freed
kernel panic: No init found. Try passing init= option to kernel

Hi dot!

Welcome to LinuxQuestions.

Moving right along:
Did you include ext3 support in the kernel? It must not be added as a module but must be compiled right in to the kernel.

Regards
Martin

Hello,

MartinN, I have a problem almost exactly like dot does. My problem is as follows:

mounting root filesystem
mount: error 19 mounting ext3 flags Mounted devfs on /dev
freeing unused kernel memory: 288K freed
kernel panic: no init found. try passing init= option to kernel

so, how do we go about changing our kernel to include the ext3 right into the kernel rather than as a being added as a module??


thanks in advance :-D

Hi Ceevu! Welcome to you too.

Is this a kernel that you have compiled yourself? Then I'd like to know a couple of things:

o What kernel version were you compiling?

o I suppose that you had a step early in the process that was 'make xconfig' or 'make menuconfig'. Which of them was it?

Regards
Martin

Hey MartinN,

thanks for the 'welcome'

I am trying to install the new kernel 2.6.1.

I was following this set of instructions:

http://www.linuxquestions.org/questi...mpile+a+kernel

I have the lilo bootmanager installed.

hehe...i ...uhm....can't remember which one i used in regards to the menuconfig or xconfig. doh! I must hve been mindlessly following orders or some such thing(i did this half a day ago or so....a long time in regards to my poor s-t memory!).

Anyhoo, thanks for the quick response. :-D

Hi again!

I make a guess that you used xconfig (a GUI configurator where you click around in a tree structure).

You have a tab for file systems (in 2.6.0 it's the fourth main "branch" of the tree). Make sure that "Ext3 journalling file system support" is built in to the kernel (i.e. it shall have a check mark, not a dot).

Good luck!
Martin

Hey, man u are fast! lol

So, i should just start the whole thing from scratch? or is there a midpoint somewhere i can start with? or start from the 'make xconfig' bit and carry on from there?


Thanks for your help!


by the way, did you check out that link for the help i got? was it quite thorough, in your opinion?

Good question! I would start from the make xconfig. I think that it should work. If you really want to be on the safe side: move away the .config file somewhere else. Then 'make mrproper', put back the .config and then 'make xconfig'. Proceed with the following steps.

Always trust the gurus The description is correct -- I've followed it myself.

Regards
Fast fingers Martin

fan-tiggly-tastic


I just ran the 'make xconfig' again and got the little check mark by the ext3 thingy-ma-bob. I was wondering what the difference between the dot and check mark were(dot = mod, check = installed in kernel, correct?)

so, i'm about to lose some sleep(needed but not well-deserved ) and carry on from that spot.


Thanks for your help and quick response again!


PS I'm about to experience deja-vu :-D

I figured you were doing this like 5:30 in the morning. It's almost lunch time here in Sweden.

You're correct about the dot and the check mark. For obvious reasons, the file system must be compiled in to the kernel.

Have a good morning's sleep.
Martin

Hehhehehe.


I got Mandrake 9.1 to load the 2.6.1 kernel but i get a whole lot of 'failed' messages when i boot up. when i do boot up in the new 2.6.1 kernel, i can't run any programs(well, i tried to open a aumix and xmms....both just went to the spinning hourglass then disappeared after a few minutes) and i couldn't acces the internet

I'll take a peek tomorrow night. Hopefully, i can enter the 'interactive' mode when booting up so i can write down all the failures on boot(one of them was in regards to mounting file systems :-s).


anyways, enjoy lunch


and, again, thanks for your help :

I just wanted to let you know that if you have the new kernel autoloading module stuff installed you actually can have things like file systems compiled as modules and have it still work

jtshaw,

first of all, hello! hehe

let me try to decipher the 'coded' message (i'm a newb to the n00bs). If i am wrong, lemme know

Quote: I just wanted to let you know that if you have the new kernel autoloading module stuff installed you actually can have things like file systems compiled as modules and have it still work


'new kernek autoloading module stuff installed'

uhm, how do i know if the kernel is autoloading stuff that is installed?(is this done when i use the command 'make xconfig' and put a 'check mark' beside something?)

ou actually can have things like file systems compiled as modules

and how would i get the kernel to compile file systems as modules??

Also, is there a way I am able to check the bootup logs? i am getting many 'failed' messages when booting but can't enter interactive bootup quick enough to catch several in the beginning.


Thank you for your suggestions, jtshaw

Sorry for the cryptic message:

Under Loadable Module Support in the kernel configuration for 2.6 this is an option called "Automatic kernel module loading".

Kernel help Description:
Normally when you have selected some parts of the kernel to be created as kernel modules, you must load them (using the "modprobe" command) before you can use them. If you say Y here, some parts of the kernel will be able to load modules automatically: when a part of the kernel needs a module, it runs modprobe with the appropriate arguments, thereby loading the module if it is available. If unsure, say Y.


If you have this enabled, and you hit M when selecting a file system in the file systems section of the kernel setup then the kernel should automatically load the file system module when it needs it.

I hope this was a little more specific.

Heh, no worries.

I used 'make xconfig' and under the Loadable Module support, i have check marks in all 4 items under 'Enable loadable module support'.

so...from my understanding of this...the check mark means that it is installed in the kernel and the dot means its a module...should i change the 'automatic module loading support' to a dot rather than a check?

thanks in advance


edit: doh! i was just messing around with it (clicking on the box) and it only has 'check' or 'no check'.... no option for a dot. is that right? or is there something i'm not doing if i need it as a module rather than installed in the kernel?