Jump to content

LS8v17 # Mac OS X 10.5.7 # GA-P35-DS4 # GA-EP45-DQ6


LS8
 Share

1,296 posts in this topic

Recommended Posts

You wanna use google instead - type something like this in your search box: site:insanelymac.com/index.php? restart prompt

 

I agree 100%: the search engine here is nearly useless - google seems to be the only way around.

Link to comment
Share on other sites

Well the update did not go well so far on my DS4 Install ..

 

I ran the update to 10.5.4 from 10.5.2(yes I never did the 10.5.3) and now when I boot on my partition I have the spinning wheel going on and on.

 

I tried to do the /sbin/fsck -fy but no success.

 

I did the update from another OSx install (so I was not live on the partition I was updated), reinstall my kext (or so I think) repair permission, clear the kext cache ...

 

Any Idea ?

 

Thanks Geoff

Link to comment
Share on other sites

Didn't work for me. I should have said that I did try that before.

 

I originally used some kext back from February (except the SMBIOS) but I was extremely stable with that so no need to upgrade anything else. When I encountered the problem with 10.5.4 upgrade, the first thing I did was running the v12 srcipt.

 

So, I guess I will have to start back from scratch .... I still have my 911 boot disk (basic install of OSx 10.5.1) so I am not completely stuck. Personal data are on a separate disk so nothing lost at all in the operation (and anyway I can still see & acess the volume when boot on my 911).

 

That's part of the game ..... :blink:

 

Geoff.

Link to comment
Share on other sites

Didn't work for me. I should have said that I did try that before.

If you went from 10.5.2 -> 10.5.4 with the combo update, then it's likely that you let the installer put the AppleIntelCPUPowerManagement.kext in place, when you probably should have done the "while sleep 1 ; rm -rf /System/Library/Extensions/AppleIntelCPUP* ; done" thing while installing it. Oh, and don't forget about the first startup script that you need to edit before you reboot...

Link to comment
Share on other sites

Hi there,

 

I've been using your guide, and it has been working great but it has a few sore spots; In order to use it, you need a working installation of OS X, which means you either need an actual Mac or a pirated DVD. In addition, you have to jump through a few hoops to use Time Machine for a full system restore. Again, this requires either a pirated DVD or a Mac (I think).

 

With the release of the open-source Chameleon EFI for both cd and hd boot you now need just the retail DVD and a few tools. How to do this have already been covered in a few other threads, but if you like, I can write up a guide specifically for the GA-P35-DS4 using your LEO_GA_P35_DS4_PACK_V12. I've just tested it doing a retail install of 10.5.1, subsequently upgrading to 10.5.4 with patch+EFI strings, and doing a full restore of my old system afterwards. The process is slightly simpler than the original method with minimal terminal work.

 

If I do that, would you be interested in adding it to your guide?

 

EDIT: It is available here instead.

Link to comment
Share on other sites

Dewdman42 reported that he had a bit of trouble with post-patch.sh (http://forum.insanelymac.com/index.php?s=&showtopic=115877&view=findpost&p=821010):

 

3 - I think you should update the post-patch.sh, there should be a check in the beginning of the script to make sure that $1 has been provided. I missed that and fortunately the script didn't do any damage other than display jiberish. You should probably update your guide to make it more clear that there is an argument; by putting the actual command line onto its own line.

 

Could you add something like this to your script?

 

#!/bin/bash
if [ -z "$1" ]
then
 echo "You need to provide the partition name"
 exit 1
fi
if [ $# -gt 1 ]
then
 echo "Too many arguments"
 exit 1
fi
cd $(dirname $0)
# the rest of post-patch.sh

 

In addition to checking whether an argument has been provided, this will enable a user to just drag and drop the script from Finder to a terminal and add the partition name, which is ever so slightly easier than changing to the correct directory first ;)

Link to comment
Share on other sites

Aside from that, the patch script worked perfectly. Thanks so much for putting this pack together.

 

I'm also wondering though if its ok to change About this mac when setting up a vanilla install like this? Can I change it using OSX86tools without breaking anything? My mac was automatically named to "joe's iMac" and I would kind of like to call it something else. Also I'd like to update the CPU and memory info fields. Is that gonna break anything if I do that?

 

Also, I'm using the AppleSMBIO you provided us, but I'm wondering if there are any other variants of this AppleSMBIOS with different memory speeds, etc.. My memory is overclocked to 1000mhz currently, but displays in About this Mac as 667.

 

??

Link to comment
Share on other sites

Has anyone got GA-P35-DS4 and ATi 1950 ID 7244. Can anyone post here the plist and EFI strings for the Card with the board together.

 

I dont know how to get EFI String for ATI 1950 to go with the GA-P35-DS4 strings.. I wish that EFI Studio had ATI 1950 EFI Strings. :P

 

or some post me the pist file so I can add the file inside the efi studio

 

Thank ypu

Link to comment
Share on other sites

Hi Guys,

 

maybe it´s the wrong place here, because i used kalyway 10.5.2 for installing, but i think the problem might be motherboard-related.

 

Onboard LAN doesn´t work, but that doesn´t matter, i use USB WLAN instead. Audio now works fine with 889 kext. Geforce 8500 GT works great with nvinject. Restart and shutdown work with fix (but fans keep spinning for about 1/2-1 minute after shutdown and then stop. is that fixable?) but wake-up after sleep doesn´t work! And the worst thing is, I get kernel panics some times, often after some hours using itunes + firefox + stuffit.

Any ideas?

 

Cheers,

hacki

Link to comment
Share on other sites

Hi ls8.

A short question about external USB drives and wake-up after sleep.

If I put my system to sleep while having a USB drive with 2 partitions mounted and then wake the system up again, I always get a warning that the USB drive has not been properly unmounted.

The drive properly re-mounts afterwards and OSX tries to replay the journal, and no data is lost and no other problems.

Just wondering if this is a common problem or did I miss anything?

Thanks

Link to comment
Share on other sites

...If I put my system to sleep while having a USB drive with 2 partitions mounted and then wake the system up again, I always get a warning that the USB drive has not been properly unmounted...

 

I have the same. Even on my real iMac. It is not hackint0sh specific.

 

...Does that mean, I should apply the LS8v12 to my existing installation?...

 

Hard to say. LS8v12 is not tested on Kalyway, it is meant to be used on retail DVD installs only.

Link to comment
Share on other sites

i get this error

localhost root [77]:recreating system.keycahin because it cannot unlock; see /usr/libexec/security-check system

appleyukon 2-en 0 link active, 100-mbit,full duplexflow control disabled port 0

july 20:47:20 local host mdnsresponder mdnsresponder -170 (jan 15 2008.....

please help me what to do

Link to comment
Share on other sites

ls8: doesn´t work with kalyway, it spoiled my installation. i will give the retail dvd a try this evening. could you please provide all bios settings, i´m experiencing stange behaviour with my p35-ds4. when i have a lot I/O the disk activity freezes for some seconds (10-20-30) and then it starts again without giving an error. logs look good so far. i´m not sure if it could be a hardware problem...

i can produce this behaviour if i do the following:

 

dd if=/dev/random of=test bs=512k count=1000 [for example, just to create some I/O]

 

that makes the system slow down. if i know start repairing disk permissions or similar, the spinning wheel comes up, everything freezes for 10-20 seconds and then the system speeds up again, before it slows down after a while. when i kill dd everything is fine again. i recognized this behaviour the first time, when i used the migration manager to migrate data from another volume.

 

ram seems to be ok, i tested it with "remember". any ideas anybody???

Link to comment
Share on other sites

 Share

×
×
  • Create New...