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 kizwan, I've finally managed to boot with GraphicsEnabler=Yes, and access it via vnc, but where can I find kernel.log and system.log?

 

EDIT:nevermind, I've found it, here is the file...

No useful information found in the log file. :D I saw that you tried SNC kext but it didn't load. It produced unresolved symbol error message:-

Aug  4 10:52:46 localhost kernel[0]: kxld[com.yourcompany.driver.SNC_for_SODV]: The following symbols are unresolved for this kext:
Aug  4 10:52:46 localhost kernel[0]: kxld[com.yourcompany.driver.SNC_for_SODV]:	 __ZN12SNC_for_SODV4freeEv
Aug  4 10:52:46 localhost kernel[0]: kxld[com.yourcompany.driver.SNC_for_SODV]:	 __ZN12SNC_for_SODV8finalizeEj
Aug  4 10:52:46 localhost kernel[0]: Can't load kext com.yourcompany.driver.SNC_for_SODV - link failed.
Aug  4 10:52:46 localhost kernel[0]: Failed to load executable for kext com.yourcompany.driver.SNC_for_SODV.
Aug  4 10:52:46 localhost kernel[0]: Kext com.yourcompany.driver.SNC_for_SODV failed to load (0xdc008016).
Aug  4 10:52:46 localhost kernel[0]: Failed to load kext com.yourcompany.driver.SNC_for_SODV (error 0xdc008016).
Aug  4 10:52:46 localhost kernel[0]: Couldn't alloc class "SNC_for_SODV"

This is unique error which, I believe, only happen with 10.6.4. You might want to test it with 10.6.3 instead.

 

I haven't take a look to SNC source code yet because, for the time being, I don't have access to my macbook.

kizwan
kizwan
Posted
  • Author
Posted
I'm actually still using 10.6.0 on this vaio... :)

I see. :P I got similar error message (but with different kext) before on my Dell Studio. It was 10.6.4. I reinstalled Mac OS X & updated only to 10.6.3 just to run some silly test. I thought it was unique 10.6.4's error messages though. :P

OoTLink
OoTLink
Posted
Posted

The SNC kext doesn't work on the Vaio F, already went over that. Besides, it doesn't have anything to do with the screen (aside from controlling brightness) anyway. :D

 

To get the display working, we first need the GPU kext to properly recognize the chip (which it may or may not have), and the ports it has. If we've got the interface (not sure if it's LVDS or an internal displayport, though the Vaio Z guys say it's displayport), then we need to figure out an EDID override for the LCD since it doesn't appear to get one by default.

 

By default, the NVDA50 that comes with the MBP update assumes the computer is a MBP and over VNC you'll see the default resolutions of 1680x1050 and 1440x900, among other things. I think it's just not looking for the display in the proper place.

 

Looking at Linux drivers, they figured it out but still needed an EDID override to get it to work (in some cases).

  • 2 weeks later...
OoTLink
OoTLink
Posted
Posted
I've tried the link you gave, without graphicsenabler it worked, it does show Internal LCD forced EDID under system profiler or diplay settings, but with graphics enabler only , it gives a blank screen, and with GraphicsEnabler=Yes VideoROM=/SONY.ROM VBIOS=Yes it gives a blank screen but the LCD backlight seems to be on...

 

*bumps thread*

 

What is this videorom=/sony.rom?

 

Is that just a vbios rom you pulled from Everest or something? I'm curious now. I've been reading about some behavior Linux users got when messing with Vaios, and the backlight coming on suggests that the screen is on but the OS can't find an EDID to use with it.

 

https://bbs.archlinux.org/viewtopic.php?pid=765848

 

So let's check out this sony.rom you're using! ;)

cloud03
cloud03
Posted
Posted

Sony.rom is the vga bios I've retrieved it from the laptop using the following method from this site:

 

http://www.projectosx.com/forum/index.php?showtopic=1029

 

The thing is, when using that particular vga bios, the backlight stays on, but the computer comes to a total halt, on the other hand, when only enabling the graphics enabler, without any bios override, the lcd turned off, but I can simply press ctrl + f2 and down arrow 10 times then enter to restart.

OoTLink
OoTLink
Posted
Posted

If the machine is responsive but you can't see anything, you can always bring up the power options box by hitting the power button (OS X knows what it is :D) - the default option is shut down, so if you hit enter after hitting the power button, your machine will shut down rather quickly. :)

 

Kinda cool about the Nvidia driver!

OoTLink
OoTLink
Posted
Posted

I installed Ubuntu successfully today, the 256.44 driver was a little kludgey and I tried to inject an EDID but in the end it wasn't necessary, I just needed to find the right instructions on how to install the dang thing. XD

 

So there's no funky framebuffer there.

 

Edit: Cloud, I would dig into that but at least for now I'm done with OS X on the Sony (I'm back in class and don't have time to burn on hobbies like that). It might be that OS X is just sitting there trying to figure out how to handle the screen. Have you got an external you can plug into in the meanwhile?

Brandom
Brandom
Posted
Posted

I am on a VPCCW21FX and, of course, have all of the same video issues. I need to go pick up a HDMI cable so I can test with an external monitor, but I am excited to hear that I can finally install Ubuntu on my laptop. If there is anything I can do to help, let me know. I have only been at this for a week, so I'm still a newb, but I have everything working but acceleration, sound (ALC262) power management (sleep/wake) and my DVD drive tries to load every 2-3 minutes (annoying.) For some reason DHCP doesn't work either, so I have to give it an IP/sub/gateway. I have full 1366 x 768 using <key>Graphics Mode</key> <string>1366×768×32</string> in my SystemConfiguration com.apple.Boot.plist GraphicsEnabler=No. I really like OS X and would use it primarily if I could just get acceleration and sound working!

 

Edit: Does this have anything to do with the VAIO problem? http://www.insanelymac.com/forum/index.php?showtopic=207635

Brandom
Brandom
Posted
Posted
Mac os x is lost cause on the vaio.

 

That's absurd! If it can be fixed on Ubuntu it can be fixed on OS X. The only thing we lack is community interest. From reading through most of this thread I've gathered that a lot of thought has been put into the solution and we simply need to continue pursuing it. The only way it's a lost cause is if the community completely gives up on it, but I don't see why they would.. doesn't this issue come up with almost every VAIO? Isn't VAIO still a pretty popular notebook? I believe a solution will be found - it just takes time. Aside from this thread is anyone else pursuing the solution? Is this thread dead?

kizwan
kizwan
Posted
  • Author
Posted
Aside from this thread is anyone else pursuing the solution? Is this thread dead?

Unless me or the moderator close this thread, this thread is not dead yet. I like your fighting spirit though. I have try my best to help. I have read a lot at linux forum about VAIO & I didn't found anything useful (according to my current knowledge). On some VAIO with linux installed, they will get blank screen too when the driver loaded but this can be fixed by injecting EDID value. I already tried it on Mac OS X but it didn't help either, unless the way I injected it is wrong.

Brandom
Brandom
Posted
Posted
What about vaag's trick with the dell, about removing the entries DVI and CRT from DSDT?

 

http://www.insanelymac.com/forum/lofiversi...hp/t198707.html

 

I tried that as well as the display override. Still get a black screen. The new official nvidia drivers work like a charm on Linux, I wish we could find out exactly what changed in the new version and try to make a patch for OS X. For some reason the VAIOs are still not officially supported by nvidia so I am stuck with these old drivers even on Windows 7. I'm beginning to feel like I should have gone with another vendor, but I've just got to play the waiting game for now. Anyone have anything else I should try? I've been trying to come up with possible solutions, but I'm still fighting the learning curve.

OoTLink
OoTLink
Posted
Posted

Not necessarily a charm, but the screen actually works in Linux *without* the nvidia drivers too - AND at full 1920x1080 (problem is by default, the framebuffer assumes the screen is 2048x1400 and a bit bigger).

 

Still, it works. They know something we don't XD

First Last
First Last
Posted
Posted

some new experiences:

 

when i was messing around with my windows drivers, i came to a result:

newest official nvidia drivers do work, but need a modded .inf file (maybe because of a sony-specific hardware id)

link: http://www.laptopvideo2go.com/

and the sfep-driver is only for hotkeys and brightness.

screen works fine without any troubles.

Brandom
Brandom
Posted
Posted
Not necessarily a charm, but the screen actually works in Linux *without* the nvidia drivers too - AND at full 1920x1080 (problem is by default, the framebuffer assumes the screen is 2048x1400 and a bit bigger).

 

Still, it works. They know something we don't XD

 

Yeah, after a reboot I found out that you still need the nomodeset option to get around a black screen, but once the nvidia drivers are loaded they take over and set the resolution, enable hardware acceleration, etc. So the nvidia driver is needed to communicate with the card/monitor unless we use the nomodeset which is roughly the equivalent of GraphicsEnabler=No which leaves us with no hardware acceleration and lousy resolutions. Does this mean that we would need a full port of this particular nvidia driver to OS X, or could we just have some sort of kext that subs in for the lack of DDC/CI support in the monitor?

ludof
ludof
Posted
Posted
Yeah, after a reboot I found out that you still need the nomodeset option to get around a black screen, but once the nvidia drivers are loaded they take over and set the resolution, enable hardware acceleration, etc. So the nvidia driver is needed to communicate with the card/monitor unless we use the nomodeset which is roughly the equivalent of GraphicsEnabler=No which leaves us with no hardware acceleration and lousy resolutions. Does this mean that we would need a full port of this particular nvidia driver to OS X, or could we just have some sort of kext that subs in for the lack of DDC/CI support in the monitor?

 

 

Hey,

 

Some posts report that they have qe/ci with full resolution on the external screen and black screen on the internal screen. These observations suggest that the gt330m graphic driver is working (it does a good job for the external screen). Is it possible that a wrong configuration value concerning the internal screen is given to the driver ? If not, could you please explain me what could be the mechanisms (or some directions) that a driver working for the external screen, does not work for the internal one ?

 

LF

Brandom
Brandom
Posted
Posted
Hey,

 

Some posts report that they have qe/ci with full resolution on the external screen and black screen on the internal screen. These observations suggest that the gt330m graphic driver is working (it does a good job for the external screen). Is it possible that a wrong configuration value concerning the internal screen is given to the driver ? If not, could you please explain me what could be the mechanisms (or some directions) that a driver working for the external screen, does not work for the internal one ?

 

LF

 

Yes, I have not tested that yet myself (I still need to pick up a HDMI cable) but based on those reports the 330M driver works fine. I believe the issue is the internal display's lack of DDC/CI support. http://en.wikipedia.org/wiki/Display_Data_Channel I am basing this off of information given by softMCCS. Under Windows and now Linux I think this information is supplied by the display driver. I am not sure whether the attempts to inject the EDID was an attempt to address this issue, or if that would only address part of the problem. Some clarification of previous attempts to fix the internal display issue would help. I am at a loss as to how to move forward and I am mostly just watching this forum for any new ideas of things to try.

ludof
ludof
Posted
Posted
Yes, I have not tested that yet myself (I still need to pick up a HDMI cable) but based on those reports the 330M driver works fine. I believe the issue is the internal display's lack of DDC/CI support. http://en.wikipedia.org/wiki/Display_Data_Channel I am basing this off of information given by softMCCS. Under Windows and now Linux I think this information is supplied by the display driver. I am not sure whether the attempts to inject the EDID was an attempt to address this issue, or if that would only address part of the problem. Some clarification of previous attempts to fix the internal display issue would help. I am at a loss as to how to move forward and I am mostly just watching this forum for any new ideas of things to try.

 

 

Did you try this dsdt patcher ?

 

http://www.insanelymac.com/forum/index.php?showtopic=133683

 

VAIO Users: pls try this patcher, i saw some Variable issues in LCD Device of VAIO DSDT, the patcher fixes this issues, maybe that will solve Internal LCD Diplay issue with QE/CI enabled. Maybe also more work is needed but actually i think we can solve your Problems in DSDT. Somebody correct me if i'm wrong. So please come here and test, thank you. I also invite more people to mess around with DSDT and come here with their findings
 Share
Go to topic listing
×
×
  • Create New...