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 anon2122

  • Rank
    InsanelyMac Protégé
  1. I managed to get my Powercolor 1GB 4670 working with QE/CI (as checked since Front Row opens, and dashboard gives the ripples when adding widgets). I used EvoEnabler to get it working with the 10.6.2 KEXTs for ATI4600Controller.kext, ATIFramebuffer.kext and ATISupport.kext This gives full QE/CI while running as a "4890" in About my Mac... I don't mind this, as it's working, apart from one thing. I can't get any 16:9 resolutions working. I tried changing the driver files to the latest 10.6.5 files and using EvoEnabler, and get a blue screen on boot (pale blue, like the aqua loading screen, just it stays there forever). I am using a 1920x1080 60Hz TFT on a DVI->VGA convertor, which works perfectly at the desired resolution in Windows 7 on the same PC. I have tried SwitchResX, which won't let me use 1920x1080 and simply tells me it is "Unavailable", according to the app... This is unbelievably frustrating, as I spent ages getting anything to come out the screen, and I only tried EvoEnabler in a moment of sheer madness and determination I am not sure what the cause of this is, but I am able to select a huge list of 4:3 resolutions, including those larger than my monitor, just not any 16:9 ones. Anyone got any ideas here? They would be much appreciated. Running 10.6.5, and I've tried just about everything I can think of, including the "Graphics Mode"="1920x1080x32". One thing to be aware of is that I'm currently using a modified PCEFi bootloader that claims to use Shrike framebuffer (I think... I will be trying the default one shortly to see if that gets me anywhere too). Cheers EDIT: I got it sorted. Turns out that I wasn't using SwitchResX correctly. For anyone who searches and finds this, try a custom resolution, using simplified "GTF" settings, at 1920x1080 or whatever, and saving. That worked for me.
  2. Dear All, Feel free to skip the first part of this, it is just background that could help pre-empt any questions. I was trying to get Snow Leopard installed on my Dell E520 PC today. After a lot of experimentation, I created a custom boot-132 CD that would boot my retail disc, and installed Snow Leopard 10.6 vanilla onto my PC. After install, I used my boot CD to start the main install, and got a successful boot, apart from graphics glitches indicating a non-compatible out-the-box framebuffer. By booting using the -x flag for safe mode, I was able to get going and set up my PC. I installed the latest PC EFI beta, and replaced the file '/boot' with the one from this page on netkas' site (beta booter). I added the following KEXTS to the /E/E folder: - FakeSMC (V2.5) - AppleIntelCPUPowerDisable - OpenHaltRestart - Dummy kext that injects my SATA RAID device ID into stock drivers Now, I could boot fine in safe mode, so I installed 10.6.2 using the combo (full file) update from the Apple website. It installed OK, and I rebooted. Here's where the problems start. I followed the instructions to edit my com.apple.Boot.plist file, and put it into my /Extra directory. I added the following to it : <key>Kernel Flags</key> <string>pci1</string> <key>GraphicsEnabler</key> <string>y</string> When I boot my PC now, I get the following, depend on what I do. Normal or verbose boot = Get kernel panic on 'ATIRadeonX2000.kext', after most of the boot process. Safe mode = System hangs at end of verbose boot screen (DSMOS ready, or something like that. Since I don't have DSMOS, I guess this is part of FakeSMC) Has anyone spotted something I have done wrongly? I have tried various beta booters, and various incarnations of yes, y, for the GraphicsEnabler property. I am using the stock 10.6.2 kexts, which apparently work for others using similar/same cards. Any help would be greatly appreciated.
  3. What will it take to get the 46xx cards to work with 10.6.2

    Yeah, fair point if the gurus are having the trouble too. I will try (if time permits) to get my SL partition set up again (digging out the boot-132 disc right now) Hope we can get this sorted, as I would really like to have a working 4670 on any OSX, but every time there is a revalation, there always seems to be a 'gotcha'
  4. What will it take to get the 46xx cards to work with 10.6.2

    I might be able to resurrect an old DVI monitor from a cupboard and give it a try at some point. Just to get things straight, to install the netkas drivers, I take it I need to -replace the file boot in / with the new one (beta booter or whatever its called) -add the kexts to the /Extra/Extensions directory (or /System/Library/Extensions) -check my dev id is in the kext (should be for 4670) -reboot and pray Unfortunately I removed my osx86 partition a while ago, so I might try and get a vanilla 10.6.2 going again (still got all the things I need, and I think I can remember how to do a boot-132 install). On another note, I take it everyone who has tried this unsuccessfully has updated to 10.6.2 and also installed the betabooter file. If not, that could be the problem, but I doubt so many people would miss it out. Just that on netkas' site I'm sure some people had it working on 4670.
  5. HD 4650 got picked up? What?

    I am looking at loading SL back on to my PC to try this. One thing though. I have 2xDVI outputs on my 4670, but two VGA monitors using DVI-VGA convertors. I'm not too fussed about getting both screens working, but I have heard that there can be problems with such adaptors. Anyone out there have any experience of this?
  6. What will it take to get the 46xx cards to work with 10.6.2

    I've got a Powercolor 4670 (1GB RAM, 2xDVI) model, and I wasn't sure whether it was worth putting SL back on (used to run it, but got fed up waiting for drivers for 4670). What I don't know is if there is any point, as both my monitors are VGA, using 2x DVI-VGA convertors. I have read about people needing to plug an 'empty' convertor into their PC to make it work, but does anyone know if you can actually get a picture through a DVI-VGA adaptor. Or, is there any external hardware device (preferably quite cheap) that pretends to be a standard DVI monitor to make SL work, but then gives the VGA monitor a converted signal so you get a picture?
  7. HD 4650 got picked up? What?

    Hi there, Unfortunately I have a feeling that this might not be the big break we all need. The problem that us 4600 series users face is that there is no working framebuffer for our cards. (if you look at some of my previous posts, you can see my trials with Motmot and Kakapo on the 4670) Not to try and put you off, but many people (including myself unfortunately) have tried to get these cards working, and we find that the monitor turns off when we get to the desktop, as the framebuffer is incompatible. If you try with only 1 monitor though, we might get somewhere, as AFAIK there is no way we would get dual monitors going as early as this. I don't have 10.5.8 iDeneb lite, so can't try this myself with exactly the same configuration as you. Do you by any chance have the file you used for the ati drivers, or a link to it so others can try this out too. I don't recognise the name atity as a driver, but realise you are not sure which one you used. Other than that, all we can do is hope this gets somewhere positive, as I would love to have my 4670 working, as I am sure everyone else here would like.
  8. HD 4650 got picked up? What?

    Wow. That looks interesting and very promising. I have a 4670 (very similar to your 4650) and I have never seen something like that. I didn't see any mention of QE/CI (Quartz Extreme or Core Image). Do you know if they are working. By the way, did you install any drivers or 'kext files'? The reason it shows up as a 4600 is that the 4650 is part of the 4600 family,and the hardware id of the graphics card determines that. A couple more questions though, if you are happy to answer them. 1) What distro or install method did you use, and what version? (eg. iPC 10.5.6 or boot-132 with retail 10.5.6) 2) Are you running Leopard (10.5) or Snow Leopard (10.6) 3) Did you do this yourself, or did you use a guide. If a guide, could you post the link, and if yourself, could you give a brief explanation of how you did it. 4) Last question, I know, lots of questions! Can you change the screen resolution from within OSX to a non-standard one from the 'Control Panel'. Sorry for all the questions, but this is _very_ interesting for me, as graphics driver support was the sole reason I switched back from OSX to Windows. I understand that you might not have knowingly installed any drivers. If this is the case, let me know and I'll try to guide you through copying the drivers and posting them online. This could be useful for the OSX86 community as a whole. EDITED: to fix typo of QE = Quartz Extreme, not Quartz Express as originally written
  9. Radeon HD4670

    Thanks netkas, At least we know now that the 4670 isn't working for a known reason (so perhaps a future framebuffer will fix it). By the way, does anyone know (have searched but couldn't find anything about ATI) if I can use my 'unsupported' 4670 with two monitors (I'm using VESA drivers with custom resolution through a config file that I've forgotten the name of -think it's com.apple.boot.plist, but not certain). And if so, is there a way to give each monitor a separate resolution. Thanks
  10. Radeon HD4670

    Hi, how did you manage to get this update. I presume you are referring to a pre-release version of the upcoming 10.5.7 update. I have a similar card (the 1GB Powercolor) and have been trying a few things to no avail, and have had similar problems. I think we really need someone in the know like netkas to make this work. BTW, to see other stuff I have posted, check out my other posts or look for the 4670 threads. HTH
  11. A Simple Guide to the 4830/4850/4870/4870x2/4890

    Thanks for the response. Good to hear that. I know that the current drivers don't officially support it, but I was trying to get it to work 'unofficially' with some alternative framebuffers, then thought 'will I even know if it does work?' FWIW, I tried Kakapo, Raven & Motmot to no avail
  12. A Simple Guide to the 4830/4850/4870/4870x2/4890

    Hi. Is there anyone who has found this too, since I am using a 4670 with VGA-DVI to connect a Dell Analogue TFT. If this is the case, sounds like I might need a new monitor. BTW, I tried both DVI sockets and also put an 'empty' DVI-VGA on the other port. Thanks
  13. ati radeon hd 4670

    Hi AROBASEFR, I have also got an HD4670, and am not able to get this natit to work. Should the default framebuffer be used (Motmot) or should I use Kakapo or Raven instead? Reason I ask is that on IRC a little while ago I was advised to try raven/kakapo and neither worked (but that was with a different natit) Thanks in advance
  14. ati 4670 memory 1024/ 1g ddr3 working with leo or not?

    No, not as far as I know at the moment. If you see http://www.insanelymac.com/forum/index.php?showtopic=157718 , I have listed my attempts and observations (I mention this only in case you are interested in trying anything out, in which case it may save you a few wasted attempts, or give you something to work on) Thanks
  15. Is this hope for HD4670 users...?

    Apologies in advance for the very long thread. I have the PowerColor HD4670 (1GB with 2 DVI sockets) and have been trying in vain for the last couple of weeks (and months ) in vain to get it to work properly (ie. QE/CI and acceleration). Recently, I spoke to a few people on IRC and it was suggested that I try the latest natit drivers, but with Raven and Kakapo framebuffers (instead of the default Motmot one). I edited the info.plist to change all references from "Motmot" to "Kakapo" or "Raven" (obviously only 1 at a time). I am relatively sure that I edited correctly, but when I booted with the kexts installed using kext helper, I got a kernel panic with either framebuffer. For the purpose of allowing others to reproduce this (if you think you can get this to work, please try), here is what I did... 1) Downloaded latest link to 48x0 drivers for 10.5.6 ( http://is.gd/li8r ) (I was using iPC 10.5.6 release) 2) Extract the pkg file to my desktop, then open it with Pacifier and extract the kexts to a temporary folder 3) Opened natit.kext in finder (Right Click > Show package contents) and opened info.plist in TextEdit 4) Performed a find/replace on "Motmot" with "Kakapo" 5) Saved the new info.plist to the desktop, then dragged it into the kext in finder and authenticated. 6) Added the kakapo.kext ( http://rapidshare.de/files/46067210/kakaraven.zip.html ) to the temp folder 7) Used kext installer to install all the kexts (including modified natit) to System/Library/Extensions - new files: ATINDRV.kext ATIRadeonX2000.kext ATIRadeonX2000GA.plugin ATIRadeonX2000GLDriver.bundle ATIRadeonX2000VADriver.bundle ATY_Kakapo.kext Natit.kext 8) Rebooted with -f to force rebuild cache. 9) PC will kernel panic on boot. If you delete the kexts in single user mode and then try again with raven, I found the same happened. #####BUT####### When I tried again without modifying the natit (by accident), therefore using the Motmot framebuffer, I didn't get a panic or other error, but my display was blank and powered off (ie. monitor led orange after grey boot screen). The PC was running, and I could verify this by the HDD activity stopping after ~20secs and the standby button spinning down the HDDs, but no display. Every 10 seconds or so, the display led would go green and then orange again, much to my delight and then frustration. Here is where I am just now: I am using a Dell 19" TFT with only a D-SUB input and a DVI-VGA dongle to run it. When testing, I tried plugging this in both DVI sockets, and also put an 'empty' DVI-VGA dongle into the other port and the switched them around to no avail. Could someone with a native DVI screen give this a shot (with the Motmot default framebuffer) and see if that helps, as I don't think I have one to hand. Thanks, and hope this helps anyone who is interested in trying a bit of experimentation. Credit to netkas, FunFactor and CycloneFr on #radeonhd channel on irc://irc.osx86.hu for most of this, but I rewrote it to try and spot any mistakes.