Reply
Active Member
migle
Posts: 95
Registered: 08-24-2008
Location: Portugal
0

Re: Help W500 graphics card question

Hi, the_enthuisast,

 

All those issues have previously been debated on this thread.

While no page exists at ATI about this Mobility FireGL V5700, already in August it was possible to find out technical data indicating that this card had the M86 chip with 120 unified shaders (links were posted previously on this thread).

I have previously expressed my feelings against the unfortunate choice of name for this card which might lead people to think it is similar to the FirePro V5700 with 320 cores, which is probably the one you read about.

 

Again, the 320 core chip is a 700 million transistor chip (like the radeon 3870), and there are no 700M transistor chips on 15.4" laptops, NVIDIA or ATI (there is one, the Clevo M860TU, which has GeForce 9800GT and less than 2h battery). Only the 120 core chip, with 30W TDP could fit the heat/power budget of this laptop.

 

BTW, I chose the W500 instead of the 8530w or M4400 exactly because it has switchable graphics. I doubt most graphics professionals actually use the GPU the whole day. For me, it was having a powerful card without the penalty. And it is implicit on the W500 datasheet listing two times for battery life.

 

As to your WEI scores, have you seen how the W500 compares with your FX 570M in the SPECviewperf results veemex posted?

W500 4062-2XG T9400/4GB/WUXGA/ATI M86/Vista 64/Gentoo Linux 64
Active Member
plitskin30
Posts: 17
Registered: 11-01-2008
Location: US
0

Re: Help W500 graphics card question

we need a lot of w500 users !!!

 

this has been really frustrating,   man......  i should have bought macbook pro instead of w500

Associate Member
jlee45
Posts: 21
Registered: 10-17-2008
Location: Toronto, Canada
0

Re: Help W500 graphics card question

maybe... 

but macbook pro sucks....

Active Member
VT-Vincent
Posts: 13
Registered: 09-20-2008
Location: Pittsburgh, PA
0

Re: Help W500 graphics card question

Since the driver update, my Graphics Driver crashing issue has gotten worse, it's happening far more frequently. It's also pretty obvious this card is nothing but a soft-mod at this point. I don't think I'll be hanging on to my W500, or buying Lenovo again. :smileysad:

Administrator
Mark_Lenovo
Posts: 3,056
Registered: 11-19-2007
Location: RTP, North Carolina
0

Re: Help W500 graphics card question

[ Edited ]

All,

 

 

The ATI Mobility FireGL V5700 in the W500 is based on AMD’s M86 GPU which is also used in AMD’s ATI Mobility Radeon HD3650.   It has been noted that these chips share the same device ID of 9591, but OS’s and drivers look at the entire Hardware ID to determine the ID of part.

 

The Hardware ID consists of four parts:

 

1) Device ID

2) Vendor ID

3) Subsystem ID

4) Subsystem Vendor ID

 

The ATI Mobility V5700 and ATI Mobility Radeon HD3650 have different Subsystem ID’s: the Mobility Radeon HD3650 has Subsystem ID’s of 2116 and 2117 depending on the switchable graphics setting, while the ATI Mobility V5700 has Subsystem ID’s of 2126 and 2127.  Some of AMD’s ATI Mobility V5700’s on other laptops do have a hardware ID of 9595 as shown by AMD’s documentation which is the source of some confusion, but even these parts contain the same M86 GPU used in the W500.

 

 

The ATI Mobility FireGL V5700 uses the same physical chip as the ATI Mobility Radeon HD3650 so separate labeling is not needed.  Some users have pointed out that prior ThinkPad’s contained ATI GPU’s that were marked as FireGL’s; this special marking (which added cost to the to the system) is no longer required as Lenovo now uses a more advanced mechanism to differentiate between the chips. Although based on the same GPU, the Mobility FireGL V5700 can use extended workstation features and logic present in the M86 GPU that are not available to the consumer level ATI Mobility Radeon HD3650.

 

In addition, the drivers used by the ATI Mobility FireGL V5700 contain workstation specific speed and stability enhancements for use with professional workstation applications developed by various independent software vendors (ISV’s).  The workstation specific enhancements allow the ATI Mobility FireGL V5700 to perform significantly faster in these ISV applications than a consumer level graphics product.

 

 

Previously, there was a situation on the ThinkPad W500 where customers would see the ATI Mobility V5700 as an ATI Mobility Radeon HD3650 in Windows Device Manager and in Display Properties.  Lenovo previously explained this in this tip 

 

 

The root cause was that the ATI Mobility Radeon HD3650 and ATI Mobility FireGL V5700 were initially given the same Hardware ID as discussed above.   A system bios update  and driver updates for VISTA and XP were released to address this situation.  

 

System BIOS version 1.18 and later change the subsystem ID section of the Hardware ID’s for the ATI Mobility FireGL V5700 to 2126 for switchable graphics mode and 2127 for discrete graphics mode.  Graphics driver version 8.54.2 and later apply this same Subsystem ID change for the ATI Mobility FireGL V5700.   Note that it is important that users follow the directions to install the driver update BEFORE updating the system bios.

 

 

Unfortunately, the system bios update that contains the updated Subsystem ID’s has the side effect of causing the drivers that were certified at the ISV’s to not work on any W500’s with system BIOS update 1.18 or later.  The reason for this is that the original drivers sent to the ISV’s did not contain the new ATI Mobility FireGL V5700 Subsystem ID’s.  New W500’s from the factory that are shipped with system BIOS 1.18 or later will not work with the these older certified ISV drivers and any W500 that is updated to this new SBIOS will also not work with the ISV drivers.  Windows will see that the Subsystem ID of the installed GPU does not match the Subsystem ID’s supported by the driver and will either unload the driver or refuse to install the driver.

 

 

To remedy this situation with the ISV drivers, Lenovo has distributed new drivers with the new ATI Mobility FireGL V5700 Subsystem ID’s to the ISV’s and they are currently being evaluated and updated.  Until the ISV’s are able to post the new drivers it is recommended that users requiring the ISV driver use drivers which Lenovo is providing via a new tip which should be made available on the web shortly and we will update this post with a link here. <- Link is now live!

  

UPDATE 11/24/08 - Link above updated for interim ISV drivers.

 

 

Additional note :  To ensure that the W500 performs at workstation levels it is sent to the ISV’s for performance and stability certification.  One of the implications of certification by ISV’s is that the certification takes some time and therefore the ISV certified driver is often an older version than the most recent Lenovo web driver, which is updated often to address issues users may encounter.  In the case of the W500 the ISV driver is also different in that it does not support switchable graphics.  This is done to guarantee absolute stability of the system and graphics driver for use by professional workstation users.

 

For more information on the implementation of switchable graphics please follow this link .

Message Edited by Mark_Lenovo on 11-17-2008 08:03 AM
Message Edited by Mark_Lenovo on 11-25-2008 06:17 PM

____________________________________________
Regards/Cordialement/Cordiali saluti/Mit freundlichen Grüßen/Saludos/
Mark Hopkins
Project Manager, Social Media
Active Member
cvantilborg
Posts: 17
Registered: 09-24-2008
Location: Canada
0

Re: Help W500 graphics card question

Mark,

 

   Thanks for all your help with this. 

 

Corey V

Active Member
migle
Posts: 95
Registered: 08-24-2008
Location: Portugal
0

Re: Help W500 graphics card question

Hi, Mark,

 

Thanks for the summary of what's been happening. I find the argument "this special marking (which added cost to the to the system) is no longer required", satisfying, although not so much this other "as Lenovo now uses a more advanced mechanism to differentiate between the chips", as this one leaves open why didn't they come properly marked before BIOS 1.18.

 

For me anything goes as long as the card works correctly and more or less swiftly. 

 

One thing worries me, though. You say that ISV certified drivers don't support switchable graphics, fine by me, I don't need ISV certified drivers. However are FireGL features (OpenGL extensions) available only on this ISV certified drivers? Or are they also available on the switchable graphics driver?

 

Because in that case switchable graphics becomes somewhat a misfeature.

This one item that differentiates this product from its competitors (M4400 and 8530w) becomes useless if one really wants OpenGL capable drivers...

 

W500 4062-2XG T9400/4GB/WUXGA/ATI M86/Vista 64/Gentoo Linux 64
Administrator
Mark_Lenovo
Posts: 3,056
Registered: 11-19-2007
Location: RTP, North Carolina
0

Re: Help W500 graphics card question

[ Edited ]

Migle,

 

Full OpenGL support should be available through both the ISV drivers and the switchable graphics mode drivers when they are set to the workstation / performance mode.

 

If there is a problem getting that support, we would treat it as a bug and work to resolve it. 

 

Best regards,

 

Mark

Message Edited by Mark_Lenovo on 11-14-2008 12:51 PM

____________________________________________
Regards/Cordialement/Cordiali saluti/Mit freundlichen Grüßen/Saludos/
Mark Hopkins
Project Manager, Social Media
Active Member
migle
Posts: 95
Registered: 08-24-2008
Location: Portugal
0

Re: Help W500 graphics card question

Thanks for the quick and satisfying answer.

(If only I could get my hands on my long delayed W500... Lenovo needs better distributors in Portugal and around, and avoid doing business with IBM... but that would be another thread...).

 

W500 4062-2XG T9400/4GB/WUXGA/ATI M86/Vista 64/Gentoo Linux 64
Active Member
comptiger5000
Posts: 33
Registered: 11-08-2008
Location: Connecticut, USA
0

Re: Help W500 graphics card question

On my W500 (Windows 2003), the normal XP drivers (non-ISV) give proper OpenGL support.  This issue seems to be resolved.