Jump to content

Dell XPS 1340 under OSX 10.6, including boot-132 install cd

bcc9

By bcc9,
in Installation Guides

 Share
1,149 posts in this topic

Recommended Posts

kalewallace
kalewallace
Posted
Posted
I get the same warning. It's a Dell BIOS warning, that says the CMOS has reset or something. It only happens after running in Mac OS X though. So I'm figuring its a result of some sort of interaction between OS X and the BIOS?

 

@mikeaffone

 

Bingo. Doesn't seem to cause any problems, but it does indeed occur only after running OS X. I'm not 100% sure, but it seems to coincide with the laptop having trouble waking (or going) to sleep.

 

???

Link to comment
Share on other sites
mobilemodman
mobilemodman
Posted
Posted

Hey guys I need a bit of help, I've got 10.5.8 up and running, and chameleon 2.0 installed, however I cannot get the audio to mute when headphones are plugged in, apparently Elecktron stated that he was able to fix that using the solution provided in the first post of this thread, So I put the new DSDT.aml into /Extra, and I've installed the provided idt kext via osx86tools. however its not fixed anything :)

 

Also i've got voodooPower installed, just wondering if the multiplier with cpu-x is supposed to be a static value or dynamic (for throttling), I've got it static at 10x?

 

Edit: got the sound working, I just copied the text from the plist inside the IDT kext and saved it into the plist inside the appleHDA kext, and then installed the modified appleHDA kext via osx86tools :)! - still wondering about the CPU multiplier state? (Bcoz it seems as if the fan is running all the time, something is generating a fair bit off heat)

Link to comment
Share on other sites
one9092002
one9092002
Posted
Posted
Here's what I've figured out so far on getting OSX working on the dell studio xps 1340, aka dell studio xps 13 under Snow Leopard.

 

Working "out of the box":

  • gig-ethernet, usb, firewire, sata
  • system suspend
  • touchpad as mouse
  • webcam (video only), video capture verified with photo booth application
  • bluetooth in HID mode (think dumb mouse)
  • Dell 1515 802.11 wireless (note: Atheros driver is 32 bit only)

Working with mods below:

  • GeForce 9400M G graphics with quartz extreme, external HDMI/VGA/display port
  • Built-in speaker, headphone jack, internal mic (without volume control), hotkey volume/mute controls
  • Intel speedstep
  • Touchpad gestures, and working touchpad after resume with modified version of voodoo team's Voodoops2controller
  • battery status & suspend on lid close
  • Bluetooth in HCI mode (full functionality)

Not working:

  • Gain for built-in digital mic, mic-in jack
  • SLI with 9500m video
  • SD flash card. I've tried VoodooSDHCI, but I just get an 'VoodooSDHC: no response from CMD_8 -- ComInhibitCMD" error upon card insertion, and the system hangs.

Not tested yet (let us know):

  • Infrared
  • expresscard

Update: For installation, you can either install 10.6 using a previous install of osx to install from, outlined here or using a boot cd install method, instructions for that are at the end of this post.

 

For basic installation, there are snow leopard install guides sprouting up all over the place. I'm not sure what the best guide is, but I have the following install recommendations.

  • I'm not sure if this is necessary but... Before the install you can setup your /Extra/smbios.plist so that the model name isn't genuine (parts of the installer look at this; I'm not sure if leaving the model set to MacbookPro4,1 causes failure or not, but it seems to cause issues...) I use: smbios.plist.v2.zip After installing this file, reboot & verify that system profiler has 'Model Identifier:' set to "Studio XPS 1340". (Later, after the 10.6 install place a copy of smbios.plist into your 10.6 /Extra partition as well.)
  • Some guides recommend installing a bunch of hackintosh kexts: OpenHaltRestart, NullCPUPM, PlatformUUID. The only kexts necessary for booting snow leopard on this platform are one to defeat the runtime DSMOS check and one to provide a usable keyboard+mouse. For the former, the only kext supported as of 10.6.2 is fakesmc . The keyboard kext is detailed below.
  • If you care about having an MBR partitioned disk (fairly important if you also want linux or windows to be able to deal with partitioning changes on the disk), you'll need a modified OSInstall binary that stops mandating a GUID partitioned disk. Diamondsw posted a patched version here. Replace the version in /Volumes/Mac OS X Install DVD/System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/OSInstall (on your snow leopard dvd or usb/flash/esata based install drive). This change is unnecessary if you are happy with GUID partitioned disks.

Once you've installed 10.6, and a hackintosh bootloader (Chameleon 2.0 or Netkas pci-efi v10.x), you can add the rest of my changes to get platform specific components working fully. For the case where you don't have a fancy multi-boot setup to worry about, probably the easiest bootloader setup is to use the chameleon installer, the newest seems to be named: Chameleon-2.0-r431.pkg.zip

I have not used the above installer myself as I do have a complex multi-boot setup for which I don't trust beta installers to do the right thing. I simply used the 3 install comands (which are detailed in chameleon's doc/README under "Normal Install") to install chameleon manually.

 

I recommend that all kext additions you make be installed in /Extra/Extensions. As I add or make changes to /Extra/Extensions, I use the following commands to keep its cache up to date

rm -f /Extra/Extensions.mkext /Extra/Caches
         kextcache -m /Extra/Extensions.mkext /Extra/Extensions

 

As of 10.6.2, all system kexts support both 32&64 bit mode. In any case, I recommend 32 bit as a starting point, as genuine macs use 32 bit mode. So I recommend editing /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and adding arch=i386 -v to the Kernel Flags string. Result: com.apple.Boot.plist.zip

 

For working keyboard and touchpad, I recommend my compiled version of the VoodooPS2 kexts, here My version is the stock 0.98 version plus 64 bit support, and the keyboard enhancements posted over here http://forum.voodooprojects.org/index.php/topic,304.0.html, and my fix for the touchpad over here http://forum.voodooprojects.org/index.php/...00.html#msg2300

 

For working quartz Extreme & core image (QE/CI), install my modified DSDT.aml to /Extra/DSDT.aml (note that filename case matters to the boot loader here). My modified DSDT.aml is based upon Dell A06 BIOS. (A06, A07 and A08 BIOS have identical DSDT, by the way). dsdt.zip

 

For working IDT audio, the above DSDT.aml includes EFI strings to point AppleHDA in the right direction, but you'll also need the following kext plist to set up a working pin configuration for the codec. hdaidt.kext.v4.zipYou can then verify working audio by going to the sound effects tab and trying something. Both 1/8" output jacks works as a headphone jacks, with proper headphone jack detection (mutes speakers when jack inserted), except that the right jack mutes the left if you try to use both. Thanks to boombeng for getting the right jack working (and ridgeline/boombeng for their earlier IDT work). Special thanks to the king, master chief, madtux for their work deciphering the applehda pinconfig/pathmap maze.

 

For working CPU throttling (intel speedstep) use my modified version of VoodooPState.kext. . Hnak has a handy monitoring app for checking p-states and temps, PStateChanger, over in this thread, and there's also cpu-x to monitor the CPU multiplier state.Intel speedstep seems to be working out of the box with the modified dsdt. Since appleintelcpupowermanagement handles the stepping, cpu-x will not correctly report the current multiplier or voltage. cpu-x will stay stuck at the max. multiplier for your cpu.

 

For working CPU halt/restart, there is the snow leopard build of OpenHaltRestart: http://www.snowx86.com/downloads/OpenHaltR...for_snow_64.tar

 

For battery status and system sleep upon lid close, there are changes in the above DSDT.aml for that , but you also need

  1. the ACPI Embedded Controller to load properly. Turns out a bug in AppleACPIPlatform was causing the embedded controller (AppleACPIEC) to fail to load, I've made a patch to AppleACPIPlatform to fix that. Attached.. So far my installer supports snow leopard versions 10a421a and 10a432 (no update is needed for OSX 10.6.1).
  2. VoodooBattery, for the battery icon

For bluetooth with HCI, I've written a driver that enables HCI mode, an installer is available here

 

boot-cd based install method:

Install vanilla 10.6 distro onto a dual layer dvd or usb thumb drive or usb disk drive. For a usb based install (this is the method I tested):
  1. setup a usb thumb drive or disk drive, with an hfs+ partition to install on (the destination partition),

  2. run disk utility

  3. right click on destination partition, select restore

  4. select 10.6 dmg file as source

  5. select destination partition again

Take .iso and burn to cd-rw or cd-r

I have pre-built a boot132 iso, available here

 

Boot system from cd

Watch 4 "EBIOS read error: Device timeout" error messages pass by, followed by startup of chameleon

Press F8 to start chameleon graphical menu (or let it timeout for same effect)

From chameleon graphical menu, select "Mac OS X Install DVD", or swap in the vanilla install DVD and boot from that

As bootstrap begins, watch 4 more EBIOS read errors pass by

MacOS installer runs with graphical window

select customize

unselect printer support->nearby and popular printers

Let install complete

Go back and boot from CD again

this time select your newly installed 10.6 distro

viola

You may now complete the configuration of your 10.6 system as described earlier in this post

I could really use some help on the non-working components! Such as:

  • For 9500m, maybe someone could figure out how to get SLI video working. The OSX drivers may not be able to handle SLI at all but it's not clear whether or not that's really true.
  • For audio, it'd be great if someone could figure out the fix to the pathmap/pinconfig to allow the analog&digital mics to fully work.
  • Something seems wrong with the IOAHCISerialATAPI driver. Upon wakeup from suspend the disk activity light flashes every 2 seconds or so apparently with the driver trying to stat the dvd-rom drive. Putting a disk in the drive fixes this.
  • The firewire controller loses its GUID upon wakeup from suspend, logging "FireWire GUID 0000000000000000 is invalid!" over&over to /var/log/kernel.log after wakeup. The workaround in 10.5.x of unloading/reloading the AppleFWOHCI.kext to fix this no longer works as that kext can't be unloaded.
  • Someone could work with zef to help figure out why his SDHC driver doesn't work with the ricoh SD card controller on this system

Contributions welcome

 

 

hi guys i am having dvd problems...if i insert dvd before boot the the dvd is recognize in snow leopard...but if i insert the dvd after boot...it does not recognize dvd...is this is common issue? i running retail snow leopard xps 1340 everything works except that problem?

Link to comment
Share on other sites
mobilemodman
mobilemodman
Posted
Posted

Ok so I figured that cpu-x wasnt displaying the information correctly, I installed cpu-i instead, and It's showing correct values now for the multiplier state. I realised the voltages were extremely high so I edited the voodopower.kext info.plist file to set min voltage to 950 and max voltage to 1012 (altho it seems in osx my min voltage is locked at 1.020, its locked at 1.000v in windows), now it idles at 6.0x 1.020v at around 56~57 degrees ... my idling temp in windows is around 46~47, but im gessing its because the min voltage in windows is 1.000v for the 6.0x multiplier

 

I noticed on the 10x multiplier i get a lower idle temp, perhaps this is because the voltage is too high for the 6x miltiplier (hence more heat) bcoz its 1.000v in windows, and 1.020v in mac osx. I tried playing around with the minPstate and max Pstate keys in the info.plist for voodopower.kext, but it is unable to keep the multiplier at 10x. Is there any other way to disable speedstepping with the voodoopower so its stays at 10x 1.085v (therefore giving a lower idle temp)

 

-----------------

OSX 10.5.8

intel P9600 core 2 Duo @ 2.66Ghz

Link to comment
Share on other sites
glitchbit
glitchbit
Posted
Posted

bcc9, did you fix the usb sleep removal bug? I know in your previous thread and another you were complaining about it and being a 14z user it affects me. I have applied several usb fixes to my dsdt but I have not nailed it yet. Please let me know what your thoughts are on this. Thanks.

Link to comment
Share on other sites
bcc9
bcc9
Posted
  • Author
Posted
bcc9, did you fix the usb sleep removal bug? I know in your previous thread and another you were complaining about it and being a 14z user it affects me. I have applied several usb fixes to my dsdt but I have not nailed it yet. Please let me know what your thoughts are on this. Thanks.
Yes, I fixed it in 10.5.x with the AAPL,clock-id DSDT entries for the USB EHCI devices. Looks like the fix is no longer working with 10.6. I didn't notice myself until this week as I normally just use ESATA.

 

Using AAPL,clock-id to get around power state problems was a pretty fragile fix, looks like we need a better solution at this point. If anyone has seen a better fix (short of marking USB drives as if they were internal) please speak up.

Link to comment
Share on other sites
glitchbit
glitchbit
Posted
Posted
Yes, I fixed it in 10.5.x with the AAPL,clock-id DSDT entries for the USB EHCI devices. Looks like the fix is no longer working with 10.6. I didn't notice myself until this week as I normally just use ESATA.

 

Using AAPL,clock-id to get around power state problems was a pretty fragile fix, looks like we need a better solution at this point. If anyone has seen a better fix (short of marking USB drives as if they were internal) please speak up.

 

Well I downloaded the DSDT file of a Macbook Pro 13" (MacBookPro5,5) and I merged a lot of it EHCx, OHCx device code into my own. I made some changes to the _PRW name though

 

Original

Name (_PRW, Package (0x02)
			{
				0x0D, 
				0x03
			})

 

modified

Name (_PRW, Package (0x02)
			{
				0x0D, 
					0x00
			})

 

If I did not zero out the later part then sleep would not occur properly, my laptop would wake up immediately after sleep. I did this for EHC1, EHC2, OHC1, and OHC2. Of course the 0x0D part changes to 0x17,0x18, and 0x05, depending on the device. Also I don't have to Zero out the later part, I can actually place 0x01 in there as well which I did on a suggestion I saw over at projectosx, but that did not help any.

 

I also recompiled the IOUSBFamily kext in an attempt to modify it to not disconnect the usb devices detected as PCI.. although my devices are indeed detected as built-in.. That had no effect.. but I guess now I could try to purposely make my usb devices to be detected as PCI and see what happens.

 

I also removed all the warnings from my DSDT and relocated the GPE scopes for the usb devices down into the ECHx, OHCx device entries to match the original more.. I think I may have also made some minor changes to my PCI device as well.

 

Here is what my EHCx, OHCx looks like right now. Only thing I did not try to port over into mine was the hub device entry.

 

			Device (OHC1)
		{
			Name (_ADR, 0x00040000)
			OperationRegion (U1CS, PCI_Config, 0x48, 0x04)
			Field (U1CS, DWordAcc, NoLock, Preserve)
			{
						Offset (0x01), 
				U1EN,   1
			}
			Name (_PRW, Package (0x02)
			{
				0x0D, 
				0x00
			})
			Scope (\_GPE)
			{
				Method (_L0D, 0, NotSerialized)
				{
					Notify (\_SB.PCI0.OHC1, 0x02)
					Notify (\_SB.PWRB, 0x02)
				}
			}

			Method (_S3D, 0, NotSerialized)
			{
				Return (0x03)
			}

			Method (_S4D, 0, NotSerialized)
			{
				Return (0x03)
			}

			Method (_DSM, 4, NotSerialized)
			{
				Store (Package (0x03)
					{
						"AAPL,device-internal", 
						0x60, 
						Buffer (0x01)
						{
							0x00
						}
					}, Local0)
				DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
				Return (Local0)
			}
		}

		Device (EHC1)
		{
			Name (_ADR, 0x00040001)
			OperationRegion (U1CS, PCI_Config, 0x84, 0x04)
			Field (U1CS, DWordAcc, NoLock, Preserve)
			{
						Offset (0x01), 
				U1EN,   1
			}
			Method (_DSM, 4, NotSerialized)
			{
			Store (Package (0x0B)
			{
			"AAPL,clock-id",
			Buffer (One)
			{
			0x01
			},

			"device_type",
			Buffer (0x05)
			{
			"EHCI"
			},

			"AAPL,current-available",
			0x04B0,
			"AAPL,current-extra",
			0x02BC,
			"AAPL,current-in-sleep",
			0x03E8,
			Buffer (One)
			{
			0x00
			}
			}, Local0)
			DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
			Return (Local0)
			}
			Name (_PRW, Package (0x02)
			{
				0x05, 
				0x01
			})
			Scope (\_GPE)
			{
				Method (_L05, 0, NotSerialized)
				{
					Notify (\_SB.PCI0.EHC1, 0x02)
					Notify (\_SB.PWRB, 0x02)
				}
			}

			Method (_S3D, 0, NotSerialized)
			{
				Return (0x03)
			}

			Method (_S4D, 0, NotSerialized)
			{
				Return (0x03)
			}
		}

		Device (OHC2)
		{
			Name (_ADR, 0x00060000)
			OperationRegion (U1CS, PCI_Config, 0x48, 0x04)
			Field (U1CS, DWordAcc, NoLock, Preserve)
			{
						Offset (0x01), 
				U1EN,   1
			}
			Name (_PRW, Package (0x02)
			{
				0x18, 
				0x00
			})
			Scope (\_GPE)
			{
				Method (_L18, 0, NotSerialized)
				{
					Notify (\_SB.PCI0.OHC2, 0x02)
					Notify (\_SB.PWRB, 0x02)
				}
			}

			Method (_S3D, 0, NotSerialized)
			{
				Return (0x03)
			}

			Method (_S4D, 0, NotSerialized)
			{
				Return (0x03)
			}

			Method (_DSM, 4, NotSerialized)
			{
				Store (Package (0x03)
					{
						"AAPL,device-internal", 
						0x02, 
						Buffer (0x01)
						{
							0x00
						}
					}, Local0)
				DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
				Return (Local0)
			}
		}

		Device (EHC2)
		{
			Name (_ADR, 0x00060001)
			OperationRegion (U1CS, PCI_Config, 0x84, 0x04)
			Field (U1CS, DWordAcc, NoLock, Preserve)
			{
						Offset (0x01), 
				U1EN,   1
			}
			Method (_DSM, 4, NotSerialized)
			{
			Store (Package (0x0B)
			{
			"AAPL,clock-id",
			Buffer (One)
			{
			0x01
			},

			"device_type",
			Buffer (0x05)
			{
			"EHCI"
			},

			"AAPL,current-available",
			0x04B0,
			"AAPL,current-extra",
			0x02BC,
			"AAPL,current-in-sleep",
			0x03E8,
			Buffer (One)
			{
			0x00
			}
			}, Local0)
			DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
			Return (Local0)
			}
			Name (_PRW, Package (0x02)
			{
				0x17, 
				0x01
			})
			Scope (\_GPE)
			{
				Method (_L17, 0, NotSerialized)
				{
					Notify (\_SB.PCI0.EHC2, 0x02)
					Notify (\_SB.PWRB, 0x02)
				}
			}

			Method (_S3D, 0, NotSerialized)
			{
				Return (0x03)
			}

			Method (_S4D, 0, NotSerialized)
			{
				Return (0x03)
			}
		}

 

Here is what I did to recompile AppleUSBEHCI.. I originally tried doing the entire IOUSBFamily but I had too many compile errors with it.

 

http://www.mediafire.com/file/ezzjkazr2wz/AppleUSBEHCI.zip

 

AppleUSBEHCI_PwrMgmt.cpp

		if (!_hasPCIPwrMgmt)
	{
		//USBError(1, "AppleUSBOHCI[%p]::CheckSleepCapability - controller will be unloaded across sleep",this);
		//_controllerCanSleep = false;
		//setProperty("Card Type","PCI");

	_controllerCanSleep = true;
		setProperty("Card Type","built-in");
	}

 

That's all I changed, according to what bcp355 did, I think that is his name. I then placed the file back in IOUSBFamily and stuck that into my EE folder.. nothing changed.

 

Maybe you can find the solution somewhere else in that code?

 

Also here are some error logs from the debug version of IOUSBFamily.. They are on detail 4, but I have a 23mb log on level 7 as well I can upload it if you want.

USB_Log4_Failure.txt

USB_Log4_MultiFail.txt

Link to comment
Share on other sites
glitchbit
glitchbit
Posted
Posted
So in summary, with all your experimental dsdt changes, they didn't solve or improve anything concerning USB functionality, right?

 

lol that would be correct.. just thought I'd share with you what I have done thus far. I even have an expressCard which has 4 usb ports on it and I tried using it to see if it would keep power over sleep and waking back up, but it loses its connection all the same..

Link to comment
Share on other sites
glitchbit
glitchbit
Posted
Posted

MCP79 USB Sleep Removal Fix

 

Well bcc9 I think I fixed it, it appears to be related to the USB PowerSharing feature. I just need some people to try this out and report back to confirm that this is indeed what fixed it for me... otherwise I will release my current DSDT.

 

Here is what you do

1. Boot up and press F2 to go into your BIOS Setup

2. Go to Advance (I think) -> Then Disable "USB PowerSharing" -> F10 (Save)

3. Boot into OSX with -v, if it freezes during the boot up this is fine, just hold down the power button and repeat this step.

4. Once OSX boots up then it might be necessary to go into sleep, but I am not certain, because this is just what I did personally. You will find that without PowerSharing OSX will go to sleep and then wake right back up (without usb eject error!), this is normal, because now it is time to restart.

5. Go back into the BIOS Setup by pressing F2.

6. Go to Advance (I think) -> Then Enable "USB PowerSharing" -> F10 (Save)

7. Boot into OSX again with -v, and don't be surprised if it freezes again and you need to repeat this step like before.

8. Once OSX has loaded try to go to sleep again and see if you have success and Please let me know!!

 

P.S. I may have just found one limitation, this fix does not work on the hybrid eSata/USB port.

Link to comment
Share on other sites
bcc9
bcc9
Posted
  • Author
Posted
MCP79 USB Sleep Removal Fix

 

Well bcc9 I think I fixed it, it appears to be related to the USB PowerSharing feature. I just need some people to try this out and report back to confirm that this is indeed what fixed it for me... otherwise I will release my current DSDT.

 

Here is what you do

1. Boot up and press F2 to go into your BIOS Setup

2. Go to Advance (I think) -> Then Disable "USB PowerSharing" -> F10 (Save)

3. Boot into OSX with -v, if it freezes during the boot up this is fine, just hold down the power button and repeat this step.

4. Once OSX boots up then it might be necessary to go into sleep, but I am not certain, because this is just what I did personally. You will find that without PowerSharing OSX will go to sleep and then wake right back up (without usb eject error!), this is normal, because now it is time to restart.

With my patched dsdt per post #1, turning off&on usb powershare mode in bios doesn't affect the usb eject error - it happens regardless.

In any case, your instructions make little sense to me as by step #8 you should be in the same state as before you started.

 

I see no fix here.

Link to comment
Share on other sites
glitchbit
glitchbit
Posted
Posted
With my patched dsdt per post #1, turning off&on usb powershare mode in bios doesn't affect the usb eject error - it happens regardless.

In any case, your instructions make little sense to me as by step #8 you should be in the same state as before you started.

 

I see no fix here.

 

You are right, I am leading at least 14z users like myself to re-enabling powersharing after having disabled it. I do not know why it has appeared to fix my 14z.. but from all appearances it has because if I revert my dsdt file back to my initial dsdt patched file my eject error is still gone! (I also think now that this issue may not affect all 14z users.. I bought a refurb with A01, maybe boards that were flashed with A04 from day 1 don't have this bug?)

 

I assumed since 1340 users share the same MCP79 chipset that what appears to work on 14z may work for 1340 users.. but I guess maybe I was wrong? I also reverted my IOUSBFamily kext back to the original before I tried the BIOS fix I mention.

 

Only thing I can figure is that something inside OSX is created or recognized in such a way that it remembers how to deal with my USB ports?? I have no idea how that could be possible, I am not aware of any files osx would modify or create to have that behavior? I would have to re-install OSX to test this theory.

 

Only other thing I could surmise is that there is a bug in the Dell BIOS that is only fixed when PowerSharing is toggled off and back on.. which is probably more likely. It would not be the first time that I have seen toggling a setting has resolved an issue.. at least with ddwrt router firmwares and even my iphone (bluetooth). I wish this was the case with the 1340 as well..

Link to comment
Share on other sites
Kenny Lee
Kenny Lee
Posted
Posted

First off, BB9 thank you for your guide. I'm definitely a noob...and got started only 3 days ago when the thought..."gee, I wonder if I can install OSX on PC..."

 

I did alot of homework/experiment, and finally got this SnowLeopard working on 1340 with Chameleon RC4...and I was thrilled!

 

However, just right now, I installed updates to SL 10.6.2, and now the SOUND is no longer working. I get "mute looking" screen icon when I try to press up and down sound button (Dell touch hardware top of keyboard).

 

I tried reinstalling your "hdaidt.kext" in post #1 (w/ permissions, and cache update - no errors), but the sound REFUSES to work! HELP!

 

There are 2 other issues that I'm not overly concerned about right now, but doesn't work:

a) Bluetooth - I installed your kext...works, but how do you turn it off?

;) It recognizes Battery vs. Power (with your solution), but when in battery mode, it doesn't show percentage or time left. Is this possible?

 

Thanks again for your help!!!

Link to comment
Share on other sites
bcc9
bcc9
Posted
  • Author
Posted
You are right, I am leading at least 14z users like myself to re-enabling powersharing after having disabled it. I do not know why it has appeared to fix my 14z.. but from all appearances it has because if I revert my dsdt file back to my initial dsdt patched file my eject error is still gone! (I also think now that this issue may not affect all 14z users.. I bought a refurb with A01, maybe boards that were flashed with A04 from day 1 don't have this bug?)

 

I assumed since 1340 users share the same MCP79 chipset that what appears to work on 14z may work for 1340 users.. but I guess maybe I was wrong? I also reverted my IOUSBFamily kext back to the original before I tried the BIOS fix I mention.

 

Only thing I can figure is that something inside OSX is created or recognized in such a way that it remembers how to deal with my USB ports?? I have no idea how that could be possible, I am not aware of any files osx would modify or create to have that behavior? I would have to re-install OSX to test this theory.

 

Only other thing I could surmise is that there is a bug in the Dell BIOS that is only fixed when PowerSharing is toggled off and back on.. which is probably more likely. It would not be the first time that I have seen toggling a setting has resolved an issue.. at least with ddwrt router firmwares and even my iphone (bluetooth). I wish this was the case with the 1340 as well..

Are there any other users who share your experience? I didn't notice any other 14z users reporting that toggling powersharing fixed anything with respect to usb for them.

From the symptoms you describe, I suspect you're seeing some sort of time-dependent behavior and/or a kext caching issue but it's hard to tell from here.

 

I tried reinstalling your "hdaidt.kext" in post #1 (w/ permissions, and cache update - no errors), but the sound REFUSES to work! HELP!
You're using hdaidt.kext.v4.zip? The kext was updated to work for 10.6.2 specifically (thus the v4).

There are 2 other issues that I'm not overly concerned about right now, but doesn't work:

a) Bluetooth - I installed your kext...works, but how do you turn it off?

You can turn it on&off with the radio control hotkey (as long as you've left it configured such that it turns off PAN at least).

There's also a software on/off solution in the bluetooth 370 thread.

You can also go back&forth between hid&hci modes with my hid2hci standalone program.

;) It recognizes Battery vs. Power (with your solution), but when in battery mode, it doesn't show percentage or time left. Is this possible?
Yes, there have been bugs in voodoobattery, that kind of behavior started showing up as of 10.5.8. I don't think superhai has sorted the bugs out. You might try his latest 10.6 beta and see if that helps. Let us know.
Link to comment
Share on other sites
Kenny Lee
Kenny Lee
Posted
Posted
You're using hdaidt.kext.v4.zip? The kext was updated to work for 10.6.2 specifically (thus the v4).

Yes I did use "hdaidt.kext.v4.zip".

 

I tried it about 3 times already....with cache/permission reset.

 

Anything that you can think of that a noobie might be missing?

 

FYI - just for kicks, I also tried booting with your BOOT-123 CD into 10.6.2 OSX install and the sound didn't work either.

 

For me, this install would be PERFECT, if the sound as working. Don't really need anything else!!!

Link to comment
Share on other sites
bcc9
bcc9
Posted
  • Author
Posted
Yes I did use "hdaidt.kext.v4.zip".

 

I tried it about 3 times already....with cache/permission reset.

 

Anything that you can think of that a noobie might be missing?

 

FYI - just for kicks, I also tried booting with your BOOT-123 CD into 10.6.2 OSX install and the sound didn't work either.

 

For me, this install would be PERFECT, if the sound as working. Don't really need anything else!!!

My bootcd pre-dates 10.6.2 and so the hdaidt I included therein does not have the 10.6.2 fixes, and so it's to be expected that the audio doesn't work with 10.6.2.

 

Probably you didn't install hdaidt.kext.v4.zip properly, or the dsdt, or the chameleon boot loader.

Link to comment
Share on other sites
Kenny Lee
Kenny Lee
Posted
Posted
My bootcd pre-dates 10.6.2 and so the hdaidt I included therein does not have the 10.6.2 fixes, and so it's to be expected that the audio doesn't work with 10.6.2.

 

Probably you didn't install hdaidt.kext.v4.zip properly, or the dsdt, or the chameleon boot loader.

 

I'm pretty sure I installed hdaidt.kext.v4 and chameleon boot loader correctly.

 

How do I ensure that I install dsdt correctly? Reference to procedures?

 

I'm pretty sure I installed hdaidt.kext.v4 and chameleon boot loader correctly.

 

How do I ensure that I install dsdt correctly? Reference to procedures?

 

OH HELLZ YEAH!!! IT WORKS!!! I'm doing the happy dance right now.

 

Okay, here is what went wrong. I used your "com.apple.Boot.plist" from your BOOT 123 CD, so I didn't have to type in the resolution, arch=i386, blah, blah. See below for the text. I removed the lines in RED and that fixed it!

 

It fixed the SOUND as well as the BATTERY issue that I was talking about.

 

BB9. I'd buy you a beer if you come to Seattle.

 

===========================

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string>arch=i386</string>

<key>Rescan</key>

<string>Yes</string>

<key>Graphics Mode</key>

<string>1280x800x32</string>

<key>Timeout</key>

<string>0</string>

<key>SMBIOSdefaults</key>

<string>No</string>

<key>DSDT</key>

<string>rd(0,0)/Extra/DSDT.aml</string>

</dict>

</plist>

Link to comment
Share on other sites
bcc9
bcc9
Posted
  • Author
Posted
OH HELLZ YEAH!!! IT WORKS!!! I'm doing the happy dance right now.

 

Okay, here is what went wrong. I used your "com.apple.Boot.plist" from your BOOT 123 CD, so I didn't have to type in the resolution, arch=i386, blah, blah. See below for the text. I removed the lines in RED and that fixed it!

Glad you figured it out. It's hard for me to tell where people are going wrong when the are doing extra things beyond what is in post #1 (a common situation :( You don't need any of those com.apple.Boot.plist additions other than the Kernel Flags key&value. You probably don't want some of those other changes such as the smbios override.

 

Thanks, I don't think I'm going to be around washington anytime soon (at least not until the summer weather kicks in for sure...)

Link to comment
Share on other sites
Kenny Lee
Kenny Lee
Posted
Posted
Glad you figured it out. It's hard for me to tell where people are going wrong when the are doing extra things beyond what is in post #1 (a common situation :) You don't need any of those com.apple.Boot.plist additions other than the Kernel Flags key&value. You probably don't want some of those other changes such as the smbios override.

 

Thanks, I don't think I'm going to be around washington anytime soon (at least not until the summer weather kicks in for sure...)

 

Thanks a bunch again. Hopefully this is my last question for this thread...

 

Somewhat unrelated...but what is the best Mac or PC software to capture harddrives images so restoration of dual boot config on 1340 is possible?

 

I only ask, b/c I'm sure everyone on this thread usually blows out their HD regularly....

 

Thanks!

Link to comment
Share on other sites
bcc9
bcc9
Posted
  • Author
Posted
Thanks a bunch again. Hopefully this is my last question for this thread...

 

Somewhat unrelated...but what is the best Mac or PC software to capture harddrives images so restoration of dual boot config on 1340 is possible?

 

I only ask, b/c I'm sure everyone on this thread usually blows out their HD regularly....

For restoring bootloader configurations, I use dd commands, like those listed in the chameleon documentation.

For moving OSX partitions around, I use the tar command from the shell, which isn't pretty as the OSX version of tar requires special handing of private/tmp.

For moving&resizing NTFS partitions I use gparted live.

 

Great work, bcc9!! Your DSDT finally got audio working on my XPS 1330!! Thanks a lot :D

Thanks. If the same HDAIDT works with the 1330 someone should alert the 1330 thread and get their instructions updated.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...