Jump to content


  • Content count

  • Joined

  • Last visited

About nuditarian

  • Rank
    InsanelyMac Protégé
  1. nuditarian

    10.5.5 to 10.5.7 on a Dell Precision 690

    I thought maybe it was drivers, I copied the ATA drivers from 10.5.5 and was able to boot. Then I noticed that it just hadn't loaded the ATA drivers because I had hosed permissions on those kexts. With this in mind, and given all the chatter about "Still waiting for root device" being related to ATA jumper settings, I switched my DVD drives from being Cable Select to being set to master and slave, copied the 10.5.7 ATA kexts back, and all is OK. So the moral of the story, if you have ANY PATA/ATA/IDE devices, set them to master/slave instead of cable select.
  2. I decided to update my vanilla 10.5.5 install to 10.5.7, and I'm stuck now with a broken install. Initially, the install failed, so I booted to an external 10.5.2 install and re-ran it from that install. Install completed, but system would not boot(KPanic). I decided to install Chameleon 2.0 rc1 and run the ideneb combo upgrade kit to see if I could get any farther. Install went smoothly, but still no full boot. At this point Chameleon seems to be working, I can attempt to boot the 10.5.7 install. Single user mode works fine, I can see and mount the boot drive, but normal boot with verbose shows "Still waiting for root device" Any tips? Is DSDT patching an absolute requirement for 10.5.7 on all installs? How can I tell if the Extensions in /Extra are being loaded by Chameleon?
  3. nuditarian

    Intel 82540EM Gigabit Random lockup

    I had problems with my Intel Pro/1000 showing cable unplugged, I solved it by populating both 64-bit PCI slots with network cards. Not all cards did the trick, but once I found the right card it works flawlessly. In my case, I have a 64-bit PCI Intel Pro/1000 Server adapter in one slot and a 32-bit PCI Intel Pro/1000 Desktop adapter in the other. I didn't try any other types of PCI cards(SCSI, firewire, etc), so I don't know if it has to be a network card. Weird but true.
  4. nuditarian

    Interesting Shutdown Solution

    The should be in the System or Console log. All logs are visible with Console.App, which is in /Applications/Utilities
  5. I have a Precision 690 working flawlessly, though shutdown fails like so many. OS X goes away, but the system doesn't actually power off. Here's an interesting detail though. The Precision 690 has an intrusion detection switch, that is triggered when the side panel is opened. If I initiate a shutdown then open the case, the system shuts down properly. If I open the case THEN start the shutdown it still fails to shut down. I'll have to try tomorrow to see if any triggering of the switch, closing or opening, allows a clean shutdown.
  6. Refurb Macbook Pro, or find a teacher to do an educational purchase which shaves a few hundred off. Refurbs have same warranty and are elligible for extension with applecare(IIRC)
  7. The last note on this install, and the answer to the original problem of the post, is a weird one. I originally was trying to get 2 cards working, the Intel Pro/1000 MT Server adapter and the Intel Pro/1000 MT Desktop adapter. Originally both were recognized but showed disconnected state regardless of whether a cable was there or not. I have it working with the Leo4All IONetworkingFamily.kext, but . . . only if both cards are installed in 64-bit PCI slots, even though one of them is a 32-bit PCI card. Here's what I tried: Precision 690 has 3 slots, 2 x 64-bit and 1 x 32-bit. I used 3 cards, an older Intel Pro/100 (32-bit), the Pro/1000 Desktop(32-bit) and the Pro/1000 Server(64-bit) Pro/1000 Desktop + Pro/1000 Server, both installed in 64-bit slots works, doesn't matter which one goes in which slot Pro/1000 Desktop + Pro/1000 Server, Pro/1000 Desktop in 32-bit slot - doesn't work Pro/1000 Server + Pro/100, both installed in 64-bit slots - doesn't work Pro/1000 Server + Pro/100, Pro/100 installed in 32-bit slot - doesn't work So the Pro/1000 Server adapter and the Pro/1000 Desktop adapter both appear to require both 64-bit slots to be full, but they can't be filled with just any card. And in the end the Pro/1000 Desktop was flakey(caused many kernel panics), so I left it installed and just deactivated it.
  8. Well, I have everything working! And at the end of the day, I did it with a retail DVD and the only changes necessary were adding dsmos.kext, removing AppleIntelCPUManagement.kext, installing nvinject 4.1 and running AppleHDAPatcher 1.2 with a dump for Sigmatel 9200, and replacing the AppleIntel8254XEthernet.kext in IONetworkingFamily.kext(for my Intel Pro 1000 MT. dsmos.kext and AppleIntel8254XEthernet.kext I used were from Leo4All. I don't think dsmos.kext was any different from what was at the n00b guide. I installed using my Macbook Pro, hooking up this drive as an external drive. I realize this isn't an option for many, but it was the simplest way for me. I was more focused on finding out what the minimal amount of modification from a vanilla retail install. I know this isn't a detailed guide, it's just a rough record of steps. Any commandline commands assume you are in the terminal and have cd'd to the correct directory(/System/Library for extensions.mkext and /System/Library/Extensions for everything else) I didn't include paths because if you are doing this as a parallel install the paths will all be goofy anyway. Steps: Install EFI patch following step 2 of n00b guide (http://forum.insanelymac.com/index.php?showtopic=86167&hl=retail) Install using OSInstall.mpkg(step 3 of n00b guide) Copy dsmos.kext to the extensions folder and remove AppleIntelCPUManagement.kext, run 'sudo chown -R root:wheel dsmos.kext' 'sudo rm -R extensions.mkext' That's all it took to get booted to a base working config. I ran software update and 10.5.2 crashed halfway through, so I had to reapply the update from a different install. After 10.5.2 I had to remove AppleIntelCPUManagement.kext again, otherwise no problems. To get everything else working, install nvinject, run AppleHDAPatcher and copy AppleIntel8254XEthernet.kext into /System/Library/Extensions/IONetworkingFamily.kext/Contents/Plugins/ , run 'sudo chown -R root:wheel IONetworkingFamily.kext' So Dell Precision 690 works(basic) with Retail DVD + EFI v8 + dsmos.kext - AppleIntelCPUManagement.kext, and complete with + nvinject4.1 + AppleHDAPatcher(Sigmatel9200) + IONetworkingFamily.kext(Leo4All) On a side note, I have a Intel Pro 1000 MT Desktop adapter that causes all sorts of trouble, made the system totally unstable. The adapter that is working is the Intel Pro 1000 MT Server adapter. The desktop adapter is a standard PCI card while the Server adapter is a 64-bit PCI card. All in all I have to say installing using OSInstall.mkpg from another install is the easiest way to go. That way you are starting with a clean vanilla retail install and only modify that which is necessary.
  9. Just tried the latest leo4all, using the netkas kernel. Same issue. I noticed that when I run the network utility, it shows a ton of receive errors, even though it shows cable disconnected. Also when I try to set speed and duplex settings manually, OS X doesn't retain the setting. dmesg_ioreg_output.zip
  10. Does anybody know how to verify that all the PCI Bus subsystems are recognized? I'm starting to wonder, since Apple System Profiler never shows any PCI cards present, if OS X isn't really recognizing the PCI bus properly.
  11. nuditarian

    Intel Pro MT 1000 Desktop Help

    Have you tried using a patched kernel to see if it magically works? I'm using vanilla kernel in 10.5 and have tested 10.5.2 as well, both have the same issue. I've tried about 4 different cards, and the all have the same "Cable disconnected" issue. Tried a 3com 3c905-TX, Intel PRO/1000 MT single port and dual port server adapters, and an Intel PRO/1000 MT desktop adapter. All are recognized but say they are disconnected. I'll try and drop in a patched kernel and see if it makes any difference.
  12. I've got a vanilla install + AppleHDAPatcher + NVInject, sound and video are rock solid. On the network side, any card that I can get detected always shows the cable disconnected. I've got link lights, but OS X always shows disconnected. I'm currently focusing on an Intel PRO/1000 MT that is detected, dmesg shows 'AppleIntel8254XEthernet: Ethernet address <correct MAC>' switch has link light, but no luck. I've tried using Chun-nan's patched IOPCIFamily.kext, but this made no difference. My Device string 'PCI\VEN_8086&DEV_1026&SUBSYS_10028086&REV_04\5&292877C9&0&300310' from Windows. Changed the IPCIPrimaryMatch string in /System/Library/Extensions/IONetworkingFamily.kext/Contents/Plugins/AppleIntel8254XEthernet.kext/Contents/Info.plist from '0x10008086&0x0000ffff' to '0x10008086&0x0000ffff 0x10268086' I also tried installing the SmallTree drivers, but that made no difference either. Any ideas? System in question is: Dell Precision 690 Intel 5000X chipset (I think) 2GB Ram nVidia 7800GT PCIExpress Booting to External USB drive Sigmatel 9200 Intel PRO/1000 MT Server Adapter
  13. nuditarian


    You've probably already figured this out, but . . . Press F8 at boot to get Darwin boot options add -s as a boot option to boot into single user mode run the commands to mount your drive ('/sbin/fsck -fy' and then '/sbin/mount -uw /' both of these are displayed when you get into single user mode) then cp -R /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleIntel8254XEthernet.kext /<backuplocation> then rm -R /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleIntel8254XEthernet.kext
  14. nuditarian

    NVIDIA cards in LEO yet?

    Using vanilla kernel and nVInject, I'm using an evga 256MB 7800GT with no vid problems. Previously had a QuadroFX 3450 that would function, but I couldn't get full support(QE Disabled)
  15. I'll take a crack at it . . . BIOS looks to boot from a specific region of the hard drive, startupfiletool sets the HFS+ startup file info. Basically, the BIOS has to release to some sort of bootloader, startupfiletool tells it what that will be. The dd commands copy the actual bootstrap code to the hard drive, in the specific spots where the BIOS will be looking. When you use GRUB, you are doing a completely different boot method, so this isn't necessarily required. The startupfiletool, in my case, is allowing me to do a native boot to a vanilla(unpatched) kernel on a non-EFI based system.