Hi,



Try using the Linux FRM from 6.9SP1 -it might work. I was working on a dc7900 and experienced similar issues. HP though reclaimed it before I could get it in our HII pool. We've asked for it back, so hopefully i'll be able to continue this in about a week or so.



Kind Regards,

Ian,.

Hey Ian.

Thanks for the tip. I tried it but ran into a problem where I was getting an error -101 "No express mount found". Maybe I am missing something? As soon as I copied back the 6.9 frm, I stopped getting that error, but...disk not found, which was, I guess, to be expected.

thanks again.

Jon

Does anyone got it working for the linux PXE ??



Thanks !!!



Bart

Grr... I'm still waiting on HP to deliver... anyone else had any luck?

No luck.

Just got a dc7900. It looks like that the Linux build doesn't contain the right drivers for this chipset. We'll have to wait until Altiris updates their Linux build to include support for it. The Linux PXE doesn't even work in IDE emulation mode.

We've been *promised* delivery of an dc7900 by HP for early next week, and HP engineers have *promised* to call to resolve the issue of imaging this model. I'll post back next week with the results...



Kind Regards,

Ian./

I'm interested in a solution too. The intel nic driver from here works:



https://kb.altiris.com/display...?aid=43591&r=0.2648737



But the via82cxxx driver for the hard drive didn't work.



I can actually image for about 20 minutes in freedos, but then I get a memory error. I have a big 20 gig image.



In winpe, I can't get on the network.

With WinPE, you'll have to add the drivers. Unfortunatly, I wasn't sure what driver it was, so I downloaded all the Network drivers for the 7900, extracted them all, and installed every INF file. It was around 20 or so INF Files. But it worked.

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./



(I've also added this also to another thread as we seem to have two threads going for the dc7900!)

Hi,



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./

Tried the new driver, Ian, and it's still a no-go. Thanks for trying!



I hope this gets resolved soon... I really don't want to use DOS and we dont own WinPE.

Winpe comes with 6.9.

Nice work, Ian! I am going to download your driver and try it out...



I, too, am currently imaging a 7900, but not with Ian's driver. KB 45286 says that if you change the BIOS to RAID, it will work. And I can confirm that is does.

Well, I downloaded the driver and added it to my boot disk, but I can't get the system to detect the hard drive when it's ACHI or IDE.



Any tips?

Hi Jenifer,



The first thing to do is put your Linux automation into a wait state -this will give you time to rummage. The next thing to check the device ID for your SATA controller on your pci bus. Type,



lspci



You should see in there your sata controller as SATA Intel Unknown (or something similar). Make a note of the pci bus digits x.y.z which prefix the entry, and then type



lspci -n



This output gives you the bus prefix and the vendorIDeviceID. On my system, the SATA controller is seen as 8086:3a02



If that's all OK, then its time to check the driver. First, check that it's loaded by typing,



lsmod



You should see ahci and libata loaded. If not, its time to take a look at the module. Your module should be in a path like /lib/modules/2.8.18.8/kernel/opt/bdc (sorry I can't confirm this -i'm not in office). In this folder you should only see the drivers you've added through bootdisk creator. Once in this folder type,



modinfo ./ahci.ko | grep "3A02"



This should produce a single line output showing an alias line for this device ID. If no output is seen, then this is the old module and you're probably getting the old cached version.



If you type,



modinfo ./ahci.ko



You should see that it's version 2 of the ahci code. I tried to patch previously version 3 of the ahci source -so if version 3 pops up it is the old one. Thinking ahead, I'll recompile the module today showing that its version 2.1 to reflect that i've patched the version 2 source.



Let me know what the above gives, and we'll see if we can get it sorted.



Kind Regards,

Ian./

Hi Jenifer,



Just to add -Altiris support have tested this successfully in their lab and they'll be putting it into a KB shortly. So, it's worth persevering.



When I did this, I added the driver through the bootdisk creator. Not sure if this is any different in the end from copying it over the the Bootwiz folder directly though.



Kind Regards,

Ian./

Hey Ian.

Thanks for this. Despite my best efforts I continue to learn something new.



Your assistance with Jennifer is helping me as well.

I am following your instructions and appear to be missing ahci and libdata when I run lsmod. I also show the SATA controller as 8086:3a02



When looking at the module, 3a02 does not come up but the version number of the .ko file is version 2

I will try to reload the driver in the bootdisk and see if maybe I goofed somewhere (always a possibility)



Thanks for all of your assistance.



Jon

Well, just reloaded the driver into the Bootdisk and refreshed the PXE services and its working!

Thanks so much to Ian (especially) and to Jennifer for asking the questions that led to troubleshooting steps.



Jon

Thank you for the steps, Ian... Here's the results.



Vendorevice = 8086:2822

We see version 2 of the ahci code.



Sooo.... when the PXE boot disk loads and go through it's thing, we get this line:



achi: version magic '2.6.18.8 smp mod_unload 686 regparm gcc-3.4' should be '2.6.18.8 smp mod_unload 686 regparm gcc-4.11'



~Jenifer

I've changed the driver now so it comes up as version 2.01 when running modinfo -this will help should to ease any confusion should we ever need to diagnose problems with it.



In the above troubleshooting steps, i've just ammended the grep statement to read "3A02" rather than "3a02" as the whole case sensitivity thing will get you otherwise... ;-)



Kind Regards,

Ian./

Hi Jenifer,



This is an old version of the driver that you're loading up. In case you've got some site caching going on, here is another link:



http://users.ox.ac.uk/~iana/ahci2.ko



I've only tested so far with the SATA controller in AHCI mode, but the deviceID 2822 should also be supported in this driver.



Kind Regards,

Ian./

Ohhh... It's working now! Thank you so very much for your help, Ian!



Now to get my driver injection to work... (Well, figure out which driver is not letting the computer boot into mini-setup).

How do you put the linux automation into a wait state?

I run a script like this:



sleep 100000



pauses for about a day

Hi,

I got my DS working to deploy our XP image with Linux PXE but when i created a Bootable DVD with this image it stops during the Linux PXE boot.
Can anyone help or advise ?

Thanks !

Bart