Print

[rcfa]

After updating to 10.5.7, I'm unable to actually get OS X to boot all the way up unless I boot with the -x flag. If I don't, I get the endless blue screen & HD light just flashes away. Should I reinstall the 950 kexts?

yes, the unpatched 10.5.7 GMA950 related extensions will cause garbled screen.
Either the latest package already contains my patched 10.5.7 kexts, or the next version will, plus there will be a bash script that will let you patch this and hopefully future versions of these kexts.

Currently working on figuring out a few other issues, like DSDT optimizations, etc. so V3 of the package should arrive in a few days or so, depending on how much spare time I have and how much progress I make...

[GuyHersh]

I just noticed that my screensaver never kicks on, even though its definitely set to turn on after 3 minutes.  I don't think the monitor shuts off either, nor does it go to sleep (unless I tell it to, in which sleep mode works fine)

Anyone else have this problem?  Would it be related to the VoodooPower.kext?

[rcfa]

I just noticed that my screensaver never kicks on, even though its definitely set to turn on after 3 minutes.  I don't think the monitor shuts off either, nor does it go to sleep (unless I tell it to, in which sleep mode works fine)

Anyone else have this problem?  Would it be related to the VoodooPower.kext?

Not a problem here. The only thing that will not work is timed sleep, i.e. if you set your computer to go to sleep after X minutes of inactivity, that will not happen. But from screen saver and screen sleep work (likely drive sleep, too, but I didn't specifically try to test for that).

Try to repair your drive's permissions, and switch time and screen saver once or twice afterwards, to see if that changes anything.

Working on an updated package anyway, which may cure some minor issues, although this should have been working all along, at least it did here.

[SheepNervous]

Hey Guys,

I have a DSDT patch question. I extracted the patcher, ran the GUI is the steps Guy listed and I'm booting fine without cpus=1 however when I open up GenericCPUPMControl it isn't showing my CPUs and throttling doesn't work. Does anyone have any ideas on this? I'm patched up to 10.5.7, KEXTs installed, and have Chameleon running as well.

[rcfa]

Hey Guys,

I have a DSDT patch question. I extracted the patcher, ran the GUI is the steps Guy listed and I'm booting fine without cpus=1 however when I open up GenericCPUPMControl it isn't showing my CPUs and throttling doesn't work. Does anyone have any ideas on this? I'm patched up to 10.5.7, KEXTs installed, and have Chameleon running as well.

Not sure why everyone keeps patching. My package contains a read-to-yse dsdt.aml file, heck, if you dd over the EFI partition of the disk image I put together, then the entire setup of the EFI partition is done.
(In the next releas that will change a bit, because to deal with the IOPlatformUUID correctly, etc. there are a few places that you will have to put your computer's MAC address and serial number to have a perfectly tuned setup).
All that requires is that you're all on the 802 version of the system firmware, because that's the only one I tested my setup with.

PS: in case there is a question about this: the disk image I supplied is a *device* disk image, the device being a 1GB SD card. This SD card has TWO partitions, an EFI partition, which you will have to manually mount to see, and the partition with the various tools and extensions on it. Most of the tools you should never have to touch, they are just there for convenience, because I used them at some point in time during my exploration on how to do this all the best way, and the disk image serves also as my personal EeeHackingToolkit, I'm too lazy to maintain two different disk images...

[yodadaone]

Quick question guys,

During the OS install did you have to repartition the HD in Disk Utility? If so is there a way to get around that, I would like to keep my XP installed and just install Mac on the second partition I have.

Thanks for any info!

sheep, don't think there is away without having to reinstall xp as osx required guid and not mbr partition.  if someone knows please share.

this info is from insane forum:  make an image of your xp (e.g., using acronis), boot with 132 cd/usb, use diskutil to partition with guid option, install osx, boot with 132 cd/usb, create image of osx disk - you'll need an external usb drive for this; repartition drive with mbr option; restore xp image; boot with 132 cd/usb; restore osx image from external usb drive.

more info here:  http://www.mlvision.com.au/mediawiki/index.php/GPT_with_Mac_OS_X_and_Windows_XP

[rcfa]

Quick question guys,

During the OS install did you have to repartition the HD in Disk Utility? If so is there a way to get around that, I would like to keep my XP installed and just install Mac on the second partition I have.

Thanks for any info!

It's possible, but quite tricky. Mac OS X, when you partition with Disk Utility, makes actually an MBR/GUID hybrid partition scheme.

With this approach, you can make WinXP think it's on an MBR disk and OSX that it's on a GUID disk.

What you would need to do this, is access to another computer running Mac OS X, and then hook up your current drive to that computer. You'd then have to have this drive in a state where Disk Utility shows its presence, but has none of the file systems mounted. (meaning there's actually a /dev/diskN assigned to the drive, but nothing has a handle onto anything on that drive)

You then have to print the existing partition table for your records, and then wipe the partition table and create from scratch with gpt a new partition table in the order required for things to work. Once that's done, you have to use fdisk to mirror the partition setup in the MBR partition table. Key thing is, that the blocks occupied by the XP partition end up being the very same ones as you had used before (that's why you printed out the layout of the existing partition table at the beginning)

If you didn't screw up, all the data that used to be on the partition will not be touched and now show up in the "new" partition.

This is a high-level overview of what you would need to do. If you're not comfortable at the command line and with the use of tools like dd, gpt and fdisk, I'd say the short answer to your question is "No, not possible".
If you are comfortable with these tools, have the ability to dump the entire drive with dd onto some backup, such that you can restore things if need be, and then follow the approach outlined above, then the answer is "Yes, possible, but be careful..."

PS: stay away from parted, pMagic, etc. these will screw with the GUID and flags of the WinXP partition, and essentially make it unbootable...

[cbf88]

Hey Guys,

I have a DSDT patch question. I extracted the patcher, ran the GUI is the steps Guy listed and I'm booting fine without cpus=1 however when I open up GenericCPUPMControl it isn't showing my CPUs and throttling doesn't work. Does anyone have any ideas on this? I'm patched up to 10.5.7, KEXTs installed, and have Chameleon running as well.

Not sure why everyone keeps patching. My package contains a read-to-yse dsdt.aml file, heck, if you dd over the EFI partition of the disk image I put together, then the entire setup of the EFI partition is done.
(In the next releas that will change a bit, because to deal with the IOPlatformUUID correctly, etc. there are a few places that you will have to put your computer's MAC address and serial number to have a perfectly tuned setup).
All that requires is that you're all on the 802 version of the system firmware, because that's the only one I tested my setup with.

PS: in case there is a question about this: the disk image I supplied is a *device* disk image, the device being a 1GB SD card. This SD card has TWO partitions, an EFI partition, which you will have to manually mount to see, and the partition with the various tools and extensions on it. Most of the tools you should never have to touch, they are just there for convenience, because I used them at some point in time during my exploration on how to do this all the best way, and the disk image serves also as my personal EeeHackingToolkit, I'm too lazy to maintain two different disk images...

I tried to mount the EFI partition on the disk image, but was unable to do so. I can see it in diskutil as /dev/disk1s1, but when I try to mount it like I do with my native EFI partition with mkdir /Volumes/EFI and mount_hfs /dev/disk0s1 /Volumes/EFI, I just get permission denied. Is there a way to mount the EFI partition on your image without putting it on a card?

Something else, too: GenericCPUPMControl.app only shows P2. In my previous iPC 10.5.7 install, it showed both P1 and P2, so I'm guessing it's not seeing the hyperthreading? I find that strange since my activity monitor shows I clearly have hyperthreading.

And one last thing: I'm not sure about how well pre-made, distributed DSDT.aml files work, since they're based on hardware and wifi cards seem to differ a little from user to user.

[rcfa]

I tried to mount the EFI partition on the disk image, but was unable to do so. I can see it in diskutil as /dev/disk1s1, but when I try to mount it like I do with my native EFI partition with mkdir /Volumes/EFI and mount_hfs /dev/disk0s1 /Volumes/EFI, I just get permission denied. Is there a way to mount the EFI partition on your image without putting it on a card?

Well, sure. First, assuming you can see it as you say as /dev/disk1s1, then you'd have to mount it with mount_hfs /dev/disk1s1 /some/mountpoint, and not as you write with mount_hfs /dev/disk0s1 /some/mountpoint.

Further, this is likely a privileged operation, so you either have to do this as root, or you have to use the sudo command to do it.

Lastly, it doesn't matter if you open the disk image, or if you restore that disk image to an SD card, the partition table, etc. should all remain the same. If you double click on the disk image, then the second partition will be mounted. So you can see the mount command to see what is mounted, and you then simply pick the first partition of that device, so if the main partition mounted is on /dev/disk4s2, then you can mount the EFI partition as /dev/disk4s1, but to dd it over to your boot drives EFI partition, there's no need to mount it (actually, it shouldn't be mounted while you do that).

Something else, too: GenericCPUPMControl.app only shows P2. In my previous iPC 10.5.7 install, it showed both P1 and P2, so I'm guessing it's not seeing the hyperthreading? I find that strange since my activity monitor shows I clearly have hyperthreading.

When things are handled properly, there will be made a distinction between CPU cores and number of threads.
Correctly the N280 should be recognized as a single, single-core CPU with hyperthreading.
If you don't see that, your DSDT.aml file is likely wonky. Also since I've moved on to VoodooPower, which should be part of the next version of my compilation, I can't quite tell you how it showed up for me, but basically, if you get two CPU meters in Activity Monitor, and you don't have to boot with cpus=1. then chances are, things are OK.

And one last thing: I'm not sure about how well pre-made, distributed DSDT.aml files work, since they're based on hardware and wifi cards seem to differ a little from user to user.

You may have a point there. Although, I'm not sure how much about the WiFi card is actually in the DSDT.aml file, because PCI cards usually have their own firmware, and the DSDT is supposed to patch the mobo's firmware. I couldn't find anything in the dsdt.dsl that would be WiFi card specific, but that doesn't mean much given my lack of knowledge about the details of this matter.

In any case, since the stock WiFi card doesn't properly work with OS X anyway, and since most who care about WiFi will spend the $30 to get an Apple Broadcom based card, the difference may not matter, if there is any.

[cbf88]

I tried to mount the EFI partition on the disk image, but was unable to do so. I can see it in diskutil as /dev/disk1s1, but when I try to mount it like I do with my native EFI partition with mkdir /Volumes/EFI and mount_hfs /dev/disk0s1 /Volumes/EFI, I just get permission denied. Is there a way to mount the EFI partition on your image without putting it on a card?

Well, sure. First, assuming you can see it as you say as /dev/disk1s1, then you'd have to mount it with mount_hfs /dev/disk1s1 /some/mountpoint, and not as you write with mount_hfs /dev/disk0s1 /some/mountpoint.

Further, this is likely a privileged operation, so you either have to do this as root, or you have to use the sudo command to do it.

Lastly, it doesn't matter if you open the disk image, or if you restore that disk image to an SD card, the partition table, etc. should all remain the same. If you double click on the disk image, then the second partition will be mounted. So you can see the mount command to see what is mounted, and you then simply pick the first partition of that device, so if the main partition mounted is on /dev/disk4s2, then you can mount the EFI partition as /dev/disk4s1, but to dd it over to your boot drives EFI partition, there's no need to mount it (actually, it shouldn't be mounted while you do that).

Something else, too: GenericCPUPMControl.app only shows P2. In my previous iPC 10.5.7 install, it showed both P1 and P2, so I'm guessing it's not seeing the hyperthreading? I find that strange since my activity monitor shows I clearly have hyperthreading.

When things are handled properly, there will be made a distinction between CPU cores and number of threads.
Correctly the N280 should be recognized as a single, single-core CPU with hyperthreading.
If you don't see that, your DSDT.aml file is likely wonky. Also since I've moved on to VoodooPower, which should be part of the next version of my compilation, I can't quite tell you how it showed up for me, but basically, if you get two CPU meters in Activity Monitor, and you don't have to boot with cpus=1. then chances are, things are OK.

And one last thing: I'm not sure about how well pre-made, distributed DSDT.aml files work, since they're based on hardware and wifi cards seem to differ a little from user to user.

You may have a point there. Although, I'm not sure how much about the WiFi card is actually in the DSDT.aml file, because PCI cards usually have their own firmware, and the DSDT is supposed to patch the mobo's firmware. I couldn't find anything in the dsdt.dsl that would be WiFi card specific, but that doesn't mean much given my lack of knowledge about the details of this matter.

In any case, since the stock WiFi card doesn't properly work with OS X anyway, and since most who care about WiFi will spend the $30 to get an Apple Broadcom based card, the difference may not matter, if there is any.

Sorry, I made a typo. I meant to say when I mount_hfs /dev/disk1s1 /Extensions/EFI it tells me permission is denied, even when I sudo -s to root beforehand. I think it might have something to do with the fact that disk1s1 etc are virtualized assignments given out by hdiutil, so I'm going to try to get an SD card and try again.

[rcfa]

Ooops!

Just forgot something: the disk image is of course read-only, while the SD card is writeable!

So you will have to mount the file system read-only, otherwise, when you try to mount it rw, write access will fail with "permission denied".
So try
mount_hfs -o ro /dev/disk1s1 /some/mountpoint
that should work...
...for the same reason you may get an error mounting the disk image when you just double-click on it.

[cbf88]

RCFA, that worked like a charm, thanks! I was looking at the different com.apple.Boot.plists in the EFI partition on the rescue image, and just had some questions...

I notice you specifically direct chameleon to use dsdt.aml with <key>DSDT</key> <string>dsdt.aml</string>. I thought chameleon would always load dsdt.aml files located in efi if present? I was also curious if you are able to boot with working video without an EFI string for it in your boot.plist? I ask because I notice the video kexts have the 0x27ae patch applied.

[pootify]

Bump to my previous question: anyone having keyboard issues with VoodooPS2Controller? My power button no longer works, and the tilde key (to the left of the 1 key) registers a different character. What kext might it still be conflicting with?

[SheepNervous]

Quick question guys,

During the OS install did you have to repartition the HD in Disk Utility? If so is there a way to get around that, I would like to keep my XP installed and just install Mac on the second partition I have.

Thanks for any info!

It's possible, but quite tricky. Mac OS X, when you partition with Disk Utility, makes actually an MBR/GUID hybrid partition scheme.

With this approach, you can make WinXP think it's on an MBR disk and OSX that it's on a GUID disk.

What you would need to do this, is access to another computer running Mac OS X, and then hook up your current drive to that computer. You'd then have to have this drive in a state where Disk Utility shows its presence, but has none of the file systems mounted. (meaning there's actually a /dev/diskN assigned to the drive, but nothing has a handle onto anything on that drive)

You then have to print the existing partition table for your records, and then wipe the partition table and create from scratch with gpt a new partition table in the order required for things to work. Once that's done, you have to use fdisk to mirror the partition setup in the MBR partition table. Key thing is, that the blocks occupied by the XP partition end up being the very same ones as you had used before (that's why you printed out the layout of the existing partition table at the beginning)

If you didn't screw up, all the data that used to be on the partition will not be touched and now show up in the "new" partition.

This is a high-level overview of what you would need to do. If you're not comfortable at the command line and with the use of tools like dd, gpt and fdisk, I'd say the short answer to your question is "No, not possible".
If you are comfortable with these tools, have the ability to dump the entire drive with dd onto some backup, such that you can restore things if need be, and then follow the approach outlined above, then the answer is "Yes, possible, but be careful..."

PS: stay away from parted, pMagic, etc. these will screw with the GUID and flags of the WinXP partition, and essentially make it unbootable...

Thanks for the tips rcfa (no to mention putting together the whole driver/utils package for this), what I eventually ended up doing was backing up my data and starting from scratch, figured it would be easier.

I used the method located at http://www.insanelymac.com/forum/index.php?showtopic=116505&hl= to create a retail Mac OS X CD that would install to a MBR partition. After getting both OS packages loaded I updated and went from there.

Is there any chance that we'll see the rest of your write-up Lonely? I'd like to compare what you did vs. what I did to see if I missed anything.

[rcfa]

Bump to my previous question: anyone having keyboard issues with VoodooPS2Controller? My power button no longer works, and the tilde key (to the left of the 1 key) registers a different character. What kext might it still be conflicting with?

The power button, I think got lost in a different context, I don't think it's part of the keyboard driver, but I could be wrong.
The thing with the ~ character is a matter of the wrong keyboard type being recognized (ISO rather than ANSI layout).

If you download this here: http://forum.voodooprojects.org/index.php?action=dlattach;topic=304.0;attach=257 from this thread http://forum.voodooprojects.org/index.php/topic,304.0.html
the keyboard layout issues should be fixed.

That will be part of my next package, and the advantage of using the Voodoo keyboard driver is that it's not some hacked Apple driver that is no longer supported, but a proper, maintained driver, so we're looking at future enhancements and likely less breakage in the context of future OS updates.

[rcfa]

RCFA, that worked like a charm, thanks! I was looking at the different com.apple.Boot.plists in the EFI partition on the rescue image, and just had some questions...

I notice you specifically direct chameleon to use dsdt.aml with <key>DSDT</key> <string>dsdt.aml</string>. I thought chameleon would always load dsdt.aml files located in efi if present? I was also curious if you are able to boot with working video without an EFI string for it in your boot.plist? I ask because I notice the video kexts have the 0x27ae patch applied.

The EFI string is there not for the video, but to make the built-in ethernet adapter be recognized as built-in, at least if it's what I have in there now. In the course of the various experiments I'm not sure what I had when. In any case, getting the built-in ethernet adapter to be recognized as built-in is one of the steps to get the IOPlatformUUID to be properly assigned, which in turn is used for things like TimeMachine, MobileMe syncing, etc. Without it, the OS will sort of work, but you may have the infamous Error 35 type messages in your system log, and certain things wont work properly in non-obvious ways.

If the EFI string does what I think it does (i.e. does what my current EFI string does), then you should see a number bigger than zero as output from this command:

Code: [Select]

cat /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist | grep -A 1 "IOBuiltin" | grep true | wc

As for why I set the dsdt.aml thing explicitly: simply to make sure that
a) it's explicit
b) if the default behavior of Chameleon should change in the future, things won't break
c) as a reminder of the syntax and options that exist in com.apple.boot.plist, such that if I ever want to do a non-default override, I don't have to go hunting all over the internet fori just to figure out what values to plug in there.

So there are other values there, too, which are simply explicit statements of the defaults, but it won't hurt or impact the performance in any significant way to have them there, and it has the above listed advantages.

[pootify]

Here's a patched DSDT.aml file for bios 0802 that fixes the power button issue, and also removes the need for Clamshell.kext and Natit.kext.

[rcfa]

Here's a patched DSDT.aml file for bios 0802 that fixes the power button issue, and also removes the need for Clamshell.kext and Natit.kext.

Thanks. How did you derive that one? Just such that I can combine it with whatever fixes my dsdt file has, or know what I could have done differently....

[cbf88]

I'm pretty sure that dsdt.aml is the one included in eNik's install bundle. It works because it just adds custom methods for the various devices and sleep, or something along those lines.

With the eNick dsdt.aml, I lose voodoo speedstepping upon waking up from sleep. Not sure why yet.

[rcfa]

I'm pretty sure that dsdt.aml is the one included in eNik's install bundle. It works because it just adds custom methods for the various devices and sleep, or something along those lines.

With the eNick dsdt.aml, I lose voodoo speedstepping upon waking up from sleep. Not sure why yet.

Indeed, Speedstep is gone. I don't think that the silly power button is worth that much. I can get all the functions of the power button through the Apple Menu, so big deal if it doesn't work.

I'll diff the two files by decompiling them, maybe I can create a version that doesn't kill speedstep...
...it'll take educated guessing, since I really don't know what I'm doing when it comes to dsdt.dsl files

I was speaking too soon. Some background process sucked so much CPU that speedstepping never went into action. But once I killed the stray process, things were just fine, even after sleep.

Anyway, we're getting closer. Last thing I'm investigating is some stuff devised for the 1000H to allow all the custom buttons to work. If I can get that running on the 1000HE without breaking anything, then we're golden. All that's missing in that case is the final version of Chameleon that allows for DVD booting and has the hibernation fix, plus better optimized VoodooHDA drivers, but both of these are easy fixes, once available. All the hard stuff is almost solved.

I have version 3 pretty much ready, but I wait with the release to see if I can the above mentioned custom button stuff working. If yes, I'll make it part of the distribution, if not, I'll put the version 3 up as it is now.

[Troklo]

Go rcfa!

i´m waiting for v3 of your patch to give this a go, once again thx for all the effort your putting in to this.

[iGo]

My short story of vanilla install - yesterday I got my new 1000HE instead of stolen one and I've decided to install MBR dual boot - XP & Mac OS. I have rcfa's v.2 package (thanks, Ronald!) and 10.5.6 Mac OS X Retail with modified OSInstall.mpkg to allow MBR install. Firstly, I installed 2 Gb PNY 667Mhz memory stick and changed stock HDD with WD 320Gb. Secondly, I booted into WinXP from my multiboot flash and made 3 NTFS partitions - 1st for XP (27Gb), 2nd for OS X (27Gb) and 3rd for rest of stuff.
After that I installed XP on 1st partiton and booted from external DVD, using boot 132 disk from rcfa's pack. After boot prompt I press enter and enter again (to see default hexadecimal DVD boot device), change boot 132 disk with Leopard one and press enter again. I get prompt saying that it's booting Leopard and press F8 for boot options. I used "-f -v cpus=1" as boot keys and start to wait of install assistant. After running Disk Utility, I choose 2 nd partition labled "OS X" and erase with  "HFS+ Journaled". Then all is as detailed  described by LonelyTV - DSDT patch, Chameleon Bootloader, and the KEXTs. As a result I have MBR dual boot 1000HE (still have no Wi-Fi in Mac OS - Broadcom 4321 replacement is still on the way).

[rcfa]

Just to make it clear: you can install from a fully unmodified DVD without modified OSXinstall.mpkg, if you use a hybrid GUID/MBR partition approach like I do.
You boot from the OS X Install DVD, and partition the disk with that, and you'll end up with a hybrid partition scheme, which you can maintain as needed with gpt and fdisk. Since that's usually a one-time affair, the pay-off is that each OS feels perfectly at home by using the partition table that it expects to see.

[srcnix]

Guys,

I've managed to get a retail version of Leopard 10.5.6 installed using boot-132 as you have described here.

I changed my wireless card  a while back when I was using iDeneb so my wireless was working straight away. I decided to then do a full update through system update and rebooted -- this destroyed my graphics but bare in mind I hadn't put in any kexts -- just main install and then update. Safe mode helped here.

I then decided to install the kexts in the /System/Library/Extensions/ directory in the DMG you provided. This resulted in fine graphics but no keyboard or track pad.

I looked at the boot messages and it's mentioning about duplication in Trackpad, mouse and keyboard (PS2) kexts so I guess that's the issue. So now I have no keyboard or mouse and require a new install.

I also ran the Chameleon package and I didn't see any options to deselect anything, none the less that didn't allow me to boot, I got the grey Apple loading screen and then an error asking me to reboot? -- Do I need to install the DSDT before it will boot through Chameleon?

I'm happy to work out the rest myself but I just wanted confirmation on the order of things (Chameleon, DSDT, Kexts, and update) along with any idea towards the trackpad and keyboard.

Any help would be much appreciated.

Cheers


Steve

[rcfa]

Once you have your initial install running, use the opportunity to install Chameleon to the EFI partition, this should write the proper boot block. Then you can overwrite most of what Chameleon Installer did, by usind dd to copy the disk image's EFI partition over to your boot drive.
You know how to recover from the 10.5.7 update, which is the the proper way to go about it, once in safe-mode, you can install the patched kexts, and you're done.

Not sure what happened with your keyboard, maybe because you didn't have Chameleon and all the relevant drivers that are in the Extra/Extensions folder installed?

In any case, a regular USB keyboard and mouse will be able to get you out of that quandry and allow you to diagnose and fix the issue, since USB keyboards use regular Apple drivers which "just work". If the built-in keyboard would work over the internal USB interface rather than through a PS2 interface, we wouldn't even have the need for a keyboard driver.