Jump to content

guidorosso

Members
  • Content Count

    36
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by guidorosso

  1. I haven't had the freezing error (nvda channel exception) since reverting to a DSDT that doesn't have speedstep or the lpc fix enabled. Is it possible that the state values posted by mm67 for my q9550 were incorrect? Or could the problem have something to do with the lpc fix? Seems like it has to be one of the two. This is what I was using: Scope (_PR) { Processor (CPU0, 0x00, 0x00000410, 0x06) { Alias (PSS, _PSS) Alias (CST, _CST) } Processor (CPU1, 0x01, 0x00000410, 0x06) { Alias (PSS, _PSS) Alias (CST, _CST) } Processor (CPU2, 0x02, 0x00000410, 0x06) { Alias (PSS, _PSS) Alias (CST, _CST) } Processor (CPU3, 0x03, 0x00000410, 0x06) { Alias (PSS, _PSS) Alias (CST, _CST) } Method (PSS, 0, NotSerialized) { Return (Package (0x06) { Package (0x06){Zero,Zero,0x0A,0x0A,0x4820,0x4820}, Package (0x06){Zero,Zero,0x0A,0x0A,0x081E,0x081E}, Package (0x06){Zero,Zero,0x0A,0x0A,0x471C,0x471C}, Package (0x06){Zero,Zero,0x0A,0x0A,0x071A,0x071A}, Package (0x06){Zero,Zero,0x0A,0x0A,0x4618,0x4618}, Package (0x06){Zero,Zero,0x0A,0x0A,0x0616,0x0616} }) } Method (CST, 0, NotSerialized) { Return (Package (0x04) { 0x3, Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,,)},One,One,0x3E8}, Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,,)},0x2,One,0x1F4}, Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,,)},0x4,0x96,0x64} }) } }
  2. I added realtek1000sl.kext and ionetworking.kext and ethernet is working now.
  3. I was actually getting this same exact error! The reason was that I had another Chameleon USB stick plugged in and it was affecting the order of the drives. It thought it was trying to boot my OSX drive but in reality it wasn't, so it couldn't find the kernel (because it was booting from another drive). As soon as I took out the second Chameleon stick, it started working fine. I know it was booting from the right stick because I purposely put different themes on them.
  4. Hi Spike, Nope I actually ran the dmg from nvidia's site. This is the exact file: http://www.nvidia.com/object/GeForce_MacOSX_18.5.2f16.html I started getting this error once I enabled Speedstepping in my DSDT. I'm now running an older DSDT without the processor stepping states and without an LPC fix, which was required to get speedstepping working. Haven't had any issues yet, but I've only been running for about 4 hours now. I'll post results as more time passes, hopefully without further crashes! Edit: Meant to say I ran the .mpkg file on the dmg.
  5. Hi afd_sg, Thanks. I can certainly try this out, but I never had this problem with my old DSDT. I started seeing the problem after adding speedstep values and the LPC fix to my DSDT, even before switching to Aargh's DSDT. I'm trying to think if there's anything else I added in the process that could be causing this. I've deleted VoodooPState.kext, CPUi.kext, CPUInjector.kext, and OpenHaltRestart.kext. Any other ideas?
  6. Apologies for re-surfacing an old thread, but I am getting the same exact error. I cannot install the driver that you recommended as it says "No Driver Update Needed. This system already has drivers which support this NVIDIA graphics solution". I'm curious if you ever ran into the issue again? I'm running 10.6.2.
  7. Hi All, Just got the NVDA error again. Freezes my entire system. Whole screen flickers for a second and everything locks up except my mouse, which can still move. The OS is entirely unresponsive, force quit doesn't work, nothing works. It's just totally frozen, only option is to do a hard reboot. This is the last thing that appears in the console: 2/8/10 7:29:09 PM kernel NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error This started happening when I added my mm67's PStates to my DSDT and also added the LPC fix. Since then I've upgraded my whole DSDT to Aargh-A-Knot's cleaner version, with the modified PStates that mm67 posted for my processor. It's obviously somehow related to my graphics card, but I had never seen this until I added the PStates and LPC fix. I should point out that Speedstepping does seem to be working great. Processor is changing based on load and the temperature is significantly lower (idles at 38 degrees vs 51 without speedstepping). Kexts I'm using are: fakesmc IONetworkingFamily IOAHCIBlockStorageInjector LegacyHDA RealtekR1000SL
  8. Perfect, that's working. Thank you!
  9. Ben, I've never tried the Lifehacker bootloader, but if it's based on Chameleon 2 RC2 or above, all you have to do is add the following lines to your com.apple.boot.plist <key>GraphicsEnabler</key> <string>Yes</string> If that still doesn't work, check your DSDT PCI root. I had to change mine from 1 to 0 to get GraphicsEnabler to work. Search your DSDT for something that looks like this: Device (PCI0) // PCI Bus { Name (_HID, EisaId ("PNP0A03")) Name (_ADR, Zero) Name (_UID, Zero) You want to change the UID value to the opposite of what it currently is, either 1 or 0 (in the above case it is set to 0).
  10. I can't seem to find a IONetworkingFamily kext for Snow Leopard. Tried uninstalling the driver and running with RealtekR1000SL but ethernet doesn't work at all now (64 bit and 32 bit). Do you have a link? Thanks again for your help, appreciate it.
  11. Yep, I read up on that. Apologies for the poor choice of words. Didn't mean to say it was being detected "wrong", I should have said that it's detecting a different UUID from what I've been using. As you probably know, the motherboard has two ethernet devices. I disabled one and have been using the other, so I suspect the new bootloader was automatically detecting my disabled one. Do you happen to know how to tell it to detect the other device? Interesting about the kexts, hadn't seen those before. Will give them a try, thanks!
  12. Looks like ethernet works only if I boot in 32 bit mode. Could this be related to the Realtek RTL8111/RTL8168 driver I'm using? From here http://www.realtek.com.tw/DOWNLOADS/DOWNLOADSVIEW.ASPX?LANGID=1&PNID=13&PFID=5&LEVEL=5&CONN=4&DOWNTYPEID=3&GETDOWN=FALSE
  13. Ethernet works if I boot in 32 bit mode. Hmm, I wonder if this is related to the Realtek RTL8111/RTL8168 driver I have installed? Got it here: http://www.realtek.com.tw/DOWNLOADS/DOWNLOADSVIEW.ASPX?LANGID=1&PNID=13&PFID=5&LEVEL=5&CONN=4&DOWNTYPEID=3&GETDOWN=FALSE
  14. I just switched over to AsereBLN Booter v1.1.7 from Chameleon 2 RC3 and my ethernet is no longer working. DSDT is the same, no changes. I have ethernetbuiltin=Yes and also tried using my old PlatformUUID.kext with system-id=No. Any ideas?
  15. Yep, saw that. I'm using the Realtek driver, so that makes sense.
  16. Ok I've switched over to AsereBLN Booter v1.1.7. Waiting to see if this fixes display freezing. In the meantime, my ethernet isn't working anymore. I'm using the same DSDT posted above, which was previously working. Only difference is the new bootloader. I'm using the following kexts: fakesmc.kext LegacyHDA.kext PlatformUUID.kext (new booter was detecting wrong UUID. I also updated com.apple.Boot.plist with system-id=No)
  17. I'm trying Aargh-a-Knot's DSDT now with my cpu values and with PCI root set to 0. I'll see if your DSDT resolves the crashes. I've also attached your DSDT with my changes.
  18. Hi All, First off, thanks again for everybody's help! Now it seemed like everything was working fine, however I've started getting crashes with this new DSDT and with Speedstepping enabled. It appears to be a graphics card software error as my displays flicker and then everything freezes, apart for the mouse, which I can still move. The specific error I get when it crashes is 2/4/10 8:03:20 PM kernel NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error Obviously appears to be an nvidia related error. However, I never had this issue before and it started the same day I got my new DSDT and Speedstepping working. I'm attaching my DSDT. Anybody seen this before?
  19. I am also running VMware Fusion 3.01 and the network is fine in bridged mode. Both the VM and OS X work normally as long as the VM is running. Quitting VMware Fusion is the problem. Once I quit it, all my network stops working. If I re-open the VM (not just VMware Fusion), it starts working again.
  20. Hi All, I have noticed a bug in VMware on both my hackintosh machines, one running Snow Leopard and the other Leopard. When I quit VMware, my ethernet stops working entirely. It still appears to be working under System Preferences, but it just won't connect to anything (local or remote). As soon as I boot up my VM again, it starts working again. I can reproduce the same exact bug on both machines. Anybody else run into this?
  21. Interesting. Do you know if these work on 9800GTX+ cards? Btw, I would've also voted for nvidia, especially if you are considering dual booting Windows. In my experience, their drivers have been much more stable than ati's. Good luck with your build!
  22. I have no problems with sleep. My drive is a Sony Optiarc 24X DVD/CD http://www.newegg.com/Product/Product.aspx?Item=N82E16827118030 System Profiler reports it as a Optiarc DVD RW AD-7240S
  23. Hi All, I recently ran into an issue that was causing random crashes. Figured it's worth sharing in case anybody runs into the same problem. I was having really weird hang ups where I'd get the spinning beach ball while doing pretty much anything. The application I was using at the moment would hang, but I could still switch to different apps. Slowly it would start to spread to other apps until eventually everything was frozen, including Force Quit. Only way to get out of it was a hard restart or power off. It was completely random to the point that I was convinced it was a hardware issue, probably RAM. But I ran memtest and found no problems and everything else seemed to be fine. After countless tests and checks I found the following message in my console: NTFS-fs warning (device /dev/disk1s2, pid 42): ntfs_inode_afpinfo_cache(): AFP_AfpInfo data attribute of mft_no 0x642a6 contains invalid data (wrong signature, wrong version, or wrong size), ignoring and using defaults. It turns out this was the problem. I immediately ran CHKDSK under Windows, which had automatically detected that it needed to run. It completed successfully but I was still seeing this error in OS X. It pops up continuously as long as that partition is mounted. My other NTFS partitions don't have this error, and interestingly enough, this is the only partition that I had enabled native NTFS R/W on through my /etc/fstab file. I disabled the native R/W by deleting the fstab file, however the errors still popup. The only solution I've currently found is to unmount the partition every time OS X loads. I would completely remove the drive from my system, but I have Windows 7 loaded on it for work so I can't yet. I'll probably end up formatting it over the weekend. Anyway, I haven't had any crashes or hangs ever since disabling that partition. Been running for a week now without problems. My suspicion is that the Snow Leopard native R/W may have caused this. So watch out for that. Obviously there's a reason why Apple didn't enable this by default on NTFS drives.
  24. Looks like mm67's Scope PR code and Aargh-a-Knot's LPC fix combined on my DSDT did the trick! Removed VoodooPState.kext and I'm seeing the P States in CPU-i. Also my temperature is idling at 40 degrees Celsius vs the 58-60 degrees from before. Perfect!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.