So, if I understand you correctly, you've let the emulator run, booted something, halted, and then you get this error? In that case we probably need to re-initialize the keyboard state at some point. I'll look into that.
Camiel.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) Booted es40 with SCSI to test the "waiting to poll message"
2) After unsuccessfull boot, I quit the emulator then start it with IDE configuration, but emulator hang at "Testing the network".
3) Quit es40 and rebooted Windows
4) Start again es40 with IDE configuration, and got the keyboard problem.
5) Quit es40 and start it again, and all is working.
Some points:
1) I noticed (but I have to verify better) if I boot with SCSI, then boot with IDE I have the hang.
2) The keyboard error happened two times, and all the times I didn't press any keys or move the mouse during the boot. Maybe this could be unrelated.
regards,
fausto
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Self Test 00000006906c
kbd: OUTB set and command 0xaa encountered
READ(60) = 38
service_keyboard: key in internal buffer waiting
SYM: start SCSI bus reset.
SYM: end SCSI bus reset.
Normally there's more output from keyboard initialization... in this case I think the process is stuck on internal buffer.
I hope this could be useful for you.
regards,
fausto
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just to add some useful info, I typed some keys when the SDL window was selected, during the startup, and maybe the internal buffer was not cleaned for some reason...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
after a system restart, during the startup I receive a keyboard wake_up error, and on DOS console I had:
kbd: OUTB set and command 0xaa encountered
At alpha prompt, if I try to type something, the chars are not displayed, and on DOS console I have these errors:
internal keyboard buffer full, ignoring scancode.(1f)
internal keyboard buffer full, ignoring scancode.(9f)
internal keyboard buffer full, ignoring scancode.(23)
internal keyboard buffer full, ignoring scancode.(a3)
internal keyboard buffer full, ignoring scancode.(1f)
internal keyboard buffer full, ignoring scancode.(9f)
internal keyboard buffer full, ignoring scancode.(23)
internal keyboard buffer full, ignoring scancode.(a3)
internal keyboard buffer full, ignoring scancode.(1f)
internal keyboard buffer full, ignoring scancode.(9f)
The environment is VisualStudio 2005 (Windows XP).
regards,
fausto
So, if I understand you correctly, you've let the emulator run, booted something, halted, and then you get this error? In that case we probably need to re-initialize the keyboard state at some point. I'll look into that.
Camiel.
Hello Camiel,
exactly these are the steps:
1) Booted es40 with SCSI to test the "waiting to poll message"
2) After unsuccessfull boot, I quit the emulator then start it with IDE configuration, but emulator hang at "Testing the network".
3) Quit es40 and rebooted Windows
4) Start again es40 with IDE configuration, and got the keyboard problem.
5) Quit es40 and start it again, and all is working.
Some points:
1) I noticed (but I have to verify better) if I boot with SCSI, then boot with IDE I have the hang.
2) The keyboard error happened two times, and all the times I didn't press any keys or move the mouse during the boot. Maybe this could be unrelated.
regards,
fausto
Hello Camiel,
I got some debug info about keyb wakeup error:
Self Test 00000006906c
kbd: OUTB set and command 0xaa encountered
READ(60) = 38
service_keyboard: key in internal buffer waiting
SYM: start SCSI bus reset.
SYM: end SCSI bus reset.
Normally there's more output from keyboard initialization... in this case I think the process is stuck on internal buffer.
I hope this could be useful for you.
regards,
fausto
Just to add some useful info, I typed some keys when the SDL window was selected, during the startup, and maybe the internal buffer was not cleaned for some reason...
Hello,
Brian did a patch for the keyboard controller that might fix this; could you try it with fresh code from CVS?
Camiel.
Hello Camiel,
now it's all ok!
Thanks!
Fausto