[BIOS not Mageia]keyboard inactive on Grub2 menu, but ok on

Hello again all.
Yes more problems (I will open another one as well on locale)
Okay, this problem started out of the blue last weekend in amongst other problems/re-boots I was having when LibreOffice and my printer both disappeared from my system (separate problems but fixed now)
Anyway, during one of these problems I re-booted, and tried to press Enter on the Grub2 menu to boot Mageia - and found that the KB wouldn't work. I have had other instances where my wired KB suddenly won't work so I unplug/replug and all is good - but not this time. I had to wait for the default 30secs for Mageia to boot and then at the login screen I was able to use my KB to login and use my system as normal!????
So, now I cannot select anything else on the Grub2 menu at re-boot! So I have no access to booting any previous version of the kernel or my Windows partition or anything!
I have even tried a completely, brand new KB in a separate USB port and the same thing happened - so it's not the KB.
I have no idea what caused this nor how to fix this.
Any help, as always, greatly accepted.
Yes more problems (I will open another one as well on locale)
Okay, this problem started out of the blue last weekend in amongst other problems/re-boots I was having when LibreOffice and my printer both disappeared from my system (separate problems but fixed now)
Anyway, during one of these problems I re-booted, and tried to press Enter on the Grub2 menu to boot Mageia - and found that the KB wouldn't work. I have had other instances where my wired KB suddenly won't work so I unplug/replug and all is good - but not this time. I had to wait for the default 30secs for Mageia to boot and then at the login screen I was able to use my KB to login and use my system as normal!????
So, now I cannot select anything else on the Grub2 menu at re-boot! So I have no access to booting any previous version of the kernel or my Windows partition or anything!
I have even tried a completely, brand new KB in a separate USB port and the same thing happened - so it's not the KB.
I have no idea what caused this nor how to fix this.
Any help, as always, greatly accepted.