[GUIDE] Installing Leopard on Dell Studio XPS i7

[chipset]

@lun_IX, chipset,

 

Have you guys had any issues getting the 48x0 drivers running properly on the Vanilla install? Last week I ordered the Sapphire Radeon HD 4870 1GB and popped it in the computer this weekend. I booted into my vanilla install and to no surprise I got a flash of blue then a blank screen. I booted into safe mode and installed the drivers and removed the EFI strings and rebooted with -f (dvi2vga adapter in second port, monitor in first port) with the same results.

 

I figured heck, what do I have to lose, let me try installing it on my iAtkos (rescue) partition. Installed in iAtkos, rebooted, works perfectly without dvi2vga adapter, QE/CI enabled and everything. I think I will wait until 10.5.7 is released before trying to get the drivers working again in the Vanilla install. Call me naieve, but since the new Vanilla kernel will support i7 natively as well as the 4800 series of ATI cards, we shouldn't have to install special drivers.

 

One thing to note is that the iAtkos kernel at boot time is "custom", whereas I am using Voodoo 9.6.0 "mach_kernel.voodoo" for my Vanilla install... methinks there is a slight difference in how the kext is addressed.

 

@all

 

Sound

Making some progress getting sound working. The Vanilla AppleHDA.kext was patched using Taruga's AppleHDA Patcher 1.20 with a codec dump produced from Mandriva Linux. I just need to get the HDAEnabler.kext patched with the right pinconfig. Once I have that working I will see what I can do to integrate it with DSDT.aml

 

Power Supply

One thing I noticed this weekend is that the power supply is adequate only for stock stuff and is only good for running apps that don't draw too much power. I booted into Vista and fired up Crysis with the new card. A few seconds after it started rendering the scene in 1280x1024 at high detail, 4xAA, the computer just powered off, no warning whatsoever. I tried it a few more times and it did the same thing. I had a spare 500W PS lying around and figured I'd give that a try. Worked like a charm!

 

If you plan on doing anything graphic intensive and plan on having more than one HDD in the computer, please upgrade your power supply!

 

I noticed a few differences on the video card. I am using the 4850, so it may be a bit different. On mine, I had to change the port it used to display the graphics. I am not completely thrilled as the card didn't offer a 1920x1200 resolution, which is native for my 24" Samsung. So, I am running 1600x1200, which is a little distorted.

 

My card has two DVI and one SVideo out. I am using a DVI to VGA adapter as the MBP is using the DVI connection.

 

As for the PS, I knew it would be an issue. I am driving two drives on mine without a problem. I plan on upgrading it one day.

 

And good luck on the sound.

[lun_IX]

@WilliamsEph97:

Will try to find some time to get my brain spill out all the steps i did to get up and running.

 

@teddiesmooth:

I installed the Ati drivers from my iATKOS installation, not directly running the vanilla.

Also you might try to use the second DVI port for the monitor and put the adapter on the 1st port. That worked for me.

 

Regarding the power supply: Yeah, it's a bit on the weak side providing 360 watts.

But how did you manage to connect your 4870, doesn't it need to 6-pin power connections?

My system is working quite fine with two HDDs. So a 2nd HDD should be fine in any case.

 

But if you manage to patch the audio kext's that'd be awesome! Good luck with that!

 

@chipset:

Maybe you should plug your MacBook to the VGA Port and the Hack to the DVI... that way you should be able to get both systems running at the native resolution.

[teddiesmooth]

@teddiesmooth:

I installed the Ati drivers from my iATKOS installation, not directly running the vanilla.

Also you might try to use the second DVI port for the monitor and put the adapter on the 1st port. That worked for me.

 

I'll have to give it a try tonight.

 

Regarding the power supply: Yeah, it's a bit on the weak side providing 360 watts.

But how did you manage to connect your 4870, doesn't it need to 6-pin power connections?

My system is working quite fine with two HDDs. So a 2nd HDD should be fine in any case.

 

I had ordered a SATA power to 4-pin adapter with the card and used one of the two PCI-e power connectors that came with the vid card. It boggles my mind that Dell decided not to put regular 4-pin connectors with their PS.

 

But if you manage to patch the audio kext's that'd be awesome! Good luck with that!

 

It pains me to keep rebooting the computer every time I make a change to the HDEnabler.kext but I feel as though it's a necessary evil. I am not confident that HDAEnabler.kext can be loaded properly with kextload.

[Daft Wullie]

Hi all,

 

I've been trying to install OSX on my studio xps for a while now using boot-132 and a purchased retail disk of 10.5.6 but have been unsuccessful. I get Darwin to start, but then after a few screens of text, I get a white flash on my screen and the machine reboots. I never even make it to main installation window.

Before I give Yardie's method a go, Is there a reason why boot-132 wouldn't work, even if the proper kexts were used in the bootloader?

 

grts,

Vince

[Yardie]

Hi all,

 

I've been trying to install OSX on my studio xps for a while now using boot-132 and a purchased retail disk of 10.5.6 but have been unsuccessful. I get Darwin to start, but then after a few screens of text, I get a white flash on my screen and the machine reboots. I never even make it to main installation window.

Before I give Yardie's method a go, Is there a reason why boot-132 wouldn't work, even if the proper kexts were used in the bootloader?

 

grts,

Vince

 

 

That would depend on a lot of things. Most important is what kernel is in the boot-132 and what kexts are being loaded.

 

I was never able to get boot-132 to work. Even when I disabled 3 cores and shutdown almost all CPU features. I didn't get enough information to know which kernel was being loaded by the boot CD. The i7 won't work with the vanilla kernel. The only kernel I found that worked are the Voodoo 9.6 beta and the 9.1 modbin kernels.

 

I did mine installation that way because the two installers I had one was using the voodoo 9.5 kernel which is known not work with i7. iAtkos worked, and Kalyway 10.5.2 worked but KPed when loading a kext. I didn't have the resources to create my own boot132. You need a working OS X to create a custom boot132, if you need all of that you might as well install the leopard while you are up and running.

[chipset]

@chipset:

Maybe you should plug your MacBook to the VGA Port and the Hack to the DVI... that way you should be able to get both systems running at the native resolution.

 

I would, but my Mac is the new MBP with the Mini Display Port. I don't feel like buying another adapter to run VGA (as the DVI connector cannot be used with a DVI2VGA adapter).

 

That, and 10.5.7 should be out soon with native support for the 4850. That will solve my issue. Only one known issue for 10.5.7.

[Daft Wullie]

Ok, so I decided to give it a try.

Did everything the way you described without natit.kext and graphics update.

First install goes ok but then after reboot I get the gray screen with apple logo and revolving timer icon for about 5-10 minutes before the screen turns to attached image and system freezes...

I left it for a while, since you mentioned you thought yours had crashed, but nothing happened after 20 mins.

Is this a graphics issue?

I'll try with some other options. You never know...

 

V

[chipset]

Ok, so I decided to give it a try.

Did everything the way you described without natit.kext and graphics update.

First install goes ok but then after reboot I get the gray screen with apple logo and revolving timer icon for about 5-10 minutes before the screen turns to attached image and system freezes...

I left it for a while, since you mentioned you thought yours had crashed, but nothing happened after 20 mins.

Is this a graphics issue?

I'll try with some other options. You never know...

 

V

 

The logo pause is a known issue and there's a fix. Once you are set, you can update the system. See the first post, it talks about a pause. There's a patch (DSDT) that must be run to get rid of the pause.

 

 

Yes, that's a graphics issue. However, you aren't going to be able to do much with those graphics. If you can, try booting into safe mode. I believe that option is -f at the boot options screen.

[lun_IX]

You have two options now:

 

1. Boot into your iATKOS install, and install the graphics driver onto your vanilla system.

2. Boot your vanilla into failsafe-mode, using the "-x" option and then directly install the graphics update.

 

After a reboot it should be fine. If it still doesn't work try switching the DVI2VGA Adapter and the DVI-Monitor-Cable.

 

I've had the same garbled screen and finally got it working, so no worries!

 

Wish you best of luck!

[titelio]

Panic kernel.

 

I have Dell Studio XPS with 8gb Ram and Ati Radeon 4850.

 

After installing everything using the steps in this guide, I have the following problem:

 

 

How can I fix it.

[teddiesmooth]

Hey all, I have some promising news on the sound front. I am able to get the kext loaded and have the proper inputs and outputs showing up in the sound pref pane and in the System Profiler. However, I cannot get sound out of any of the ports.

 

I think it can be traced back to how the codec address is described in the dump from Mandriva. Maybe OSX uses ATI as address 2 and the onboard as address 0?

 

I am hoping someone here has a sound system with an S/PDIF optical input to test this out. I do not get any sound unfortunately. I am switching the pin config to codec address 0 and seeing what kind of results I get.

 

Cross your fingers and toes!

ALC888kexts_beta.zip

[lun_IX]

Panic kernel.

 

I have Dell Studio XPS with 8gb Ram and Ati Radeon 4850.

 

After installing everything using the steps in this guide, I have the following problem:

 

 

How can I fix it.

 

Try replacing the ACPI related kexts.

I think i've had the exact same problem using the kext's from digital_dreamers package.

After changing them to the one's provided by Yardie it just worked.

 

Or maybe it was the other way round? Yardie's didn't work, but digital_dreamer's?! Mhm, can't remember... just try both.

 

 

@teddiesmooth: How am i supposed to get to work now? With toes and fingers crossed... damn. Should call my boss.

[titelio]

Try replacing the ACPI related kexts.

I think i've had the exact same problem using the kext's from digital_dreamers package.

After changing them to the one's provided by Yardie it just worked.

 

Or maybe it was the other way round? Yardie's didn't work, but digital_dreamer's?! Mhm, can't remember... just try both.

 

 

@teddiesmooth: How am i supposed to get to work now? With toes and fingers crossed... damn. Should call my boss.

 

I made the changes and does not work

[chipset]

Teddie,

 

Good luck on the sound. I don't have one or I would try it for you.

[lun_IX]

I made the changes and does not work

 

Did you try replacing all the kext's?

[teddiesmooth]

Teddie,

 

Good luck on the sound. I don't have one or I would try it for you.

 

No worries. The speaker setup I have are an older (2002?) Boston Acoustic S/PDIF RCA connector type that I had received from my uncle after he got his iMac in '04 (and became useless for his computer). Great speakers but no optical input so they're pretty much useless with this PC. Luckily my monitor has audio input that works well and I have some headphones to test out with.

[titelio]

Did you try replacing all the kext's?

 

 

Do not install correctly the "ketxs". This resolved and now works perfectly.

 

Thanks.

 

 

What driver you installed for the video card?

And you sound card works?

[teddiesmooth]

I just want to reiterate that the sound kexts that I attached show the proper inputs and outputs, however under my current build of the kexts I cannot get any audio. Hopefully someone can verify these?

 

Things are looking promising.  I have been reading around about the HD Audio spec and found a tool for MS Windows (yeech) through the MSDN website that gives the pin mappings. This utility is called High Definition Audio Utility 2.2 (HDUA.exe) and I can't seem to find it anywhere on the interwebs except for through the MDSN extranet (lame), which requires authentication. I requested access earlier this afternoon, and to no avail, have not received a response from that email (uaa@microsoft.com). Supposedly this application gives you no BS about what pinouts are configured to which jacks, etc. Who knows, we might even be able to tackle HDMI audio with this as well

 

I would like to try getting this working before the weekend, otherwise we'll have to go another weekend in integrated audio silence.

 

@lun_IX - Don't cross your fingers and toes so hard, they'll cramp up. Work is important! So is life!

[chipset]

I used to have MSDN access, but I don't anymore. Sorry there.

 

My keyboard's volume controls do cause the volume to change on my system (meaning the graphic and sliders move). However, I have no sound.

[yeraym]

I just want to reiterate that the sound kexts that I attached show the proper inputs and outputs, however under my current build of the kexts I cannot get any audio. Hopefully someone can verify these?

 

Things are looking promising.  I have been reading around about the HD Audio spec and found a tool for MS Windows (yeech) through the MSDN website that gives the pin mappings. This utility is called High Definition Audio Utility 2.2 (HDUA.exe) and I can't seem to find it anywhere on the interwebs except for through the MDSN extranet (lame), which requires authentication. I requested access earlier this afternoon, and to no avail, have not received a response from that email (uaa@microsoft.com). Supposedly this application gives you no BS about what pinouts are configured to which jacks, etc. Who knows, we might even be able to tackle HDMI audio with this as well

 

I would like to try getting this working before the weekend, otherwise we'll have to go another weekend in integrated audio silence.

 

@lun_IX - Don't cross your fingers and toes so hard, they'll cramp up. Work is important! So is life!

 

 

@teddiesmooth

 

I have tried your kexts but still no sound. I have created a codecgraph from my ubuntu codecdump which is exactly the same as yardie's codecdump. Maybe you can find the pin mappings out of this.

 

I have also the Vista PinConfigOverrides (which has address #0):

01171c40 01171d01 01171e43 01171f99

01471c10 01471d40 01471e01 01471f01

01571c12 01571d10 01571e01 01571f01

01671c11 01671d60 01671e01 01671f01

01771c14 01771d20 01771e01 01771f01

01871c50 01871d98 01871ea1 01871f01

01971c60 01971d98 01971ea1 01971f02

01a71c5f 01a71d30 01a71e81 01a71f01

01b71c20 01b71d40 01b71e21 01b71f02

01c71cf0 01c71d11 01c71e11 01c71f41

01d71c19 01d71da6 01d71e16 01d71f40

01e71c30 01e71d11 01e71e45 01e71f01

01f71c70 01f71d11 01f71ec5 01f71f01

 

I modified it to match Leopard specification (I found a guide in this forum):

01471c10 01471d40 01471e01 01471f01

01571c10 01571d10 01571e01 01571f01

01671c10 01671d60 01671e01 01671f01

01771c10 01771d20 01771e01 01771f01

01871c50 01871d98 01871ea1 01871f01

01971c60 01971d98 01971ea1 01971f01

01a71c50 01a71d30 01a71e81 01a71f01

01b71c20 01b71d40 01b71e21 01b71f01

01c71cf0 01c71d11 01c71e11 01c71f41

01d71c10 01d71da6 01d71e16 01d71f40

01e71c30 01e71d11 01e71e45 01e71f01

01f71c70 01f71d11 01f71ec5 01f71f01

 

I removed the first line because I haven´t seen it in the others codec verbs but I'm not sure about this.

 

I replaced your ConfigData with this verbs with the same result.

 

I hope this will help you.

Good luck

 

Attached file:

- Realtek ALC888 codec_2.zip -> My codecgraph

- PinConfigOverrides.zip -> PinConfigOverrides Vista's regedit export

Realtek_ALC888_codec_2.zip

PinConfigOverrides.zip

[teddiesmooth]

@teddiesmooth

 

I have tried your kexts but still no sound. I have created a codecgraph from my ubuntu codecdump which is exactly the same as yardie's codecdump. Maybe you can find the pin mappings out of this.

 

I have also the Vista PinConfigOverrides (which has address #0):

01171c40 01171d01 01171e43 01171f99

01471c10 01471d40 01471e01 01471f01

01571c12 01571d10 01571e01 01571f01

01671c11 01671d60 01671e01 01671f01

01771c14 01771d20 01771e01 01771f01

01871c50 01871d98 01871ea1 01871f01

01971c60 01971d98 01971ea1 01971f02

01a71c5f 01a71d30 01a71e81 01a71f01

01b71c20 01b71d40 01b71e21 01b71f02

01c71cf0 01c71d11 01c71e11 01c71f41

01d71c19 01d71da6 01d71e16 01d71f40

01e71c30 01e71d11 01e71e45 01e71f01

01f71c70 01f71d11 01f71ec5 01f71f01

 

I modified it to match Leopard specification (I found a guide in this forum):

01471c10 01471d40 01471e01 01471f01

01571c10 01571d10 01571e01 01571f01

01671c10 01671d60 01671e01 01671f01

01771c10 01771d20 01771e01 01771f01

01871c50 01871d98 01871ea1 01871f01

01971c60 01971d98 01971ea1 01971f01

01a71c50 01a71d30 01a71e81 01a71f01

01b71c20 01b71d40 01b71e21 01b71f01

01c71cf0 01c71d11 01c71e11 01c71f41

01d71c10 01d71da6 01d71e16 01d71f40

01e71c30 01e71d11 01e71e45 01e71f01

01f71c70 01f71d11 01f71ec5 01f71f01

 

I removed the first line because I haven´t seen it in the others codec verbs but I'm not sure about this.

 

I replaced your ConfigData with this verbs with the same result.

 

I hope this will help you.

Good luck

 

Attached file:

- Realtek ALC888 codec_2.zip -> My codecgraph

- PinConfigOverrides.zip -> PinConfigOverrides Vista's regedit export

 

Eh, I expected that the sound wouldn't work but I wanted to know if anyone could test with a Toslink S/PDIF receiver or speaker system.

 

I've been using a couple of the guides on the forums. After uploading the kexts the other night I tried changing the codec address from 2 to 0 and yes, my verbs come out to the same as yours using the dump from Mandriva. What I did notice is that some of the nodes that are put in using the apple HDA kext using Taruga's Patcher (1.20) don't match up with the SVG graph, and others aren't included at all in the patched HDA file. The patched HDA file that I included has those pinouts changed but I didn't add any info from the other nodes. I think the only way that we are going to get sound working on this is to manually add each of the node information per line of verb data, and to make sure each line in the Layout portion of the HDA kext match up with each verb of the config data.

 

I've given up on the sound kexts until 10.5.7 comes out (should be soon, right?). Last night I picked up a decent pair of speakers (Logitech Z-5) that connect via USB and work great in OSX. When I get home tomorrow I'll post all of the raw files if anyone wants to work this out.

[titelio]

New driver for alc888

 

http://forum.voodooprojects.org/index.php/board,10.0.html

[titelio]

Install VoodooHDA-0.2.2

 

I get this devices in the Sound Preferences Panel :

 

On the 'Output' section

Unknow (Here headphones in the rear panel working but distort)

Headphones (Here headphones in the front panel working properly)

SPDIF-out

SPDIF-out

 

And on the 'Input' section:

Mic

Mic

SPDIF-in

 

Mic inputs aren't working.

[lun_IX]

What did you do to install that kext?

Did you delete any present kext's?

[titelio]

What did you do to install that kext?

Did you delete any present kext's?

 

Delete AppleHDA.kext and install VoodooHDA.kext