PDA

View Full Version : Dell E6500 with Win8 Hybrid shutdown


Andy Burns
December 14th 12, 08:51 AM
Ùpgraded my Dell Latitude E6500 to Win8 a few weeks ago, generally good,
only hardware not properly detected was bluetooth which I manually found
a driver for, and fingerprint reader where the biometric framework
driver loads and can detect swipes, but refuses to allow logon or
actually enrolling new fingers, just goes though the motions.

On the software side, only issue is vSphere client which I gather is an
IE10 issue and requires upgrade of vSphere server to fix.

For my own sanity I installed start8.

Took me a while to realize that when using shutdown, most devices were
being powered off (hard disc, WiFi/HSDPA/bluetooth LEDs all going off,
LCD panel and/or external monitor, etc) but the actual power not being
switched off, and fan left running. After pressing and holding the power
button it will fully turn off, and next time it boots without complaint
about improper shutdown.

Made sure I'm on the latest BIOS rev, checked reboot works fine and it's
only shutdown causing the issue, then turned off the fast boot (hybrid
shutdown) feature and now it shuts down fully.

The machine has an SSD, so boots quite quickly anyway, but the hybrid
shutdown starts back-up even faster, so worth trying to get it working.

Anyone else? Any suggestions?

Andy Burns
December 14th 12, 08:19 PM
Andy Burns wrote:

> turned off the fast boot (hybrid
> shutdown) feature and now it shuts down fully.

tried turning it back on again today, and it shutdown properly with it
on, but does it take a reboot after turning it on, for it to actually be on?

Couple of reboot later (to remove widcomm bluetooth and revert to
Microsoft bluetooth stack ith only the dell driver) and hybrid shutdown
was back to hanging again

> The machine has an SSD, so boots quite quickly anyway, but the hybrid
> shutdown starts back-up even faster, so worth trying to get it working.

only 5 seconds in it (19 seconds to logon screen v.s. 24)

Joe Morris
December 15th 12, 01:10 AM
"Andy Burns" > wrote:

> Ùpgraded my Dell Latitude E6500 to Win8 a few weeks ago, generally good,
> only hardware not properly detected was bluetooth which I manually found a
> driver for, and fingerprint reader where the biometric framework driver
> loads and can detect swipes, but refuses to allow logon or actually
> enrolling new fingers, just goes though the motions.

The API that supports presentation of logon credentials is hairy - I had to
dig through the interfaces last year when we expected to need the ability
for unprivileged users to force off users on conference room computers...and
I've still got a headache from it. (The project was abandoned when we
shifted the conference room machines to one of our internal clouds.) Given
their complexity and Microsoft's habit of changing the way the guts of
Windows do their job I'm not surprised that the FPR program for (I presume)
Windows 7 is having problems presenting the logon credentials on Win8.

At least what you've encountered won't be a problem for me: our information
security department prohibits FPR-based login for several reasons, not the
least of which is the poor quality of the sensors and matching software.
(Google for "gummy bear attack".)

> On the software side, only issue is vSphere client which I gather is an
> IE10 issue and requires upgrade of vSphere server to fix.

What version of vSphere are you using? I'll need to check it in the
not-too-distant future but for a number of reasons that's nowhere near the
top of my to-do list today.

Joe

Andy Burns
December 15th 12, 01:16 AM
Joe Morris wrote:

> "Andy Burns" > wrote:
>
>> only hardware not properly detected was [...] fingerprint reader
>
> The API that supports presentation of logon credentials is hairy

Someone else pointed out that the Dell version of the Digital Persona
driver supports enrolling and logging on, provided that the Broadcom WBF
driver is loaded, so that's sorted now.

>> On the software side, only issue is vSphere client
>
> IE10 issue and requires upgrade of vSphere server to fix
>
> What version of vSphere are you using?

The problem is 5.0, it works with 4.x and 5.1, the version that counts
is the version on the vCentre server, not the viclient installed on the
Win8 machine, or the ESX version ... everything works in the client
except the ability to connect to consoles of VMs.

Andy Burns
December 15th 12, 01:22 AM
Andy Burns wrote:

> Someone else pointed out that the Dell version of the Digital Persona
> driver

Sorry, I meant the Digital Persona management app, rather than driver.

> supports enrolling and logging on, provided that the Broadcom WBF
> driver is loaded

Joe Morris
December 15th 12, 05:34 PM
"Andy Burns" > wrote:
> Joe Morris wrote:
>> "Andy Burns" > wrote:

>>> On the software side, only issue is vSphere client

>> IE10 issue and requires upgrade of vSphere server to fix

>> What version of vSphere are you using?

> The problem is 5.0, it works with 4.x and 5.1, the version that counts is
> the version on the vCentre server, not the viclient installed on the Win8
> machine, or the ESX version ... everything works in the client except the
> ability to connect to consoles of VMs.

OK; thanks. The way you phrased the earlier posting had me worried about
vSphere itself.

I'll need to validate vSphere on Win8 at some point in the future but right
now I'm trying to convince Windows 8, configured to comply with the local
security requirements, to work cleanly in a XenDesktop environment even
without a statement of support from Citrix.

I'm also trying to find a sweet spot for the Dell Win7 drivers for a
Latitude XT3 running Win8, but that's another story.

Joe

Google