0

Hell Everyone,

I built a server with the mentioned motherboard. I installed Windows Server 2008 R2 Enterprise on this server.

IPMI is integrated on the motherboard with its own dedicated NIC. I've got that NIC configured with its own IP address. I can remote into it using IPMI, and I can remotely control the server settings before booting the OS ( BIOS, RAID configuration, etc). When the OS boots, I lose the mouse and keyboard. I cannot use the keyboard or mouse when installing the OS either. So the Keyboard and Mouse only work when no OS is loaded. Once the OS loads I lose it - that is my problem.

I've been doing some research and trying a few things, but I have not been successful in fixing this issue. I may be wrong, but based on the things I've found online, it seems that the problem could be caused by the way the OS handles USB.

The server is headless. There is no keyboard, mouse, or monitor plugged into it. When I boot up the OS and remote into it, I cannot see a mouse or keyboard listed in the Device Manager. Based on what I've read, it seems that the OS should detect a mouse and a keyboard when connecting remotely via IPMI.

The following are the solutions I've tried. Nothing has worked so far:

I've updated the firmware of the IPMI component to the latest firmware - 1.33. I made sure that the mouse mode was set to Absolute (Windows OS). I've loaded the factory defaults several times. I've enabled Port64h/60h Emulation under the USB settings in the BIOS. I've disabled USB legacy support in the BIOS. I made sure the firewall wasn't blocking IPMI (disabled the firewall).

And that's about it.

I've found threads in some forums from people having the same issue as me, but they were not running the same OS. They were either running Linux or FreeBSD. Most of them fixed their problem by selecting the right mouse mode (Linux in their case). There was one other that solved the problem by disabling USB Mass Storage mode. He stated "When I set it to disable USB Mass Storage when no image is loaded, the ukbd came alive, and I'm typing this on the IPMI Console. " source: http://freebsd.1045724.n5.nabble.com/IPMI-Console-No-luck-once-OS-is-booted-td3967868.html

I suspect the solution described in the previous paragraph is somehow related to my problem. I've found several threads on the internet with issues describing the same problem, but none of them were with Windows Server 2008 R2. Again, I may be wrong, but it seems like that could be the issue. I just don't know how I go about applying a solution in Windows Server 2008 R2.

In any case, I could use your expertise. Maybe I am missing something, or maybe I'm on the right track.

Your help is much appreciated.

Thank you in advance,

LDelgado
  • 9
  • 1
  • 2
  • 1
    Have you tried contacting Supermicro for support and/or ensuring that any Windows specific support drivers for the hardware are installed as well? – user48838 Aug 06 '11 at 18:32
  • I've contacted Supermicro already. They suggested some basic things I had already tried. The only new thing they suggested I try was to enable the Port64h/60h Emulation. I did that, but it didn't fix the problem. They have not got back to me since then. So I posted here in hopes that someone would have some ideas I could try. – LDelgado Aug 11 '11 at 01:08
  • What occurs when the OS is booted in "safe" mode? – user48838 Aug 11 '11 at 06:49
  • Actually, I am able to select safe mode (the keyboard works on the "Windows Did not shut down successfully" screen). When the system boots up in safe mode, I Can't use they keyboard or mouse still though. – LDelgado Aug 12 '11 at 00:32
  • Then it does come down to driver issues with the hardware. – user48838 Aug 12 '11 at 05:25
  • Did you find a solution to this? I seem to have the same problem... – SnAzBaZ Feb 11 '13 at 12:26
  • I've had issues like that on other motherboards. Plugging the keyboard into a different USB controller fixed it. I think i had it plugged into a USB 3.0 controller and it didn't work but when I plugged it into a port with a USB 2.0 controller it did. Couldn't be that could it? – hookenz May 08 '14 at 05:33
  • have you trying install the chipset drivers on Supermicro website? is there any unknown device in device manager – Will Nov 15 '14 at 04:31

3 Answers3

1

Based on information thus far, maybe two possible options:

  1. Press Supermicro for the appropriate driver/driver setting
  2. Look into disabling the correct existing driver(s) from your current configuration
user48838
  • 7,431
  • 2
  • 18
  • 14
  • Well, based on what I've read online, and as stated on the link I provided, it seems that disabling USB Mass storage would be a solution. That is not an acceptable solution in my case because I need access to storage devices via USB. I'm still working with SuperMicro Support. They haven't got back to me yet. I will post back if I find a solution to this. In the mean time, if anyone has any ideas, I would appreciate any feed back. Thanks, – LDelgado Aug 14 '11 at 18:15
0

We have the same issue on Windows 2008 R2. And we have "Unknown USB Device" in Windows Device Manager. After pressing several tens on "Reset USB" on IPMI Web interface the device is detected correctly and mouse and keyboard start to work.

Sergei
  • 1
0

I had a very similar issue to the original post. During the boot of the OS I would lose control of the mouse and keyboard. The keyboard and mouse would only work when no OS was loaded. I could get into the BIOS settings and change them using the IPKVM. After loading the OS and attempting to activate the IPVKM using IPMI View the video would display but the mouse/keyboard would not be available. In the Windows Server 2008R2 device Manager a USB device would appear as an "unknown USB device".

Setup:

X7DBE motherboard AOC Sim1u+ IPMI with IPVKM and dedicated LAN Windows 2008 Server R2

My motherboard has 3 PCI-E Slots: Slot 1 is x8, Slot 2 is x8 and Slot 3 is x4. I had an Adaptec 1430SA in Slot 2 and an Adaptec 1430Sa in Slot 3. Slot 1 was empty.

Last night, in order to free up slot 3 for a sound card, I moved the Adaptec Sata Controllers to slots 1 and 2.

The moving of these cards to slots 1 and 2 fixed the IPKVM issue. After the OS loaded the keyboard and mouse now both worked correctly.

User X
  • 1