Jump to content


  • Content Count

  • Joined

  • Last visited

About ohpossum

  • Rank
    InsanelyMac Protégé
  1. ohpossum

    Shutdown problems

    My shutdown issues came from the AppleHDA.kext I was using. It was the one I used in my 10.4.9 install and was patched with Taruga's 1.16 op
  2. Single user isn't going to work either I don't think. If i was in his situation, I would format a USB stick as HFS+, put the correct IOUSBFam on it and boot the install DVD. Disk Util should show the key mounted (if not, mount it) and then copy IOUSBFamily over. Fix permissions and reboot. op
  3. ohpossum

    QT 7.1.3 update problems

    QT 7.1.3 completely killed the sound on my Dell D600. AC97Audio.kext could still be loaded, and I could adjust volumes and whatnot, but no sounds from any programs or the system. I think QT 7.1.3 makes radical changes to CoreAudio such that it doesn't work on SSE2 systems, and/or takes advantage of some instructions that SSE3 emulation just can't handle.. No amount trying to revert back to 7.1.2 worked. I borked my system up even more in the process of ridding it of 7.1.3. The only solution (for me) was to reinstall. So, word of warning, don't mess with QT 7.1.3 unless you have time reinstall if it messes things up terribly. op
  4. ohpossum

    CpuThrottler on intel based mac

    No, CPUThrottler requires Niall's ACPICPUThrottle.kext which will not load on real Apple Macs (kernel version problems) op
  5. ohpossum

    CPUThrottler2Beta2 released

    Saber, is it possible to share the source for CPUThrottler? I'm especially interested in the NSStatusBar stuff for the status-bar update (and possibly adding a menu). Thanks! op
  6. ohpossum

    borisbadenov ATI X1000-series Solution

    Since you've bypassed the whole IOPCIDevice discovery by matching on "display" instead of whatever the card's real name is (if it even outputs a name at all), I'm thinking that it won't be easy to have the system recognize the card. If I understand whats happening, you've tricked ATINDRV into loading even those there is no "ATY, Wormy" hardware by matching on anything with the PCI name "display". Therefore the whole process where the card gets discovered is skipped (and needed to be skipped in order for it to work). ATINDRV is a good, but very, very simple framebuffer for x1600/x1800 series cards. With each new update, Apple restricts the hardware a little bit more, so I guess it makes sense that Munky's x1800 works under 10.4.5, but not 10.4.6 I wish someone with some real knowledge of IOKit graphics could chime in.. op EDIT: I think my terminology has been all wrong. I've mixed Framebuffer for Driver.
  7. ohpossum

    borisbadenov ATI X1000-series Solution

    Crazy, 4.2.4 is 10.4.5 and 4.2.6 is 10.4.6 EDIT: I got ATINDRV to load at boot. It still makes no sense that the damn kext would load during boot, but wouldn't load by hand later???? The "bar-code" vertical lines people have described is probably incorrect timings (or incorrect everythings) for the particular non-x1600 video card. If you get the vertical lines, reboot into single-user and do a kextstat, ATINDRV should be there. The fact that the driver doesn't even recognize the card even in working systems says something to how single-purposed it may be. Getting correct communication to cards that are waaaay off from an x1600 will be....maybe impossible?? I hope I get proved very very wrong op EDIT2: Has anyone tried dual-link yet?
  8. ohpossum

    borisbadenov ATI X1000-series Solution

    I am going to be very surprised if this works for anything put an x1600 (and probably not all x1600s). I bet ATINDRV has some binary checks for the correct dev_id and its only got timings for a few versions of x1600. Perhaps I'm wrong, but isn't ATINDRV's lack of support the whole reason for Callisto? Are they not both low level framebuffers? I'm still trying to get my head around the whole IOKit architecture...(I'm not a developer and don't pretend to be one. I'm just trying to understand how all this stuff works) I'm still baffled on how a kext that shouldn't even load could make so much difference. Could someone who has this working do a kextstat and post whether ATINDRV is loaded?
  9. ohpossum

    borisbadenov ATI X1000-series Solution

    Can someone who has this working copy the output of "kextstat | grep ATI". If I try "sudo kextload -t ATINDRV.kext" with either the 10.4.4, 4.5, or 4.6 versions, I get this error: kernel extension ATINDRV.kext has problems: Validation failures { "Kext has a kernel dependency prior to version 6.0 and CFBundleVersion does not match executable's MODULE_VERSION" = true "Kext has a kernel dependency prior to version 6.0 and CFBundleIdentifier does not match executable's MODULE_NAME" = true } Now, I can edit Info.plist to resolve these errors, but those edits aren't in Boris' initial steps. I don't understand how ATINDRV is actually doing anything if its failing to load. For those that have gotten this to work, what happens if you don't do the ATINDRV changes? Thanks op
  10. To anyone reading this thread: Understand the difference between MiniPCI and MiniPCI EXPRESS!!! read about MiniPCI EXPRESS: http://www.dell.com/content/topics/global....=us&l=en&s=corp The two technologies are *not* interchangeable. Don't get stuck buying hardware that won't work because you don't understand what you need. op
  11. ohpossum

    [HowTo] Broadcom wireless cards in 10.4.3

    You only have to do this step if your onboard ethernet isn't detected or you only have one network interface (the wireless one). The process that does the "baseball diamond" signal strength meter is stupid and always assumes the wireless interface to be the 2nd interface in the laptop, so it only works if the interface is en1. *If your onboard (wired) ethernet is already working you shouldn't have to do this step* op
  12. ohpossum

    ALPS Glidepad beta driver

    Some interesting results: After hearing suleiman had a pointerstick and a trackpad, I took my keyboard out of the laptop to find the ribbon cable to my pointerstick had broken. I never used the pointer, so I never noticed. I yanked a keyboard from another laptop at work and with it in place, the Darwin trackpad kext behaves differently. Without the pointer, the kext would't load at all. With the pointer, dmesg shows: "ApplePS2Trackpad: ALPS GlidePoint v4.34". With the pointer I have a Trackpad sys-pref menu where I can change mouse-speed, and enable/disable tapping. Now then, after loading phb's latext kext (the FFScroll core one), without the ponter, would show "ApplePS2Trackpad: ALPS GlidePoint v4.50" at boot. With the pointer, it shows "ApplePS2Trackpad: ALPS GlidePoint v4.34" at boot. Unfortunately, neither try worked. Both times the touchpad was unresponsive. I'm guessing I luckily happened to grab a keyboard with a different model of GlidePoint that the Darwin kext can deal with.. phb, if you're up for some debugging I can meet you on irc.... op
  13. ohpossum

    ALPS Glidepad beta driver

    Thats a good question. With your latest Trackpad kext installed, ioreg reports this: | | +-o ApplePS2MouseDevice <class ApplePS2MouseDevice, registered, matched, active, busy 0, retain count 7> | | | { | | | } | | | | | +-o ApplePS2ALPSGlidePoint <class ApplePS2ALPSGlidePoint, registered, matched, active, busy 0, retain count 9> | | | { | | | "JitterNoClick" = 0 | | | "HIDPointerConvertAbsolute" = <00> | | | "IOClass" = "ApplePS2ALPSGlidePoint" | | | "TrackpadScroll" = 0 | | | "TrackpadHorizScroll" = 0 | | | "USBMouseStopsTrackpad" = 0 | | | "Dragging" = 0 | | | "CFBundleIdentifier" = "com.apple.driver.ApplePS2Trackpad" | | | "IOProbeScore" = 1000 | | | "HIDPointerResolution" = <00006400> | | | "IOMatchCategory" = "IODefaultMatchCategory" | | | "Use Panther Settings for W" = 0 | | | "HIDPointerContactToMove" = <00> | | | "HIDPointerAccelerationSettings" = (<00000000>,<00002000>,<00005000>,<00008000>,<0000b000>,<0000e000>,<00010000>) | | | "PalmNoAction Permanent" = 0 | | | "JitterNoMove" = 0 | | | "HIDScrollAccelerationType" = "HIDMouseScrollAcceleration" | | | "HIDSubinterfaceID" = 2 | | | "IOProviderClass" = "ApplePS2MouseDevice" | | | "Clicking" = 1 | | | "DragLock" = 0 | | | "Trackpad Jitter Milliseconds" = 192 | | | "PalmNoAction When Typing" = 0 | | | "TwofingerNoAction" = 0 | | | "HIDKind" = 2 | | | "HIDVirtualDevice" = No | | | "HIDPointerAccelerationType" = "HIDTrackpadAcceleration" | | | "OutsidezoneNoAction When Typing" = 0 | | | "HIDInterfaceID" = 5 | | | "HIDPointerButtonCount" = 2 | | | } Nothing in the output resembles a device ID to me. Perhaps the IOProbeScore? Another interesting thing, when using the old Darwin PS2Trackpad.kext, it loads com.apple.driver.ApplePS2Trackpad at boot, but then eventually fails and disappears from kextstat. I'm thoroughly confused... op
  14. ohpossum

    ALPS Glidepad beta driver

    I removed kextcache and forced a re-cache with -f at boot. Still get this: Set Timeout Starting Set Timeout to loop Failed 0 Set Timeout to loop Ending Click Timer Starting Add Click Timer to Work loop Failed Set Timeout to loop Ending ApplePS2Trackpad: ALPS GlidePoint v4.50 for what its worth, none of your builds have worked with my Alps Glidepoint on a Dell Lat D600. All of them enable the Trackpad menu in System Preferences, but all have no response to pad input. This newest version is the only one to show the loop errors. Also the PSTrackpad.kext in Maxxuss' PS2Controller.kext works fine with my trackpad, but I have no Sys Pref menu with his. Strange, huh? op
  15. ohpossum

    ALPS Glidepad beta driver

    Thanks for the hard work on this! I tried your latest build and unfortunately got this: Set Timeout Starting Set Timeout to loop Failed 0 Set Timeout to loop Ending Click Timer Starting Add Click Timer to Work loop Failed Set Timeout to loop Ending ApplePS2Trackpad: ALPS GlidePoint v4.50 com.apple.driver.ApplePS2Trackpad is loaded, but it doesn't respond to any trackpad input at all. Can you provide any input on where I should look to troubleshoot this?? Thanks! op