[tea]

2lnxneo
Hi. I see you don't use native brightness regulation.
Try add to dsdt this device:

Device (PNLF)
{
  Name (_HID, EisaId ("APP0002"))
  Name (_CID, "backlight")
  Name (_UID, 0x0A)
  Name (_STA, 0x0B)
}

Place it before Device (PWRB). After it see your Display settings...

[tea]

Forgive, has forgotten: It is necessary to inject to your GFX device following properties in addition:

                            "AAPL,Haslid", 
                            Buffer (0x04)
                            {
                                0x01, 0x00, 0x00, 0x00
                            }, 
                            "AAPL,backlight-control", 
                            Buffer (0x04)
                            {
                                0x01, 0x00, 0x00, 0x00
                            }, 

                            "AAPL,BacklightRestore", 
                            Buffer (0x04)
                            {
                                0x01, 0x00, 0x00, 0x00
                            }, 

                            "AAPL,HasPanel", 
                            Buffer (0x04)
                            {
                                0x01, 0x00, 0x00, 0x00
                            }

[lnxneo]

Originally Posted by tea

2lnxneo
Hi. I see you don't use native brightness regulation.
Try add to dsdt this device:

tea,

Thank you for your suggestion. the brightness control of 10v works out of box, except it does not show flash screen of brightness changes. I tried to your patch for DSDT, unfortunately, the flash screen does not show either, do you have any idea ( currently, it's low priority for me fixing it)?

The next target is to get native speedstep working ( not through thirty party kext), do you have any insight? Thanks,

-lnxneo

[tea]

Yes. I know how do it.
1. Add to dsdt _PSS section for CPU (in my dsdt you can find it).
2. Create Legacy for ACPI_SMC_PlatformPlugin Profiler, add to it our model (for ex. MacBook2,2) and configure it for correct work with GFX, CPU and Mem.

[lnxneo]

Originally Posted by tea

Yes. I know how do it.
1. Add to dsdt _PSS section for CPU (in my dsdt you can find it).
2. Create Legacy for ACPI_SMC_PlatformPlugin Profiler, add to it our model (for ex. MacBook2,2) and configure it for correct work with GFX, CPU and Mem.

tea, thanks for the info. Does your _PSS come from SSDT dump of N270 or some other processor?

[tea]

In SSDT no _PSS. We can calculate it:
First simple way - grab pss from CPU-i.app.
CPU-i.v1.0.3b1.zip
Need install kext first (based on VoodooPower) and run CPU-i.app.
Second, more true way calculate it by yourself with help of P-States Calculator.app
P-States Calculator.zip
In this way we can regulate Vcore and make more cool CPU.

[bmcclure937]

The progress being made in this thread is very encouraging and exciting!! Keep up the great work... I look forward to what this may mean for the future of running OSX on Minis

The idea of a fully Vanilla install is very interesting and it seems like it is progressing at a rapid and mind-numbing pace!!

Thanks for the hard work, keep it up!

[0deuce0]

Well... I thought everything was working... I did find two issues... power always thinks its plugged in now and some of the complex graphics seem slow ( more advanced screen savers ) Kind of afraid to try anything since I have all the audio working...


--tom

[lnxneo]

Originally Posted by tea

In SSDT no _PSS. We can calculate it:
First simple way - grab pss from CPU-i.app.
CPU-i.v1.0.3b1.zip
Need install kext first (based on VoodooPower) and run CPU-i.app.
Second, more true way calculate it by yourself with help of P-States Calculator.app
P-States Calculator.zip
In this way we can regulate Vcore and make more cool CPU.

tea, Thanks for the info. I run into a few problems and have a question.
1) In your dsdt file, how did you come up the voltage?
2) p-states calculator may have a bug for Atom, the voltage does not translate to correct package data.
3) I was able to get _PSS data from CPU0INST. However, I don't think the data are correct either. for two reasons: a) it claims power consumption of CPU is 35W, b) the voltage at 1.6GHz is 1.125v, which exceeds the N270 spec (1.1v).

any thought?

-lnxneo

[tea]

1. You need enter all data manually, no automatic (you need understand what you do, see specs for CPU).
2. For start use P-states grabbed from VoodooPower, or from my dsdt - it default, Vcore = normal.

P.S. in my dsdt _PSS added to all two CPU. This not correct, need only for first, CPU0.