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

  1. nVidia injection

    If you are talking about video bios dumping, im not sure if you can get it through DSDT from any card, i guess the corresponding function will just work for laptops which hold the video bios in their bios.
  2. nVidia injection

    Yeah, good question, i dont have the time anymore yet im not that good at reversing, maybe someone else can find the unknown bits or correct the info above. About vbios dumping, if you are talking about a hackmac you can use NVEnabler, it dumps your vbios into the IORegistry and you can see it with "ioreg -lw0 | grep vbios". Actually it should also be possible to load NVEnabler on a running real mac and then issue the ioreg command mentioned above. greets
  3. GeForce Go 7600

    Graphics are a tough bit on Vaios. Can you boot up with an external screen and load the kext in the attachment. Take a look if the panel gets turned on or not. greets Btw, am I the only one who sees the attachment adding broken? I didnt see it in Safari at all and in Firefox (3.6.3) it got displayed a bit off. Happened the second time here. NVDAEnabler.kext.zip
  4. No and no. You have to build the NVCAP by looking at various tables in the rom. More information here http://www.insanelymac.com/forum/index.php?showtopic=215236 Or you just use NVEnabler or GraphicsEnabler (nvidia part) which gets your cards rom and calculates the NVCAP. NVCAPMaker didnt calculate right NVCAP for any card i tried. If you are using SnowLeopard, this information was removed from System Profiler. At least QuartzExterme and CoreImage was, dont know about QuartzGL.
  5. nVidia injection

    Hey guys, i wanted to share the current stuff we know about the various properties mac nvidia efi drivers set to get the graphics card working properly in mac os x. Also if somebody can help disassembling those drivers you are welcome to help here if you want. And if you already know some bits please post them, so we can get this going as soon as possible. Also with 10.6.3 it seems the drivers got pickier from what i've read so far so i thought now is the best time to get into it. First about display-cfg. It describes what type of screen is attached. The last two bytes are made up as following: If some condition (unknown yet, we thought it had to do with if a screen is attached to that output, which it had not) is met we get: BYTE: Display-Number BYTE: I2C Read Offset BYTE: 0xFF BYTE: 0xFF If the unknown condition above is not met its build up as following regarding the type of screen attached. For ANALOG: BYTE: Display-Number BYTE: I2C Read Offset BYTE: 0xFF BYTE: 0x00 For TV: BYTE: Display-Number BYTE: I2C Read Offset BYTE: 0xFF BYTE: 0x01 And for everything else like LVDS, TMDS and Display-Port BYTE: Display-Number BYTE: I2C Read Offset BYTE: DCB Entry OR (guessing) BYTE: 0x03 There is one display-cfg for each screen. Here an example (note we have to swap bytes to inject): ANALOG @0,display-cfg <00FFXX00> XX = I2C Read Offset @1,display-cfg <00FFXX01> XX = I2C Read Offset TV @0,display-cfg <01FFXX00> XX = I2C Read Offset @1,display-cfg <01FFXX01> XX = I2C Read Offset ELSE @0,display-cfg <03YYXX00> XX = I2C Read Offset; YY = DCB ENTRY OR VALUE (guessing) @1,display-cfg <03YYXX01> XX = I2C Read Offset; YY = DCB ENTRY OR VALUE (guessing) Now about NVCAP: It describes which outputs can be used simultaneously and the following: BYTE: NVCAP_VERSION (hardcoded, goes from 0 to 5) BYTE: HAS_CLAM_SHELL (lid) BYTE: UNKNOWN (most built-in cards and MacPro 7300GT have that set to 1) BYTE: UNKNOWN (most built-in cards have that set to 1. something about backlight?) WORD: OUTPUT GROUP 3 (guessing, it describes what outputs are usable together with S-Video out) WORD: OUTPUT GROUP 1 (describes what outputs are grouped to Display-A) WORD: OUTPUT GROUP 2 (describes what outputs are grouped to Display-B) BYTE: BYTE: BYTE: BYTE: BYTE: BUILT-IN (guessing, built-in cards apart from 7300GO (AppleTV) have this set to 1) BYTE: UNKNOWN (hardcoded value) BYTE: EDID_MANUFACTURER_RESERVED_TIMINGS (BYTE 0x25 of the primary screens EDID) BYTE: BYTE: BYTE: UNKNOWN (MacBookPro 8600MGT (15") 128MB Vram has this set to 1) About the Output groups, they are generated like following. It all depends on the DCB table in your video bios. You can find your DCB table by looking at offset 0x36 of a nvidia bios. You byte swap the word at 0x36, thats the address of the DCB table. In the DCB table we have entries describing what type of connection can be used for a physical output, like ANALOG, ANALOG/DVI etc. Let's take an example DCB (iMac 7600GT). DCB ENTRY 0: ANALOG DCB ENTRY 1: LVDS DCB ENTRY 2: TMDS DCB ENTRY 3: TV In this case we have LVDS at index 1 (so we set bit 1), it is always alone on an output group. So OUTPUT GROUP 1 would be hex: 0x0002 binary: 0000 0000 0000 0010 All the other entries will be grouped to OUTPUT GROUP 2, so we have DCB ENTRY 0,2 and 3 (so we set bit 0,2 and 3) grouped which would be 0x000D binary 0000 0000 0000 1101 As you can see we set bit X (X is the DCB ENTRY INDEX) to group an entry to an output group. The same is done for OUTPUT GROUP 3, it's just generated when we have a TV entry in our DCB. It would be of big help if somebody with iMac 7600GT an tell us what outputs do work simultaneously with an S-Video adapter since iMac 7600GT is the only one having just the TV entry in this output group. Now about NVMT: it describes the capabilities of the primary screen: BYTE: NVMT_VERSION BYTE: DISPLAY_TYPE (0 = ANALOG, 1 = TV, 3 = the rest) BYTE: UNKNOWN BYTE: UNKNOWN WORD: EDID_MANUFACTURER WORD: EDID_PRODUCT_CODE WORD: SCREEN WIDTH WORD: SCREEN HEIGHT WORD: SCREEN WIDTH + SOME VALUE WORD: SCREEN WIDTH + SOME VALUE WORD: SCREEN WIDTH + SOME VALUE WORD: ZEROED WORD: SCREEN HEIGHT + SOME VALUE WORD: SCREEN HEIGHT + SOME VALUE WORD: SCREEN HEIGHT + SOME VALUE WORD: ZEROED DWORD: SOME VALUE * 10000 WORD: BYTE: BYTE: --BYTE: BYTE: BYTE: 7 DWORDS: ZEROED BYTE: 0xFF HARDCODED BYTE: 0xFF HARDCODED 6 BYTES: ZEROED DWORD: BYTE: BYTE: 6 BYTES: ZEROED BYTE: BYTE: BYTE: BYTE: --WORD: the --BYTE is this value >> 8 BYTE: BYTE: Looking at NVMT is quite a mess, too much is unknown yet. If somebody has any further info for instance how to calculate the screen width/height values please help. NVDA,Features: according to 8800GT Efi driver it is: SUBSYSTEM_ID << 16 | 0x02FF built-in injected when the card is built-in. To check with: REGISTER STRAP_INFO_2 & 0x10 device-type "NVDA,Parent" (HARDCODED) Ext_Present injected when there is a second screen available at boot. @X,built-in, @X,use-backlight-blanking injected when the attached screen is fixed and not removable (LVDS) @0,AAPL,boot-display injected for the primary screen @X,backlight-control injected with the value of AAPL,backlight-control @0,name "NVDA,Display-A" (HARDCODED) @1,name "NVDA,Display-B" (HARDCODED) @X,device-type "display" (HARDCODED) @X,compatible "NVDA,NVMac" (HARDCODED) As you see there is still much left to investigate, if somebody has some hints or wants to help you are welcome to join this thread here. Also for easing your investigation i created a small app (based on the great work of the guys at nouveau project) attached at this thread. Note it just parses the bios, it can't save any changes you make. Also if you happen to have real macs, it would be great if you can provide us an ioreg dump and your nVidia bios. NvidiaInfo.zip greets fassl
  6. OSx86

    Ne kein problem, ich würd das ganze nur anders angehen und zB nicht von Insanelymac und den zahlreichen forks kopieren, steht oft viel blödsinn und teilwissen drin. Das sorgt dann nur für noch mehr Verwirrung und Scheitern. Und vielleicht Howtos nur posten wenn man 100% sagen kann das sie richtig sind und auch zum gewünschten Erfolg führen. Mehr Arbeit am Anfang, spart dir und anderen dafür nachher viel Arbeit.
  7. schwarzer Bildschirm mit Mauszeiger

    Was für einen Injector benutzt du?
  8. VoodooHDA sleep fix

    Workaround als shell script: #!/bin/sh sudo kextunload /System/Library/Extensions/VoodooHDA.kext sleep 1 sudo kextunload /System/Library/Extensions/VoodooHDA.kext sudo kextload /System/Library/Extensions/VoodooHDA.kext Das script ausführen nachm sleep dann geht der sound wieder normal.
  9. Festplatte wiederherstellen

    Das wird dann wohl die Mircosoft Variante der EFI System Partition sein, sollte deine Platte als GUID Partition Table formatiert worden sein. Die eig. 200mb groß sein sollte als FAT32. Microsoft ftw...
  10. Gigabyte P55A-UD5 und i7-860

    Du kannst da auch GeForce irgendwas stehen haben und es wird funktionieren, ändern kannst das im Injector unter modelwhatever
  11. Sleep geht plötzlich nicht mehr....

    Sleep probleme sind schwer zu diagnostizieren da praktisch jeder Treiber schuld sein kann. Welche Grafikkarte hast du und welchen Injector benutzt du?
  12. Kernel in Installation DVD einbinden

    Denke mit ner Linux Live CD wirst genug über deine Hardware erfahren.
  13. OSx86

    Was auch sicher noch "hilfreich" wäre, ist die Verfasser der HowTo's zu nennen wenn du sie schon 1:1 kopierst. mfg fassl
  14. Warum eigentlich Snow Leo ?

    Alles was ich dazu sagen kann: Ein Kumpel besaß ein Macbook2,1 mit Leopard, hat jetzt das neueste Macbook mit Snow Leopard. Alles in allem lief der alte Macbook um _einiges_ flotter in jeglicher hinsicht, als der neue noch ziemlich frisch aufgesetzte mit Snow Leopard. Also meiner Meinung nach, lohnt sich Snow Leopard sicher erst in ein paar OS updates. lg fassl
  15. TV-out Snow Leopard Nvidia

    Nvenabler oder nvenabler_ no_display-cfg?