Hi pentiumpc,

Thanks for the information and sharing your beta fn key driver.

I'll go and post some information/guide up on ipis about all this.

Regards,

Steve.

Thread for applying your fixes :
http://ipis-osx.wikidot.com/forum/t-...dt#post-403326

Thread for your exprimental kext :
http://ipis-osx.wikidot.com/forum/t-...er#post-403338

Hi pentiumpc,

I'd be intersted in trying to offer my programing skills towards your kext.

Would you be willing to share your source for your experimental kext please?

Regards,

Steve.

I've made up a skeleton kext that has a basic WorkLoop.

The kext inits, probes, finds and matches the ATKD device nub and then enters my start()

I'm having issues adding an IOInterruptEventSource.

I've declared it in the start() like so :

interruptSrc = IOInterruptEventSource::interruptEventSource(
(OSObject*)this,
OSMemberFunctionCast( IOInterruptEventAction,
this,
&com_ipis_driver_AsusFNKeys::interruptOccurred ),
(IOService*)provider,
(int)0);

I have a test in place to report an error if it's not added to the WorkLoop but as soon as I start up the kext I get KP.

I've tested that it is the interrupt event source causing the issue by removing the above code reducing the kext to a really bare template/skeleton and this allows the driver to load correctly.

If you could point me in the right direction I'd appreciate it.

Hi! How the things going?
I want to make some more improvements to 1000H DSDT and need assistance.

The first question is about PS2 controller(doublepost on http://www.insanelymac.com/forum/ind...&#entry1131277 ):

We all using the code
and it makes doubling in ioreg



and another info - log from open bsd booting

This code works well, but its better to fix this doubling. Any ideas?

And the second question concern the Wakeup on clamshell open function. Any1 try to made it?

Still no answers, very sad.
Meanwhile i'll make my own DSDT based on the fixes above and my own fixes. Now, my system works and sleeps perfect under 10.5.6. But, Fn key fixes still works buggy for me.
I'm still looking for more improvements for 1000H DSDT. For instance, i dreaming about clamshell wakeup. Any ideas?

Hi,

I would like to know where and how can I set the FSB to run these settings:

FSB=54
PCIE=176

That's to get a frequency of 1,9Mhz on my 1000h eeepc, and thus to overclock it the same way as I do under XP with eeectl.

Thanks a lot.

Someone here?

got some stuff from insanely , but i think it would look nice in this collection
fixing sleep mode with the _WAK method

information about the _WAK method.
Arguments:
0 The value of the sleeping state (1 for S1, 2 for S2, and so on).
Result Code (2 DWORD package):
Status Bit field of defined conditions that occurred during sleep.
0x00000000 Wake was signaled and was successful
0x00000001 Wake was signaled but failed due to lack of power.
0x00000002 Wake was signaled but failed due to thermal condition.
Other Reserved
PSS If non-zero, the effective S-state the power supply really entered.

This value is used to detect when the targeted S-state was not entered
because of too much current being drawn from the power supply.

OK, so the _WAK method accepts one argument, which is the number of the sleep state that was requested. It returns its result as a package of 2 DWORDs. The first value is a code that tells whether the wake was successful (0 on success, nonzero on failure) and, if not, why. The second value is also zero on success and on failure returns the value of the sleep state that was actually entered. So basically, it's a success/failure code.

The first argument of the package declaration specifies the number of elements in the package, and the second is the package itself. So, the declaration above simply defines a two element package, where each of the elements is zero. This is necessary because the spec requires that the _WAK method return two values.
So, what this really boils down to is a dummy return value that satisfies the spec (thus eliminating the warnings), but doesn't really do anything. It just always returns a success condition.

Fixing sleep mode.

Look for: _WAK

CODE
Method (_WAK, 1, NotSerialized)
{
Store (0xFF, DBG1)
If (LEqual (Arg0, 0x03))
{
Store (0x8F, SCP)
}

If (LEqual (Arg0, 0x04))
{
If (LEqual (OSFL, Zero))
{
If (LEqual (OSFX, 0x03))
{
Store (0x59, SMIP)
}
Else
{
Store (0x58, SMIP)
}
}

If (LEqual (OSFL, One))
{
Store (0x56, SMIP)
}

If (LEqual (OSFL, 0x02))
{
Store (0x57, SMIP)
}

If (LEqual (OSFX, 0x03))
{
Store (0x59, SMIP)
}
}

If (LEqual (Arg0, One)) {}
If (OSFL)
{
Notify (\_SB.PWRB, 0x02)
}
Else
{
If (LEqual (RTCW, Zero))
{
Notify (\_SB.PWRB, 0x02)
}
}

Notify (\_SB.PCI0.USB0, Zero)
Notify (\_SB.PCI0.USB1, Zero)
Notify (\_SB.PCI0.USB2, Zero)
Notify (\_SB.PCI0.USB3, Zero)
Notify (\_SB.PCI0.USB4, Zero)
Notify (\_SB.PCI0.USB5, Zero)
Return(Package(0x02){0x00, 0x00}) <------ Add here. Edit dsdt_fixed.txt before compiling
}

Backlight control
Another nice thing to add in your laptop DSDT: (Under _SB)

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

Might help you in loading the backlight control