Lfs 7.7 boots to green background non inactive shell
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.
Lfs 7.7 boots to green background non inactive shell
Okay so I've got most of the bugs ironed out, but when I boot, lfs opens a shell, ribs some scripts, then the console background turns green. And then nothing. No login shell. Not even an inactive , just the green background of the script. What?
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
insmod ext2
set root=(hd0,1)
menuentry "GNU/Linux, Linux 3.19-lfs-7.7" {
linux /boot/vmlinuz-3.19-lfs-7.7 root=/dev/sda1 ro
}
inittab
Code:
# Begin /etc/inittab
id:3:initdefault:
si::sysinit:/etc/rc.d/init.d/rc S
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
su:S016:once:/sbin/sulogin
1:2345:respawn:/sbin/agetty --noclear tty1 9600
2:2345:respawn:/sbin/agetty tty2 9600
3:2345:respawn:/sbin/agetty tty3 9600
4:2345:respawn:/sbin/agetty tty4 9600
5:2345:respawn:/sbin/agetty tty5 9600
6:2345:respawn:/sbin/agetty tty6 9600
# End /etc/inittab
What configuration did you use to build your kernel? Did you use the automatic 'defconfig' which generates the default kernel configuration, or did you import one from another distribution like your host (Ubuntu maybe)?
Did you at any time adjust or tamper with any of the configuration files, like /etc/sysconfig/rc.site?
i did make defconfig by default and then when that crashed my lfs, I went back and enabled a bunch of things based on the error and lspci(oh and disabing uevent), like sata, nvidia, amd, thunderbolt, android, etc.
Import from ubuntu? I can do that?
Save it to your /sources directory with everything else, then:
Code:
cp -v /sources/config-huge-3.18.11.x64 /sources/linux-3.19/.config
make olddefconfig (This will update everything to 3.19)
Then build and install the kernel as normal. It will install a lot of extra modules and support vectors, but you might have accidentally enabled a bad setting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.