Jump to content

Sony Vaio VPCF115FM Discussion: DSDT Injection

kizwan

By kizwan,
in Laptops

 Share
787 posts in this topic

Recommended Posts

PlumberGr
PlumberGr
Posted
Posted
I'm looking for Monitor vendor ID, not GPU vendor ID.

 

I am not very familiar with this but this is what I got (Sony Vaio F11Z1E)

 

15:51:54.283A5...Dump: complete Windows device enumeration

15:51:54.287A6...*******************************************

15:51:54.292A7...1.DeviceName = \\.\DISPLAY1

15:51:54.297A8.....DeviceFlags = 00080005

15:51:54.301A9.....DeviceString = NVIDIA GeForce GT 330M

15:51:54.306AA.....DeviceID = PCI\VEN_10DE&DEV_0A29&SUBSYS_9067104D&REV_A2

15:51:54.311AB.....DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Video\{F73C1383-0B7B-45DD-AC56-71131BE7A084}\0000

15:51:54.317AC.....DeviceDriver = nvd3dumx,nvwgf2umx,nvwgf2umx

15:51:54.324AD.....a.MonitorName = \\.\DISPLAY1\Monitor0

15:51:54.329AE.......MonitorFlags = 00000003

15:51:54.333AF.......MonitorString = Digital Flat Panel (1920x1080 60Hz)

15:51:54.337B0.......MonitorID = MONITOR\MS_0025\{4d36e96e-e325-11ce-bfc1-08002be10318}\0002

15:51:54.342B1.......MonitorKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0002

15:51:54.349B2.......Raw EDID = 00FFFFFFFFFFFF00367F2500000000002D0C010490241400EAA8E099574B92251C505400000001010101010101010101010101010101403880B4703840403C3C550068C810000018403880807138AA408080880068C810000018000000FC004E76696469612044656661756C000000FC007420466C61742050616E656C00001F

15:51:54.356B3...2.DeviceName = \\.\DISPLAY2

15:51:54.364B4.....DeviceFlags = 08080000

15:51:54.370B5.....DeviceString = NVIDIA GeForce GT 330M

15:51:54.375B6.....DeviceID = PCI\VEN_10DE&DEV_0A29&SUBSYS_9067104D&REV_A2

15:51:54.380B7.....DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Video\{F73C1383-0B7B-45DD-AC56-71131BE7A084}\0001

15:51:54.389B8.....DeviceDriver = nvd3dumx,nvwgf2umx,nvwgf2umx

15:51:54.397B9...3.DeviceName = \\.\DISPLAYV1

15:51:54.402BA.....DeviceFlags = 00000008

15:51:54.407BB.....DeviceString = RDPDD Chained DD

15:51:54.411BC.....DeviceID =

15:51:54.417BD.....DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0000

15:51:54.444BE.....DeviceDriver = rdpdd 6.1.7600.16385

15:51:54.452BF...4.DeviceName = \\.\DISPLAYV2

15:51:54.456C0.....DeviceFlags = 00200008

15:51:54.461C1.....DeviceString = RDP Encoder Mirror Driver

15:51:54.465C2.....DeviceID =

15:51:54.470C3.....DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Video\{42cf9257-1d96-4c9d-87f3-0d8e74595f78}\0000

15:51:54.478C4.....DeviceDriver = rdpencdd 6.1.7600.16385

15:51:54.484C5...5.DeviceName = \\.\DISPLAYV3

15:51:54.488C6.....DeviceFlags = 00200008

15:51:54.493C7.....DeviceString = RDP Reflector Display Driver

15:51:54.497C8.....DeviceID =

15:51:54.501C9.....DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Video\{b043b95c-5670-4f10-b934-8ed0c8eb59a8}\0000

15:51:54.508CA.....DeviceDriver = rdprefdd 6.1.7600.16385

15:51:54.514CB...Total number of monitors enumerated = 1

15:51:54.517CC...*******************************************

Link to comment
Share on other sites
First Last
First Last
Posted
Posted
LOL :wacko: . No one asking you to wasted your time. I'm doing this on my free time & it doesn't interfere my job at all. As I said earlier, if you want to build SNC.kext, you will need to refer the SNC code in DSDT. I bet you'll wanna vomit a lot. LOL. Right now I'm looking on how to obtain monitor vendor ID. So far no success yet. When I have anything useful for VAIOs, I will update this thread.

 

Got this from ioreg in mac os:

 

...

| | | | | | +-o AppleDisplay <class AppleDisplay, id 0x1000003e2, re$

| | | | | | {

| | | | | | "IOClass" = "AppleDisplay"

| | | | | | "CFBundleIdentifier" = "com.apple.iokit.IOGraphicsF$

| | | | | | "IOProviderClass" = "IODisplayConnect"

| | | | | | "DisplayProductID" = 1815

| | | | | | "IOPowerManagement" = {"CurrentPowerState"=3}

| | | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatform$

| | | | | | "IODisplayParameters" = {"ggsc"={"min"=0,"max"=6553$

| | | | | | "IOProbeScore" = 2000

| | | | | | "IOMatchCategory" = "IODefaultMatchCategory"

| | | | | | "AppleDisplayType" = 10

| | | | | | "AppleSense" = 1815

| | | | | | "IODisplayConnectFlags" = <84400000>

| | | | | | "DisplayVendorID" = 1970170734

...

 

EDIT:

But i'm not sure if mac os reads the right ids

Windows Hardware Manager says

Hardware ID: MONITOR/SNY05FA

Compatible ID: *PNP09FF

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
Posted
Got this from ioreg in mac os:

 

...

| | | | | | +-o AppleDisplay <class AppleDisplay, id 0x1000003e2, re$

| | | | | | {

| | | | | | "IOClass" = "AppleDisplay"

| | | | | | "CFBundleIdentifier" = "com.apple.iokit.IOGraphicsF$

| | | | | | "IOProviderClass" = "IODisplayConnect"

| | | | | | "DisplayProductID" = 1815

| | | | | | "IOPowerManagement" = {"CurrentPowerState"=3}

| | | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatform$

| | | | | | "IODisplayParameters" = {"ggsc"={"min"=0,"max"=6553$

| | | | | | "IOProbeScore" = 2000

| | | | | | "IOMatchCategory" = "IODefaultMatchCategory"

| | | | | | "AppleDisplayType" = 10

| | | | | | "AppleSense" = 1815

| | | | | | "IODisplayConnectFlags" = <84400000>

| | | | | | "DisplayVendorID" = 1970170734

...

 

EDIT:

But i'm not sure if mac os reads the right ids

Windows Hardware Manager says

Hardware ID: MONITOR/SNY05FA

Compatible ID: *PNP09FF

When we run "ioreg -l" command in Terminal, DisplayVendorID is in decimal. If we convert 1970170734 to HEX, it will be 756E6B6E which is generic vendor ID, not actual vendor ID to our monitor. From windows Device Manager, we can easily get the monitor device ID but not the vendor ID. In your post, you specify "Hardware ID: MONITOR/SNY05FA" & this show us the device ID for your monitor is "05FA". Honestly, I'm not sure if the display override can get the VAIO monitor detected but I'm still want to test it. However, inability to get the monitor vendor ID prevent me from doing so.

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
Posted
The problem with that is if you get the 'right' drivers (the nvidia macbook pro ones) to work, there's no monitor detected (and I posted an ioreg dump showing this)

That is why I'm trying to find out how to obtain the monitor vendor ID in my attempt to forced OS X to recognized the internal monitor. I already know the internal monitor is not detected when drivers for nvidia is loaded. I already know the problem. What I'm trying to do now is solved the problem.

Link to comment
Share on other sites
PlumberGr
PlumberGr
Posted
Posted
@kizwan

 

Plug and Play ID......... MS_0026 :(

 

 

OK I did the remote thing, when the screen is black I got the following ioreg dump.

 

I have just installed the 10.6.3(retail) with Mamooth CD. Boot with Mamooth CD and GraphicsEnabler=Yes

 

I do not have the MacBookUpdate installed.

 

I do not know where to look.

 

Shall I repeat with the

1.MacBookUpdate?

2. 10.6.4

3.changing the DSDT?

 

please advice.

1063simple.zip

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
Posted
OK I did the remote thing, when the screen is black I got the following ioreg dump.

 

I have just installed the 10.6.3(retail) with Mamooth CD. Boot with Mamooth CD and GraphicsEnabler=Yes

 

I do not have the MacBookUpdate installed.

Looks like the graphic card was detected just fine without the macbookpro update.

 

@kizwan

 

Plug and Play ID......... MS_0026 :rolleyes:

It only shows monitor device / product ID = 0026 :(

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

 

Vendor Id: 0x13BD

Anyone interested to test this? Please visit this thread to create the display override files. The first post explained how to do it. It only have two pages, not too long to read. Please use this override file as a template:-

http://www.mediafire.com/?tdylsjrtlr988gr

 

If it work, you should see LCD Monitor Forced EDID under Displays (Graphics/Displays section) in System Profiler.

Link to comment
Share on other sites
cloud03
cloud03
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...

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
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...

Did you changed the EDID value, vendor ID & product ID with yours? The file is only a template.

 

OK.....Does QE/CI working with GraphicsEnabler=No? Can you give me ioreg & System Profiler dump (GraphicsEnabler=No)?

Link to comment
Share on other sites
cloud03
cloud03
Posted
Posted

I've followed the guide, and apparently my VendorID and productID are exactly the same as the one on the guide, and I've replaced the EDID with my EDID that I retrieved from moninfo, and then converted the base64,

 

With GraphicsEnabler=No QE/CI doesn't work, and I've attached the sprofiler and ioreg dump from it...

cloud_ioreg_sprofiler.rar

Link to comment
Share on other sites
OoTLink
OoTLink
Posted
Posted

Sounds like you're making some progress ;)

 

I wanted to add a quick note that the SNC kext that was used on the Vaio P doesn't really appear to have much about the monitor except backlight control from the FN keys (and powering on/off the bluetooth/wifi modules which are already on by default anyway).

 

I'll dig this up in a bit, but the writer of that kext politely posted the source code, it's a small bit of C++ if you'd like to check it out. :wacko:

Link to comment
Share on other sites
kizwan
kizwan
Posted
  • Author
Posted
I've followed the guide, and apparently my VendorID and productID are exactly the same as the one on the guide, and I've replaced the EDID with my EDID that I retrieved from moninfo, and then converted the base64,

 

With GraphicsEnabler=No QE/CI doesn't work, and I've attached the sprofiler and ioreg dump from it...

The vendor ID 756e6b6e & prodcut ID 717 (DisplayVendorID-756e6b6e/DisplayProductID-717) are actually generic vendor & product ID. They're not actual vendor & product ID for your internal monitor. BTW, can you boot with GraphicsEnabler=Yes & obtain these files: kernel.log & system.log. Don't cut & paste the contents, just copy the files & post it here. I want to see whether it produced any error message regarding the display or not. If it contain error messages regarding framebuffer, I believe VAIO will need custom framebuffer, just like ATI Mobility Radeon HD does. If it just say display not detected, it would be very difficult to decipher it.

 

Sounds like you're making some progress ;)

 

I wanted to add a quick note that the SNC kext that was used on the Vaio P doesn't really appear to have much about the monitor except backlight control from the FN keys (and powering on/off the bluetooth/wifi modules which are already on by default anyway).

 

I'll dig this up in a bit, but the writer of that kext politely posted the source code, it's a small bit of C++ if you'd like to check it out. :wacko:

I don't think so OoTLink. :lol: I'm afraid, we're still a long way from making a progress. I already take a look the SNC linux driver source code & I got same conclusion which I can only see monitor backlight control & other regular FN keys control. But if you can give me the source code, I really want to take a look how the Mac version of SNC driver communicate with the SNC device. Don't hope too much though, because I'm not an apple driver programmer. :D

Link to comment
Share on other sites
cloud03
cloud03
Posted
Posted
The vendor ID 756e6b6e & prodcut ID 717 (DisplayVendorID-756e6b6e/DisplayProductID-717) are actually generic vendor & product ID. They're not actual vendor & product ID for your internal monitor. BTW, can you boot with GraphicsEnabler=Yes & obtain these files: kernel.log & system.log. Don't cut & paste the contents, just copy the files & post it here. I want to see whether it produced any error message regarding the display or not. If it contain error messages regarding framebuffer, I believe VAIO will need custom framebuffer, just like ATI Mobility Radeon HD does. If it just say display not detected, it would be very difficult to decipher it.

 

How can I obtain if I can't see the interface? with VNC? or is there any other way?

Link to comment
Share on other sites
OoTLink
OoTLink
Posted
Posted

I have a crazy method for doing that:

 

On my PowerBook G4, I set up sharing airport over bluetooth, then with the generic graphic mode on the Vaio I paired the Vaio with the PowerBook, and made an automator app to connect to the PB over bluetooth. Once that was done, I set that as a login item..

 

So when I am in a crazy graphics mode, it auto connects and then I can use screen sharing. Fun, eh? XD

 

Easily noted:

 

http://store.apple.com/us/product/MB442Z/A

 

For $29 you can have ethernet REALLY easily - this method is guaranteed to work! Best of all, it's small and easier to plug in than an ethernet cable (yuck). Sadly, 10/100.

 

There's also airport cards, and depending on whether the expresscard slot works or not.. that's an option too. And for the brave souls, you could always swap out your wifi card with an airport card. :( Tempted to do this, since that particular Atheros card seems to be eh.. suckage?

 

Maybe I'll blow off a few hours tomorrow trying out this idea.

 

Also: The OEM airport cards can be had for less than $20 shipped on ebay. Just worth consideration for when your warranty is up...

 

:)

 

Shooting in the dark, but if you get nviida default panel, it might be vendor 10de and product 37. Might. HAha

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