- Joined
- Oct 21, 2012
- Messages
- 3,392
- Motherboard
- HP Elitebook 8470p
- CPU
- i5 3320M
- Graphics
- HD 4000, 1600x900
- Mobile Phone
Your Bluetooth is included in the card, replace by 43225HMB and both will work.
Dell Inspiron 3x37 - 5x37 -7x37 Clover Install Guide
- Thread starter nguyenmac
- Start date
- Status
Your Bluetooth is included in the card, replace by 43225HMB and both will work.
- Joined
- May 13, 2012
- Messages
- 22
- Motherboard
- Yosemite
- CPU
- i3
- Graphics
- Geforce GTX660OC
- Mac
- Classic Mac
- Mobile Phone
Hey nguyenmac,
first I want to thank you for your work with inspiron laptops!
I recently bought a 7537 with FHD Display. I know that it´s kind of unsupported, but I will definitely give it a try!
With <key>ig-platform-id</key> <string>0x01660004</string> I am able to boot into the installer and install system + recovery. When trying to boot the system the system just stops when the desktop should show up (no black screen).
I furthermore have a different cpu (i7 4510U), but LG Display.
The problem i am struggling with is the DSDT patching. When I just compile the fresh DSDT.dsl I get the errors:
syntax error unexpected PARSEOP_ARG0
syntax error unexpected PARSEOP_FIELD
syntax error unexpected PARSEOP_METHOD
There are no other warnings or anything else, which seems quite nice to me.
With the copy/paste patch from 14 I get much warnings and 3 different errors:
Name already exists in scope (_SB_.PCI0.PEG0)
Name already exists in scope (_SB_.PCI0.PEG0.PEGP)
Name already exists in scope (_SB_.RP05.PEG0)
I tried to apply all patches mentioned in your guide but after applying the first patch maciasl doesn´t allow any further patches (apply button can´t be clicked).
Please help me to fix this problem, so I can try to get the 7537 running! I attached my DSDT/SSDT files if someone wants to see them!
Thank you!!
first I want to thank you for your work with inspiron laptops!
I recently bought a 7537 with FHD Display. I know that it´s kind of unsupported, but I will definitely give it a try!
With <key>ig-platform-id</key> <string>0x01660004</string> I am able to boot into the installer and install system + recovery. When trying to boot the system the system just stops when the desktop should show up (no black screen).
I furthermore have a different cpu (i7 4510U), but LG Display.
The problem i am struggling with is the DSDT patching. When I just compile the fresh DSDT.dsl I get the errors:
syntax error unexpected PARSEOP_ARG0
syntax error unexpected PARSEOP_FIELD
syntax error unexpected PARSEOP_METHOD
There are no other warnings or anything else, which seems quite nice to me.
With the copy/paste patch from 14 I get much warnings and 3 different errors:
Name already exists in scope (_SB_.PCI0.PEG0)
Name already exists in scope (_SB_.PCI0.PEG0.PEGP)
Name already exists in scope (_SB_.RP05.PEG0)
I tried to apply all patches mentioned in your guide but after applying the first patch maciasl doesn´t allow any further patches (apply button can´t be clicked).
Please help me to fix this problem, so I can try to get the 7537 running! I attached my DSDT/SSDT files if someone wants to see them!
Thank you!!
RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,006
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
01660004 is not appropriate for Haswell. It is HD4000/Ivy specific. Try 0xa260006 instead.
Fix all errors before proceeding with patches. Don't use patches intended for an Ivy system on Haswell system.
- Joined
- May 13, 2012
- Messages
- 22
- Motherboard
- Yosemite
- CPU
- i3
- Graphics
- Geforce GTX660OC
- Mac
- Classic Mac
- Mobile Phone
Hey Rehabman thanks for the quick reply!
I got the parseop errors fixed! As soon as the 3 errors are fixed the others with PEGP etc. appear!
I tried to use the first patch-block from 14 as it removes the external device entries that cause the error, but the patch doesn´t remove the devices from the definition block. I now deleted the 3 external device entries by hand and my dsdt is free of errors.
But the problem with the other patches from your repository are still present: Trying to rename GFX0 to IGP for example can´t be applied and all other patches too.
Are these patches all not for Haswell? I searched for Haswell specific patches, but I didn´t find anything at all!
I got the parseop errors fixed! As soon as the 3 errors are fixed the others with PEGP etc. appear!
I tried to use the first patch-block from 14 as it removes the external device entries that cause the error, but the patch doesn´t remove the devices from the definition block. I now deleted the 3 external device entries by hand and my dsdt is free of errors.
But the problem with the other patches from your repository are still present: Trying to rename GFX0 to IGP for example can´t be applied and all other patches too.
Are these patches all not for Haswell? I searched for Haswell specific patches, but I didn´t find anything at all!
RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,006
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Something in your DSDT is confusing MaciASL (MaciASL bug...) I'm not sure what it is. You should report the bug to SJ_Underwater and see if he can fix it. You should also try his latest version.
patchmatic does this:
Code:
Speedy-ML:DSDT Admin$ patchmatic DSDT.dsl ~/Projects/laptop.git/graphics/graphics_Rename-GFX0.txt DSDT_p.dsl
2014-06-19 12:12:42.033 patchmatic[737:507] *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSCFString rangeOfCharacterFromSet:options:range:]: Range {9223372036854775808, 9223372036855205458} out of bounds; string length 547955'
*** First throw call stack:
(
0 CoreFoundation 0x00007fff90ff025c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff85e7ae75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff90ff010c +[NSException raise:format:] + 204
3 Foundation 0x00007fff895741cf -[NSString rangeOfCharacterFromSet:options:range:] + 172
4 patchmatic 0x0000000100006c27 patchmatic + 27687
5 patchmatic 0x00000001000041de patchmatic + 16862
6 patchmatic 0x00000001000039fa patchmatic + 14842
7 patchmatic 0x0000000100003aef patchmatic + 15087
8 patchmatic 0x0000000100003aef patchmatic + 15087
9 patchmatic 0x0000000100003aef patchmatic + 15087
10 patchmatic 0x0000000100003aef patchmatic + 15087
11 patchmatic 0x0000000100002c3c patchmatic + 11324
12 patchmatic 0x00000001000017bd patchmatic + 6077
13 patchmatic 0x0000000100001434 patchmatic + 5172
14 ??? 0x0000000000000004 0x0 + 4
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6So there is definitely a bug in the MaciASL patch code somewhere...
- Joined
- May 13, 2012
- Messages
- 22
- Motherboard
- Yosemite
- CPU
- i3
- Graphics
- Geforce GTX660OC
- Mac
- Classic Mac
- Mobile Phone
Ahh that explains the wierd behavior!
My Problem is as I am a new user the system blocks my attempt to send SJ a pm
Only 76 posts away :-D
My Problem is as I am a new user the system blocks my attempt to send SJ a pm
Only 76 posts away :-D
RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,006
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Ahh that explains the wierd behavior!
My Problem is as I am a new user the system blocks my attempt to send SJ a pm
Only 76 posts away :-D
Post here: http://www.tonymacx86.com/dsdt/83565-native-dsdt-aml-ide-compiler-maciasl-open-beta.html
- Joined
- May 13, 2012
- Messages
- 22
- Motherboard
- Yosemite
- CPU
- i3
- Graphics
- Geforce GTX660OC
- Mac
- Classic Mac
- Mobile Phone
Hey!
I made some progress with my 7537 FHD!
I did most of the DSDT edits by hand :-! and looked at the EDID information under windows. Thereby I found out that the LG screen itself has 3 EDID informations. I first tried using Clover to inject EDID information for all 3 by hand without success.
By injecting the EDID information and ID 0xa260006 into SSDT-7 aka SSDT-1 i am now able to boot directly into OSX. It is a bit glitchy (about 20%) as it recognizes my graphics card as a Intel HD5000.
At least a little step further
I´ll try different kg-platform-id´s later, any suggestions?
I made some progress with my 7537 FHD!
I did most of the DSDT edits by hand :-! and looked at the EDID information under windows. Thereby I found out that the LG screen itself has 3 EDID informations. I first tried using Clover to inject EDID information for all 3 by hand without success.
By injecting the EDID information and ID 0xa260006 into SSDT-7 aka SSDT-1 i am now able to boot directly into OSX. It is a bit glitchy (about 20%) as it recognizes my graphics card as a Intel HD5000.
At least a little step further
I´ll try different kg-platform-id´s later, any suggestions?
RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,006
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Hey!
I made some progress with my 7537 FHD!
I did most of the DSDT edits by hand :-! and looked at the EDID information under windows. Thereby I found out that the LG screen itself has 3 EDID informations. I first tried using Clover to inject EDID information for all 3 by hand without success.
By injecting the EDID information and ID 0xa260006 into SSDT-7 aka SSDT-1 i am now able to boot directly into OSX. It is a bit glitchy (about 20%) as it recognizes my graphics card as a Intel HD5000.
At least a little step further
I´ll try different kg-platform-id´s later, any suggestions?
Make sure you set the bootloader resolution to your native laptop resolution.
- Joined
- May 13, 2012
- Messages
- 22
- Motherboard
- Yosemite
- CPU
- i3
- Graphics
- Geforce GTX660OC
- Mac
- Classic Mac
- Mobile Phone
Clover config.plist has native resolution 1920x1080!
My thesis is that OSX recognizes my display as multiple displays and chooses the wrong as default. I attached a picture of my logfile which shows multiple displays being recognized with different resolution. One of the has retina resolution I think?
My first display is recognized with the right resolution of 1920x1080 an the device id 0x04273c80.
The other 3 displays have a different id 0x003f003f,0x003f003e, 0x003f003d and have retina or no resolution at all.
I tried using fixedid to fake a macbook air display, no difference.
My thesis is that OSX recognizes my display as multiple displays and chooses the wrong as default. I attached a picture of my logfile which shows multiple displays being recognized with different resolution. One of the has retina resolution I think?
My first display is recognized with the right resolution of 1920x1080 an the device id 0x04273c80.
The other 3 displays have a different id 0x003f003f,0x003f003e, 0x003f003d and have retina or no resolution at all.
I tried using fixedid to fake a macbook air display, no difference.
- Status