Unsolved
This post is more than 5 years old
5 Posts
0
323080
April 7th, 2011 08:00
Problem with Free Fall Sensor
Hello,
I've integrated the most current Driver CAB into SCCM.
After OS deployment, there is a "unknown device", described as Free Fall Sensor (ST Micro Accelerometer). The error message says, that the device was started, but errors occured.
I've downloaded manual the most current version of the Application and Driver package for this device ("ST-MICROELECTRONICS_FREE-FAL_A06_R294986.exe")
I've extracted the driver manual by calling "setup.exe /v"EXTRACTDRIVERS="" as described in the readme.txt
I've integrated the driver into SCCM. Still the same error.
When I try to install the application (full and with parameter /APPLICATION for Application installation only) the setup fails.
When I install the setup manual after OS deployment, everything works and the device and installation is correct.
The same hardware seems to be integrated into the E6510, see http://www.delltechcenter.com/thread/3956813/E6410+Windows+7+ST+Micro+Accelerometer+issue
Any ideas ?
TIA and regards,
Ralf
I've integrated the most current Driver CAB into SCCM.
After OS deployment, there is a "unknown device", described as Free Fall Sensor (ST Micro Accelerometer). The error message says, that the device was started, but errors occured.
I've downloaded manual the most current version of the Application and Driver package for this device ("ST-MICROELECTRONICS_FREE-FAL_A06_R294986.exe")
I've extracted the driver manual by calling "setup.exe /v"EXTRACTDRIVERS="" as described in the readme.txt
I've integrated the driver into SCCM. Still the same error.
When I try to install the application (full and with parameter /APPLICATION for Application installation only) the setup fails.
When I install the setup manual after OS deployment, everything works and the device and installation is correct.
The same hardware seems to be integrated into the E6510, see http://www.delltechcenter.com/thread/3956813/E6410+Windows+7+ST+Micro+Accelerometer+issue
Any ideas ?
TIA and regards,
Ralf
0 events found
No Events found!
StephanvanderPl
4 Posts
0
May 25th, 2011 06:00
Thank you for sharing your solution. By analyzing your solution, I found the root cause and solved this problem in a better way, at least that's what I think:
- Import the drivers for all OS types you want to deploy
- For each driver, open the Properties and go to the Applicabilaty Tab. You see the radio box "This driver can run only on the specified platforms" is already selected. But too much OSes are selected here, at least for the x64 drivers. I think this is the root cause (because also the INF file mentions too much OSes). So deselect all x86 OSes in the x64 drivers and all x64 OSes in the x86 drivers.
The drivers now only will apply to the machines with the corresponding OS architecture, even when using the auto apply driver from all catagories option.
Regards,
Stephan
Note: The TS step Install Software that runs the "setup /APPLICATION /s" program, can (or in my opinion should) be filterd by the WMI (root/CimV2) query:
Select * From Win32_PnPEntity Where DeviceID Like '%ACPI\\SMO8800%'
marvw
3 Posts
0
June 9th, 2011 18:00
#1 the autounattend.xml file generated by WAIK is not being read when building the the reference machine using Dell branded reinstallation media - WAIK's documentation doesn't mention it anywhere, but I've read on other forums the autounattend.xml will only get read before Windows installation ONLY when using Microsoft VL media. That said, if we force sysprep to read unattend file during the prep portion, it seems to work - or at least did during our initial attempt going this route.
The only changes we're putting in the unattended test file is PersistAllDeviceInstalls=True in the Microsoft-Windows-PnPSysprep component block.
Dell's imaging engineers in China (??) got back to our account rep and said there are known issues with the FFS and sent us the FFS installer, version A00 - the original release. I haven't attempted to use this file as of yet since I just got back from vacation.
You guys are all using SCCM or MDT, so your mileage may vary.
Mateo_21
1 Message
0
January 21st, 2012 10:00
After installing the ST Micro Accelerometer should go to the Device Manager and update the driver manually selecting the locations of ST Micro Accelerometer (c / program files (x86) / STMicroelectronics). Pop-up error disappears and everything is working properly
IntraX
1 Message
0
January 23rd, 2012 03:00
Has anyone got an automated fix for this yet. I am getting these problems with MDT 2010 U1 on a Vostro V131. I am using the drivers from R305726.
cyoxall
2 Posts
0
September 17th, 2012 04:00
I have the same problem, with Freefall sensor and Mini-Wifi card on a dell E6230 using MDT 2010 for deployment and WMI queries for task sequence
Just to throw my 2 pennys worth into the pot, i notice that when you manually install them using setup.exe it drops inf drivers into c:\programe files\
So ive just injected my MDT server with these drivers i took off a machine i manually installed them on, currently dpeloying a base wim to another E6230 now with these new drivers imported, will report back if it works or not, no reason why it shouldnt as when I just pojnted DM to those drivers on my USB stick it picked them up and installed them no problem, we shall see...
cyoxall
2 Posts
0
September 17th, 2012 05:00
just to confirm, this works fine doing it this way
install the applications manually, then go to c:\programme files\ - it was something like ST micro or something like that, and copy that folder, go to your MDT server and import drivers from that folder, re-deploy, works fine now.. hope that helps people