Jump to content

6800GS


superstition
 Share

7 posts in this topic

Recommended Posts

I tried Natit with the Kalyway 10.5.1 install DVD and got a kernel panic every time I tried to start up. Nvinject, which was also on the disc, didn't work. I checked the official Nvinject forum and no one seems to be able to get it working.

 

eVGA 6800 GS PCI-e 256 MB.

 

Edit: I accidentally confused my GS with a GT. Oops. I'm looking into posts about the GS now.

Link to comment
Share on other sites

eVGA 6800GS 256 MB PCI-E

Gigabyte GA-P35-DS3L motherboard

e2140 processor with Tuniq at stock speed

two 1 GB DDR-800 PQI ram sticks in dual mode (rated CAS 4 but running at CAS 5)

cheap 2+1 VIA PCI firewire card

Hawking 802.11g PCI wifi (not recognized)

TSScorp IDE DVD combo

Western Digital 7200 RPM SATA drive 120 GB (JS model)

 

Kalyway 10.5.1, with AHCI on and vanilla kernel, one GUID partition

 

I just tried the NVinject 0.2.1 per the instructions in this topic and OS X hangs now. I'm going to write down the messages and post them. It's interesting that when I did the rm in Terminal for the extensions.kext, it appeared in the GUI directory before I rebooted. Does OS X rebuild it immediately? I rebooted with -s, hoping I could remove the extensions.kext and so forth, but the hard drive was mounted as read only.

 

I've read a number of posts about people getting a 6800gs to work, but there's no information about how to go about it. The posts are also old, from the 10.4 era.

Link to comment
Share on other sites

I booted in -x mode and it hung, although at a different point. Here is the plain -v booting:

 

Jettisoning kernel linker.

Resetting IOCatalogue.

display: family specific matching fails

Matching service count = 1

Matching service count = 2

Matching service count = 2

Matching service count = 2

Matching service count = 2

Matching service count = 2

display: family specific matching fails

ACPI_SMC_CtrlLoop :: initCPUCtrlLoop-pmCPUControl (PMIOCSETPSTATABLE) returned Ox45ad780

Jan 6 05:26L01 localhost DirectoryService [40]: Launched version 5.0 (v514)

ALCinject: Starting.

ALCinject: Setting built-in=<data not shown>

ALCinject: Setting layout-id=<data not shown>

Jan 6 05:26L01 localhost WARNING - dsTouch: file was asked to be opened </Library/Preferences/DirectoryService/.DSIsRunning> (File exists)

Apple RTL8169Ethernet: Ethernet address 00:1d:7e:a5:d9:29

display: family specific matching fails

dsmos: Initializing...

dsmos: Hook and decryption contexts set!

dsmos: Starting...

Jan 6 05:26L01 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow [32]: LoginWindow Application Started

Jan 6 05:26L01 localhost /user/sbin/ocspd [63]: starting

Jan 6 05:26L01 localhost mDNS Responder mDNS Responder -164 (Nov 4 2007 13:23:04)[28]: Starting

display: family specific matching fails

NVinject: Probing.

NVinject: Setting NVPM=<data not shown>

NVinject: Setting @0, device_type=display

NVinject: Setting NVCAP=<data not shown>

NVinject: Setting @0, compatible=NVDA,NVMac

NVinject: Setting model = Graphics by NVIDIA

NVinject: Setting @0,name=NVDA,Display-B

NVinject: Setting device-type=NVDA,Parent

NVinject: Setting name = display

NVinject: Setting rom-revision=NVinject 0.2.1

NVinject: Setting @0,name=NVDA, Display-A

NVinject: Setting @0, compatible=NVDA,NVMac

NVinject: Setting @1, device_type=display

 

Here is what happens with -x:

 

ACPI_SMC_CtrlLoop :: initCPUCtrlLoop-pmCPUControl (PMIOCSETPSTATABLE) returned Ox45ad780

display: family specific matching fails

display: family specific matching fails

NVinject: Probing.

NVinject: Setting NVPM=<data not shown>

NVinject: Setting @0, device_type=display

NVinject: Setting NVCAP=<data not shown>

NVinject: Setting @0, compatible=NVDA,NVMac

NVinject: Setting model = Graphics by NVIDIA

NVinject: Setting @0,name=NVDA,Display-B

NVinject: Setting device-type=NVDA,Parent

NVinject: Setting name = display

NVinject: Setting rom-revision=NVinject 0.2.1

NVinject: Setting @0,name=NVDA, Display-A

NVinject: Setting @0, compatible=NVDA,NVMac

NVinject: Setting @1, device_type=display

dsmos: Initializing...

dsmos: Hook and decryption contexts set!

dsmos: Starting...

Jan 6 05:26L01 localhost fsevents d[33]: eventlogs in /.fseventsd out of sync with volume. destroying old logs. (1797 30 1886)

display: family specific matching fails

Matching service count = 1

display: family specific matching fails

NVinject: Probing.

NVinject: Setting NVPM=<data not shown>

NVinject: Setting @0, device_type=display

NVinject: Setting NVCAP=<data not shown>

NVinject: Setting @0, compatible=NVDA,NVMac

NVinject: Setting model = Graphics by NVIDIA

NVinject: Setting @0,name=NVDA,Display-B

NVinject: Setting device-type=NVDA,Parent

NVinject: Setting name = display

NVinject: Setting rom-revision=NVinject 0.2.1

NVinject: Setting @0,name=NVDA, Display-A

NVinject: Setting @0, compatible=NVDA,NVMac

NVinject: Setting @1, device_type=display

Jan 6 05:26L01 localhost fsevents d[33]: log dir: /.fseventsd getting new uuid 63DE9B49-7567-4577-B7F3-DB0A25B49972

Apple RTL8169Ethernet: Ethernet address 00:1d:7e:a5:d9:29

Jan 6 05:26L01 localhost DirectoryService [40]: Launched version 5.0 (v514)

Jan 6 05:26L01 localhost WARNING - dsTouch: file was asked to be opened </Library/Preferences/DirectoryService/.DSIsRunning> (File exists)

Jan 6 05:26L01 localhost mDNS Responder mDNS Responder -164 (Nov 4 2007 13:23:04)[28]: Starting

Jan 6 05:26L01 localhost /usr/sbin/ocspd[58]: starting

 

Is it possible to do anything to recover, or should I re-install?

Link to comment
Share on other sites

I did it!

 

I got hardware acceleration/QE/rotation working (along with the correct interface type and RAM amount) and, despite the kernel panics from installing NVinject 0.2.1, by editing the following after booting with -s mode:

 

GeForce.kext, NVDANV40Hal.kext, and NVDAResman.kext

 

I replaced the ids with 0x00c010de and 0x0000ffff

 

The first part, 0x00c0 is the device id. Mine is a 6800GS. The second part, 10de, is the vendor id. I used 10de which is Nvidia, not eVGA, but it works. The 0x0000ffff was in one of the id areas, and I didn't know what to substitute, so I used it.

 

In NVDANV40Hal.kext and NVDAResman.kext, there are multiple device/vendor ids listed. You only need the one for your card. I deleted the rest. Tutorials I've found don't mention this twist.

 

I ended up repairing permissions from the Kalyway 10.5.1 boot disk via Disk Utility. There were problems with each of the three kexts, even though I did chmod and chown like I was supposed to. I could have probably repaired permissions with -s mode, but the GUI via the boot CD worked fine.

 

Now the only thing I need to do is get sleep/reboot/shutdown working reliably.

 

Tip: Even though NVinject 0.2.1 isn't supposed to need device ids to be manually added, they need to be added manually for this card to those kexts.

Link to comment
Share on other sites

  • 1 month later...
  • 10 months later...
 Share

×
×
  • Create New...