zoliky
Members-
Posts
24 -
Joined
-
Last visited
Everything posted by zoliky
-
Thank you! Do I need to have that "Kernel Flags" entry in the file? It is empty.
-
I have these in org.chameleon.Boot.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string></string> <key>Default Partition</key> <string>hd(0,2)</string> <key>EthernetBuiltIn</key> <string>Yes</string> <key>Quiet Boot</key> <string>Yes</string> <key>DropSSDT</key> <string>Yes</string> </dict> </plist> Does the order matter? For example, do I need to insert "Default Partition" at the very beginning (before Kernel) ? or doesn't matter? Thank you. Your suggestion would be greatly appreciated!
-
Here's my RAW DSDT, so you can make an idea what I'm talking about. Any help would be greatly appreciated. dsdt.aml.tar.gz
-
Hello, I compiled the latest version of iasl with AcpicaTool I try to decompile the raw DSDT generated with Ubuntu: ./iasl -d dsdt.aml and I get this (only with the new iasl 20130328-64 version!) It gives me the dsdt.dsl file, but the weird thing is that iasl insert that warning into the header: Is there any way to skip that warning/check or the only fix is to move back to older iasl? No problems with the older 20130117-64.
-
Wow. Thank you! That is greatly appreciated. May I ask one more thing? Are GeneratePStates and GenerateCStates disabled by default? In other words, are they set to "No" by default in chameleon?
-
Nice guide. Is GraphicsEnabler enabled by default in latest chameleon-trunk? thank you!
-
Thank you, your time is greatly appreciated.
-
Hi, Is there a way to check if SMBUS is working and patch has been applied correctly? Please tell me what's the difference between this patch: Device (BUS0) { Name (_CID, "smbus") // _CID: Compatible ID Name (_ADR, Zero) // _ADR: Address Device (DVL0) { Name (_ADR, 0x57) // _ADR: Address Name (_CID, "diagsvault") // _CID: Compatible ID } } and this one: Device (BUS0) { Name (_CID, "smbus") // _CID: Compatible ID Name (_ADR, Zero) // _ADR: Address Device (DVL0) { Name (_ADR, 0x57) // _ADR: Address Name (_CID, "diagsvault") // _CID: Compatible ID Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x02) { "address", 0x57 }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } Is there any reason to include that additional Metdod _DSM and DTGP call? I ask this question because I saw these two different versions on the web. I would be grateful for any suggestion. Thank you!
-
Hello, I have a HP Probook 4540s laptop. It's a very versatile notebook and OS X works like a charm. I think my Function Key (I have only one on the keybord) works out of the box. What I mean is this: I press FN+F1 and notebook goes to sleep. I press FN+F9 and volume increases. And so on. My question is: Do I need this patch ? # Enable functions keys into device label PS2K insert begin Method (_DSM, 4, NotSerialized)\n {\n Store (Package (0x02)\n {\n "AAPL,has-embedded-fn-keys", \n Buffer (0x04)\n {\n 0x01, 0x00, 0x00, 0x00\n }\n }, Local0)\n DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n Return (Local0)\n }\n end; As I mentioned earlier, my function key works without that patch. Another question, here's the shutdown fix: # Shutdown fix into method label _PTS code_regex_not If\s\(LEqual\s\(Arg0,\s0x05\)\) code_regex ^((?:.|\n)*)$ replace_matched begin If (LEqual (Arg0, 0x05)) {}\n Else\n {\n %1 } end; Both FN key and Shutdown patch are in the laptop section on Olarila. I never experienced problems with shutdown, so I need that shutdown patch? What does that shutdown patch really do? Any suggestion would be greatly appreciated. Thank you!
-
DTGP is already in the file, at the end. The problem is something else.
-
Hi, I added this code to Device (GFX0). I need it for AppleHDA. Method (_DSM, 4, NotSerialized) { Store (Package (0x04) { "hda-gfx", Buffer (0x0A) { "onboard-1" }, "AAPL,snb-platform-id", Buffer (0x04) { 0x00, 0x00, 0x01, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } After adding that code, I'm getting a lot of DSDT errors. I would like to mention, it's a RAW dsdt of my HP4540s laptop. The only thing I added is HDEF and that patch posted above. I'm stuck and need your help, please. I attached my DSDT. I would be very grateful for any suggestion! Your time is appreciated. HP4540s-dsdt.dsl.zip
-
Sorry for being curious, but it has a logic behind it? Did you check my codec_dump? I read that "hda-gfx" adds HDMI audio support. I have a HDMI port on my laptop. I think I need to add that "hda-gfx" code into Device (GFX0) as well. Intel HD 3000 Graphics. How can I test the HDMI audio? I have a TV with HDMi support. Should I connect my laptop to the TV via HDMI cable?
-
Hi, I need to use this dsdt code to enable my patched AppleHDA. Device (HDEF) { Name (_ADR, 0x001B0000) Method (_DSM, 4, NotSerialized) { Store (Package (0x04) { "layout-id", Buffer (0x04) { 0x0C, 0x00, 0x00, 0x00 }, "PinConfigurations", Buffer (Zero) {} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Some DSDT I have seen use this additional code in the Store (Package (0x04): "hda-gfx", Buffer (0x0A) { "onboard-1" }, or "hda-gfx", Buffer (0x0A) { "onboard-2" }, I'm not sure which one should I use for my built-in sound card onboard-1 or onboard-2? Is there a way to figure that out? I have a HP4540s laptop. If it helps, I attached my codec_dump generated in Ubuntu. Thank you! codec_dump.txt.zip
-
HP 4540s: Initializer list shorter than declared pkg length
zoliky replied to zoliky's topic in DSDT & Patch Requests
My HD3000 works without patches or enablers. I changed this address in AppleIntelSNBGraphicsFB.kext IOPCIPrimaryMatch 0x1C3A8086 to this: IOPCIPrimaryMatch 0x1E3A8086 Please note, this change works only with Intel 7-series motherboards. I use a HP 4540s laptop - i5-2450m sandy bridge. -
HP 4540s: Initializer list shorter than declared pkg length
zoliky replied to zoliky's topic in DSDT & Patch Requests
Thank you. I appreciate it! -
HP 4540s: Initializer list shorter than declared pkg length
zoliky replied to zoliky's topic in DSDT & Patch Requests
May I ask how did you obtain the correct Package () informations? For example for this code: My DSDT: Package (0x1A) { "HP QuickLook", "", "\\System Configuration\\Device Configurations", Zero, One, Zero, 0x0137, 0x03, " ", " ", " ", Zero, "Disable", 0x02, "Disable", "Enable" }, Your fixed DSDT: Package (0x10) { "HP QuickLook", "", "\\System Configuration\\Device Configurations", Zero, One, Zero, 0x0137, 0x03, " ", " ", " ", Zero, "Disable", 0x02, "Disable", "Enable" }, My dsdt have 0x1A, and your fixed dsdt have 0x10 -
HP 4540s: Initializer list shorter than declared pkg length
zoliky replied to zoliky's topic in DSDT & Patch Requests
Wow. Thank you so much! Did you edit my DSDT or do you have the same specs/BIOS ? -
HP 4540s: Initializer list shorter than declared pkg length
zoliky replied to zoliky's topic in DSDT & Patch Requests
Cassio, Thank you very much! You help is greatly appreciated. I removed that 0x1A value, compiled then decompiled the file. I didn't see 0x0E in the file. The compiler set that removed value back to 0x1A. -
My specs: HP 4540s laptop, i5-2450m, Intel HD3000M, BIOS 68IRR Ver F. 01 My DSDT.dsl https://dl.dropbox.com/u/1924024/dsdthp.dsl IASL I use iasl20121114 to compile and decompile the DSDT. The problem This is how the original (Hewlett-Packard) DSDT looks. ~iasl: Compilation complete. 0 Errors, 6 Warnings, 275 Remarks, 4643 Optimizations I have more than 200 remarks: dsdthp.dsl 15838: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15856: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15876: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15896: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15916: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15934: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15954: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15972: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 15992: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 16012: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 16030: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 16048: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 16066: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 16084: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length dsdthp.dsl 16102: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length and much more... Ok, let's examine the first remark: dsdthp.dsl 15838: Package (0x1A) Remark 5063 - ^ Initializer list shorter than declared package length Package (0x1A) <--- this is line 15838 { " ", " ", " ", 0x01, 0x00, 0x01, 0x02A7, 0x03, " ", " ", " ", 0x00, " ", 0x00 }, There's a way to fix that by replacing Package (0x1A) with Package () but doing that for more than 200 remarks isn't fun. I don't know if removing (0x1A) is correct. I think the problem is somewhere else, maybe a bracket is missing in the factory DSDT. I searched three forums on the internet, but I didn't find a solution. Can you please take a look at my DSDT? It is already decompiled. Should I ignore these remarks and warnings? Your time is greatly appreciated. Thank you!
-
Thank you!
-
Thank you so much! Should I insert the original code like this? : Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (0x01, INIM) DKET () Store (\_SB.SBRC (), Local0) Or (Local0, 0x80000000, \_SB.PCI0.GFX0.BCLP) Store (0x00, WDSA) Store (0x00, WDST) Store (0x00, WDGN) If (CondRefOf (FPED)) { FPED () } } or just call the function directly without the conditional? Method (_INI, 0, NotSerialized) // _INI: Initialize { Store (0x01, INIM) DKET () Store (\_SB.SBRC (), Local0) Or (Local0, 0x80000000, \_SB.PCI0.GFX0.BCLP) Store (0x00, WDSA) Store (0x00, WDST) Store (0x00, WDGN) FPED () // <---- calling the function (IF REMOVED) }
-
Thank you Cassio. I greatly appreciate your help. Can you please take a look at my DSDT ? I'm not sure where should I move that IF condition, because I have more method INI. Thank you so much! hp4340s.dsl.zip
-
Yes, sorry. You're perfectly right. I built the latest iasl from sources (20121114) and I have 200 errors. I have this code in my DSDT (HP 4540s laptop, i5, intel hd3000): If (CondRefOf (FPED)) { FPED () } I commented out the code: // If (CondRefOf (FPED)) // { // FPED () //} All 200 errors fixed. I'm wondering what does this FPED thing do.
-
I'm wondering what method/command the DSDT editor use to extract the DSDT. It gives me a lot of errors and warnings. As an alternative, I tried to obtain my DSDT through ioreg/terminal: sudo perl -e 'open(CMD, "ioreg -lw0 \| grep DSDT|") or die; while(<CMD>) { chomp; if($_ =~ /\"DSDT\.?\d?\"=<([^>]*)>/) { $buff = $1; open(PIP, "|xxd -r -p > ~/Desktop/dsdt.aml") or die; print PIP "$1"; } }' The terminal command gives me a cleaner DSDT (the same DSDT as Ubuntu gives me) with 0 warning and just 1 error: Error 4095 - ^ syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK Can someone clarify this to me? I can do the DSDT editing in TextMate. I don't necessary need DSDT Editor. Thank you!
