Jump to content
InsanelyMac Forum

SpeBlue

Members
  • Content count

    7
  • Joined

  • Last visited

About SpeBlue

  • Rank
    InsanelyMac Protégé
  1. You're fantastic. Quick look in Sound settings showed 2 "Headphones", one dedicated and one which changed to "Internal Speakers" when headphones were removed. Select the dynamic one and presto, sound is working. Thanks for all the help, and if it's helped improve the guide for others then even better
  2. Renamed your DSDT to DSDT2, screen was fixed Added wen1 DSDT and ran the kextcache command, then repaired disk permissions and now audio is half working! It works when I plug in headphones, but not through the built-in speakers. This isn't a problem for me as I keep the headphones in all the time, but I should point it out in case anyone else gets this problem. Thanks again DoiX, you're a great person.
  3. Forgot to add UseKernelCache=Yes, sound is detected now but still not working. Specs: CPU: i5 2410M GPU: HD 3000 & NVIDIA 525M RAM: 4GB 1333MHz DDR3 LCD: 720p HD WLED, not multi-touch version HDD: 500GB Western Digital WiFi: Intel Centrino Wireless-N 1000 Using the HD Display DSDT, not the Full HD one.
  4. Created my user account manually and added /var/db/.applesetupdone (skips first run screen). If anyone else wants to do it this way, you'll want to mount the drive as always, run the launchctl command on this page, then follow the dscl guide here from commenter Ivan, then before you restart run 'touch /var/db/.applesetupdone' The kexts seem to be installed, and my DSDT is in /Extra, but when I boot the AppleHDA kext fails to load correctly, and then the system stops before loading the GUI, which seems to be the HD3000 problem. If I boot with -f, it boots to the desktop (1024x768) with all other kexts (except AppleHDA) working, and there's a message in the console saying 'SNB Framebuffer did not show up, unload' Would updating to 10.7.2 fix either of these problems? I'm going to try some other methods to get the HD3000 working, I'll report back with results. EDIT: Added the MacBookPro8,1 smbios from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and that's got the HD3000 detected and working with QE/CI, but uh, there's a new problem now, picture attached.
  5. Thanks for the help DoiX. Not sure if this is due to the kexts being installed manually or if this would have happened before, but I still get the "No keyboard connected" screen. However, when I press Alt-Q (mapped to Cmd-Q), it recognises the keys. I think it may just be a problem with the first-run application, in which case, is there any way for me to fill in the details it asks for by single user mode line and bypass the GUI? I know there's a file that gets created to tell OS X that first-run is complete, I'm just wondering if I need to do anything more than just create my user account?
  6. Thanks rndlgna, -x helped get to the first run screen from HD boot, I'll report back to you all when I get an external keyboard to use. As a general question, is there any reason a PS/2 keyboard, connected through a PS/2 to USB converter, wouldn't work? I have an old PS/2 keyboard lying around and it'd be much cheaper for me to just get a converter
  7. Just tried installing Lion today on my L502x, here's the results. Booted and installed from iAtkos L1. No problems other than 1024x768 resolution, but KB/M worked fine. Booting from HD (-v GraphicsEnabler=No busratio=23) stalls after ACPI_SMC_PlatformPlugin::startForReal - waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out Transcript Offline - Buffer Pool Allocate [181000] failed A line above says the DSMOS has arrived, if that helps. When booting from rBoot LE, same flags, it prints out the same lines as above but continues to the first-run GUI. Once there, though, it can't detect the keyboard. Native resolution, 1366x768.
×