borisbadenov ATI X1000-series Solution

JaS · May 30, 2006

Anybody tried yet ?

I tried and get a kernel panic when booting after adding the second device id to the x1000 kext,the reason for this you can see in ioreg (I'll just include the displays from it

| | | +-o display@0 <class IOPCIDevice, registered, matched, active, busy 0, retain count 12>

| | | | | {

| | | | | "ATY,Connected" = <002207073f170000e50006a50000000000000000000000000000000000000000>

| | | | | "IODeviceMemory" = (({"address"=18446744073172680704,"length"=268435456}),({"address"=18446744073702146048,"length"=65536}),{"offset"=43008,"parent"=({"address"=0,"length"=65536}),"length"$

| | | | | "AAPL,ndrv-interrupt-set" = "IONDRVInterruptSet is not serializable"

| | | | | "my_box" = <0005000000040000200000000000000000000000>

| | | | | "Power Management protected data" = "{ theNumberOfPowerStates = 3, version 1, power state 0 = { capabilityFlags 00000000, outputPowerCharacter 00000000, inputPowerRequirement 00000000, sta$

| | | | | "saved-config" = <24048200170700e50000000000000000302a000598063000700000042a0401000300000400050

030000000000000000000000000000000000000000000000000000000001000000c8000000c80000

00100000000$

| | | | | "reg" = <00000100>

| | | | | "IOInterruptSpecifiers" = (<1000000007000000>)

| | | | | "my_Id1" = <0048d002ffb72ffd656d69537a6c7552>

| | | | | "AAPL,maps" = ("_IOMemoryMap is not serializable","_IOMemoryMap is not serializable","_IOMemoryMap is not serializable")

| | | | | "MVAD" = <24048200170700e50000000000000000302a000598063000700000042a0401000300000400050

03000000000000000000000000000000000000000000000000>

| | | | | "assigned-addresses" = <1000014300000000000000e00000000000000010180001030000000000008fff0000000000000

00200001010000000000a800000000000000010000>

| | | | | "driver-ist" = <c0e5b30201000000c0e5b30202000000c0e5b30203000000>

| | | | | "compatible" = <"pci174b,850","pci1002,71c2","pciclass,030000"> <-- the first device id

| | | | | "AAPL,address" = <0070ba2f00b09d2f00a80000>

| | | | | "Power Management private data" = "{ this object = 02d04800, interested driver = 02d04800, driverDesire = 0, deviceDesire = 0, ourDesiredPowerState = 2, previousRequest = 2 }"

| | | | | "AAPL,RegEntryID" = <0048d002ffb72ffd656d69537a6c7552>

| | | | | "CRT2,EDID" = <00ffffffffffff004293a506753a0100330e010368221b962a6e06a1544c9926194f54bfef000

010101010101018180000000000000302a009851002a4030701300510e1100001ec31e0020410020

010601300510e1$

| | | +-o display@0,1 <class IOPCIDevice, registered, matched, active, busy 0, retain count 11>

| | | | {

| | | | "AAPL,maps" = ("_IOMemoryMap is not serializable")

| | | | "built-in" = <00>

| | | | "IODeviceMemory" = (({"address"=18446744073702080512,"length"=65536}))

| | | | "AAPL,ndrv-interrupt-set" = "IONDRVInterruptSet is not serializable"

| | | | "device-id" = <e2710000>

| | | | "IOChildIndex" = 2

| | | | "name" = "display"

| | | | "AAPL,RegEntryID" = <0049d002ffb62ffd656d69537a6c7552>

| | | | "AAPL,ndrv-dev" = Yes

| | | | "AAPL,gray-value" = <c38c6400>

| | | | "IOName" = "display"

| | | | "vendor-id" = <02100000>

| | | | "revision-id" = <00000000>

| | | | "driver-ist" = <e0f6ad0201000000e0f6ad0202000000e0f6ad0203000000>

| | | | "subsystem-vendor-id" = <4b170000>

| | | | "Power Management private data" = "{ this object = 02d04900, interested driver = 02d04900, driverDesire = 0, deviceDesire = 0, ourDesiredPowerState = 2, previousRequest = 2 }"

| | | | "Power Management protected data" = "{ theNumberOfPowerStates = 3, version 1, power state 0 = { capabilityFlags 00000000, outputPowerCharacter 00000000, inputPowerRequirement 00000000, sta$

| | | | "mach_o" = <"1.0f198">

| | | | "AAPL,address" = <00d00740>

| | | | "class-code" = <00800300>

| | | | "compatible" = <"pci174b,851","pci1002,71e2","pciclass,038000"> <---- the second video output display device id is already detected and matched

| | | | "AAPL,iokit-ndrv" = <601d8d2f>

| | | | "subsystem-id" = <51080000>

| | | | "assigned-addresses" = <100101030000000000008eff0000000000000100>

| | | | "reg" = <00010100>

| | | | "AAPL,gray-page" = <01000000>

As you can see the second video output display device id is already detected and matched.Thats why if you add it to the x1000 kext it causes a panic on boot

aberracus · May 30, 2006

In terminal type:

kextstat

and paste here or PM me the output of that.

Kexstat says:

Index Refs Address Size Wired Name (Version) <Linked Against>

1 1 0x0 0x0 0x0 com.apple.kernel (8.4.1)

2 16 0x0 0x0 0x0 com.apple.kpi.bsd (8.4.1)

3 21 0x0 0x0 0x0 com.apple.kpi.iokit (8.4.1)

4 22 0x0 0x0 0x0 com.apple.kpi.libkern (8.4.1)

5 21 0x0 0x0 0x0 com.apple.kpi.mach (8.4.1)

6 14 0x0 0x0 0x0 com.apple.kpi.unsupported (8.4.1)

7 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (8.4.1)

8 1 0x0 0x0 0x0 com.apple.driver.AppleNMI (8.4.1)

9 1 0x0 0x0 0x0 com.apple.iokit.IOSystemManagementFamily (8.4.1)

10 1 0x0 0x0 0x0 com.apple.iokit.ApplePlatformFamily (8.4.1)

11 36 0x0 0x0 0x0 com.apple.kernel.6.0 (7.9.9)

12 1 0x0 0x0 0x0 com.apple.kernel.bsd (7.9.9)

13 1 0x0 0x0 0x0 com.apple.kernel.iokit (7.9.9)

14 1 0x0 0x0 0x0 com.apple.kernel.libkern (7.9.9)

15 1 0x0 0x0 0x0 com.apple.kernel.mach (7.9.9)

16 12 0x34b02000 0x9000 0x8000 com.apple.iokit.IOPCIFamily (1.8) <11>

17 6 0x34b0e000 0x4000 0x3000 com.apple.iokit.IOACPIFamily (1.2.0) <11>

18 2 0x34b49000 0x37000 0x36000 com.apple.driver.AppleACPIPlatform (1.0.3) <17 16 11>

19 0 0x34bd0000 0x5000 0x4000 com.apple.BootCache (25.1) <6 5 4 3 2>

20 3 0x34c93000 0x32000 0x31000 com.apple.iokit.IOHIDFamily (1.4.7) <6 5 4 3 2>

21 0 0x34cfa000 0x4000 0x3000 com.apple.driver.AppleAPIC (1.1.0) <11>

22 0 0x34d0d000 0x4000 0x3000 com.apple.driver.AppleSMBIOS (1.0.6) <11>

23 0 0x34df8000 0x4000 0x3000 com.apple.driver.AppleACPIButtons (1.0.3) <20 18 17 6 5 4 3 2>

24 0 0x3a809000 0x5000 0x4000 com.apple.driver.AppleRTC (1.0.2) <17 5 4 3 2>

27 7 0x3aa33000 0x16000 0x15000 com.apple.iokit.IOStorageFamily (1.5) <6 5 4 3 2>

29 0 0x3aaa2000 0x3000 0x2000 com.apple.driver.AppleACPIPCI (1.0.3) <18 17 16 11>

30 3 0x3aaee000 0xd000 0xc000 com.apple.iokit.IOATAFamily (1.6.0f2) <11>

31 0 0x3ab02000 0x7000 0x6000 com.apple.driver.AppleIntelPIIXATA (1.7) <30 16 11>

32 11 0x3ab70000 0x19000 0x18000 com.apple.iokit.IOUSBFamily (2.4.6) <11>

33 0 0x3ab9c000 0xc000 0xb000 com.apple.driver.AppleUSBUHCI (2.4.6) <32 16 11>

34 3 0x3ad0b000 0x30000 0x2f000 com.apple.iokit.IOFireWireFamily (2.1.7) <11>

35 0 0x3ad70000 0x16000 0x15000 com.apple.driver.AppleFWOHCI (2.6.1) <34 16 6 5 4 3>

37 0 0x3aeb6000 0x10000 0xf000 com.apple.driver.AppleUSBEHCI (2.4.5) <32 16 11>

38 0 0x3af01000 0x9000 0x8000 com.apple.driver.AppleUSBHub (2.4.6) <32 11>

39 5 0x3af5c000 0x15000 0x14000 com.apple.iokit.IOSCSIArchitectureModelFamily (1.4.7) <11>

40 0 0x3af7d000 0x4000 0x3000 com.apple.iokit.IOATAPIProtocolTransport (1.4.3) <39 30 11>

41 0 0x3b04f000 0xa000 0x9000 com.apple.iokit.IOATABlockStorage (1.4.3) <30 27 11>

42 2 0x3b1b5000 0x8000 0x7000 com.apple.iokit.IOCDStorageFamily (1.4) <27 5 4 3>

43 1 0x3b1e5000 0x13000 0x12000 com.apple.iokit.IOSCSIBlockCommandsDevice (1.4.7) <39 27 11>

44 1 0x3b212000 0x5000 0x4000 com.apple.iokit.IODVDStorageFamily (1.4) <42 27 5 4 3>

45 0 0x3b245000 0x12000 0x11000 com.apple.iokit.IOSCSIMultimediaCommandsDevice (1.4.7) <44 43 42 39 27 11>

47 0 0x3b348000 0x6000 0x5000 com.apple.iokit.SCSITaskUserClient (1.4.7) <39 27 11>

48 0 0x3b379000 0x3000 0x2000 com.apple.driver.AppleUSBComposite (2.4.5) <32 11>

49 0 0x3b491000 0x9000 0x8000 com.apple.iokit.IOUSBMassStorageClass (1.4.2) <39 32 27 11>

51 2 0x3b679000 0x34000 0x33000 com.apple.iokit.IOBluetoothFamily (1.7.3f4) <11>

52 1 0x3b6b2000 0x5000 0x4000 com.apple.driver.AppleUSBBluetoothHCIController (1.7.3f4) <51 32 11>

54 1 0x3b827000 0x5000 0x4000 com.apple.iokit.IOUSBHIDDriver (2.4.5) <32 20 11>

55 0 0x3b84e000 0x2000 0x1000 com.apple.driver.AppleUSBMergeNub (2.4.5) <32 11>

56 0 0x44a9e000 0x3000 0x2000 com.apple.driver.BroadcomUSBBluetoothHCIController (1.7.3f4) <52 51 11>

57 0 0x3aaa5000 0x9000 0x8000 com.apple.iokit.IOUSBUserClient (2.4.5) <32 11>

58 3 0x3aab6000 0x1b000 0x1a000 com.apple.iokit.IOGraphicsFamily (1.4.3) <16 6 5 4 3>

59 2 0x3ab09000 0xf000 0xe000 com.apple.iokit.IONDRVSupport (1.4.3) <58 16 6 5 4 3>

60 0 0x3ab18000 0x32000 0x31000 com.apple.kext.ATINDRV (4.2.6) <59 58 11>

61 0 0x3aba8000 0xf000 0xe000 com.apple.iokit.IOFireWireAVC (1.9.5) <34 11>

62 0 0x3abb7000 0x14000 0x13000 at.obdev.KUC (1.2.59) <6 5 4 3 2>

65 2 0x3aad1000 0x7000 0x6000 com.apple.iokit.IOHDAFamily (1.1.0a20) <5 4 3 2>

66 0 0x3abd6000 0x9000 0x8000 com.apple.driver.AppleHDAController (1.1.0a20) <65 16 5 4 3 2>

67 2 0x3abe3000 0x9000 0x8000 com.apple.iokit.IOSerialFamily (9.0.0d30) <6 5 4 3 2>

68 1 0x3abec000 0x8000 0x7000 com.apple.driver.Apple16X50Serial (1.7) <67 16 11>

69 0 0x3aa5a000 0x2000 0x1000 com.apple.driver.Apple16X50ACPI (1.7) <68 17 11>

70 2 0x3abf4000 0x16000 0x15000 com.apple.iokit.IONetworkingFamily (1.5.0) <6 5 4 3 2>

71 0 0x3ac0a000 0xb000 0xa000 com.apple.driver.AppleIntel8254XEthernet (1.1.2) <70 16 5 4 3 2>

72 0 0x3ad86000 0x48000 0x47000 com.apple.ATIRadeonX1000 (4.2.6) <59 58 16 11>

73 0 0x3ac39000 0x2000 0x1000 info.yuriev.driver.FrontRowPass (1.0.0d1) <54 32 20 11>

74 1 0x3af0a000 0x17000 0x16000 com.apple.iokit.IOAudioFamily (1.5.6b1) <32 11>

75 0 0x3aec8000 0x12000 0x11000 com.apple.driver.AppleHDA (1.1.0a20) <74 65 5 4 3 2>

76 0 0x3af91000 0x8000 0x7000 com.apple.iokit.IOFireWireIP (1.4.2) <70 34 6 5 4 3 2>

77 1 0x3b063000 0xa000 0x9000 com.apple.driver.AppleSMC (1.0.1d9) <17 5 4 3>

78 0 0x3af43000 0x3000 0x2000 com.apple.Dont_Steal_Mac_OS_X (6.0.0) <77 6 4 3 2>

79 0 0x3b897000 0xb000 0xa000 com.apple.filesystems.msdosfs (1.4.5) <6 5 4 2>

80 0 0x55a5d000 0x9000 0x8000 com.apple.iokit.IOBluetoothSerialManager (1.7.3f4) <67 11>

and Cyclonefr, YES my display sleeps normally and can be awaken normaly thats good news.

JAS, i tried that too, and have the same KERNEL PANIC, but i dont knew why, so you are telling us, the second output of our video cards are being detected, but somehow thay are sleep or something, cause when i have two attached displays, (one LCD thru DVI and one CRT thru VGA), the CRT is off after OSX starts, and when i run an OPENGL Full screen game like Quake, the CRT cames alive with the game and the LCD went to sleep.

aberracus · May 30, 2006

yes but did u try to play a game for 10 minutes?
else the monitor sleep isnt supported for me

I repeat it again, it's not a problem if the artifacts bugs can be fixed using ATINDRV 10.4.5, i dont think the latest version as lots of improvments

sorry for the second post, but this is important i think, when a video card generates artifacts AFTER some time of USE or HIGH power use (like a game) that means only one thing, TEMPERATURE, and the cause is normally associated with overclocking, but TEMPERATURE is the problem.

So, maybe Cyclone u should try with you computer cover off and some high powered FAN blwoing to your video card, just to check if the artifacts appear later. If thats right we wil have proven that the ATINDRV 10.4.6 overclocks or at least consider higher clocks vor the ATI X1600 card, such overclocking could be accepted in some cards without problem because they are XT cards or because they simply have good chips that could eb overclockable.

what do you think?

Tush · May 30, 2006

sorry for the second post, but this is important i think, when a video card generates artifacts AFTER some time of USE or HIGH power use (like a game) that means only one thing, TEMPERATURE, and the cause is normally associated with overclocking, but TEMPERATURE is the problem.

So, maybe Cyclone u should try with you computer cover off and some high powered FAN blwoing to your video card, just to check if the artifacts appear later. If thats right we wil have proven that the ATINDRV 10.4.6 overclocks or at least consider higher clocks vor the ATI X1600 card, such overclocking could be accepted in some cards without problem because they are XT cards or because they simply have good chips that could eb overclockable.

what do you think?

Quite an interesting idea, that might be the problem.But what is also intersting, after I tried the 10.4.6 ATINDRV.kext working with all the other 10.4.5 kexts, I got lower xbench result.(from 95 to 65) Even the GUI seemed to be fast just like before.

cyclonefr · May 30, 2006

Quite an interesting idea, that might be the problem.But what is also intersting, after I tried the 10.4.6 ATINDRV.kext working with all the other 10.4.5 kexts, I got lower xbench result.(from 95 to 65) Even the GUI seemed to be fast just like before.

yeah tush, can u try putting 10.4.6 kexts + OPENGL.FK and play a game with ur Sapphire PRO and see if u have artifacts? btw you have AGP or PCI-E?

Abeeracuss with all my respect, i dont think it's overclocking problem (this bug appear in 10sec under WoW and if i quit OSX hasnt any artifacts)...maybe just new registries (in 10.4.6 ATINDRV.kext) that seek for other files, cause if Tush hasnt any artifacts on his PRO that cannot explain the whole thing...

mine is AGP but ive seen other guys having PCIE X1600 and getting artifacts with ATINDRV 10.4.6....this whole thing is so weird!

btw no1 found how to activate the monitor sleep ?

cardinal · May 30, 2006

I've also suggested that 10.4.6 driver might be clocking the memory or gpu (maybe they did that to address some of the MBP overheat or whine problems?), and that's why many Pro cards are failing. I think this idea was originally brought up as early as page 10 or so of this thread by someone else. As far as I've noticed, all XT users have no artifact/crash problems with 10.4.6. DVI issue is another one, and I think it depends on implementation of individual cards. Possibly it is related to device id, as there may be something else hardcoded other then what we can modify in info.plist.

Anyway, I'll check when I get home how my kexts compare to aberracus and try to make sure they are the same version. If I still get artifacts, I will try to exchange my card for the same one that aberracus has and see if problems magically go away.

bablefish · May 30, 2006

After spending hours testing, retesting, reinstalling 10.4.5, 10.4.4, 10.4.6 extensions, and reading all pages of this thread extensions I finally got it to work on my Asus 1600XT silent.

The main problems I had was that with 10.4.5 extensions I got artifacts and the computer would freeze after some time, with 10.4.6 I would only get a black screen with a cursor and (sometimes) some kind of red field..

I came across a post about the opengl framework and tested to replace the OpenGL framework with the 10.4.6 supplied. Voila ... now it works (1920x1200 on a Dell 2405).

It turned out that since I had earlier installed the GMA900 support for 10.4.6 the 10.4.5 OpenGL framework was installed (that is incompatible with the 10.4.6 drivers).

I don't know if this is the solution to anybody else problem, but I hope that this experience will help someone struggling to get their card working.

acababune · May 30, 2006

anybody try OpenMark

here the address

http://www.giofx.net/osx/openmark.htm

cyclonefr · May 30, 2006

Anyway, I'll check when I get home how my kexts compare to aberracus and try to make sure they are the same version. If I still get artifacts, I will try to exchange my card for the same one that aberracus has and see if problems magically go away.

great idea!! im sure it will work with the XT

bablefish · May 30, 2006

Tested OpenMark, and after the benchmark is finished it says

ATI Radeon X1600 OpenGL Engine

1920x1200x32

Score 11520

Don't know if this is good or bad :-)

cardinal · May 30, 2006

I guess this is old news to most of you, but I just found out that X1600 on MacBook Pro is underclocked, to below regular Pro speed. I haven't been able to find out anything about iMac clock. Alas, it would be interesting if someone could compare graphics benchmarks with a Jas 10.4.6 install (on a x1600Pro that doesn't crash with 10.4.6, such as Sapphire card) and then also by replacing ATINDRV from 10.4.5. If hypothesis that 10.4.6 is overclocking Pro cards, this test should give us an idea if that is a reasonable guess. It might not tell us a lot if tested on XT cards, because they are already running at higher speed anyway.

aberracus · May 30, 2006

I sugest overclocking as a possiblity for artifacts, because is the MOST obvious one, AND and overclocked card could raise to Artifacts generating temp in just a few seconds in a gem and minutes in another one, depending on the exigencies. I know about overclocking and video cards, i have done it a lot.

In situations when some brands or models of cards work without artifacts and some others didn't, it happens because there are brands or models with chips that are underclocked (as the Saphires are known) or clocked to retail specs or advertised specs but the chips aren't really at their maximum capacity. So we can't rule out PRO cards and XT cards as compatible or incompatible with ATNDRV 10.4.6

Tried Openmark... ok it works, i cant measure against anything... i wold love to have in fo about the real clock or speed of our video chipsets.

The idea is to ruleout overclocking, maybe its something happening maybe not, but we must rule it out scientifically. So we start to comprenhend it instead of calling it just Weird. with al due respect Cyclonefr.

Ok about Sleep, mi monitor is sleeping and awakening perfectly now

hanschien · May 30, 2006

JaS 10.4.6 w/ 10.4.5 ATINDRV.kext; ASUS X1600 PRO 512MB

I removed: AppleHWSensor.kext, AppleEFIRuntime.kext, AppleSMC.kext and AppleSMCLMU.kext

Index Refs Address Size Wired Name (Version) <Linked Against>

1 1 0x0 0x0 0x0 com.apple.kernel (8.4.1)

2 13 0x0 0x0 0x0 com.apple.kpi.bsd (8.4.1)

3 15 0x0 0x0 0x0 com.apple.kpi.iokit (8.4.1)

4 17 0x0 0x0 0x0 com.apple.kpi.libkern (8.4.1)

5 16 0x0 0x0 0x0 com.apple.kpi.mach (8.4.1)

6 9 0x0 0x0 0x0 com.apple.kpi.unsupported (8.4.1)

7 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (8.4.1)

8 1 0x0 0x0 0x0 com.apple.driver.AppleNMI (8.4.1)

9 1 0x0 0x0 0x0 com.apple.iokit.IOSystemManagementFamily (8.4.1)

10 1 0x0 0x0 0x0 com.apple.iokit.ApplePlatformFamily (8.4.1)

11 28 0x0 0x0 0x0 com.apple.kernel.6.0 (7.9.9)

12 1 0x0 0x0 0x0 com.apple.kernel.bsd (7.9.9)

13 1 0x0 0x0 0x0 com.apple.kernel.iokit (7.9.9)

14 1 0x0 0x0 0x0 com.apple.kernel.libkern (7.9.9)

15 1 0x0 0x0 0x0 com.apple.kernel.mach (7.9.9)

16 10 0x46832000 0xf000 0xe000 com.apple.iokit.IOPCIFamily (2.0) <11>

17 4 0x46844000 0x4000 0x3000 com.apple.iokit.IOACPIFamily (1.2.0) <11>

18 2 0x4687f000 0x37000 0x36000 com.apple.driver.AppleACPIPlatform (1.0.3) <17 16 11>

19 0 0x468cd000 0x5000 0x4000 com.apple.BootCache (25.1) <6 5 4 3 2>

20 2 0x4692e000 0x32000 0x31000 com.apple.iokit.IOHIDFamily (1.4.7) <6 5 4 3 2>

21 0 0x4698a000 0x4000 0x3000 com.apple.driver.AppleAPIC (1.1.0) <11>

22 0 0x46993000 0x4000 0x3000 com.apple.driver.AppleSMBIOS (1.0.6) <11>

23 0 0x4c474000 0x4000 0x3000 com.apple.driver.AppleACPIButtons (1.0.3) <20 18 17 6 5 4 3 2>

25 0 0x4c548000 0x5000 0x4000 com.apple.driver.AppleRTC (1.0.2) <17 5 4 3 2>

26 0 0x4c621000 0x3000 0x2000 com.apple.driver.AppleACPIPCI (1.0.3) <18 17 16 11>

27 8 0x4c69f000 0x16000 0x15000 com.apple.iokit.IOStorageFamily (1.5) <6 5 4 3 2>

29 8 0x4c6da000 0x1a000 0x19000 com.apple.iokit.IOUSBFamily (2.4.0) <11>

30 0 0x4c70e000 0xd000 0xc000 com.apple.driver.AppleUSBUHCI (2.4.0) <29 16 11>

31 1 0x4c750000 0x16000 0x15000 com.apple.iokit.IONetworkingFamily (1.5.0) <6 5 4 3 2>

33 0 0x4c8d4000 0x8000 0x7000 com.apple.driver.AppleIntel8255x (1.4) <31 16 5 4 3 2>

34 3 0x4c8f8000 0xd000 0xc000 com.apple.iokit.IOATAFamily (1.6.0f2) <11>

35 0 0x4c90c000 0x7000 0x6000 com.apple.driver.AppleIntelPIIXATA (1.7) <34 16 11>

36 0 0x4c94c000 0x12000 0x11000 com.apple.driver.AppleUSBEHCI (2.4.0) <29 16 11>

38 0 0x4c9aa000 0xb000 0xa000 com.apple.driver.AppleUSBHub (2.4.0) <29 11>

39 6 0x4c9d5000 0x15000 0x14000 com.apple.iokit.IOSCSIArchitectureModelFamily (1.4.7) <11>

40 0 0x4c9f6000 0x4000 0x3000 com.apple.iokit.IOATAPIProtocolTransport (1.4.3) <39 34 11>

41 0 0x4cab5000 0xa000 0x9000 com.apple.iokit.IOATABlockStorage (1.4.3) <34 27 11>

42 2 0x4cba5000 0x8000 0x7000 com.apple.iokit.IOCDStorageFamily (1.4) <27 5 4 3>

43 2 0x4cbd5000 0x13000 0x12000 com.apple.iokit.IOSCSIBlockCommandsDevice (1.4.7) <39 27 11>

44 1 0x4cc04000 0x5000 0x4000 com.apple.iokit.IODVDStorageFamily (1.4) <42 27 5 4 3>

45 0 0x4cc35000 0x12000 0x11000 com.apple.iokit.IOSCSIMultimediaCommandsDevice (1.4.7) <44 43 42 39 27 11>

46 0 0x4cd02000 0x6000 0x5000 com.apple.iokit.SCSITaskUserClient (1.4.7) <39 27 11>

47 0 0x4cd27000 0x3000 0x2000 com.apple.driver.AppleUSBComposite (2.4.0) <29 11>

48 0 0x4ce29000 0x9000 0x8000 com.apple.iokit.IOUSBMassStorageClass (1.4.2) <39 29 27 11>

50 0 0x4d015000 0x3000 0x2000 com.apple.driver.iPodSBCDriver (1.1.2) <43 39 11>

51 0 0x4d0ff000 0x5000 0x4000 com.apple.iokit.IOUSBHIDDriver (2.4.0) <29 20 11>

52 0 0x53c2d000 0x9000 0x8000 com.apple.iokit.IOUSBUserClient (2.4.0) <29 11>

53 3 0x53c40000 0x1b000 0x1a000 com.apple.iokit.IOGraphicsFamily (1.4.3) <16 6 5 4 3>

54 2 0x53c5b000 0xf000 0xe000 com.apple.iokit.IONDRVSupport (1.4.3) <53 16 6 5 4 3>

55 0 0x53c6a000 0x32000 0x31000 com.apple.kext.ATINDRV (4.2.4) <54 53 11>

57 2 0x53ca9000 0x7000 0x6000 com.apple.iokit.IOHDAFamily (1.1.0a20) <5 4 3 2>

58 0 0x53cb0000 0x9000 0x8000 com.apple.driver.AppleHDAController (1.1.0a20) <57 16 5 4 3 2>

59 0 0x53cbd000 0x48000 0x47000 com.apple.ATIRadeonX1000 (4.2.6) <54 53 16 11>

60 1 0x53d60000 0x17000 0x16000 com.apple.iokit.IOAudioFamily (1.5.6b1) <29 11>

61 0 0x53d77000 0x12000 0x11000 com.apple.driver.AppleHDA (1.1.0a20) <60 57 5 4 3 2>

62 0 0x53ed1000 0x8000 0x7000 com.apple.filesystems.ntfs (1.2) <4 2>

63 0 0x53eb2000 0xb000 0xa000 com.apple.filesystems.msdosfs (1.4.5) <6 5 4 2>

64 0 0x4d194000 0x5000 0x4000 com.apple.driver.XsanFilter (2.7.0) <27 11>

aberracus, are you running JaS 10.4.6? I noticed your com.apple.iokit.IOPCIFamily is 1.8 while mine is 2.0. Maybe that is why you can use ATINDRV 4.2.6.

curlyboy · May 30, 2006

Well i just plugged my HP pavillion mx70 standard run of the mill monitor into the DVI socket with supplied adapter and power option works absolutely perfect ,,, but not so good when in vga , also i noticed when plugged into vga the profiler / graphics show MX70 but when in DVI it shos just VGA and also when in vga socket when screen sleeps nothing but the mouse sleeps wierd huh the screen just stays there

hanschien · May 31, 2006

Same situation for me, but my monitor sleeps and resumes on DVI-VGA, but only sleeps on VGA.

curlyboy · May 31, 2006

Yeah exact same , but i dont mind bcos on the dvi with adapter it work perfect id say

cardinal · May 31, 2006

OK, here is summary of differences. I deleted all lines where all 3 of us had same drivers loaded:

cardinal x1600pro broken

16 10 0x34b7c000 0x9000 0x8000 com.apple.iokit.IOPCIFamily (1.8) <11>

30 7 0x3ab8b000 0x19000 0x18000 com.apple.iokit.IOUSBFamily (2.4.6) <11>

31 0 0x3abb7000 0xc000 0xb000 com.apple.driver.AppleUSBUHCI (2.4.6) <30 16 11>

34 0 0x3ac78000 0x10000 0xf000 com.apple.driver.AppleUSBEHCI (2.4.5) <30 16 11>

36 0 0x3ad68000 0x9000 0x8000 com.apple.driver.AppleUSBHub (2.4.6) <30 11>

45 0 0x3b1a4000 0x3000 0x2000 com.apple.driver.AppleUSBComposite (2.4.5) <30 11>

48 0 0x3b4ec000 0x5000 0x4000 com.apple.iokit.IOUSBHIDDriver (2.4.5) <30 20 11>

49 0 0x34ca5000 0x9000 0x8000 com.apple.iokit.IOUSBUserClient (2.4.5) <30 11>

52 0 0x3ab24000 0x32000 0x31000 com.apple.kext.ATINDRV (4.2.4) <51 50 11>

54 2 0x34d83000 0x5000 0x4000 com.apple.iokit.IOHDAudioFamily (1.0.0d1) <5 4 3 2>

55 0 0x3a754000 0x6000 0x5000 com.apple.driver.AppleAzaliaController (1.0.0d1) <54 16 5 4 3 2>

57 0 0x3af9e000 0x39000 0x38000 com.apple.iokit.AppleYukon (1.0.0d30) <56 16 11 2>

60 0 0x3abe5000 0xc000 0xb000 com.apple.driver.AppleAzaliaAudio (1.0.0d1) <59 54 5 4 3 2>

61 1 0x3ad08000 0xa000 0x9000 com.apple.driver.AppleSMC (1.0.1d9) <17 5 4 3>

62 0 0x3a7ce000 0x3000 0x2000 com.apple.Dont_Steal_Mac_OS_X (6.0.0) <61 6 4 3 2>

64 0 0x34d93000 0x5000 0x4000 com.apple.driver.XsanFilter (2.7.0) <28 11>

65 0 0x3e513000 0x2c000 0x2b000 com.apple.AppleDiskImageController (113.3) <28 6 5 4 3 2>

hanschien x1600pro broken