Jump to content

Sooper Oozer

Members
  • Content count

    20
  • Joined

  • Last visited

About Sooper Oozer

  • Rank
    InsanelyMac Protégé
  1. ATI Radeon HD 3200 Drivers

    I've been reading through all this business on unsupported video cards in OSX and I'm a little disappointed in what I'm hearing out of certain members of the community. In particular when it comes to these cards I keep hearing things like "there won't be" and "will never work." Anyone who knows technology should know far better than to make such definite statements ever. If you had asked me in 2000 when I had six years of programming under my belt if something like the iPhone would ever exist I would have been doubtful, if you had shown me one back when I was learning Basic and Pascal I would have said it was "magic." Those of you who keep asking the same question over and over do need to stop, if working drivers for these cards are developed, the community will be shouting it from the highest mountains. If they are going to show up, they will show up on their own, you don't need to ride the community over it. Better yet, do some research and find a group working on it, CONTRIBUTE! I was looking into doing a driver for the NVIDIA 310M for a Sony Vaio, and if that taught me anything it's that if someone or some group of people have the time, patience, and skill to develop the driver, there is sufficient information out there scattered about to allow the driver to be written. Apple has a tutorial on writing drivers on their own website for F-sakes. I'm not saying it would be easy, but it's not impossible. Will it EVER happen? Maybe not, but it isn't impossible. Now, the real question to ask is if there is anyone out there that finds writing the driver to be a worthwhile proposition? I'm slowly working on something, I've got an idea that may work but it's off in the distance.... Let me throw this line out there though to see if anyone else is working on it or has thoughts or information on it: So, here is my thought. Chasing each of these card and writing drivers for them would be a monumental task. Even doing one might prove to be so time consuming as to be prohibitive. So, while I did say before that I think it's possible, I don't think it's the most efficient use of our time. Now, on the other hand we do have some advantages to play with here. Apple isn't like windows, to those with the time a patience the inner workings of OSX are fairly well transparent. Also, while it's not the same as Linux (and STFU with your "it's based of BSD" {censored} and just listen for a minute!) they are both based off of Unix and do share a number of similarities. What we also have is a pretty complete set of drivers in Linux for all of these graphics cards. So, maybe we can use this information to our advantage. Here is what I'm researching. Instead of building all these drivers, perhaps we can come up with a way to build some software that will replace the rendering sytem in OSX or work with the X11 window server to build Xorg into OSX and have it download and implement the proper drivers from the Ubuntu repository. I think this would be possible, what I don't know is if it would result in a fast well functioning alternative to simply writing the drivers, but it looks like it would require coming up with a bit of hybrid version of OSX or at least a program which once installed would hijack the window server or operate over the current rendering environment. If anyone has any information on this, if anyone else has attempted it or is currently working on it or would like to participate, feel free to contact me via a private message. As for the rest of you, if you have working systems and don't want to help others trying to find new solutions and generate new workarounds, get the F off the forums and stop harassing people who are trying to explore different solutions. I don't care how many PCs you have put OSX on, if you think anything is ever impossible in the world of computing you don't know the first thing about modding or hacking.
  2. Hackintosh Toshiba Satellite M305D

    Still no luck on video support... I started a new thread just for ATI Radeon 3100 support. View it over here. Seems like it should be doable. A few of the cards that are supported are based on the same chip set so it seems like it should be possible to get it up and running. Looks like it will simply take more cajoling than I had anticipated. Oh well... Give me your best guess!
  3. Hello all... Soooo.... anyone have any ideas on how to get the ATI Radeon 3100 card to work in OS X? I've got a little project running to get OS X up on a Toshiba Satellite, you can see my progress here, but I'm starting a different thread to ask for / post anything I find out regarding coaxing this card to work in OS X. Well... I'm all ears!
  4. Hackintosh Toshiba Satellite M305D

    Ok, nevermind... My keyboard and trackpad are working. I'm not sure if it was the VooDoo PS2 deal I already tried to install or not, but I just rebooted and somehow my keyboard and touch pad are both working now! So, I'm down to tweaking the graphics, getting sound, and getting wifi (might be a pipe dream). Here is the really odd part... I've been using that nawcom mod CD I downloaded. I had been loading the Modbin kernel because I believe that is the kernel with AMD support and this is an AMD machine. Well, I didn't mean to reboot from the CD, I was trying to get back to Ubuntu and in an attempt to cause a kernel panic so I could reboot I just let it boot from the hard drive essentially using a vanilla install. Well... it actually booted vanilla. Don't ask me how, I don't know. So, I'm off to find video support.
  5. Hackintosh Toshiba Satellite M305D

    Ugh! Got it set up with a USB keyboard and mouse, but no luck getting the internal keyboard and mouse to work. I tried installing the VooDooPS2Trackpad.pgk file, but it didn't help. Still no support. I'm going to download some things and try some different stuff but this is pretty frustrating. I don't see why it would work in the installer but not once snow leopard is up and running. I may try to see if I can switch the PS2 controller from the installer back into my version of snow leopard. Ugh, hackintoshes. What a pain. If anyone has any ideas on this please let me know, but I'm pretty sure I'm talking to myself anyway.
  6. Hackintosh Toshiba Satellite M305D

    Ok, made a little more progress. Using my working install USB I was able to access terminal and change the following files.... again... on the OSX partition in order to boot. Keyboard and mouse do not work at the moment. USB keyboard and mouse do work, but I don't have the time to deal with it at the moment. I know it doesn't have anything to do with crippling the firewire because I had access to the keyboard and mouse for the install process. So... looks like I'll need to work out what kexts I need to run the keyboard and mouse and then take it from there. Important part is that at least I have some display, the hard disk, and USB ports all working at the moment. AppleFWAudio.kext IOFireWireAVC.kext IOFireWireFamily.kext IOFireWireIP.kext IOFireWireSBP2.kext IOFireWireSerialBusProtocolTransport.kext
  7. Hackintosh Toshiba Satellite M305D

    It can be done though. I think I just got it figured out for mine. AMD can be a pain to get OS X to work on, but it will do it if you have patience and work through it. Ok, looks like I may have made some progress... So I tried this little CD that I found in another forum. Nawcom's Mod CD or boot CD. You can find it through Google. However, the issue I ran into with the Firewire continued to pop up. Now, I'm lucky enough to be using an 8 gig Sony USB stick which I have restored the full retail snow DVD to for my install, so I hopped on an iMac at work and mutilated some kexts by adding .bad to the ending of them. I know it might have been overkill, but the following kexts were modified: AppleFWAudio.kext IOFireWireAVC.kext IOFireWireFamily.kext IOFireWireIP.kext IOFireWireSBP2.kext IOFireWireSerialBusProtocolTransport.kext All of this had to be done through terminal because the files were hidden in nautilus or whatever the GUI environment on Mac is. It was a pain, but I'm glad I did it. I fired up the computer with the Nawcom Mod CD again and popped in my modified Sony USB and it worked! It still had some issues with getting the reformatting on the hard drive done properly, but I worked it out and it's installing now. More information to come once I get to reboot it. ********NOTE: There may be other ways to do this, but right now this is the only way I know of and it may require repartitioning and completely reformating your hard drive. Be ready to reinstall windows, linux, or whatever you have... not an issue for me though. I've been wanting to try out something new for a bit anyway. Sabayon here I come...****** And... drats! The return of the FW panic. Got it installed on the hard disk though, now I need to find a way to get in there to mutilate those kexts again.
  8. Hackintosh Toshiba Satellite M305D

    Hi again everyone. Finally got my Toshiba back, and I'm already having issues. I've tried using a 10.6.6i by Hazard distro, but it isn't quite working. I'm pretty sure it's compatible with AMD, but I'm trying to download another distro due to issues I've had. I'm having an issue with a firewire kernel panic after the "Mac framework initializing" portion of the boot. I'm going to try another distro, also considering installing to my spec using another machine hard drive swap, but if anyone has any other ideas on fixing this firewire issue let me know. Just for reference I've tried using -v -x cpus=1 or 2 and busratio=10 flags
  9. 5 different EDIDs?

    Yeah, I agree. We may need some guru help to finish this one off. However, have you ever seen how they get truly slammed with questions in the forums? I think to get the help of someone a little more experienced, we are going to have to do the homework and research ourselves and hand it off to a guru that can help by realizing the final solution. I think for the moment though, it would be most effective to keep gathering information on the situation and keep the expert questions to simple yes/no situations. Another thing that seems odd to me, I was doing some more looking through that EDID section of the DSDT and things are getting even stranger. You know, a section of code shouldn't be allowed to spread out over say 5 to 10 pages, because then you look through the code and realize that the section with 5 EDIDs is duplicated somewhere else in the code like I just did. Soooo... yeah, two EDID sections, so now I need to figure out what to do with that. Good luck, I'll continue doing research, and let me know if you find out anything.
  10. 5 different EDIDs?

    Here is the code you requested: Device (PEG3) { Name (_ADR, 0x00030000) Device (NGFX) { Method (_ADR, 0, Serialized) { \DBGC (0x65, 0x00, BCEN) Return (0x00) } OperationRegion (NVFX, PCI_Config, 0x00, 0x10) Field (NVFX, AnyAcc, NoLock, Preserve) { NVID, 16 } Name (_DOD, Package (0x04) { 0x0100, 0x0110, 0x80007330, 0x8000A430 }) Name (BCL1, Package (0x09) { 0x34, 0x40, 0x4F, 0x5E, 0x6F, 0x86, 0xA0, 0xC3, 0xFF }) Name (BCL4, Package (0x09) { 0x34, 0x3E, 0x4B, 0x5C, 0x6F, 0x86, 0xA0, 0xC3, 0xFF }) Name (BCL5, Package (0x09) { 0x0D, 0x13, 0x1B, 0x27, 0x39, 0x53, 0x79, 0xAF, 0xFF }) Name (ICL2, Package (0x0B) { 0x64, 0x64, 0x04, 0x10, 0x1C, 0x28, 0x34, 0x40, 0x4C, 0x58, 0x64 }) Name (I10B, Buffer (0x08) {}) CreateField (I10B, 0x00, 0x08, I_AL) CreateField (I10B, 0x08, 0x08, I_AH) CreateField (I10B, 0x10, 0x08, I_BL) CreateField (I10B, 0x18, 0x08, I_BH) CreateField (I10B, 0x20, 0x08, I_CL) CreateField (I10B, 0x28, 0x08, I_CH) CreateField (I10B, 0x30, 0x08, I_DL) CreateField (I10B, 0x38, 0x08, I_DH) Method (SBRI, 1, NotSerialized) { Store (0x14, I_AL) Store (0x4F, I_AH) Store (0x94, I_BL) Store (0x01, I_BH) Store (Arg0, I_CL) PHDD (0xE2, I10B) } Name (SSBR, 0x00) Method (GBRI, 0, NotSerialized) { Store (0x14, I_AL) Store (0x4F, I_AH) Store (0x94, I_BL) Store (0x00, I_BH) Store (0x00, I_CL) Store (PHDD (0xE2, I10B), I10B) Store (DerefOf (Index (I10B, 0x04)), SSBR) Return (SSBR) } Name (EDI1, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x4D, 0xD9, 0xFA, 0x06, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54.... I'm not sure how far back you wanted me to go though, so the entire file is attached as well. I saw your comment that AlexanderPD had tried the same thing. When I have a minute more I'm going to search through the posts to see what method he used. This is an IF statement, so you couldn't just delete all the options, I think the thing to do would be guess that OS X may be defaulting to the empt value, or at least that is the only thing that would make sense based on what I can see in my computer and my IO registry, and based on that guess tweak the EDID to return whichever value of the five that works the best, recompile, and see what happens. I'm not trying to knock AlexanderPD or anything, but we have a bunch of people looking into this with different skill levels, and I've seen valid fixes proclaimed bunk before (though not for this issue) just because someone bungled the procedure. So I'm likely to give this a shot anyway. One additional interesting thing I noticed in a quick line during OS X boot is a line that said something to the effect of IOAPIC (I think that is the abbreviation it uses, it flashes by so fast, I need to use the wait flag) table not found. So I don't know if this section of the DSDT affects how it operates at all or not. What I do know after all the reading that I've done is that we aren't going to get updated drivers from NVIDIA anytime soon, nor are we likely to port a driver from Linux that has been updated to fix the problem, unless someone happens to know a programing super genius that can reverse engineer the closed nvidia drivers, also, we can't take the route I was looking for which was to basically hard-code the monitor properties into OS X since it rebuilds the IO registry each time it boots up. So, whatever we do will have to use injecting some type of information at boot in the form of an EDID, a DSDT, or some other less well known solution. .... not sure but it might yet be possible to plug this information into the com.apple.windowserver.plist files, but then again it might just overwrite that on the next boot, and I can't quite make sense out of how to generate my own com.apple.windowserver.plist file. Not sure how they work yet. Good luck! EDIT: Not allowed to upload the dsdt.... screw you forum. Email me if you want the whole file.
  11. Hackintosh Toshiba Satellite M305D

    Hello all, This will be a thread to discuss installing OS X on a Toshiba Satellite M305D, or more specifically the M305D-S4830 model. I'm currently waiting on it's return from Toshiba where it is being repaired. The specs are as follows: Processor: AMD Turion X2 Ultra mobile ZM-80 / 2.1 ghz Chipset: AMD M780V Ram: DDR2 4 gb Graphics Card: ATI Radeon 3100 Hard Drive: WD 320 gb (replacement, original Toshiba HD failed) Audio: ? Not sure More info here: http://www.laptopdrivers.net/specs/toshiba...aptop_specs.htm Moving right along, I have had OS X running in Virtual Box on this system, but now I'd like to get it up and running natively. I'm planning on using the newly released 10.6.6i for AMD/Intel from Hazard for the install. I'm already pretty certain I'm going to need flags -v -x cpus=2 busratio=10 (might be off on that one, need to double check) to get the installer to run. May need other tweaks, it is yet to be seen. I'm going to try to get absolutely everything working on this. I've looked around, and it sounds like it's possible, but it may take some heavy lifting so to speak, so I'm going to use this thread as part guide part group think for others trying to get OS X up and running on this little beast. Thoughts, concerns, hair brained ideas, and theories are always welcome!
  12. Sony Vaio VPCF115FM Discussion: DSDT Injection

    {censored}! I meant to post this as a reply on this thread, but I screwed up. I was going through my DSDT and found some odd entries 5 different EDID values linked up to the LCD. I'm not sure if I'm on to something or not, kinda need someone better with EDID, but my new topic post is here: http://www.insanelymac.com/forum/index.php...p;#entry1667869 Kinda strange, I'm not sure why it would have 5 EDID values, 6 if you count the mysterious empty version.
  13. 5 different EDIDs?

    Oh even better. The EDID returned in Windows does not match any of the EDID values in the DSDT. Maybe that is why injecting EDID has not worked up to this point? Here are the hex values for my EDID from Windows. :1000000000FFFFFFFFFFFF004DD9FA0600000000D0 :100010002D0C010390241400EAA8E099574B922586 :100020001C50540000000101010101010101010124 :10003000010101010101302A405E618418307474DA :10004000880068C810000018302A40906184B43019 :100050008585CC0068C810000018000000FC004E73 :1000600076696469612044656661756C000000FC70 :10007000007420466C61742050616E656C0000AA14 :00000001FF So again, WTF? Where is that Kizwan guy to make sense of this nonsense?
  14. 5 different EDIDs?

    I was just looking through the dsdt table for my Vaio, and I noticed that it looks like the DSDT is set to return one of 5 different values for the EDID of the LCD display... 6 if you count the last one. EMPT I'll post it here, maybe someone can make sense out of it. Maybe if we can figure out the right one to use, or how to get OS X to match up with the IF statement with the EDID that would work, maybe it would fix the issue. Not sure. Name (EDI1, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x4D, 0xD9, 0xFA, 0x06, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x28, 0x23, /* 0038 */ 0x40, 0x32, 0x60, 0x84, 0x0A, 0x30, 0x11, 0x11, /* 0040 */ 0x33, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x28, 0x23, 0x40, 0x13, 0x61, 0x84, 0x3C, 0x30, /* 0050 */ 0x5B, 0x5B, 0x44, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0xEE }) Name (EDI2, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x4D, 0xD9, 0xFA, 0x06, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x30, 0x2A, /* 0038 */ 0x40, 0x5E, 0x61, 0x84, 0x18, 0x30, 0x74, 0x74, /* 0040 */ 0x88, 0x00, 0x6A, 0xCC, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, 0x76, 0x69, /* 0050 */ 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, 0x66, 0x61, /* 0058 */ 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x74, /* 0060 */ 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, 0x50, 0x61, /* 0068 */ 0x6E, 0x65, 0x6C, 0x00, 0x00, 0x00, 0x00, 0xFD, /* 0070 */ 0x00, 0x00, 0x3D, 0x1D, 0x38, 0x0B, 0x00, 0x00, /* 0078 */ 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x8A }) Name (EDI3, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x4D, 0xD9, 0xFA, 0x06, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x30, 0x2A, /* 0038 */ 0x40, 0x5E, 0x61, 0x84, 0x18, 0x30, 0x74, 0x74, /* 0040 */ 0x88, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x30, 0x2A, 0x40, 0x90, 0x61, 0x84, 0xB4, 0x30, /* 0050 */ 0x85, 0x85, 0xCC, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0xA9 }) Name (EDI4, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x36, 0x7F, 0x25, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x40, 0x38, /* 0038 */ 0x80, 0xB4, 0x70, 0x38, 0x40, 0x40, 0x3C, 0x3C, /* 0040 */ 0x55, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x40, 0x38, 0x80, 0x80, 0x71, 0x38, 0xAA, 0x40, /* 0050 */ 0x80, 0x80, 0x88, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0x1F }) Name (EDI5, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x36, 0x7F, 0x25, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x40, 0x38, /* 0038 */ 0x80, 0xB4, 0x70, 0x38, 0x40, 0x40, 0x3C, 0x3C, /* 0040 */ 0x55, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x40, 0x38, 0x80, 0x80, 0x71, 0x38, 0xAA, 0x40, /* 0050 */ 0x80, 0x80, 0x88, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0x1F }) Name (EMPT, Buffer (0x80) { /* 0000 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0018 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0020 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0028 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0030 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0038 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0040 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0048 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0050 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0058 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0060 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0068 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0070 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0078 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 }) Device (LCD) { Name (_ADR, 0x0110) Method (_DDC, 1, NotSerialized) { Store (\GPID, Local0) If (LEqual (Local0, 0x01)) { Return (EDI1) } If (LEqual (Local0, 0x02)) { Return (EDI2) } If (LEqual (Local0, 0x03)) { Return (EDI3) } If (LEqual (Local0, 0x04)) { Return (EDI4) } If (LEqual (Local0, 0x05)) { Return (EDI5) } Else { Return (EMPT) } } Yeah, just looked at a few other DSDT files to compare and the LCD section from those examples does not include multiple EDID values or the code at the bottom with the if statements for the different EDID versions. Still don't know if this has anything to do with the issue. Maybe someone could clear up the "IF (LEqual (Local0, 0x0X)) part. Maybe somehow OSX is falling into the else part and ending up with EMPT returned, which looks like no EDID. Also interesting, EDI4 and 5 are the same, while 1, 2, and 3 are all different. The plot thickens...
  15. Sony Vaio VPCF115FM Discussion: DSDT Injection

    Yeah, after one last huff, I'm done with this. I don't think it can be done at all. The linux solution hands off the EDID directly to the GPU, if those of you with natively supported cards can figure out a way to do this possibly with the com.apple.windowserver.plist files, you might be able to make something happen, but I don't think so. I think this has something to do with how the card and lcd are implemented in the vaio. I don't think it's a simple BIOS issue, it would have been much simpler to send out a bios flash update than to have NVIDIA fix the driver. No, whatever this is, it's in the nvidia drivers, and it's fixed for everything but OS X because, well, these machines aren't really supposed to be running OS X. No more losing sleep over this one peeps. Again, the leverage of the entire Linux community only found one way to do this, give that EDID in .bin format directly to the card, but I don't know if OS X would even begin to support any type of fix like this, and apple isn't forthcoming with any ways to manually register devices in the IO tree. Maybe a DSDT, maybe not. In general though, I think we are all SOL unless someone can talk NVIDIA into releasing an updated driver for OSX that includes the fix they had to do for the Sony laptops, and what do you think the odds of that are? I'll be focusing my attentions on my Toshiba when I get it back. Good luck all!
×