Hi

I think you will find that the book refers to chapter 7.2+7.3 I would carry on with chapters 7.4 onwards

Ok Ok I am almost there I guess ...
prompt says now : kurt login:
problem was that I 've putted my hostname between brackets <kurt>, so this was causing errors at boot
Now I still have the problem that nothing appears on screen when using the kbd.
what I type on the keyboard for inputting the username at login is not shown on screen ; enter is working because after hitting the enter button it asks for password
but I am not able to log in anyway with the strings I try to type
someone?

K.

Post your /etc/inittab please

Hi

Well maybe the only thing left is the kernel I know you had probs with the kernel and used host kernel but maybe the problem lies in there, dont how, maybe someone has another thought.

well well I discovered something new!
when switching to other tty numbers I can type and login!!!
only tty1 is not working for some reason; and also I configured following the LFS manual everything for nl_BE but the keyboard mapping is wrong. Its in qwerty and I need azerty ..
anyway Keith here's my initab file config:
# 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

All is good then

If you're still using that initial ram disk (nothing wrong with that if you like it), you probably just have something in the kernel compiled as a module when it should be built in and available early during booting. You probably could figure out what it is and get rid of the initial ram disk, but I guess that's optional.

Well you already discovered the problem its on tty1 so just change the line in your inittab that refers to tty1, from to:Now you have a working bootable system you can get the custom kernel built which will hopefully get rid of any other minor problems.

HI Keith

yeah this was also my first thought .. but unfortenately this is not working
removing this option cleans only the boot info text i see on the login screen
typing is still not working for tty1
I wish I was never started with building a LFS system :-)
I don't sleep anymore :-p

Kurt

It's possibly related to the hosts kernel/initrd when you build your own kernel it may disappear if not you may have to just live with it.

Sleep? Who needs sleep when you've got your very own custom linux?

I finally found the solution in a thread on internet !!! So happy it works all described problems are solves in one shoot :-)
I would like to share what it was. As I mentionned before all was done in Vmware
SCSI drivers where enabled in kernel but on top of that u have also to enable the following for booting in Vmware environement:

Device Drivers --->[*] Fusion MPT device support --->
<*> Fusion MPT ScsiHost drivers for SPI
<*> Fusion MPT ScsiHost drivers for FC
<*> Fusion MPT ScsiHost drivers for SAS

Thanks to all for willing to help me. I've learded a lot anayway with all those problems

Cheers
Kurt

Hi all,

Just wanted to post and say, 7 1/2 years later and using the latest stable build of LFS (lfs-9.0-systemd), I experienced the same initial error as the OP upon trying to boot the new system.

Kurt's solution above is still relevant and worked for me with the 5.2.8 kernel - so big thanks to him, as well as the other posters that helped him get to the solution (although he read it in another thread, but may have given up without their support).

I intend to email the maintainers of LFS to suggest adding this note to the guide.

Cheers all,

mev

Anything needed to boot the system should be built right in the kernel image or a properly configured initramfs environment (and if building your own custom kernel for your own system, you shouldn't want that... distributions do things differently to support diverse hardware configurations). If you choose MPT Fusion for the disk controller in Vmware (default these days?), then you need that driver in kernel.

This is kernel configuration 101.