Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About quaestor

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    North America
  • Interests
    In no particular order:<br />Photography (digital: Nikon D90), Electronic music (making and listening), Gaming (all kinds, as long as it's digital :) ), F1 (go Jensen!), Radiohead, Anime (the good stuff, particularly currently running), Character Animation (mostly 3D), Film (cinema, not photography)
  1. If I understand you correctly, I think what you should do is start a new thread (and consider making an entry in the Hardware Compatibility List, like this one).
  2. [edit update] On Vista SP2, Windows 7 and Server 2008 R2, do the following in the Registry: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation] "RealTimeIsUniversal"=dword:00000001 If that looks like chicken scratch, google for a beginner's guide to editing the Windows Registry; not to be rude, but I don't do Windows support - queries will be forwarded to /dev/null I wish I could remember where I found this fix and how to actually do it, but I can tell you that you have to change a Windows Registry entry to tell Windows to use UTC instead of local time (Windows will still compensate properly and display the local time). Google
  3. Man, my brains just don't seem to work anymore; or else this board is really hard to configure, 'cause I'm still not getting notifications... Guess I'll have to check in every day Some musings: FWIW - I'm almost certain that the LED embedded in the lid "glows" (slowly dims and brightens) when the laptop is sleeping under Windows 7. Potentially annoying (apparently 'very annoying' for some people ), but expected behavior. Not to say that it can't be stopped in some way... FWIW - I've had to do quite a bit of fiddling with both this laptop (Win 7) and my P5Q3 Win 7 desktop to get sleep to happen. In both cases, I had to manually (command-line) take all the USB ports n' hubs out of the list of wake-triggering devices. I've also had the keyboard and mouse not respond after wake F1x0r wlan wpa2z plx kthx!!1! I haven't edited the "front page" in a while; I need to get around to it...
  4. Do you really mean every time you logout/login, or do you mean every time you reboot/login? If it's the latter, then something is (probably) wrong with voodoohdahelper. I don't remember off the top of my head where it should be... If it's the former, you're on your own .
  5. Just a quick update: I've tried all the "new stuff" here - Cool: Fn keys work well. New Cham hasn't broken anything . I guess C/P-state support works; I haven't tested it, and the temps seem to be about what they were before (~38c idling). New DSDT is great; mem bus speed is now correct, among other things. New PS2 driver is great; I can run 64-bit clean. Seems a little twitchy after wake. Clamshell/manual sleep (from Apple menu) work (more on sleep below). Not so cool: HDA is reset during/after sleep, so voodoohdahelper must be run to restore mixer settings. Hibernate is still broke as *&%$; the machine won't boot until the hiberfile is deleted. Fn key sleep doesn't work. Haven't tried PM "timeout" sleep. Wake from sleep works, unless the system sits for some undetermined time - on wake, display comes up as normal, but the keyboard, trackpad, and even external USB mouse are unresponsive, so a hard rest is necessary. Very uncool mostly because of the amount of time I spent on it yesterday: "Native" (Atheros) wireless. This wireless thing is weird; but first the facts (as they say in mystery stories ): AR9285 ~= AR5B95 i.e. as far as I can tell they might as well be identical. The card is labeled "AR5B95", but Windows and the published system specs say "AR9285", to wit: Windows PCI ID string: VEN_168C&DEV_002B&SUBSYS_10891A3B What does this tell us? VEN_168C - The device manufacturer (vendor). DEV_002B - Manufacturer's identification of this part (device ID). SUBSYS_10891A3B - Broken down into two parts: 1089 - "sub-device" identification; This can be lots of things - a particular model from a family of similar devices (in which case the "device ID" will often refer to a family of devices), a particular custom firmware version of a part which is otherwise identical to other part with the same "device ID", etc. There are many possibiities. 1a3b - "sub-vendor"; the company (possibly) re-branding the part, usually the manufacturer of the system as a whole. More specifically: 168c = Atheros 002a/002b (I've seen both) = AR9285/AR5B95. I don' know the relationship between DEV ID and Atheros part number; there may not be any. 1089 = unknown, but maybe related to Asus-specific firmware (shrug). 1a3b = Asus, system mfg. So, the lightbulb should have gone off for those who have been following the Atheros saga. If you could look at the Windows PCI ID for a "real" Apple Airport card (say, using Bootcamp or 'lspci') you'd (probably) see VEN_168C&DEV_002B&SUBSYS_008F106B. What does this tell us? VEN and DEV IDs are the same; Atheros 9285. Surprise. The important part is the sub-system: 008f = Airport Extreme device 106B = Apple, system mfg. wonslung is absolutely right; using Cham's DSDT "fake EFI" capability to tell OSX that the wireless card's embedded info corresponds to a real Airport card should make it work like one. With one exception. Based on my experiences with a Dual-Band Airport Extreme (the access point, not the wireless card), and pending verification by wonslung (I don't think he's specifically mentioned wireless 'n'), it looks like wireless 'n' connections don't work. I am seeing exactly the same issues that cknoblet is. I suspect that something, possibly the firmware on the card, isn't cooperating properly with the driver. I need to do a tcp dump and some other diags to look at exactly what's going on at a low level, but yesterday left me kinda burnt out . EDIT: Having written the above, I remembered something interesting from yesterday. Edited output of 'ifconfig': en0: media: autoselect (1000baseT <full-duplex>) fw0: media: autoselect <full-duplex> en1: media: <unknown subtype> 'en1' is the Atheros wireless card. Interesting.
  6. Wow, I can't believe this thread is still alive and active (and has as many views as it does!); I guess this is a popular laptop... Apologies for (seemingly) abandoning this thread; Invision is massive fail - it stopped sending me email notices of thread replies, and that's what I was relying on to keep me updated. Kudos to those who've stepped up, in the best open source fashion, to help out others, particularly Cknoblet and wonslung (also, big thanks to the guys in the G51J/Jx thread; seems like there's a lot of "cross-pollination" going on here). I'll be trying out all the new stuff posted since the last time I read this thread (July!) and updating the guide as appropriate, where 'appropriate' is defined as "works for me" .
  7. Sorry for the late reply. Good that it's working. I had to mess around a bit with that wacky Voodoo control panel to figure out which slider does what - some of them aren't so obvious; I'll take a look tonight and try to remember what I did to get the mic working. I've ended up using SteerMouse. It doesn't really fix the problem all the way, but it helps. This issue is the main reason I'm using the meklort kext vs Voodoo: the Voodoo kext (when I first did the install) was unusable; really bad tracking, cursor jumping around like a flea... The last time I tried Voodoo (after I read Ocha888's post) it didn't work at all See above for PS2. Everything I'm using is is linked to in the "kext" section of the guide. Sound works great, no complaints, except the minor annoyance that I get a quick pop of feed back when the kext loads during boot. Since the control panel and prefs loader aren't available at that point, I don't know of anything that can be done about it. The main disclaimer for me is that I'm primarily using this laptop with a USB mouse (so the trackpad flakiness isn't really a show-stopper, although if I'm on the road and don't have the mouse, I do find it annoying) and S/PDIF for sound. I don't need the mic, although I do know that it works.
  8. I've always gotten good results from downloading the Combo Updates and applying them manually. As far as anything else goes, I've never heard of Hazard and I've only ever installed/run OSX bare-metal, so I can't speak to anything involved with running it virtualized.In any case, this is a little off-topic; I'm sure there are threads out there which deal more specifically with virtualized OSX.
  9. @nfshp253: Sorry, man, I have no clue about handwriting input. I strongly suspect that without "native" trackpad support (i.e. Apple Trackpad pref pane is available and usable) the system doesn't think there's a trackpad connected and doesn't offer handwriting input. Just a guess. @Ocha888: Is there any way you can upload or attach the installers you used for PS2 and sound? I can't find a 64-bit VoodooHDA prefpane anywhere, and the latest VoodooPS2 installer from nawcom.com does not work for me at all. @Cknoblet: Interesting. I may try that out this weekend if I'm feeling particularly brave.
  10. Great, thanks, much clearer. If you're booting with "arch=i386", you are NOT booting the 64-bit kernel. You are booting the 32-bit kernel with 64-bit extensions. The following is (roughly) what you'll see in system.log when booting the 32-bit kernel (this is actually from Leopard, but SL is very similar): May 7 09:09:02 localhost kernel[0]: PAE enabled May 7 09:09:02 localhost kernel[0]: Darwin Kernel Version 9.7.0: Tue Mar 31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386 On SL booting the 64-bit kernel, the end of the second line will state "x86_64" or something very similar
  11. I don't understand what you mean by "with 10.4.0 vanilla kernel". The VoodooPS2 installer includes the kernel?! I'm a little confused; iAtkos 7 is Leopard (10.5.7). It shouldn't have any 64-bit kexts or pref panes (note to self; I see that there's a very new VoodooPS2 installer at nawcom.com... newer than the kext files there). I'm still curious as to how you got sound working. It seems as though you ran a VoodooHDA installer, and then copied files over top of that by hand. Is that the case? Also, I take it that the pref pane you mention is the HDA pref pane, not the one for PS2?
  12. So, you ran the VoodooHDA 0.2.61 installer, and then copied the files from the guide over that? I wasn't concerned with making things 64-bit clean, so I don't recall for certain, but I'm pretty sure that the 64-bit pref pane is included in the archive I linked to. And this is with the VoodooPS2 kext (not the Meklort)? Which version? Can you post a link? You are probably missing the voodoohdahelper; I don't know if it's included in the installer you mentioned or not. The link is in the guide.
  13. I'm at work right now, so I can't attach any files yet, but I'm wondering what the exact problem is. You said you're having trouble installing the kext; are you being literal, or do you mean you install the kext and sound doesn't work? If the latter, what are the symptoms? No devices in System Prefs? Devices but no sound? S/PDIF never worked for me until after the 10.6.4 update, at which point I realized I'd forgotten to take the new AppleHDA.kext out of use. I've just left it alone since then 'cause it works and hasn't caused any problems. Point being; if you deleted the AppleHDA.kext after you did the update, it may have broken sound completely. Just a theory, mind you.
  14. Can take a whack at it, though I've never tried it before.