OSX 10.7, 10.8 and 10.9 on the Dell XPS 1340 laptop

[bcc9]

Sorry, bcc9.

 

I tried DSDT.aml from v3, and then attempted to troubleshoot via orig.aml and ed1-6, 8 and 9. (ed7.aml was not in the zip files, though it was there as a dsl.)

 

None of them worked to get past [PCI Configuration Begin]. Only DSDT=no got it to the usual booting state of bridges 8 devices 22, followed by bridge 4 device 1 cardbus 0 and so forth.

 

Maybe I should roll back to A14 like Dual_Shock?

If you really can't even boot with DSDT=orig.aml, then something is pretty broken. You're using chameleon r1649?

Are you trying to boot the 10.7 install partition (the first boot), or the partition you made during the install (the second boot)?

 

Dual shock's post didn't indicate whether or not he was able to boot with a vanilla .aml under a14 or a15 so his limited data seems to only show that downgrading to a14 didn't fix the use of a modified .aml for those who are having trouble.

[bfbruin]

I've been using 1493, so I'll upgrade to the 1649 now. UPDATE: Cannot sem to find Chameleon 1649, as builds.voodooprojects appears to be down.

 

I'm booting my Lion partition, not my Install Partition.

[bcc9]

I've been using 1493, so I'll upgrade to the 1649 now. UPDATE: Cannot sem to find Chameleon 1649, as builds.voodooprojects appears to be down.

I wouldn't sweat it; either version should be fine (both work fine for me).

 

I'm assuming you can't boot into single user mode or safe mode with orig.aml? Does the system really seem to have hung or just fails to display anything after "pci configuration begin" (with disk activity continuing)?

[bcc9]

If those who are having problems with hanging at "pci configuration begin" can't get anywhere with dsdt troubleshooting, then I recommend testing the old workaround of using the 10.6.8 IOPCIFamily. If that works, then it's clear what has been going wrong and what needs a better fix.

[metamorphoise]

I had a go with your debug DSDTs and like bfbruin, even DSDT=orig.aml gives me a hang on [PCI config begin]

i tried to boot to safe mode with -x DSDT=orig.aml npci=0x2000 and it hung at a message slightly before [PCI config begin], something like "PFC64 0x5100000000" or similar.

I would like to try the 10.6.8 IOPCIFamily.kext workaround but I have no 10.6 installation to get the file and have not been able to find a downloadable 10.6.8 kext

 

 

Here is some information that may or may not be pertinent:

-I'm using A14 BIOS

-I'm using Chameleon SVN 1650 as the 1649 link seems to be down

-I needed to remove the SMmemtype from smbios.plist as my system seemed to have trouble booting with that, I think I changed the ram in my 1340 at some stage, still 4Gb.

-I am installing off a clean lion install done with Tonymac's [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] tool, could this be causing problems?

-Maybe 50% of the time, it seems to boot fine but no graphics are displayed (monitor turns off) and i have to boot with GraphicsEnalber=No

-The kexts in /E/E are 9400m_gstate_inject, AppleACPIPS2Nub, fakesmc, VoodooBattery & VoodooPS2Controller

 

PS, the links to the OpenHaltRestart and your HCI bluetooth pkg seem to be broken, also some links in the older 10.6 guide. they send me to the main insanelymac page. seems like something changed with this board's handling of links?

 

Thanks,

Tom

[ticktick]

thanks for detailed tutorial. After upgrade to 10.7.2 I am stuck at still waiting for root device and it never goes further.

[bcc9]

I had a go with your debug DSDTs and like bfbruin, even DSDT=orig.aml gives me a hang on [PCI config begin]

i tried to boot to safe mode with -x DSDT=orig.aml npci=0x2000 and it hung at a message slightly before [PCI config begin], something like "PFC64 0x5100000000" or similar.

I would like to try the 10.6.8 IOPCIFamily.kext workaround but I have no 10.6 installation to get the file and have not been able to find a downloadable 10.6.8 kext

The 10.6 iopcifamily kexts are floating all over the place. I've never tried them, so I don't know which one works with various flavors of 10.7. Perhaps oleg's: http://cl.ly/3R460x3f092m0F0F393q ? Recommend you check back in the 10.6 thread for details.

-I needed to remove the SMmemtype from smbios.plist as my system seemed to have trouble booting with that, I think I changed the ram in my 1340 at some stage, still 4Gb.

Makes no sense, the SMmemtype should just be cosmetic (allows the memory to show up as ddr3 in system profiler). Any memory you added would have been ddr3 so the SMmemtype would still be right...

-I am installing off a clean lion install done with Tonymac's [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] tool, could this be causing problems?

You're having problems, but you're using a completely different install method, not following directions? I'm not sure how I can help you with that. Presumably tonymac's installers would give you different .plists in /Extra.

There's plenty more debugging that you could do such as booting with Wait=yes, and comparing the no dsdt case vs the DSDT=orig.aml case.

-Maybe 50% of the time, it seems to boot fine but no graphics are displayed (monitor turns off) and i have to boot with GraphicsEnalber=No

-The kexts in /E/E are 9400m_gstate_inject, AppleACPIPS2Nub, fakesmc, VoodooBattery & VoodooPS2Controller

 

PS, the links to the OpenHaltRestart and your HCI bluetooth pkg seem to be broken, also some links in the older 10.6 guide. they send me to the main insanelymac page. seems like something changed with this board's handling of links?

That kext list seems about right, for starters, of course they can't just be in /E/E if you're using UseKernelCache=Yes

Those other links used to be fine, looks like the board corrupted them and also made them no longer work.

Update: Fixed. Definintely a forum bug. These same links are busted in the 10.6 1340 thread too.

[LatinMcG]

try changing

Device (PCI0)
	{
		Name (_ADR, 0x00)
		Name (_HID, EisaId ("PNP0A08"))
		Name (_CID, EisaId ("PNP0A03"))
		Name (_UID, 0x01)

to

Device (PCI0)
	{
		Name (_HID, EisaId ("PNP0A08"))
		Name (_CID, EisaId ("PNP0A03"))
		Name (_ADR, 0x00)
		Name (_UID, 0x00)

 

root uid 1 for AMW0 as its on same _SB both UID 0 might conflict.. so change AMW0 _UID to 0x01

[bcc9]

try changing

Why, to obviate the need for PCIRootUID being set in org.chameleon.Boot.plist? (This can also be achieved by simply moving the _UID assignment to before the _HID&_CID assignments.) This avoids the problem with chameleon's buggy .aml parsing so that it is able to find the _UID value without a PCIRootUID assignment.

 

Or is the intent here to somehow help the hang at "PCI Configuration Begin" case?

root uid 1 for AMW0 as its on same _SB both UID 0 might conflict.. so change AMW0 _UID to 0x01

Seems this shouldn't conflict with AMW0 either way as the two don't share _HID or _CID values. "The

_UID must be unique across all devices with either a common _HID or _CID." in the spec...

[LatinMcG]

when 10.6.8 cme out my inspiron would not boot. till i read somewhere the tequila fix worked due to UID being 0 not 1.

yes it can be done in chameleon..but the real mac way is 0x00.

my inspiron 1520 didnt have _UID at all . i try to add under _ADR and no boot.

so i replaced _ADR with _UID and it works. no more pci config hang.

 

the amw0 i wasnt sure if the UID had to be non conflicting or not.. i guess both can say Zero

[bcc9]

I'm not seeing anything in the two "tequila fix" threads I can find about the UID change having any effect on hangs at "pci configuration begin". At least I don't see how changing the UID number for systems that already have both ADR & UID defined would have that effect. But folks who are having problems are free to experiment of course.

 

Yes, patching the dsdt so as to not need to configure PCIRootUID seems slightly preferable. Seems some people are having trouble booting consistently with PCIRootUID set (metamorphoise's 50% failure with graphics sounds like this situation).

[metamorphoise]

I seem to have tracked down what was causing my [PCI config hang], my extracted DSDT was different from the original DSDT this guide is based on.

 

I have attached the relevant files for others with the same problem to try, but I imagine that your DSDT may be different again so here is the process I followed:

I extracted my DSDT using DSDTESE and ran it through filemerge (nice diff program, installed when you install Xcode) with the orig.dsl from dsdt.a14.lion.v3.zip. filemerge showed 9 differences, 4 being insignificant differences in comments at the top and 5 being significant differences like:

 

metamorphoise1340orig.dsl				OperationRegion (ASLD, SystemMemory, 0x8FECF5CA, 0x00000100)
orig.dsl				OperationRegion (ASLD, SystemMemory, 0xAFECF5CA, 0x00000100)

and

metamorphoise1340orig.dsl				OperationRegion (ROM1, SystemMemory, 0x8FECF6CA, 0x00010000)
orig.dsl				OperationRegion (ROM1, SystemMemory, 0xAFECF6CA, 0x00010000)

 

I then renamed my extracted dsl to orig.dsl and copied it to the dsdt.a14.lion.zip directory, overwriting the existing file. Then ran the cmd file to patch my dsl, and we have a new fixed.dsl

 

Drop that fixed.dsl into iaslMe (http://www.insanelym...howtopic=189272), move the resulting aml to /Extra/DSDT.aml, and boot! (i also did chmod 775&&chown root:wheel on it but don't think that is necessary)

 

 

 

 

Now my system seems to be almost fully functional, but there are still some issues with the graphics that I will look into now but the symptoms are below and any help would be greatly appreciated:

Often the system will boot seemingly normally but nothing is displayed when it gets to login (screen backlight is on but screen is black, disk and keyboard lights functioning) and I have to reboot one or more times till it decides to work, or boot with GraphicsEnabler=No

metamorphoiseDSDT.zip

[bcc9]

I extracted my DSDT using DSDTESE and ran it through filemerge (nice diff program, installed when you install Xcode) with the orig.dsl from dsdt.a14.lion.v3.zip. filemerge showed 9 differences, 4 being insignificant differences in comments at the top and 5 being significant differences like:

Interesting, that's the first time anyone has reported any dsdt differences (and we've been sharing dsdts for this laptop for almost 3 years now).

This is with a14 bios, right? And you have a 9400m?

[metamorphoise]

Interesting, that's the first time anyone has reported any dsdt differences (and we've been sharing dsdts for this laptop for almost 3 years now).

This is with a14 bios, right? And you have a 9400m?

 

Yes it is A14 BIOS

 

You may be onto something with the graphics card though, I bought this laptop 2nd hand and thought it was a 9400m.

When the GraphicsEnabler works, About This Mac identifies it as a "GeForce 9400M G 256 MB"

But if i put my service tag (BQ6SWK1) into Dell website, it says my original configuration was/is "NVIDIA® GeForce® 210M - 512MB"

 

I have to scoot to work now so can't really look into it until tonight, but seems like this is some form of Hybrid SLI model. From what i can see here, '9500m hybrid SLI' consists of a 9400m & 9200m GS, but if mine is a 9400m & 210m maybe the original purchaser upgraded the graphics.

 

On another note, I tried applying LatinMcG's patch to my DSDT and removing the PCIRootUID string&key from org.chameleon.Boot.plist, no change. still boots only sometimes.

[LatinMcG]

at third step in tequila fix.(this is from 2009 no lion or pci config issues then but relevant)

 

the differences seem to be in ram amount changes: SystemMemory, 0x8FECF5CA

 

btw the 9400 is similar chip to 210. (rebranded with a lil tweaking in the rom and hdmi i think i read somewhere)

[bcc9]

You may be onto something with the graphics card though, I bought this laptop 2nd hand and thought it was a 9400m.

When the GraphicsEnabler works, About This Mac identifies it as a "GeForce 9400M G 256 MB"

But if i put my service tag (BQ6SWK1) into Dell website, it says my original configuration was/is "NVIDIA® GeForce® 210M - 512MB"

 

I have to scoot to work now so can't really look into it until tonight, but seems like this is some form of Hybrid SLI model. From what i can see here, '9500m hybrid SLI' consists of a 9400m & 9200m GS, but if mine is a 9400m & 210m maybe the original purchaser upgraded the graphics.

Well a 1340 with 210M would be a 9400M plus a 210M., just as a 1340 with 9500M is a 9400M plus a 9200M. The 1340s with 9500M shared the same DSDTs as the plain 9400M-only models. I think you're the first to go to the trouble of posting a 210M DSDT.

 

Per your service tag showing the 210M part, you already have the newer/upgraded model. A 9500M or 9400M only model would be a *downgrade*. You can't switch the GPU in the field without replacing the whole motherboard (which is a PITA, I did it once), as the 210M/9200M chips are soldered in. Plus the whole heat sync assembly is different than with the 9400M only model.

 

The 5 differing memory regions in the DSDT are all within the 2 memory ranges reported by linux like so:

BIOS-e820: 00000000afec0000 - 00000000afed3000 (ACPI data)
BIOS-e820: 00000000afed3000 - 00000000afee5000 (ACPI NVS)

(This is on my machine)

On another note, I tried applying LatinMcG's patch to my DSDT and removing the PCIRootUID string&key from org.chameleon.Boot.plist, no change. still boots only sometimes.

So you gotta figure out what is different between the two cases. Maybe failure happens after you warm reboot from windows? Or you're booting via a different disk (chameleon sometimes leaks settings from the partition it loads from instead of the partition you select for boot).

[LatinMcG]

i put linux mint 11 in a xps m1530 and windows 7 and strange thing would happen on reboot. from linux to windows 7. the Nvdia became standard VGA adapter. untill i shutdown and turn on again (like it wasnt reseting video ram or framebuffer.) im sure its not related.. but something to think about when restarting rather cold booting (and bios version/video version)

[bcc9]

i put linux mint 11 in a xps m1530 and windows 7 and strange thing would happen on reboot. from linux to windows 7. the Nvdia became standard VGA adapter. untill i shutdown and turn on again (like it wasnt reseting video ram or framebuffer.) im sure its not related.. but something to think about when restarting rather cold booting (and bios version/video version)

Basically the same thing happens with the 1340, where warm booting into windows sometimes results in the wrong resolution. And now I see the windows DSDT methods are mucking with ACPI non-volatile memory. So this is why I threw out warm booting as a possibility for metamorphoise's intermittent problems.

[metamorphoise]

Hi, Status Report:

I installed NVenabler.kext earlier today, and so far so good. I didn't change anything else (first few boots I booted with GraphicsEnabler=No but then I forgot and it still seems to work fine). Have booted around 5 times with no problems.

AboutThisMac reports "Unknown nVidia card 256 MB". QI/CE seems to work and Geekbench trial mode gives a score of around 3500.

 

VGA out seems to be working partially; no detection of displays plugged in when the computer is running but correctly detects displays plugged in at boot time. I will spend some time tinkering with this.

 

Oh and to clarify, I just have the one disk with the one GUID partition with Lion. no Windows/Linux/multiboot setup.

[bcc9]

Hi, Status Report:

I installed NVenabler.kext earlier today, and so far so good. I didn't change anything else (first few boots I booted with GraphicsEnabler=No but then I forgot and it still seems to work fine). Have booted around 5 times with no problems.

To narrow down your problem, I think you should try my 10.6 DSDT graphics injection strings and see if that also avoids the problems you're having with GraphicsEnabler.

[Dual_Shock]

Hey !

I'm sorry, I didnt have much time these days, but I have try to downgrade AppleACPIPlatform with an older 10.5 I believe, and I crash my system.

After restore with good AppleACPI and fix it with bcc patch 1.8, I have try metamorphoise DSDT and it work perfectly ! I have sound and graphic correctly !

For information, I didn't have GeForce 210 but 9200 + 9400 and always with A14 Bios.

Many thanks to you !

[bcc9]

So I've written a couple scripts that will look at a running OSX system's memory and figure out whether my patched DSDT.aml is appropriate, or one with the alternate address space (as posted by metamorphoise). This should eliminate any need for guessing. dsdt-check-0.1.zip

 

To use, run dsdt-check.pl from a terminal window.

 

The included showbootermemorymap is from Amit Singh's osx book, enhanced by me to work with 64-bit address space.

% ./dsdt-check.pl
Address space matches original DSDT.aml
Copy DSDT.aml from post #1 to /Extra/DSDT.aml
%

 

Makes sense?

[bcc9]

I've updated the dsdt & plist attachments in post #1 to a new version which includes the DSDT edit to renumber the PCI0 UID to 0.

This avoids the need to set the PCIRootUID in org.chameleon.Boot.plist. I've also integrated the dsdt-check.pl instructions&scripts so everything you need to figure out the right DSDT to use is in post #1.

[Dual_Shock]

Thank you, your classical DSDT doesn't work, but your DSDT-alt work like metamorphoise DSDT's.

But I have a lot of artefacts in game (Age of Empire III), under osx 10.5.8 for example, it work perfectly.

I think GFX is not working at 100%

[bcc9]

Thank you, your classical DSDT doesn't work, but your DSDT-alt work like metamorphoise DSDT's.

But I have a lot of artefacts in game (Age of Empire III), under osx 10.5.8 for example, it work perfectly.

I think GFX is not working at 100%

The GPU throttling you get by using 9400m_gstate_inject may not be appropriate for gamers. Try running without it.

Genuine macbook users have reported these kinds of issues with nvidia graphics as well.