Quote:
Since 1073 installed ... 1 - upgraded to 1074. 2 - put the kernel "bronzovkAnVoodoo_0_9_26" 3 - I applied the patch "amd_insn_patcher_src.zip" So now I'm not even allowed to copy a file. And Disk Utility does not recognize the device any more. It really is very odd. What did I do wrong? :'( ps: but the applications were running smoothly both 32bit and 64bit:) |
Quote:
here are my BIOS settings for Gigabyte Motherboard GA-990-UD3 FXA Intelligent Tweaker (MIT) ------> leave everything on default Standard CMOS Features: here must be the Lion HDD in the first place, if not then change the SATA cable. The HDD's Windows on the second position, otherwise error message when you boot ----> AppleUSBOHCI ... still waiting for root device.l Advanced BIOS Features: AMD C1E [Disabled]!!! if Enabled then .... wait for root device! Virtualization [Enabled] AMD 8 Col & Q. [Auto] Hard Disk Boot Priority under the LION HDD must be positioned in the first place Integrated Peripherals On-chip SATA Controller [Enabled] On Chip SATA Type [Native IDE] On-chip SATA 3.0 [Enabled] F_USB30 Controller [Enabled] SATA3 Controller [Enabled] SATA3 Ctrl Mode [AHCI] ON Board 1394 Function [Disabled] Enabled if it is error message: .... waiting for root device ------> Leave everything on default then it should work: flag boot:-legacy -force64 UserKernelCache=No -v -f or -legacy -force64 UserKernelCache=No -v -f arch = i386_x64 Good luck! |
Quote:
take this >>>> http://osx86.co/f36/legacy-kernel-10...post55947.html amd_ins_patcher_src.zip ( IOHIDFamily nintervalcheck.kext.zip --> S/L/E ) and use the How-To by AkimoA (root86.org) AMD binary patching! Unzip the file'm amd_insn_patcher and copy it to /usr/bin then open the Terminal Then you give the command: code: sudo-s amd_insn_patcher / usr / lib / libSystem.B.dylib / usr / lib / libSystem.B.dylib.patched mv / usr / lib / libSystem.B.dylib.patched / usr / lib / libSystem.B.dylib amd_insn_patcher / usr / lib / dyld / usr / lib / dyld.patched mv / usr / lib / dyld.patched / usr / lib / dyld amd_insn_patcher mv amd_insn_patcher / System / Library / QuickTime / QuickTimeComponents.component / Contents / MacOS / QuickTime Components / System / Library / QuickTime / QuickTimeComponents.component / Contents / MacOS / QuickTimeComponents.patched mv / System / Library / QuickTime / QuickTimeComponents.component / Contents / MacOS / QuickTimeComponents.patched / System / Library / QuickTime / QuickTimeComponents.component / Contents / MacOS / QuickTime Components amd_insn_patcher / System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar / System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar.patched mv / System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar.patched / System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar Then the repair permissions and re-enter the following in the terminal. code: sudo update_dyld_shared_cache |
@frisco2,
I really appreciate your help! I checked again my BIOS settings and everything which are the same with my motherboard are as you wrote. |
Quote:
|
Here is my PC specs:
AMD Phenom II 965 Black Edition MSI 790FX-GD70 8GB Super Talent DDR3 1600MHz 2TB Western Digital Caviar Green SATA II 350GB Samsung SATA II ATI Radeon HD 5450 ASUS Xonar D2X Sony/Nec Optiarc DVD-RW SATA II. A few lines before the "still waiting for root device", it writes something like that: "couldn't alloc IOUSBMassStorageClass". Maybe it's this kext? |
@erineos
Normaly the system stocks on this point if the used harddisk is not on sata1 port. |
Quote:
|
I will install today ComboUbdate 10.7.5, then I report
|
Good afternoon,
My Snow Leopard HDD (where i would like to install Lion) is in the SATA 1 port. From a search in the net i found that probably it's the SB750 southbridge that causing the problem and it can't see any SATA ports. I found that an IOATAfamily.kext for SB700/750 for Lion, it may resolve the "still waiting for root device". What do you think? Is this kext available or we can specially make it? |