Unknown devices on X301 w/ Server 2008 Enterprise x64

[jollerbarn]

Hi,

I'm running Server 2008 x64 on my X301, and I'm currently having trouble getting certain devices to work. The devices in quetion are the ethernet card (yes, strangely Lenovo's x64 Vista driver doesn't work) and two unknown devices.

Do any of you have experience in getting these devices to work on x64? Or maybe just know which devices the unknown devices are?



Rgds.
Jesper[/img]

[donzoomik]

Show the PCI ID's or use Everest.

[sutrakhk]

I have the same experience when installing XP in X301

I would like to ask did you install the sound driver yet? It seems the first PCI serial port would be sound device. (In XP, I have to install KB888111 first)

The PCI simple communications Controller would be the driver of TPM/AMT.

For the ethernet driver, can you find it in intel's site or in Windows update?

[jollerbarn]

Good stuff sutrahk,

I found the Ethernet driver here:
http://downloadcenter.intel.com/filter_ ... &submit=Go!

Strangely though, it doesn't work. Windows is firmly confident that the driver isn't the one I'm looking for. Is it possible that the ethernet card in my X301 is not Intel 82567?

About the sound driver I already have Conexant High Definition SmartAudio 221. Sound is working too, so it must be something else.

I've already drivers for Trusted Platform Module 1.2, so are you sure the Simple Communication controller is TPM?

[jollerbarn]

Hardware ID's for the Ethernet Controller are:
PCI\VEN_8086&DEV_10F5&SUBSYS_20EE17AA&REV_03
PCI\VEN_8086&DEV_10F5&SUBSYS_20EE17AA
PCI\VEN_8086&DEV_10F5&CC_020000
PCI\VEN_8086&DEV_10F5&CC_0200

Hardware ID's for PCI Serial Port are:
PCI\VEN_8086&DEV_2A47&SUBSYS_20EC17AA&REV_07
PCI\VEN_8086&DEV_2A47&SUBSYS_20EC17AA
PCI\VEN_8086&DEV_2A47&CC_070002
PCI\VEN_8086&DEV_2A47&CC_0700

Hardware ID's for PCI Simplet Communication Controller are:
PCI\VEN_8086&DEV_2A44&SUBSYS_20E617AA&REV_07
PCI\VEN_8086&DEV_2A44&SUBSYS_20E617AA
PCI\VEN_8086&DEV_2A44&CC_078000
PCI\VEN_8086&DEV_2A44&CC_0780

[jollerbarn]

Everest for Ethernet Controller:
PCI Enhed Intel 82567LM ICH9M Gigabit Network Connection

Everest for PCI Serial Port:
PCI Enhed Intel GL40/GM45/GS45/PM45 Chipset - Keyboard Controller Style (KCS) [B-3]

Everest for PCI Simple Communication Controller:
PCI Enhed Intel GL40/GM45/GS45/PM45 Chipset - Host Embedded Controller Interface 1 (HECI1) [B-3]

(Sorry for spam!)

[jollerbarn]

Update: I got the ethernet driver working by forcing Windows to use Intel's driver for Intel 82567LM-4.

It works although I had to click through a dozen of warnings.

[sutrakhk]

I've already drivers for Trusted Platform Module 1.2, so are you sure the Simple Communication controller is TPM?

I think it would be Intel AMT, but I cannot find the 64bit version

[jollerbarn]

If that's all it is I could care less about the driver really

I got the ethernet card working, and that helps a lot! Thanks for the help.

[donzoomik]

PCI serial is AMT
http://www-307.ibm.com/pc/support/site. ... MIGR-70313
The last on should be AMT part 2.
http://www-307.ibm.com/pc/support/site. ... MIGR-70317

[jollerbarn]

PCI serial is AMT
http://www-307.ibm.com/pc/support/site. ... MIGR-70313
The last on should be AMT part 2.
http://www-307.ibm.com/pc/support/site. ... MIGR-70317

I tried 'em, but they do not support Server 2008. "This operating system is not supported".

[crazeazn]

hate to bump a super old thread, but what display driver did you use for the intel 4 series express chipset? I just got my 32 bit install of 2008 r2 server running...but the display keeps crashing on me,

[crazeazn]

ahh opened youtube and now the darn thing wont boot.

[masterus]

Hi,

Why don't you use some virtualisation software (VMware/Citrix) tu run W2K8
It's faster and easier way and you don't have to worry about drivers

Rgds
Robert

[erik]

I just got my 32 bit install of 2008 r2 server running...but the display keeps crashing on me,

there's no such thing as 32-bit server 2008 R2.   all versions of 2008 R2 are 64-bit.   perhaps you're trying to install the wrong driver because of this?

i ran 2008 R2 enterprise on my X301 with all drivers installed and running correctly.   my recommendation would be to install drivers manually through devmgmt.msc rather than running any .exe installers.   this mitigates most installation headaches.

if you can't find a driver, try letting windows update supply one.   however, from memory i simply used win 7 x64 drivers for everything and it worked without issue.

[vtohthree]

i ran 2008 R2 enterprise on my X301 with all drivers installed and running correctly.   my recommendation would be to install drivers manually through devmgmt.msc rather than running any .exe installers.   this mitigates most installation headaches.

if you can't find a driver, try letting windows update supply one.   however, from memory i simply used win 7 x64 drivers for everything and it worked without issue.

Sorry to resurrect an old thread, but when you mention to manually install through devmgmt.msc, as in going into the device manager and individually going into the properties of each device and "selecting driver" location for each device?

I'm in a similar boat, I installed server 2k8 r2 on my T500, the wifi didn't even work out of the box, it's just frustrating to install anything without jumping through tons of security hurdles.

[The Solutor]

Why not use the thinkvantage updater to install all the drivers automagically ?

[vtohthree]

Because TVSU doesn't work. I did some googling but still can't quite get it to work on there. It goes to like 10% and says, "an error occurred", this is with the latest TVSU. Having said that, I was able to install most of the drivers so far by using the device manager. I found that I would have to install each driver individually(it would create a driver's folder) and then in addition to it I would use the Device manager, tedious, but at least it's kind of working.

[erik]

wifi won't work on any 2008 R2 installation unless you install the service in server manager.   that's true of any windows server installation since it's meant to be a server OS, not an end-user workstation OS.

i'd suggest taking a look at win2008r2workstation.com for tips on how to use your server OS for things it wasn't meant to do.

on devmgmt.msc, yes, i was referring to manual driver installations by browsing to the unpacked driver directory.   in many cases this is the only way to get a win 7 driver installed in 2008 R2.

to add to the TVSU point, TVSU doesn't work on server OSes because it's not intended for a server environment.   it has no idea how to handle desktop/notebook drivers in a server OS.   that would require an enormous undertaking since 2008 R2 is not certified for thinkpad hardware.   "automagically" and "server OS" typically don't go hand-in-hand.

[vtohthree]

Gotcha, thanks Erik.

I found out about that site and had the wifi feature installed. I stopped tinkering with the TVSU, I guess I'll just keep on keeping on with device manager, I greatly appreciate the help! =]