Jump to content

Tyrone Shoe

Members
  • Content count

    45
  • Joined

  • Last visited

About Tyrone Shoe

  • Rank
    InsanelyMac Protégé
  1. Yup, paticularly if you are on a laptop, you'll be hosed without it... no trackpad or keybd. You wont even be able to type if you boot with -s
  2. Good laptop for osx86?

    Well my T60p works darn well. Most of the components are shared between the T60 and the X60 which is a recent model ultrallight from Lenovo. I know several people have gotten them working
  3. Cheapest install EVER

    Sorta like an AppleTV
  4. Post Leopard Graphics Update Kext Tweaking

    Thanks to some dedicated folks in IRC, I now have my video working 100%. Even my external VGA works when I boot with a display attached. Ironically, it even fixed my sleep for me :-). Many thanks to everyone who helped
  5. Porblem with hardware install

    Just in case you haven't done it already, pull all your drives out of the system. also pull out any add-in cards (except your video). If you have multiple memory chips installed, remove them and only install enough to POST. Remove any extra fans other than your CPU fan. You shouldn't need anything more than RAM and a video card to at least get a POST screen. If at that point, you still don't get any video up on your screen, it probably is a dead mobo. If you do POST successfully, start adding things back in until it hoses up again. I assume you didn't get a crappy PSU for your case? I've seen some of the real bargain bin supplies brown out with very little extra hardware connected.
  6. RAID... which board?

    I'd experiment with the Silicon Image cards as suggested by the user before me. They're great as you can get them for under $25 in most cases. I know monoprice.com has a lot of them for sale, both PCI and PCI-E
  7. Post Leopard Graphics Update Kext Tweaking

    I found the extra stuff I needed to change in the LGU ATIRadeonX1000.kext to get it to recognize my card and not cause a kernel panic. However, I have new weirdness: 1) Without any ATIinject, It recognizes all my screen resolutions however, the screen is corrupted. It is stretched wide (like scanlines) and the color is inverted. 2) If I put in my ATIinject.kext (which worked fine prior to the update), I get a QE/CI display which looks fine but is locked at my boot resolution and has mouse tearing. It almost acts the way it would with the VESA drive. I know my ATIinject is good b/c if I boot off my 10.5.1 backup, It works perfectly. I can't figure out what would have changed to cause it to no longer have any available resolutions. It would be great if I could figure out a way to un-corrupt my display and not even have ot use an injector but that sounds unlikely. Any ideas how to get my ATIinject back to a working state? <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleExecutable</key> <string>ATIinject</string> <key>CFBundleIdentifier</key> <string>com.max.ATIinject</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>ATIinject</string> <key>CFBundlePackageType</key> <string>KEXT</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>1.0.0d1</string> <key>IOKitPersonalities</key> <dict> <key>ATIinject</key> <dict> <key>CFBundleIdentifier</key> <string>com.max.ATIinject</string> <key>IOClass</key> <string>com_max_ATIinject</string> <key>IOMatchCategory</key> <string>IOFramebuffer</string> <key>IONameMatch</key> <string>display</string> <key>IOPCIMatch</key> <string>0x00001002&0x0000ffff</string> <key>IOProbeScore</key> <integer>0</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>entriesToAdd</key> <dict> <key>@0,AAPL,boot-display</key> <integer>1</integer> <key>@0,ATY,EFIDisplay</key> <string>LVDS</string> <key>@0,compatible</key> <string>ATY,Wormy</string> <key>@0,connector-type</key> <integer>2</integer> <key>@0,device_type</key> <string>display</string> <key>@0,display-connect-flags</key> <integer>0</integer> <key>@0,display-dither-support</key> <integer>0</integer> <key>@0,display-dual-link</key> <integer>2</integer> <key>@0,display-link-component-bits</key> <integer>6</integer> <key>@0,display-link-type</key> <integer>0</integer> <key>@0,inverter-current</key> <integer>0</integer> <key>@0,name</key> <string>ATY,Wormy</string> <key>AAPL,backlight-control</key> <integer>1</integer> <key>AAPL00,Coherency</key> <integer>2</integer> <key>AAPL00,DualLink</key> <integer>1</integer> <key>AAPL00,LinkType</key> <integer>0</integer> <key>ATY,Copyright</key> <string>Copyright ATI Technologies Inc. 2005</string> <key>ATY,DeviceID</key> <data> 1HEAAA== </data> <key>ATY,EFIVersion</key> <string>01.00.068</string> <key>ATY,FrameBufferOffset</key> <integer>512</integer> <key>ATY,VRAM,MemSize</key> <integer>512</integer> <key>ATY,VendorID</key> <integer>4098</integer> <key>LVDS,EDID</key> <data> AP///////wAwriJAAAAAAAAPAQOAHRV46i0Fl1dRiicj UFQhCACBgAEBAQEBAQEBAQEBAQEBMCp4IFEaEEAwcBMA HtYQAAAZJSN4IFEaEEAwcBMAHtYQAAAZAAAADwCQQzKQ QygPAQBMo1A0AAAA/gBMVE4xNDFQNC1MMDIKABk= </data> <key>device-id</key> <data> cdQQAg== </data> <key>device_type</key> <string>ATY,WormyParent</string> <key>model</key> <string>ATi Mobility Radeon x1700</string> <key>name</key> <string>ATY,WormyParent</string> </dict> </dict> </dict> <key>OSBundleLibraries</key> <dict> <key>com.apple.iokit.IOPCIFamily</key> <string>1.0.0b1</string> <key>com.apple.kernel.iokit</key> <string>6.0</string> </dict> <key>OSBundleRequired</key> <string>Safe Boot</string> </dict> </plist>
  8. Post Leopard Graphics Update Kext Tweaking

    Maybe I'm missing something but I'm still not seeing anything on the site applicable to my issues. Even if I try all the Natit stuff or EFI strings on there, I still don't have a working RadeonX1000 driver to use with it.
  9. I started with Kalyway 10.5.1 but I used Netkas' upgrade method. It worked flawlessly for me. It sounds like the Kalyway 10.5.2 updater is more trouble than it's worth.
  10. leopard graphics update, safe?

    I'm having exactly the same problems with my X1700 based FireGL card. Hex editing the model IDs into the kext only gets me kernel panics after the update.
  11. Post Leopard Graphics Update Kext Tweaking

    Thanks but I'm not using a Radeon HD card. Netkas' site won't be very helpful.
  12. Every waiting for root device error I've ever had related to drive configuration. the most recent time, it was because I had my DVD drive set to Slave. I moved it to a different IDE channel and made it master, poof.
  13. Hey, so prior to the Leopard Graphics Update, I had a pretty stable graphics setup on my laptop. I followed the normal methods of modding files: inserting EDID into ATIInject, Adding device ID to ATIRadeonX1000's Info.plist. I also modded the ATIRadeonX1000.kext/Contents/MacOS/ATIRadeonX1000 with 0xED. This all worked with the preexisting Kexts. However, doing the same with the post-update kexts gets me nothing but kernel panics. In fact, if the only thing I do just add my card to Info.plist, I still get a kernel panic. Using the old kexts gets me black menus, etc. I've been searching google for a couple of hours today with no luck. Is there a known change to the way Apple's kexts detect graphics chipsets? If so, any suggestions on what I can try to get past my current problems?
  14. ATI Mobility FireGL T2 - working - but how to activate QE?

    my old laptop had the same gfx card. Under tiger, it was a snap to get it working. Try using callisto or natit drivers. If you spend the time searching these forums, you'll find an answer
  15. Via SATA Support

    You could try running your SATA controller in compatibility mode in the meantime. You won't get the same performance level but at least you might be able to avoid FUBAR'ing your whole system.
×