Jump to content

VoidStar

Members
  • Content count

    10
  • Joined

  • Last visited

About VoidStar

  • Rank
    InsanelyMac Protégé
  1. I'm seeing this in 10.8.1. I also see something similar when I boot my SSD without another non-SSD drive. Do any of you have an SSD as your boot and another non-SSD connected? See post: http://www.tonymacx8...html#post526829
  2. VoidStar

    LaptopDisplay

    np_ Sorry, it doesn't seem to decompress to the correct directories using stuffit expander. It works if you do it from the command line using "unzip". Strange... Here are some of the files unziped: Radeon9000Mobility_dmesg_totest.txt Radeon9000Mobility_ioreg_totest.txt Radeon9000Mobility_kextstat_totest.txt Radeon9000Mobility_dmesg_ATI8500NoAGPDispMatch.txt Radeon9000Mobility_ioreg_ATI8500NoAGPDispMatch.txt Radeon9000Mobility_kextstat_ATI8500NoAGPDispMatch.txt
  3. VoidStar

    LaptopDisplay

    np_ I installed your totest.zip and here are my results. I hope this helps. I'm at a loss I would love to get QE/CI working. Anything else you can recommend based on these values? For each test I recorded ioreg, kextstat, and dmesg... Radeon9000Mobility_SingleUserMode.zip Single user mode (-s) no totest Radeon9000Mobility_totest.zip Just the contents totest (no ATI Drivers) - Full boot without graphics (sh /etc/rc) Radeon9000Mobility_totestNatit.zip The contents of totest with Natit - Full boot without graphics (sh /etc/rc) Radeon9000Mobility_totestAGP.zip The contents of totest with AGPGart 2.1 - Full boot without graphics (sh /etc/rc) Radeon9000Mobility_ATI8500.zip totest + ATI8500 drivers + AGPGart Radeon9000Mobility_ATI8500Natit.zip totest + ATI8500 drivers + Natit + AGPGart Radeon9000Mobility_ATI8500NoAGP.zip totest + ATI8500 drivers + Natit - AGPGart Radeon9000Mobility_ATI8500NoAGPDispMatch.zip Added my EDID to DisplayVendorID-756e6b6e/DisplayProductID-0. Can change resolution Radeon9000Mobility_ResChangable.zip Added Callisto 6. Can change resolution This is from lspci under Linux for my graphics card: 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 02) (prog-if 00 [VGA]) Subsystem: IBM: Unknown device 0531 Flags: bus master, stepping, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 11 Memory at e0000000 (32-bit, prefetchable) I/O ports at 3000 Memory at c0100000 (32-bit, non-prefetchable) Expansion ROM at <unassigned> [disabled] Capabilities: [58] AGP version 2.0 Capabilities: [50] Power Management version 2 0000:01:00.0 0300: 1002:4c66 (rev 02) Subsystem: 1014:0531 Flags: bus master, stepping, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 11 Memory at e0000000 (32-bit, prefetchable) I/O ports at 3000 Memory at c0100000 (32-bit, non-prefetchable) Expansion ROM at <unassigned> [disabled] Capabilities: [58] AGP version 2.0 Capabilities: [50] Power Management version 2 PS: While looking around I discovered /System/Library/MonitorPanels. If you rename the Display.monitorPanel you shift around options is the Display settings. There are some other panels under AppleDisplay.monitorPanels that look interesting. "find /System/Library/MonitorPanels -type f -perm 755" PS: Also odd is that Darwin boot prompt says I have 31MB not 32MB. Do you recommend the 10.4.8 ATI drivers? ATINDRV.kext changed alot. Thanks! Radeon9000Mobility_ATI8500.zip Radeon9000Mobility_ATI8500Natit.zip Radeon9000Mobility_ATI8500NoAGP.zip Radeon9000Mobility_ATI8500NoAGPDispMatch.zip Radeon9000Mobility_ResChangable.zip Radeon9000Mobility_SingleUserMode.zip Radeon9000Mobility_totest.zip Radeon9000Mobility_totestAGP.zip Radeon9000Mobility_totestNatit.zip
  4. VoidStar

    LaptopDisplay

    Thank you _np for you work, I have a Radeon 9000 Mobility in my Thinkpad T40. I've been at a loss and finally this thread is starting to shed light on the issue. I can't see an entry for EDID so I loaded Phoenix EDID Designer 1.3 In windows and got this: Its called a IBM254D Registry Key : DISPLAY\IBM254D\5&279fdc78&0&00000110&01&00 Monitor Name : 1400x1050 Manufacture Week : 0 / 2004 ManufacturerID : 19748 (0x4D24) ProductID : 9549 (0x254D) Serial Number (Numeric) : 0 (0x00000000) EDID BYTES: 0x 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F ------------------------------------------------ 00 | 00 FF FF FF FF FF FF 00 24 4D 4D 25 00 00 00 00 10 | 00 0E 01 03 80 1D 15 78 EE EE 91 A3 54 4C 99 26 20 | 0F 50 54 21 08 00 81 80 90 40 01 01 01 01 01 01 30 | 01 01 01 01 01 01 30 2A 78 20 51 1A 10 40 30 70 40 | 13 00 1E D6 10 00 00 18 00 00 00 FC 00 54 68 69 50 | 6E 6B 50 61 64 20 4C 43 44 20 00 00 00 FC 00 31 60 | 34 30 30 78 31 30 35 30 0A 20 20 20 00 00 00 00 70 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 B8 Another thing that confuses me is that the display is listed under "VID@0" in ioreg (this doesn't seem normal). One thing worth mentioning is after poking around the ioreg output I noticed that my EDID is actually in there. But it is embedded in a lot of other data in the "ACPI Tables" key under the AppleACPIPlatformExpert node. In fact I detected two copies of it with this between them: 0845444c321145100b0001. I'll download your latest zip file and give you feedback. PS: Should I disable AGPGart.kext? Some more information from a rather confused post of mine: http://forum.insanelymac.com/index.php?sho...c=38408&hl= Thank you!!!
  5. My install of 8f1111 is not matching these devices to extensions: 8086:24c3 (rev 01) SMBus: Intel Corp. 82801DB/DBM (ICH4) SMBus Controller (rev 01) 8086:24c5 (rev 01) Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97 Audio Controller (rev 01) 8086:3340 (rev 03) Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03) Does anyone have a guess? Thanks
  6. Because this extension is not intel. Try this: file /System/Library/Extensions/AppleAirPort2.kext/Contents/MacOS/AppleAirPort2 Rosetta will not work on this... :-(
  7. I'm not sure of that driver but I just looked at AppleAirPort2 and found a bunch of device IDs just like the ATIs: Starting around 0x000169f0: 91 3d 00 00 90 5c 00 00 38 21 00 50 80 01 00 08 bb 81 ff f0 7c 08 03 a6 4e 80 00 20 3d 80 00 00 61 8c 00 00 7d 89 03 a6 4e 80 04 20 2f 83 14 e4 40 9e 00 4c 2f 84 43 01 41 9e 00 4c 2f 84 43 07 41 9e 00 44 2f 84 43 20 41 9e 00 3c 2f 84 43 25 41 9e 00 34 2f 84 43 03 41 9e 00 2c 2f 84 43 21 41 9e 00 24 2f 84 43 24 41 9e 00 1c 2f 84 43 18 41 9e 00 14 2f 84 43 19 41 9e 00 0c 38 60 00 00 4e 80 00 20 38 60 00 01 4e 80 00 20 7c 08 02 a6 93 e1 ff fc 7c 7f 1b 78 90 01 00 08 94 21 ff b0 80 03 00 08 2f 80 00 00 41 9e 00 34 80 03 11 48 2f 80 00 00 40 be 00 20 38 00 00 01 80 9f 19 d4 Guessing at the first byte in each group: Devices start on the 4th byte in an 8 byte item array: Re-aligned: 4c 2f 84 43 01 41 9e 00 4c 2f 84 43 07 41 9e 00 44 2f 84 43 20 41 9e 00 3c 2f 84 43 25 41 9e 00 34 2f 84 43 03 41 9e 00 2c 2f 84 43 21 41 9e 00 24 2f 84 43 24 41 9e 00 1c 2f 84 43 18 41 9e 00 14 2f 84 43 19 41 9e 00 Hence, this driver really supports these devices: 4301 4307 4320 (in Info.plist) 4325 (in Info.plist) 4303 4321 4324 (in Info.plist) 4318 (in Info.plist) 4319 If I'm right, this means that the driver supports more devices then listed in the plist file. Get a hexeditor and look around! Remember to search by hex not string! This has to lead to something!
  8. While snooping around with a hexeditor I found that the device ids normally found in an ATI driver's plist file are also located in the binary file in the MacOS directory. From /System/Library/Extensions/ATIRadeon8500.kext/Contents/MacOS/ATIRadeon8500: I not sure of the exact starting point of the data but it seems like each device is in a data structure that is 12 bytes long. There seems to be an additional 4 bytes after the first, fifth, and eighth devices. Perhaps this describes characteristics of the devices that follow? I think the start of each group begins 3 bytes before the start of the device id and ends on a null. All data seems to end with a null (00). There are nine devices listed and one is listed twice. The data begins (I'm guessing the starting point) at address 0x0001A387. The first device is three bytes in and is 0x514C. You may ask, So what? Well it means that it might not matter what you put in the Info.plist file! The bytes around those ids may tell the driver how to configure the card. Hence, playing with these numbers may help discover something. Perhaps some of those values identify ids specific to mac ATI cards. First thing would be to try and identify those values. Could simply be bit flags... I would guess this is true of all ATI drivers or even other kinds of drivers! Wifi etc.. ??? I just don't have the time to experiment with this so have fun! Don't bother PMing me, this is all I know. On a side note: The binary file in IOGraphicsFamily.kext contains a string called IOFBRefreshRate/IOFBWidth/IOFBHeight. If this can be set in a plist file then we may be able to control the resolution and refresh for people that get the ATI drivers loaded. Just an idea... If this works out someone should start another topic. Good luck to anyone that has the time... Please keep us informed...
  9. Just passing on some information that I've descovered while trying to get an ATI card working. Maybe this can help spark some new ideas... Since PC monitors are not mac monitors they need a special plist file to support them. Without this the resolution and refresh rates are fixed. Monitor configuration files are in /System/Library/Display/Overides The display file your using is probably in a folder in that directory (check the date) (DisplayConfigX will tell you) The program called DisplayConfigX can create a custom display file for any monitor. It adds new refresh rates and resolutions. http://www.3dexpress.de To get an ATI AGP card to be listed as AGP not PCI you need to install this: AppleI386.kext. See post 6 in this thread. I was not able to get AppleI386GenericPlatform.kext to load until I increased the version numbers of the Info.plists file. It then would load via kextload but it will not load at boot time. (Can someone figure this out?) When using the AppleI386.kext extension, the 8500 accelerator tried to load but locked up. It almost seems like the computer is working fine but the screen is just not visible. Like the display settings are way off! This lock up looks very simular to having a messed up display config file which leads me to wonder that the reason why the accelerator is not launching is due to a display file bug, display timing, sync.... Perhaps DisplayConfigX is not writing the correct data or there are some sync values that work better.(Note I didn't buy it so high resolutions were not available.) Results: The ATI drivers wo/acceleration is faster than the vesa drivers but I can't kick the resolution up (May have to buy DisplayConfigX). I was able to make the refresh rate much higher. Don't think people need to modify there bios for this... I urge people to investigate DisplayConfigX and AppleI386.kext + AppleI386GenericPlatform.kext. PS: using 8F1111a Hope this helps...
  10. Got a D915GEV motherboard and it works great and runs cool! When there is no activity it goes to sleep. The drive goes off and the screen fades a bit. It wakes up again after about 5 minutes for some reason... It did this over and over for about 2 hours. During this time it got hotter and hotter until it shut down due to a "thermal event". I powered it up and smoke! The board was toast! Anyone having any issues with the D915GEV and sleeping?
×