[QEMU] PS/2 Mouse does not recieve input if mouse is moved or keyboard is pressed during initialization

[fido2020]

Haven't been able to reproduce outside of QEMU.

If the mouse is moved or keyboard is pressed during ~1 second that the PS/2 controller is being set up, the mouse will not work at all until the system is rebooted.

[peggy-48]

I think the problem resides in the kernel driver, or in the SeaBIOS implementation it has.

Haven't been able to reproduce outside of QEMU.

If the mouse is moved or keyboard is pressed during ~1 second that the PS/2 controller is being set up, the mouse will not work at all until the system is rebooted.

Well, this is a problem with the controler, and not the kernel itself (I presume).

You see, when your computer boots up, the PS/2 controller needs a brief window of time (~1 second just like you said) to initialize and configure the mouse. If any input through any device is received during this exact time frame, then the controller can become confused, leading to the mouse being unusable after the boot, and requires a restart.

A temporary solution is to just reboot the system, and there is no problem with that, it absolutely works, but then at the same time, it's also not the best way to deal with this problem. So some better solutions (I presume) are to:

• Try using a different PS/2 mouse (a very simple and basic fix, but sometimes that might not work too if the situation is different).

• Try using some other mouse other than a PS/2 mouse (correct me if I am wrong, because I don't know the reason for you guys to work with a PS/2 mouse, so my opinion might be incorrect).

• Try not to use fast boot (if available in this OS) because that might interfere with the mouse's usability after the fast boot, and it might lead to the mouse not functioning at all and requires a restart.

Other than these troubleshooting techniques, I don't think other techniques that might also work are that ideal, so these two are your best odds.

As far as I know, this OS is not bad at all and pretty stable for a startup project and the Readme provides good info about this project, but even if these techniques don't work, then there is a solid chance that there might be something wrong with the kernel just like @peggy-48 stated.

[peggy-48]

Worse is that it might be a messy BIOS implementation. Try on another computer in this case and give me the results.