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 sydlix

  • Rank
    InsanelyMac Protégé
  1. Kizwan if you look at the radeondump of the person who got the fullhd panel working on 4650 you see he set 02 00 TR/ENC values but it's radeonhd log said "mapping dig2 on uniphyE". DIG2 should be 01, mine says DIG1 and should be 00.
  2. Let me know if it does anything Thanks
  3. I can confirm that the Override method does nothing more than the system was doing before. Indeed I got the EDID from IORegexplorer, because it was already loaded, adding the plist just loaded the same values, still screen OFF at boot and black with backlight after detection. Hope wmarsh can provide something better.
  4. Can you provide the override file with this log from moninfo? Here you go, I am ready to test it: http://dl.dropbox.com/u/8433914/rbgled_moninfo.txt
  5. I don't know if EDID is the problem but take this in account: Display settings like resolution and refresh rate for the working screens (vga, hdmi) are remembered by the system. LVDS starts off, it's resolution settings are remembered when I detect displays but it shows: 1) no refresh rate setting 2) brightness does not work, is not remembered. This must mean someting.
  6. wmarsh I think you are understimating something: I actually booted once with the drivers fully loaded, perfect colors and 1920x1080 resolution on LVDS. I was using 10.6.7 normal kexts, Shrike framebuffer with LVDS set as [02 00 00 00 40 00 00 00 09 01 00 00 02 00 00 05]. Stupid me I rebooted to check again, I can't replicate. If I remember correctly I was testing your first modified trunk ati.c. First of all I compiled the boot file, booted into SL, placed kexts with modified FB and boot file, repaired, rebooted. As usual, vga started and LVDS not. When I went to display config and selected detect displays, I got the LVDS to initialized with a BACKLIGHTED black screen. Now, this usually happens all the time. The LVDS is recognized in IOREG, Sysprofiler, but it ain't working. At boot is not initialized and I need to do the detect displays thing. Then is detected. black with backlight on. IMPORTANT: WITH MY NOT WORKING I CAN SELECT RESOLUTION BUT NO REFRESH RATE IS DETECTED/SELECTABLE. This may lead to something. However, I decided to edit the dual link value to 0x01 instead 0x02. But before I wanted to try your stock version without DSDT. So I delete the dsdt and boot again. SAME. Ok then I put again the dsdt into place along with the new 0x01 boot file. I reboot and my LVDS turns on together with the vga... But why this actually happened only once? Dunno. Investigating. I need your first version ati.c, please, with also link format options an that stuff.
  7. wmarsh check out the imac 10,1 ioreg I posted in the other thread since there are different interesting link format and stuff lines, you may find useful to try it. I also recommend to use less lines possible since with the first version of modified trunk ati.c you provided I actually got one totally working boot, as you already know. I had the dual link flag (the second one into the framebuffer, not the one into device), set to 0x01, and had just placed again the dsdt after having removed it. Unfortunately I cannot replicate, but if you are right maybe the framebuffer is using dual link and we need single, play with the link type and dual link flags, put them to 0x00 and try the ones of the imac ioreg. Let me know.
  8. wmarsh, I think we are close. I got the display working at boot. DO NOT KNOW WHY. It was extended to to vga I did not have the bar and I could not take any information. It was completely random, I cannot replicate. I have your lines in my boot file but maybe we are looking for something else, like: http://support.apple.com/kb/TA24192 I think is some kind of bad nvram I dunno. Investigate.
  9. just tried with the supposedly correct values 12 00, dsdt aml modified with dsm mode, imac 11,1 smbios. LVDS starts off, then detect displays, still BLACK.
  10. Thanks, I will also need an imac 10,1 smbios.plist.
  11. I think I already tried changing the features even to 29 05 without results. I do not know if our problem is dual link but I think that we should contact the RadeonHD framebuffer developers. Check this: http://code.google.com/p/osx86-driver-rade...ec=svn7&r=7 along with the output you get from radeondump with the RadeonHD kext loaded. But again we need someone that says like: HDMI is working at high res, vga too and your LVDS is black even with correct TE settings? I think the problem could be...etc. I need a readeondump from RadeonHD loaded driver from a working LVDS configuration.
  12. wmarsh, I don't think that your control flag statement can be correct, in particular, looking at shrike framebuffer: 0000000 02 00 00 00 40 00 00 00 09 01 00 00 02 01 00 03 0000010 02 00 00 00 00 01 00 00 09 01 00 00 20 01 02 02 0000020 00 04 00 00 04 03 00 00 00 01 00 00 10 00 01 01 as you see you have 2 LVDS strings, plus 1 displayport (but it's really only for displayport?). Now, I don't know how the imac 10,1 uses these strings, but it has in theory 2 connectors, one lvds and one mini-dvi. I am guessing that the third string is the mini-dvi. Lately we have been linking the transmitter 0x values with dual link since they mean (still if is correct) link A+B But as you can see there is a contraddiction, since the frist string using the 40 00 00 00 control flag is actually using A+B/2 and the second with control flag 00 01 00 00 is using B/1. If our ati injection is working fine, I don't know what's wrong with the values we put in the framebuffer. However if you take a look at the imac ioreg I posted, you'll see the controlflag on the LVDS display to be 0x04 so I think it is using the first string of the framebuffer. My opinion again is to involve in this someone who has the knowledge we are missing..any ideas?
  13. Here is the ioreg you are interested in. Unfortunately I can't get the one of the last macbooks. http://dl.dropbox.com/u/8433914/iMac%20101.ioreg
  14. No but I got the one of an imac 10,1 with 4670 mobility. It should be in the log zip I posted.
  15. Yeah I know that now but if you check the ati.c file you see that using the supposedly dual link 02 you use the first lines with TMDSB and not the // non 48xx listed below. However my opinion is that we are using the right encoder but there is something missing in the ati.c injection that leads to no video signal on the LVDS connector. Again we need someone that knows how to edit the bootloader and recognizes what can cause a fully recognized LVDS display to show black screen.