User-reported bug: Pi 3 simulator showed boot output but keyboard input was ignored — the shell was effectively read-only. Root cause: velxio-init's bash redirect was `</dev/console >/dev/console`. From userspace, /dev/console is write-only — it is the kernel's printk target and accepts writes (so we saw boot output fine) but reads return EOF / block forever. Bash never saw a keystroke and the user couldn't type. Fix: read AND write through /dev/ttyAMA1. The 12 s devtmpfs-wait already in velxio-init guarantees the device node exists by the time the shell-respawn loop runs. setsid -c still gives bash a controlling terminal so PS1, job control, and Ctrl-C all work. Manifest version bumped to 2026-04-21+ttyAMA1; sidecar SHA check invalidates the cached SD on every velxio backend so the fix lands without an operator dance. |
||
|---|---|---|
| .. | ||
| app | ||
| scripts | ||
| sdk | ||
| tests | ||
| .env.example | ||
| Dockerfile | ||
| debug_qemu.py | ||
| mcp_server.py | ||
| mcp_sse_server.py | ||
| requirements.txt | ||