Gigabyte's Nvidia 9400 powered M-ATX MOBO

[LJSeinfeld]

A couple of pages back someone posted the kexts to get gigabit ethernet working properly and get the hard drives to show up correctly in the finder and the profiler. Using Signal64's DSDT (post #76 of this thread) seems to work okay for me. What install are you using and have you run memtest to see if your system snows?

 

Sound has been a problem for all of us.

......

 

Installed the nForce LAN driver from here: (0.62.9) http://forum.insanelymac.com/index.php?sho...125569&st=0 system hangs at boot (see attached pic).

 

 

Will try the memtest ASAP.

 

Note, I left the system on when I went to sleep last night, woke up to a Kernel Panic screen. I was downloading the 10.5.6 update to the machine when it happened... not sure if that's related (disk activity?).

[LJSeinfeld]

Looks like I have shared memory issues... my memory isn't on the Qualified Vendor list... it's Kingston -- NewEgg description (MEM 2Gx2|KST KVR800D2N5K2/4G R). PN is KST KVR800D2N5K2/4G R.

 

Wonder if that means I have bad RAM, or if I need to tweak some BIOS settings? I set the cards shared memory to a static 256, turned on the graphics accelerator option (maybe need to turn that off)...?

[kromozone]

Installed the nForce LAN driver from here: (0.62.9) http://forum.insanelymac.com/index.php?sho...125569&st=0 system hangs at boot (see attached pic).

 

 

Will try the memtest ASAP.

 

Note, I left the system on when I went to sleep last night, woke up to a Kernel Panic screen. I was downloading the 10.5.6 update to the machine when it happened... not sure if that's related (disk activity?).

 

I've had my ethernet shut off, as reported earlier in the thread, as well as a full snowcrash on wake from sleep. Perhaps your machine went to sleep, and when trying to awaken your ethernet kext freaked out. I haven't been able to get this board working perfectly regardless of the configuration. The GPU will show full QE/CI, pass all test, etc. but when I actually try to run a 3D game on it, it invariably crashes with varying degrees of intensity. I even tried putting in an 8600 card which I know is well supported, setting the 9400 to disable on external GPU, and pulling out all but 2gb of RAM, and there were still issues with crashing in 3D apps. Even more bizarre, I loaded a Vista install on this machine and 3DMark06 will crash whenever I try to run it. I'm going to see if their latest BIOS update does anything for me.

[Signal64]

Lot's of stuff going on, sorry I couldn't reply sooner with anything helpful.

Item 1: E7AUM-DS2H ALC889 Audio

 

Please try this out and let me know how it works for you.

It is in Boot-132/Legacy Audio format meaning make sure you have the "vanilla" unmodified version of the AppleHDA.kext installed!

I'm including a DSDT.aml that will also remove the requirement for HDAEnabler.kext as well.

If you use this DSDT.aml then remove any HDAEnabler.kext you might have installed!!

 

Install the kext directory as is via kexthelper.

 

Again, the original unmodified AppleHDA.kext is required and there is no need to modify it.

 

Credits of course to THeKiNG's examples and knowledge base thread:

 

I do not have the "grey" port mapped in the output preferences.

Green Line Out switches to Headphones when Front Panel Headphones are plugged in

Internal Mic is mapped to Front Panel Mic.

All other ports functional.

 

No work on HDMI as I have no HDMI video devices that accept audio yet (soon to be resolved).

Try it and let me know.

 

Edit: Disable HDMI Audio in BIOS for now otherwise you will get plenty of sound assertion errors which is a bad thing.

See posts below.

 

Edit2: Sleep disables the audio (just like the ethernet).

 

See the README.txt in the zip.

 

Item 2: 4+ Gig of Memory Issue

 

Don't know if this is the only issue, but the video memory is not being moved up to a protect space when you use 4Gig or more of memory. I've compared this to my unibody macbook with 2Gig and 4Gig, and the ASUS with 2Gig, 4Gig, and 8Gig installed.

On those systems, the IODeviceMemory shown in IORegistry is bumped up to higher addresses with more memory installed.

The Gigabyte is not doing this. It is keeping the memory mapped starting at an address around 3.2Gig and is considered useable by OS X when you have 4Gig or more installed.

 

The ASUS behaves itself in this regard and isn't an issue on that board.

I'm still futzing with getting the MSI installed to check on that.

 

Question is, where does the memory for integrated video get allocated?

 

I've tried updating the VGA Bios from other boards (which are all generic for three device id's btw) which have older and newer versions than the Gigabyte, but haven't been able to successfully do so. The regular nvidia tools I'm aware of for updating nvidia display bios's won't work here as it is in the regular system bios. Hacking it in via Award tools hasn't yielded anything yet.

 

All of the bios's I've come across for other 730i boards have to some degree included newer updates for the nvidia hardware (some more so than others). The Gigabyte hasn't yet and hope they catch up.

 

Still plugging away at this in the meantime.

 

Edit: To be clear, what this means is you shouldn't run 4GB of RAM on the Gigabyte for now.

I can't say why I'm not seeing the issue after hours of use and some folks are right away, but stay away from this for now.

 

 

Item 3. NoPE MB Restore Disc

 

As zchef2k mentioned, I helped him install using the NoPE disc and the result was that it reported build 9F2088 after the install.

 

A compare of the restore disc that came with my aluminum 13" macbook unibody is showing no differences.

The md5 of the extensions directory is the same.

 

The md5 of the n-mxl155.dmg file is:

f6e7b0ee9b4132080743a428c15f6e40

 

 

Item 4. Problem Reporting

 

It's worth mentioning again or refering to the post where on how you installed when posting problems.

 

If you used some release other than a aluminum unibody macbook restore disc, then yea, expect problems.

It's no different than the legacy of problems other installs on nvidia motherboard chipsets have.

 

Bottom Line, suggest mentioning how it was installed and with what in a problem reporting post to make it clear as we have a few things going on in this thread.

 

 

Item 5. Attached Files

I'm adding in the AHCI kexts again as well and my original v1 DSDT.aml file I provided earlier

Again, there is a new DSDT.aml file in the audio zip which is v1 with the audio section to eliminate having to use hdaenabler.

E7AUMDS2H_audio_v2.zip

730i_AHCI.zip

E7AUM_DS2H_DSDTAML_V1.zip

[bobisdead]

don't know what i'm doing wrong..

 

I get syncing disks.... killing all processes" blabla "MACH reboot".

 

1) Made one partition with GUID table

2) Opened ALU macbook restore (md5: te21df32f6fceaa64619e820cf85dbfb2) disc with Pacifist on with my old macbook

3) Installed contents on first partition using Pacifist - connected via external USB.

4) coied DSDT.aml to root

5) Installed PC EFI v9 (Chameleon v1.0.12) with Universal OSx86 Installer.

6) Installed dsmos.kext, IntelCPUPMDisabler.kext,SMBIOSEnabler.kext with with Universal OSx86 Installer. .

7) Changed com.apple.boot.plist so that I get the 8 seconds timeout.

8) disabled IDE, SERIAL, paralel, firewire in bios

9) Connected HD on Sata.

10) tried to boot in safe mode or from USB

 

could anyone tell me what i forgot ??

 

thx

 

Bob

[Signal64]

Apply the OSInstall.mpkg I posted earlier (removes model check) to the restore disc, boot the restoredisc on the macbook, restore to the usb drive.

 

THEN apply chameleon, dsdt.aml, etc on the usb drive after you've restored to it.

[bobisdead]

Apply the OSInstall.mpkg I posted earlier (removes model check) to the restore disc, boot the restoredisc on the macbook, restore to the usb drive.

 

THEN apply chameleon, dsdt.aml, etc on the usb drive after you've restored to it.

 

Thanks for your anwser, I'll do it and let you know.

 

have a good day

 

bob

[stan78]

Item 1: E7AUM-DS2H ALC889 Audio

 

Please try this out and let me know how it works for you.

 

Wow, first of all I'm glad that you took care of some of the audio stuff. I tried some things too

but this topic seems rather complicated.

But I can report back that it's working for me.

I still have a lot of sound assertion errors but basically it works like the hacked applehda.kext files

did. Still no spdif input for example and I didn't have a mic to check the analog inputs.

 

One question though - in one of your plists it said "885 Codec". And I've read somewhere that the

linux codec dump is making the mistake of confusing 885 and 889A. Like I said I don't know that

much about all the codec stuff but are you sure you were using the correct dump ?

 

As for HDMI Audio. I will call my first son Signal64 if you find out how to do it ;-)

 

Thanks you very much for everything.

st

[Signal64]

Wow, first of all I'm glad that you took care of some of the audio stuff. I tried some things too

but this topic seems rather complicated.

But I can report back that it's working for me.

I still have a lot of sound assertion errors but basically it works like the hacked applehda.kext files

did. Still no spdif input for example and I didn't have a mic to check the analog inputs.

 

One question though - in one of your plists it said "885 Codec". And I've read somewhere that the

linux codec dump is making the mistake of confusing 885 and 889A. Like I said I don't know that

much about all the codec stuff but are you sure you were using the correct dump ?

 

As for HDMI Audio. I will call my first son Signal64 if you find out how to do it ;-)

 

Thanks you very much for everything.

st

 

Thanks for trying it out.

I'm not getting any other sound assertion errors which is the key to stable audio and system.

 

The 3 error lines I listed in the README.txt is "normal" for the Mikey driver for now.

It isn't finding a device (which we don't have presumably).

You shouldn't see any other ones and if you are, it isn't a good thing.

 

If you are seeing other errors, make sure HDMI Audio is disabled in BIOS and see if that helps.

Post the errors your seeing as well.

 

The SPDIF Input is mapped to the onboard header which you need an adapter for.

Hmm... I'll see what I can do, not sure how to disable an output when it is selected as an input but remember something like that in another layout.

 

There is no mistake, the device ID for the realtek 889 is the same as an 885.

It isn't the only chip from Realtek that shares a device id (some of their ethernet chips are the same way).

[stan78]

The 3 error lines I listed in the README.txt is "normal" for the Mikey driver for now.

You shouldn't see any other ones and if you are, it isn't a good thing.

 

Thanks for the quick reply.

You are absolutely right - I disabled HDMI Audio in BIOS and now I only have three lines.

 

Before:

	   Sound assertion "0 == pathMap_aDriverInstance" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 1302 goto Exit
   Sound assertion "0 != createAudioEngines ( fPathMap_aDriverInstance )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 114 goto Exit
   Sound assertion "0 == pathMap_aDriverInstance" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 1302 goto Exit
   Sound assertion "0 != createAudioEngines ( fPathMap_aDriverInstance )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 114 goto Exit
   Sound assertion "0 == pathMap_aDriverInstance" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 1302 goto Exit
   Sound assertion "0 != createAudioEngines ( fPathMap_aDriverInstance )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 114 goto Exit
   Sound assertion "0 == pathMap_aDriverInstance" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 1302 goto Exit
 Sound assertion "0 != createAudioEngines ( fPathMap_aDriverInstance )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 114 goto Exit
   Sound assertion "0 == fMikeyDriver" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 1036 goto handler
   Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAWidget.cpp" at line 2445 goto handler
   Sound assertion "0 != widget->setUnsolicited ( true )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDACodecGeneric.cpp" at line 850 goto handler

 

 

After:

 

	   Sound assertion "0 == fMikeyDriver" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 1036 goto handler
   Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAWidget.cpp" at line 2445 goto handler
   Sound assertion "0 != widget->setUnsolicited ( true )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDACodecGeneric.cpp" at line 850 goto handler

 

Thanks again for working on it. I will try to get the spdif adapter asap.

 

st

[stan78]

Oh damn....

I had Itunes open and some music playing. Then I sent my system to sleep for testing.

After waking up I literaly got thousends of sound assertion messages, over and over again.

Couldn't even reboot and had to do a hard reset.

 

This seems to happen all the time after sleep.

 

This is what I get:

 Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAWidgetALC885.cpp" at line 642 goto Exit
Sound assertion "0 != powerState ( &curPowerState )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDANode.cpp" at line 540 goto Exit
Sound assertion ""( kRequestStateCORB == fCodecRequest->state ) = CORB engine stuck or response was missing"" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDAController/AppleHDAController.cpp" at line 1804 goto handler
Sound assertion "0 != err" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/IOHDAFamily/IOHDACodecDevice.cpp" at line 129 goto Exit
Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDANode.cpp" at line 362 goto Exit
Sound assertion "0 != powerState ( &curPowerState )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDANode.cpp" at line 540 goto Exit
Sound assertion ""( kRequestStateCORB == fCodecRequest->state ) = CORB engine stuck or response was missing"" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDAController/AppleHDAController.cpp" at line 1804 goto handler
Sound assertion "0 != err" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/IOHDAFamily/IOHDACodecDevice.cpp" at line 129 goto Exit
Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDANode.cpp" at line 362 goto Exit
Sound assertion "0 != audioFunctionGroup->powerState ( &restorePowerState )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 244 goto handler
Sound assertion ""( kRequestStateCORB == fCodecRequest->state ) = CORB engine stuck or response was missing"" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDAController/AppleHDAController.cpp" at line 1804 goto handler
Sound assertion "0 != err" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/IOHDAFamily/IOHDACodecDevice.cpp" at line 129 goto Exit
Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAWidget.cpp" at line 1383 goto handler

 

Do you get the same errors ?

 

st

 

 

And as for HDMI, just tell me if you need a lab rat...

[netcastle]

You guys rock

[your mother]

Has anyone tried osx with ZOTAC GF9300-A-E? It's under $100 on newegg so I was thinking of picking it up.

[LJSeinfeld]

Sorry to bump, but I edited my original install post to include my installation steps -- sorry I didn't post them originally, it was late ...

 

Steps are:

Install method:

• Started from my working P5W setup
  
• Hooked up new build's drive via USB dongle, formatted the new build's drive, GUID, 3 partitions - 2 for testing, 1 for storage incase it works!
  
• Obtained "Nope" MBP unibody distro from usual places (my MPB is not unibody), Cloned distro to another external HD with Carbon Copy Cloner (Saves burning and re-burning Dual Layer DVDs if something doesn't work) Modified OSInstall.mpkg to skip model and bios revison checks.
  
• Ran OSInstall.mpkg off of the external HD that I cloned it to and installed OS X 10.5.5
  
• Installed Chamelon/EFI with Universal OSX installer (OneSeXytool), installed their "MOBO" package of kexts as well.
  
• Installed NVKush
  
• Repaired permissions of /System/Library/Extensions via terminal (or could use OSX86tools)
  
• Installed Signal64's DSDT.aml posted earlier in this thread
  
• Fired it up -- it booted!
  

[stan78]

Installed the nForce LAN driver from here: (0.62.9) http://forum.insanelymac.com/index.php?sho...125569&st=0 system hangs at boot (see attached pic).

 

I had the same problem. Saw the new version and just had to update.

Then I installed 0.62.7 again and that worked fine.

 

st

[bobisdead]

Sorry to bump, but I edited my original install post to include my installation steps -- sorry I didn't post them originally, it was late ...

 

Steps are:

Install method:

• Started from my working P5W setup
  
• Hooked up new build's drive via USB dongle, formatted the new build's drive, GUID, 3 partitions - 2 for testing, 1 for storage incase it works!
  
• Obtained "Nope" MBP unibody distro from usual places (my MPB is not unibody), Cloned distro to another external HD with Carbon Copy Cloner (Saves burning and re-burning Dual Layer DVDs if something doesn't work) Modified OSInstall.mpkg to skip model and bios revison checks.
  
• Ran OSInstall.mpkg off of the external HD that I cloned it to and installed OS X 10.5.5
  
• Installed Chamelon/EFI with Universal OSX installer (OneSeXytool), installed their "MOBO" package of kexts as well.
  
• Installed NVKush
  
• Repaired permissions of /System/Library/Extensions via terminal (or could use OSX86tools)
  
• Installed Signal64's DSDT.aml posted earlier in this thread
  
• Fired it up -- it booted!
  

Thx a lot i got it working !!

 

have a great day

 

bob

[LJSeinfeld]

I had the same problem. Saw the new version and just had to update.

Then I installed 0.62.7 again and that worked fine.

 

st

Thanks- Gonna try that version next

 

Thx a lot i got it working !!

 

have a great day

 

bob

Glad something I posted here actually helped someone!

 

Signal64

 

Installed the audio driver you posted, I have audio now (thanks). Here's the errors I'm getting for your reference:

1/11/09 4:44:58 PM kernel Sound assertion "0 == fMikeyDriver" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDADriver.cpp" at line 1036 goto handler 
1/11/09 4:44:59 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:44:59 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:45:00 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:45:00 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:45:00 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:45:01 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:45:01 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:45:01 PM kernel Sound assertion "0 == entry" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAEngine.cpp" at line 2626 goto Exit 
1/11/09 4:45:01 PM kernel Sound assertion "0 != result" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDAWidget.cpp" at line 2445 goto handler 
1/11/09 4:45:01 PM kernel Sound assertion "0 != widget->setUnsolicited ( true )" failed in "/SourceCache/AppleHDA/AppleHDA-158.4.39/AppleHDA/AppleHDACodecGeneric.cpp" at line 850 goto handler

Probably should note that I'm using the AppleHDA.kext taken from the MPB install CD (in the System folder of the CD) -- hope that is OK.

 

Many thanks to all that have contributed to figuring out this board. There's no way I'd be this close to a working system without your help and effort!

[Signal64]

See Stan78's and my posts. Just to confirm, did you disable HDMI Audio in BIOS?

 

And yes, sleep is an issue - damn - same situation as the ethernet.

[LJSeinfeld]

Tried putting the other 2gb of RAM back in my system... within 30 minutes it be came jerky and eventually unresponsive....

 

weird

[Signal64]

Go back and read my post about 4+ Gig.

[LJSeinfeld]

See Stan78's and my posts. Just to confirm, did you disable HDMI Audio in BIOS?

 

And yes, sleep is an issue - damn - same situation as the ethernet.

 

 

Yep- HDMI audio is disabled in the BIOS -- forgot to mention that...

The 4 gig issue I knew about, I was just curious to see what would happen and how long it would take--

 

As a side note, I was playing music through the speakers too at the time that the system totally hung.

[stan78]

Thanks for your answer

 

 

So, we can actually say that Gigabyte boards have these problems right now with no solution:

1) +2GB Ram and you get problems with shared memory graphics.

2) Sound and ethernet don't work after sleep

3) HDMI audio not working

 

Ethernet works for me after sleep.

 

So at the moment, this board is a pretty good base for a small htpc like I have. If you need

a machine to work on there are better solutions atm. But I really hope that those issues will

be resolved soon.

 

st

[zchef2k]

Signal64,

 

Where are you looking to solve this shared memory issue? Has anyone tried to manually set the iGPU Frame Buffer Control to 256M rather than "Auto"? Would this give the OS the impression that 256M is all it has to use, no more, no less?

 

I have been doing some digging and have found a couple of kernel level declarations for vram memory usage.

 

For instance, in the IOKIT framework, there is an interesting comment in one of the header files, maybe something, maybe not.

 

in IOFramebuffer.h....Example taken from current 9.6 kernel source....

 

/*! @function getApertureRange

@abstract Return reference to IODeviceMemory object representing memory range of framebuffer.

@discussion IOFramebuffer subclasses must implement this method to describe the memory used by the framebuffer in the current mode. The OS will map this memory range into user space for client access - the range should only include vram memory not hardware registers.

@param aperture The system will only access the aperture kIOFBSystemAperture.

@result an IODeviceMemory instance. A reference will be consumed by the caller for each call of this method - the implementatation should create a new instance of IODeviceMemory for each call, or return one instance with a retain for each call.

*/

 

virtual IODeviceMemory * getApertureRange( IOPixelAperture aperture ) = 0;

 

/*! @function getVRAMRange

@abstract Return reference to IODeviceMemory object representing memory range of all the cards vram.

@discussion IOFramebuffer subclasses should implement this method to describe all the vram memory available on the card. The OS will map this memory range into user space for client access - the range should only include vram memory not hardware registers.

@result an IODeviceMemory instance. A reference will be consumed by the caller for each call of this method - the implementatation should create a new instance of IODeviceMemory for each call, or return one instance with a retain for each call.

*/

 

virtual IODeviceMemory * getVRAMRange( void );

 

protected:

 

/*! @function handleEvent

@abstract Notify IOFramebuffer superclass code of events.

@discussion IOFramebuffer subclasses should call this IOFramebuffer method on certain power state changes.

@param event The event that has occurred:<br>

kIOFBNotifyWillPowerOff call before entering a state other than the maximum.<br>

kIOFBNotifyDidPowerOn call after entering the maximum power state.<br>

kIOFBNotifyWillPowerOff call before entering a state other than the maximum.<br>

kIOFBNotifyDidPowerOn call after entering a state other than the maximum.<br>

@param info None of the above events require additional info, pass zero.

@result an IOReturn code, safely ignored.

*/

 

 

Could this be where the kernel protects system RAM?

 

-Z

[LJSeinfeld]

A quick note to confirm that the nForce LAN driver 0.62.7 does work with my system, seems to be OK sleeps and wakes up fine. Driver can be found here:

 

So now that my system sleeps (which is a first for me in the Hackintosh scene). I've noticed that when it wakes up you need to re-introduce it to my USB keyboard by pressing the Z and ? keys (asks for the keys located next to the 2 shift keys).

 

Anyone else have that problem? -- Off to search for a solution....

 

Should also note that the same thing happens when I unplug/replug the keyboard... USB driver issue maybe? Keyboard is an old iMediaKey from macally... (going there next...).

[stan78]

So now that my system sleeps (which is a first for me in the Hackintosh scene). I've noticed that when it wakes up you need to re-introduce it to my USB keyboard by pressing the Z and ? keys (asks for the keys located next to the 2 shift keys).

 

Congratulations to your NForce Driver :-)

I have to tell you though that I keyboard is working without a problem after sleep. I already had a big MS

and some 5€ keyboard and they both didn't have to be reconfigured.

Sorry that I can't give you a solution.

 

st