Printable View
that's the rror I get when trying to boot onto my 2.6.0-test4 kernel. The system then panics and says that it can't find any init.
I can bodge my way around it by taking the initrd out of the grub.conf setup.
Has anyone got any ideas of what I've done wrong?
thanks
Nerderello
did you build ext3 support into the kernel?
This page might help start you off http://www.vineyard.net/vni/docs/grub/errors.html , And why do you use an initrd image isnt that for boot disks??
my first thought was that I'd left off ext3, so I re-did the build xconfig (looks so much better now) and made sure that not only was ext3 in, but I had also checked the debug info box as well.
Same result.
Now, I've had something like this before when I forgot to put the underline in 'build modules_install' , but I am definately doing that (you get screens of *.ko modules being created and copied).
As to why I'm using initrd, because I thought that that was the correct thing to do (my Redhat distro came with it). Is this not the case.
thanks
Nerderello
ps. enjoying being a newbie again :?
I guessed you where using Grub am i right? And ive never used initrd because i thought it was for RAM disks. And AFAIK for it to work you need unix PTY's enabled. Also you should disable loadable modules in the kernel there slower and can be a security risk.
EDIT, Your answer > Just solved your problem, Whats wrong is you compiled ext3 support in as a module yeh? It needs to be compiled into the kernel cause when you boot it checks your file system but at this point your modules havent been loaded into the kernel so it wont work so just use a * not a m :twisted:
yup, you're right. I got back from work ( a concept that is highly overated) and decided to go back to the 'good old ways' by doing a "build menuconfig" and sure enough, there it was, a "M" instead of a "*". In my defense I will say that I was using "build xconfig" for the first time in anger and hadn't quite got my head around the difference between a tick and a blob.
Thanks guys for helping.
Now all I've got to do is get the X working and I'll be happy.
have fun
Nerederello
guess what, my X problems were down to having the agpgart stuff as modules instead of in the kernel.
Oh well, at least I'm learning how not to do it. :wink:
have fun
Nerderello
Glad to see that you're figured it all out. Stupid/careless mistakes like that are very common...especially when you're going through a kernel config...just remember to always compile in your chipset drivers...though I don't know anyone that would've forgotten that... :oops:
Hi nerderello,
I am facing the following problem after installation of Fdero 4. Can you help me?
Decompressing linux ..done
Booting the kernal
..MP -BIOS bug : 8254 timer not connected to 10-APIC
Red Hat nash version 4.2.15 starting
mkrootdev:label/1 not found
mount: error 2 mounting ext3
ERROR opening, /dev/console !!!! :2
error dup2' ing fd of 0 to 0
error dup2' ing fd of 0 to 1
error dup2' ing fd of 0 to 2
switchroot : mount failed :22
kernal panic - not syncing : Attended to kill init!
Hi graja !
Duplicate Threads/Posts are not allowed and this is a pretty old thread. Please continue here only. Thread Locked.