Help - Search - Members - Calendar
Full Version: Nvenabler Testing And Discussion
Project OS X Forums > OS X 10.6 (Snow Leopard) > Hardware Information > Graphics
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
Krazubu
Feb 1 2011, 02:37 PM
QUOTE
Now it seems they first had success with a custom EDID and now patched the bios, so the problem is resolved.

I searched on that site,
I can't actually find that patched BIOS.
funkyfrank
Feb 2 2011, 06:57 PM
QUOTE (Krazubu @ Feb 1 2011, 03:37 PM) *
I searched on that site,
I can't actually find that patched BIOS.


Krazubu sorry, it seems this was just regarding an updated nvidia driver or something. There is no new bios, just a new driver with revision 260.xx, that is not available for osx (258 still)... On the webpage it is written "new bios update", but I believe now he means this new driver... Strange... But there are reports that this special edid injection from the page works on linux systems. Could this work also on osx? They retrieve the edid directly from /proc/ or acpi. Is this edid dynamic?

QUOTE
22 Section "Device"
23 Identifier "Device0"
24 Driver "nvidia"
25 VendorName "NVIDIA Corporation"
26 BoardName "GeForce 9300M GS"
27- Option "ConnectedMonitor" "DFP-0, DFP-2"
28- Option "CustomEDID" "DFP-0:/etc/X11/SNY06FA.bin"
29+ Option "CustomEDID" "DFP-0:/proc/acpi/video/DGPU/LCD/EDID"
30 Option "NoLogo" "True"
31 Option "OnDemandVBlankInterrupts" "True"
32 EndSection

There are some edids inside the dsdl:

QUOTE
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
})


Do you think this way (edid injection) could work? Because you already stated it has nothing to do with edid and won't help. Why does it actually help on linux?
Krazubu
Feb 3 2011, 09:28 AM
I understood that there's a driver update but also some ROM patch.
Maybe he means the patch is done by the driver itself, in that case some motivated folk could have a look to code sources, if there are (isn't that driver closed ?).
About the EDID, the problem is not totally related tho not completely independent either. When it comes to outputs detection EDID is never far. So maybe Linux has enough with a special EDID, but OSX will hang whatever EDID you provide.
Anyway, you still can try, it can't hurt.
funkyfrank
Feb 3 2011, 10:27 AM
QUOTE (Krazubu @ Feb 3 2011, 10:28 AM) *
I understood that there's a driver update but also some ROM patch.
Maybe he means the patch is done by the driver itself, in that case some motivated folk could have a look to code sources, if there are (isn't that driver closed ?).
About the EDID, the problem is not totally related tho not completely independent either. When it comes to outputs detection EDID is never far. So maybe Linux has enough with a special EDID, but OSX will hang whatever EDID you provide.
Anyway, you still can try, it can't hurt.


Krazubu, would this rom patch be a temporary or a permanent one? Maybe it's somehow easy to extract this patch, modify the bios and dump it to the card? I think it's not possible to look at the sources, they talk about the closed nvidia driver sad.gif It's all very annoying.

Does nvenabler provide proper EDID injection or do I need to use chameleon? I tested chameleon a lot, it seems there are plenty of bug inside the graphics enabler.

And finally what do you think about a approach to patch the apple's framebuffer kext for nvidia cards? As far as I understand the display would then have quartz acceleration..?

Thanks for providing us with your knowledge and wisdom smile.gif
Krazubu
Feb 3 2011, 01:05 PM
NVE does provide a way to inject an alternate EDID and BIOS. Check my older nVidia thread to find how to inject EDID, about the BIOS it's explained in this topic several times.
We sure could understand what the driver does then patch the ROM with that, that's already what we did so far to make NVE and also by reverse engineering mac ROMs to figure some stuff like NVCAP building method or display-cfg, though we didn't incorporate the code yet for that last one.
However to do that we need access to drivers sources or at least the required infos, reverse engineering it is a bit too off focus here and difficult to get into it.
Proceeding with NVE would be the proper way as you wouldn't alter the physical ROM and it would be future proof.
Proceeding from the kext side is not a way as it will be far more complicated and can probably be done from once for good in the ROM and in a much cleaner way, less "hacky".
My guess is that OSX just expects some way to get infos from the ROM, that are not provided as they should. The way would be to rewrite that part in a OSX friendly way.
For that we have to know
1-What and where is that data
2-How OSX wants it
3-How to code that data in that ROM region, we need to know or figure the meaning of each byte
funkyfrank
Feb 4 2011, 03:41 AM
Hey Krazubu, what do think about this approach:

kizwan did a proper edid dsdl injection, and it is working properly. Now the IOReg shows two identical displays, but only display-B has the display0 node inside. This node is matched by IOGraphicsFamily. So I guess IOGraphicsFamily is responsible for failing to match the vaio display. ioreg shot

Happily the iographicsfamily is opensource.

opensource.apple.com/source/IOGraphics/IOGraphics-48

This particular sources seem to be responsible for the device detection:

opensource.apple.com/source/IOGraphics/IOGraphics-48/IOGraphicsFamily/IODisplayWrangler.cpp
opensource.apple.com/source/IOGraphics/IOGraphics-48/IOGraphicsFamily/IODisplay.cpp


Do you think it's a right track?

My dsdt post is here: vaio f11 dsdt thread post 450


EDIT: And here, a second theory, please read: Missing advanced menu / enable static vga display policy on sony vaio system bios and how to enable it
crackmac
Feb 7 2011, 07:14 PM
Hey guys, relative noob here. I read through this thread and I'm having trouble, I hope you can help me out...

I have a Dell Latitude E6510, quad i7, 8GB Ram, with an nVidia NVS 3100m with 512MB DDR3 (PCI PID 0x0a6c). I have OS X 10.6.6 running, and I'm trying to get NVEnabler running. Note that GraphicsEnable=Yes in Chameleon works for me and I get acceleration with QE running. However, when it's turned on I can't perform a proper system shutdown; shutdown happens from the OS perspective, but the hardware doesn't actually have its power removed. When I set GraphicsEnable=No, I can shutdown properly. I was hoping that maybe by using NVE, I might be able to fix this problem, and also have a method to better configure external displays as well.

I believe I followed the instructions in the first post properly:

- Set boot.plist GraphicsEnable to No
- Updated NVDANV50Hal.kext's pList to include my adapter; my .plist file is below, my addition is in red;

CODE

?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>NVDANV50Hal</string>
<key>CFBundleGetInfoString</key>
<string>NVDANV50Hal 1.6.26.22 (256.00.15f04)</string>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nv50hal</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>NVIDIA NV50 Resman Kernel Extension</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>1.6.26</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>6.2.6</string>
<key>IOKitPersonalities</key>
<dict>
<key>NVidiaRM</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nv50hal</string>
<key>IOClass</key>
<string>NVDANV50HAL</string>
<key>IOMatchCategory</key>
<string>IOService</string>
<key>IOPCIPrimaryMatch</key>
<string>
0x00f010de&amp;0xfff0ffff
0x019010de&amp;0xfff0ffff
0x040010de&amp;0xfff0ffff
0x042010de&amp;0xfff0ffff
0x05e010de&amp;0xfff8ffff
0x05f010de&amp;0xfff0ffff
0x060010de&amp;0xffe0ffff
0x062010de&amp;0xffe0ffff
0x064010de&amp;0xffe0ffff
0x06e010de&amp;0xfff0ffff
0x086010de&amp;0xffe0ffff
0x08a010de&amp;0xffe0ffff
0x0a2010de&amp;0xffa0ffff
0x0a6c10de&amp;0xfff0ffff
0x0ca010de&amp;0xffe0ffff
</string>
<key>IOProbeScore</key>
<integer>60000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
</dict>
</dict>
<key>OSBundleCompatibleVersion</key>
<string>1.2.0</string>
<key>OSBundleLibraries</key>
<dict>
<key>com.apple.NVDAResman</key>
<string>1.2.0</string>
<key>com.apple.kpi.iokit</key>
<string>9.0.0</string>
<key>com.apple.kpi.libkern</key>
<string>9.0.0</string>
</dict>
<key>OSBundleRequired</key>
<string>Safe Boot</string>
</dict>
</plist>


- Installed NVEnabler.kext to E/E, changed permissions, rebuilt caches, etc.

On reboot, my display hangs; it doesn't go black, or blank, it just sits as it is with the boot log stuck, never displaying the OSX Desktop. I thought the system was completely hung, but I am able to get it to a shutdown state by "flying blind". Since I can't really control anything at this point, I rebooted into single user mode, where NVEnabler was already loaded, and did an ioreg dump; see attached.

Click to view attachment

If anyone can help out, or if someone can direct me to a post in this thread I might have missed that explains how to fix this, I'd really appreciate it.
Breaking Bad
Feb 11 2011, 01:43 AM
-

Cheers,
Breaking Bad.
Pulpo
Feb 11 2011, 01:45 AM
My card is an ECS N9500GT-1GKS-F.

The DVI is working fine with D-Sub, but the HDMI is not working in Snow Leopard. When the system boots, the HMDI works fine until the system start. QE/CI is working also. I've tried an ECS 9400GT with the same layout (DVI & HDMI), and is the same problem: HDMI is not working under Snow Leopard. Using DVI with an adapter DVI to HDMI, is not working with HDMI.



This is the graphic card:



NVCAP: 0400000000000300000000000000000700000000 (from NVCAP Maker 1.4)

Click to view attachment

I'm using:

Core i5 760
Gigabyte GA-H55M-USB3
2 x 2GB A-Data 2000MHz (working @1333MHz 1.5V)
Samsung F4 1.5TB
LiteON DVD-RW 22X
Thermaltake PurePower 700W
Snow Leopard 10.6.6, multibeast 3.1, 64-bit, Graphic enabler = yes + nvenabler.kext (S/L/E)

Testing:

If I plug an ECS GT240 1GB (Accelero version) and ECS GTS 250 1GB, everything works flawless, even the HDMI and QE/CI. The system don't recognize the GT240 name, but that is an easy thing to solve. I can't use those cars because I want to use the low profile 9500GT with a LCD TV connected via HDMI in a mATX case.

I need some guidance to configure the connectors please.



Update:

I tried two adapters through DVI:



The first does not work, the second works well but with poor image quality. The HDMI connector is still not working.

Thanks!

Sorry for my english biggrin.gif
Krazubu
Feb 11 2011, 09:00 AM
If you're using NVE, why are you using a custom NVCAP from a non working software ?

Your IOReg is unusable, please read 1st post for instructions
Pulpo
Feb 11 2011, 10:00 AM
First I tried NVE which is always my first choice. As HDMI did not workI started to try different alternatives and that is why mess with NVCAP.

I have 2 hours to sleep before going to work ( sad.gif ) but when I return, I'll do a clean install and start from scratch.

QUOTE
However Requirement That stays for NVDANVXXHal. Could It Be That Simply.


I need to edit something else, besides the NVDANVXXHal and instructions from the first post for an installation from scratch? I tried it before and it did not work, surely I'm missing something ...


This is the card:



Thanks!
Breaking Bad
Feb 11 2011, 05:19 PM
-

Click to view attachment Click to view attachment

Cheers,
bb.
Slice
Feb 12 2011, 07:55 AM
In your case it is not needed
CODE
0x060010de&amp;0xffe0ffff

means ID from 0x060010de to 0x061f10de including your 0x061410de.
So you need no to correct info.plist.
Breaking Bad
Feb 12 2011, 01:56 PM
QUOTE (Slice @ Feb 12 2011, 08:55 AM) *
In your case it is not needed
CODE
0x060010de&amp;0xffe0ffff

means ID from 0x060010de to 0x061f10de including your 0x061410de.
So you need no to correct info.plist.

So, just to get things crystal clear to me:
You're saying that I don't need to do ANY CHANGE into my NVDANV50HAL.kext?
I'll try this, but I'm almost sure it won't work because it didn't before.

One more thing... in #1 post it says to put NVEnabler.kext into /S/L/E or into /Extra folder. Does that make any difference at all?

Cheers,
bb.

EDIT - Bad News
Today I ran a test and for my surprised the steps on #1 post didn't work.
My steps:
- Placed NVEnabler into /Extra folder.
- Checked NVDANV50HAL.kext and it's "default" option.
- Removed every single trace of: Injection - Strings or any other thing to make GFX work.
- Repaired permissions via Terminal (sudo diskutil repairPermissions / )
- Ran: sudo touch /System/Library/Extensions
- Changed bootloader to the one by ASERE.

Resolution is locked on 1024x768 and there's no chance to change it.
So my question is... is there anything I could do to make it work fine?

Cheers again,
bb.
Slice
Feb 12 2011, 06:33 PM
kernel.log?
Breaking Bad
Feb 13 2011, 05:47 PM
QUOTE (Slice @ Feb 12 2011, 06:33 PM) *
kernel.log?

I found it in /private/var/log
Here it is.
Click to view attachment
If this is not the correct file, let me know.

Cheers,
bb.

EDIT - BIOS issue?
Hi Slice.
Is there any chance of this problem could be related to the mod BIOS I'm using in my rig?
I'm thinking about rolling everything back to DSDT to see if this issue stops. What do ya think?

Cheers again,
bb.

EDIT 2 - Breaking News.
Yesterday I installed a fresh copy of SL into 10.6 version and all GFX ports (VGA - DVI - HDMI) works flawless.
I made a copy of the working partition to see if I can update it and for my surprise even in 10.6.2 the ports stop working.
I don't mind in using 10.6 only, but as I use Magic Mouse + Aluminum Wireless Keyboard, in 10.6 it just loose most of the nice features the devices have.

I even tried NVEnabler64.kext + Slice mod of Chameleon but still a no go.

Best regards,
bb.
crackmac
Feb 17 2011, 02:00 PM
QUOTE (crackmac @ Feb 7 2011, 02:14 PM) *
Hey guys, relative noob here. I read through this thread and I'm having trouble, I hope you can help me out...

I have a Dell Latitude E6510, quad i7, 8GB Ram, with an nVidia NVS 3100m with 512MB DDR3 (PCI PID 0x0a6c). I have OS X 10.6.6 running, and I'm trying to get NVEnabler running. Note that GraphicsEnable=Yes in Chameleon works for me and I get acceleration with QE running. However, when it's turned on I can't perform a proper system shutdown; shutdown happens from the OS perspective, but the hardware doesn't actually have its power removed. When I set GraphicsEnable=No, I can shutdown properly. I was hoping that maybe by using NVE, I might be able to fix this problem, and also have a method to better configure external displays as well.

I believe I followed the instructions in the first post properly:

- Set boot.plist GraphicsEnable to No
- Updated NVDANV50Hal.kext's pList to include my adapter; my .plist file is below, my addition is in red;

CODE

?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>NVDANV50Hal</string>
<key>CFBundleGetInfoString</key>
<string>NVDANV50Hal 1.6.26.22 (256.00.15f04)</string>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nv50hal</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>NVIDIA NV50 Resman Kernel Extension</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>1.6.26</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>6.2.6</string>
<key>IOKitPersonalities</key>
<dict>
<key>NVidiaRM</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.nvidia.nv50hal</string>
<key>IOClass</key>
<string>NVDANV50HAL</string>
<key>IOMatchCategory</key>
<string>IOService</string>
<key>IOPCIPrimaryMatch</key>
<string>
0x00f010de&amp;0xfff0ffff
0x019010de&amp;0xfff0ffff
0x040010de&amp;0xfff0ffff
0x042010de&amp;0xfff0ffff
0x05e010de&amp;0xfff8ffff
0x05f010de&amp;0xfff0ffff
0x060010de&amp;0xffe0ffff
0x062010de&amp;0xffe0ffff
0x064010de&amp;0xffe0ffff
0x06e010de&amp;0xfff0ffff
0x086010de&amp;0xffe0ffff
0x08a010de&amp;0xffe0ffff
0x0a2010de&amp;0xffa0ffff
0x0a6c10de&amp;0xfff0ffff
0x0ca010de&amp;0xffe0ffff
</string>
<key>IOProbeScore</key>
<integer>60000</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
</dict>
</dict>
<key>OSBundleCompatibleVersion</key>
<string>1.2.0</string>
<key>OSBundleLibraries</key>
<dict>
<key>com.apple.NVDAResman</key>
<string>1.2.0</string>
<key>com.apple.kpi.iokit</key>
<string>9.0.0</string>
<key>com.apple.kpi.libkern</key>
<string>9.0.0</string>
</dict>
<key>OSBundleRequired</key>
<string>Safe Boot</string>
</dict>
</plist>


- Installed NVEnabler.kext to E/E, changed permissions, rebuilt caches, etc.

On reboot, my display hangs; it doesn't go black, or blank, it just sits as it is with the boot log stuck, never displaying the OSX Desktop. I thought the system was completely hung, but I am able to get it to a shutdown state by "flying blind". Since I can't really control anything at this point, I rebooted into single user mode, where NVEnabler was already loaded, and did an ioreg dump; see attached.

Click to view attachment

If anyone can help out, or if someone can direct me to a post in this thread I might have missed that explains how to fix this, I'd really appreciate it.



Since this last post I tried injecting display-cfg properties (using the MacBook strings outlined in the 1st post) for display 0 and 1, and I'm seeing the same results as above.

Can anyone help out here? Did I not provide information I should have?

Krazubu
Feb 17 2011, 03:15 PM
Crackmac
Most likely, NVEnabler is simply not loaded due to bad permissions or cache rebuilding.
crackmac
Feb 17 2011, 04:53 PM
QUOTE (Krazubu @ Feb 17 2011, 10:15 AM) *
Crackmac
Most likely, NVEnabler is simply not loaded due to bad permissions or cache rebuilding.


C'mon, dude, give me a little more credit than that...

Driver is loaded, kernel log below. It's possible that it might be unloading on an error, but if that's happening I can't tell. My previous post contains an IOReg dump from manually loading NVE in single-user mode.

Note: On this run, I removed the @1 entires from NVE's Info.plist, because I did see a message previously that it couldn't add a @1 property for some reason. However, the end result is still the same.

CODE

Feb 17 11:33:53 localhost kernel[0]: succeeded
Feb 17 11:33:53 localhost kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:33:53 localhost kernel[0]: AppleIntelCPUPowerManagementClient: readyvendor:device: 0x8086:0x10ea.
Feb 17 11:33:53 localhost kernel[0]: AppleIntelE1000e(Info): changing MTU from 0 to 1500
Feb 17 11:33:53 localhost kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:33:53 localhost kernel[0]: NVClockX: Vendor ID: 10de, Device ID: a6c
Feb 17 11:33:53 localhost kernel[0]: NVClockX: Architecture: 800000
Feb 17 11:33:53 localhost kernel[0]: NVClockX: GT218 [NVS 3100M]
Feb 17 11:33:53 localhost kernel[0]: NVClockX: Memory mapped successfully
Feb 17 11:33:53 localhost kernel[0]: Error reading BIOS
Feb 17 11:33:53 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SAT0@1F,2/AppleIntel5SeriesAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/TOSHIBA MK5056GSY Media/IOGUIDPartitionScheme/OS X@2
Feb 17 11:33:53 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Feb 17 11:33:53 localhost kernel[0]: Kernel is LP64
Feb 17 11:33:53 localhost kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:33:55 localhost kernel[0]: AppleIntelE1000e: Ethernet address 5c:26:0a:24:2b:80
Feb 17 11:33:55 localhost kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:33:55 localhost kernel[0]: systemShutdown false
Feb 17 11:33:56 localhost kernel[0]: Waiting for DSMOS...
Feb 17 11:33:58 Victor-Sorianos-iMac kernel[0]: AppleIntelE1000e(Info): Link is Up 100 Mbps Full Duplex, Flow Control: None
Feb 17 11:34:01 Victor-Sorianos-iMac kernel[0]: Previous Shutdown Cause: 3
Feb 17 11:34:01 Victor-Sorianos-iMac kernel[0]: Refusing new kext com.apple.iokit.IONetworkingFamily, v1.10: already have loaded v1.9.
Feb 17 11:34:01 Victor-Sorianos-iMac kernel[0]: NVDANV50HAL loaded and registered.
Feb 17 11:34:01 Victor-Sorianos-iMac kernel[0]: NVEnabler: init : begin
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : probe
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : ROM shadow enable
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : patch PRAMIN
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : patch PROM
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : patch bios at 0xc0000
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: dcb table at offset 0x51a1
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: dcb numentries 16
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 0: 02033300
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 1: 02011362
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 2: 08022382
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: 2 not grouped
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: 3 not grouped
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Channel 1: 03
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Channel 2: 0c
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Model found: Unknown nVidia card
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG VRAM: 512
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property device_type
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property @0,name
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler::probe fails
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: DSMOS has arrived
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: init : begin
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : probe
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : ROM shadow enable
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : patch PRAMIN
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : patch PROM
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : patch bios at 0xc0000
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: dcb table at offset 0x51a1
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: dcb numentries 16
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 0: 02033300
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 1: 02011362
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 2: 08022382IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: 2 not grouped
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: 3 not grouped
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Channel 1: 03
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: Channel 2: 0c
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Model found: Unknown nVidia card
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG VRAM: 512
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property device_type
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: DEBUG Setting property @0,name
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler::probe fails
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: init : begin
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : probe
Feb 17 11:34:02 Victor-Sorianos-iMac kernel[0]: NVEnabler: probe : ROM shadow enable
Feb 17 11:34:03 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch PRAMIN
Feb 17 11:34:03 dhcp-128-94-149-58 kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:03 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch PROM
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch bios at 0xc0000
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: dcb table at offset 0x51a1
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: dcb numentries 16
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 0: 02033300
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 1: 02011362
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 2: 08022382
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: 2 not grouped
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: 3 not grouped
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Channel 1: 03
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Channel 2: 0c
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Model found: Unknown nVidia card
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG VRAM: 512
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property device_type
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,name
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler::probe fails
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: init : begin
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : probe
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : ROM shadow enable
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch PRAMIN
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch PROM
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch bios at 0xc0000
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: dcb table at offset 0x51a1
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: dcb numentries 16
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 0: 02033300
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 1: 02011362
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 2: 08022382
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: 2 not grouped
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: 3 not grouped
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Channel 1: 03
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Channel 2: 0c
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Model found: Unknown nVidia card
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG VRAM: 512
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property device_type
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,name
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler::probe fails
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: init : begin
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : probe
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : ROM shadow enable
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch PRAMIN
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch PROM
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: False ROM signature: 0xffff
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: probe : patch bios at 0xc0000
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: dcb table at offset 0x51a1
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: dcb numentries 16
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 0: 02033300
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 1: 02011362
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 2: 08022382
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: 2 not grouped
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: 3 not grouped
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Channel 1: 03
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: Channel 2: 0c
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Model found: Unknown nVidia card
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG VRAM: 512
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Feb 17 11:34:04 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property device_type
Feb 17 11:34:05 dhcp-128-94-149-58 kernel[0]: NVEnabler: DEBUG Setting property @0,name
Feb 17 11:34:05 dhcp-128-94-149-58 kernel[0]: NVEnabler::probe fails
Feb 17 11:34:05 dhcp-128-94-149-58 kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:34:05 dhcp-128-94-149-58 kernel[0]: NVDA: rmStart failed
Feb 17 11:34:05 dhcp-128-94-149-58 kernel[0]: IT87x: [Warning] found unsupported chip ID=0x4b00
Feb 17 11:34:38: --- last message repeated 1 time ---
Feb 17 11:34:38 dhcp-128-94-149-58 kernel[0]: systemShutdown true
Feb 17 11:34:38: --- last message repeated 1 time ---
Feb 17 11:34:38 dhcp-128-94-149-58 kernel[0]: Kext loading now disabled.
Feb 17 11:34:38 dhcp-128-94-149-58 kernel[0]: Kext unloading now disabled.
Feb 17 11:34:38 dhcp-128-94-149-58 kernel[0]: Kext autounloading now disabled.
Feb 17 11:34:38 dhcp-128-94-149-58 kernel[0]: Kernel requests now disabled.

Krazubu
Feb 17 2011, 05:52 PM
You didn't give the available outputs on that laptop.

It seems that your Laptop has an eDP internal display, that is the problem.
Try with that attached roughly edited ROM. Load that ROM using NVE plist.
Click to view attachment

If it ever works I'll try to do a more refined edit as this one has all external outs disabled.

Use this NVCAP :
0401010100000100000000000000000a00000000

those display-cfg strings :
03010f00
ffffffff
crackmac
Feb 17 2011, 06:24 PM
QUOTE (Krazubu @ Feb 17 2011, 12:52 PM) *
You didn't give the available outputs on that laptop.


Not sure if there's some official designation related to NVE that you're referring to, or that I need to provide, but the laptop has its internal display (1920x1080), a VGA output, and an HDMI output. The docking station also has 2 DVI outputs, each with corresponding HDMI outputs as well. I would suspect the laptop's dock connector has pins to drive those as well, unless they are all driven via HDMI somewhow.

AFAIK only one video adapter is being identified, and that's the NVS3100m; I'm not sure if the Intel chipset video could be causing a problem despite it not being seen on the PCI-Express bus. See my lspci output below for reference.

CODE

00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI
[8086:d132] (rev 11)
Subsystem: Dell Device [1028:040b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Capabilities: <access denied>

00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI
Express Root Port 1 [8086:d138] (rev 11) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00007000-00007fff
Memory behind bridge: d0000000-e30fffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:08.0 System peripheral [0880]: Intel Corporation Core Processor
System Management Registers [8086:d155] (rev 11)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Capabilities: <access denied>

00:08.1 System peripheral [0880]: Intel Corporation Core Processor
Semaphore and Scratchpad Registers [8086:d156] (rev 11)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Capabilities: <access denied>

00:08.2 System peripheral [0880]: Intel Corporation Core Processor
System Control and Status Registers [8086:d157] (rev 11)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Capabilities: <access denied>

00:08.3 System peripheral [0880]: Intel Corporation Core Processor
Miscellaneous Registers [8086:d158] (rev 11)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:10.0 System peripheral [0880]: Intel Corporation Core Processor QPI
Link [8086:d150] (rev 11)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:10.1 System peripheral [0880]: Intel Corporation Core Processor QPI
Routing and Protocol Registers [8086:d151] (rev 11)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:19.0 Ethernet controller [0200]: Intel Corporation 82577LM Gigabit
Network Connection [8086:10ea] (rev 05)
Subsystem: Dell Device [1028:040b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 51
Region 0: Memory at e9600000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at e9680000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 8040 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series
Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) (prog-if 20
[EHCI])
Subsystem: Dell Device [1028:040b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e9670000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd

00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series
Chipset High Definition Audio [8086:3b56] (rev 05)
Subsystem: Dell Device [1028:040b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 53
Region 0: Memory at e9660000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel

00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) (prog-if 00
[Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00006000-00006fff
Memory behind bridge: e8200000-e95fffff
Prefetchable memory behind bridge: 00000000e9700000-00000000e98fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 2 [8086:3b44] (rev 05) (prog-if 00
[Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: e6e00000-e81fffff
Prefetchable memory behind bridge: 00000000e9900000-00000000e9afffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 3 [8086:3b46] (rev 05) (prog-if 00
[Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=04, subordinate=05, sec-latency=0
I/O behind bridge: 00002000-00003fff
Memory behind bridge: e3100000-e59fffff
Prefetchable memory behind bridge: 00000000ec000000-00000000efffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.3 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 4 [8086:3b48] (rev 05) (prog-if 00
[Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=06, subordinate=0b, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: e5a00000-e6dfffff
Prefetchable memory behind bridge: 00000000e9b00000-00000000e9cfffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series
Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05) (prog-if 20
[EHCI])
Subsystem: Dell Device [1028:040b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 17
Region 0: Memory at e9650000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev a5) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>

00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset
LPC Interface Controller [8086:3b07] (rev 05)
Subsystem: Dell Device [1028:040b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
Kernel modules: iTCO_wdt

00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series
Chipset 6 port SATA AHCI Controller [8086:3b2f] (rev 05) (prog-if 01
[AHCI 1.0])
Subsystem: Dell Device [1028:040b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 50
Region 0: I/O ports at 8090 [size=8]
Region 1: I/O ports at 8080 [size=4]
Region 2: I/O ports at 8070 [size=8]
Region 3: I/O ports at 8060 [size=4]
Region 4: I/O ports at 8020 [size=32]
Region 5: Memory at e9640000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
Kernel modules: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset
SMBus Controller [8086:3b30] (rev 05)
Subsystem: Dell Device [1028:040b]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin C routed to IRQ 10
Region 0: Memory at e9630000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at 8000 [size=32]
Kernel modules: i2c-i801

01:00.0 VGA compatible controller [0300]: nVidia Corporation GT218
[NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:040b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e2000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at e0000000 (64-bit, prefetchable) [size=32M]
Region 5: I/O ports at 7000 [size=128]
Expansion ROM at e3000000 [disabled] [size=512K]
Capabilities: <access denied>
Kernel driver in use: nouveau
Kernel modules: nouveau, nvidiafb

01:00.1 Audio device [0403]: nVidia Corporation High Definition Audio
Controller [10de:0be3] (rev a1)
Subsystem: Dell Device [1028:040b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at e3080000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel

03:00.0 Network controller [0280]: Intel Corporation Centrino
Ultimate-N 6300 [8086:422b] (rev 35)
Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN [8086:1121]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 52
Region 0: Memory at e6e00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlagn
Kernel modules: iwlagn

04:00.0 CardBus bridge [0607]: Ricoh Co Ltd Device [1180:e476] (rev 02)
Subsystem: Dell Device [1028:040b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 18
Region 0: Memory at e5940000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=04, secondary=05, subordinate=08, sec-latency=176
Memory window 0: ec000000-effff000 (prefetchable)
Memory window 1: e3400000-e37ff000
I/O window 0: 00002000-000020ff
I/O window 1: 00002400-000024ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket

04:00.1 SD Host controller [0805]: Ricoh Co Ltd Device [1180:e822]
(rev 03) (prog-if 01)
Subsystem: Dell Device [1028:040b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 19
Region 0: Memory at e5930000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: sdhci-pci
Kernel modules: sdhci-pci

04:00.4 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd Device [1180:e832]
(rev 03) (prog-if 10 [OHCI])
Subsystem: Dell Device [1028:040b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 16
Region 0: Memory at e5900000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci, ohci1394

3f:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath
Architecture Generic Non-Core Registers [8086:2c52] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder [8086:2c81] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link
0 [8086:2c90] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Kernel modules: i7core_edac

3f:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI
Physical 0 [8086:2c91] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:03.0 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller [8086:2c98] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:03.1 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Target Address Decoder [8086:2c99] (rev
04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:03.4 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Test Registers [8086:2c9c] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:04.0 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 0 Control Registers [8086:2ca0]
(rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:04.1 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 0 Address Registers [8086:2ca1]
(rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:04.2 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 0 Rank Registers [8086:2ca2] (rev
04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:04.3 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 0 Thermal Control Registers
[8086:2ca3] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:05.0 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 1 Control Registers [8086:2ca8]
(rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:05.1 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 1 Address Registers [8086:2ca9]
(rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:05.2 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 1 Rank Registers [8086:2caa] (rev
04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

3f:05.3 Host bridge [0600]: Intel Corporation Core Processor
Integrated Memory Controller Channel 1 Thermal Control Registers
[8086:2cab] (rev 04)
Subsystem: Intel Corporation Device [8086:8086]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
crackmac
Feb 17 2011, 08:07 PM
QUOTE (Krazubu @ Feb 17 2011, 12:52 PM) *
You didn't give the available outputs on that laptop.

It seems that your Laptop has an eDP internal display, that is the problem.
Try with that attached roughly edited ROM. Load that ROM using NVE plist.
Click to view attachment

If it ever works I'll try to do a more refined edit as this one has all external outs disabled.

Use this NVCAP :
0401010100000100000000000000000a00000000

those display-cfg strings :
03010f00
ffffffff


This didn't seem to work, but I'm attaching my NVE plist to make sure I didn't mess anything up. What's really strange is that the Chameleon GraphicsEnabler will work with the internal display and get me QE/CI, but of course then I can't shutdown or use the external outputs.

Click to view attachment
Krazubu
Feb 18 2011, 10:33 AM
I'll look a bit deeper when I have time.
crackmac
Feb 18 2011, 02:07 PM
QUOTE (Krazubu @ Feb 18 2011, 05:33 AM) *
I'll look a bit deeper when I have time.


Krazubu,

No problem, looking forward to any other advice/help you can give, and let me know if there's anything else I can do to help debug the problem. Hope to find a solution for this, as I really don't want to have to go back to Win7... sad.gif
JrCs
Feb 20 2011, 05:24 PM
Hi all,

i can't upgrade my system above 10.6.2 because if i do this i have a blank screen.
I have try to used NVEnabler on a 10.6.6 system without luck: the nVidia driver is not used and i go in a 1280xXXX mode without acceleration.
My Card is a Zotac 9800GTX+ Amp Edition. It has 2 DVI ports and i connect one of the port to a HDMI monitor.
This is what i have in the kernel.log: http://pastie.org/1586216

Can someone help me to fix my problem, i'll really appreciate.

I can made all the tests you want.

Edit: after reading a lot of posts, there seems an NVCap problem. Can you confirm Krazubu ? If yes how can i check and test ?

JrCs
Krazubu
Feb 21 2011, 03:00 PM
crackmac,
Try this better formed ROM
Click to view attachment

Use this NVCAP :
04010101000001003e0000000000000a00000000

those display-cfg strings :
03010f00 - ffff0001
Breaking Bad
Feb 21 2011, 06:23 PM
-

Cheers,
bb.
JrCs
Feb 22 2011, 08:41 AM
Hi Krazubu,

can you give me a hint please about my post below ?

Best Regards
Breaking Bad
Feb 22 2011, 09:23 PM
-
Click to view attachment

Cheers,
bb.
crackmac
Feb 22 2011, 09:27 PM
QUOTE (Krazubu @ Feb 21 2011, 10:00 AM) *
crackmac,
Try this better formed ROM
Click to view attachment

Use this NVCAP :
04010101000001003e0000000000000a00000000

those display-cfg strings :
03010f00 - ffff0001


Krazubu,

Still no luck with this. Just to be clear and make sure I'm doing this right, I've added the properties to the Info.plist as follows:

- keys @0,display-cfg and @1,display-cfg as type string using the above values
- key NVCAP as type data using the above values
- key nvbios as type data using the attached ROM
- removed skipvbios_disabled key

Is this correct? If so, this still isn't working... sad.gif
Krazubu
Feb 23 2011, 08:30 AM
Display-cfg strings are data, however I doubt it's the cause of the problem.
crackmac
Feb 23 2011, 03:16 PM
QUOTE (Krazubu @ Feb 23 2011, 03:30 AM) *
Display-cfg strings are data, however I doubt it's the cause of the problem.


You're right. I tried just to be paranoid, but still no luck. Is there any debug information I can provide that might help, or a build with additional debug logging I can run that might identify the source of the problem?

EDIT: Krazubu, not sure if it helps, but one thing I saw in the debug log different from the other attempts with the latest ROM and settings was the following:

QUOTE
2/23/11 10:14:57 AM kernel NVDA: rmStart failed
2/23/11 10:14:57 AM kernel NVDA,Display-B: Not usable


This came after all the messages which shows NVE perfroming property setting and the like. Hopefully this might help out...
Krazubu
Feb 24 2011, 06:03 PM
Providing infos as asked in post #1 would help to get answered.
Breaking Bad
Feb 24 2011, 06:51 PM
-

Cheers,
bb.

Kernel.log - Click to view attachment
NVEnabler Ioreg Dump - Click to view attachment
- DSDT.aml extracted with DSDTSE - Click to view attachment
crackmac
Feb 24 2011, 07:08 PM
Krazubu,

Seeing that Chameleon's Graphics Enabler is working for me out-of-box (with the exception of preventing shutdown), is it possible to configure it similar to NVEnabler so that I can make use of all the video outputs? The ones I would be most interested in are:

- The internal display
- The built-in external DP
- The dock's 2 DVI/DP ports

If I can drive 2 external monitors while docked, I'd be all set; even better if I can drive the built-in display at the same time as well. Is it possible to provide NVCAP and display-cfg info to Chameleon's built-in version of NVE? If so, what strings should I provide to enable the aforementioned ports?

Note that currently, I can drive the internal and ONE of the dock's DVI/DP ports with no mods.

If none of that will work, then I'm short on options, because at this point NVE isn't even working with the built-in display.

In any event, just a brainstorm; what do you think?
JrCs
Feb 26 2011, 10:52 AM
Hi Krazubu,

i can't upgrade my system above 10.6.2 because if i do this i have a blank screen.
i have a Zotac 9800GTX+ Amp Edition (Device ID: 0x0612). It has 2 DVI ports and i connect one of the port to a HDMI monitor.
It work well in 10.6.2 with Chameleon Injection but not above.

Here the informations that perhaps can help you:

Working Configuration OSX 10.6.2 with Chameleon GraphicsEnabler: Click to view attachment
Not Working Configuration (blank screen) OSX 10.6.6 with NVEnabler 64:
ioreg dump: Click to view attachment
kernel.log: Click to view attachment

My Graphic Cards ROM: Click to view attachment

Karzubu if you can give me a hint, i'll really appreciate (i'm french and i connect to #radeonhd sometimes)
AlexanderPD
Feb 26 2011, 02:06 PM
Hi Krazubu, sorry if i'm just "another one that spam questions", i'm just trying all i can to make internal lcd works on vaios.
I'm not that good in dsdt editing and whatelse, but tell me if what i'm going to say it's totally nonsense or not smile.gif
In Windows i can see the "hardware" name of internal lcd, it's not a PNPxxxx (with x=hex number), but MS_0025.
So i tried to force MS_0025 via dsdt:

CODE
                    Device (LCD)
                    {
                        Name (_ADR, 0x0110)
                        Name (_HID, EisaId ("MS_0025"))


the problem here is the EisaID, it want's 3 Uppercase letters and 4 numbers. My problem here is the "_" that is not a letter. Can be this "non standard" name to fool OsX and make lcd totally death?

I studied a bit the nvidia windows driver installer, and it do this for my vga:

CODE
[FAEIDS_78_addreg]
HKR,,OverrideEdidFlags0,%REG_BINARY%,7C,00,00,00,00,00,FF,FF,04,00,00,00,08,02,36,7F
HKR,,OverrideEdidFlags1,%REG_BINARY%,36,7f,fa,08,00,00,ff,ff,0d,00,00,00,15,6A,29,17,00,EA,A8,E0,99,57,4B,92,25,1C,5
0,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,37,2F,90,84,61,B1,
1
E,30,20,30,26,00,98,E6,10,00,00,18,9C,27,90,90,61,B1,1E,30,20,30,26,00,98,E6,10,
0
0,00,18,00,00,00,FC,00,4E,76,69,64,69,61,20,44,65,66,61,75,6C,00,00,00,FC,00,74,
2
0,46,6C,61,74,20,50,61,6E,65,6C,00,00
HKR,,OverrideEdidFlags2,%REG_BINARY%,36,7f,25,00,00,00,ff,ff,0d,00,00,00,15,6A,29,17,00,EA,A8,E0,99,57,4B,92,25,1C,5
0,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,69,3A,80,18,71,38,
3
6,40,50,32,4A,00,99,E6,10,00,00,18,BB,30,80,20,71,38,32,40,50,32,4A,04,99,E6,10,
0
0,00,18,00,00,00,FC,00,4E,76,69,64,69,61,20,44,65,66,61,75,6C,00,00,00,FC,00,74,
2
0,46,6C,61,74,20,50,61,6E,65,6C,00,00
HKR,,Panel01,%REG_SZ%,",MS_,,08FA"
HKR,,Panel02,%REG_SZ%,",MS_,,0025"
HKR,,Panel03,%REG_SZ%,",MS_,,0025"


FAEIDS_78_addreg is one of the procedure called from the installer for my VEN-DEV-SUBVENDOR combination.
The first string looks like an NVCAP.. second and third string are EDIDs without initial header, but not the same edid that we can get from windows using tools like MonInfo.. i really don't know where they came from.

all this crap have a sort of "sense" or it's just crap? Thank you for your time smile.gif

edit: i just checked and first EDID is for MS_08FA, second is for MS_0025.
Maybe there are 2 MS_0025 because my vaio (F series) is shipped with 2 lcd, one with 1920x1080 the other with 1600x900.
Both the 2 EDIDs have non sense in the timing section, the second tell about a 314x881 resolution O.o Maybe a sony proprietary edid standard?
If needed i can post both the report for the right edid and the nonsense one! I'm not posting now because is looong and annoying tongue.gif

edit2: using that 7C,00,00,00,00,00,FF,FF,04,00,00,00,08,02,36,7F as NVCAP osX boot normally, so internal lcd blank and external working, but from IOREG i can see the external monitor as Display@A, maybe this means something!
Krazubu
Feb 28 2011, 11:46 AM
QUOTE
the problem here is the EisaID, it want's 3 Uppercase letters and 4 numbers. My problem here is the "_" that is not a letter. Can be this "non standard" name to fool OsX and make lcd totally death?

Don't think so
If you wanna mess with IOReg content don"t do it through dsdt but with an injecter. much flexible and simpler for trials.

QUOTE
The first string looks like an NVCAP..

After many beers

QUOTE
second and third string are EDIDs without initial header, but not the same edid that we can get from windows using tools like MonInfo.. i really don't know where they came from.

probably EDID extensions

QUOTE
all this crap have a sort of "sense" or it's just crap? Thank you for your time

yes and no
EDID extension might be something to dig, so is IOREG data, but our trials so far seems to say no.

QUOTE
edit2: using that 7C,00,00,00,00,00,FF,FF,04,00,00,00,08,02,36,7F as NVCAP osX boot normally, so internal lcd blank and external working, but from IOREG i can see the external monitor as Display@A, maybe this means something!

Read as a NVCAP, the bytes here tell that there's a display as Display-A, nothing encouraging, most random string would do the same, no string would probably do to.
AlexanderPD
Feb 28 2011, 03:16 PM
QUOTE (Krazubu @ Feb 28 2011, 12:46 PM) *
After many beers


i lol'd at this laugh.gif

but i'm still researching on this and seems like all the laptop with "MS_" (almost all the Vaios..) as initial HID and with nvidia have a total blank screen on startup! They are not EISA-type ID after all sad.gif
Sadly i can't see the HID from ioreg so i can't inject a new one sad.gif Any idea to how to try this "overwrite"?

Thank you again smile.gif
bisk
Feb 28 2011, 09:24 PM
OK !

I've been pulling my hair out for quite a while on this one. I've read all 25 pages of this post and I'm about to do it again but, in the meantime, I just gotta know if it's something really silly that I'm missing here.

I've got an HP TouchSmart IQ506 with NVidia GeForce 9300M GS/256. I've tried all of the usual injectors, including this one and I have tried the MacBook display-cfgs for the 9400M but always greeted by the same black screen.

VNC shows me that I have resman but the system is unable to find it's internal display. I do see LCD display objects defined in the registry but I don't know what to do with this info.


ioreg dump included as per instruction.

Any guidance will be massively appreciated !

bisk
AlexanderPD
Feb 28 2011, 09:53 PM
QUOTE (bisk @ Feb 28 2011, 10:24 PM) *
OK !

I've been pulling my hair out for quite a while on this one. I've read all 25 pages of this post and I'm about to do it again but, in the meantime, I just gotta know if it's something really silly that I'm missing here.

I've got an HP TouchSmart IQ506 with NVidia GeForce 9300M GS/256. I've tried all of the usual injectors, including this one and I have tried the MacBook display-cfgs for the 9400M but always greeted by the same black screen.

VNC shows me that I have resman but the system is unable to find it's internal display. I do see LCD display objects defined in the registry but I don't know what to do with this info.

Looks like NVE finds the video chip OK ...

.....


it's only a personal request.. i suffer of this problem too but from a vaio tongue.gif Can you post your edid or (better) your hardware id for your display? You can found it using "moninfo" from windows: http://www.entechtaiwan.com/files/moninfo.exe
If i'm lucky (and you just run out of luck) you have my same problem biggrin.gif
Monitor ID is taken from 3 letters and 4 hex number (so, normal number + A B C D E F letters), mine is MS_0025 (third letter is underscore in my case) tongue.gif
bisk
Mar 1 2011, 01:24 AM
OK, I did as you requested and got:

Model Name: t Flat Panel
Windows Desc: Generic PnP Monitor
Manufacturer: NVD
Plug & Play ID: NVD0100
EDID rev.: 1.3

There is also an item called Display IDs in the upper right hand corner with a Raw Data dump under it where the ID that, I think you're looking for, appears again, right on top.

NV0100 [Registry-Active]
NV0100 [Registry]
ABC8014 [Sample]
ABCF201 [Sample]
ABC0D1D [Sample]
ABC8114 [Sample]
ABC3D3D [Sample]

So, it looks like NVD0100 or N V D Zero One Zero Zero for my integrated LCD display.

What can I do with this or does this plop me into the camp of the hopeless ?
AlexanderPD
Mar 1 2011, 07:19 AM
argh.. sorry i was hoping in a different code sad.gif My theory on "why internal lcd it's totally blank" is failing sad.gif
Just to let u know.. i think this problem is "that code related", i just verified that if manufacter is MS_ or NVD it doesn't work.. but i really don't know why.. someone theoryze that is the snc device fault but i don't know nothing for sure sad.gif

also: can u post the raw data for NVD0100? It's the EDID.. maybe it's useless (probably) but i always hope in some luck tongue.gif

edit: can you try this?
boot hackintosh without any injecter or graphicsenabler, so you can go in your os in VESA mode (1024x768 without QI/QE)
download this DSDT editor: http://www.osx86.es/?p=610
extract your DSDT table
Search for something that looks like:
CODE
                    Device (LCD)
                    {
                        Name (_ADR, 0x0110)

After that "name" add:
CODE
Name (_HID, EisaId("NVD0100"))


if you have more that 1 "Device (LCD)" add that string for all your lcd device. If you don't have nothing like "Name (_ADR, 0x0110) don't worry, just add the new string after the "Device (LCD) {"
compile, save it where u want
Go in Extra folder
edit com.apple.Boot.plist
Add a new element called "DSDT", type String
Add your dsdt path value to the new element, something like "/DSDT.aml" if you just saved it in your root.
Save and reset
Remember that you must add the .aml file, not the .dsl!

aaaand.. it if works.. we just solved the "vaio and similar blank screen problem" biggrin.gif
*cross his fingers*
Krazubu
Mar 1 2011, 12:05 PM
Breaking bad
Restore older kexts that were working (along with OpenGL.framework)

Bisk
You didn't inject display-cfg, try 03010300 for 1st display
bisk
Mar 2 2011, 12:24 AM
QUOTE (Krazubu @ Mar 1 2011, 12:05 PM) *
Breaking bad
Restore older kexts that were working (along with OpenGL.framework)

Bisk
You didn't inject display-cfg, try 03010300 for 1st display


Kruzubu,

You are correct, the dump from my earlier post was in the simplest form, without any enhancements. I had tried the 9400M display-cfg values from page 1 to no avail or at least I thought that I did. Perhaps, I had done it incorrectly.

So, attempted again to add @0,display-cfg accompanied with the data value of 03010300 to Info.plist under addProperties and got the BIG BLACK.


AlexanderPD,

I'll look into how to dump the EDID with this utility that you turned me on to. I understand the DSDT edits but not sure what it means to add DSDT as an "element" to c.a.B.plist. Do you mean a kernel flag ? Oh, maybe you are just trying to make sure that it gets loaded ... if I simply drop DSDT.aml into /Extra that happens. Of course, you can't know my level of undertstanding. That's fine smile.gif
I'll mess with the DSDT stuff now. I actually have seen LCD in my DSDT dump from ubuntu. BTW, when ubuntu comes up on this TouchSmart, the whole display shimmies back and forth by about an inch like there's an earthquake going on or something. I am able to dump the /proc dsdt and codec files to a USB stick more or less by feel though. I've done it enough times wink.gif


Kruzubu,

Here is kernel.log and the ioreg dump again along with my NVEnabler 64.kext for the @0,display-cfg try ...
bisk
Mar 2 2011, 08:37 AM
QUOTE (bisk @ Mar 2 2011, 12:24 AM) *
Kruzubu,

You are correct, the dump from my earlier post was in the simplest form, without any enhancements. I had tried the 9400M display-cfg values from page 1 to no avail or at least I thought that I did. Perhaps, I had done it incorrectly.

So, attempted again to add @0,display-cfg accompanied with the data value of 03010300 to Info.plist under addProperties and got the BIG BLACK.


AlexanderPD,

I'll look into how to dump the EDID with this utility that you turned me on to. I understand the DSDT edits but not sure what it means to add DSDT as an "element" to c.a.B.plist. Do you mean a kernel flag ? Oh, maybe you are just trying to make sure that it gets loaded ... if I simply drop DSDT.aml into /Extra that happens. Of course, you can't know my level of undertstanding. That's fine smile.gif
I'll mess with the DSDT stuff now. I actually have seen LCD in my DSDT dump from ubuntu. BTW, when ubuntu comes up on this TouchSmart, the whole display shimmies back and forth by about an inch like there's an earthquake going on or something. I am able to dump the /proc dsdt and codec files to a USB stick more or less by feel though. I've done it enough times wink.gif


Kruzubu,

Here is kernel.log and the ioreg dump again along with my NVEnabler 64.kext for the @0,display-cfg try ...



OK ... I did the DSDT mods as suggested ...

Device (LCD)
{
Name (_ADR, 0x0118)
Name (_HID, EisaId("NVD0100"))
Name (CUBR, 0x64)
Method (_BCL, 0, NotSerialized)
{
Return (Package (0x0D)
{
0xFF,
0x80,
0x03,
0x1A,
0x33,
0x4D,
0x66,
0x80,
0x99,
0xB3,
0xCC,
0xE6,
0xFF
})
}
}

Device (LCD)
{
Name (_ADR, 0x0400)
Name (_HID, EisaId("NVD0100"))
Name (CUBR, 0x64)
Method (_BCL, 0, NotSerialized)
{
Return (Package (0x0B)
{
0x02,
0x08,
0x0E,
0x14,
0x1A,
0x20,
0x26,
0x2C,
0x32,
0x38,
0x3E
})
}
}

and I can see in the Service Tree that both devices do take on the NVD0100 name but if I try to boot with NVE, I still get the black screen.

Is there another step that I'm missing in there somewhere ?

Here is my EDID dump ...
AlexanderPD
Mar 2 2011, 11:01 AM
wow 2 different internal lcd with 2 different address? Hp's dsdt really sucks!
btw.. what i'm "suggesting" it's only a test based on my personal and not verified theory, so i'm using you as a "human experiment" XD
I stated that you can use the same "Name (_HID, EisaId("NVD0100"))" string on both of the LCD because i was thinking, like vaios, your dsdt table can talk about 2 identical VGA with 2 identical configurations. But in your case the addresses are different, so you must figure what is the real one LCD device. You can make 2 try, in the first delete the "Name (_HID, EisaId("NVD0100"))" from the first LCD, without erasing from second LCD.
In the second reverse this thing, delete second and leave the first.
This because if you use the same HID for different devices the os checks for an UID, an unique identifier (usually a counter) that is added to main HardwareID.

I Explain my theory, really not confirmed and "not that possible":
In our vaios vga works, but only on external and hdmi port. The external monitor is named "display@B" so osX in someway can reach the main lcd and assign to him the "display@A". In my theory osx tell to the nvidia driver: "hey nvidia driver, i found this internal lcd on LVDS port, please take care of him"
Nvidia driver answers: "k, i'll handle it!"
but when he goes to check he can't found (or he can't reach) the HardwareID, so he ignore the LCD. Why a driver must get the HiD? Good question! I'm not sure of it, but seems like nvidia driver on other os like to know the HiD of the internal LCD. This because:
On Windows, when you install the driver, there is a "custom configuration" made for my Vaio (or better, my combination of VGA, LCD and Sony manufacturer) and the driver manually injects the HiD on windows registry. I found that operation in the appropriate ini file used from nvidia driver installer. So, seems like is an important piece of information.
In Linux driver the "MS_" manufacturer is placed on the main driver option screen, giving to it same importance of the VGA model.
So, probably all my theory is crap, but there is a little % that it's true, so i'm investigating on it. If making the 2 tryes i stated before you can get the internal lcd working this theory it's true, else its missing some important piece of information.
*still cross his fingers*
Krazubu
Mar 2 2011, 11:18 AM
Bisk
Try to load this patched ROM, same display-cfg as before

Click to view attachment
bisk
Mar 3 2011, 02:29 AM
QUOTE (Krazubu @ Mar 2 2011, 11:18 AM) *
Bisk
Try to load this patched ROM, same display-cfg as before

Click to view attachment


OK, Thanks !

I should start here by saying that I'm off to Mexico tomorrow night and I won't be back until March 22nd.
So, unfortunately, I'll need to pick this up again later. I will definitely try and report back on anything suggested in the next 24 hours though.

I did try this but still got the BLACK SCREEN. Just to verify that I did everything right, I

added: the key-> vbios under addProperties
with the data value-> 55AA7EEB 4B373430 30E94C19 77CC5649 ... FFFFFFFF FFFFFFFF FFFFFFFF FFFFFF

The entire buffer was 65535 bytes long.

I extracted it in hex with: xxd -p bisk.rom | tr -d '\n'

I also removed the skipvbios_disabled association.

No DSDT.aml active either, I promise !

Here's a bit of the kernel.log ...

Mar 2 12:00:52 haxmax16 kernel[0]: NVDANV50HAL loaded and registered.
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: init : begin
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: probe : probe
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: probe : ROM shadow enable
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: probe : patch PRAMIN
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: False ROM signature: 0xffff
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: probe : patch PROM
Mar 2 12:00:52 haxmax16 kernel[0]: DSMOS has arrived
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: dcb table at offset 0xba1e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: dcb numentries 16
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 0: 01010323
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 1: 02001300
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 2: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 4: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 5: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 6: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 7: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 8: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 9: 0000000eRT2860WirelessDriver: Ethernet address 00:16:44:d7:97:74
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 10: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 11: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 12: 0000000ecom_chucko_RealtekR1000: Ethernet address 00:22:15:07:57:18
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 13: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 14: 0000000e
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: numentries = 16 num_outputs = 15
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: found LVDS
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Channel 1: 01
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: Channel 2: fe
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Model found: GeForce 9300M GS
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG VRAM: 256
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,name
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,name
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property device_type
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property vbios
Mar 2 12:00:52 haxmax16 kernel[0]: NVEnabler::probe fails
Mar 2 12:01:02 haxmax16 kernel[0]: FakeSMC: key info not found MSDS, length - 6
Mar 2 12:01:02 haxmax16 kernel[0]: ACPI_SMC_PlatformPlugin::start - waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out
Mar 2 12:01:02 haxmax16 kernel[0]: FakeSMC: key not found BEMB, length - 1
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: init : begin
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: probe : probe
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: probe : ROM shadow enable
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: probe : patch PRAMIN
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: False ROM signature: 0xffff
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: probe : patch PROM
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: dcb table at offset 0xba1e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: dcb numentries 16
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 0: 01010323
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 1: 02001300
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 2: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 4: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 5: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 6: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 7: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 8: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 9: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 10: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 11: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 12: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 13: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 14: 0000000e
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: numentries = 16 num_outputs = 15
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: found LVDS
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Channel 1: 01
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: Channel 2: fe
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: DEBUG Model found: GeForce 9300M GS
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: DEBUG VRAM: 256
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Mar 2 12:01:02 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,name
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,name
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property device_type
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property vbios
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler::probe fails
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: init : begin
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: probe : probe
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: probe : ROM shadow enable
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: probe : patch PRAMIN
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: False ROM signature: 0xffff
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: probe : patch PROM
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: dcb table at offset 0xba1e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: dcb numentries 16
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 0: 01010323
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 1: 02001300
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 2: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 3: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 4: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 5: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 6: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 7: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 8: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 9: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 10: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 11: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 12: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 13: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Raw DCB entry 14: 0000000e
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: numentries = 16 num_outputs = 15
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: found LVDS
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Channel 1: 01
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: Channel 2: fe
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Model found: GeForce 9300M GS
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG VRAM: 256
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @1,name
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property @0,name
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property device_type
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler: DEBUG Setting property vbios
Mar 2 12:01:03 haxmax16 kernel[0]: NVEnabler::probe fails

and here is the ioreg dump from this session ...
bisk
Mar 3 2011, 02:48 AM
QUOTE (AlexanderPD @ Mar 2 2011, 11:01 AM) *
wow 2 different internal lcd with 2 different address? Hp's dsdt really sucks!
btw.. what i'm "suggesting" it's only a test based on my personal and not verified theory, so i'm using you as a "human experiment" XD
I stated that you can use the same "Name (_HID, EisaId("NVD0100"))" string on both of the LCD because i was thinking, like vaios, your dsdt table can talk about 2 identical VGA with 2 identical configurations. But in your case the addresses are different, so you must figure what is the real one LCD device. You can make 2 try, in the first delete the "Name (_HID, EisaId("NVD0100"))" from the first LCD, without erasing from second LCD.
In the second reverse this thing, delete second and leave the first.
This because if you use the same HID for different devices the os checks for an UID, an unique identifier (usually a counter) that is added to main HardwareID.

I Explain my theory, really not confirmed and "not that possible":
In our vaios vga works, but only on external and hdmi port. The external monitor is named "display@B" so osX in someway can reach the main lcd and assign to him the "display@A". In my theory osx tell to the nvidia driver: "hey nvidia driver, i found this internal lcd on LVDS port, please take care of him"
Nvidia driver answers: "k, i'll handle it!"
but when he goes to check he can't found (or he can't reach) the HardwareID, so he ignore the LCD. Why a driver must get the HiD? Good question! I'm not sure of it, but seems like nvidia driver on other os like to know the HiD of the internal LCD. This because:
On Windows, when you install the driver, there is a "custom configuration" made for my Vaio (or better, my combination of VGA, LCD and Sony manufacturer) and the driver manually injects the HiD on windows registry. I found that operation in the appropriate ini file used from nvidia driver installer. So, seems like is an important piece of information.
In Linux driver the "MS_" manufacturer is placed on the main driver option screen, giving to it same importance of the VGA model.
So, probably all my theory is crap, but there is a little % that it's true, so i'm investigating on it. If making the 2 tryes i stated before you can get the internal lcd working this theory it's true, else its missing some important piece of information.
*still cross his fingers*


Well, I can tell you for sure that when I look at my IORegistry I see ...

PCI0@0
..GFX0@20000
....LCD@400

and then further down in the PCI0@0 node ...

..POP2@1
....VGA@0
......LCD@118

Whenever we try to inject via NVEnabler, the GFX@2000->LCD@400 is unchanged but the POP2@1 node becomes ...

..POP2@1
....VGA@0
......LCD@118
......NVDA,Display-A@0
......NVDA,Display-B@1

So my guess would be that it's the LCD@118 where the action is !

I'll play some more with your DSDT suggestions and report back.

OK, I'm back wink.gif

I have now tried the name game with PCI0.GFX0.LCD@400 and PCI0.P0P2.VGA.LCD@118 together and individually with no difference in the outcomes. Unfortunately, it's all black sad.gif

Here is an unedited version of my dsdt just in case you are curious ...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2012 Invision Power Services, Inc.