kernel did not make in chapter 8, how to redo without starting over
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
kernel did not make in chapter 8, how to redo without starting over
well, it has been a fun filled weekend of learning and sitting at the computer for hours and i saw the light at the end of the tunnel. i got all the way to the end of chapter 8, tried to compile and build the kernel, then when i hit make, it bombed out.
Code:
root:/sources/linux-3.13.3# make
scripts/kconfig/conf --silentoldconfig Kconfig
SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h
SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_64.h
SYSHDR arch/x86/syscalls/../include/generated/uapi/asm/unistd_x32.h
SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_32.h
HOSTCC arch/x86/tools/relocs_32.o
HOSTCC arch/x86/tools/relocs_64.o
HOSTCC arch/x86/tools/relocs_common.o
HOSTLD arch/x86/tools/relocs
CHK include/config/kernel.release
UPD include/config/kernel.release
WRAP arch/x86/include/generated/asm/clkdev.h
CHK include/generated/uapi/linux/version.h
UPD include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
CC kernel/bounds.s
GEN include/generated/bounds.h
CC arch/x86/kernel/asm-offsets.s
GEN include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/selinux/genheaders/genheaders
HOSTCC scripts/selinux/mdp/mdp
HOSTCC scripts/kallsyms
HOSTCC scripts/pnmtologo
HOSTCC scripts/conmakehash
HOSTCC scripts/sortextable
CC init/main.o
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
CC init/do_mounts.o
CC init/do_mounts_initrd.o
CC init/do_mounts_md.o
LD init/mounts.o
CC init/initramfs.o
CC init/calibrate.o
CC init/init_task.o
LD init/built-in.o
HOSTCC usr/gen_init_cpio
GEN usr/initramfs_data.cpio.gz
/sources/linux-3.13.3/scripts/gen_initramfs_list.sh: line 318: gzip: command not found
/sources/linux-3.13.3/usr/Makefile:73: recipe for target 'usr/initramfs_data.cpio.gz' failed
make[1]: *** [usr/initramfs_data.cpio.gz] Error 1
Makefile:816: recipe for target 'usr' failed
make: *** [usr] Error 2
i am getting really good at tracing down the errors, but i have to admit, after i started chapter 6, there were very few of them, all easily solved by deleting the directory i created untarring the file and starting over.
i have been trying for a day now to figure this one out, and i have one question: can i just delete the linux-3.13.3 directory and start again? my gut says no, that i have to go back to the beginning of chapter 6 and go in order, but there may be a workaround that will save me another two days. i have to admit, this took me back to the old days when i was a kid, sitting in my bedroom all night sometimes typing away in basic just to create a not-so-cool game(by todays standards)of a riverboat seeming to move and shoot things. just to date myself, it was a ti 99-4a and a tv as a monitor, saving everything to a tape recorder.
anyway, i am starting another build on my laptop, the difference in the time it took is amazing. the sbu was around 7 - 8 minutes on this one, and 1.5 on the laptop. and i really appreciate all the assistance i have received from all of you, it has been fantastic. i just hope i am not being too much bother.
Last edited by sfzombie13; 04-22-2014 at 09:47 AM.
Reason: typo
you may be correct, it looks like what the error says. now for one more question: can i just go an install it now? once again, i think it is no due to following the order exactly, but i am going to try it anyway. just to get done with this one, i am still going to work on the other one. worst case, it doesn't work and i blow the folder to start again. no biggie, now that i know how much time i saved on the laptop. it was more convenience on the desktop because i just left it on all the time and didn't have to worry about forgetting to reset something correctly. small price to pay. thanx for the quick answer.
eta: ok, it worked, i got the interactive kernel setup, did a make install and now am stuck on the part about copying the ...bzinstall to root. it's not there. i guess i will find out how important that is in a few minutes.
Last edited by sfzombie13; 04-22-2014 at 10:12 AM.
Reason: got a little further
i did and it didn't boot, said unrecognized file system. i made a boot usb when i installed slackware, but it didn't work. looks like i have to boot from a live cd and reload the mbr to get into it. or just reinstall everything and start over. either way, i think i will try to rescue it later, off to work now, i mean work i get paid for. thanx for the assistance, i can't wait til i get to building on my laptop. soon as i get home this evening. man, this shit is very addictive, but i am learning so much. my opinion is this book should serve as a linux class in college, it is perfect to explain the intricacies of the os.
i did and it didn't boot, said unrecognized file system.
Maybe you need to review the kernel config for the filesystems that are enabled.
Quote:
Originally Posted by sfzombie13
i made a boot usb when i installed slackware, but it didn't work. looks like i have to boot from a live cd and reload the mbr to get into it.
Until you get the a permanent bootloader arrangement made, consider downloading one of the various live CDs such as Knoppix, Super Grub Disk, System Rescue CD, GParted Live CD, and so on. Anything with a boot menu that will drop to a GRUB prompt. From there, typing manual GRUB commands to emergency boot any system is easy. That Super Grub Disk may even boot your LFS system for you. Anyway, everybody should have some kind of way to emergency boot for that day when the bootloader gets busted.
Quote:
Originally Posted by sfzombie13
can i just delete the linux-3.13.3 directory and start again?
You always can do that. In fact, until you enter make install_<something>, nothing has happened outside of the linux-x.x.x build directory. And even after installing a kernel, it is easy to remove. The stuff we manually copy to /boot simply can be deleted. Everything else goes to folders in /lib/modules and /lib/firmware. Delete the folder in /lib/modules that corresponds to the unwanted kernel. I always leave the /lib/firmware folder as is no matter what kernels I delete. I recommend against deleting a good and working kernel until you have booted into a new good and working kernel.
Distribution: LFS 9.0 Custom, Merged Usr, Linux 4.19.x
Posts: 616
Rep:
You could try a general purpose kernel off of a live CD of some kind. That would at least get you into the system. Just grab a big one that's got almost everything built in... A gentoo minimal CD is likely to have a 3.12.x - 3.13.x kernel on one of the last few versions.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,150
Rep:
First few times I made LFS I cheated and used the slackware huge config for the kernel, it's got just about everything in it including the kitchen sink!
yeah, it was a bit of a letdown, but not really. it was the same thing when i went to school for networking. since i was pretty smart, the instructors let me figure things out on my own, which in turn, freed them up to help the students who needed more help. and i learned so much about troubleshooting, i got a job working level 2 tech support for ameriprise financial. which in turn taught me so much more about troubleshooting. that is another reason why i would go for days sometimes trying to figure something out before posting a question here.
i do have my favorite live cd, ophcrack, which i use for partitioning more than anything, but it serves well as a rescue disk. i did use the option to make a rescue usb stick when i installed slackware, but for some reason it didn't work. anyway, i am taking the evening off and trying to catch up on my laptop, sitting on the couch hacking is nice after spending a week and a half in the basement shop. i am going to have a long day tomorrow, so i will try it in the evening, see if i can get that system up. i know it is just missing a couple of boot files, the vmlinuz or whatever and another one. when i got to the part about copying them to the boot folder, it said file not found. i should have stopped there, but went for it anyway. once i get them in, i think it will be fine.
I'm with Keith, and honestly I still cheat and use Slackware's Huge kernel. Really, Slackware's kernel is a one shot kill all kernel.
You have to have the file systems compiled into the kernel, not as modules.
Just grab Slackware's /testing Huge kernel 3.11+ config, copy it to your kernel source directory as .config, and run make oldconfig against it selecting the recommended default options.
Huge has everything you'll ever need, even though it's bulky, it's comprehensive in what it supports.
thanx reaper, will do. so that means basically blowing out the old folder, as it is not a working kernel, there would be no need to keep it. to me, it is all about the learning experience, not the build so to speak. i just saw this as finally submersing myself into it and learning. if i am going to sell support, i had better be good. by the way, is there any remote assistance software you recommend, like teamviewer? i am looking into that as well, but personal reviews are always preferred as a starting place. and i still need to strip the headers and use the ones in the book, correct? sometimes what seems to be an obvious thing is not so obvious.
As far as remote assistance... usually just about any VNC server/client setup or even LogMeIn-Linux would do, though I'm not sure if LogMeIn-Linux has a 64-bit client for Linux and I think it's terminal only, no GUI.
TigerVNC is probably your best bet though you'll want to make sure the person on the other end has the same package for TigerVNC, but I think it does support remote X sessions and terminal sessions also with secure channels.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.