Jump to content
InsanelyMac Forum

ktbos

Members
  • Content count

    56
  • Joined

  • Last visited

About ktbos

  • Rank
    InsanelyMac Protégé
  1. I have an Optiplex 9020 too. And I followed the same guide to get it set up in the first place. Mine is actually working pretty well (see below for the two issues). I hadn't tried two monitors until just now to test it out and they both work well. Functionality appears normal. The only weirdness was the menubar on the second screen wasn't opaque initially. After I clicked over to that screen it did turn opaque and now seems to be working fine. I only have one DisplayPort monitor, though. The other monitor is hooked in using a passive DP-DVI adapter which, I believe, effectively turns the jack into a DVI jack and therefore that may not be a real dual DisplayPort test. The monitor I have hooked in using a DP connection is running 1920x1200 and the second monitor is running 1600x1200. So what kind of connections did you use? If any adapters, do you know if they were passive or active? What was the resolution of your screens? Also, what MacOS are you running? 10.9.4? Also, a question for you: I have two issues with the setup. One is that I can't get wake to work and the other is audio. I haven't gotten a chance to work on the audio, but I've been burning up days on the sleep/wake issue. I just can't get it to work - it sleeps okay but when it wakes, the screen is either black (on the high res) or blinking grey (on low res). Can you report back whether you have sleep and wake working? And if so, what monitor set up you have? (how many, what connectors, what resolution, etc.) Thanks!
  2. Wow, okay, so trial and error it is. Very tedious. Fortunately, you can do it without the -x boot by leaving it out of the boot plist and entering it at the boot prompt like IntelCapriFB=4 That will make trial and error twice as fast! The IntelCapriFB option (and the other two) are indented under the VBIOS option in the Chameleon help. That appears to imply that the VBIOS option is needed for IntelCapriFB to work? What about GraphicsEnabler? I put the VBIOS=Yes and GraphicsEnabler=Yes into the boot plist so I wouldn't have to type them every time when testing. Also, FYI, my DSDT had a patch in it for GFX that was preventing this option from working. Before using Chameleon's IntelCapriFB option, I was getting the text hanging before the login screen because the DSDT was specifying a platformID that was incorrect. After removing the DSDT patch (and otherwise modified AppleIntelFramebuffer.kext), then booting gave me the black screen. That's when I was able to begin testing different PlatformID numbers with Chameleon.
  3. FYI, I used 'lspci -nn' and got the following output for my HD4000 (Dell Latitude E6430): VGA compatible controller [0300]: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 09) I was assuming this would translate to device 01660009 and therefore I would be able to use IntelCapriFB=9. Didn't work. I tried all of the other values and surprisingly, "4" worked for me. So either the rev number has nothing to do with the platformID (in which case I wonder how you determine what the platformID is short of trying all 12 options) or something isn't working with entering the number. Regardless, it's great that IntelCapriFB does get my video card working! Thanks for the feature!
  4. ktbos

    Pandora's Box OS X installer

    Sorry, but I have to complain about the way Pandora takes over Terminal. When I first ran Pandora, it said it wanted to adjust my Terminal settings. I said "no" so it ended. What? Okay, I tried again and this time said "yes". Within a blink, my Terminal settings were replaced with Pandora's and my computer rebooted - without warning, while I had lots of other things going on. I think it is crazy that Pandora needs special terminal settings in the first place. But if you really need them, you should do a much better job of explaining to the user what is going on and what will happen and give them a chance to exit out of other programs before rebooting!!
  5. I'm not fully working yet, but I think I have my problem figured out. I thought I'd share what I have found so far in case anyone else comes across the issue. (Or if somebody already has and wants to chime in with more info than I have figured out so far!) I have a working Hacintosh that's been running well now for 4 or so years. It's a Dell E520 and yes, it is getting a little too old to keep using, and yes, I haven't upgraded the OS because I'd like to upgrade the hardware. But hey, it works, and Apple still hasn't come out with a midline desktop computer. Today, after uninstalling some software, I rebooted. (I don't need to do that very often which is nice, so the last reboot was a few weeks ago.) Strangely, Mac Update started and said that it was updating my computer - I had seen it on the screen earlier today, but I had clicked "Not Now" and it had gone away. But I knew that the update was just a Security Update that had been bugging me for the last couple weeks so I let it go. The computer wouldn't come back up. The BIOS ran fine and Chameleon gave me a "boot done" and then froze immediately on the "\" "|" "/" "-". Hitting power button to shut it off and then again to turn it on gave the same results. Eventually I discovered that disabling one of the 3 hard drives did the trick. Fortunately it is not the system disk. It is my Time Machine disk. Apparently, Seagate drives have a known firmware bug that causes the drive to shutdown. In some cases, it fails to report to the BIOS at all ("BSY" error) and in other cases, it reports to the BIOS as a 0 byte size drive ("LBA" error). I believe I am seeing the latter and that Chameleon gets stuck when running through the disks and finding a drive that is zero bytes. If the drive is under warranty, you can have Seagate fix it. If it isn't, like mine, you can try the fix yourself. And I may do that. But for now, I wanted to post that what appeared to me at first to be a Hacintosh-related error on a Mac update turned out to be complete coincidence and it was actually a hard drive firmware bug that confused Chameleon.
  6. ktbos

    [GUIDE] Dell Latitude E6410

    Here's some info about Core Image, and by extension about Quartz Extreme: http://en.wikipedia.org/wiki/Apple_Core_Image I wrote that you may have been closer when it was crashing because that may be when you were getting the full graphics engine to start up, even though it may have crashed. It's like you are closer to driving a car when the car starts but stalls leaving the driveway than you are when you get on a bicycle and pedal down the street. But it's tough to tell since you don't know where the crash was - maybe you are closer now than when it was crashing - it was just my guess. And without the real full graphics engine working, a lot of other stuff won't work as you've already discovered. As for the NVidia - definitely not a POS. It is not standard for a Mac, that is true. But for Linux and Windows 7 it works great. These are the pitfalls of Hacintoshing and exactly why it's easier for MacOS to not have to worry about all the hardware that's out there. So the hard part is finding out how to make MacOS happy with the hardware as though it were hardware that MacOS was originally built to use and that's where you are stuck now. And where many people before you have been stuck too. So as you say, you've only been at it a week - you've done great for a week-old-newbie! If you do figure it out, that'll be really cool. But also don't feel bad because others have spent a lot of time before and haven't succeeded and it may not actually be as solvable as we'd all like it to be - so don't kill yourself at the expense of the other important things in your life too!
  7. ktbos

    [GUIDE] Dell Latitude E6410

    I'm not sure but I'm guessing you don't have CI/QE working. Is your menubar translucent? If not, then I think all you've got is enough disabled that you have it not crashing. I think you want to go the other way and get stuff enabled to fully enable the graphics. In other words, you may have been closer with the crashing than you are now. :-( Just guessing, though. And do keep posting your findings so others can comment on them.
  8. ktbos

    [GUIDE] Dell Latitude E6410

    What a fantastic guide!! Thanks for posting that here. It clears a lot off my to-do list! Can't wait to try it myself!
  9. ktbos

    [GUIDE] Dell Latitude E6410

    Peter, can you reply to the post here with the details on your E6410? Any spec details would be helpful. In particular, those that vary from my configuration (in the original post). And also, what version of Mac DVD are you trying to run?
  10. Cool! Always good to know it works with later versions.
  11. ktbos

    [GUIDE] Dell Latitude E6410

    You're welcome. Glad it works. I think the post from maleorderbride makes a good point about a new kext in 10.6.5 that causes graphics issues. And that probably impacts your integrated graphics too. As for the custom kernel, I believe it has something to do with the standard MacOS not working with the latest Intel chips. I can't remember where I got the kernel now but I do remember that there were different kernels compiled for different Intel chips. And I suspect to get 10.6.5 working without a panic, we'll need a new version of that custom kernel. Updates to the install guide (with new kernel for 10.6.5, graphics, and WiFi) are on my to-do list but frankly aren't very high. Sorry - still paying for the time I sunk into the original guide! :-)
  12. ktbos

    [GUIDE] Dell Latitude E6410

    Thanks, but I think we should hold the beer until we get the WiFi and the graphics fully functional with an easy install that doesn't have problems with updates!
  13. ktbos

    [GUIDE] Dell Latitude E6410

    Okay, so there are a number of differences between your specs and mine. For starters, make sure that GraphicsEnabler is off in Chameleon. Next, use your BIOS to shut off the WiFi, just in case that's an issue. The Voodoo audio shouldn't be the issue so I would worry about that secondarily. It's possible that the i7 makes a difference with the kernel but that seems unlikely. Your RAM shouldn't be a problem. Anyway, my bet is that it's the video that is causing the trouble since that's the most significant difference between what I have and what you have. One more thought is that there's a possibility that the Mac isn't hung but is actually working without video. And that the video will eventually start working. One way to check is to make sure that you can telnet/rsh in to the Mac from another computer even though the graphics will be out. If you can, and all appears well, give it as much as 15 minutes to see what happens. I had one hacintosh (not the E6410) that just needed to sort of settle it's video issues over a few minutes and I kept on interpreting the blue screen I saw as I would a Windows BSOD. I don't know if your apple logo screen is a similar issue - probably not.
  14. ktbos

    [GUIDE] Dell Latitude E6410

    What are your system specs?
×