Gregory Haerr

Hello @Vutshi, > This setting broke compilation for me: > kbd-scancode.c:136:5: error: ‘xtkb_scan’ undeclared here (not in a function) > xtkb_scan, /*mode = 0*/ This is a result of having...

> Meanwhile I have a suspicion that disabling the new options > CONFIG_SYS_DEFSHELL_SASH > does not restore the original sh You're right - fixed in #1337.

> bios keyboard doesn't bring luck for me:bios keyboard doesn't bring luck for me > It doesn't respond to a single key in English or Russian register It seems perhaps...

> The program interrogates the keyboard in a loop and prints what was typed in. As you have probably seen, ELKS uses an identical method to poll for and read...

> Apparently, READ BACK command is missing in 8253, whatever it means. I'll have to check. Could you try running the test with the two lines inserted as described above?...

> Maybe it didn't respond to the keyboard in the first place because it was stuck. Anyway, now it happens before booting is complete. Definitely strange. It seems we are...

Something else which seems strange... is it just me or does the computer always seem to stop working when the ELKS cursor gets to the bottom line? Perhaps change the...

Also notice in first printk, and also the second-to-last line in screenshot above: the "kbd poll" is missing the first letter: it says "bd poll". The TTY output drops the...

> What are these bioshd(0) messages? I saw them even on my Intel Core 2 Duo running this test build of ELKS: These are BIOS floppy read retry messages: CHS...

Here is what the screen should look like. Make sure you "make clean; make". Attached is also the config file I'm using. [config.small.zip](https://github.com/jbruchon/elks/files/8952545/config.small.zip)