ssh logs but no prompt (2013.03-armv5te)

[icy6210]

More than a year ago I put Archlinuxarm (ARMv5TE) on a ICYBOX NAS6210 (jack) http://archlinuxarm.org/forum/viewtopic.php?f=27&t=2618 and I used it as a backup drive and print server (Cups). Ithas always worked fine until a few days ago. In fact, after the installation of "systemd-sysvcompat" to make the system 100% systemd the problems began.

Problem
--------
1) Can't print:
My laptop sees the network printer on the server jack (lpstat-a 2030), the server accepts the job and assigns a number, but not printing.
The network works, then I connect to the print server (jack: 631) with the browser and cups tells me that there's a job waiting for data. The process stops there, the job will never be printed. With other client computers the same thing happens.

2) Can't open an interactive ssh session with the server jack:
$this->bbcode_second_pass_code('', '
| $ Ssh-v root @ jack
| [...]
| Debug1: Next authentication method: password
| Root @ jack's password:
| Debug1: Authentication succeeded (password).
| Authenticated to jack ([192.168.11.3]: 22).
| Debug1: channel 0: new [client-session]
| Debug1: Requesting no-more-sessions@openssh.com
| Debug1: Entering interactive session.
')
It all ends here, no prompt, the keyboard does not respond except for ending the session (enter ~.)
Instead accepts commands. For example $this->bbcode_second_pass_code('', '$ ssh-v root @ jack 'poweroff'') turns the server down.

In this home network where archlinuxarm is, there are 3 other pc on the same router, two with linux and one windows and everyone can establish ssh connections between them thus exclude external problems.

Solutions brought
-------------------
a) Thinking that with the update and installing systemd-sysvcompat I messed around too much, I again repartitioned the usb stick, formatted (ext2) and reinstalled ex-new ArchLinuxARM ARMv5TE-latest.tar.gz (March 2013).

b) Miscellaneous Changes to the sshd_config file.

c) By starting sshd on request (sshd.socket)

None of these aims has changed the problem, better or worse. I do not know which way to go, the problem does not seem authentication and this would exclude (?) PAM but do not know what other systems are at stake.