Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I try do build my first real time kernel. When I start booting I get several errors which are not there when booting the normal kernel .25.2 debian/lenny/sid...
HElp = needed here!
Thanks in advance
Post Posted: 2008-07-07 09:22 Post subject: Reply with quote
I get these errors, but not with the normal 25.2 kernel:
When booting process starts:
resume: libgcrypt version: 1.4.1
> > resume: couldn't not stat the resume device file '/dev/hda3'
> > please type in the full path name to try again
> > or press ENTER to boot the system
when I press enter, I get after a few seconds booting:
fsck.ext3: no such file or directory while trying to open /dev/hda2
/dev/hda2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else) then the superblock
is corrupt, and you might try running e2fsk with an alternate superblock:
e2fsck -b 8193 <device>
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.