Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About forch

  • Rank
    InsanelyMac Protégé
  1. Protools HD 8.0.3, HD2 PCI, X58 topic

    @update We exchange both PCI HD cards with the newer Native HD card. Mainly because recording is being done in Logic and only 8 ins and outs are available using the pro/acc HD cards. Just wanted to confirm that the Native card works like a charm. No problems at all, we exchanged every card on the fly, booted the hack, installed drivers, installed pro tools 9, and after a second reboot everything was detected (2x 192I/O's, 1x96I/O, SyncI/O). Cheers
  2. DSDT editor and patcher

    Is the DSDT Editor still being maintained? I have this weird problem where sometimes at the start of the first scope, e.g where Scope (_SB) should start, only the text [child] appears and the rest of the DSDT is missing. Is the code downloadable (SVN, git)? Cheers
  3. UPDATED 20.12. GenericBrightness.kext

    PEG3 is in the original extracted DSDT, you just got me thinking that I tried to overwrite it with the same address, cause P0P3 and PEG3 share 0x00030000. But chams graphics enabler inject it under PEG3.GFX0, also without any enablers the display0 is under PEG3, I just verified it again, also with a freshly extracted DSDT that the PEG3 method is present. I remember I tried months ago to inject values on all possible graphic sections, PCI0.P0P2.VGA, PCI0.P0P3.VGA, PCI0.GFX0, etc, because I couldn't really believe that PEG3 was responsible for the 330m card with all the other graphic spaces available, well the graphics worked only under the PEG3 space without any enablers (never used kext enablers anyway).
  4. UPDATED 20.12. GenericBrightness.kext

    Don't get me wrong, I am doing research, if this would be a linux machine, I would attach a separate distro to it, put this kernel in debug mode, attach kernels and catch everything there is to debug, but it's not linux and I'm damn unfamiliar with this whole OSX stuff and this flipp'in kernel .. I could't even get OSX in debug mode to start with, would lock up every-time, but that's a different story .. There is no output, no change in ioreg, nothing. System just freezes and hits panic, 7 out of 10 times the internal display gets scrambled, the HDMI is connected to a plain external 23" LCD monitor, I'm not able to test sound, also I have to reconfigure pins in VoodooHDA to get the HDMI digital outs, which fail at the moment. I'll be glad to hear any suggestions to see changes in the ioreg before the panic hits without scrambling my screen But I guess this is a dead-end, and don't get me wrong, your situation trying to solve this is the worst and I can only say thumbs up for the time you put into this and keeping the thread so active .
  5. UPDATED 20.12. GenericBrightness.kext

    Login in window funny enough has a delay of 2 or 3 seconds, after that the panic gets called. I can give you screenshots of the panic this time, don't know if it has any value to you.
  6. UPDATED 20.12. GenericBrightness.kext

    It does panic, but it doesn't log anything concerning the panic, when changing brightness I get these bytewise values brightnessmin 0, brightnessmax 1024, currentbrightness 0 brightnessmin 0, brightnessmax 1024, currentbrightness 64 brightnessmin 0, brightnessmax 1024, currentbrightness 128 brightnessmin 0, brightnessmax 1024, currentbrightness 192 brightnessmin 0, brightnessmax 1024, currentbrightness 256 brightnessmin 0, brightnessmax 1024, currentbrightness 320 brightnessmin 0, brightnessmax 1024, currentbrightness 384 brightnessmin 0, brightnessmax 1024, currentbrightness 448 brightnessmin 0, brightnessmax 1024, currentbrightness 512 brightnessmin 0, brightnessmax 1024, currentbrightness 576 brightnessmin 0, brightnessmax 1024, currentbrightness 640 brightnessmin 0, brightnessmax 1024, currentbrightness 704 brightnessmin 0, brightnessmax 1024, currentbrightness 768 brightnessmin 0, brightnessmax 1024, currentbrightness 832 brightnessmin 0, brightnessmax 1024, currentbrightness 896 brightnessmin 0, brightnessmax 1024, currentbrightness 960 brightnessmin 0, brightnessmax 1024, currentbrightness 1024 Is that what you need?
  7. UPDATED 20.12. GenericBrightness.kext

    hmm, here all logs from console, and dmesg log, at 05:54:10 I unplugged the HDMI .. dmesg.txt console.alllogs.rtf
  8. UPDATED 20.12. GenericBrightness.kext

    k, where did you log it? console.log? as in /var/log/console.log?
  9. UPDATED 20.12. GenericBrightness.kext

    Still kernel panic, when disconnecting and connecting, panic message gets scrambled but I think, as quickly as I could read, still the same backtrace.
  10. UPDATED 20.12. GenericBrightness.kext

    hope you meant the textual output (ioreg -l), can also give .ioreg files, have to upload them somewhere though. -- lol, thought so will update post in a few minutes -- here you go .. with.hdmi.ioreg without.hdmi.ioreg
  11. UPDATED 20.12. GenericBrightness.kext

    So, the GB.kext (82kb, from GenericBrightness.zip) which needs PNLF KP's when con./disc. HDMI. Kernel panic dependency backtrace is the same as in Mammoth KP screenshot. The one with the AppletSlider (GB.kext is 86kb in NoSlider.zip) does not KP when con./disc, though brightness controls only possible with AppletSlider, keys and Display slider don't work (as expected I guess). ioreg values are set, but brightness property does not change value when using AppletSlider (guess also as expected). Also boot time with both GB.kext's is between 6 and 10 seconds more, normal boot time is about 2/3 seconds starting from apple logo appearing (SSD). -- not using any brightness methods in PNLF -- the AppletSlider in NoSlider.zip is not a blend overlay right? It but does actually interact with the LCD? Anything else I can do or check? Cheers
  12. UPDATED 20.12. GenericBrightness.kext

    Yer I know, I just added LCD1234 on both LCD devices (PCI0.POP2.VGA.LCD and PCI0.POP3.VGA.LCD), LCD brightness now changes, counted visually 8 levels, which also is reported by dmesg: Acpi brightness levels:8, lowest brightness:10, highest brightness:100 Have to remove one or the other to see which one is getting called upon. -- I now also have the KP with disconnectin/connecting HDMI. K, LCD1234 is now in device PCI0.POP3.VGA.LCD, brightness 'works'.. now have to start re-reading the posts to see if I can have it working without GB.kext
  13. UPDATED 20.12. GenericBrightness.kext

    Hi, first of all, I have a GT 330M, I've managed to get sun icon appearing using keys 'scroll lock' and 'pause', Display slider is working and values are registered in ioreg, where max value is 0x400 min value is 0x0, when using brightness keys or Display slider (influences both) and refresh ioreg, the brightness value has changed as it should. but the LCD brightness itself is not changing. I'm not using GenericBrightness.kext or any of the drivers/code you posted here. I located my graphics section and its under PCI0.PEG3.GFX0, I modified bungo's nvidia injection (_DSM) with EDID, NVCAP, etc. Here is where all the stuff started to work but not changing the actual LCD brightness. Before bungo's modified nvidia injection I had the sun icon appearing (same brightness keys) but no values changed in ioreg (min=0, max=0 problem) and also the 'slider-stuck-at-100%' stuff, so I guess the pwm-info, etc was the key. After the modified nvidia injection, it also solved the problem with the HDMI connect/disconnect KP (same as yehia Amer is reporting only without GenericBrightness.kext, etc). I have reconnected and disconnected it tens of times and it is stable as hell. Also overscan option on ext. monitor does not KP (as before). @ivik If there is anything I can do to check some values why it's not KP-ing anymore, just say so. Then the brightness to actually change, something is missing, I've attached my DSDT.dsl. Are you willing to look at it for a few seconds and maybe you see something I don't? , all the DSDT edits can be found with "@hack" search string, but I guess only the PNLF and PCI0.PEG3.GFX0._DSM are useful. Cheers dsdt_.zip
  14. OSX on toshiba a660 166

    Yes it will, I'm on a A660-11M (i7-720QM, NV330M, etc) and I'm writing this message from OSX 10.6.5, from an external 23" LED monitor connected through HDMI. You can see my work here I have replaced the wifi with an Atheros AR9285 (which works oob with the 10.6.5 kexts). It seems the A660 series have all the same bios, I'm having a lot of troubles with it (not regarding the DSDT, those are pretty ok!), for example: at the moment I'm unable to boot from the HDD with any bootloader I tried (and all variations and techniques), I'm using a black nano usb (it's exactly 0.4cm's in width ). I'm unable to get 8 cores working (using 4 cores atm). I would recommend another thing, upgrade it to a cheaper 30GB SSD, it will save lots of time reinstalling and rebooting the system. Booting, counted from the first apple logo appearance takes about 3 seconds. Cheers
  15. Toshiba A600 series (maybe others)

    Yer, the iPortable Bootfix solves booting from USB, don't forget to tell us Stuart .. cause I think were the only people on earth with these laptops