-
-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | AmiBerry: No login console active when exiting fastboot mode #2703
Comments
Sorry, i forgot to say that i have the problem with the latest Version from DietPi-Homepage i downloaded yesterday. Version 6.22.3 |
@Trigger58 Okay if you tried You did hit |
Good Morning, it seems that in the other boot options the keyboard driver was not loaded or something else. |
UPDATE: |
UPDATE2: I got it to work. Finally. There the steps i did:
It seems that there is something wrong with fastboot. i have the same Problem with normal dietpi Image so could it be that there is fastboot enabled too? |
@Trigger58 You only face the non-functional keyboard after exiting AmiBerry from fastboot mode, right? So on first boot login works but when you install AmiBerry, enable fastboot, then booting into AmiBerry and exiting to console, keyboard does not work?
I guess it has to do with the following:
AmiBerry fastboot is intended to interfere at very early boot stage and skip all the agetty stuff to allow starting that fast. Also preventing
@midwan @Fourdee |
@MichaIng |
@midwan @Trigger58 Could you please try to enable systemd-logind:
Then boot into fastmode (autostart option 6) and test if exiting then brings you into a login prompt. In case it doesn't (getty on TTY1 does not spawn automatically), then you can switch to TTY2 by pressing F2 button. systemd-logind should then automatically spawn a getty (login prompt) there. From there you can revert autostart option. As said first assure that SSH works, just in case. |
@MichaIng |
Hi,
I can Test it. SSH is working all time but i get only access through a PC Tools called FileZilla. The Tools in Dietpi to get access from a PC dont work. I cant get access through them.
I hole that the procedure you wrote works. Otherwise i cant get access to my System anymore.
…--
Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.Am 12.04.19, 15:39, MichaIng <notifications@github.com> schrieb:
@midwan
Possibly systemd-logind does the getty spawn on other systemd.
@Trigger58
You can access the system via SSH right, so e.g. using PuTTY from remote Windows system? Otherwise skip the following, as we then need to get SSH running first.
Could you please try to enable systemd-logind:
systemctl unmask systemd-logind
systemctl --now enable systemd-logind
Then boot into fastmode (autostart option 6) and test if exiting then brings you into a login prompt. In case it doesn't (getty on TTY1 does not spawn automatically), then you can switch to TTY2 by pressing F2 button. systemd-logind should then automatically spawn a getty (login prompt) there. From there you can revert autostart option.
As said first assure that SSH works, just in case.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/MichaIng/DietPi","title":"MichaIng/DietPi","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/MichaIng/DietPi"}},"updates":{"snippets":[{"icon":"PERSON","message":"@MichaIng in #2703: @midwan \r\nPossibly `systemd-logind` does the getty spawn on other systemd.\r\n\r\n@Trigger58 \r\nYou can access the system via SSH right, so e.g. using PuTTY from remote Windows system? Otherwise skip the following, as we then need to get SSH running first.\r\n\r\nCould you please try to enable systemd-logind:\r\n```\r\nsystemctl unmask systemd-logind\r\nsystemctl --now enable systemd-logind\r\n```\r\n\r\nThen boot into fastmode (autostart option 6) and test if exiting then brings you into a login prompt. In case it doesn't (getty on TTY1 does not spawn automatically), then you can switch to TTY2 by pressing F2 button. systemd-logind should then automatically spawn a getty (login prompt) there. From there you can revert autostart option.\r\n\r\nAs said first assure that SSH works, just in case."}],"action":{"name":"View Issue","url":"#2703 (comment)"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#2703 (comment)",
"url": "#2703 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
So i changed autoboot to 6 and made a reboot. Amiberry starts fast. After quitting Amiberry it happens nothing. The bootprocess was killed during start from amiberry so i needed the CTRL-ALT-F2 combo to get access. |
Ok, i have to correct my last answer. Now it seems to work. |
@Trigger58 I think AmiBerry does not really kill the boot process, but it goes on in background, printing to TTY3 (you should see boot process output when pressing F3, if still done). When exiting too fast, I guess systemd-logind is not yet at a stage to spawn on TTY1 automatically. When you hit F2 then I guess boot was already far enough to allow getty spawn by logind. And if you wait a bid longer than it is already when exiting AmiBerry. However long story short:
As well on our pre-installed AmiBerry image(s) we need to have logind unmasked. I can update our RPi AmiBerry image this weekend, only need to know about the install procedure outside of DietPi-Software. |
Okay fix merged for v6.23: #2718
|
Hello,
i tried the following 2 Distros with my RaspberryPi 3b+:
The 1. Distro is working fine and Amiberry runs great but every time i quit amiberry or i try to use another boot option without autologin into console, then i can't use the keyboard.
I get the screen with please enter login to continue but i can't enter anything.
Only if i change in dietpi.txt the boot option 7=Console+auto root login then the keyboard works.
Same problem with the 2. distro.
What i have to do to change all boot options to autologin?
At the moment my only possible way to change a file is with ftp-tool like FileZilla. I copy the dietpi.txt to pc, change it and overwrite the file on pi.
The implemented way that is described at your homepage with root:dietpi@192.168.0.100 don't work too. I tried different IP's ,including the IP that DietPi got from my fritzbox, but no way to get into it. Only FileZilla gets access but with FileZilla i can only transfer files but i can't get access to dietpi-config or another menu with it.
The text was updated successfully, but these errors were encountered: