Jump to content
5 posts in this topic

Recommended Posts

I'm having a rather frustrating issue with my USB keyboard. Whenever I restart or shutdown Leopard and then turn the computer back on I get a "Keyboard error/Keyboard not found" error during POST. This does not happen when I reboot using Windows or Linux. It does occur when I don't shut my computer down properly using Linux however. I'm not sure what could be going wrong. This is a fresh installation of 10.5.7. This error has been occurring since day 1 of this installation. My hardware is as follows:

 

Motherboard: MSI K8N SLI-F (with Nforce4 chipset)

Processor: AMD x2 4600+

Graphics: Nvidia 8800GT 512mb

RAM: 3GB (Not sure which brand, I think maybe Corsair)

 

I'm not sure if you guys need any other hardware specs or not. If I unplug my computer for 7 seconds and then try to boot again everything is fine. After 7 seconds a little green light on my motherboard near the network interface turns off. At that point the computer boots as if nothing ever happened. Any ideas as to what could be going wrong or how I can fix this?

Link to comment
https://www.insanelymac.com/forum/topic/201355-keyboard-error-on-reboot/
Share on other sites

Ugh. A DSDT patch is essentially new programming for your BIOS. I can't be sure because I've never run into this problem myself, but I'm betting that this is a conflict between the Mac OS X kernel and your BIOS. Anyway for figuring out a DSDT patch first you should look at this. Then you can look for an original DSDT for your motherboard/BIOS and try to figure out how to modify it. Mind you this is most likely beyond your ability, but you might be able to get someone else to look at it and figure out what to do. Of course there's a decent chance I'm completely wrong and a DSDT patch won't fix it. But to answer your original question, I don't think there is any quick fix or kext you can install to fix this.

 

I took another look at your original post and I noticed you said this happens when you reboot linux improperly... I would boot up in verbose mode and then shut down to see if there's anything unusual that comes up in the output. I can't remember if those messages are logged in kernel.log, but it might be worth a look to see if the system is crashing on shutdown.

×
×
  • Create New...