1350 replies to this topic

[macgirl]

DarwinX, on 21 April 2013 - 10:13 PM, said:

Following a kext installation, repair permissions then simply delete the obsolete Extensions.mkext along with the kernelcache in the /System/Library/Caches/com.apple.kext.caches/Startup directory then reboot.
The kernelcache will be automatically regenerated by the system upon reboot.

Just for reference, here are all the latest files (kexts, plists and DSDT) needed to viably boot and operate the XPS M1530 under the OS X 10.8.x

XPS M1530 - 10.8.x.zip

Thanks a lot, where do you put the extensions? If I compare to the first post only FakeSMC goes to /Extra/Extensions

[theconnactic]

Hi!

In Mountain Lion, unlike anterior iterations, these kexts should be installed at /S/L/E.

Good to know you decided to give ML a go on your system. Are you using the patched 10.8.x kernel from AnV?

All the best!

[macgirl]

theconnactic, on 22 April 2013 - 03:42 AM, said:

Good to know you decided to give ML a go on your system. Are you using the patched 10.8.x kernel from AnV?
All the best!

Ohhhh, thanks again.

No, the kernel I am using is the Vanilla one from 10.8.3

So you dont need to replace IOUSBFamily.Kext and IOBluetothFamily.kext ?

[DarwinX]

macgirl, on 22 April 2013 - 02:55 AM, said:

Thanks a lot, where do you put the extensions? If I compare to the first post only FakeSMC goes to /Extra/Extensions

As theconnactic has already mentioned, ever since the OS X 10.7, the /Extra/Extensions directory along with the Extensions.mkext itself is now completely obsolete and unnecessary.
ALL kexts are now to be installed into the /System/Library/Extensions directory as the kernelcache could only by generated from there and nowhere else.

macgirl, on 22 April 2013 - 03:54 AM, said:

Ohhhh, thanks again.

No, the kernel I am using is the Vanilla one from 10.8.3

So you dont need to replace IOUSBFamily.Kext and IOBluetothFamily.kext ?

To the best of my knowledge, in our systems the regression of the USB and the Bluetooth kexts is unnecessary as they are all "vanilla" under the 10.7.x - 10.8.x

theconnactic, on 22 April 2013 - 03:42 AM, said:

Hi!

In Mountain Lion, unlike anterior iterations, these kexts should be installed at /S/L/E.

Good to know you decided to give ML a go on your system. Are you using the patched 10.8.x kernel from AnV?

All the best!

The Dell XPS M1530 and M1330 requires no kernel patching, the native kernel retains full compatibility with our rigs.

[macgirl]

DarwinX, on 22 April 2013 - 01:35 PM, said:

As theconnactic has already mentioned, ever since the OS X 10.7, the /Extra/Extensions directory along with the Extensions.mkext itself is now completely obsolete and unnecessary.
ALL kexts are now to be installed into the /System/Library/Extensions directory as the kernelcache could only by generated from there and nowhere else.



To the best of my knowledge, in our systems the regression of the USB and the Bluetooth kexts is unnecessary as they are all "vanilla" under the 10.7.x - 10.8.x

Excellent, I take back the original kexts and seems fine.

[luaduck]

I get the feeling I've made a moumental cockup somewhere, but here goes: I updated from 10.8.2 to 10.8.3 using Combo, making sure to move AppleGraphicsPowerManagement.kext out as suggested by immo here before rebooting. It did come with an interesting side effect, though, with a lovely [ PCI configuration begin ] hang and a stuck pinwheel. I've tried all the tips that google can provide, like graphicsenabler=no, npci=0x2000, and PCIRootUID=1 with no avail. Any ideas? I can't even boot into single-user mode as it's hanging way before then. Did I just forget to recopy some kexts or something?

[DarwinX]

luaduck, on 24 April 2013 - 08:58 PM, said:

I get the feeling I've made a moumental cockup somewhere, but here goes: I updated from 10.8.2 to 10.8.3 using Combo, making sure to move AppleGraphicsPowerManagement.kext out as suggested by immo here before rebooting. It did come with an interesting side effect, though, with a lovely [ PCI configuration begin ] hang and a stuck pinwheel. I've tried all the tips that google can provide, like graphicsenabler=no, npci=0x2000, and PCIRootUID=1 with no avail. Any ideas? I can't even boot into single-user mode as it's hanging way before then. Did I just forget to recopy some kexts or something?

Simply roll back your existing AppleACPIPlatform.kext to that of the Snow Leopard (v1.3.6).

 AppleACPIPlatformV1.3.6.kext.zip   425.64K   3 downloads

[luaduck]

DarwinX, on 24 April 2013 - 09:19 PM, said:

Simply roll back your existing AppleACPIPlatform.kext to that of the Snow Leopard (v1.3.6).

AppleACPIPlatformV1.3.6.kext.zip

Thanks babe, I think you've got me out of a tight spot (although it's now hanging at a grey apple even booting in verbose what) nevermind it was a journal issue

[DarwinX]

luaduck, on 24 April 2013 - 10:31 PM, said:

Thanks babe, I think you've got me out of a tight spot (although it's now hanging at a grey apple even booting in verbose what) nevermind it was a journal issue

No problem, we are here to help each other.

[Fa90]

Hi, so i posted in the old XPS Compilation thread, but DarwinX mentioned this thread to me

My problem is that my XPS M1530 with the T8100 CPU only runs at 600 mhz in Mountain Lion, instead of 2,1ghz

I tried it with severals kexts, but nothing changed

Here is a Picture of my Specs:
(Attachement)


Cheers,
Fred

Attached Files

•  Bildschirmfoto 2013-05-18 um 16.12.38.png   813.5K   12 downloads

[DarwinX]

Fa90, on 18 May 2013 - 02:31 PM, said:

Hi, so i posted in the old XPS Compilation thread, but DarwinX mentioned this thread to me

My problem is that my XPS M1530 with the T8100 CPU only runs at 600 mhz in Mountain Lion, instead of 2,1ghz

I tried it with severals kexts, but nothing changed

As our systems are nearly identical, If you use the files which I provided, this should not happen.