Thanks Dan. On 15/06/2010, at 10:34 AM, Dan Shoop wrote:
>>> Note, as I said, this is not purely a driver issue (not that we have real >>> drivers in OS X anyway) and 10.6.4 may not resolve this, you may need to >>> wait for the next bootable release, not just an update. >> >> Could you elaborate on this please? > > We don't have drivers like they do on Windows or Linux, b/c of the way IOKit > operates. You don't need I/O drivers to support a device. I understand that (or at least I believe I do). > As I said you may need a more recent kernel build, machine profiles, kexts, > ... It's not going to be solely an issue of "drivers". > >> Why it is so? > > Um... Because. But I don't see how 10.6.4 may NO resolve the problem - I'm pretty sure it would be a more recent kernel build, machine profiles, kexts - as you alluded to. How could 10.6.4 NOT resolve this? What do you mean by a "bootable release"? Surely 10.6.4 will be bootable on all released Macs? >> Any idea why an install from the restore DVD over the previous version left >> me with horizontal black (and then dark blue) and white lines. > > I could speculate. You had kexts clobber each other, the hw was only > partially supported by the overlays, basically since there should have been > no expectation for that to work you were lucky to see whatever artifacts. > >> The boot got much further than before, the login screen even blinked on the >> display for a second before the thick lines appeared. > > Meaning... nothing. Meaning ... it got a lot further than the previous attempt (using 10.6.3 from earlier MBP). I was surprised that the login screen even appeared - it would seem that most of he graphics was working ... >>> Your best options in order are: >>> >>> (1) Clean install from the Installer CD/DVD, reinstall any third party app, >>> copy over your $HOME and data. >>> >>> (2) Clean install from the Installer, as root (preferably in SUM, logged in >>> via ssh or the Terminal) copy over any missing applications (which should >>> be self-contained .apps or should have supporting code in /Library), and >>> everything in /Library. You shouldn't have anything in /System that doesn't >>> belong to Apple. Then copy over your $HOME and data. >> >> Both much messier than I'd hoped for (but, of course, that's not your fault). > > > You're woolly thinking, not mine. You aren't accounting for how the OS > operates from the kernel up properly. You're right there, woolly thinking and all, I'm just trying to learn more about this stuff. Not enough time to keep on top of it all. Cheers, Ashley. -- Ashley Aitken Perth, Western Australia mrhatken at mac dot com Skype Name: MrHatken (GMT + 8 Hours!) _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
