Jump to content

Sony Vaio VPCF115FM Discussion: DSDT Injection

kizwan

By kizwan,
in Laptops

 Share
787 posts in this topic

Recommended Posts

kizwan
kizwan
Posted
  • Author
Posted
Hi guys

I will buy a VPCF1390X CTO with 425m but i was looking on the 330m and i found this

Is this 425M are you referring to? Good Memory Width which is 128bit but only DDR3, not GDDR3. Good for gaming of course.

 

No no no! Stop! Don't buy Sony VAIO if you intend to install Mac OS X on it. Also don't buy any notebook with Nvidia Optimus Technology. Buy Dell, Acer or HP notebook instead. Be careful with Asus because lot of Asus notebook have Nvidia Optimus Technology.

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
Posted
@kizwan

yes thats the card

 

actually its not my idea to install on my vaio

it would be just for fun

i already have a P6T-SE fully working so it will be just for fun

thanks for your reply

 

Have you tryed the link i posted?

No. The Nvidia graphic card on my Asus doesn't work yet. It have Optimus Technology so it stuck with Intel HD & AppleIntelHDGraphics.kext caused kernel panic when trying to load it.

Link to comment
Share on other sites
stevmach
stevmach
Posted
Posted

Hi all

 

I read on many threads and on the net too but i need help for my f**g dsdt for ma sony vaio, i got 166 errors when i compile, my laptop run without dsdt but i want to run HDMI and sd card slot and a dsdt can possibily help my for that, i have just the intel HD graphic card , you can watch 2 print screens i have posted on other thread to see what work. My VAIO laptop is VPCEB12FD with core i3.

 

http://www.insanelymac.com/forum/index.php...23754&st=40

 

and i join a dsdt.aml extract with linux and dsdt.dsl extract with DSDTSE for windows

 

dsdtwin.txt

dsdtlinux.txt

 

thanks in advance !!!

Link to comment
Share on other sites
  • 4 weeks later...
  • 2 weeks later...
Funky frank
Funky frank
Posted
Posted

I inserted the code to activate two displays to the nvidia.c chameleon code and compiled it, as mentioned here: projectosx - 2 displays in nvidia.c

 

The notebook freezes just before the login screen. So I guess I have to change the display config values?

 

 

How do I get the correct values of display config of the Vaio F11? Is there a ioreg tool for Win7? Is this approach senseless? Anyone experienced?

Link to comment
Share on other sites
Iperzampem0
Iperzampem0
Posted
Posted

Hi guys!

I'm reading all this thread because I have a VAIO FZ21M and I'm really interested in finding a solution for this "Black Screen after Boot with Nvidia driver installed" in all VAIO laptops.

What I know (since an year or so) is that the "problem" seems to be the Sonypi driver! I don't know if this is the same thing as the SNC driver...

And here is the link at the project page: http://code.google.com/p/sonypi-macosx/updates/list

Unfortunately the author abandoned this project since the beginning... :(

So I'm still waiting for a solution... like you, above all...

And I know for sure that if I install a Nvidia driver for my 8400M GT, this will function with an External Monitor.

If I didn't install the driver, the VAIO laptop magically works, but in VESA mode...

Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted
Hi,

 

the source is somewhere in P's thread.

 

I use to mede internal display enabler SNC for SODV but it's not useless.

( also in the therad)

 

I think it's not SNC problem but LCD detection method unmatch

between osx's way and vaio's one.

 

So I suggest that you should disadm and

binpatch the display driver's kext.

 

 

Hello ryuu123,

 

could you provide me with your source of your snc0928 kext? I am trying to enable the internal LVDS screen of the Vaio F11 notebook on Snow Leopard. Currently only external screens work or you have to disable nvidia kexts completly to boot into vesa mode.

 

I am really not experienced with all this dsdt and acpi stuff, but I can do programming a little bit.

 

Could you give me some hint in which direction I should investigate?

In this thread http://www.insanelymac.com/forum/index.php...8556&st=120

some users suggest you have to enable the internal screen with the snc device before the nvidia driver gets activated... Is this right? What do you think?

 

Thanks a lot for help.

 

Regards

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
Posted

Sonypi & SNC driver is not responsible with the internal display problem on VAIO notebooks. A lot of people already look into it & make the same conclusion. What you need here is someone with driver programming. He/She don't have to be able to write new driver but at least able to investigate (trace) where the problem is. You can see an example at Intel HD thread where she was able to troubleshoot the driver/kext. Of course she still can't solve the issue but it just a matter of time.

Link to comment
Share on other sites
OoTLink
OoTLink
Posted
Posted

Kizwan, what thread are you talking about?

 

Unfortunately there has been no progress on this. Guys, I could use a little help (I do know a decent bit of C++, and could try to ad lib the rest).

 

Here's my problem:

 

I can't find ANYTHING for Windows like ioreg (Everest SUCKS), is there anything better to dig into how your drivers are working? How about for Linux?

 

Both in Windows and Linux, Nvidia's driver has a special provision for Vaio notebooks that makes them work. Whatever they did, we need to replicate somehow. I'm not going to get very far staring at a page of decompiled hex, though.

 

Believe me, I'm motivated - I love OS X! Where else can you run Netflix and office without WINE ... and have a nice handy terminal!

Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted

I need the right DisplayCfg values of the F11. They can be only obtained out of the GT330m video bios. The bios can be obtained in these ways:

 

Video Bios Dumper

 

Kernel Memory Dumper

 

Some dumps of a gt330m

 

 

Now how can I disassemble the video bios to get the DisplayCfg values?

 

Edit: Here are some F11 DisplayCfg values:

 

Krazabu DisplayCfg values

 

 

- Use the attached patched ROM in the plist

0A75.006C.006F.vga.rom.zip ( 38.67K ) Number of downloads: 22

 

- Set display-cfg strings as :

03010600 and ffff0001

 

- Add string @0,EDID with value (data) :

CODE

00FFFFFFFFFFFF002E0D0000000000000409010280000000E2000000000000000000000008000101

010101010101010101010101010164190040410026301888360000000000006000000000000000000

000000000000000000000000000000000000000000000000000000000000000000000000000000000

000000000000FF

 

Edit: Internal screen still black, but loads my selfbuilt chameleon

 

Trying now with these nvcaps grabbed from here...

 

0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00,

0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07,

0x00, 0x00, 0x00, 0x00

 

Edit: Doesn't work

Link to comment
Share on other sites
Funky frank
Funky frank
Posted
Posted
This is post by fassl: nVidia injection. There is an utility available on this thread called NvidiaInfo. It can be use to read the VBIOS file. I use it when I want to generate proper NVCAP & display-cfg. I hope it helps somehow.

 

Thanks, looks like very useful information!

 

But I didn't get it to find the DCB table until now. Can somebody help me and show me my misakes here? At offset 0x36 there is a 0x0D value and afterwards text starts. Bios attached below. I will dump it again with nvidiainfo.

 

0A29.006C.006F.vga.rom.tar.gz

 

Edit: Results displayed by nvidiainfo:

 

post-39386-1289583603_thumb.png

 

post-39386-1289583642_thumb.png

 

 

Edit: From the manual posted above I get these display_cfg and nvcap values:

uint8_t display_cfg_0[]= {0x03, 0x00, 0x0F, 0x00};
uint8_t display_cfg_1[]= {0xff, 0xff, 0x06, 0x01};

static uint8_t default_NVCAP[]= {
0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 
0x06, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 
0x00, 0x00, 0x00, 0x00
};

 

Does it look correct to you? Do I have to byteswap word areas in NVCAP? Maybe our problem is that the bios has LVDS as first entry, but the macbook analog as first entry...?

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
Posted
Does it look correct to you? Do I have to byteswap word areas in NVCAP? Maybe our problem is that the bios has LVDS as first entry, but the macbook analog as first entry...?

Yes, it does look correct on NVCAP part. I'm not sure for display-cfg though but it looks correct based on the guide. I don't have enough hardware to test the display-cfg properties. On my Acer Aspire 9420, I don't need to set the display-cfg. It will automatically detected "ff ff 02 00" for primary display/connector & "ff ff 00 01" for secondary display/connector (on older Snow Leopard or Leopard, I got "ff ff ff ff" & "ff ff 00 00" if I'm not mistaken). If I set display-cfg according to VBIOS, I only get blank screen. However, I have read a lot of post mentioning the important of display-cfg where if it didn't specified, the display won't work correctly. Maybe mine is special case. Lack of hardware prevent me from testing any further.

 

I don't think the different on the arrangement of the LVDS, Analog, TMDS, etc is the cause of the problem since we can control the display output with NVCAP. At my post #19, you can see where you set primary display (output 1), secondary display (output 2) & TV (S-VIDEO I think) (output 3). My Acer Aspire 9420 also have LVDS at first entry & it works.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...