[SOLVED] First time installing LFS: Boot hangs after "md: ...autorun Done"
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.
Thanks for the replies! I get no other errors. Just information about what devices are found such as hard drives, USB-devices, etc. The screen just freezes and the computer can only be turned off via pulling the power plug.
I will take a look at the Kernel once more. I did all the configurations that the LFS book recommended me to do. I will recheck them. Are there any others I should check? I noted the BLFS book has a part about mesa drivers, so maybe I will do that as I have an AMD CPU.
You didn't say what version of LFS you are building, sysvinit or systemd based, or what host you are using. If recent sysvinit based (udev extracted from systemd instead of separate eudev package) don't forget this line in your fstab:
- believe it or not, that can cause the issue you are describing. Also, make sure you have the required radeon GPU firmware in /usr/lib/firmware. Look in dmesg output of the host for the exact firmware being used or just install all of the radeon firmware.
Hi! Thanks for the replies. I haven't had much time to work on this, but perhaps in the weekend. This is my fstab, which should be correct as I copy & pasted it from the book. I am building the sysvinit and I followed all the steps in the book.
Hi! Thanks for all the responses. I installed the firmware and I was able to get past the original problem. I tried booting LFS and my PC was no longer freezing on the same line. Instead, I got a nice kernel panic about "unable to mount root fs", which is a better situation as I now have some output. I need to do some investigating on what causes this error. I did notice that the output (see image below) shows some problems on the hard-drive I have LFS installed on (/dev/sdb) as it lists only one partition instead of the three. I posted my fstab above and I did notice that my swap partition was listed as /dev/sb2 instead of /dev/sdb2, which I fixed. This didn't fix the kernel panic, but good progress anyways. I did check the kernel configuration that ext4 was ticker on with *. Any tips regarding this new issue is also appreciated :-) Thank you!
I did notice that the output (see image below) shows some problems on the hard-drive I have LFS installed on (/dev/sdb) as it lists only one partition instead of the three.
This sounds weird. What does
Code:
fdisk -l /dev/sdb
tell, if your're running it from the Hostsystem (the one you used to build LFS)?
/dev/sdb doesn't show any partitions. If it isn't a missing driver problem in the kernel, the drive order may be changing when a usb drive is plugged in. To work around this use lsblk -f to find the uuids of the lfs install and change the fstab to use uuids something similar to this
Hi all and thank you all for your continuous support, great community! I have gotten the installation working now. I tweaked some of the kernel settings and messed about with my fstab -file. I also installed initramfs. It is unclear to me which one of these worked though the important thing is that I now have a running system and I can continue inspecting and learning it.
To recap, overall I had to do the following things:
- Went through the kernel configuration again and compiled it
- Installed firmware for my GPU and CPU
- Triple checked my /etc/fstab file
- Installed initramfs
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.