Looking for help with 10.5.8 shutdown problem.
Well, first off I want anyone willing to help to know that I have a complete bootable backup drive just for testing OSX updates. So there is no worries that I will crash my main system. That said. On my main drive I have 10.5.7. My…
- Primary Author
- @jeff4760 Published 2009-11-27
- Collection
- Leopard 10.5
- Archival Footprint
- 7,908 historical reads · 2 curated field notes (from 4 dispatches) · 2009-11-27 – 2010-01-25
- Credited Voices (3)
- @jeff4760 (2)@chadp1a@Mykebr
Well, first off I want anyone willing to help to know that I have a complete bootable backup drive just for testing OSX updates. So there is no worries that I will crash my main system.
That said. On my main drive I have 10.5.7. My hardware is:
* a Gigabyte P965-DS3 (rev. 3) mobo. It has ICH8, ALC888, the infamous JMicron controller, and a Marvell Yukon 88E8056 nic.
* Graphics card is ATI 3870 512 MB.
* 6 GB of DDR2 667 RAM
* Kenesis freestyle keyboard made for Mac OSX
* Kensington Expert Mouse with OSX drivers
* Kesington Bluetooth dongle
* a Dynex 4-port USB PCI card
* a Dynex Firewire 800/400 card
* a SiliconImage 3132 2-port RAID card (controlled by the SI drivers from the site)
* I use a Linksys Wireless-N USB wifi adapter for internet right now and it is controlled by the current Ralink drivers.
The hacks I have are:
* Chameleon 2 RC3
* an EFI string in the boot.plist for the TimeMachine fix;
* LegacyAppleAHCIPort (patched with/for JMicron), LegacyAppleYukon2, LegacyIOAHCIBlockStorage, OpenHaltRestart, current VoodooPower, Disabler, AppleDecrypt, and Natit (for gfx).
* I also use an old skippyretard installer for audio that patches AppleHDA (works fine for me) and a JMicron installer to install a newer JMicron kext.
The kexts are all in the main extensions folder. I never had good experiences utilizing the Extra folder. Everything works fantastic including sleep, shutdown and restart. I am a little late in the 10.5.8 update rush because I had some pretty major tragedies go on in my life a few months back. I am back in the the hackintosh world, so to speak, and tested the 10.5.8 update on my backup. Everything but sleep and shutdown worked. I fixed sleep with the pista7 sleepenabler.kext. For the life of me, I cannot figure out why shutdown doesn't work. The system logs out, I hear a click in my tower, the spinning wheel spins, and then the monitors shutdown completely. The fans and LED's on my tower keep right on truckin' though.
Anyone have an idea what is causing this and what I should tinker with?
Thanks,
Jeff
Author Updates & Technical Revisions
Follow-up dispatches by @jeff4760
Well I just found out that its the wifi card I used verbose mode to log in and and then eyeballed it as it shutdown. It ran quickly but I caught a glimpse of it saying something to the extent of "either remove inet6 from en0" and then vanished...I figured "what the hell..." The Ralink adapter has to have it's program constantly running to stay connected; specifically if the wifi SSID is password encrypted. So I rebooted then closed the program, removed the adapter from its base and shutdown. It was a perfect shutdown Now the only question remains is why the adapter did that. Either some brave soul may want to look into it or we have to wait on a fix from Ralink that makes the adapter and its drivers work correctly for 10.5.8.
Synthesized Community Field Notes
2 technical responses curated from 4 original dispatches
@jeff4760Well, first off I want anyone willing to help to know that I have a complete bootable backup drive just for testing OSX updates. So there is no worries that I will crash my main system. That said. On my main drive I have 10.5.7. My hardware is: * a Gigabyte P965-DS3 (rev. 3) mobo. It has ICH8, ALC888, the infamous JMicron controller,…
Are you using GraphicsEnabler=Yes ?
If so that is the problem more than likely with the shutdown issue. I am experiencing the same issue. I can set GraphicsEnabler=No and my laptop will shutdown fine.
Jeff,
I actually have an issue with ralink before also. Actually it was on a Mac System not an OSx86, and the issue was that the encryption I was using was I believe WPA2 and it was causing the error as soon as I changed to WPA or WEP it started working. Have you ever tryed that?
Let me know, and good Luck.