Jump to content

PRO Help needed: Black screen when adding DevID to NVDAResman.kext


Woutje
 Share

14 posts in this topic

Recommended Posts

I have a very difficult problem.. on my notebook:

 

Intel Core 2 Duo P9500

Intel PM95 + ICH9M chipset

nVidia GeForce 9300m GS 256MB

vanilla kernel 9.4.0, Leo 10.5.4 all working OK!

 

When I install either 10.5.2 or 10.5.3 Geforce kext, and I add my Device ID to NVDAResman.kext, I get a black screen when Leopard starts to boot (after the grey screen with apple logo, no weird messages with -c boot flag).

 

To find out where the problem is, I added my Device ID kext by kext...First to NVDANV50HAL, which resulted in the message that this kext was succesfully loaded and registered.. But as soon as I add my DevID to NVDAResman.kext leopard boots (can hear startup sound, and my network is connecting) I get a black screen, no backlight, nothing..

 

This also happens when I try to use the GFX string (EFI) method. I have also tried different NVCAP settings in an injector, but it doesn't seem to make a difference.

 

I have an idea of what it could be.. you see, my notebook is a Centrino 2 notebook with all kinds of new stupid hardware from Intel.. I ran DPCI and above by nVidia card (10de:06e9) which is not recognized (ERROR: Unknown Device) there's an 'Intel Corperation Device' (also ERROR: Unknown Device) with the following ID: 8086:2a41 (0x2a418086). After some searching on the internet, this could very well be: '8086:2a41: Cantiga PCI Express Graphics Port'. (Cantiga is the codename for the PM45 Penryn/Montevina platform: Centrino 2)

 

so, could it be that I would never get QE/CI because my PCI-E Graphics port is not recognised? Or is this not the problem? (I do have VESA support..)

 

Thanks in advance!

 

-Wout

Link to comment
Share on other sites

(hehe, right topic now? :censored2: )

 

Yes i tried, while I was trying all the different NVCAP settings I had an LCD on my VGA port, and a TV on the HDMI port.. But they both didn't get a signal..

 

Could it be that I also have to change something in the NVDAResman.kext, besides the DevID?

Link to comment
Share on other sites

I followed that tutorial a few times already, that's how I found out that I got a black screen when adding my DevID to NVDAResman... without having an injector.. and it also does not work with an injector..

 

I always follow almost every tutorial there is before i start asking questions.. I just hope i'm missing something..

 

Oh, there is one thing.. When I add my DevID to NVDAResman, the following line shows up in during boot:

NVDA: Probe <VGA>

((((than a who lote of NVInjectGo lines..))))

NVDA: Start <VGA> 1

NVDA: Start <VGA> 1 Failed...

 

 

1: What could the black screen mean when adding my DevID to NVDAResman

2: Basically, i have to keep trying different NVCAP settings?

Link to comment
Share on other sites

I think I might have found the problem.

 

When I add my DevID to NVDAResman, I get the following message in the system.log just before my notebook locks up:

 

 

kernel[0]:NVChannel(GL):Graphics channel timeout!

 

 

What could this be?? Do I need to try other OpenGL framework?? If so.. how? I did that once, and it ruind my installation..

Link to comment
Share on other sites

  • 5 months later...

I have an asus m50vm with a 9600m 1024 and finally got QE/CI to work. I used the ipc distro and when installing i selected the nvdarwin 1024 kernel. i had tried befor and selected the latest macbook pro drivers and this didn't work. tried efi gfx strings and got full resolution but no QE/CI. then tried nvdarwin with nothing else and it's working 100%.

 

 

 

good luck

Link to comment
Share on other sites

  • 2 weeks later...

i´ve ipc distro too and selceted latest mbp kexts during install. after that i tried nvdarwin and dsdt patch but both didn´t get me QE/CI. I also get the black screen, only when i remove NvdaResman.kext i get into leopard on my laptop display. my gfx is recognized but no qe/ci and the hdmi and vga out arent working too.

Maybe i have to remove the latest mbp kexts, but how? delete all nv*.kexts and geforce kexts or replace it with older ones ?

Link to comment
Share on other sites

  • 2 months later...

Has anyone resolved this issue? I am having the same problem!

 

i´ve ipc distro too and selceted latest mbp kexts during install. after that i tried nvdarwin and dsdt patch but both didn´t get me QE/CI. I also get the black screen, only when i remove NvdaResman.kext i get into leopard on my laptop display. my gfx is recognized but no qe/ci and the hdmi and vga out arent working too.

Maybe i have to remove the latest mbp kexts, but how? delete all nv*.kexts and geforce kexts or replace it with older ones ?

Link to comment
Share on other sites

  • 4 months later...

I am experiencing this exact issue. I have to remove NVDAResman.kext in order to NOT get a blank screen, and this severely limits my graphics (only get 1024x768 and no QE/CI)

I've tried both iPC release and iDeneb v1.6 10.5.8 Lite Edition, no difference.

 

Mobo: Asus P5VDC-X (VIA chipset)

Gfx: Geforce 8800GTS 640mb

Link to comment
Share on other sites

  • 1 year later...

I have the same issue. I have an EVGA nVidia GeForce 8400GS on an NForce 430 chipset, device ID is 0x06e410de, and the monitor is connected to the VGA port.

 

I've tried every single injector, NVinject, NVKush, NVEnabler, and other methods, e.g. EFI strings, GraphicsEnabler in Chameleon, everything. I would always get either the black screen, or the monitor would shut down after the initial boot process, i.e. loading of the kernel and extensions and stuff.

 

I finally narrowed it down by process of elimination that the issue is with NVDAResman and when I edit it. When I insert my device ID properly and the drivers kick in, that's when I get the monitor turning off. I had some success with NVEnabler. I actually got CI and QE, but it broke the mouse and the keyboard. I would get that issue where the mouse becomes super sensitive and moves in the opposite direction than the one you move it in; the keyboard just doesn't respond. After a restart, the mouse works as it should, but it doesn't respond to any clicks and the keyboard still didn't work.

 

I read somewhere that NForce and nVidia cards had some kind of conflict. They recommended to delete all the device IDs from NVDAResman and just leave the one for my card. Tried that. Didn't work.

 

All this, and the fact that NVEnabler actually yielded CI/QE, leads me to believe that it's an NVCAP issue. I'm going to try EFI strings again with the two different output settings, DVI I/VGA and VGA/DVI I. I really don't understand the difference between those two, so if you can share any insight into that, that'd would be much appreciated. If either of those doesn't work, I'm going to try getting the NVCAP values for my card using this method.

 

If anybody else has figured out this issue or has any good suggestions, please share.

Link to comment
Share on other sites

  • 11 months later...

Hi guys, i have the same problem with NVDAResman.kext, but the card is reported correctly, with the correct ram (a nvidia nvs 135m with 128MB nvram). I can only boot in safe mode if i have the kext installed but i get 1440x900, problem is i loose the rest.

If i delete NVDAResman, then i get all working but resolution is 1024x768.

I remember in a plist there is a setting for the screen resolution, how can i go to manually set it?

If i can set in the boot files then it will work.

Anybody knows how to set screen resolution without using NVDAResman?????

 

Thanks in advance

Link to comment
Share on other sites

 Share

×
×
  • Create New...