D610 and Ghost

The chipset is different, to name one major component.

You'd be better off building a fresh image for the 610 - the hardware is appreciably different from that in the 600.

Thanks for your help.  I don't wont to sound ungrateful but I knew that the chipset was different.  Which driver is it using?    Is this an Intel Chip set?  Mobile 915?  These are the kind of things I need.  I really don't care if the modem , sound, pc cards  etcc  do not get installed properly as I can fix them if I can at least get the PC to boot.    I understand about building a seperate iamge but that is not an option.  I can explain in more detail if you drop me an email

 

mark@madsdad.com

 

Thanks

Hi there:

I have a very similar problem; I currently use "Ubiboot" from Qualystem, Inc (http://www.qualystem.com/en/ubiboot.html). Using this software, I have one image for the following models:

GX150
GX400
GX240
GX260
GX270
GX280
D600 Latitude

I just received a new D610 and when I tried to reimage it (we use Novell's ZENWorks), it boots up normally, but upon doing a search for new hardware _always_ freezes at "IDE Channel". I have emailed Ubiboot support just in case, but I noticed your posting and at least can conclude to some degree I am not the only one running into this issue. The whole point about the Ubiboot program is that creating new images isn't needed when new hardware is introduced.

I am going to try another D610 I received just to make sure the problem isn't isolated to one machine.

[8F] The NyQuil Kid

If the image won't transfer at all, chances are the problem is with the network drivers or cloning program options. What are you using to distribute the images?

Thanks for confirming that issue.  I would not even bother trying it on another 610.  I will let you know which driver is missing if I figure it out.  If you do please let me know as well.  The issue is not with the image,  the imaging software or the network card.  setup stops at about 50% this is normally an indication of a driver from a specific chipset for example intel 915 etc...  If I knew which chipset this laptop used or which specific drivers I could fix the issue.

 

Thanks Mark

The chipset choices that I see are the 915 or the 910GML; Dell provides a driver that covers both, and I checked Intel's website and discovered the same thing with theirs:

http://support.intel.com/support/chipsets/sb/CS-020149.htm

Also, Intel does offer a chipset ID utility:

http://support.intel.com/support/chipsets/inf/sb/CS-009266.htm

The problem you're running into sounds very similar to mine; while I don't use Sysprep and therefore do not go through a setup procedure, my "Ubiboot" image does boot up, but upon hardware discovery (which appears to be what your image is doing during that particular part of the setup routine), it freezes completely - no reaction from the keyboard, hard drive etc...

[8F] The NyQuil Kid

You're not alone.  We've got a general Laptop image that we use for all our laptops (everything from a CPI up to a D600.) We use Ghost 8 and Sysprep to create our images.

We tried to update our laptop image for the D610, and it hangs at ~50% durring the hardware discovery.

We'll keep you updated if we find a solution, but for now we're creating a seperate image for the D610.  When we get out test D410 in we'll see if the D610 image will work on it.

Thanks for the update; I had a feeling this would happen; I've been doing some testing of my own and will post here with more info.

Also, check the posts from the "Hard Drive" forum for Latitudes; there are other posts concerning this issue.

[8F] The NyQuil Kid

Hi Folks-

I'm still not convinced that there is not an issue with the drivers for the D610. A couple of observations that I have made while banging my head against this over the past couple days:

• The machine will boot into Safe Mode, but not Safe Mode with Networking. This makes me think that it is something to do with the Broadcom 57XX driver.
• The machine hangs on boot in a Diagnostic Startup (via msconfig). This reinforces the gut feeling that there is a driver issue 
• I noticed when booting the machine into Linux (ZenWorks Imaging) that the PCI device list indicated that the Broadcom Network Controller was detected as having 64-bit memory addressing.

Just out of curiosity, I have tried this with an XPSP1a image, and I noticed that NyQuil_Kid has tried win2k. Are any of the images others are trying to use SP2? What about other OSes? (I only bring that up due to the quirk I noticed in the PCI device list under Linux)

Yes, here we tried both SP1 and SP2 images created on a Dell Latitide D400, then syspreped with the D610 Drivers available.  Neither works.  The D410 is a worked just fine, and from a hardware prespective it's virtually the same as D610.

When I talked to the Dell rep, he did mention something about the Broadcom drivers, but it was in refrence to problems Ghosting, not driver issues.  I did go out to the Broadcom site and download their drivers, but they are the same version and size as the Dell drivers.  I haven't done a binary comparison though.

Message Edited by Morninigstar on 03-03-2005 11:29 AM

Hi there:

Just wanted to get a clarification, so my apologies in advance if this has been answered.

I noticed you received a D410; have you attempted to take your pre-existing D600 image, place it on the D410 and if that works, prep the D410 (with the D600 image) and try it on the D610? I am wondering whether this might work (we don't have a D410 to test here).

Thanks in advance for any information you can provide.

[8F] The NyQuil Kid

Message Edited by NyQuil_Kid on 03-04-2005 03:18 PM

Hi guys,

Try the A03 version of BIOS, I think this fixes the issue.

The Apostate.

Have you tried this yourself? Can anyone else confirm this? I will give it a shot tomorrow morning...

Thanks for the heads up!

EDIT: Confirmed - I was able to image my D610 after flashing the BIOS to A03; again thanks for the heads up!

[8F] The NyQuil Kid

Message Edited by NyQuil_Kid on 03-07-2005 08:46 AM