Deployment Solution

We are testing the new HP dc7900 desktop line and are having issues imaging. Under the normal achi setting, in the BIOS, Rdeploy cannot see the drive...yet under IDE mode it images fine.

I have taken the drivers and placed them according to Article 36472 and 20566 with no luck. I even tried just adding them straight thru the Boot Creator and it seems that it just wont load. The new Sata Controller is the Intel ICH10D/10 (PC\Ven_8086&DEV_3A02)

If anyone has any ideas it would be much appreciated.

Thanks

Having similar issues with dc7900

Is there a solution yet for this problem ?

We did get this to work, but my notes are at work. Will share what we did when I get into the office on Monday.

What about with the HP EliteBook 6930P? I'm using linux automation and I'm having issues with it not seeing the disk of the 6930P. I've even ebabled IDE only. I've also followed the article 43591 at kb.altiris.com. Any help is greatly appreciated.

I am also having the same issue. I got a new dc7900 and trying to find the correct winpe 2.1 drivers.

Any update on which drivers work?

I have a Zip File of the drivers we used to add to our WinPE. This worked for the dc7900. Let me know how you would like to receive them. You can email me with your info if you like.

Hi, could you please send me the zip file (jm@db.dk)?? Anyone have succeeded in getting this to work with linux drivers?

I downloaded XP drivers from HP and added them into WinPE at the same location you add NIC drivers [Altiris tech told me to do this last time we had the issue with the 6910P laptops], but it didn't work this time. I ended up setting the SATA drive into IDE mode in the BIOS and it worked fine. Probably not the best solution but we needed this done asap.

John

Can you please send the file to umang09@yahoo.com. Thanks!

I got it working with DOS without having to enable IDE with the 6930P. I need it to work with Linux automation. Hopefully Altiris and Hp will get on the same page and fix the problem.

I'd love to have that zip file me at mpking dot com

Umang09...did that file I sent you work ok?

My problem was not with the Sata drive. I was having a problem finding the correct NIC driver for WINPE 2.1. I was able to find the correct NIC driver and create an image.

Thank you for sending the SATA drivers to me.

Oh..sorry about that..I had the NIC drivers too

Does anyone got it working for the linux PXE ???

Thanks ...

Bart

What are the NIC Drivers? (I have the exact same problem)

Using these two articles, I was able to get a HP DC7800 to work Linux boot properly:

Linux automation stops after “Uncompressing Linux” https://kb.altiris.com/article.asp?article=39929&p=1
How to add Linux pre-boot drivers to HP computers: https://kb.altiris.com/article.asp?article=43591&p=1

For the DC7800 it works fine but not for the DC7900 .... :-)

Gtz

Bart

Anyone found a solution for WinPE or Linux? Win PE gets a "RDeploy:The disk was not found" error, and Linux gets a "No Express Mount found error"

Same problem. Memory error in dos using undi net (big image). No hard drive in linux (I got the net driver from the link above). No network in winpe.

I got it to work in windows PE.

I downloaded all the network drivers from HP's website, and added them all to the WinPE boot image. I think it was something like 20 different INF Files. I'm not sure which one was it, but I've imaged about 20 dc7900's at this point. (ACHI mode on the SATA controller) I also added a SATA driver as well, so that might have helped.

Hmm, I added e1k5132.inf for the 'intel(r) 82567LM-3 gigabit network connection' to winpe. It gave a warning about unknown class. But I just get 'restarting dhcp client service' over and over.

Duh. I was trying the XP driver instead of the Vista driver: 'elk6032.inf'. It's started imaging, fast.
Currently in IDE mode.

I entered a case on this tonight.


Case # 320-160-773
Open

Product/Version
Severity

Deployment Solution 6.9 SP1
2 (Critical)

Platform/Version

Windows Server 2008 Standard (x64-64bit)

Summary

Support for HP DC7900 in WinPE and Linux




I called Support requesting that they test the DC7900's with HP fefore releasing the DS gold code for 6.9 SP1.

We went through this last year.

I also entered a ticket on the Optiplex 960 (HP DC7900 sister machine)
Case # 320-160-777
Open


Product/Version
Severity

Deployment Solution 6.9 SP1
2 (Critical)

Platform/Version

Windows Server 2008 Standard (x64-64bit)

Summary

Support for Dell Optiplex 960 in WinPE and Linux

I have to set the SATA Emulation to IDE in the bios, or else it blue screens when imaging in winpe. I installed the vista storage driver through the 'have disk' button on the winpe drivers screen.

Thank you for opening a case for it !!!

Please let me know if there is a answer ...

Gtz

Bart

I'm not sure what driver I added, but I know it was not the Vista driver, I know I only loaded the XP drivers. The driver was leftover from making a Nlite XP CD that had SATA drivers on it.

If I can get a chance, I'll look what one it was, but I'm pretty sure I got it from Intel's website (Intel Storage Matrix Driver) and not HP's.

Mike

This whole ahci thing is pretty aggravating. In XP, the setup program won't install the ahci driver, unless I install the ahci driver by hand first. Then if I set IDE in the bios, the computer bluescreens. If I try to go back to a generic ide driver, bluescreen.

Hi,

We've finally got the HP dc7900 and this is what we've found so far.

1] Imaging with Linux is NOT supported in either the IDE or AHCI BIOS modes for the controller. Intel have not released ICH10 Linux drivers and this seems to be the core of the problem.

We can get Linux agent communication though using the e1000.ko driver which we installed previously to get comms working for the dc7800 -so good news there.

2] Imaging with the Microsoft DOS UNDI environment works a treat as long as you put the BIOS into IDE mode. DOS is great for getting these odd controllers imaged (its a shame Altiris have de-emphasised DOS in DS).

3] Haven't tried imaging with WinPE 1.6 or WinPE 2.1 as yet, as we'd had a succession of PXE based imaging issues with WinPE which have put us off for life.... ;-)

So, for us the resolution is to use DOS until Linux support is available. This is a pain for our HII process as this is purely linux based now. :-(

I've opened a case with both HP and Altiris on this -hoping that a pincer attack on Intel will get us what we need.


Kind Regards,
Ian./

Hi,

This is a dupicate post as we have two threads on this: apologies.

I've tried re-compiling the latest AHCI driver for linux against the older kernel used in Linux Automation for DS6.9.

The resulting driver (ahci.ko) is only therefore valid against the 2.6.18.8 kernel.

I've just compiled this, and its untested. I won't get around to testing it until next wednesday, so I thought I'd post it up on the off chance it works. This should recognise device IDs 3a05 & 3a35 as the Intel ICH10 controllers, but to be honest i've no idea what will happen.

Best of luck,
Ian./

I have had no luck compiling any Linux driver files against the 2.6.18.8 kernel so far. They compile but do not work during a PXE boot. It always seems like things are supported in the "next version" when you find or get an answer from support.

Painfully, I have went from DOS > Linux > WinPE2. I would recommend refinning your process and using WinPE2. This will support the Vista/2008 drivers and seems to have the best driver support. It is also the easiest environment to add new drivers to with 'Have Disk'. I reduced my image process down to 1 reboot so I don't have to wait for it to load each time. It is unfortunate that I had to end up going this route, but it is definately the easiest to support. From my experiences, it seems to be the environment Altiris is recommending.

For WinPE2 if you need to add driver support for a NIC or MSD, make sure you use the Vista/2008 drivers. The process to add them is in the AKB article

Also to be clear, WinPE driver support and a BSOD after the image has been layed down are two different things. Once you get the pre-boot environment to support your hard drive/nic, you also have to make your XP image support the Intel MSD's. This is done by adding entries for the drivers in the OS before you sysprep it. Yes this means you have to re-create your image. You cannot inject these in like a normal driver because the entries are actually added to the criticaldevicedatabase in the registry. You will find articles in juice about fudging those entries in, but I would recommend the cleaner way of re-doing your image because you have that process documented anways . Below are the entries I appended to my sysprep.inf massstorage section to support all Intel Matrix Drivers to date. You will have to download the drivers (XP) then extract them from the .exe's (check the readme.txt for the commands, usually -a -a). http://downloadcenter.intel.co...er.aspx?ProductID=1809 . Once that is done add them to your source image like I have in c:\drivers\MSD and sysprep -mini -reseal -quiet. You will be able to support both IDE and AHCI if it is done right.

If you don't want to make a new image you can go to 6.9 SP1 and use the deployanywhere feature to add the MSD's to its database. I haven't tried this yet though.

[SysprepMassStorage]

; APPEND ADDITIONAL SATA CONTROLLER DRIVERS HERE
PCI\VEN_8086&DEV_24DF&CC_0104=%systemdrive%\drivers\MSD\IMver5\iastor.inf ; Intel(R) 82801ER SATA RAID Controller
PCI\VEN_8086&DEV_25B0&CC_0104=%systemdrive%\drivers\MSD\IMver5\iastor.inf ; Intel(R) 6300ESB SATA RAID Controller
PCI\VEN_8086&DEV_2652&CC_0104=%systemdrive%\drivers\MSD\IMver7\iastor.inf ; Intel(R) 82801FR SATA RAID Controller
PCI\VEN_8086&DEV_2652&CC_0106=%systemdrive%\drivers\MSD\IMver7\iaahci.inf ; Intel(R) 82801FR SATA AHCI Controller
PCI\VEN_8086&DEV_2653&CC_0106=%systemdrive%\drivers\MSD\IMver7\iaahci.inf ; Intel(R) 82801FBM SATA AHCI Controller
PCI\VEN_8086&DEV_2682&CC_0104=%systemdrive%\drivers\MSD\IMver8\iastor.inf ; Intel(R) 631xESB/632xESB SATA RAID Controller
PCI\VEN_8086&DEV_27C3&CC_0104=%systemdrive%\drivers\MSD\IMver8\iastor.inf ; Intel(R) 82801GR/GH SATA RAID Controller
PCI\VEN_8086&DEV_27C6&CC_0104=%systemdrive%\drivers\MSD\IMver8\iastor.inf ; Intel(R) 82801GHM SATA RAID Controller
PCI\VEN_8086&DEV_2822&CC_0104=%systemdrive%\drivers\MSD\IMver8\iastor.inf ; Intel(R) ICH8R/ICH9R SATA RAID Controller
PCI\VEN_8086&DEV_282A&CC_0104=%systemdrive%\drivers\MSD\IMver8\iastor.inf ; Intel(R) 82801HEM SATA RAID Controller
PCI\VEN_8086&DEV_2681&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) 631xESB/632xESB SATA AHCI Controller
PCI\VEN_8086&DEV_27C1&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) 82801GR/GH SATA AHCI Controller
PCI\VEN_8086&DEV_27C5&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) 82801GBM SATA AHCI Controller
PCI\VEN_8086&DEV_2821&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) 82801HR/HH/HO SATA AHCI Controller
PCI\VEN_8086&DEV_2829&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) 82801HEM/HBM SATA AHCI Controller
PCI\VEN_8086&DEV_2922&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) ICH9 SATA AHCI Controller
PCI\VEN_8086&DEV_2929&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) ICH9M-E/M SATA AHCI Controller
PCI\VEN_8086&DEV_3A02&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) ICH10D/DO SATA AHCI Controller
PCI\VEN_8086&DEV_3A22&CC_0106=%systemdrive%\drivers\MSD\IMver8\iaahci.inf ; Intel(R) ICH10R SATA AHCI Controller

Brandon,

Where have you found a reference that it has to be Vista/2008 drivers?

As far as I know (and I don't know very much) WinPE is still XP based.

Mike

I was told by support WinPE 1.6 is XP. WinPE2.1 is the new driver model (Vista/2008) and has been re-written for that. The fact XP drivers worked for you means it was a fluke and the drivers supported both XP/Vista, or else you are using an older WinPE.

Hi Brandon,

This is crazy huh? I've done DOS -> Linux -> WinPE ->WinPE2 and then back to Linux. Our push back to Linux was after a DS6.9 upgrade when our WinPE started automation cycling (when delivered of PXE). This was unsolvable by support.

I feel a bit like a ping-pong ball.

Altiris needs to be much more pro-active in recompiling their Linux environments for the latest kernels and driver support if Linux automation is to be of any practical use for recent models. And we have to separate this somehow from the DS version too. It's crazy to upgrade a working DS just to support more drivers and risk breaking your DS functionality in the process.

But I hear you -If you can use a Windows automation (WinPE 1.6 or 2.1) then you'll be certain of the best driver support and general product support too.

Kind Regards,
Ian./

I can rebuild in winpe 2 in IDE mode in the bios, with the right network card driver for vista.

Hi,

I've managed to get the Linux driver now working here for the dc7900, and i'm imaging a model as we speak. I've had to use a different method and hack the old driver, but it seems to work.

You can download it here: ahci.ko

I'm sodding happy this works.

Kind Regards,
Ian./

Thank you Thank you Thank you! I loaded the hacked driver file and am now able to image my Dell OptiPlex 760's. Thanks again!

Glad that your first time these forums has been so positive for you! The Dell 760 and the HP 7900 have the same controller so if one works -the other will.

Now all I have to do it get all this working when the BIOS's are set to IDE mode too.... ;-)

Kind Regards,
Ian./

Hi All,

I can't get my PXE Linux working for the DC7900 ...

I added the new driver but the linux comes up and then the system reboots ...

Can anyone help ?

Gtz,

Bart

I sent the DS support team a 7900 and a 960.

They have written up the KB articles to support the ich10 in raid mode.

You can find it in the KB articles. (45286)


- @ltirisDude

linky

(45286)

Hi Bart,

Try the troubleshooting steps in the other thread on this:
http://forums.altiris.com/mess...id=53785&enterthread=y

Are you getting an error in the console? Or is automation just rebooting? Remember aside from the SATA controller support you'll also need to NIC support added too. The KB article posted by@ltirisdude has the details for this.

The patched sata driver in the KB is the one we gave support last week, so either one will do. In the version that I post, i've modified the version number though so you can tell if the patched driver is the one that loads (or the native module from the Altiris Linux environment).

Remember to put your disk into AHCI mode. I've been working on a module to image in IDE mode, but I am getting some instability. Will determine whether this is because of a network glitch, or a driver problem before I let it out the cage.

Kind Regards,
Ian./

Hi Ian,

Thank you for trying to help me :-)

I'm get following errors during the PXE boot:

0000:00:19:0 Failed to initialize MSI interrupts - Falling back to legacy interrrupts

ACPI: Invalid PBLK length [7]

The rest seems to be ok except it reboot instead of saying Deployment Server has instructed to wait

Gtz,

Bart

Hi Bart,

Those errors you're seeing are normal (at least in my experience!!). Do you see automation actually mounting the deployment share? Does it get that far?

See the attached LinuxAuto-ShareMapped.jpg to see what you should expect.

I still suspect a NIC issue, so when Linux automation loads try checking your NIC status with,
<b>ifconfig</b>

I've done a screenshot too of what to expect here -LinuxAuto-ifconfig.jpg

Kind Regards,
Ian./

Hi Ian,

I got the system to work many thanks for your help and understanding !!!

Gtz,

Bart

No problem Bart, glad its working.

Kind Regards,
Ian./

Is anyone out there still having difficulty imaging a RAIDed Dell Optiplex 960?

I made a new image with the 960 (Raid On)
I have no trouble putting an image on the machine, but it only works in legacy mode.

As far as I know, I have the most recent Linux SATA controllers for DS 6.9. Once I image the machine in any raid mode, it just sits there (no blue screen) Is there something silly that I am missing? 

 Hi Parklifer,

Can you let me know the controller device IDs? I don't have an Optiplex 960, but I might have other models which have the same controller on them to test.

Kind Regards,
Ian./