Bungo Posted January 29, 2014 Share Posted January 29, 2014 Where should I check for spaces? In smbios.plist? Because I don't have (and never had but I got the "not specified") any SMcpupartnumber line there. Should I make one there? Also how can I get my original smbios? I can't find any app for Windows to do an smbios dump properly. edit: I just saw Gringo's #2026 post, I'll put that line into smbios.plist and report back. edit 2: adding SMcpupartnumber into smbios.plist fixed the empty part number line problem. Once again, some vendors (e.g I've seen in Gigabyte's smbios) fill some entries up with space chars (" "). To be sure what exactly contain your smbios (original and patched) you should to use dmidecode command. You can do it on your already installed osx (method I described few posts before). Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted January 29, 2014 Share Posted January 29, 2014 Here bdmesg_2360t1.txt dmesg_2360t1.txt Everything looks fine. Link to comment Share on other sites More sharing options...
ErmaC Posted January 29, 2014 Author Share Posted January 29, 2014 Everything looks ... SMBIOS orig was = f04c0 SMBIOS new is = 2673000 efi_inject_get_devprop_string NULL trying stringdata Read HFS+ file: [hd(0,2)/Extra/DSDT.aml] 35886 bytes. any device injected from o.c.B.p? Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted January 29, 2014 Share Posted January 29, 2014 No, nothing. I don't know why it does that. That message has been there as far back as I can remember. I have EthernetBuiltIn=y + GraphicsEnabler=y with SkipNvidiaGfx=y. Link to comment Share on other sites More sharing options...
nyolc8 Posted January 29, 2014 Share Posted January 29, 2014 dmidecode from ubuntu linux: dmidecode_ubuntu.txt (Bungo you right, it contains " " for many lines) Btw I have that "efi_inject_get_devprop_string NULL trying stringdata" line too in my bdmesg since I use chameleon/hackintosh. (~3 years) Link to comment Share on other sites More sharing options...
ErmaC Posted January 29, 2014 Author Share Posted January 29, 2014 The latest changes were sent to SVN. Here the Chameleon rev. 2362 -> i386_v2362.zip I would like to FIX (try) a feature no longer working since OS X Lion 10.7+ and up. The Hibernation...Last week, Slice has kindly informed me in PM, about the recent progress on hibernation with CloverSo first thx go to him and his Clover team. Next I need to know if in actual Chameleon the HIBERNATION feature still working for SNOW LEOPARD…???so Snow user pls report... I have absolutely no experience and knowledge with OS X Hibernation Feature so I hope with your help... Some info I collected from the issue side:http://forge.voodooprojects.org/p/chameleon/issues/278/http://forge.voodooprojects.org/p/chameleon/issues/133/ ErmaC 2 Link to comment Share on other sites More sharing options...
Bungo Posted January 30, 2014 Share Posted January 30, 2014 dmidecode from ubuntu linux: dmidecode_ubuntu.txt (Bungo you right, it contains " " for many lines) OK. BTW. Easiest IMHO way to get and decode an smbios I described before, your dump doesn't contain raw headers data (may be some option swictch?) # dmidecode 2.11b Handle 0x0000, DMI type 0, 24 bytes 0000: 00 18 00 00 01 02 00 f0 03 1f 80 98 89 3f 05 00 <=== 0010: 00 00 03 05 00 01 ff ff <=== BIOS Information Vendor: Apple Inc. Version: MBP61.88Z.0057.B0F.1112091028 Release Date: 12/09/11 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 2048 kB Characteristics: ... Btw I have that "efi_inject_get_devprop_string NULL trying stringdata" line too in my bdmesg since I use chameleon/hackintosh. (~3 years) I've never got hibernation working Link to comment Share on other sites More sharing options...
nyolc8 Posted January 30, 2014 Share Posted January 30, 2014 Original SMBIOS got how Bungo told: # dmidecode 2.11b Handle 0x0000, DMI type 0, 24 bytes 0000: 00 18 00 00 01 02 00 e0 03 07 80 9e c9 7f 00 00 0010: 00 00 33 05 ff ff ff ff BIOS Information Vendor: Award Software International, Inc. Version: F6 Release Date: 06/05/2008 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 512 kB Characteristics: PCI is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/360 kB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Targeted content distribution is supported Handle 0x0001, DMI type 1, 27 bytes 0000: 01 1b 01 00 01 02 03 04 00 00 00 00 00 00 00 00 0010: 00 00 00 1f d0 09 7f 8a 06 05 06 System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: G31M-S2L Version: Serial Number: UUID: 00000000-0000-0000-0000-00***00***** Wake-up Type: Power Switch SKU Number: Family: Handle 0x0002, DMI type 2, 8 bytes 0000: 02 08 02 00 01 02 03 04 Base Board Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: G31M-S2L Version: Serial Number: Handle 0x0003, DMI type 3, 17 bytes 0000: 03 11 03 00 01 03 02 03 04 02 02 02 02 00 00 00 0010: 00 Chassis Information Manufacturer: Gigabyte Technology Co., Ltd. Type: Desktop Lock: Not Present Version: Serial Number: Asset Tag: Boot-up State: Unknown Power Supply State: Unknown Thermal State: Unknown Security Status: Unknown OEM Information: 0x00000000 Handle 0x0004, DMI type 4, 35 bytes 0000: 04 23 04 00 01 03 01 02 fb 06 00 00 ff fb eb bf 0010: 03 8e 8c 01 a0 0f 60 0c 41 0f 08 00 09 00 ff ff 0020: 04 05 06 Processor Information Socket Designation: Socket 775 Type: Central Processor Family: Other Manufacturer: Intel ID: FB 06 00 00 FF FB EB BF Signature: Type 0, Family 6, Model 15, Stepping 11 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM)2 Duo CPU Voltage: 1.4 V External Clock: 396 MHz Max Speed: 4000 MHz Current Speed: 3168 MHz Status: Populated, Enabled Upgrade: Socket 478 L1 Cache Handle: 0x0008 L2 Cache Handle: 0x0009 L3 Cache Handle: No L3 Cache Serial Number: Asset Tag: Part Number: Handle 0x0005, DMI type 5, 20 bytes 0000: 05 14 05 00 04 04 03 03 0a 01 00 01 00 01 02 06 0010: 00 07 00 04 Memory Controller Information Error Detecting Method: 8-bit Parity Error Correcting Capabilities: None Supported Interleave: One-way Interleave Current Interleave: One-way Interleave Maximum Memory Module Size: 1024 MB Maximum Total Memory Size: 2048 MB Supported Speeds: Other Supported Memory Types: Other Memory Module Voltage: 5.0 V Associated Memory Slots: 2 0x0006 0x0007 Enabled Error Correcting Capabilities: None Handle 0x0006, DMI type 6, 12 bytes 0000: 06 0c 06 00 01 1f 00 01 00 0b 0b 00 Memory Module Information Socket Designation: A0 Bank Connections: 1 Current Speed: Unknown Type: Other Installed Size: 2048 MB (Single-bank Connection) Enabled Size: 2048 MB (Single-bank Connection) Error Status: OK Handle 0x0007, DMI type 6, 12 bytes 0000: 06 0c 07 00 01 2f 00 01 00 0b 0b 00 Memory Module Information Socket Designation: A1 Bank Connections: 2 Current Speed: Unknown Type: Other Installed Size: 2048 MB (Single-bank Connection) Enabled Size: 2048 MB (Single-bank Connection) Error Status: OK Handle 0x0008, DMI type 7, 19 bytes 0000: 07 13 08 00 01 80 01 40 00 40 00 20 00 20 00 00 0010: 02 02 02 Cache Information Socket Designation: Internal Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 64 kB Maximum Size: 64 kB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x0009, DMI type 7, 19 bytes 0000: 07 13 09 00 01 81 01 00 08 00 10 20 00 20 00 00 0010: 02 02 02 Cache Information Socket Designation: External Cache Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: Internal Installed Size: 4096 kB Maximum Size: 2048 kB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x000A, DMI type 8, 9 bytes 0000: 08 09 0a 00 01 16 02 00 ff Port Connector Information Internal Reference Designator: PRIMARY IDE Internal Connector Type: On Board IDE External Reference Designator: External Connector Type: None Port Type: Other Handle 0x000B, DMI type 8, 9 bytes 0000: 08 09 0b 00 01 16 02 00 ff Port Connector Information Internal Reference Designator: SECONDARY IDE Internal Connector Type: On Board IDE External Reference Designator: External Connector Type: None Port Type: Other Handle 0x000C, DMI type 8, 9 bytes 0000: 08 09 0c 00 01 17 02 00 a1 Port Connector Information Internal Reference Designator: FDD Internal Connector Type: On Board Floppy External Reference Designator: External Connector Type: None Port Type: 8251 FIFO Compatible Handle 0x000D, DMI type 8, 9 bytes 0000: 08 09 0d 00 01 18 02 08 07 Port Connector Information Internal Reference Designator: COM1 Internal Connector Type: 9 Pin Dual Inline (pin 10 cut) External Reference Designator: External Connector Type: DB-9 male Port Type: Serial Port 16450 Compatible Handle 0x000E, DMI type 8, 9 bytes 0000: 08 09 0e 00 01 18 02 08 07 Port Connector Information Internal Reference Designator: COM2 Internal Connector Type: 9 Pin Dual Inline (pin 10 cut) External Reference Designator: External Connector Type: DB-9 male Port Type: Serial Port 16450 Compatible Handle 0x000F, DMI type 8, 9 bytes 0000: 08 09 0f 00 01 05 02 05 05 Port Connector Information Internal Reference Designator: LPT1 Internal Connector Type: DB-25 female External Reference Designator: External Connector Type: DB-25 female Port Type: Parallel Port ECP/EPP Handle 0x0010, DMI type 8, 9 bytes 0000: 08 09 10 00 01 ff 02 0f 0d Port Connector Information Internal Reference Designator: Keyboard Internal Connector Type: Other External Reference Designator: External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x0011, DMI type 8, 9 bytes 0000: 08 09 11 00 01 0f 02 0f 0e Port Connector Information Internal Reference Designator: PS/2 Mouse Internal Connector Type: PS/2 External Reference Designator: Detected External Connector Type: PS/2 Port Type: Mouse Port Handle 0x0012, DMI type 8, 9 bytes 0000: 08 09 12 00 01 00 02 12 10 Port Connector Information Internal Reference Designator: USB Internal Connector Type: None External Reference Designator: External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0013, DMI type 8, 9 bytes 0000: 08 09 13 00 01 00 02 12 10 Port Connector Information Internal Reference Designator: USB Internal Connector Type: None External Reference Designator: External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0014, DMI type 9, 13 bytes 0000: 09 0d 14 00 01 06 05 03 04 00 00 06 05 System Slot Information Designation: PCI Type: 32-bit PCI Current Usage: Available Length: Long ID: 0 Characteristics: 5.0 V is provided 3.3 V is provided PME signal is supported SMBus signal is supported Handle 0x0015, DMI type 9, 13 bytes 0000: 09 0d 15 00 01 06 05 03 04 01 00 06 05 System Slot Information Designation: PCI Type: 32-bit PCI Current Usage: Available Length: Long ID: 1 Characteristics: 5.0 V is provided 3.3 V is provided PME signal is supported SMBus signal is supported Handle 0x0016, DMI type 9, 13 bytes 0000: 09 0d 16 00 01 06 05 03 04 00 00 06 05 System Slot Information Designation: PCI Type: 32-bit PCI Current Usage: Available Length: Long ID: 0 Characteristics: 5.0 V is provided 3.3 V is provided PME signal is supported SMBus signal is supported Handle 0x0017, DMI type 9, 13 bytes 0000: 09 0d 17 00 01 06 05 03 04 00 00 06 05 System Slot Information Designation: PCI Type: 32-bit PCI Current Usage: Available Length: Long ID: 0 Characteristics: 5.0 V is provided 3.3 V is provided PME signal is supported SMBus signal is supported Handle 0x0018, DMI type 13, 22 bytes 0000: 0d 16 18 00 03 00 00 00 00 00 00 00 00 00 00 00 0010: 00 00 00 00 00 01 BIOS Language Information Installable Languages: 3 n|US|iso8859-1 n|US|iso8859-1 r|CA|iso8859-1 Currently Installed Language: n|US|iso8859-1 Handle 0x0019, DMI type 16, 15 bytes 0000: 10 0f 19 00 03 03 03 00 00 20 00 fe ff 02 00 Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 2 GB Error Information Handle: Not Provided Number Of Devices: 2 Handle 0x001A, DMI type 17, 27 bytes 0000: 11 1b 1a 00 19 00 fe ff 40 00 40 00 00 08 09 00 0010: 01 02 02 00 00 20 03 03 04 05 06 Memory Device Array Handle: 0x0019 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: DIMM Set: None Locator: A0 Bank Locator: Bank0/1 Type: Unknown Type Detail: None Speed: 800 MHz (1.2 ns) Manufacturer: Serial Number: Asset Tag: Part Number: Handle 0x001B, DMI type 17, 27 bytes 0000: 11 1b 1b 00 19 00 fe ff 40 00 40 00 00 08 09 00 0010: 01 02 02 00 00 20 03 03 04 05 06 Memory Device Array Handle: 0x0019 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: DIMM Set: None Locator: A1 Bank Locator: Bank2/3 Type: Unknown Type Detail: None Speed: 800 MHz (1.2 ns) Manufacturer: Serial Number: Asset Tag: Part Number: Handle 0x001C, DMI type 19, 15 bytes 0000: 13 0f 1c 00 00 00 00 00 ff ff 3f 00 19 00 01 Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000FFFFFFFF Range Size: 4 GB Physical Array Handle: 0x0019 Partition Width: 1 Handle 0x001D, DMI type 20, 19 bytes 0000: 14 13 1d 00 00 00 00 00 ff ff 1f 00 1a 00 1c 00 0010: 01 00 00 Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0007FFFFFFF Range Size: 2 GB Physical Device Handle: 0x001A Memory Array Mapped Address Handle: 0x001C Partition Row Position: 1 Handle 0x001E, DMI type 20, 19 bytes 0000: 14 13 1e 00 00 00 20 00 ff ff 3f 00 1b 00 1c 00 0010: 01 00 00 Memory Device Mapped Address Starting Address: 0x00080000000 Ending Address: 0x000FFFFFFFF Range Size: 2 GB Physical Device Handle: 0x001B Memory Array Mapped Address Handle: 0x001C Partition Row Position: 1 Handle 0x001F, DMI type 32, 11 bytes 0000: 20 0b 1f 00 00 00 00 00 00 00 00 System Boot Information Status: No errors detected Handle 0x0020, DMI type 64, 13 bytes 0000: 40 0d 20 00 00 1f d0 09 7f 8a ff ff ff Unknown Type Header and Data: 40 0D 20 00 00 1F D0 09 7F 8A FF FF FF Strings: Handle 0x0021, DMI type 127, 4 bytes 0000: 7f 04 21 00 End Of Table Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted January 30, 2014 Share Posted January 30, 2014 I had hibernation working once a long time ago, early Snow Leopard on my old P5Q-E I think. But then I had an accident, I think the hibernation data wasn't properly saved and when coming out of hibernation an old (or corrupted) hibernate file was restored. Then nothing worked and I had to reinstall. If you remember the failed teleportation experiments from the movie "The Fly", that's how bad it was. Since then I've done everything I can to prevent hibernation from working! For that reason I would only be prepared to test this feature if I had a backup installation of OS X and I don't have the hard drive space for that at the moment. Link to comment Share on other sites More sharing options...
juanerson Posted January 30, 2014 Share Posted January 30, 2014 Hibernation (deep sleep = mode 1) worked beautiful a long time ago with Chameleon 2RC5 r611. System SL 10.6.5 - 10.6.6. Update: In r2286 do not works hibernation, computer shutdown in 15 sec (a forced shutdown, see note 1), but "after wake" I get the message at bootloader prompt: header read size 200 Incorrect image signature I think sleepimage is corrupt because I have 4 GB ram, and the sleepimage is only 2.15 GB: Notes: 1) Forced shutdown because "after wake" or after the computer is ON again, during boot, the Console.app log shown: 30/01/14 15:48:03,000 kernel[0]: hfs: Removed 7 orphaned / unlinked files and 12 directories 2) Sleep Mode 0 (pure ram) and Mode 3 (ram to disk), both modes works fine. 3) Actually my OS X partition is not active. Windows 7 is the active partition. Link to comment Share on other sites More sharing options...
Smith@@™ Posted January 30, 2014 Share Posted January 30, 2014 efi_inject_get_devprop_string NULL trying stringdata That is there since year 2009! At lest for me. Link to comment Share on other sites More sharing options...
RehabMan Posted January 30, 2014 Share Posted January 30, 2014 Latest build r2344: ProBook-ML:clover.git Admin$ bdmesg|head Chameleon 2.2svn (svn-r2344) [2014-01-20 13:07:09] msr(428): platform_info 60011500 msr(432): flex_ratio 00010000 Unusable flex ratio detected. Patched MSR now 00000000 Sticking with [BCLK: 99Mhz, Bus-Ratio: 21] CPU: Brand String: Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz CPU: Vendor/Family/ExtFamily: 0x756e6547/0x6/0x0 CPU: Model/ExtModel/Stepping: 0x2a/0x2/0x7 CPU: MaxCoef/CurrCoef: 0x0/0x15 CPU: MaxDiv/CurrDiv: 0x0/0x0 Incorrect information displayed in About this Mac (screen shot attached): Also, latest build broke kozlek's FakeSMC's detection of SMBIOS info (SMBIOS vs. SMBIOS-ORIG in IODeviceTree:/efi/platform). See: https://github.com/kozlek/HWSensors/issues/179 1 Link to comment Share on other sites More sharing options...
ErmaC Posted January 31, 2014 Author Share Posted January 31, 2014 Latest build r2344: ProBook-ML:clover.git Admin$ bdmesg|head Chameleon 2.2svn (svn-r2344) [2014-01-20 13:07:09] msr(428): platform_info 60011500 msr(432): flex_ratio 00010000 Unusable flex ratio detected. Patched MSR now 00000000 Sticking with [BCLK: 99Mhz, Bus-Ratio: 21] CPU: Brand String: Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz CPU: Vendor/Family/ExtFamily: 0x756e6547/0x6/0x0 CPU: Model/ExtModel/Stepping: 0x2a/0x2/0x7 CPU: MaxCoef/CurrCoef: 0x0/0x15 CPU: MaxDiv/CurrDiv: 0x0/0x0 Incorrect information displayed in About this Mac Hi RehabMan thx for the feedback. Can you test the latest 2362 from the SVN? Or simply the pre-compiled binaries (i386_v2362.zip)from my previous post? ErmaC Link to comment Share on other sites More sharing options...
RehabMan Posted January 31, 2014 Share Posted January 31, 2014 Hi RehabMan thx for the feedback. Can you test the latest 2362 from the SVN? Or simply the pre-compiled binaries (i386_v2362.zip)from my previous post? ErmaC Tested by using your binaries previously posted (I updated only /boot). The bug in About this Mac is fixed. The change from IODT:/efi/platform/SMBIOS to IODT:/efi/platform/SMBIOS-ORIG is still present and will affect people using FakeSMC until it can be updated. Is the change necessary/intentional? Link to comment Share on other sites More sharing options...
ErmaC Posted January 31, 2014 Author Share Posted January 31, 2014 The change from IODT:/efi/platform/SMBIOS to IODT:/efi/platform/SMBIOS-ORIG is still present and will affect people using FakeSMC until it can be updated. Is the change necessary/intentional?The change was proposed by Bungo, more info about the change: http://www.insanelymac.com/forum/topic/231075-chameleon-22svn-official-pkg-installer-binaries/page-97?do=findComment&comment=1983165 ErmaC Link to comment Share on other sites More sharing options...
RehabMan Posted January 31, 2014 Share Posted January 31, 2014 The change was proposed by Bungo, more info about the change: http://www.insanelymac.com/forum/topic/231075-chameleon-22svn-official-pkg-installer-binaries/page-97?do=findComment&comment=1983165 ErmaC Is there a reason behind it, or just change for the sake of change? If it actually fixes a real problem, that's great. If it does nothing, then perhaps it should be reconsidered, given that it has a downstream effect (in this case, FakeSMC). FYI: The history behind FakeSMC looking at this entry is this: FakeSMC used to map a region of memory where the SMBIOS data is and parse it directly. Problem was this would cause "waitForSystemMapper" and kernel backtrace during startup. By looking at the (same) data in ioreg we were able to avoid the backtrace. 1 Link to comment Share on other sites More sharing options...
Bungo Posted January 31, 2014 Share Posted January 31, 2014 Is there a reason behind it, or just change for the sake of change? If it actually fixes a real problem, that's great. If it does nothing, then perhaps it should be reconsidered, given that it has a downstream effect (in this case, FakeSMC). FYI: The history behind FakeSMC looking at this entry is this: FakeSMC used to map a region of memory where the SMBIOS data is and parse it directly. Problem was this would cause "waitForSystemMapper" and kernel backtrace during startup. By looking at the (same) data in ioreg we were able to avoid the backtrace. Hi, I'll not insist with it. Doesn't metter if "SMBIOS" or "SMBIOS-ORIG", I get "waitForSystemMapper" with stock AppleACPIPlatform. Helped patched one from Downloads Link to comment Share on other sites More sharing options...
RehabMan Posted January 31, 2014 Share Posted January 31, 2014 Hi, I'll not insist with it. Doesn't metter if "SMBIOS" or "SMBIOS-ORIG", I get "waitForSystemMapper" with stock AppleACPIPlatform. Helped patched one from Downloads If it doesn't matter, then I'd suggest changing it back. You will get no waitForSystemMapper if you use the latest FakeSMC. No need for patched AppleACPIPlatform... you can run vanilla. Link to comment Share on other sites More sharing options...
ErmaC Posted January 31, 2014 Author Share Posted January 31, 2014 If it doesn't matter, then I'd suggest changing it back. I will revert back soon. Thx guys for investigate. ErmaC EDIT: done in commit 2368. 2 Link to comment Share on other sites More sharing options...
Bungo Posted February 1, 2014 Share Posted February 1, 2014 If it doesn't matter, then I'd suggest changing it back. You will get no waitForSystemMapper if you use the latest FakeSMC. No need for patched AppleACPIPlatform... you can run vanilla. I tried v4.4.1 and v3.3.1 (no plugins), with the same result. I've seen IOHIDFamily and VoodooPS2Trackpad in backtrace if I remember, I'll take a photo Link to comment Share on other sites More sharing options...
RehabMan Posted February 1, 2014 Share Posted February 1, 2014 I tried v4.4.1 and v3.3.1 (no plugins), with the same result. I've seen IOHIDFamily and VoodooPS2Trackpad in backtrace if I remember, I'll take a photo Sounds like a different backtrace... I'm talking about one caused by FakeSMC, not other kexts you may have. And FakeSMC version numbers don't correlate to the above... version I'm running: 6.0.1335 Link to comment Share on other sites More sharing options...
DarwinX Posted February 1, 2014 Share Posted February 1, 2014 And FakeSMC version numbers don't correlate to the above... version I'm running: 6.0.1335 Bungo is likely referring to the Slice's FakeSMC branch. 1 Link to comment Share on other sites More sharing options...
RehabMan Posted February 1, 2014 Share Posted February 1, 2014 Bungo is likely referring to the Slice's FakeSMC branch. Probably, but as I stated at the very beginning (emphasis added): "Also, latest build broke kozlek's FakeSMC's detection of SMBIOS info (SMBIOS vs. SMBIOS-ORIG in IODeviceTree:/efi/platform). See: https://github.com/k...sors/issues/179" Probably slice's version still has the backtrace problem as it is probably still locking down the memory region where SMBIOS is kept. I'm not certain though, as I use only my fork of kozlek's FakeSMC. @ErmaC: Thanks for the revert! FYI: I'm generally using Clover now, so this change really didn't affect me personally... But many ProBook users are still using Chameleon and so it was noticed by them. Link to comment Share on other sites More sharing options...
Bungo Posted February 1, 2014 Share Posted February 1, 2014 Probably, but as I stated at the very beginning (emphasis added): "Also, latest build broke kozlek's FakeSMC's detection of SMBIOS info (SMBIOS vs. SMBIOS-ORIG in IODeviceTree:/efi/platform). See: https://github.com/k...sors/issues/179" Probably slice's version still has the backtrace problem as it is probably still locking down the memory region where SMBIOS is kept. I'm not certain though, as I use only my fork of kozlek's FakeSMC. @ErmaC: Thanks for the revert! FYI: I'm generally using Clover now, so this change really didn't affect me personally... But many ProBook users are still using Chameleon and so it was noticed by them. Yes, I use Slice's version. I reviewed that KP it's not related to any kexts I mentioned before, booting stops on "backtrace ....." no kexts listed. I found kozlek's precompiled 6.0.1079 ony. Is 6.0.1335 source's version? Link to comment Share on other sites More sharing options...
RehabMan Posted February 1, 2014 Share Posted February 1, 2014 Yes, I use Slice's version. I reviewed that KP it's not related to any kexts I mentioned before, booting stops on "backtrace ....." no kexts listed. I found kozlek's precompiled 6.0.1079 ony. Is 6.0.1335 source's version? I don't really keep track of kozlek's builds. As mentioned, I have my own fork of his code and do my own builds every so often. You can find my fork at: https://github.com/RehabMan/OS-X-FakeSMC-kozlek. In general, I'm running from binary built from sources, so the version on my machine may be a bit ahead of even my own public builds. I usually "sit on" a rev for a while before deciding to push a new build for download. The waitForSystemMapper + backtrace that comes from older versions of FakeSMC does not prevent boot but is annoying nonetheless. Link to comment Share on other sites More sharing options...
Recommended Posts