Jump to content

The Great Gatsby

  • Content Count

  • Donations

  • Joined

  • Last visited

About The Great Gatsby

  • Rank
  • Birthday 06/29/1944

Contact Methods

  • Website URL

Profile Information

  • Location:
  • Gender
    Not Telling
  1. It's more than four years now since I've opened this thread, but since the problem still exists - albeit nowadays under OS X 10.9.2 Mavericks - I thought I could revive this topic: ? ? While this indeed deactivates BIOS error messages getting displayed, it does not alter the fact that I'm being stuck without keyboard input on Chameleon's drive selection. I really need to unplug the USB keyboard from the USB port and reattach it to have keyboard input working again after a reboot initiated from OS X.
  2. I can't see that anything has been done to this text - the fifth bold title ("Fake dissection / Dissassembling of EFiX made by Asere-BLN (XXX, City, Country)") still quotes his entire real name. Please remove that.
  3. Please remove AsereBLN's real name from your quote - I don't think it should be spread further without his explicit consent. Thank you.
  4. I assume the original post had an attachment with the icon as a file? Seems it got lost on the merge with kexts.com. Could you bring it back, too? - Thanks!
  5. Yes, indeed, please look for a fix. I need to fix sound in my Gigabyte GA-EP45-DS3R DSDT and I need the corresponding file from the now missing attachments really badly.
  6. Could you approve mine as well? I wrote a note about the correct smcpuvalue for Intel Core Duos in the thread about AsereBLN's booter, but they're apparently in the moderation queue, perhaps because I used a few URLs to document my sources ... Thanks a lot.
  7. Would it be possible to add support for detecting Intel Core Duos? The boot loader currently only recognizes Core 2 Duo, Core 2 Quad and Core i7 processors correctly and assumes unkown CPUs to be Core 2 Duos. This can be fixed by inserting the correct SMcputype value into smbios.plist. Apple themselves have used Core Duos at least in the first MacBook and MacBook Pro generations. Here are the correct values: Intel Core Duo: 513 - 0x201 - 0x0102 (little endian)* *Source via Sebinouse
  8. An addition to AsereBLN's blog post on CPU detection: My addition: The OS X CPU type (SMcputype) for Intel's Core Duo as found in the first generation of MacBooks and MacBook Pros should be: Intel Core Duo: 513 - 0x201 - 0x0201 (little endian)* *Source via Sebinouse
  9. This is a really nice icon indeed. Thanks!
  10. @ richiem: Thank you very much, I'll try these values on the weekend! By the way, did you achieve line-in/mic jacket activation on your machine with these values?
  11. Hi everybody, according to recent posts on Insanelymac, all ALC889a input and output jacks have now been made working on Gigabyte EP45-boards using LegacyHDA.kext (including line-in, mic, ...!): http://www.insanelymac.com/forum/index.php?showtopic=140941&st=700# Is anybody here able to integrate this into our current DSDTs available for download? I tried, but unfortunately, iasl returned a few errors and wouldn't compile my modified DSDT ... Thanks for your help!
  12. A few more words on this: I've tried to find an alternative solution to the 'dummy partition'-method. In my view, the most promising attempt was defining how to handle specific partitions in /etc/fstab. Apple's man page on fstab is quite detailed and Mac OS X Hints has published a few helpful notes on this, too. So writing something like /dev/disk0s3 none ext4 ro,noauto into /etc/fstab seemed to be worth a try to me. Unfortunately, this method won't work for two reasons, at least as far as I can see: a) Partitions with unrecognized file systems do not have an UUID for Mac OS X, so it is impossible to address them in /etc/fstab. And writing '/dev/diskxsy'-lines into fstab as suggested above does not work. Even if it would, you still would have to deal with the problem that Mac OS X establishes 'x' and 'y' at boot time and may change them every now and then, so you never could be sure which partition you're actually pointing to. The fs_vfstype - see Apple's man page above - cannot be blank, but has to be defined by a known file system. An entry like ext4 does not work. So again, Mac OS X has to be able to at least recognise the file system to be told not to mount it consecutively. This is really annoying. Even on real Macs, with today's Terrabyte-hard disks there must be people using partition schemes containing other than the few file systems known to Mac OS X. And I can't imagine these customers appreciate their OS to propose them to wipe out the data on their external hard drive by 'initializing the device' every time they plug it in, only because it happens to also contain an ext3 partition ... Any further ideas?
  13. For obvious reason (... read my signature ): My I ask if you also did that on your other system, the one with the Palit card?
  14. I would assume this is the reason. I remember having the same problem on an MBR-formatted hard disk with Chameleon when Grub was not installed to the specific partition (/dev/sd[letter][number]), but only to /dev/sd[letter].
  15. This doesn't however activate the mic-in jacket, I assume? :confused:
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.