Image location: http://autobuilder.yoctoproject.org/pub/releases/1.5_M4.rc2/machines/qemu/qemumips/ Git rev: master/5745e45b18e5099e94b4d5a73bc97dc6d4cdc91f Steps: 1. Download the kernel and rootfs from the autobuilder 2. Boot up the image with command: runqemu qemumips vmlinux.bin core-image-sato-sdk-qemumips.ext3 3. Click the Terminal icon to launch the terminal. Can not input anything in the terminal. This issue also happens when using nfs boot: runqemu nfs vmlinux.bin rootfs
confirm that this works with core-image-minimal. I tested that here.
(In reply to comment #1) > confirm that this works with core-image-minimal. I tested that here. This issue happens in the application "Terminal" on the sato desktop. So please use a sato or sato-sdk image to test.
That wasn't my question. I know it happens with sato, the point being that before uprev each and every qemu machine was booted and logged into. Something in SDL + qemu + the new kernel is grabbing the inputs and not passing them to X. If you boot that same image with nographic, you'll be able to log in. And I want that confirmed.
I tried this via a VNC connection which I think removes the SDL, and it still failed to have input. I also tried a 3.8 kernel with the userspace and it worked and a older userspace with the newer kernel (3.10) and it failed, so I am thinking more and more kernel related.
I have the fix. Pull request arriving shortly.
Terminal input OK in 1.5_M4 rc3 build
Verified, terminal app input is ok and working. Image used: core-image-sato-sdk-qemumips Image location: http://autobuilder.yoctoproject.org/pub/releases/1.5_M5.rc8/machines/qemu/qemumips/ Commit: 529bf977e956175bd8405ebffc88194192e44740