Re: getty errors in Debian GNU/Hurd over Thinkpad T410. I can't access to tty

[Almudena Garcia]

ups, wait to translate

pruebas@debian:~$ sudo dpkg-reconfigure hurd
Setting up translators: /hurd/exec /hurd/proxy-defpager /hurd/pflocal (+link) inet (+link) inet6 (+link) /hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/password crash-kill crash-suspend crash-dump-core crash.
Creating device nodes: fdln: failed to access 'stdin/0': Not a directory
ln: failed to access 'stdout/1': Not a directory
ln: failed to access 'stderr/2': Not a directory
 fdX stdln: failed to access 'stdin/0': Not a directory
ln: failed to access 'stdout/1': Not a directory
ln: failed to access 'stderr/2': Not a directory
 vcs hdX hdXsY hdXs1Y sdX sdXsY sdXs1Y rumpdisk wdX wdXsY wdXs1Y cdX netdde ethX loopX ttyX ptyp ptyq lprX comX random urandom kbd mousermdir: failed to remove 'shm': Directory not empty
 shmsettrans: shm: Is a directory

El mar, 17 ago 2021 a las 0:51, Almudena Garcia (<liberamenso10000@gmail.com>) escribió:

> dpkg-reconfigure hurd

It shows many errors

pruebas@debian:~$ sudo dpkg-reconfigure hurd

[sudo] password for pruebas:
Setting up translators: /hurd/exec /hurd/proxy-defpager /hurd/pflocal (+link) inet (+link) inet6 (+link) /hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/password crash-kill crash-suspend crash-dump-core crash.
Creating device nodes: fdln: fallo al acceder a 'stdin/0': No es un directorio
ln: fallo al acceder a 'stdout/1': No es un directorio
ln: fallo al acceder a 'stderr/2': No es un directorio
 fdX stdln: fallo al acceder a 'stdin/0': No es un directorio
ln: fallo al acceder a 'stdout/1': No es un directorio
ln: fallo al acceder a 'stderr/2': No es un directorio
 vcs hdX hdXsY hdXs1Y sdX sdXsY sdXs1Y rumpdisk wdX wdXsY wdXs1Y cdX netdde ethX loopX ttyX ptyp ptyq lprX comX random urandom kbd mousermdir: fallo al borrar 'shm': El directorio no está vacío
 shmsettrans: shm: Is a directory

El mar, 17 ago 2021 a las 0:12, Samuel Thibault (<samuel.thibault@gnu.org>) escribió:

Almudena Garcia, le mar. 17 août 2021 00:01:21 +0200, a ecrit:
> 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.

That doesn't mean that getty is not an underlying cause of keyboard not
working the hurd Hurd console: the keyboard might be working in the mach
console but not in the Hurd console. Possibly the Hurd console is locked
altogether actually.

Also, note that getty is very most probably not the cause of the issues
you are getting, it's only the messenger, telling you that the server
side of the console seems to be bogus.

Just to make sure: did you run

dpkg-reconfigure hurd

to make sure that translators are properly set up?

Samuel