[Help] Boot-132

[buoo]

Hi guys!

 

I'm trying to create a universal cdboot for P5Q's users to avoid modded BIOS.

I have already created a cdboot using this guide http://forum.voodooprojects.org/index.php/...84.msg2131.html it's very easy!

In the Extra/Extensions folder I have added these kext

 

AHCIPortInjector

ATAPortInjector

fakesmc

IOAHCIBlockStorageInjector

NullCPUPowerManagement

OpenHaltRestart

UUID

 

this c.a.b.p

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//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></string>
<key>GraphicsEnabler</key>
<string>Yes</string>
<key>EthernetBuiltIn</key>
<string>Yes</string>
</dict>
</plist>

 

and extensions.mkext

 

This cdboot works good with some P5Q (ex P5Q Deluxe) but for some P5Q (ex P5Q Pro) I've found this problem

 

ACPI_SMC_platformplugin: : start - wait for service ( resourcematching ( appleintelcpu power management ) timed out

 

What can I do?

 

Thanks

BootCD.iso.zip

[Gringo Vermelho]

Add a LegacyAppleLPC.kext that injects the device ID for the LPC device on the ICH10R.

 

Search the forums to find out how to make a legacy/plist-only kext, or google 'LegacyAppleLPC.kext' and see how it's done. Yours should be based on AppleLPC.kext from 10.6.4.

 

 

If your boot CD is based on Chameleon 2.0 RC5, the following kernel extensions are unnecessary:

NullCPUPowerManagement

OpenHaltRestart

UUID

RC5 patches the FACP table (restart fix) by default, and provides a Hardware UUID which is taken from motherboard DMI table:

"Platform UUID is taken from the BIOS (UUID from SMBIOS Table 1). You can remove PlatformUUID.kext, SMUUID from smbios.plist and also System-ID from com.apple.Boot.plist." (comes from here: http://www.kexts.com/software-mac-os-x/717...cefi10-5-a.html - Chameleon 2.0 RC5 has the same feature set + more).

 

There is no reason to use NullCPUPM, your boot CD is for a P5Q-series board with a Core microarchitecture CPU. If you're doing this because you want Pentium 4/D users to be able to use your boot CD, you need to provide a patched kernel as well, and the ability to select it during boot. Otherwise it's pointless to block AppleIntelCPUPowermanagement.kext. Plus in doing that you're killing native power management, which is one of the main features of Chameleon 2.0 RC5.

 

cdboot from Chameleon 2.0 RC5 rxxx is attached to my Chameleon boot CD guide here: http://forum.voodooprojects.org/index.php/...31.html#msg2131

 

For the Marvell 61xx PATA controller found on some P5Q boards you can add SuperVIAATA.kext.zip

For the Marvell 88E8056 LAN on the P5Q-E and the P5Q Deluxe (other P5Qs use it as well?) you can add:LegacyAppleYukon2.kext.zip

 

I would set GraphicsEnabler=n and use FrameBufferDisabler.kext instead - GraphicsEnabler doesn't work with all video cards and having it enabled on a system with a video card that isn't supported by OSX video drivers can cause a lockup on boot.

Framebufferdisabler.kext is nice on a boot CD because it lets the system install and boot without any risk of video driver conflicts. Of course you lose hardware accelerated graphics, but only a few lucky people would have that without editing the drivers as well anyway. And QE/CI s not required during installation.

[buoo]

Thanks Gringo

 

I have found LegacyAppleLPC.kext in a russian forum and this is its info.plist

 

 

 

instead this is the info.plist modified ...Is it ok?

 

 

 

 

about extra folder...

 

I have to use these kext:

 

AHCIPortInjector

ATAPortInjector

fakesmc

IOAHCIBlockStorageInjector

FrameBufferDisabler.kext

LegacyAppleLPC.kext

 

but if I add SuperVIAATA.kext what does it change ? And if I add LegacyAppleYukon2.kext can I install Snow on the IDE hard disk ??

Can I use these two last kext togheter ?

 

best regards

[Gringo Vermelho]

but if I add SuperVIAATA.kext what does it change ? And if I add LegacyAppleYukon2.kext can I install Snow on the IDE hard disk ?? Can I use these two last kext togheter ?

I already told you in plain English which devices those kernel extensions are for.

I've edited my post to make it a little clearer, after I noticed that you haven't downloaded LegacyAppleYukon2.kext yet.

 

I've never tried installing Snow on (or from) a PATA drive but my old PATA CD-RW drive was fully supported in 64-bit Snow using SuperVIAATA.kext.

Yes of course you can use them together, one is for a Marvell Yukon ethernet controller, the other is for a Marvell PATA controller. You're supposed to know that, you're the Universal P5Q series Boot CD guy remember?

 

I've never made a LegacyAppleLPC.kext myself, I went straight to fix it in DSDT, so I can't offer much more help with that.

Here's a guide: http://www.projectosx.com/forum/index.php?showtopic=798

 

The Legacy kext from cvad has no device IDs in it, I'm not sure I understand how it's supposed to work, it looks like it loads by device class (?) and therefore will load no matter what? You should definitely try cvad's LegacyAppleLPC on the P5Q Pro where you had the problem and see if the message goes away and if AppleLPC.kext gets loaded (check System Profiler/Extensions).

 

Otherwise just keep experimenting with your own, it looks like you're on the right track. If you want to make the legacy kext smaller you could delete all the unneeded device IDs and just leave the ICH10 and ICH10R LPC Device IDs in (all P5Qs have ICH10/R right? You're the expert!).

[buoo]

Thanks Gringo

 

A friend of mine is trying the cdboot with LegacyAppleLPC.kext

[buoo]

Hei Gringo

 

The boot132 works good!!

 

The test was done on P5Q Pro, the error ACPI_SMC_platformplugin: : start - wait for service ( resourcematching ( appleintelcpu power management ) timed out has gone away

but another problem has arrived USBF: 6.193 Apple USBUHCI [0xffffff80492cc000] start unable to initialize UIM

I have solved this using the flag USBBusFix=Yes.

 

Is there a way to avoid to use this flag?? Could I try to make any other change to improve my boot132 for P5Q family ??

 

Thanks!

[Gringo Vermelho]

That's great, nice work. Is that with cVad's LegacyAppleLPC or did you make your own?

 

I don't remember seeing that USB error on my P5Q-E, which, like the P5Q Pro has USB ports on the ICH10R.

 

Make sure your friend is using the default BIOS settings for USB, Legacy Support set to auto etc etc, the default settings are listed in the manual.

 

In any case, USBBusFix=y should not do any harm on mobos where it is not needed, I think you can safely leave it in.

[buoo]

There is no reason to use NullCPUPM, your boot CD is for a P5Q-series board with a Core microarchitecture CPU. If you're doing this because you want Pentium 4/D users to be able to use your boot CD, you need to provide a patched kernel as well, and the ability to select it during boot. Otherwise it's pointless to block AppleIntelCPUPowermanagement.kext. Plus you're killing native power management, which is one of the main features of Chameleon 2.0 RC5.

 

I don't want to take care about Pentium4/D users but Have I to add the following strings in the com.apple.boot.plist if I don't use Nullcpupowermenagment.kext ????

 

       <key>DropSSDT</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>

 

 

That's great, nice work. Is that with cVad's LegacyAppleLPC or did you make your own?

 

I am using cVad's LegacyAppleLPC

 

 

Thanks :mellow:

[Gringo Vermelho]

Have I to add the following strings in the com.apple.boot.plist if I don't use Nullcpupowermenagment.kext ????

       <key>DropSSDT</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>

Only if you want native CPU power management to work!

To activate P-States generation add "GeneratePStates"="Yes" option into boot.plist. To activate C-States generation add "GenerateCStates"="Yes" option into boot.plist. Those features are not activated by default!

Plus:

To enable native power management you should use proper mac model (...)

Here's a complete MacPro3,1 smbios.plist (except serial number) that you can use on the boot CD:

MacPro3_1smbios.plist.zip

Also, you might want to play around with this: http://www.kexts.com/view/343-injector_for...e.html?langid=1

As you can see, you'll need to collect SMbus device IDs from all your target P5Q boards - P5Q-E (ICH10R) is 3a30, I don't know if the SBus dev ID is the same for all P5Q boards with ICH10R - you'll have to find out. Ask your friend to run LSPCI -nn on his P5Q Pro.

It doesn't really do anything AFAIK except getting rid of some error messages during boot, and it's not necessary for booting and installing OS X. But for completions sake I think it would be a nice addition.

[buoo]

Hei Gringo

 

A further ACPI error could cause a stop during the installation for some P5Q, so the risk could be reduced using the NullCpuPoweragement.

What do you think about?

So regarding the smbios.plist can I not add the serial number?

 

Using EvoToolsX I discovered that the P5Q Deluxe's smbus is the same as P5Q (3a30)

Maybe it's the same for many P5Q and I can add random smbus in SMBus_injector, like this 3a32 3a33 3a34 for more safeness, but this is optional!

[Gringo Vermelho]

A further ACPI error could cause a stop during the installation for some P5Q, so the risk could be reduced using the NullCpuPoweragement.

Tell me more about the error, maybe there's a better way.

Disabling native CPU power management just because a few P5Q boards are misbehaving is not cool.

So regarding the smbios.plist can I not add the serial number?

Of course you can. But I think people might want to add their own when they're done using the boot CD and have Chameleon installed to their hard drive. Here's a tutorial from Prasys on how to create your own "authentic" serial number:

http://prasys.info/2009/11/understanding-mac-serial-number/

If you don't override it via smbios.plist, the serial number will be "SOMESRLNMBR" which I think is no better or worse than you adding a random serial number.

I can add random smbus in SMBus_injector, like this 3a32 3a33 3a34 for more safeness

That's a really terrible idea, don't do that. Adding random device IDs that you've made up yourself will not accomplish anything.

All the P5Q boards use ICH10 or ICH10R, right? (it's your boot CD, do the research!) so, 3a30 is the smbus on ICH10R (now confirmed on P5Q-E and P5Q Deluxe). What's the device ID for the smbus on P5Q models with ICH10 (non-R)? That's what you need to find out.

[buoo]

Tell me more about the error, maybe there's a better way.

Disabling native CPU power management just because a few P5Q boards are misbehaving is not cool.

 

There was a misunderstanding, there isn't any error.

I was asking you if to ensure the working of this cd boot for every P5Q it was better using the nullcpupowermenagment. I want only to guarantee that every person will be able to install Snow. Do you think that its use is better or not? I don't know this! This is a curiosity.

 

Of course you can. But I think people might want to add their own when they're done using the boot CD and have Chameleon installed to their hard drive. Here's a tutorial from Prasys on how to create your own "authentic" serial number:

http://prasys.info/2009/11/understanding-mac-serial-number/

If you don't override it via smbios.plist, the serial number will be "SOMESRLNMBR" which I think is no better or worse than you adding a random serial number.

 

Of course everyone should have an authentic serial number, but the bootcd must be only one, so what is the serial number that I have to insert in smbios.plist??

Could you write it to me?

 

That's a really terrible idea, don't do that. You might end up adding a device ID that belongs to a different device altogether.

All the P5Q boards use ICH10 or ICH10R, right? (it's your boot CD, do the research!) so, 3a30 is the smbus on ICH10R (now confirmed on P5Q-E and P5Q Pro). What's the device ID for the smbus on P5Q models with ICH10 (non-R)? That's what you need to find out.

 

So in the Smbus_injector.kext i have to insert only two id: 3a30 and "Mr.X"

[Gringo Vermelho]

Power Management: I think you should leave it in - if someone complains I'm sure we can find a workaround. It should work fine on all P5Q boards with a Core Micro-architecture CPU installed, and that's the "target audience" for your boot CD.

Someone using a non-Core Micro-architecture CPU cannot use your boot CD at all because they can't run the vanilla kernel anyway.

 

Serial Number: As I said, if you don't add a serial number anyone who boots with your CD will just get "SOMESRLNMBR" assigned. This is perfectly fine.

 

People can then create their own personal serial number following Prasys' tutorial and use that when they stop using your Boot CD and install Chameleon to their hard drive.

Perhaps you could add a readme.txt to your boot CD with links and stuff that explain these things.

 

If you're hellbent on adding a serial number, just add something like "12345678910" or "BUOOWASHERE" (11 characters).

I don't like it but it's your boot CD so do whatever you think is cool.

 

SBUS: As I said, All you need to do is to get someone with a P5Q board with ICH10 (non-R) to run LSPCI-nn so that you can get the correct device ID.

Another thing you can do is google for this information, it's not hard to find. Sites that collect Linux bug reports usually have full dumps done with LSPCI where you can get this info. "Mr. X" is not going to work for anybody, even Italians with an incomprehensible sense of humor.

 

Also I don't mind elaborating on things that I've said but I tend to get really cranky when I find that I have to repeat myself in writing. I'm glad to help you with this so far but please try not to make me repeat things that I've already written.

[Alessandro17]

Topic cleaned of off-topic posts. If anybody thinks there is something technically wrong with this topic, they are welcome to intervene in a civilized manner.

[Gringo Vermelho]

Thanks.

 

If anyone is interested, the finished product ended up here:

 

http://www.insanelymac.com/forum/index.php?showtopic=232885

http://www.insanelymac.com/forum/index.php?showtopic=234196

[Alessandro17]

If anyone is interested, the finished product ended up here:

 

http://www.insanelymac.com/forum/index.php?showtopic=232885

http://www.insanelymac.com/forum/index.php?showtopic=234196

 

A pity that there wasn't an English version, in the end.

[Gringo Vermelho]

If you run the page through google translate it's not perfect but anyone who understands English will be able to follow the instructions.

[Alessandro17]

If you run the page through google translate it's not perfect but anyone who understands English will be able to follow the instructions.

 

Maybe some of us could volunteer to translate it into English? Possibly you, buoo or myself.

[Gringo Vermelho]

It really isn't necessary. Look:

 

http://translate.google.com/translate?hl=e...wtopic%3D232885

 

http://translate.google.com/translate?hl=e...wtopic%3D234196

[Alessandro17]

I am amazed. It is good English.

[buoo]

Hi Gringo

 

Do you remember this?

 

I would set GraphicsEnabler=n and use FrameBufferDisabler.kext instead - GraphicsEnabler doesn't work with all video cards and having it enabled on a system with a video card that isn't supported by OSX video drivers can cause a lockup on boot.

Framebufferdisabler.kext is nice on a boot CD because it lets the system install and boot without any risk of video driver conflicts. Of course you lose hardware accelerated graphics, but only a few lucky people would have that without editing the drivers as well anyway. And QE/CI s not required during installation.

 

This stuff helped a lot of people but unluckely it doesn't work for other ATi owners (like ATi 4870).

 

The problem is the following:

 

 

I solved it with a new alternative boot-132 based on kabyl's bootloader http://www.insanelymac.com/forum/index.php?showtopic=231768 , GraphicsEnabler=Yes in c.a.b.p. without Framebufferdisabler.kext . This worked for several ATi !

ATi owners will able to use different framebuffers with AtiConfig= ......

 

 

Thanks for your help

[Gringo Vermelho]

Great, but on the other hand, setting GraphicsEnabler=y if you have an nvidia card that doesn't have its device ID in NVDANVx0HAL.kext can cause a lockup during boot!

 

This happens on 10.5.8 with my 7600 GT. I have to add its device ID to NVDANV50Hal.kext first.

 

Maybe there really is no way to make it work for everybody - unless you make separate versions of the boot CD for people with ATI and Nvidia cards.

 

Try picking apart other boot CDs such as [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], Empire EFI etc etc to see how they get around this issue.

Apparently I was wrong to assume that FrameBufferDisabler.kext would be the best solution.