Jump to content

Search the Community: Showing results for tags 'about this mac'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 7 results

  1. Successfully installed iATKOS L2 OS X Lion 10.7.2 on my computer. So far, it has been working fine. When I open Apple menu > About This Mac > Additional Info, my computer appears as Mac Pro. Yes, there's nothing wrong with it. But I would like to see iMac instead of Mac Pro, as my computer is an all-in-one machine. As of what I know, I am supposed to edit SMBIOS plist to do that. Is it correct? If so, what iMac model is appropriate to my machine? Or should I just leave it as-is(Mac Pro)? Here are the full specs: Processor: Intel P6200 @ 2.13GHz Chipset: Intel HM57 Graphics: Intel HD Graphics (Arrandale) Sound: Realtek HD Audio (ALC272) LAN: Realtek RTL8168/8111 WLAN: Atheros AR9285
  2. If you get the Unknown CPU in About This Mac you can use the following settings according to your processor. Use IORegistry Explorer or IOJones to check the current "cpu-type" value for your processors. You can find the value by clicking the CPU0@0 like shown in the picture below: I have an Intel Core i7 6700K so the value is 0507. For Core i3 Series you can set the CPU type to: 0x0309 = Core i3 For Core i5 series you can set the CPU type to: 0x0407 0x0601 or 0x0605 (to be more accurate) = Intel Core i5 For Core i7 Series you can set the CPU type to: 0x0701 or 0x0705 (to be more accurate) = Intel Core i7 You can also try 0x0507 if the values above didn't work. For Xeon Series you can set the CPU type to: 0x0505 Dual-Core Intel Xeon 0x0510 Quad-Core Intel Xeon 0x05A5 Quad-Core Intel Xeon
  3. Hi, When I try to open About This Mac from the apple menu nothing happens, no windows open. When I try to open it, console reports this: 12/05/2014 18:27:01.724 loginwindow[70]: *** NSRunStorage, _NSBlockNumberForIndex(): index (42) beyond array bounds (42) 12/05/2014 18:27:01.727 loginwindow[70]: ( 0 CoreFoundation 0x00007fff95f3325c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff8c43ce75 objc_exception_throw + 43 2 CoreFoundation 0x00007fff95f3310c +[NSException raise:format:] + 204 3 AppKit 0x00007fff8cbc48e7 _NSBlockNumberForIndex + 85 4 AppKit 0x00007fff8cbc7541 -[NSLayoutManager textContainerForGlyphAtIndex:effectiveRange:] + 274 5 loginwindow 0x000000010582d564 loginwindow + 398692 6 loginwindow 0x00000001057f0c83 loginwindow + 150659 7 loginwindow 0x00000001057efc00 loginwindow + 146432 8 loginwindow 0x00000001057e44eb loginwindow + 99563 9 AE 0x00007fff9495ee1f _Z20aeDispatchAppleEventPK6AEDescPS_jPh + 381 10 AE 0x00007fff9495ec32 _ZL25dispatchEventAndSendReplyPK6AEDescPS_ + 31 11 AE 0x00007fff9495eb36 aeProcessAppleEvent + 315 12 HIToolbox 0x00007fff93fa2161 AEProcessAppleEvent + 56 13 AppKit 0x00007fff8caf3246 _DPSNextEvent + 1026 14 AppKit 0x00007fff8caf2a2b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122 15 AppKit 0x00007fff8cae6b2c -[NSApplication run] + 553 16 loginwindow 0x00000001057d1b32 loginwindow + 23346 17 libdyld.dylib 0x00007fff88fc15fd start + 1 18 ??? 0x0000000000000002 0x0 + 2 ) I have done some minor modification to the SMBios using Clover Configurator but I do not think this is the problem. I am using clover bootloader r2636 and the machine works perfectly with no other issues with the most recent OS X update (10.9.2)
  4. Hello guys, been a while since my last post in here. I came up with a thought while trying to make my HDMI port on my MSI 6770 1gb while at the same keeping ATI Radeon HD 6770 1024 MB in the about this mac window. Skip to the end if you are in a hurry I found that if I inject my "@0-2" framebuffer names as "Hoolock" in my DSDT per Rampagedev's instruction in http://www.insanelymac.com/forum/topic/282687-radeon-hd-6770-full-qeci-mlmavericksyosemite/page-2?do=findComment&comment=1902721, my card was recognised as 6770 and VGA and DVI worked, but the HDMI didn't. If, on the other hand I, don't fiddle with them in my DSDT, DVI and HDMI works(video only) (i really forgot to test VGA at that point) but in ioreg, the chosen framebuffer would be "ATI_Framebuffer" or something like that. At the same time, in "About this Mac" the card was recognised as ATI Radeon HD 5000 1024 MB. Hold my (that) though. After bumping in this and this tutorials, again by Rampagedev, whom I respect for this guy is tremendously btw, I noticed that Hoolock that it has wrong port types. In detail: Personality: Hoolock ConnectorInfo count in decimal: 3 Disk offset in decimal 166176 0000000 00 04 00 00 04 06 00 00 00 01 00 00 21 03 05 01 // 0x400 means Display Port 0000010 00 04 00 00 04 06 00 00 00 01 00 00 11 02 04 02 // 0x400 means Display Port 0000020 04 00 00 00 14 02 00 00 00 01 00 00 02 04 01 03 // 0x4 means DVI-Dual Link port 0000030 Connector Type LVDS 0x00000002 = 02 00 00 00 Note: Laptop Monitor Connector Type DVIDL 0x00000004 = 04 00 00 00 Note: Dual Link DVI Connector Type VGA 0x00000010 = 10 00 00 00 Connector Type S-V 0x00000080 = 08 00 00 00 Connector Type DP 0x00000400 = 00 04 00 00 Connector Type HDMI 0x00000800 = 00 08 00 00 Connector Type DVISL 0×00000200 = 00 02 00 00 Note: Single Link DVI On the contrary, Vervet had 2 of my connector types correct: Personality: Vervet ConnectorInfo count in decimal: 4 Disk offset in decimal 166224 0000000 00 04 00 00 00 04 00 00 00 71 00 00 12 04 04 02 // 0x400 means Display Port 0000010 04 00 00 00 14 00 00 00 00 71 00 00 01 12 01 04 // 0x4 means DVI-Dual Link port 0000020 00 02 00 00 14 00 00 00 00 71 00 00 00 00 06 03 // 0x200 means DVI-Single Link port 0000030 00 08 00 00 00 02 00 00 00 71 00 00 22 05 05 01 // 0x800 means HDMI 0000040 So I thought hey what the hell, I'll try it ,and to my blame-my-genius type of shock, it finally has worked.Video worked through HDMI and my card had the so crazily desired correct/corrected name. Gonna update the post after I used these chaned Vervet framebuffer and in order to make the 3rd port,by swapping the Single Link DVI, with the working VGA from Baboon. This is how it looks: 0000000 10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 // ex-Displayport, now VGA from Baboon Framebuffer 0000010 00 08 00 00 00 02 00 00 00 71 00 00 22 05 05 01 // ex-DVI-Dual Link, now HDMI 0000020 04 00 00 00 14 00 00 00 00 71 00 00 01 12 01 04 // ex-Single Link, now 0000030 00 04 00 00 00 04 00 00 00 71 00 00 12 04 04 02 // ex-HDMI type, now Display Port and the reason for using Display Port, 0000040 // was to preserve the framebuffer's port symmetry,weight. edit 1: Didn't do much.. VGA got recognized only if I use an HDMI to DVI adapter and a VGA cable but I didn't got the right resolution on that screen. Still a bit better than before. Im gonna continue tomorrow, I had an all-nighter and it's 8 am already.. edit 2: (The Last Edit) Curtesy of Antien's post here,behold a patched Vervet FrameBuffer that HDMI and DVI works perfectly. I added VGA from Baboon which I know is working and voilà, fully working DVI+HDMI(audio too)+VGA ports on MSI 6770 1Gb. I hope this will help present and future, 6770 owners. 0000000 10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 // VGA from Baboon 0000010 04 00 00 00 14 02 00 00 00 01 00 00 11 02 03 03 // DVI-Dual Link from Antien 0000020 00 02 00 00 04 02 00 00 00 01 00 00 00 10 04 03 // Display Port from Antien 0000030 00 08 00 00 04 02 00 00 00 01 00 00 22 05 02 04 // HDMI from Antien 0000040
  5. Hi, I would like to ask for little help. In "about this Mac" my processor is not correctly recognized and is showing as an Intel Core i7 instead of Xeon E3... My build is using latest Clover, everything is working, sleep etc. Smbios I used iMac14,2 because it is the closest Haswell model to mine. Can anyone please help me to correct this issue? Thanks a lot.
  6. Hello, folks! My main hackintosh has been working like a charm for longer that I could remember. Then it crashed badly after a power surge last week, and apparently died. After testing individually each and every component, I found that either the motherboard was burned, or it's firmware became corrupted. Hoping for the latter, I did a CMOS reset and, after an seemingly infinite boot loop (in itself a good sign, since at least the computer was turning on), I was able to access the BIOS and enter my settings. Props for Gigabyte's Dual BIOS system! The following day, I decided to give my computer a newer case, one with better ventilation, size, looks and front audio and USB3 connections. After my hardware was installed on its new enclosure, I noticed that About This Mac reported my hackintosh as an "iMac 27'', mid 2011", despite my iMac 13,1 smBIOS, which was loaded and correctly reported as such in the system report. And, after HWMonitor detected higher-than-usual CPU temps, I ran MSRDumper and found I was getting only 16 and 34 and the turbo 36, 37 and 38 multipliers as p-states. To make things worse, today I realized my computer wasn't waking up properly - it would wake, but to a black screen, forcing me to a hard reboot. Console.app logs were of no help at all. I'm using the same ACPI tables, Chameleon settings and smBIOS I've been using for quite a while without any issues, so I suspect that the USB3 front header (which doesn't work) or the backup BIOS the motherboard loaded when the original one crashed might be the cause(s) of my woes. How can I isolate the culprit and, if possible, how can I solve this - I'm lost here. Any help with getting the front USB3 (which uses the motherboard header) to work like the rear USB3 ports do (with DSDT edits, because I never needed kexts for the rear ones, using this method instead: http://www.insanelymac.com/forum/topic/287901-how-to-get-intel-7-series-usb-30-fully-working-step-by-step-guide/page-4?hl=%2Bgiacomoleopardo&do=findComment&comment=1992234 ) would also be greatly appreciated. I'm on 10.9.2 by the way. All the best!
  7. Hi guys, I need help to change About This Mac ram memory size and possible processor type, I'm using chameleon enoch 2773. About this mac shows: Processor: 2.5 GHz Quad-Core Intel Xeon - to be Intel Core2 Quad Q9300 Memory: 8.38 GB 1066 MHz DDR2 SDRAM - to be 8GB Thanks
×