 |
|
| node: | Re[5]: OS X 10.8 |
| template: | 4 |
| parent: | Re[4]: OS X 10.8 |
| owner: | eyo |
| viewed by: | |
| created: | 18.02.2012 - 17:10:51 |
|
cwbe coordinatez: 101 63540 63542 2109677 1857521 6505320 6505379 6505399 6505423 6505440 6508235 ABSOLUT KYBERIA |
| permissions | |
| you: | r, |
| system: | public |
| net: | yes |
total descendants::5
total children::2
takze to vyzera, ze to nie je kvoli vykonu, ale kvoli tomu, ze 10.8 uz bude iba cisto 64bit system. a na to predpokladam prepisanie ziadneho konfiguracneho suboru nepomoze :) ale zasa je ten zoznam kompatibilnych macov o dost vacsi ako som si myslel z toho povodneho linku.
The release notes for Mountain Lion clearly say that Mountain Lion is 64-bit only and does not support 32-bit Kernel Extensions, unlike Lion which is a hybrid 32/64-bit system that can run 64-bit apps on a 32-bit kernel.
That means it requires
a) A 64-bit processor
b) A 64-bit EFI
c) 64-bit Kernel Extensions for all devices
The first one isn’t a problem, since Lion dropped support for all pre-Core 2 CPUs, but b and c will be.
TUAW are 100% correct in blaming the Intel graphics processors. AppleIntelGMAX3100.kext and AppleIntelGMA950.kext are indeed 32-bit only Kernel Extensions, at least as far as Lion goes, whereas most other graphics drivers (including the X1600 and 7300 kexts) are both x86 and x64.
The other products The Verge list like the late 2006 iMacs/Macbook Pros and original Mac Pros aren’t excluded because of their GPUS, but because they don’t have 64-bit EFIs.
Here is every supported product along with its predecessor:
iMac (Late 2006): 32-bit EFI
iMac (Mid 2007): 64-bit EFI
MacBook (Mid 2007): 32-bit kext (GMA950)
Macbook (Aluminum 2008, Plastic 2009): 64-bit kext (GF9400)
Macbook Air (original): 32-bit EFI
Macbook Air (late 2008): 64-bit EFI
Macbook Pro 13" (Original, aka Mid 2009): 64-bit EFI
Macbook Pro (15", 2.16/2.33GHz): 32-bit EFI
Macbook Pro (15", 2.2/2.4GHz): 64-bit EFI
Macbook Pro (17", Late 2006): 32-bit EFI
Macbook Pro (17", Late 2007): 64-bit EFI
Mac Mini (Mid 2007): 32-bit kext (GMA950)
Mac Mini (Early 2009): 64-bit kext (GF9400M)
Mac Pro (Original): 32-bit EFI
Mac Pro (Early 2008): 64-bit EFI
The list of supported Macs sure looks like the list of fully 64-bit machines now doesn’t it?
No “guesses” as to why these machines aren’t compatible are required. It took all of 5 minutes to look up the machines on a website. A tech website should be able to do the same!
The release notes for Mountain Lion clearly say that Mountain Lion is 64-bit only and does not support 32-bit Kernel Extensions, unlike Lion which is a hybrid 32/64-bit system that can run 64-bit apps on a 32-bit kernel.
That means it requires
a) A 64-bit processor
b) A 64-bit EFI
c) 64-bit Kernel Extensions for all devices
The first one isn’t a problem, since Lion dropped support for all pre-Core 2 CPUs, but b and c will be.
TUAW are 100% correct in blaming the Intel graphics processors. AppleIntelGMAX3100.kext and AppleIntelGMA950.kext are indeed 32-bit only Kernel Extensions, at least as far as Lion goes, whereas most other graphics drivers (including the X1600 and 7300 kexts) are both x86 and x64.
The other products The Verge list like the late 2006 iMacs/Macbook Pros and original Mac Pros aren’t excluded because of their GPUS, but because they don’t have 64-bit EFIs.
Here is every supported product along with its predecessor:
iMac (Late 2006): 32-bit EFI
iMac (Mid 2007): 64-bit EFI
MacBook (Mid 2007): 32-bit kext (GMA950)
Macbook (Aluminum 2008, Plastic 2009): 64-bit kext (GF9400)
Macbook Air (original): 32-bit EFI
Macbook Air (late 2008): 64-bit EFI
Macbook Pro 13" (Original, aka Mid 2009): 64-bit EFI
Macbook Pro (15", 2.16/2.33GHz): 32-bit EFI
Macbook Pro (15", 2.2/2.4GHz): 64-bit EFI
Macbook Pro (17", Late 2006): 32-bit EFI
Macbook Pro (17", Late 2007): 64-bit EFI
Mac Mini (Mid 2007): 32-bit kext (GMA950)
Mac Mini (Early 2009): 64-bit kext (GF9400M)
Mac Pro (Original): 32-bit EFI
Mac Pro (Early 2008): 64-bit EFI
The list of supported Macs sure looks like the list of fully 64-bit machines now doesn’t it?
No “guesses” as to why these machines aren’t compatible are required. It took all of 5 minutes to look up the machines on a website. A tech website should be able to do the same!