Miod, Following the suggestion you gave, I looked at the comkbd_init() function in sys/arch/sparc64/dev/comkbd_ebus.c, it seemed that in order for the "no keyboard" statement to be printed that code tried and failed the keyboard reset sequence five times. The sequence itself looked to attempt to send the reset command, check 1000 times (waiting 1 millisecond [1000 microseconds] between) to see if the keyboard was in the reset state. Next, it checked if the keyboard was "ready", using similar logic. Finally, it sent the layout request and waited using similar logic.
Using your assumption that the keyboard was not handling the reset sequence (or being slow about it), I increased the delay period from 1 millisecond (1000 microseconds) to 3 milliseconds (3000 microseconds) for each of the three portions of the comkbd_init() function (each call to DELAY() in comkbd_init() function). Rebuilt the kernel, and gave it a try. I am happy to report that I have booted the computer three times with the SV 125 converter (and a PS2 keyboard hooked up), and each time it was properly handled and worked well. Next step (later in the week) I will hook it up to the PS2 KVM and get X running (I will report results) Not sure if that would be a proper fix to include in the source code, I will let the proper people decide that. I can provide a patch file if anyone is interested or someone can easily follow what I did above. Thank you very much for the information. On Sat, Mar 12, 2011 at 5:33 PM, Miod Vallat <[email protected]> wrote: >> You are correct in the fact that this particular one (SV 125) is not >> powered separately. It works fine in Solaris as well as at the "Forth" >> {ok} prompt. >> >> I have not hooked it up to a KVM yet, at this point, I am testing it >> with a normal PS2 keyboard and mouse. I have tried multiple keyboards. >> >> It should be noted as well that when I use the machine with the PS2 >> keyboard that I cannot enter any text, but when I shut it down remotely >> I can then see text that I tried to enter with the PS2 keyboard at the >> "Forth" {ok} prompt. >> >> If anyone happens to remember which combinations (machine & converter) >> have worked, please let me know. > > I have been playing with the official Sun PS/2 adaptor brick in the > past, without any issues (can't tell you the Sun partnumber at the > moment, that device is still packed somewhere in a box). > > If the OpenBSD kernel reports there is no keyboard, it is likely that > the adaptor does not correctly handle a Sun keyboard reset sequence (or > with relaxed timing). You might want to tinker in > sys/arch/sparc64/dev/comkbd_ebus.c comkbd_init() to figure out what > causes the code to consider the reset sequence did not get acknowledged > properly. > > Miod
