Jump to content
InsanelyMac Forum

volram

Members
  • Content count

    15
  • Joined

  • Last visited

About volram

  • Rank
    InsanelyMac Protégé
  1. I have disabled integrated graphics card in bios (boot VGA Controller Selection for" to "other" instead of "windows 7/Vista"), and the behavior is the same in the OS X (no acceleration by Nvidia). In Windows 7 only one card (nvidia). The problem has to be in some other thing...
  2. Please, look at Ioreg attached, and then leap at a conclusion and don't vice versa.
  3. Well, the card is not only detected, but is working with the intel hd 4000. That is the point. The kext Geforce.kext don't load with ML and the system crashes. But with Mavericks that don't happen. Look at Ioreg.
  4. Everybody knows that with Geforce.kext and others Nvidia kexts the system hangs and the video crash. But with the actualization of Mavericks (DP2-DP7), my two cards are running. I'm using SMBIOS 9,1. I don´t know if the system automatically switch between the cards. My files for those that want to dig in this. Thanks. http://db.tt/0qjLahVb
  5. Stripes in screen with mobility 4650

    Welcome to the club! Probably you have a connection to LVDS via eDP. That means that theres is no solution to this problem as far i know.
  6. ATI 4650m and the 1600x900 LVDS via eDP

    My early theory is confirmed. In some cases 4650 mobility (and perhaps a lot of others AMD mobility GPUs) uses the LVDS/eDP connector. The log of softMCCS confirmed that: We need help of some guru to solve the problem. I believe that I found the root of it. You can find my softMCCS log here: https://mega.co.nz/#...wgUgNbG2iVxuuk.
  7. ATI 4650m and the 1600x900 LVDS via eDP

    @aunoor, I think the problem is not the senseID. I have senseID=7 and no luck. I have exactly the same information in the rom of my card that is in the rom of smartie77 available here: http://www.osx86.net/view/1446-qe-ci_ati_4650mobility_lvds_for_toshiba.html. The problem has to be located in dsdt.
  8. ATI 4650m and the 1600x900 LVDS via eDP

    @aunor, I Think that there is something in this direction. Take a look of a similar problem with the installation of Windows 7: http://support.microsoft.com/kb/978226. Note the reference to the Imac (4670m) in the description of the problem. However, some people with the connector object id [14] has been successful in getting the LVDS output. The problem should be in DSDT (sleep or lcd section). I noted that there is a interference between the lvds and hdmi output even though there is no conflict in the edited framebuff. When I plug the hdmi cable the lvds turn black (white line to backlight). More: when I plug a usb the lvds change the color (when it is not black). The problem is the conflict. Or the dual link pathc or the dsdt (sleep, usb, lcd). A big trouble.
  9. Working AMD Radeon HD 6990M Lion

    Toris, post you DSDT and Ioreg, please.
  10. There is a big problem well known for the ATI mobility users: 1600x900 screen in LVDS is very difficult to attain. I think I have found the real motive for this. ATI uses, in some cases, the eDP output for connect with the internal lcd probably because of the high resolution of the panel. In my case the output is the following: Connector Object Id [14] which is [LVDS] encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [5] which is [VGA] encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A] encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x20 [duallink 0x0] enc 0x1)] linkb: true But the transmitter 12/04 or 12/01 give me a black screen or half resolution (even with the dual link patch that can be made with chameleon, DSDT or via ATY_init plist). The root of the problem, then, I think is the connector type. Reading the Linux driver info ( http://cgit.freedesk...ecac298b8d441d0) in the section Connector Object ID Definition has it: -#define CONNECTOR_OBJECT_ID_eDP 0x14 As you can see, the connector that is identified as LVDS with the redsox bios decoder is really the eDP decoder. Kizwan has noted that some Imacs uses that port: http://www.insanelymac.com/forum/topic/249642-editing-custom-personalities-for-ati-radeon-hd45xxx/page__st__260#entry1662530. The problem is that with the Shrike framebuffer Mountain Lion simply not load the GUI in my HP. How to solve that? I mean how to patch a framebuffer with this info i.e eDP output to enable LVDS connected via eDP. What are the connector type and control flags?
  11. Help with Ati Mobility 4650 (id:9480) on HP DV7 17"

    May be the problem is the dual lvds interface as touched in this forum (about other matter):http://forums.guru3d.com/showthread.php?p=3789313 I think so because my panel is a lg and present the very same problem as your: I can´t get lvds. Seems that it show half resolution and not the expected image. Btw, my card (4650 mobility) uses dig 5. Very strange.
  12. I think that the solution is identical in both cases. I get corrupted screen when I use Chameleon; I get black screen with ATY. I too found that when the hex sequence is altered, the lcd image is altered.
  13. That´s a puzzle. I have found that if you plug only the vga it remains black, but if you plug the hdmi it works. Maybe the problem is around the relation betwen the LVDs port and the DVI port (my card has 4 output). I´m inclined to think that we need a personality that support 4 outputs.
  14. The problem is certainly with the hex. These people who had a similar problem get a solution: http://www.insanelymac.com/forum/index.php?showtopic=269163&hl=%2B4670+%2Bmobility&fromsearch=1
  15. Try this: http://www.insanelymac.com/forum/index.php?showtopic=270344
×