Stuck without PS/2 keyboard...

[hat]

I recently did a BSEL mod on the machine with my Celeron 430 in it, and I decided to clear the CMOS to start fresh and see what I got when I poked around in the BIOS... after I booted the system, I was greeted with a funny error message saying that a 200MHz FSB processor was installed, but not supported by the system, asking me if I wanted to boot at 266FSB with reduced performance. Y to continue, N to shut down. Problem is, it doesn't recgonize my USB keyboard at this point, as this message comes up before anything else happens. I don't have a PS/2 keyboard anywhere, nor do I have a USB -> PS/2 adaptor. Wat do?

Took a picture of the message for the lulz:

 

[FordGT90Concept]

Buy a cheap PS/2 keyboard. I'd say the lion's share of USB keyboards often aren't initialized until after the BIOS options are past. USB, therefore, is useless in trying to access the BIOS menus. PS/2 always works without fail.

If you know someone that hordes old computers, they might have a few PS/2 keyboards they will let you have for free or cheap.

 

[hat]

I can get one as early as tomorrow... but I would rather find a solution for it now.

 

[Tatty_Two]

Unfortunatly, I think you will have to wait then, as you have probably gathered, by resetting CMOS you have by default set "enable legacy USB support" to disable and therefore without a PS2 keyboard you are knackered.

With it enabled, immediatly on Bios boot you get keyboard use so even error messages can be dealt with.

 

[Thrackan]

Seriously? There's no USB>PS/2 adapter to be found anywhere? Those things like spawn in piles of hardware.

 

[hat]

Unfortunatly, I think you will have to wait then, as you have probably gathered, by resetting CMOS you have by default set "enable legacy USB support" to disable and therefore without a PS2 keyboard you are knackered.

With it enabled, immediatly on Bios boot you get keyboard use so even error messages can be dealt with.

I suppose so. However, this poses the question... what reason can be found on land, sea, the stars above and everything in between for not having that enabled by default?

Seriously? There's no USB>PS/2 adapter to be found anywhere? Those things like spawn in piles of hardware.

I have one, but it's got a mouse symbol on it. I tried plugging my keyboard into it, and the adapter in the keyboard ps/2 slot for the hell of it, but it didn't work.

 

[FordGT90Concept]

PS/2 and USB are not natively compatible. Those adapters that come with mice are designed specifically for the mouse they came with (although it is likely different mice from the same manufacturer will work with the same adapter).

 

[Tatty_Two]

I suppose so. However, this poses the question... what reason can be found on land, sea, the stars above and everything in between for not having that enabled by default?



I have one, but it's got a mouse symbol on it. I tried plugging my keyboard into it, and the adapter in the keyboard ps/2 slot for the hell of it, but it didn't work.

Not sure, perhaps with legacy USB support enabled but with a PS2 board plugged in it wouldn't work? Ohhh and I am going to move this to general hardware I know you like me to tell you beforehand!

 

[hat]

Borrowed my uncle's PS/2 keyboard and sorted things out. Interestingly enough, legacy USB support WAS enabled in the BIOS by default. Is there a certain port the keyboard has to be plugged into for it to work, or is it that the keyboard can be the only USB device plugged in at the time, or both? Or is it just that whether USB legacy support is enabled or not, processor related errors are prompted before anything USB related loads?

 

[newtekie1]

I would guess that prompt is happening before USB support kicks in, since the processor is probably one of the first things initialized, long before the USB controller in the POST process.

 

[FordGT90Concept]

Or is it just that whether USB legacy support is enabled or not, processor related errors are prompted before anything USB related loads?

I think it has everything to do with load order. PS/2, being part of the core BIOS framework, loads very high in the order (among the first things to load). USB, being an add on, loads later. Whether or not USB devices work depend if USB initilizes before you need it or not. I'd say about 90% of the time for me, it is not.

The USB port shouldn't matter nor how many USB devices are plugged in. The BIOS is only programmed to handle certain USB devices (namely keyboard and hard drives).


I doubt this problem will be fixed until UEFI becomes mainstream. For the record, I don't like EFI (it's basically a DRM wet dream) but that looks to be the only proposal that is getting any acceptance in the near future.

 

[newtekie1]

I think it has everything to do with load order. PS/2, being part of the core BIOS framework, loads very high in the order (among the first things to load). USB, being an add on, loads later. Whether or not USB devices work depend if USB initilizes before you need it or not. I'd say about 90% of the time for me, it is not.

The USB port shouldn't matter nor how many USB devices are plugged in. The BIOS is only programmed to handle certain USB devices (namely keyboard and hard drives).


I doubt this problem will be fixed until UEFI becomes mainstream. For the record, I don't like EFI (it's basically a DRM wet dream) but that looks to be the only proposal that is getting any acceptance in the near future.

On modern motherboards I have never had a problem with using a USB keyboard. I could do away with my PS/2 keyboards if it wasn't for Pre-2010 systems...

 

[Frick]

On modern motherboards I have never had a problem with using a USB keyboard. I could do away with my PS/2 keyboards if it wasn't for Pre-2010 systems...

+1. When overclocking and stuff and it basicly stops at the same place it still works. This is kinda wierd.

Oh, and USB->PS/2 have to be an active adapter afaik.

 

[hat]

For the record, I don't like EFI (it's basically a DRM wet dream) but that looks to be the only proposal that is getting any acceptance in the near future.

do go on...