Skip to content
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] Non responsive keyboard after quit #514

Closed
JerichoCross opened this issue Sep 16, 2019 · 3 comments
Closed

[DietPi] Non responsive keyboard after quit #514

JerichoCross opened this issue Sep 16, 2019 · 3 comments
Assignees
Labels

Comments

@JerichoCross
Copy link

Describe the bug
When using the DietPi-based distribution, selecting Quit drops you back to the command line but the keyboard is unresponsive. The keyboard works fine whilst Amiberry is running. The Pi had not frozen, however, because I was able to interract with it via SSH from another machine.

To Reproduce
Steps to reproduce the behavior:

  1. Boot the DietPi-based Amiberry distribution on a Pi 3b
  2. Select 'Quit' in Amiberry
  3. Try to type something

Expected behavior
Normal CLI behaviour - ability to issue commands via the keyboard

Screenshots
If applicable, add screenshots to help explain your problem.

Hardware
Raspberry Pi 3b

@midwan
Copy link
Collaborator

midwan commented Sep 16, 2019

@JerichoCross
This is a known bug, but it's not related to Amiberry itself - it's something to do with the DietPi environment.

In any case, there's an update incoming to bring it up to Buster, so we could make sure this is also fixed there.

@midwan midwan changed the title Non responsive keyboard after quit [DietPi] Non responsive keyboard after quit Sep 16, 2019
@midwan
Copy link
Collaborator

midwan commented Sep 16, 2019

Reported here: MichaIng/DietPi#3104

@midwan midwan self-assigned this Sep 16, 2019
@MichaIng
Copy link
Contributor

MichaIng commented Sep 16, 2019

@JerichoCross
Thanks for your report.

Actually it sounds like being this bug, which has been resolved with DietPi v6.23 already: MichaIng/DietPi#2718

Can you please verify the following:

  • You updated to the latest DietPi version.
  • You boot into Amiberry using the dietpi-autostart Amiberry fast boot (index 6) option, or flashed the RPi Amiberry image which has this setting applied automatically?
  • When exiting Amiberry, no login prompt appears, only a blank screen with a blinking dash at best?
  • Is this changing when you hit Ctrl+Alt+F1 (actively switch to TTY1, if not yet the case)?
  • Is this changing when you run systemctl enable --now getty@tty1 from SSH session?
  • Can you verify systemctl is-active systemd-logind prints active?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants