Ml350G6/Blade driver failure/compatibility Issues - Windows 10X (USB2, USB Syopsys Controller, IPMI

[RrichardD]

[Dr Rick Finney]

 MS update malfunctioned and took-out my Z400 (April 20 - see MS Forum), so I fired-up a spare ML350G6 (easier to move/set-up than the DL380G6's).

 I noticed the USB driver first did not work for drives (HDD/SSD/USB-stick), then only as USB one (1) - at ultra slow speed (less than 8Mb/minute - standard doc/text/image transfer rate to main onboard drives - although the ML350G6 is supposed to be USB2.

1. Came to HP support, followed instruction to try Win update/then update via Device Manager ... which ended in win update/Device manager saying they had no compatible drivers/nothing installed (error messages #28 & 31) - then sending me back to the manufacturers (HP) for drivers.

 Rather frustrating, and going in circles tends to cause dizziness. Have HP go a URL (their's) for the USB/USB2 drivers to suit ML350G6/Blade series/DL380G6 servers?

2. Exactly the same thing happened for the USB Syopsys Controller (code 31); IPMI interface (code 28), several other devices, and the standard (microsoft) vga adapter driver (on this thing, as I recall the onboard is ATI).

 Pointers to where the drivers for these components might be found - at HP - would be appreciated, because they are not at Microsoft./MS Update ... and seemingly not likely to be.

 I believe the components in question probably serve some good or function - elsewise HP would not have them on the system/motherboard.

 ... On the way in I noticed a listing of with HP units are compatible with the increasingly schizophrenic offerings from MS (ie. Windows 10x, and the next assault on our sanity (Windows No-X?). I am inclined to say - based on function/performance ...

ML350G6/Blade series are not cross compatible with Windows 10x ... if you try higher functionality (anything over what an old 486DX100 could do).

 Any help or useful pointers would be appreciated (as always). Yes to the Linux guys - but I do not have time just now to shift everything to redHOT or Umbantu; while trying to "Roll Back" (Server 2014) killed the Z800.

I use the Assorted Candies emergency procedure (keep packets in the stationary cupboard). Everytime MS product stuff something (monthly thing), I make a fresh coffee, then open a packet of candies ... much a few and try to imagine I'm off somewhere fishing, or sunbathing, etc.

Does help.

Cheers all - stay safe and stay healthy ...

Rick.

[Paul_Tikkanen]

Hi:

HP split into two companies a few years ago.

HP supports PC's, printers, tablets and calculators.

HP Enterprise (HPE) supports servers, switches, routers and tape drives.

You may also want to post your question on the HPE community support forum -- proliant servers section...

https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bd-p/itrc-264#.Xr15lNaSnGg

[RrichardD]

Hi Paul, Good to see you are well ... and smiling (icon). I'll do as you suggested (and await your thoughts). Post issue here however - I selected Windows 10X and it posted as 8.1 ... might be a crossed link/html code error.

 Scroll down to the Legacy USB post (as stated - not stealing your glory, but I had looked at the forums posts on the USB2/Legacy issues (I know it comes down to the Microsoft difficulties, HP and other main manufacturers are having with them), as well as checked/read-up on the HP manuals (Ml350G6 and Blades); so tried to recount what I'd read/tried two days ago). Thought the guy might be hanging-out, and no one seemed about, so I thought something is better than nothing.

 Also the guy over us, with the HP screen issue ... more my end of the game {smile}. A spike can occur in circumstances described (no big enough to do real damage), that can scramble the chips/roms a bit (need normal reset). In control systems (radar), we usually turn the thing off for 30 minutes ... take it away from the UPS and plug it into a normal mains socket, switch it on and see if it resets (bare - not connected to computer/systems). 9/10 times it will reset and recover, I think because the sine wave of the UPS has not got the kick/grunt to trigger a reset event.

 Might try suggesting that ...

 Cheers,

 Rick.