Jump to content

lebidou

Members
  • Content count

    136
  • Joined

  • Last visited

About lebidou

  • Rank
    InsanelyMac Geek

Contact Methods

  • Website URL
    http://en.gael-philippe.fr

Profile Information

  • Gender
    Male
  • Location
    Fr
  1. Hi, I had the same issue: hopefully, you have a backup of your kexts, so reinstall the pre-graphics update ones, (in theory, reapplying plan3r package should be fine).
  2. Hello, the trick from my previous post worked fine again for me. If it doesn't, try using the kexts you had working in 10.6.3, it might work just fine. The 81FA60720000 string appears two times, I replaced them both, and noticed nothing wrong. As I can't test the patch for 7280 and 7288 cards, I won't post any patched kext, I'll let someone who can test do it. I hope it will help you.
  3. lebidou

    Mobility HD4XXX thread

    You do realise that this has already been tried lots of times since 10.4.8 came out in 2007, right ? Mobility cards are known not to work because Apple is using a slightly modified LVDS connector. From that point, the only way to get it working is a new driver, specifically designed for our cards (say hello to Dong's RadeonHD.) I take the risk to repeat myself : you won't go anywhere trying different framebuffers. The kexts that deal with hardware, tune outputs, set crtcs registers, are the ATIxxxxController.kext. If there is something to do with Apple's kexts, it is patching the ATIxxxxController.kext binaries, not playing with your DSDT.
  4. Sorry for imprecision, only the ones at offset 0x2D682 and 0xB0D58 should be replaced. Actually you should look for 81 FA 60 72 00 00 and replace it by 81 FA xx 72 00 00 (where xx is either 88 or 80, according to your id). I hope you'll get it back this time. edit: I'm using vanilla ATIRadeonX1000GA.plugin, there is no need for replacing it.
  5. lebidou

    Information on VESA modes in ATI&NVIDIA bios

    You should try arch=i386, I'm not sure arch=x86_32 is still used since it's not an official architecture name. For the resolution limitation, it seems to be due to VESA implementation in the motherboard's BIOS. It's an issue that has already been encountered. I'm currently working on solving it, along with the so called 'bottom bug' on Nvidia cards.
  6. lebidou

    Mobility HD4XXX thread

    I have an X1900 Mobility card with LVDS which should be working with Wormy (it has LVDS support.) Except it doesn't since 10.4.8. It's impossible to recompile Apple's framebuffers since they're closed source. That's why Dong started the RadeonHD project, to have an open source driver. The problem is he did it alone, and had a really hard time getting any help from other developers. It took Dong's two plain years to achieve what's done, and there is still a lot to do. If you want to have native resolution in 64 bits mode, you can use the patch I made for chameleon (see here.) You may experience mouse glitches and surely won't get acceleration, but it's an alternate solution I've been working on since I don't know for how long the old ATINDRV.kext I use (incompatible with your card) will work with newer systems. In snow leopard, output support (LVDS, DVI, ...) has moved to the ATIxxxxController kexts, ATIFramebuffer being more generic. I don't think you'll get anywhere playing with the ATIFrambuffer Info.plist. The only remaining solution would be to reverse engineer the controller kexts, which would take a lot of time, and result in heavily Apple dependant solution. Or, of course, pursue Dong's effort. Don't take me wrong, I'm not trying to discourage you or anything. But since you are requiring informations, I'm just telling all know about the subject.
  7. lebidou

    Mobility HD4XXX thread

    hello, ATM the only solution to get resolution changing in SL for Radeon HD moblity cards is Dong's RadeonHD Framebuffer. It is a framebuffer itself , so it doesn't use any Apple defined framebuffer (Motmot and al). You are right assuming that's because of the LVDS output. Apple's framebuffers don't handle outputs dynamicaly and thus don't set correct settings for Mobility cards. Unfortunatly, Acceleration on HD2xxx series and above requires an Apple framebuffer and won't work with RadeonHD. The reason is simple, Acceleration kexts call a Framebuffer function that is not implemented in RadeonHD. This function has to be reverse engineered, which easy to say, harder to do. I hope I answered your questions, and I'm sorry to bring bad news. Have a nice day.
  8. Hello, I successfully got 10.6.3 to work on my ATI X1900 Mobility (0x7284). How did I do it : -get an Hex editor, like 0xED. -make a backup of your ATI kexts, copy them somewhere for editing. -remove ATIxxxxController kexts, ATIFramebuffer.kext and ATISupport.kext -on your 'edit copy', set owner to 501 ( " sudo chown -R 501:0 ATIRadeonX1000.kext " ) -right click ATIRadeonX1000.kext, and select show package content -in folder Contents/MacOS, open RadeonX1000 file with your hex editor -look for 81FA60720000 in hex content and replace it by 81FA88720000 if your devid is 8872, 81FA80720000 if it's 7280 -save the file and add your devid in Info.plist -install the ATIRadeonX1000 ... .kexts with Kext Helper, Install ATINDRV and/or ATIRNDRV from the package in the first post. -repare permissions, touch Extensions and reboot. The only thing I'm not sure about is the ATINDRV/ATIRNDRV because I don't use the same as you. But since mine comes from 10.4.7, I don't see why the ones provided by Bronya wouldn't work. Hoping it helps a bit.
  9. lebidou

    Information on VESA modes in ATI&NVIDIA bios

    Hello, I checked, I don't think Integrated chipset will be supported because of the lack of documentation from the manufacturers. The patch uses a functionality in Intel Host Controllers to unlock the vBios image in the system memory. Without documentation, it's impossible to tell if this same functionality is available for other chipsets. If someone knows, information is welcome. The main goal of this isn't just to get chameleon to the native resolution, it's to have native resolution in MacOS since the first boot after installation (and maybe during installation), before you've set up GraphicsEnabler, messed with your kexts and all. And to keep native resolution if you have to disable GraphicsEnabler for a while... To have native resolution, no matter what. Also this is the only way for me to have native resolution in 64 bits mode on my Radeon Mobility. Note that it worked on a Nvidia 9800 and an ATI X1900 Mobility, other nVidia cards don't set the mode yet, and it makes ATI drivers crash with HD3xxx and HD4xxx (HD2xxx is untested, X1300 to X1900 should be working fine though). It is still work in progress. @phroz, loading your vbios in the registry with VBIOS/VideoROM/etc won't help, this is for OS X drivers, later in the boot process. To set native resolution from boot, you need the patch I'm working on, or to flash your card. If you'd like to test the patch, it hasn't been tested on GT1xx, GT2xx series. And the EDID bug isn't in cause. There are already testers for nvidia 7xxx, 8xxx, 9xxx and ati HD3xxx and HD4xxx. If you don't have one of these and/or if you have a laptop, I'd like to know how it behaves on your machine. I hope it clarifies things a bit, have a nice day.
  10. lebidou

    Information on VESA modes in ATI&NVIDIA bios

    It hasn't been tested on those kind of systems. It has been tested on my ATI Mobility X1900 (MXM, not integrated), and on Desktop NVidia 9800GTX+ (working), 8800GTS (didn't work) and 7300GT (VGA seems ok, DVI not). Pre ATOMBIOS ATI cards won't work (ie. pre X1000 series). There are 3 conditions for it to work: -Have an Intel Chipset that doesn't belong to the 5 series (you can know that with lspci) -The vbios must be located at address 0xC0000 (it usually is) -The bios must return an EDID to get native resolution (and have native resolution in it) So please test and report indicating you graphics model and chipset. Thank you for testing.
  11. Is it a Mobility card ? What kind of connector are you using (internal LVDS, DVI, VGA, HDMI) ? Did you try with another connector ? It says it sees the "Uniphy" connector but don't detect a display, have tried with another display ? Surely Dong can answer that: are desktop card supported by RadeonHD? I think it was first intended for mobility with LVDS connectors but can't be sure about that.
  12. Hello, It's hard to tell… maybe the EDID doesn't match your panel exactly. You see, EDID doesn't depend on the graphics card, but on the panel. If the EDID you entered doesn't match exactly your panel it may lead to unexpected behaviour. You should try to get your own EDID from a linux live CD with read-edid. IMO it's more reliable than some EDID grabbed from another laptop. What happen if you boot in verbose mode (-v a boot prompt) ? Do you see the panic message (with a lot of numbers and stuff) ? A picture of it would help for debug, particularly to know if it actually comes from RadeonHD or something else, and witch function causes panic. Does it always enter GUI when debug mode is on (see plist file) ? Does it work with an empty EDID value ? Do you still use an Injector (ATY_Init, ATILead, ATIinject, ATYinject, Natit…) or gfx string, or DSDT patching ? Did you remove ATIRadeonX2000 kexts ? Could you post the result of RadeonDump (when you enter GUI, and in a code box please)?
  13. Forget the base64 encode thing and use a Plist Editor, for example Plist Editor Pro, just google.
  14. try booting snow with the -x32 flag. this driver isn't 64bit compatible yet, and pc_efi boots snow in 64 bits by default.
  15. CXSkin Games are not displayed correctly with last version (I'll take screenshot later), it was working fine with the 10/20 version.
×