Contribute
Register

[Guide] 2015 X1 Carbon Yosemite

Status
Not open for further replies.
RehabMan said:
Interesting... I wonder how universal that is...

At a minimum, verification of the module/offset should be done with IFR extractor.
Click to expand...

Okay, I just did that, and I found a module that contained an IFR for the "Configuration Settings" formset, with 'OilSetup' as the first var store, and the following entry:

Code: 
0x4A08 		Suppress If: {0A 82}
0x4A0A 			64 Bit Unsigned Int: 0x1 {45 0A 01 00 00 00 00 00 00 00}
0x4A14 			Setting: Hidden Page, Variable: 0x4 {05 A6 16 00 17 00 11 00 01 00 04 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x4A3A 				Option: Disabled, Value: 0x0 {09 1C 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x4A56 				Option: Enabled, Value: 0x1 (default) {09 1C 1D 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x4A72 			End of Options {29 02}
0x4A74 		End If {29 02}

which matches up, once I realized that relative to these "Variable:" addresses, the efivars files in Linux have a 4-byte header at the start, so that should be added to the offset values when working with a hex editor in Linux (though not for using EFI shell). Anyway, it looks like this "Hidden Page" setting is what you would look for in other, similar BIOSes.

edit: also, if using EFI shell, if I'm not mistaken you would have to use the alternate setup_var2 command and specify the variable name, since it's outside the main 'Setup' variable. I could be wrong about that possibility though - EFI shell method just doesn't work for me.
 
RehabMan said:
Different problem. Already fixed. Use the 128mb OsxAptioFixDrv-64.efi that is in Clover v3263.
Click to expand...

Yeah I double checked it. The only thing I've been able to figure out, is that if I enable the debug to console in OsxAptioFixDrv.c, I see the following difference between 10.10:

Code: 
StartImage(936C4718)
FilePath: System\Library\CoreServices\boot.efi
ImageBase: 92425000 - 924B5000 (90000)
OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi
Using reloc block: yes, hibernate wake: no
OsAptioFixDrv: AllocateRelocBlock(): gRelocBase set to 85853000 - 8F378FFF
efiboot loaded from device: Acpi(PNP0A03,0)/Pci(1F12)/SATA(0,0)/HD(Part6,Sig............)
boot file path: System\Library\CoreServices\boot.efi
....................
root device uuid is ...
+++++++++++++++++++++++++++++++++++++++++++++++++++

and in 10.11, it's the same but without the "efiboot loaded" and path and "root device uuid" lines:

Code: 
StartImage(936C4718)
FilePath: OS X Install Data\boot.efi
ImageBase: 92425000 - 924B5000 (90000)
OsxAptioFixDrv: Starting overrides for OS X Install Data\boot.efi
Using reloc block: yes, hibernate wake: no
OsAptioFixDrv: AllocateRelocBlock(): gRelocBase set to 85853000 - 8F378FFF
+++++++++++++++++++++++++++++++++++++++++++++++++++

So it seems like maybe my problem could be unrelated to the memory relocations and all that? To me the output suggests something amiss with finding the root device, plus an unusually fast kernel panic thereafter. Maybe an interaction of both types of problem? I don't know. What do you think, RehabMan?

An important note on my data here is that enabling that debug output in the OsxAptioFix driver actually caused my boots to hang right after these messages, where the kernel should start up and do its thing. That was for both 10.10 and 10.11, which is weird, because it's just debug output.
 
kylec said:
Yeah I double checked it. The only thing I've been able to figure out, is that if I enable the debug to console in OsxAptioFixDrv.c, I see the following difference between 10.10:

Code: 
StartImage(936C4718)
FilePath: System\Library\CoreServices\boot.efi
ImageBase: 92425000 - 924B5000 (90000)
OsxAptioFixDrv: Starting overrides for System\Library\CoreServices\boot.efi
Using reloc block: yes, hibernate wake: no
OsAptioFixDrv: AllocateRelocBlock(): gRelocBase set to 85853000 - 8F378FFF
efiboot loaded from device: Acpi(PNP0A03,0)/Pci(1F12)/SATA(0,0)/HD(Part6,Sig............)
boot file path: System\Library\CoreServices\boot.efi
....................
root device uuid is ...
+++++++++++++++++++++++++++++++++++++++++++++++++++

and in 10.11, it's the same but without the "efiboot loaded" and path and "root device uuid" lines:

Code: 
StartImage(936C4718)
FilePath: OS X Install Data\boot.efi
ImageBase: 92425000 - 924B5000 (90000)
OsxAptioFixDrv: Starting overrides for OS X Install Data\boot.efi
Using reloc block: yes, hibernate wake: no
OsAptioFixDrv: AllocateRelocBlock(): gRelocBase set to 85853000 - 8F378FFF
+++++++++++++++++++++++++++++++++++++++++++++++++++

So it seems like maybe my problem could be unrelated to the memory relocations and all that? To me the output suggests something amiss with finding the root device, plus an unusually fast kernel panic thereafter. Maybe an interaction of both types of problem? I don't know. What do you think, RehabMan?

An important note on my data here is that enabling that debug output in the OsxAptioFix driver actually caused my boots to hang right after these messages, where the kernel should start up and do its thing. That was for both 10.10 and 10.11, which is weird, because it's just debug output.
Click to expand...

I have to admit I lost track of what problem you're trying to solve.

maybe this....
If i try boot with Clover 3259 on El Capitan PB7/All versions of El Capitan, get the error on boot:
panic( cpu 0 caller 0xffffff808032ffb6):"zone_init:kmem_suballoc failed" .(blabla), zalloc.c".
I see - this problem on the memory map.
Click to expand...
 
RehabMan said:
I have to admit I lost track of what problem you're trying to solve.
Click to expand...

My bad. I'll start a new thread in a moment and update this post with a link.

maybe this....
If i try boot with Clover 3259 on El Capitan PB7/All versions of El Capitan, get the error on boot:
panic( cpu 0 caller 0xffffff808032ffb6):"zone_init:kmem_suballoc failed" .(blabla), zalloc.c".
I see - this problem on the memory map.
Click to expand...
Click to expand...

Yes, exactly. So far, I know that on the S41 it happens with LowMem, AptioFixDrv, AptioFix2Drv, whether booting off USB or hard drive, for versions of 10.11 back to PB1. I tried some different values of KERNEL_BLOCK_NO_RT_SIZE_PAGES - if it's much below 96 MB then I get some error message from Clover about memory size mismatch. Otherwise, I get this kmem_suballoc panic.
 
kylec said:
My bad. I'll start a new thread in a moment and update this post with a link.



Yes, exactly. So far, I know that on the S41 it happens with LowMem, AptioFixDrv, AptioFix2Drv, whether booting off USB or hard drive, for versions of 10.11 back to PB1. I tried some different values of KERNEL_BLOCK_NO_RT_SIZE_PAGES - if it's much below 96 MB then I get some error message from Clover about memory size mismatch. Otherwise, I get this kmem_suballoc panic.
Click to expand...

It could be anything. Troubleshooting it would involve discussing your installation and post-installation procedures.
 
Anyone get this working on the 2015 QHD (2560x1440) Multi-touch?
 
Hi guys!
Sorry for being a bit out of the main topic here but there might be other people interested in the answer :

I'm trying to get everything ready before I follow this guide to "hackintosh" my X1 with a very similar configuration to JCSNIDER :
I7-5500U with 8Gb ram and FHD Screen

I got a dell DW1560 card and installed it.
I got have a bios chip programmer that I finally didn't even need to use since I got no whitelist error and got the card fully detected in windows10 :)

The only thing : no network detected...
I saw JCSNIDER's post on tenforums (http://www.tenforums.com/drivers-ha...-no-networks-found-plot-twist.html#post410428).

@JCSNIDER : Have you had any success using it under W10?
I could see that you managed to make it work under OSX (hackintosh).

Thanks for your help and thanks in advance for your guide that I'm about to follow anyway :)
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top