[Guide] Success! Install 10.8 on old unsupported Mac

H2SO4 · Nov 7, 2012

Alazoral said:
I successfully installed 10.8.2 with this guide, but there are two problems I have outstanding that I would really love some assistance with.

The first is that I can't set the boot disk. Neither the preference pane nor BootChamp can set it, and bless says:

Code:

Could not find IODeviceTree:/options Can't access "efi-boot-device" NVRAM variable

Since I am using a new non-EFI card, I can't use the boot select screen, so I am basically required to open the computer up, change the card back to the older EFI card to boot into Windows, set it as default using the Boot Camp control panel and then shut it down and put the new card back. In such a state it is easy to get back to ML but when I want to go back to Windows after, I would have to do the whole thing again.

So I guess I really need some kind of alternate boot menu that works with non-EFI cards or a third party or hacked up bless that will work on my Mac Pro 1,1, or something. Please, any assistance you wonderful people can give would be amazing.

The second issue, which is more minor, is that the computer believes that it is still 10.8.0, possibly due to the copying the kernel back manoeuvre. This means I can't update iPhoto, and it displays just "10.8" on About This Mac. I am also slightly concerned that just forever using this older kernel means I won't be able to benefit from any improvements or patches to it. Thoughts?

You have the same issue I have, (I think), and I hope your logic board hasn't died. Still not sure if mine has.
Tell me, does ;
1. nvram -p give you any kind of output in terminal?
2. Your DVD Player work with items that are not real DVDs? (That is open a VIDEO_TS folder or .img file with it).

Alazoral · Nov 7, 2012

H2SO4 said:
You have the same issue I have, (I think), and I hope your logic board hasn't died. Still not sure if mine has.
Tell me, does ;
1. nvram -p give you any kind of output in terminal?
2. Your DVD Player work with items that are not real DVDs? (That is open a VIDEO_TS folder or .img file with it).

My logic board should be fine, as I mentioned, I can set the boot disk just fine using the Windows control panel (ironically). If I was to guess I would assume it's some framework that in mountain lion doesn't know how to work the NVRAM for my OG Mac Pro.

1. nvram -p gives "nvram: nvram is not supported on this system"
2. Yep, DVD Player works great, both drives. Venture Brothers never looked better.

H2SO4 · Nov 7, 2012

Alazoral said:
My logic board should be fine, as I mentioned, I can set the boot disk just fine using the Windows control panel (ironically). If I was to guess I would assume it's some framework that in mountain lion doesn't know how to work the NVRAM for my OG Mac Pro.

1. nvram -p gives "nvram: nvram is not supported on this system"
2. Yep, DVD Player works great, both drives. Venture Brothers never looked better.

Then your problem is very similar. I get the same NVRAM message, that's part of the problem. Trouble is though, which framework. Oh and I think it's 10.8.2 as I'm sure I had no trouble with the earlier versions. My DVD Player works by the way, but only with real DVDs. You were trying with virtual disks right?

What NON EFI card do you have?

Alazoral · Nov 7, 2012

H2SO4 said:
Then your problem is very similar. I get the same NVRAM message, that's part of the problem. Trouble is though, which framework. Oh and I think it's 10.8.2 as I'm sure I had no trouble with the earlier versions. My DVD Player works by the way, but only with real DVDs. You were trying with virtual disks right?

What NON EFI card do you have?

Ha, it looks like bless isn't the only tool having trouble reading, I am too! Yeah, it quits silently for me too, weird. Console gives:

Code:

8/11/12 5:14:09.065 PM WindowServer[108]: CGXGetWindowOwner: Invalid window 421
8/11/12 5:14:09.065 PM DVD Player[1147]: CGSGetWindowOwner
8/11/12 5:14:10.297 PM com.apple.launchd.peruser.501[148]: ([0x0-0xb50b5].com.apple.DVDPlayer[1147]) Exited with code: 1
8/11/12 5:14:14.684 PM com.apple.SecurityServer[15]: Killing auth hosts
8/11/12 5:14:14.684 PM com.apple.SecurityServer[15]: Session 100022 destroyed

I am using a GTX 660, replacing a flashed HD 4890.

H2SO4 · Nov 7, 2012

Alazoral said:
Ha, it looks like bless isn't the only tool having trouble reading, I am too! Yeah, it quits silently for me too, weird. Console gives:

Code:

8/11/12 5:14:09.065 PM WindowServer[108]: CGXGetWindowOwner: Invalid window 421 8/11/12 5:14:09.065 PM DVD Player[1147]: CGSGetWindowOwner 8/11/12 5:14:10.297 PM com.apple.launchd.peruser.501[148]: ([0x0-0xb50b5].com.apple.DVDPlayer[1147]) Exited with code: 1 8/11/12 5:14:14.684 PM com.apple.SecurityServer[15]: Killing auth hosts 8/11/12 5:14:14.684 PM com.apple.SecurityServer[15]: Session 100022 destroyed

I am using a GTX 660, replacing a flashed HD 4890.

I have a 5770, tell me where exactly in Console did you get that text from?

Alazoral · Nov 7, 2012

H2SO4 said:
I have a 5770, tell me where exactly in Console did you get that text from?

All Messages.

Some brief research seems to indicate that the key framework is IOKit, which sounds pretty kernel-oriented. So that opens another possibility aside from blacklisting or effective blacklisting, it might be some kind of mismatch between kernel and framework.

H2SO4 · Nov 7, 2012

Alazoral said:
All Messages.

Some brief research seems to indicate that the key framework is IOKit, which sounds pretty kernel-oriented. So that opens another possibility aside from blacklisting or effective blacklisting, it might be some kind of mismatch between kernel and framework.

I wonder if anybody else with a 1,1 has the same issue?
Does your boot log also show FIPS being an issue?

I also compared the loaded extensions on a MacBook air using kextstat and found that com.apple.driver.AppleEFINVRAM isn't loaded on my Pro.
Tried manually loading with kextload but didn't work.

Alazoral · Nov 7, 2012

H2SO4 said:
I wonder if anybody else with a 1,1 has the same issue?
Does your boot log also show FIPS being an issue?

I also compared the loaded extensions on a MacBook air using kextstat and found that com.apple.driver.AppleEFINVRAM isn't loaded on my Pro.
Tried manually loading with kextload but didn't work.

No, my boot log seems pretty much fine. Although right after it seems like IOKit and a familar error rears its head:

Code:

Nov  8 16:16:54 localhost configd[18]: InterfaceNamer: timed out waiting for IOKit to quiesce
Nov  8 16:16:54 localhost configd[18]: Busy services :
Nov  8 16:16:54 localhost configd[18]:   MacPro1,1 [1, 97438 ms]
Nov  8 16:16:54 localhost DumpPanic[53]: Error getting a reference to IODeviceTree:/options

I am also not seeing anything mentioning EFI in my kextstat. Maybe fixing this is as simple as copying over an old kext?

H2SO4 · Nov 7, 2012

Alazoral said:
No, my boot log seems pretty much fine. Although right after it seems like IOKit and a familar error rears its head:

Code:

Nov 8 16:16:54 localhost configd[18]: InterfaceNamer: timed out waiting for IOKit to quiesce Nov 8 16:16:54 localhost configd[18]: Busy services : Nov 8 16:16:54 localhost configd[18]: MacPro1,1 [1, 97438 ms] Nov 8 16:16:54 localhost DumpPanic[53]: Error getting a reference to IODeviceTree:/options

I am also not seeing anything mentioning EFI in my kextstat. Maybe fixing this is as simple as copying over an old kext?

I hope it's that simple. I may clone and start looking for options. Trouble is I've deleted my old 10.8 and 10.8.1 installers.
I get no mention of anything about reference to IODeviceTree:/options in my boot log though. How are you accessing yours?

Alazoral · Nov 7, 2012

H2SO4 said:
I hope it's that simple. I may clone and start looking for options. Trouble is I've deleted my old 10.8 and 10.8.1 installers.
I get no mention of anything about reference to IODeviceTree:/options in my boot log though. How are you accessing yours?

Just in system.log in Console.app.

H2SO4 · Nov 7, 2012

Alazoral said:
Just in system.log in console.

Oh, Ok. Try sudo dmesg > ~/Desktop/BootLog.txt, it'll place a text file with the boot process on your desktop that'll open with TextEdit, (assuming that's your default editor).

Alazoral · Nov 7, 2012

H2SO4 said:
Oh, Ok. Try sudo dmesg > ~/Desktop/BootLog.txt, it'll place a text file with the boot process on your desktop that'll open with TextEdit, (assuming that's your default editor).

Thats a neat trick. OK, no errors there except something inconsequential about firewire and a ton of NTFS-fs errors which is weird since I shut down the computer correctly last time.

Code:

NTFS driver 3.10 [Flags: R/W].
NTFS volume name Windows, version 3.1.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0xdaf23 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0xdaf23.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0xdaf23 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0xc0883 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0xc0883.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0xc0883 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x15359 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x15359.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x15359 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0xcd9c1 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0xcd9c1.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0xcd9c1 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x54c9e is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x54c9e.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x54c9e (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x2ab91 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x2ab91.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x2ab91 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x5bb46 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x5bb46.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x5bb46 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x5e6e2 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x5e6e2.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x5e6e2 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0xd6b08 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0xd6b08.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0xd6b08 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x4e217 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x4e217.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x4e217 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x48deb is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x48deb.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x48deb (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0xd6b0c is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0xd6b0c.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0xd6b0c (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x51e6d is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x51e6d.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x51e6d (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x25c84 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x25c84.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x25c84 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x2d964 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x2d964.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x2d964 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x1ce7a is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x1ce7a.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x1ce7a (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x51bda is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x51bda.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x51bda (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x27390 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x27390.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x27390 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x316cb is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x316cb.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x316cb (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x1cfe7 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x1cfe7.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x1cfe7 (error 5).
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0x25642 is corrupt.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0x25642.  Run chkdsk.
NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0x25642 (error 5).

H2SO4 · Nov 7, 2012

Alazoral said:
Thats a neat trick. OK, no errors there except something inconsequential about firewire and a ton of NTFS-fs errors which is weird since I shut down the computer correctly last time.

Code:

NTFS driver 3.10 [Flags: R/W]. NTFS volume name Windows, version 3.1. NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_mft_record_map_ext(): Mft record 0xdaf23 is corrupt. Run chkdsk. NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed to map mft record. NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_inode_read(): Failed (error 5) for inode 0xdaf23. Run chkdsk. NTFS-fs error (device /dev/disk2s2, pid 164): ntfs_vnop_lookup(): Failed to get inode 0xdaf23 (error 5).

Wow. I get nothing NTFS related at all. Mind you I've uninstalled Paragon ages ago and don't use BootCamp, (I'm a Parallels man).
I keep folder in my top level Applications folder called ShellScripts and in that keep all of the little terminal tricks I use on a regular basis saved as Automator workflows. For that one if you open Automator Choose the 'Run AppleScript' function and paste in;

on run {input, parameters}
do shell script "dmesg > ~/Desktop/BootLog.txt" with administrator privileges

return input
end run
Then save it as an Application called BootLog it all comes together quite nicely as a clickable application.

hackerwayne · Nov 8, 2012

H2SO4 said:
Wow. I get nothing NTFS related at all. Mind you I've uninstalled Paragon ages ago and don't use BootCamp, (I'm a Parallels man).
I keep folder in my top level Applications folder called ShellScripts and in that keep all of the little terminal tricks I use on a regular basis saved as Automator workflows. For that one if you open Automator Choose the 'Run AppleScript' function and paste in;

on run {input, parameters}
do shell script "dmesg > ~/Desktop/BootLog.txt" with administrator privileges

return input
end run
Then save it as an Application called BootLog it all comes together quite nicely as a clickable application.

Right this just got more interesting, now 2 person is having the exact same issue. First things first, forgot to ask, to H2S04 are you using a flashed card or a genuine Apple card?

----------

cthurber said:
Will an ATi R6670 Graphics card in a Mac Pro 1,1 work? I have the other two 7300 GTs but I know they don't work... This card is technically for PCs and I didn't flash it but it works except for the boot screen.

Yes it will work in Lion not sure about ML thou

----------

Sparacis said:
Don't know if this has been discussed just throwing in my 2 cents. Is the brightness issues on macbook 3,1 and 4,1 because of the lack of light sensor like MBP have.

Nope, its because of the framework issue, the kext isnt complete as it was pulled from 10.6.2

----------

53kyle said:
Well that sucks, I guess I will just get the macbook aluminum 2008 because that is the most I can afford. Do you think and future mac os like 10.9, 11.0 will work on that?

Probably not, its at the edge lol.. The early 2008 MacBook isnt supported in ML, i won't be surprised if Apple decided to drop all C2D Macs.

----------

happel said:
This works nicely on my macbook4,1 . Great work all!

For me the brightness level in Mountain Lion remains at the same setting as I set in Lion, which is acceptable (in my opinion) as I don't change the brightness that much. The real problem what keeps me from really using Mountain Lion is the sleep issue, a laptop that can't sleep isn't all that useful. But who knows someone can come up with a clever solution .

Did anyone else notice ML is quite a bit slower than Lion? It shaves about 25% off my geekbench score..

Thats because the X3100 drivers don't have OpenGL, Geekbench score will drop dramatically.

H2SO4 · Nov 8, 2012

hackerwayne said:
Right this just got more interesting, now 2 person is having the exact same issue. First things first, forgot to ask, to H2S04 are you using a flashed card or a genuine Apple card?

----------

Genuine Apple 5770.

H2SO4 · Nov 9, 2012

By the way Alazoral, exactly what is your boot drive?

Alazoral · Nov 9, 2012

H2SO4 said:
By the way Alazoral, exactly what is your boot drive?

It's a Seagate. It is:

Code:

ST2000DM001-9YN164:

  Capacity:	2 TB (2,000,398,934,016 bytes)
  Model:	ST2000DM001-9YN164                      
  Revision:	CC4B    
  Serial Number:	            W1E0LN2J
  Native Command Queuing:	Yes
  Queue Depth:	32
  Removable Media:	No
  Detachable Drive:	No
  BSD Name:	disk1
  Rotational Rate:	7200
  Medium Type:	Rotational
  Bay Name:	Bay 1
  Partition Map Type:	GPT (GUID Partition Table)
  S.M.A.R.T. status:	Verified
  Volumes:
disk1s1:
  Capacity:	209.7 MB (209,715,200 bytes)
  BSD Name:	disk1s1
  Content:	EFI
Citadel:
  Capacity:	1.97 TB (1,968,859,484,160 bytes)
  Available:	1.05 TB (1,049,860,042,752 bytes)
  Writable:	Yes
  File System:	Journaled HFS+
  BSD Name:	disk1s2
  Mount Point:	/
  Content:	Apple_HFS
  Volume UUID:	8FE66EE3-BB25-34A9-B8CD-3C7E3554552E

H2SO4 · Nov 9, 2012

Alazoral said:

It's a Seagate. It is:

Code:

ST2000DM001-9YN164:

  Capacity:	2 TB (2,000,398,934,016 bytes)
  Model:	ST2000DM001-9YN164                      
  Revision:	CC4B    
  Serial Number:	            W1E0LN2J
  Native Command Queuing:	Yes
  Queue Depth:	32
  Removable Media:	No
  Detachable Drive:	No
  BSD Name:	disk1
  Rotational Rate:	7200
  Medium Type:	Rotational
  Bay Name:	Bay 1
  Partition Map Type:	GPT (GUID Partition Table)
  S.M.A.R.T. status:	Verified
  Volumes:
disk1s1:
  Capacity:	209.7 MB (209,715,200 bytes)
  BSD Name:	disk1s1
  Content:	EFI
Citadel:
  Capacity:	1.97 TB (1,968,859,484,160 bytes)
  Available:	1.05 TB (1,049,860,042,752 bytes)
  Writable:	Yes
  File System:	Journaled HFS+
  BSD Name:	disk1s2
  Mount Point:	/
  Content:	Apple_HFS
  Volume UUID:	8FE66EE3-BB25-34A9-B8CD-3C7E3554552E

Nothing strange in there then.

Alazoral · Nov 9, 2012

Ok, after restoring the old 10.7.5 AppleEFIRuntime kext from Time Machine, my computer did not only not break but kextstat shows it running!

Code:

   30    0 0xffffff7f82949000 0x5000     0x5000     com.apple.driver.AppleEFIRuntime (1.5.0) <7 6 5 4 3>

This is good news, however, I still can't seem to read or write to NVRAM.

H2SO4 · Nov 9, 2012

Alazoral said:
......The second issue, which is more minor, is that the computer believes that it is still 10.8.0, possibly due to the copying the kernel back manoeuvre. This means I can't update iPhoto, and it displays just "10.8" on About This Mac. I am also slightly concerned that just forever using this older kernel means I won't be able to benefit from any improvements or patches to it. Thoughts?

Best thing for that is to apply the 10.8.2 combo. Now when I did it, the time elapsed was about 20 hours so I suggest you clone first then boot from temporary install A and apply to install B which you'd cloned earlier using pacifist.

----------

Alazoral said:
Ok, after restoring the old 10.7.5 AppleEFIRuntime kext from Time Machine, my computer did not only not break but kextstat shows it running!

Code:

30 0 0xffffff7f82949000 0x5000 0x5000 com.apple.driver.AppleEFIRuntime (1.5.0) <7 6 5 4 3>

This is good news, however, I still can't seem to read or write to NVRAM.

At least that's a start. Now, anybody have the 10.8.0 kext.......Anybody?

Alazoral · Nov 9, 2012

I tried replacing the IOKit Framework and now it won't boot. Will have to change graphics cards and so on. I'll try the pacifist combo thing while I'm there.

hackerwayne · Nov 10, 2012

H2SO4 said:
Best thing for that is to apply the 10.8.2 combo. Now when I did it, the time elapsed was about 20 hours so I suggest you clone first then boot from temporary install A and apply to install B which you'd cloned earlier using pacifist.

----------

At least that's a start. Now, anybody have the 10.8.0 kext.......Anybody?

It won't be 20 hours if you disable signature signing in Pacifist

----------

Well try installing Lion, if the problem is on Lion as well, its definitely a hardware issue.

H2SO4 · Nov 10, 2012

Shouldn't be 20 hours but mine took aaaaaaages. Even with the enter key held down.
Probably better to install from a separate drive which leaves the Mac still useable in the mean time?

Is it perhaps something to do with the MP11 hardware?

Alazoral · Nov 10, 2012

hackerwayne said:
Well try installing Lion, if the problem is on Lion as well, its definitely a hardware issue.

Well my dual boot stuff was working fine on Lion. I just upgraded to Mountain Lion to use my new graphics card, but it looks like if I can't get boot camp working I should just time machine back to before I embarked upon this quest, use my old graphics card and just build a PC.

soldierblue · Nov 10, 2012

So it looks like I'll be coming into the possession of a 2006 Mac Pro with a Radeon 5770. From this guide I gather I should have 100% functionality? Have any of you guys done it with that specific machine?

[Guide] Success! Install 10.8 on old unsupported Mac

macrumors 603

macrumors newbie

macrumors 603

macrumors newbie

macrumors 603

macrumors newbie

macrumors 603

macrumors newbie

macrumors 603

macrumors newbie

macrumors 603

macrumors newbie

macrumors 603

macrumors 6502a

macrumors 603

macrumors 603

macrumors newbie

macrumors 603

macrumors newbie

macrumors 603

macrumors newbie

macrumors 6502a

macrumors 603

macrumors newbie

macrumors 6502

Our Staff