User login screen is not offered
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Hello.
I know how to solve some connection problems. I can't find enough explanation to understand the cause of this problem!
It seems to loop forever on the user login and network acquisition sequences.
First stage
"try ubuntu before installing it"
This step goes smoothly. The present screen forces you to choose the NOMODESET option. which has become very easy ..
I didn't notice anything abnormal.
Second step
"Install ubuntu"
I didn't notice anything abnormal.
Initially I had chosen not to update the software during installation and to automatically log in the user.
I restarted the installation by asking to update the software during the installation and to propose the user connection grid.
There is no change
Third step
"The normal boot"
The screen proposing to enter the username does not appear regardless of the chosen kernel.
Removing the two "quiet splash" options allows you to see a significant amount of failed and the loop that seems eternal. I even waited over 30 minutes ....
Fourth step
"Boot recovery"
The recovery screen is displayed.
I can do the proposed actions.
Some go wrong.
For example, the fsck command says the partition is "already mounted". I don't think the problem is there.
The most important is the network enable command which does not seem to indicate any errors and which does not activate the network!
Ping 8.8.8.8 says network is not operational
Fifth step
"The start by CHROOT"
This technique allows me to access the log of the installed instance (journalctl -D / mnt / var / log / journald)
and find the first level of errors. Some advice says to dig deeper with the systemctl command but this one does not work in chroot mode.
Sixth step
"The diagnosis".
As the normal boot never ends except by power-off, I used the recovery mode to access the logs of the previous boot.
It is not that easy. I put in .txt files that I will send to you.
I think reading the contents of some of these files will allow you to give me additional commands to find the cause of the problem.
Thanks in advance.
| geole0 (geole0) wrote | #1 |
| geole0 (geole0) wrote | #2 |
| geole0 (geole0) wrote | #3 |
| geole0 (geole0) wrote | #4 |
| affects: | dbus (Ubuntu) → systemd (Ubuntu) |
| Dan Streetman (ddstreet) wrote | #5 |
| Changed in systemd (Ubuntu): | |
| status: | New → Invalid |
Contents of Journalctl