I completely removed all of the cached files and recreated/redownloaded them (image, all apple updates). Im still getting the same problem. Ive tested a 6,2 and a 4,1 mbp with no issues. The 3,1s that I have all fail with that kernel panic which im guessing is a nic driver issue.

Anyone have the same problem? My next step is to comment out the combo update from the vanilla catalog.

Well all things point to the image. I have two test servers, 1 vm and 1 running on a 3,1 mbp. Tried creating the netrestore from both and same problem. Ill try the image I created tonight without the combo update tomorrow.

Ill try that deploy to 3,1 then capture it again but im not sure how that will affect the 4,1 or 6,2 deployments. Im trying to be as universal as possible. Thanks for the feedback.

To clarify im using instadmg to create the dmg images. in this case im using only the vanilla catalog. I then create a netboot image by starting SIU, I select “Net Restore Image” and then create the netboot without any customizations. I select the new image in server admin and then test with a network boot.

Ive confirmed in my lab that something is up with the 10.6.5 combo update regarding 3,1 macbook pros. I created a new netboot image without it but with all the other standard updates as of Nov 2 and it work with all of my macs (3,1/4,1/6,2 mbp). I also have a new pic that has more 3,1 10.6.5 update kernel panic details below

Ok looks like I got an acceptable solution. I took the i386 folder (/library/netboot/netbootsp0/mynetrestore.nbi/i386) from a 10.6.5 less image which contains the boot files and slapped it on my latest custom image with 10.6.5. It works for my 3,1s and my 4,1 but not the 6,2.

I get around this by having two identical image folders with different i386 boot files and then filter by model. Do this by going to server admin -> netboot -> settings -> images -> click on bottom left pencil icon. Thanks for the help.