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.
Tried to compile new kernel 2.6.28, but I forgot to add something, so I decided to recompile it again, I couldn't, these are error messages that I've got
Code:
# make
find: /usr/src/linux-2.6.28/.tmp_vmlinux1: Input/output error
find: /usr/src/linux-2.6.28/.version: Input/output error
find: /usr/src/linux-2.6.28/.tmp_vmlinux1: Input/output error
find: /usr/src/linux-2.6.28/.version: Input/output error
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CC kernel/bounds.s
GEN include/linux/bounds.h
CC arch/x86/kernel/asm-offsets.s
GEN include/asm/asm-offsets.h
CALL scripts/checksyscalls.sh
CC init/main.o
make[1]: stat: include/linux/compile.h: Input/output error
CHK include/linux/compile.h
/usr/src/linux-2.6.28/scripts/mkcompile_h: line 30: .version: Input/output error
UPD include/linux/compile.h
mv: accessing `include/linux/compile.h': Input/output error
make[1]: stat: include/linux/compile.h: Input/output error
CC init/version.o
init/version.c:9:27: error: include/linux/compile.h: Input/output error
init/version.c:32: error: 'UTS_VERSION' undeclared here (not in a function)
init/version.c:33: error: 'UTS_MACHINE' undeclared here (not in a function)
init/version.c:41: error: expected ',' or ';' before 'LINUX_COMPILE_BY'
init/version.c:46: error: expected ',' or ';' before 'LINUX_COMPILE_BY'
make[1]: *** [init/version.o] Error 1
make: *** [init] Error 2
I've compiled new 2.6.28 kernel on debian lenny. After rebooted my computer to open with new kernel but i coulnd't boot deb. when i boot pc with new kernel I see always this screen.
http: //img258.imageshack.us/my.php?image=dsc00003gk7.jpg . Plz Help me ?
Umount the volume and use fsck to test it. If it's the root volume you will need to use a livecd.
I downloaded fresh kernel source, and this time everything went good, I didn't have time to run fsck yet, but I think I'll have to, just to make sure.
Thanks for the tip
I downloaded fresh kernel source, and this time everything went good, I didn't have time to run fsck yet, but I think I'll have to, just to make sure.
Thanks for the tip
If there's fs corruption and you continue operating the thing can get much much worse. I'd run fsck the first thing before doing anything else. Maybe I am wrong (and I would be glad to be wrong), but if I am not your data is at high risk until you sort that out.
I highly doubt that an arror while unpacking is provoking that, the kernel should never leave a file to remain in an inconsistent state even if tar failed or whatever, if that happens, then again it's called "fs corruption".
fsck 1.40.6 (09-Feb-2008)
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 1/3/2009 11.53.38
Using default parameter: -p
The current device is: /dev/hdb6
Block size in bytes: 4096
Filesystem size in blocks: 52389965
**Phase 0 - Replay Journal Log
Filesystem is clean.
well you will find 2.6.28 moved all your x86 kernel headers to a different place. I have spent day after day working on it. I give up the 2.6.28 is not for me or anybody that want to live with a x86. after reading all the bull about it you will see there is nothing but broken stuff the kernel compiles fine but to use it with other stuff is just out of my desire to fix something that was not broken to begin with http://bugzilla.kernel.org/buglist.c...ksearch=2.6.28
The Filesystem is clean comment means only that it has not been marked as dirty. I'd strongly suggest a fsck -f on the (unmounted) partition to force the check.
The Filesystem is clean comment means only that it has not been marked as dirty. I'd strongly suggest a fsck -f on the (unmounted) partition to force the check.
well you will find 2.6.28 moved all your x86 kernel headers to a different place. I have spent day after day working on it. I give up the 2.6.28 is not for me or anybody that want to live with a x86.
It's hard to figure out the justification for your comments. What exactly was moved where? The kernel headers, for a kernel compiled from source, are in the source tree. IOW, they're wherever YOU put them.
From my perspective, 2.6.28 is a great kernel. It fixed some issues I had, and hasn't failed me for any reason. I'm kind of a kernel junkie, but I haven't had any motivation to move further down the road from this one. I suppose it could be that I don't have the hardware that has the problems you're referring to.
you have to be kidding me a simple google would give you the out put. Please be patient with my frustration but the kernel is evolving toward the 64 bit system. and now your asm-x86 is now in /linux-2.6.28.7/arch/x86/include/asm and none of your stuff will find the header files to compile. you will have to symlink /usr/src/linux-2.6.28.x/include/asm -> asm-x86 but you have to also /2.6.28-/arch/x86/include/asm. there is a seperate tree for x86.
trust me google it and look at the change logs. this has created a lot of problems for the x86 to compile with. look at all the patch scripts ubuntu and fedora a bunch of them have been doing to solve this problem. Nice kernel well written just does not make x86 easy.
If you really want to see what is happening look at all the people have a hard time with nvidia kernel drivers it is not a nvidia driver problem when the kernel moves it's tree branches.
you have to be kidding me a simple google would give you the out put. Please be patient with my frustration but the kernel is evolving toward the 64 bit system. and now your asm-x86 is now in /linux-2.6.28.7/arch/x86/include/asm and none of your stuff will find the header files to compile. you will have to symlink /usr/src/linux-2.6.28.x/include/asm -> asm-x86 but you have to also /2.6.28-/arch/x86/include/asm. there is a seperate tree for x86.
trust me google it and look at the change logs. this has created a lot of problems for the x86 to compile with.
The OP is saying he's having trouble compiling the kernel. I didn't have the problem, as I stated in my response and as you can see in my info.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.