Jump to content
InsanelyMac Forum

Sapricot

Members
  • Content count

    19
  • Joined

  • Last visited

About Sapricot

  • Rank
    InsanelyMac Protégé
  1. I'm not sure this is stated often enough, so I'll say it again: You rock, MAJ! (I'm on 10.6.7 on a new ssd I got – install was a breeze just cloning my raid install and running the script, then adding back my dsdt.)
  2. Maybe you should've tried putting RealtekR1000SL.kext in /S/L/E instead? It might work even when it doesn't in /Extra. Something else to consider: Perhaps your KP:s are related to using an older bios version? Sometimes the smallest thing can cause unexpected behavior. And d00d actually writes this about his pre-modified dsdt: "derived from GA-EX58-UD5 and BIOS F9m through F12". So maybe your problem is bios F7.
  3. CruisAr: Nice website you've got there man! My dad has been to Ghana twice (I was abroad myself both times so I couldn't come), having a great time and only catching a little bit of malaria
  4. rumz: Nope, just the one. Would be nice with two, but I a) don't really *need* it, and can't buy a decent monitor where I live now (Mongolia), at least not for a decent price. Thanks to Spaces and Exposé, I have a pretty smooth workflow going. Regarding graphics cards: I've heard good things about 5870, considering Apple uses that card in Mac Pro. I think with the latest chameleon 2 rc5 it might actually work ootb, though you shouldn't take my word for it (haven't researched it, just seem to remember reading something about it).
  5. rumz: I don't know about the 460 (though it seems that there is at least experimental support for it), but the gts 250 is, as far as I know, just a rebranded 9800 gtx+, which is the same card I have and with which I have no problem running some pretty graphic intense games (including running Dragon Age through Parallels). I don't know why you would prefer to use an EFI string instead of Graphics Enabler, though I don't see how it could cause your problem. And regarding the outputs: My card has one dvi, one hdmi and one s-video connector and they seem to work fine. Though my stupid display thinks it's a tv if I use dvi (limiting it to 1080p) so I have to use Apples dvi to vga adapter to get 1920x1200.
  6. septicdeath: You seem to have run into the same problem I and Josvdp have already encountered. Some boot loaders just make the UD5 freeze at POST or, as you noticed, if you plug it in after cham starts. Try doing the stick with DD's script and then "update" to another version of cham, for instance r426 that has been working for me. If it works, you can just keep it for the install and then do the actual install on the internal hard drive using DD's script and the newest version of cham. Edit: Three minutes! You beat me by three minutes, Josvdp
  7. Thanks for the suggestions, but it doesn't work. I don't really need this to work, but it's annoying to be so close to a 100% working system, I just want to do it for the hell of it. Are you using a modified dsdt with the legacyhda you're using now? If so, could you post your "Device (HDEF)" section? --- EDIT: I just tried opening up my case again and noticed I had AC97 plugged in and not HD Audio, so I changed that and tried again and guess what? Now it notices the headphones. But now there's another problem: it makes crackling noises that change when I turn the plug around. Interference? Problem with the actual plug? I have no problem with the green sound out on the back. Maybe it's time I just plunk down 10 bucks and buy a usb sound stick --- P.S. On a different topic, I ran the latest version of DD's script, since he seems to have fixed all the raid bugs now and it's much easier to let the script install a new bootloader than doing it manually. Installed r702 on my apple raid and it boots up just fine. Thanks for all your hard work Maj!
  8. Oh that's interesting... maybe I'll try r691 on the raid. If the problem is with usb as it says, then any bootloader on an internal sata drive should be fine. Thanks for mentioning that! As for dsdt, I'm using d00d's premodified dsdt.aml (this one), but I also recently dared to venture into modifying it myself to fix the sound after I updated to the newer LegacyHDA mentioned in his guide (I was hoping to get my front headphone jack working, but still no luck with that... I might've plugged it in wrong on the motherboard, or it might be broken).
  9. Can't say I'm glad to hear someone else having the same issue, but it's good to know it seems to be a real issue and not just me farking something up. If you want "Generate C-states" to work, I think you need to have a newer version of cham2. If my luck with r426 is any proof, you could try that version. With D00d's dsdt (slightly tweaked for audio with a newer LegacyHDA, but otherwise identical), my setup works like a charm with 10.6.6 with only FakeSMC and LegacyHDA in Extra and RealtekSL1000 in /S/L/E. One note if you run an Apple Raid setup like me: Make sure you copy over the new mach_kernel from / to the raid helper partitions after you update to 10.6.6, you could have some weird problems otherwise (I think...)
  10. Thanks, but of course it's GUID. How else would it start up fine with r426? I just tried going back to that and it works like a swiss watch. It's really strange that certain versions work and others don't. I think I'll try another newer release, just not r691.
  11. I ran into something quite strange again a couple of days ago. Last time I wrote here, I had just solved my installation problem. The solution to getting my usb disk to actually let the computer start and not stall on POST was to install Chameleon 2 rc5 r426 (earlier versions made the computer stall at POST, I couldn't even get to BIOS settings with the drive plugged in). Now, feeling a bit like experimenting, I tried to install r691 on the same external drive that I used to install to my internal raid setup (don't want to risk my working install not working anymore – this computer is used for work). And the same problem came back! If I start the computer with the usb drive plugged in, it hangs on POST (I forget the number, but it's "initializing usb" so obviously has something to do with the drive). I am completely dumbfounded as to how a certain bootloader installed on a drive can make the computer fail POST. If anyone has an idea what's going on here, I'd be very happy to hear it.
  12. Oh I see, well yes, I think you should. However, I don't understand why you would want to have the hazzle of starting through a booter like that every time when your hardware supports a completely functional install. To do that, you should create a boot drive from your usb stick. It's option 15 in the script.
  13. I'm an expert by no means, but I think you might have selected the usb drive as install location in the script (in the first step, before you reach the menu). To install kexts, you need a target drive with OS X installed. If your efi-x install works, you should be able to run the script on that install, installing the boot loader and kexts and such. Then make sure you remove the efi-x before starting again, and I think it should work. I don't know if efi-x installs anything, so if it does, it might screw things up. But it's worth trying at least. Just make sure you have a backup of your important documents.
  14. Success! After much tinkering and thinking and reading and trying different things, I have managed to get my SL installed on a software raid0 on my two WD 1TB drives. Here's what I had to do (simplified): 1. Install SL on USB drive using DD:s script with C2RC5 r426 bootloader and d00d's modified DSDT.aml. Only kexts are fakesmc, legacyhda and realtek1000 (haven't actually tested either sound or network yet, so might have to tinker extra with those). Native power management and cstates seem to work fine. Changed com.apple.boot.plist to disable GUI and add Graphics Mode. 2. Boot said drive. 3. Format raid and install boot loader manually using this guide: http://www.insanelymac.com/forum/index.php?showtopic=160467. Added raid drive's UUID to kernal flag in com.apple.boot.plist on the helper partitions. 4. Copy mach_kernel from / to raid helper partitions. 5. Clone startup drive to raid drive. 6. Remove Extra from raid drive. And there it is. Somehow, older bootloaders (pcefi and c2rc4) won't even let me pass post to enter bios (no idea why), but with rc5 r426, everything seems just peachy so far. Gonna try the sound and network, and sleep and such now to see how stable it is. But at least I'm up and running now. Big phew on not having any hardware problems :-) Update: Turns out neither sound nor network worked. I had to change LegacyHDA to another version and put the realtek driver into /s/l/e. Sleep works as expected.
  15. Jon: Well, I just read that installing SL from Leopard is a big hassle, but more importantly, I want to reformat my internal drive to make a raid for SL, which kind of makes it hard to install from it. But thanks for the suggestion. As for my problem: I figured out what was causing the no keyboard issue in Chameleon. Sometime during my trial-and-error I had switched off usb keyboard and mouse support in the bios. This of course didn't prevent me using it to enter bios or using them in my old install, but it was needed for Chameleon. Now I ran into a new problem though. Chameleon loads up the boot drive, but hangs during the startup process (it tries to creat ramdisks for /Volumes and other folders, but fails). I'm now trying another approach (making the "boot disk" a full install of 10.6.4 from my SL-running MBP). We'll see how it goes.
×