Jump to content

X1900XT fully working with Dual-Screen, DVI out (Natit)


  • This topic is locked This topic is locked
34 replies to this topic

#21
MiR

MiR

    InsanelyMac Protégé

  • Retired Developers
  • 18 posts

This was my first ever "try"
Will do, meanwhile since I had previously installed the Boris-style patch for x1x00, I went back and replaced my ATI* kexts and OpenGL.framework with original 10.4.8 versions. This time I get a display, mirrored on both monitors.

But looking at boot messages, Natit.kext ran 6 times during boot and here is a summary of the errors:

4.80.46.0display: family specific matching fails
display: family specific matching failsdisplay: family specific matching fails

Natit: Starting.
Natit: Setting model=Unknown nVidia

Natit: Starting.
Natit: Setting model=Unknown nVidia
display: family specific matching fails

Natit: Starting.
Natit: Setting @0,device_type=displaydisplay: family specific matching fails

Natit: Starting.
Natit: Setting model=Unknown nVidia

Natit: Setting model=Unknown nVidia
display: family specific matching fails

Natit: Starting.
Natit: Setting model=Unknown nVidia

ATY,Wormy: Not usable
ATY,Wormy: Not usable


Perhaps you have more than one device that matches the ATI-Signature (1002) and because of this Natit gets called more often than necessary.

On my System Nantit is called twice (Once for the Primary Device ID of the Graphics card, the second time it is called for the Secondary ID (this is forthe 2nd Display))

Please edit

<key>IOPCIMatch</key>
<string>0x00001002&amp;0x0000ffff</string>

to:

<key>IOPCIMatch</key>
<string>0xXXXX1002</string>

where XXXX is the Device ID found for the Graphics Card in 'About this Mac'

In my case the Device-ID is 7249 ; my Entry is now:

<key>IOPCIMatch</key>
<string>0x72491002</string>

Now you have to

rm /System/Library/Extensions.*

and reboot.

Now Natit only matches once and will only be called once.

MiR
MiR

#22
munky

munky

    Agent of Evolution

  • Retired
  • 2,900 posts
  • Location:The Land of Hairy-Arsed Highlanders
Here's what worked for me:

- Installed JaS 10.4.6 w/ Intel SSE3 patch
- Installed JaS 10.4.7 Update
- Installed Official Apple 10.4.8 Combo
- Replaced mach_kernel and AppleSMBIOS.kext with those from Mifki/Vitaliy's release
- Booted up
- Downloaded Natit.kext from here: http://forum.insanel...showtopic=32427
- Downloaded OP's Info.plist and replaced
- Repaired permissions/ownership etc, removed mkext and kextcache
- Rebooted to working system.


EDIT: I just realised i'm probably not using the dual-display Natit. I dont have a second monitor to test with, so its unimportant to me.

i can ssh to my reawakened hackintosh. can anyone suggest a terminal command which would force a reposting of the video?

btw i can VNC to the machine - it connects but shows a black window... curious... anyone any ideas how i can force it to repost video? (i dont have teh 'repost video on s3 resume' option in bios...)

#23
Rammjet

Rammjet

    InsanelyMac V.I.P.

  • Gurus
  • 5,302 posts
  • Gender:Male

Perhaps you have more than one device that matches the ATI-Signature (1002) and because of this Natit gets called more often than necessary.

On my System Nantit is called twice (Once for the Primary Device ID of the Graphics card, the second time it is called for the Secondary ID (this is forthe 2nd Display))

I have only one ATI device

Please edit

<key>IOPCIMatch</key>
<string>0x00001002&0x0000ffff</string>

to:

<key>IOPCIMatch</key>
<string>0xXXXX1002</string>

where XXXX is the Device ID found for the Graphics Card in 'About this Mac'

The generic IOPCIMatch string of "0x00001002&0x0000ffff" worked just fine on my previous Boris-style patched system. It loaded only once and unfortunately recognized only one output of my ATI card.

Now Natit only matches once and will only be called once.

Won't hard coding it back to a single device id force it to only recognize one of the ATI card outputs and limit me to only one monitor - defeating the whole purpose of this exercise? If I wanted that, I would reload all of my previous kexts and frameworks from my working Boris-style patched system.

#24
MiR

MiR

    InsanelyMac Protégé

  • Retired Developers
  • 18 posts

Won't hard coding it back to a single device id force it to only recognize one of the ATI card outputs and limit me to only one monitor - defeating the whole purpose of this exercise? If I wanted that, I would reload all of my previous kexts and frameworks from my working Boris-style patched system.


Nope. Natit always does the same on every invocation. Reducing the number of invocations does not hurt, it makes the logging output easier to read.

Please remember, Natit is not a display driver, it only fill's the registry with missing entries that are needed for the real graphics driver to load.

The 2nd display is handeled internaly in the original driver. I once added the second Device-ID of my graphics card to an extension, the result was a wonderfull crash :D

MiR

#25
Rammjet

Rammjet

    InsanelyMac V.I.P.

  • Gurus
  • 5,302 posts
  • Gender:Male

Nope. Natit always does the same on every invocation. Reducing the number of invocations does not hurt, it makes the logging output easier to read.

Please remember, Natit is not a display driver, it only fill's the registry with missing entries that are needed for the real graphics driver to load.

The 2nd display is handeled internaly in the original driver.

Interesting. 4 hours ago you said:

(Important, make sure that you replace the original entry for IOPCIMatch with the following:
<key>IOPCIMatch</key>
<string>0x00001002&0x0000ffff</string>
otherwise Natit will not load the Keys)

Anyway, I hard-coded IOPCIMatch to "0x71c01002" and Natit.kext loaded 4 times with the same errors as before.


The essence of my problem is that when I look at the ioreg output from single-user mode, I don't find very many variables to set/tweak and I'm wondering where you found some of the ones that you did set.

For instance, here is the ioreg output for my secondary port (dev id 71e0) on the ATI card:

| |   |   +-o display@0,1  <class IOPCIDevice, registered, matched, active, busy 0, retain count 7>
	| |   |   |   {
	| |   |   |	 "IODeviceMemory" = (({"address"=18446744073703129088,"length"=65536}))
	| |   |   |	 "device-id" = <e0710000>
	| |   |   |	 "IOChildIndex" = 1
	| |   |   |	 "name" = "display"
	| |   |   |	 "IOName" = "display"
	| |   |   |	 "vendor-id" = <02100000>
	| |   |   |	 "revision-id" = <00000000>
	| |   |   |	 "IOPCIResourced" = Yes
	| |   |   |	 "subsystem-vendor-id" = <4b170000>
	| |   |   |	 "Power Management private data" =  (edited for space considerations)
	| |   |   |	 "Power Management protected data" = (edited for space considerations)
	| |   |   |	 "IOPCIExpressLinkStatus" = 4353
	| |   |   |	 "IOPCIExpressLinkCapabilities" = 3329
	| |   |   |	 "class-code" = <00800300>
	| |   |   |	 "compatible" = <"pci174b,881","pci1002,71e0","pciclass,038000">
	| |   |   |	 "assigned-addresses" = <100106820000000000009eff0000000000000100>
	| |   |   |	 "subsystem-id" = <81080000>
	| |   |   |	 "reg" = <0001060000000000000000000000000000000000100106020000000000000000000000000000
100>
	| |   |   |   }

I find nothing similar to the following <key>'s that you set nor the following <string>:

<key>device_type</key>
<string>ATY,AlopiasParent</string>  <-- would expect ATY,WormyParent for mine

<key>ATY,FrameBufferOffset</key>
<key>ATY,IOSpaceOffset</key>
<key>ATY,RegisterSpaceOffset</key>
<key>@1,device_type</key>
<key>@1,display-connect-flags</key>



#26
MiR

MiR

    InsanelyMac Protégé

  • Retired Developers
  • 18 posts

The essence of my problem is that when I look at the ioreg output from single-user mode, I don't find very many variables to set/tweak and I'm wondering where you found some of the ones that you did set.

I find nothing similar to the following <key>'s that you set nor the following <string>:

<key>device_type</key>
<string>ATY,AlopiasParent</string>  <-- would expect ATY,WormyParent for mine

<key>ATY,FrameBufferOffset</key>
<key>ATY,IOSpaceOffset</key>
<key>ATY,RegisterSpaceOffset</key>
<key>@1,device_type</key>
<key>@1,display-connect-flags</key>


Those values are from ioreg output of a real mac pro. This is the posting:

http://forum.insanel...showtopic=32645

I've added more and more keys from the ioreg output until I got it working.

As you seem to have a X1600-Card perhaps you will also find some tricks in the following post:

http://forum.insanel...showtopic=32554


Did this message ATY,Wormy not useable disappear in your log?

This could perhaps mean that the driver for your card could not be loaded. I also get a mirrored screen when the 'real' driver does not load because the VESA-based driver seems to activate mirroring when it gets invoked.

A wild guess from me: Perhaps your Device-ID is unknown to the ATY,Wormy driver and you will either have to add your device ID to the Info.plist of the driver or you will have to patch the driver's binary.


MiR

#27
romey-rome

romey-rome

    SooperDooperPooper

  • Members
  • PipPipPip
  • 147 posts
Which card(s) are you all using?

I was about to pick up a 1600, but I'll swing for a 1900 if you guys have that going.

Thanks

#28
natedogg

natedogg

    InsanelyMac Protégé

  • Members
  • Pip
  • 24 posts
Hey Munky,

I'm hoping you can help me out, or anyone for that matter. Can you run me through what you did step by step. I've never owned a mac in my life so my mac hacking skills are next to none. I have a 512mb Sapphire x1900 xtx and mainly I'm just looking to get the thing working. The boris method doesn't work for me with the new 10.4.8 kernel and I really want the new kernel cause it is 100 times faster then the old one in 10.4.6.

If you could help me get it going I would really appriciate it, and to have DVI working would be even better, I'm not worried about dual displays as I don't need it at the moment.


Thanks everyone in advance for the help and for being patient with a windows converted to hackintosh fan.

#29
MiR

MiR

    InsanelyMac Protégé

  • Retired Developers
  • 18 posts

Hey Munky,

I'm hoping you can help me out, or anyone for that matter. Can you run me through what you did step by step. I've never owned a mac in my life so my mac hacking skills are next to none. I have a 512mb Sapphire x1900 xtx and mainly I'm just looking to get the thing working. The boris method doesn't work for me with the new 10.4.8 kernel and I really want the new kernel cause it is 100 times faster then the old one in 10.4.6.

If you could help me get it going I would really appriciate it, and to have DVI working would be even better, I'm not worried about dual displays as I don't need it at the moment.
Thanks everyone in advance for the help and for being patient with a windows converted to hackintosh fan.


NeoPheus has offered to create an installer, your best bet would be to wait for the installer to be finished. Your card should run out of the box because it has the same device-id as a x1900xt, the only difference is the timing of GPU and memory.

Here's the URL to NeoPheus site:

http://www.installers.dl.am/

#30
munky

munky

    Agent of Evolution

  • Retired
  • 2,900 posts
  • Location:The Land of Hairy-Arsed Highlanders
or try the instructions i posted here:

http://forum.insanel...;hl=ATY_Alopias

#31
natedogg

natedogg

    InsanelyMac Protégé

  • Members
  • Pip
  • 24 posts

or try the instructions i posted here:

http://forum.insanel...;hl=ATY_Alopias



Is this using Natit? I'd really like to get DVI working if possible so I don't have to switch between DVI and VGA all the time. I tried your instructions, but I have an X1900 XTX do you know which plugin is for the x1900's? I'll give it some trial and error but having DVI would be awesome.

Thanks again

-EDIT- I tried Alopias and Sphyrna all this did was freeze up my machine after initial log in. Any ideas? I get what you are trying to do with your post, I just don't get how you did it any help would be great as NEO hasn't released anything lately and I'd really like to get my mac back up and working, been using vista "shiver"

#32
ooZberg

ooZberg

    InsanelyMac Protégé

  • Members
  • PipPip
  • 51 posts
I have a X1900XTX and it works like a charm right out of the box :D

I just:
1. Installed a clean 10.4.8 with 8.8.1 kernel.
2. Installed Natit.kext (Edited), got from other thread.

Works with dual screen/DVI :)

#33
Kaspers

Kaspers

    Pro

  • Members
  • PipPipPipPipPip
  • 315 posts
  • Gender:Male
  • Location:the Netherlands
Does this trick also work on 10.4.7 ?

#34
casse

casse

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
1) Do "we" know why the x1900xt card works with dual dvi monitors more or less out of the box? I'm guessing it's no coincidence, assuming the Mac Pro mentioned above - from which the info came - was equipped with the x1900xt. Was it?

Also, I'm wondering:

2) Do we have any idea if 512 MB is supported "out of the box" on the x1900xt? It would make sense, since the card Apple offers has 512 MB. Or is it not that simple?

3) If this newly discovered dual display support is dependent on the card having the same device id as the x1900xt, it makes me wonder which other cards share this device id. Is it only the x1900xtx? I'm partly asking because the x1950 pro seems like such sweet price/performance deal.

Thanks for any answers! :thumbsdown_anim:

#35
bottleNeckKiller

bottleNeckKiller

    InsanelyMac Protégé

  • Members
  • PipPip
  • 90 posts
How about widescreen on this card, is that working?

Hope this card has this.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy