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.
Strange. Have you posted on the lfs-support@linuxfromscratch.org list?
The other thing that springs top mind is to run /sbin/ldconfig, even if you have no modules. This creates certain files (modules.dep notably) and without that, inspection of System.map will throw an error.
Just an additional note (yes, I know this thread is closed!): I've had exactly the same problem in LFS6.4 with a lovingly hand-crafted kernel and (just like gazza1z) I worked exactly from the book. System.map-($uname -r) is present in /boot AND I soft-linked it to /boot/System.map.
I built LFS 6.3 last year in a similar manner with no problems at all (so it's unlikely I've been an idiot this time).
Unfortunately (according to the klogd manual page) there are some drivers that require the map, so I can't just ignore it (and I hate unexplained things in my distro anyway). There's been no subsequent Internet posting that solves this issue, so I guess I'll have to trawl through the source code for klogd next :-(
Making an all static kernel is bad practise. It's unneccessary overhead which slows things down, and clogs memory. You cannot pass any options to any module. The sound instructions, for one, suggest an all modular sound setup. I am sure you are tripping up something silly in the kernel. I imagine you can check the LFS archives and find a similar thread, where this is explained.
the gurb errors 15 and 17 i was getting were due to an incorrect /boot/grub/devices.map file (which is what led me to this thread).
i initially thought it was my System.map file too- but i eventually discovered the problem to lie with devices.map and once rectified grub booted normally.
it was strange b/c i could edit the grub entries during boot and use tab completion to specify the kernel image file and even an initrd.img- so i considered this confirmation that these files actually existed and were being found.... so why wouldnt grub boot to them? well- after changing boot disks and kernel it turned out some of my kernel device names changed for hd0 & hd1 for sda, sdb, hda, etc. using slax to boot i mounted my boot partition and hand edited /boot/grub/devices.map to reflect the correct devices and made sure my /etc/fstab coincided.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.