unable to boot from lfs 6.2 after kernel compilation
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.
unable to boot from lfs 6.2 after kernel compilation
dear list,
- i have successfully compiled all the modules as mentioned in lfs 6.2 book.
- the kernel is successfully compiled with few warnings.
- i have the following partitions
- i have no clue why my lfs would not boot.
in the boot up process the kernel is unable to uncompress the bzImage (which is previously produced by the compilation of source kernel). as mentioned by the lfs book, i have copied this bzImage into the lfs directory /boot.
- after failing to uncompress the bzImage of the target lfs system, my machine reboots and again grub appears. i dont have any error message displayed like kernel panic as it seems I am struck in a too early starge.
unable to boot from lfs 6.2 after kernel compilation
dear daws,
many thanks for your help. as suggested i have copied bzunzip from /bin to /usr/bin. still my kernel never seems to uncompress. besides i am not sure about the problem, as its based on my assumption. could there be any other reason besides this.
This is true, I didn't notice that. But I think something else is going on. grub seems to find the kernel alright, otherwise it would be a different error, not "unable to decompress".
Oh I found something else. Apparently all kernels are compressed with gzip, bzImage does not mean bzip2 compressed (apparently it gets put into "High memory" or something, went straight over my head anyway). So make sure all gzip related tools are in /bin not /usr/bin.
unable to boot from lfs 6.2 after kernel compilation
To
Vitalie Ciubotaru - For your kind attention to this thread
Daws - For your patience and continous attention
Together sorry for this long message
Why we want LFS
---------------
- We need our own custom kernel without distribution specific images, logo and availablity of OS commands
- We have a specific slow but new hardware for mass production
- the hardware is 8" chinese b/w monitor, SChrome VIA Vga Card, VIA PC 1500 barebone
problem in reproducing the code
-------------------------------
my fc3 vga is a little bit shaky making the system hang if too many scrolling is done (in firefox, etc and whatever), making me impossible to cut and paste my menu.lst or grub.conf. what i have tried to do is reproduce the code here. forgive me if they are not exact. (dear vitalie, in my menu.lst there is no white space, its only in my mail. sorry for the not typing exactly as it appeared.)
what we did differently other than what is mentioned in lfs book
---------------------------------------------------------------
- i have two seperate partitions one for / for target lfs in hda5 and another for /usr in hda6. hd5 and hd6 resides in extended partition hd4. hd1 for fc3 and hd2 for swap. hd3 is not represented by any partition.
anything looked strange ?
-------------------------
- except kernel compilation which had few warnings there was no other noticable error or warning for cause of concern during the entire lfs unpack, configure and make process.
- kernel was recompiled after removing the source/linux-2.6.16.27 directory completely after unsuccessful booting and rebooting of lfs
output during boot process (not exact representation)
-----------------------------------------------------
I have seen things like this before, on my own system more often than not.
I understand what you mean now, where the system hangs at
Uncompressing kernel ...
The problem may lie in the configuration of the kernel. It is possible that you have forgotten to compile in support for something key in the system. Maybe the filesystem (which should not be a module), or support for the chipset, or you have enabled some experimental code (what I did) by accident... The list goes on. I'm afraid you have to go through the configuration again, recompile and hopefully, after some trial and error, you will find what went wrong.
Sorry I couldn't be more specific. Hope it works out...
I have seen things like this before, on my own system more often than not.
mate. though its not a good thing, this is the only hope for me now :-)
I understand what you mean now, where the system hangs at
Quote:
Uncompressing kernel ...
i am expecting this but this text never appears.
Quote:
The problem may lie in the configuration of the kernel. It is possible that you have forgotten to compile in support for something key in the system. Maybe the filesystem (which should not be a module), or support for the chipset, or you have enabled some experimental code (what I did) by accident... The list goes on. I'm afraid you have to go through the configuration again, recompile and hopefully, after some trial and error, you will find what went wrong.
Actually I have selected all the option during the previous compilation. Now I have select only certain things that I feel is absolutely necessary. yet no success. I guess i need to make another try and another and another ... :-(. Also I am thinking of making a diff between the .config of LFS and the .config of my FC3 host to see what goes wrong in my compilation.
i have noted some warnings in my compilation and again this is not an exact representation of the output.
fs/bio.c - in function bio_alloc_bioset
warning idx may be used uninitialized in this function
fs/eventpoll.c - in function .............
fs/isofs/namei.c
fs/nfsd/nfsctl.c
fs/udf/balloc.c
fs/udf/super.c
ipc/msg.c
ip/sem.c
sound/core/oss/route.c
i368/math-enu/fpu_entry.c
i have an interesting output when i compiled bzimage and module seperately. the output is
Quote:
Root device is (3,5)
Boot Sector 512 bytes
Setup is 7007 bytes
System is 1942 kb
Kernel: arch/i368/boot/bzImage is ready(#1)
I hope i can give some more clue.
Quote:
Sorry I couldn't be more specific. Hope it works out...
No problems mate, in fact you are my only hope now in the entire community. I wonder why there is no body to reply in the lfs-support@linuxfromscratch.org. may be its due to my poor english.
I have recompiled and reduced my warnings during compile to a bare minimum. I have read in the redhat manual that certain older bios will not support booting of linux if the hdd cylider is above 1024. So i have backed up the lfs to a new hdd (hdc) in the beginning cylinder. however, i am unable to boot as my grub is not able to find the stage1 located in /boot/grub/
i entered the chroot environment and my grub output is below when i type setup (hd1,0).
Code:
checking if "/boot/grub/stage1" exists ... no
i am sure that stage1 exists in that location. now i guess if i my grub detect my stage1, i can see if the cylinder on which my linux resides is a problem or not.
OK this is getting a bit beyond my ability now, all I could offer is guesses. However I do suggest that you ask a mod nicely to move this thread (maybe rename it too) to a different forum, maybe Linux - Kernel or Linux - General. Both forums receive more traffic than the LFS forum and perhaps regulars there will be able to help.
There is thread around here somewhere about this, lfs-support do not normally ignore requests for help, it may be due to their strict spam filters. I do not believe they ignored your message due to poor english.
PS. raskin seems to know what he is talking about so it would be in your best interests to follow his advice and post the infomation he and others request if you can.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.