After change to mach console, I report that the getty error is not the cause of the keyboard lock. The getty errors continues appearing, but I can using the keyboard in the tty.
Now I have to find the cause of the lock: I've disable the kbd repeater (in other times, this was the cause) and re-enabled hurd-consile, but the problem continues El lun, 16 ago 2021 a las 21:59, Samuel Thibault (<samuel.thiba...@gnu.org>) escribió: > Almudena Garcia, le lun. 16 août 2021 21:32:38 +0200, a ecrit: > > > It rather looks to me like it's the Hurd console which cannot start > for some > > reason, and that's where you want to investigate. > > What do I have to search? I only have access via Rescue Mode > > You can disable the hurd console from /etc/default/hurd-console, so that > you can reboot in non-rescue, and run it by hand. > > That said, easiest to debug such kind of console issues is to run > stuff from ssh, since otherwise you'll most often see your keyboard > non-working. > > Samuel >
