Thinkpads Forum

I posted this on the Lenovo forums, and it has been ignored, no help at all:

When trying to install a Seagate GoFlex Thunderbold adapter (model SRD0001) I get an error "This Thunderbold Device is not certified for PC use. I contacted Seagate, and they sent me a link to download a driver: Asmedia 106x SATA Controller. When looking at Device Manager under "IDE ATA/ATAPI Controllers" it has a code 12, saying this device cannot find enough resources. Without this Asmedia 106X SATA Controller driver, I get the same code 12, with the "Standard AHCI 1.0 serial ATA controller.

As the title says, this is with my new W540, and Windows 7 OS.

I appreciate your help!

Did you try rebooting the machine with the adapter connected to it?

dr_st wrote:Did you try rebooting the machine with the adapter connected to it?

Yes. Thank you for your suggestion.

Takeda wrote:code 12, saying this device cannot find enough resources

I believe this is a problem with platform firmware, A.K.A. "BIOS". I expect several more revisions to be released: there is a general lack of software quality sanity these days, from Lenovo and pretty much the whole world of consumer electronics, so I fully expect more problems to be found and later fixed. If BIOS 2.08 is not a fix, then perhaps inform Lenovo, they might not be aware of this.

W540 BIOS Version 2.08 was made available yesterday.

someotherguy wrote:These files should be posted to support website next week but I provide them in my dropbox for now.
W540 BIOS 2.08 ISO package (flash from CDROM):
https://dl.dropboxusercontent.com/u/622 ... uj05us.iso

automobus wrote:

Takeda wrote:code 12, saying this device cannot find enough resources

I believe this is a problem with platform firmware, A.K.A. "BIOS". I expect several more revisions to be released: there is a general lack of software quality sanity these days, from Lenovo and pretty much the whole world of consumer electronics, so I fully expect more problems to be found and later fixed. If BIOS 2.08 is not a fix, then perhaps inform Lenovo, they might not be aware of this.

W540 BIOS Version 2.08 was made available yesterday.

someotherguy wrote:These files should be posted to support website next week but I provide them in my dropbox for now.
W540 BIOS 2.08 ISO package (flash from CDROM):
https://dl.dropboxusercontent.com/u/622 ... uj05us.iso

Thank you Bill! I would have thought posting this problem on the Lenovo forums would have let them know about the problem, but they have completely ignored my post! So much for customer satisfaction!

So, is the problem resolved or not?

dr_st wrote:So, is the problem resolved or not?

I installed BIOS Rev. 2.08, and I'm still getting code 12 with the Thunderbolt device driver. So, problem is still not resolved.

Thank you for asking!

I don't know if the problems are related, or not, but I noticed the sound breaks up also. It does this on all sources (internet, or HDD music files).

I have posted this on Lenovo Forums, with the Thunderbolt problem, and still no replies to my posts.

Let's try a few things to possibly help with the diagnosis:

1) In the Device Manager, choose View --> Devices by connection.
2) Locate the troublesome device (which complains about not having enough resources).
3) In the properties of this device, the Resources tab, you should see the memory ranges allocated to this device. Can you post the numbers?
4) Repeat the procedure in step (3) for the bridge/root-port directly above the troublesome device in the hierarchy. What are the memory ranges allocated to that?

And on an unrelated topic - are there any BIOS settings related to Thunderbolt that you can find and try playing around with?

dr_st wrote:Let's try a few things to possibly help with the diagnosis:

1) In the Device Manager, choose View --> Devices by connection.
2) Locate the troublesome device (which complains about not having enough resources).
3) In the properties of this device, the Resources tab, you should see the memory ranges allocated to this device. Can you post the numbers?
4) Repeat the procedure in step (3) for the bridge/root-port directly above the troublesome device in the hierarchy. What are the memory ranges allocated to that?

And on an unrelated topic - are there any BIOS settings related to Thunderbolt that you can find and try playing around with?

Thank you dr_st!

Here is the screen image with the information you requested, I hope you can see it ok:

http://bob-ayers.smugmug.com/photos/i-6 ... qJQ-X3.jpg

Thank you for your reply.

According to your image, there is plenty of memory reserved, so it should not be a problem. However, there is no I/O space reserved at all, and my guess is that the device thinks it's an issue. But it may not be.

There is a directive from Microsoft which explains how to prevent device from requiring I/O if it's not needed:
http://msdn.microsoft.com/en-us/library ... 85%29.aspx

It appears that drivers have to specifically include this line to avoid requesting I/O. After some investigation, it appears that some older drivers from ASMedia (for example, version 1.4.1.0) had this line, which was later removed.

Now it may be that it was removed because of causing a real issue somewhere, but it may also be an accidental omission. No way to know but to try:

Try downloading the WHQL driver version 1.4.1.0 from this page and see if it works for you:
http://www.station-drivers.com/index.ph ... 40-asmedia

With that said, this is just a guess. The fact that the device initially came up with the "not certified" warning may mean that some flows are not fully supported, and you may run into some problems, even if you can get it to work... Or it may not mean anything. It's hard to know what "certification" really stands for.

I say, give it a shot, but be wary, and if the drive does work, try it out for a while before actually storing anything important there.

Edit:Changed link

dr_st wrote:Thank you for your reply.

According to your image, there is plenty of memory reserved, so it should not be a problem. However, there is no I/O space reserved at all, and my guess is that the device thinks it's an issue. But it may not be.

There is a directive from Microsoft which explains how to prevent device from requiring I/O if it's not needed:
http://msdn.microsoft.com/en-us/library ... 85%29.aspx

It appears that drivers have to specifically include this line to avoid requesting I/O. After some investigation, it appears that some older drivers from ASMedia (for example, version 1.4.1.0) had this line, which was later removed.

Now it may be that it was removed because of causing a real issue somewhere, but it may also be an accidental omission. No way to know but to try:

Try downloading the WHQL driver version 1.4.1.0 from this page and see if it works for you:
http://www.station-drivers.com/index.ph ... 40-asmedia

With that said, this is just a guess. The fact that the device initially came up with the "not certified" warning may mean that some flows are not fully supported, and you may run into some problems, even if you can get it to work... Or it may not mean anything. It's hard to know what "certification" really stands for.

I say, give it a shot, but be wary, and if the drive does work, try it out for a while before actually storing anything important there.

Thank you for the information dr_st! I tried looking for the driver you suggested from the link you posted, and had trouble locating it. The drivers seem to be listed by date, can you tell me the date the driver is listed under?

I don't know if this will help you with my problem, but I dumped out the Hardware I/O resources, since you have identified an I/O resource problem:


0x00000000-0x0000000F Direct memory access controller OK
0x00000000-0x0000000F PCI bus OK
0x00000010-0x0000001F Motherboard resources OK
0x00000020-0x00000021 Programmable interrupt controller OK
0x00000024-0x00000025 Motherboard resources OK
0x00000028-0x00000029 Motherboard resources OK
0x0000002C-0x0000002D Motherboard resources OK
0x00000030-0x00000031 Motherboard resources OK
0x00000034-0x00000035 Motherboard resources OK
0x00000038-0x00000039 Motherboard resources OK
0x0000003C-0x0000003D Motherboard resources OK
0x00000040-0x00000043 System timer OK
0x00000050-0x00000053 Motherboard resources OK
0x00000060-0x00000060 Standard PS/2 Keyboard OK
0x00000061-0x00000061 System speaker OK
0x00000062-0x00000062 Microsoft ACPI-Compliant Embedded Controller OK
0x00000064-0x00000064 Standard PS/2 Keyboard OK
0x00000066-0x00000066 Microsoft ACPI-Compliant Embedded Controller OK
0x00000070-0x00000071 System CMOS/real time clock OK
0x00000072-0x00000077 Motherboard resources OK
0x00000080-0x0000008F Direct memory access controller OK
0x00000090-0x0000009F Motherboard resources OK
0x000000A0-0x000000A1 Programmable interrupt controller OK
0x000000A4-0x000000A5 Motherboard resources OK
0x000000A8-0x000000A9 Motherboard resources OK
0x000000AC-0x000000AD Motherboard resources OK
0x000000B0-0x000000B5 Motherboard resources OK
0x000000B8-0x000000B9 Motherboard resources OK
0x000000BC-0x000000BD Motherboard resources OK
0x000000C0-0x000000DF Direct memory access controller OK
0x000000F0-0x000000F0 Numeric data processor OK
0x000003B0-0x000003BB Intel(R) HD Graphics Family OK
0x000003C0-0x000003DF Intel(R) HD Graphics Family OK
0x000004D0-0x000004D1 Programmable interrupt controller OK
0x00000800-0x0000087F Motherboard resources OK
0x00000D00-0x0000FFFF PCI bus OK
0x000015E0-0x000015EF Motherboard resources OK
0x00001600-0x0000167F Motherboard resources OK
0x00001640-0x0000165F Motherboard resources OK
0x00001800-0x0000187F Motherboard resources OK
0x00003000-0x00003FFF Intel(R) 8 Series/C220 Series PCI Express Root Port #3 - 8C14 OK
0x00004000-0x00004FFF Intel(R) Xeon(R) processor E3-1200 v3/4th Gen Core processor PCI Express x16 Controller - 0C01 OK
0x00004F80-0x00004FFF NVIDIA Quadro K2100M OK
0x00005000-0x0000503F Intel(R) HD Graphics Family OK
0x00005060-0x0000507F Intel(R) 8 Series Chipset Family SATA AHCI Controller OK
0x000050A0-0x000050A7 Intel(R) 8 Series Chipset Family SATA AHCI Controller OK
0x000050A8-0x000050AF Intel(R) 8 Series Chipset Family SATA AHCI Controller OK
0x000050B0-0x000050B7 Intel(R) Active Management Technology - SOL (COM3) OK
0x000050B8-0x000050BB Intel(R) 8 Series Chipset Family SATA AHCI Controller OK
0x000050BC-0x000050BF Intel(R) 8 Series Chipset Family SATA AHCI Controller OK
0x0000EFA0-0x0000EFBF Synaptics SMBus Driver OK

I just found this, sounds familiar:

https://communities.intel.com/message/182478

Takeda wrote:Thank you for the information dr_st! I tried looking for the driver you suggested from the link you posted, and had trouble locating it. The drivers seem to be listed by date, can you tell me the date the driver is listed under?

Holy cow, they changed their site and the old links no longer work.

This is the new link:
http://www.station-drivers.com/index.ph ... 40-asmedia

You can also download the driver from here:
http://drivers.softpedia.com/progDownlo ... 05511.html

dr_st wrote:

Takeda wrote:Thank you for the information dr_st! I tried looking for the driver you suggested from the link you posted, and had trouble locating it. The drivers seem to be listed by date, can you tell me the date the driver is listed under?

Holy cow, they changed their site and the old links no longer work. Have no idea where they keep the old drivers now.

Try downloading the driver from here:
http://drivers.softpedia.com/progDownlo ... 05511.html

Thank you again dr_st. Lenovo is now investigating my problem, so I think I will wait to see what they find. I appreciate your help.

Do let us know how it turns out in the end.

dr_st wrote:Do let us know how it turns out in the end.

I certainly will.

update:

I have been exchanging e-mails with Lenovo support. The engineer I'm working with tried a LaCie Thunderbolt drive on his W540, and it worked fine. LaCie also uses the Asmedia 106X driver, but it is a different level than the Seagate Asmedia 106X driver. He tried the Seagate Asmedia 106X driver, and got the ERROR CODE 12, like I'm getting. The next step, I want to take my W540 to Lenovo, and try the LaCie Thunderbolt drive on my W540. If it works, I'll be returning this Thunderbolt Adpapter to Seagate, if they can't provide me with a fix.

What do you mean by "the driver is a different level"?

Did you try the driver I pointed you to (version 1.4.1.0)?

dr_st wrote:What do you mean by "the driver is a different level"?

Did you try the driver I pointed you to (version 1.4.1.0)?

Thank you again Dr_st! I did not try driver version 1.4.1.0. The Lenovo L2 team solved my Seagate Thunderbolt adapter problem! The Asmedia ASM106X SATA controller driver has to be 1.3.9. This driver from Seagate was 2.0.4

Good to know!

Next time you may try to tell us in advance when you post in the forum that you have no intentions of actually trying the solutions we propose. Some people may decide not to waste their time in such a case.

With that said, I did learn a bit about Thunderbolt and drivers in general thanks to this thread, so thank you.

dr_st wrote:Good to know!

Next time you may try to tell us in advance when you post in the forum that you have no intentions of actually trying the solutions we propose. Some people may decide not to waste their time in such a case.

With that said, I did learn a bit about Thunderbolt and drivers in general thanks to this thread, so thank you.

Dr_St, I'm sorry if I offended you by not trying the driver you suggested. One advantage I have is living close to Lenovo, and once the L2 team was involved with my problem, I decided to see what they found on the problem. So, I took my W540 to Lenovo, and it was a pleasure to meet with the L2 team.