Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I have just finished installing my LFS following the instructions in the book but I must have forgotten something.
My setup is as follows:
Archlinux host system boots in UEFI mode,
AMD processor.
I want to start LFS using archlinux grub. LFS starts up fine and my problem appears as login prompt.
login: is displayed and I quickly see the following message appear:
(udev worker) (202) used greatest stack depth: 12326 bytes left.
This message is followed a few second later by another one: snd-hda-intel 0000:2d:00.4: cannot probe codecs giving up.
When I enter my user name and my password I receive an incorrect login message.
so the CLI is spitting out messages while you still need to log in?
what do you do?
just type over them like they never showed up, like a normal login.
The message has to do with your sound card. It shouldn't prevent you from logging in.
You have received a login prompt so it ought to be OK to enter a login name. I can't remember if you already have a user account at this stage; it's probably safer to log in as root. Then wait for the password prompt and give the root password. You can create a user account later if necessary using the useradd command.
I have the login prompt and I can enter the root login name. Then I receive the password prompt and I can enter the password but I have an ‘login incorrect’ message.
I had also created a user account during the chroot but I have exactly the same problem. So I'm still stuck on the login…
I wonder if my problem is not related to the ‘linux console’ and/or a ‘locale’ problem,
Here is the journalctl:
Quote:
Mar 31 16:50:32 lfs systemd[1]: Startup finished in 21.511s (firmware) + 5.856s (loader) + 2.630s (kernel) + 962ms (userspace) = 30.961s.
Mar 31 16:50:36 lfs kernel: (udev-worker) (203) used greatest stack depth: 12336 bytes left
Mar 31 16:50:51 lfs nscd[271]: 271 recherche fichier surveillé `/etc/netgroup': Aucun fichier ou dossier de ce type
Mar 31 16:51:01 lfs login[268]: invalid password for 'root' *on '/dev/tty1'
Mar 31 16:51:21 lfs login[268]: invalid password for 'root' *on '/dev/tty1'
Mar 31 16:51:29 lfs kernel: snd_hda_intel 0000:2d:00.4: Cannot probe codecs, giving up
Mar 31 16:51:41 lfs login[268]: invalid password for 'root' *on '/dev/tty1'
Mar 31 16:51:53 lfs systemd[1]: getty@tty1.service: Deactivated successfully.
Mar 31 16:51:53 lfs systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
Mar 31 16:51:53 lfs systemd[1]: Stopped Getty on tty1.
Mar 31 16:51:53 lfs systemd[1]: Started Getty on tty1.
Mar 31 16:52:05 lfs login[294]: invalid password for 'root' *on '/dev/tty1'
Mar 31 16:52:27 lfs login[294]: invalid password for 'root' *on '/dev/tty1'
Mar 31 16:52:45 lfs login[294]: invalid password for 'root' *on '/dev/tty1'
Mar 31 16:52:56 lfs systemd[1]: getty@tty1.service: Deactivated successfully.
Mar 31 16:52:56 lfs systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 2.
Mar 31 16:52:56 lfs systemd[1]: Stopped Getty on tty1.
Mar 31 16:52:56 lfs systemd[1]: Started Getty on tty1.
Mar 31 16:54:00 lfs agetty[297]: tty1: invalid character 0x1b in login name
Mar 31 16:54:10 lfs systemd[1]: getty@tty1.service: Deactivated successfully.
Mar 31 16:54:10 lfs systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 3.
Mar 31 16:54:10 lfs systemd[1]: Stopped Getty on tty1.
I wonder if my problem is not related to the ‘linux console’ and/or a ‘locale’ problem,
A good way to test your password for corruption by a bad locale is to type it as a response to the login prompt. Your login name is visible, so you can check that what you see is what you thought you were typing.
A good way to test your password for corruption by a bad locale is to type it as a response to the login prompt. Your login name is visible, so you can check that what you see is what you thought you were typing.
Oh yeah I hadn't thought of that. And having done so tells me that the password I see is the right one
What about logging into your host system, chrooting over to LFS, and deleting the root password from /etc/shadow? Then you should be able to log in as root without a password and you can set a new one.
If the new password misbehaves in the same way, then I can't help you any further!
What about logging into your host system, chrooting over to LFS, and deleting the root password from /etc/shadow? Then you should be able to log in as root without a password and you can set a new one.
If the new password misbehaves in the same way, then I can't help you any further!
that is what I was thinking. just chroot that system then do it again "sam".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
