theconnactic Posted June 12, 2013 Share Posted June 12, 2013 Hi, folks! After a failed attempt to run 10.9 on my Asus 1201n netbook, i decided to try my luck with a more compatible hardware and installed it on a HHD where 10.6.8 was previously installed. I used pretty the same method i did for the Asus netbook - installed on a thumb driver first (i already had it, since i'd already done a installation using it for my netbook) and then restored it to the partition. Since the has already Snow Leopard on it, i decided to use Carbon Copy Cloner instead of simply restore the thumb drive to the disk: Carbon Copy Cloner gives me the option of keeping the files that weren't on the thumb drive untouched, while replacing the older 10.6.8 system files and core applications by their 10.9 counterparts. That's very useful a function, but also quite risky, and i wouldn't recommend installing Mavericks this way to anyone, unless s/he had already made a complete system backup, like i did. Obviously this method is only possible when you have another working partition to run CCC - in my case, i did it from inside my main HDD running 10.8.4. After the process was finished, i did the following in this order: installed latest Chameleon to the disk and replaced the Boot file by a patched one provided elsewhere by Oldnapalm (i read later that Ermac committed this file to the trunk, so it would be easier if i had waited, and i think latex Chameleon, therefore, can boot 10.9 without issues); copied my entire working Extra folder (including DSDT and SSDT) from my Mountain Lion disk to the root of my now-10.9'ed HDD; manually copied FakeSMC and reboot. So, when the system restarted (i used the common flags i always use for updates/upgrades, -v -f), it gracefully went to a kernel panic. And that's the downside of installing on an existing OSX installation. Went back to the 10.8.4 and removed SleepEnabler and Nawcom's "evil"kexts (which i already had in 10.6.8, since this installation was itself a clone of what i used to run on my AMD machine, and they never bothered me with my Intel machine, so i forgot they existed) and also the GPUSensor plugin from inside FakeSMC, and some DAW-related kexts. They weren't removed at the same timer, meaning i had a series of kernel panics until cleaning all the garbage, and that wasn't fun at all. But in the end, the system started up just fine. I didn't have to go through the account creation process, which i had already done when the thumb drive installation was created, and only had to set the Dock, Finder and System Preferences the way i'm accustomed to (yes, i use them the same in all my hacks and Macs, and it has the additional advantage of enabling me to make an unbiased analysis of the interface). The first thing i noticed was the boot time. Slow, painfully slow. And the system froze for 10-15 minutes when the desktop arrived in the first boot. Let indexing run and repair permissions with disk utility done away with the boot freeze, but the boot time remains slow - something surely related to an incapacity to have the caches rebuilt properly. The first upside i notice was the independent menu bars - really cool. They became highlighted/opaque according to the monitor your using in a given moment, a good way to not to get lost. In the System Preferences, i realized Spaces and Exposé were back - great news for the Snow Leopard homesick, but a bit worrying for me, since Mission Control in the Lion/Mountain Lion way as a key factor in my productivity. But i realized that despite the name and the preference pane, all worked just like before so i felt a bit of relief - i probably woudn't hate 10.9! Besides some icon changes, all panes seemed the same, and some previously installed Snow Leopard panes were there, fully functional (except for MobileMe, of course). A new app in the Dock - Apple Maps, very nice! - but i din't really explore it, as well as i din't have time to investigate changes in most of the revisited core apps. Safari has a new start screen but seems to work just the same up to now. Messages, iCloud, App Store - everything works as it should, and i cannot test FaceTime because i don't have a compatible WebCam. The great thing, and that deserves its own paragraph: Apple heard my prayers and added tab browsing and full screen windows to the Finder. I used to whine from time to time about it, so i officially i'm in love with Finder! Let's see how long the honeymoon will last. Many of my previously installed third part apps seems to work fine - i didn't have the time to test all of them - but some, like Bioshock, are absolutely unusable. The graphics performance, overall, is kind of glitchy, and even some package installers will have unusual behavior when running. That may be because of the beta drivers, but also because of my DSDT-injected three card setup - the HD4000 (primary), the 9800GT and the G210. on the bright side, my legacy PCI hardware works just fine with their oldie goldie drivers. Having to abandon them wouldn't have been a deal breaker, but being able to use them is really amazing, given the age of the drivers. Hope they survive to the final version. Another upside is that my old Ralink R070 kind of works (for a while, until it crashes taking the whole system with it) better than ever before: with 10.6 and 10.7 it would take an eternity to register a working IP, and with 10.8 it wouldn't work at all, despite Ralink's claims of a fully functional Mountain Lion driver. This 10.8 driver is what enables it to be used with Mavericks. All in all, this beta system left a strongly positive overall impression on me. If it wasn't so buggy and if i had tested all my crucial apps to a working condition - which i'll be busy doing the next few nights of insomnia - i'd switch to it as my main OS without any regrets. Anyway, i'll keep posting in this thread about my times with 10.9, so if you have a similar hardware and are wary to test it yourself, stay tuned. All the best! P.S.: Well, my crucial DAWs and Multimedia suites work as fine as with Mountain Lion. That's really a great start! 1 Link to comment Share on other sites More sharing options...
theconnactic Posted June 12, 2013 Author Share Posted June 12, 2013 P.P.S. - my complete specs: Gigabyte H77-DS3H (Intel 7-series chipset, 4 USB 2.0 and 2 USB 3.0 ports); I5-3570K @3,4 (this motherboard allows very limited OC, so i opted for none); Intel HD 4000 + Geforce 9800GT + Geforce G210 (all working, only the HD4000 has HDMI audio enabled, and the HDMI out from the 9800GT won't work on OSX; the Intel HD is the primary, all injected via DSDT as of this topic: http://www.insanelymac.com/forum/topic/286474-about-using-discrete-and-integrated-graphics-at-the-same-time/); Soudblaster Live! 5.1 (using KX Drivers, no MIDI and no inputs, outputs working but without controls) and M-Audio Audiophile 2496 (using Envy 24 64-bit drivers, all ports but MIDI working, controls only for output); ALC887 (working with Mountain Lion patched HDA); Optiarc DVR R/W (works OOB, DVDPlayer.app not tested yet); Ralink RT2070 (works fine but its drivers are quite unstable). 1 Link to comment Share on other sites More sharing options...
FrDakota Posted June 13, 2013 Share Posted June 13, 2013 Hi! I have the same motherboard and decided to test Mavericks following this thread. I had the same problem for my first start, very slow start and not even reaching the desktop. But in fact I forgot to create the Extra folder and put in it the smbios.plist and org.chamelon.Boot.plist from my actual 10.8.3, after I did that the system started correctly. I had to put the Atheros drivers for my network chip and I got the surprise to see that my Asus GeForce 550Ti was natively handled (with wrong ram capacity) no need to patch. 1 Link to comment Share on other sites More sharing options...
theconnactic Posted June 13, 2013 Author Share Posted June 13, 2013 Great to know! Until now, the system is running quite stable, as long as i don't plug the Ralink USB wi-fi adapter. The computer is on since yesterday, Sleep/Wake work oob with my DSDT, and i already installed all my main software, so it's being quite my main machine for serious work - it's risky to do so with a beta OS, but it's perfectly doable when you have a rock-solid installation ready to take over if anything bad happens - and i must tell it's doing really great. All the best! P.S.: a little, almost insignificant hassle: does someone know how can i enable access for assistive devices in Maverick DP1, since there appears to be no such an option in the accessibility pane, and simply copying the AcessibilityAPIEnabled file from Mountain Lion to Maverick's /private/var/db/ didn't help. Thank you. Link to comment Share on other sites More sharing options...
theconnactic Posted June 14, 2013 Author Share Posted June 14, 2013 Link to comment Share on other sites More sharing options...
theconnactic Posted June 16, 2013 Author Share Posted June 16, 2013 Yes, no reboot on wake (i use Chameleon instead of Clover though) and yes, it does - but the correct value should be 512 MB, right? All the best! Link to comment Share on other sites More sharing options...
theconnactic Posted June 16, 2013 Author Share Posted June 16, 2013 Great to know it's also working for you! Link to comment Share on other sites More sharing options...
pepote97 Posted November 25, 2013 Share Posted November 25, 2013 wow theconnactic, 11659 its too high, i only get 11060 with similar configuration ¡¡¡ congratulations ¡¡¡¡¡ Link to comment Share on other sites More sharing options...
Recommended Posts