Dell Latitude E6410, E6510 and ST Microelectronics Accelerometer

Hello:

   Has anyone had any luck pre-staging (for XP Imaging) the ST Microelectronics Accelerometer found in the newest E6410 and E6510 series laptops from Dell?  I've unpacked the drivers from the installers, staged them in my XP drivers directory as usual, and added the driver location to sysprep.inf but 1) after mini-setup runs, the machine fails to auto-reboot into a working OS and 2) XP doesn't recognize the device in device manager.

   I'm using the old method of manually creating a drivers directory and using sysprep&ghost to capture an image.  We have only a few months left on our intended support of XP, so I'm trying not to spend the time necessary to bring the XP image into MDT.

Thoughts?

Thanks
d

We are a complete Dell shop, so my workload has been significantly reduced by the efforts of Greg, Warren, and others at Dell that have so kindly packaged all the relative drivers for each model:
http://www.delltechcenter.com/page/dell+business+client+operating+system+deployment+-+the+.cab+files

The 6410 and 6510 are among those listed, so that definitely makes things easier if you choose to import your XP image into your MDT environment.  We have about 15 different Dell workstation models, and (knock on wood) they have all worked with the drivers in the cab files posted on the Dell Tech Center (linked above).  If you change your mind and do choose to use MDT, and this driver continues to be a hassle, you could always use your Task Sequence to install the driver after the image is laid down on the targeted hardware.

Did your image boot into the OS fine before adding this driver (and capturing with Ghost)?

Thanks Jeremy... I've definitely used that Dell resource for Drivers for Win7/MDT, but it's less useful for our legacy practices with XP, Sysprep, and Ghost.  Have you tried the XP package specifically with a Latitude E6410 or E6510?  I'd be curious to see if you have the same issue through MDT, since MDT is basically just doing a more targeted version of what I'm doing with Sysprep.inf.  When I try to install the drivers manually to an existing XP system, device manager complains that the "drivers aren't meant for this platform".  It's very strange, and in ~5 years of managing this XP image, I've ever seen anything like it.  Part of me is wondering if this is an isolated problem with my image or if other folks are seeing the same issues.

d

The 6410 and 6510 are among those listed, so that definitely makes things easier if you choose to import your XP image into your MDT environment. We have about 15 different Dell workstation models, and (knock on wood) they have all worked with the drivers in the cab files posted on the Dell Tech Center (linked above). If you change your mind and do choose to use MDT, and this driver continues to be a hassle, you could always use your Task Sequence to install the driver after the image is laid down on the targeted hardware.

Right now, our most current laptop is the E6400.  So, I don't personally have any experience with the 6410 or 6510.  I looked at my Deployment Workbench, though, just to see if I had an STMicroelectronics driver for the E6400.  I didn't see one, so it looks like the free fall sensor may have been introduced later.  This may be something that I have to contend with in the near future, so I'll see what else I can find.

Can you confirm that this is the same driver that you're using (version 2.00.00.12, A00, release date 05/13/2010)?
http://tinyurl.com/232um94

Yup, that's the driver I'm using.

I'm chasing down another issue that may be at fault for the sysprep mini-setup hang... Will report back if I find that answer.  For now, I'm pretty well resigned to there being an unknown device in device manager at least until an updated driver version is released...

Thanks for your help
dan

I am having the same problem, if I load the computer using the included SP3 disc, use the F6 drivers in sysprep.inf and extract the 6410 driver cab and run spdrvscan against it it will sysprep and reboot without hanging.

I dont think it has anything to do with just your image.  I am experiencing your exact issues from the driver & reboot issue down to what sound like your move from ghost to MDT tools  & Win 7
 
Right now I am trying to determine why the machine hangs during a reboot but not during the shutdown.  Ill Let you know what I find.
 
 

As expected, we finally received a 6410 to work with.  So, here's what I've found...
Initially, I had two problems.  The first was a prompt for the Intel Dual-Core Turbo Boost driver during mini-setup, even though the driver (impcd.sys) was actually copied locally by the Task Sequence (under C:\Drivers\System\Impcd...).  After digging around a bit, I found that there are 2 versions, one x64 and one x86, each of which were imported to the MDT workbench and erroneously configured (automatically) as being compatible with both architectures.  After I modified each driver in the workbench, checking only the correct architecture (x86 or x64), the next attempt at running the Task Sequence proved that this particular issue was resolved. 

The second problem was the "hang" described above.  After a little research in the Dell forums, it appears that quite a few folks have shared the pains of the initial release of the BIOS on the E6410.  Here's a good thread:
http://www.delltechcenter.com/thread/3938139/SCCM+2007+XP-SP3+OSD+for+new+6510+and+6410+problems...?offset=0&maxResults=20

Essentially, you need to be at BIOS version A03.  If you're currently at A01, this entails a patch (to A01.1) first before upgrading to A03.  Once you get to A03, everything should move along without the "hanging" problem. 

As for the ST Micro Accelerometer driver issue (ongoing here - [link=http://www.delltechcenter.com/thread/3956813/E6410+Windows+7+ST+Micro+Accelerometer+issue]http://www.delltechcenter...ro+Accelerometer+issue[/link]), I was able to run the Dell-provided executable (with the -s switch for a silent install) to get the driver installed (as an application within my Task Sequence).  After the install, the hardware is now recognized in Device Manager, but the device status still shows a warning - "This device cannot find enough free resources that it can use.  (Code 12)".  I have yet to find anyone that has been able to resolve this, but I'll keep looking.  I'll be sure to post here if/when I get it fixed.  I won't be surprised if we see a new driver release in the near future.

Gone are the days when more people focused on the installation of system software and less on networking.

I have deployed many (79) 6410's on my network, and have no issues with the likes of what you have here.  I did, however find the "unknown" issue on the first (test machine) machine that was to create the master image. The fix was simple. Since I was creating an image, and not concerned with streamlining drivers into the installation, I did what any Joe off the street would do with one small exception, I used an image with SP3 already streamlined in the image. Then, following the instructions from Dell, I used the drivers and utilities CD included with the laptop.

"After installing the Operating System and Service Pack the most important component to install is the Dell Notebook / Desktop System Software (NSS / DSS). The Notebook / Desktop System Software executable is a collection of essential software that provides critical updates for correct Operating System functionality. This software package is designed to automatically detect and install the appropriate files and/or updates, depending on the Operating System and Service Pack present.

MNeau,
Can you duplicate your results without using the Dell hardware to capture your image?  Essentially, use a VM to build and capture.  The Dell System Software Utility is model-specific, so I personally don't want to install this on my reference image.  There are some versions of the utility that are compatible with several models, but I prefer not to have any software in my reference image that is not standard across all hardware models. 

Hi jgillean,
 
?I have the same problem with the ST Microelectronics Accelerometer driver, i.e.  a warning "This device cannot find enough free resources that it can use (Code 12)". Have you ever found any solution for it?
 
I have a Dell Vostro 3750 with Win XP x32 on which I succeeded installing just about all XP drivers except for the above. I have tried just about all drivers I could find on the internet (including original Dell's drivers) and all suggestions for fixing this problem, but to no avail.
Any suggestion on how to fix it would be appreciated.
 
Thanx.
Peter

Hi Peter,
I haven't worked with XP in quite a while.  I do know that we don't have any issues injecting the accelerometer driver when deploying Windows 7 to the same models mentioned above (E6410 and E6510).  However, we don't have any Vostros in our environment (that I'm aware of), so I can't provide much help on those models.  I'm sure you've probably already tried this, but here's the link for the applicable driver from Dell's site:
http://www.dell.com/support/drivers/us/en/555/DriverDetails/DriverFileFormats?DriverId=GWK5J&FileId=2731100277
I would try to extract the driver from the executable and work with that, if possible.  If that fails, I would contact Dell (hopefully, you have a tech rep for direct contact) and see if they can provide some assistance.  Wish I could be of more help.