"Unable to find driver for this platform" ACPIP

[DavidMIRV]

So I got a dreaded KP on ACPIP "Unable to find driver for this platform" as used to happen with some of the older versions. Booting using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] (unable to get xpc to boot). Is the only fix for this to remove the ACPI kexts from the S/L/E ? Or does anyone know anything else I might experiment with?

 

Thanks

[Crna Brada]

Have you found a solution for this problem?

I am getting the same KP & message when I try to boot DP4 from RAID. See http://www.insanelymac.com/forum/index.php?showtopic=258800

It appears from what you are mentioning that removing one kext would (forcefully) solve the problem? Could you please give me more info about that? That seems to be the closest lead to solving my RAID boot problem.

 

Regards

Crna Brada

[marliwahoo]

Same problem. I did get RAID to boot when I mistakenly changed UUID on a different working lion HD.

 

In other words I can not boot directly from RAID.

I can boot RAID from a different HD - w/ working lion (dp4) install - with the RAID UUID in boot.plist.

[Crna Brada]

Interesting combination. I tried something similar: booting from Chameleon installed on Lion DP3 on a USB HD. It didn't work. I'll try your "trick" and let you know.

Thanks for answering.

[marliwahoo]

OK here is the problem -

 

Lion DP4 won't boot from RIAD kernelcache - must use extensions.mkext. Must remove kernelcache from /System/Liabrary/Caches and from RAID boot partition. Then make extensions.mkext and add to both places where you removed kernelcache.

 

Also might be a good idea to remove platform support.plst from RAID boot partition /System/Liabrary/CoreSevices.

[Crna Brada]

OK here is the problem -

 

Lion DP4 won't boot from RIAD kernelcache - must use extensions.mkext. Must remove kernelcache from /System/Liabrary/Caches and from RAID boot partition. Then make extensions.mkext and add to both places where you removed kernelcache.

 

Also might be a good idea to remove platform support.plst from RAID boot partition /System/Liabrary/CoreSevices.

 

I am 24 hours behind you. I just successfully repeated your previous trick with booting from a third Lion disk and it worked.

Now I will try this one and let you know. I guess I should manually create Extensions.mkext using "kextcache -v 1 -t -m ..."?

 

Thanks for the help!

 

UPDATE: This second trick would not work!

Doesn't matter if I create Extensions.mkext and keep copying it tp all three places, Lion keeps recreating kernelcashe.

i also deleted platform.support.plist. Still, the outcome is identical: KP & missing platform!

 

It seems to me that somewhere in the configuration (DSDT maybe, or in a config file like symbios we should "tell" the OS it is working on a right platform. It clearly gets that proper information when booted from isolated Lion drive which points to boot-uuid to RAID.

 

Where that magic should be done?!

Edited June 14, 2011 by Crna Brada

[marliwahoo]

I am 24 hours behind you. I just successfully repeated your previous trick with booting from a third Lion disk and it worked.

Now I will try this one and let you know. I guess I should manually create Extensions.mkext using "kextcache -v 1 -t -m ..."?

 

Thanks for the help!

 

UPDATE: This second trick would not work!

Doesn't matter if I create Extensions.mkext and keep copying it tp all three places, Lion keeps recreating kernelcashe.

i also deleted platform.support.plist. Still, the outcome is identical: KP & missing platform!

 

It seems to me that somewhere in the configuration (DSDT maybe, or in a config file like symbios we should "tell" the OS it is working on a right platform. It clearly gets that proper information when booted from isolated Lion drive which points to boot-uuid to RAID.

 

Where that magic should be done?!

 

 

I had the same problem and just kept deleting the kernelcache from - /raid boot part/com.apple.boot.R/System/Library ect ...../. Then I realized you could simply put all extensions from extra folder into /sys/lib/extensions then create a new extensions.mkext and put it in the in Extra folder of RAID boot partition. You no longer need to be concerned about kernelcache - you do need to manually create a new extensions.mkext every time your extensions folder changes because it will not auto update.

[Crna Brada]

I had the same problem and just kept deleting the kernelcache from - /raid boot part/com.apple.boot.R/System/Library ect ...../. Then I realized you could simply put all extensions from extra folder into /sys/lib/extensions then create a new extensions.mkext and put it in the in Extra folder of RAID boot partition. You no longer need to be concerned about kernelcache - you do need to manually create a new extensions.mkext every time your extensions folder changes because it will not auto update.

 

As the slogan of a famous Canadian cough medicine would say: "It Tastes Awful. And It Works."

 

I guess it took you quite awhile to come up with this quite complex "formula" to solve the issue.

I still hope there will be a clean(er) solution that would use Lion native kernelcache.

Meanwhile, with AppleRTC fix for sleep, I have fully functional lighting fast Lion on RAID!

Thanks marliwahoo!!!

[marliwahoo]

As the slogan of a famous Canadian cough medicine would say: "It Tastes Awful. And It Works."

 

I guess it took you quite awhile to come up with this quite complex "formula" to solve the issue.

I still hope there will be a clean(er) solution that would use Lion native kernelcache.

Meanwhile, with AppleRTC fix for sleep, I have fully functional lighting fast Lion on RAID!

Thanks marliwahoo!!!

 

 

Actually, it didn't take that long to figure out. The hardest part was figuring out that there is nothing wrong with the kernelcache - it's that the kernelcache is simply not loading.

 

I don't know if that is a problem with Lion or Chameleon. In any case, it's not a difficult work around, just sloppy.

[Crna Brada]

Actually, it didn't take that long to figure out. The hardest part was figuring out that there is nothing wrong with the kernelcache - it's that the kernelcache is simply not loading.

 

I don't know if that is a problem with Lion or Chameleon. In any case, it's not a difficult work around, just sloppy.

 

Last night, I was trying to figure out the same thing - ".. if that is a problem with Lion or Chameleon..".

It is hard to say but based on how I manage to get Lion on RAID working, but only once immediately after the installation, I tend to believe it is the Chameleon who knows how to deal with Extensions.mkext better than with kernelcache.

Here is the scenario how you can get RAID working without Extensions.mkext.

 

1. Use Chameleon on another SL or Lion drive to boot Lion Install USB stick.

2. Install Lion from the USB stick to a RAID volume.

3. Restart after the installation is completed.

4. Use the same Chameleon to go to to the Install USB stick again the same way you did in Step 1 above - as if you are about to install Lion again.

5. Instead of going into Install app on the USB stick, system starts Lion OS on the RAID. No complaints about unsupported platform or anything else while Extensions.mkext has never been created.

6. You can stay there, install Chameleon, add kexts, go on network, install applications and updates as it is usual for any regular Mac OS installation.

7. Once you reset the system and try to get into the RAID install directly - it will fail with unsupported platform complaint KP. If you try again to go to Lion Install USB stick, it will take you to Install app but nevermore would you get to Lion OS on RAID.

 

I tried this procedure twice and it would work exactly the same way.

While it is not conclusive about who is to blame, there are some things that seem to be clear. At least under some specific circumstances:

1. Lion can work with kernelcache and without Extensions.mkext on RAID.

2. Lion does have right drivers to work from RAID - platform is supported.

 

I'll experiment more to try to pin-down where the issue might be and keep you posted.

 

Thanks for the ideas. It is great to have a 'partner in pain' to brainstorm.

 

Cheers

[digital_dreamer]

Great research, guys. But, I'm still trying to parse what's going on.

I'll be back after some tests.

 

MAJ

[digital_dreamer]

Doesn't seem that Chameleon is handing off to the system on RAID setups. Once the kexts and other files are loaded in /Extra, it's supposed to then hand off to the system and load kexts in S/L/E. Not happening. Which is why you have to have the full cache in /Extra.

 

In the HackInstaller script, I just use the Combo option, which builds both /Extra and /System cache into /Extra. With this, I have all my modded kexts in /Extra.

 

Thanks for the work, guys. Off to report this to the Chameleon guys.

 

MAJ

[Crna Brada]

Doesn't seem that Chameleon is handing off to the system on RAID setups. Once the kexts and other files are loaded in /Extra, it's supposed to then hand off to the system and load kexts in S/L/E. Not happening. Which is why you have to have the full cache in /Extra.

 

In the HackInstaller script, I just use the Combo option, which builds both /Extra and /System cache into /Extra. With this, I have all my modded kexts in /Extra.

 

Thanks for the work, guys. Off to report this to the Chameleon guys.

 

MAJ

 

 

Out of the curiosity. How would you explain "the first time login into RAID" success I described above?

Truly enjoy your lessons Prof. MAJ.

 

Sincerely,

Crna Brada

[digital_dreamer]

Out of the curiosity. How would you explain "the first time login into RAID" success I described above?

Truly enjoy your lessons Prof. MAJ.

 

Sincerely,

Crna Brada

 

Have no real idea, except to believe it's related to the fact that a successful boot hinges on initially booting on a standard Lion installation (non-RAID) from the BIOS, then selecting the RAID from the bootloader screen. So, something is amiss with the RAID hand off.

 

As demonstrated, you can boot to USB drive, but select RAID and boot.

Here, kernel, Lion kexts, and DSDT, is loaded (from USB drive) and successfully handed off to system, because booting was, initially, from a non-RAID drive.

 

You can boot to a different Lion install (non-RAID) with the boot-UUID pointing to the RAID, then successfully boot into RAID. Again, kernel, Lion kexts, and DSDT is loaded (from non-RAID drive) and successfuly handed off to load S/L/E.

 

I'd assume that booting would be accomplished for EFI installs if the boot-UUID is also pointing to the RAID system drive.

 

Apparently, something different in the Lion RAID setup causes Chameleon to be unable to hand off to load S/L/E.

But, that's all I can speculate on, as I don't know how bootloaders turn control over to the System. Additionally, I'm unclear on how just having the cache from S/L/E in /Extra completes this job. Unless, the hand-off is not so much the issue, but just loading kexts/cache from a RAID install.

 

best regards,

MAJ

[S.V.]

Is there a tutorial for installing Lion/Raid?