-
Posts
143 -
Joined
-
Last visited
Reputation
17 GoodProfile Information
-
Gender
Male
-
Location
Serbia
Contact Methods
-
Skype
lostandstupid
Recent Profile Visitors
7,331 profile views
-
Hi the connatic. Cheers for the reply and the helpfulness,don't you worry man,Gainward 9600 GT GS up and running full on Was just posting a success if anybody has some old similar hardware,not to give up,it can work,a bit sketchy process but it pays off heh.Will post it there,thanx for the reminder. Igor
-
Success story after 4 days of painstaking work.Just to get QE/CI up and running and im all good. Old AMD Athlon X2 64 4200+ with a cheap-ass 30 euro ASRock piece of crud motherboard boasting the nForce 630 chipset. First tinkered with VMWare Workstation and 10.6.8 snow leopard,made a virtual hard disk,restored Basesystem.dmg etc etc all the usual stuff.Made a .sparsebundle image,booted 10.5.7 Leopard off a DVD,restored it to a HDD partition,did the terminal work,pulled all neccecary stuff from a USB flash drive.The restore process for some odd reason didnt copy the /var and /Volumes partition so i had fun with that for a few hours but finnaly managed to copy those from another restored image on a USB flash drive.Booted the HDD partition,installed,again back to Leopard and the terminal,fixed it up,and et voala,booted in. 4 days of work total. Btw kernel is Bronzovka 10.7.4 arch=i386, 64 bit userland functioning. What can i say,it was a challenge.Now off to setup meself some Mountain Lion goodness on a proper Intel i5 3570K
-
Fairly old post,glad it's still helping people Cheers
-
Bug: launchctl.c:2408 problem while booting iATKOS L2 USB
.picodev replied to cowboy36289's topic in OSx86 10.7 (Lion)
Boot with -v GraphicsEnabler=No it will boot normal. -
Getting an ElliotForceLegacy.kext kernal panic
.picodev replied to sags95's topic in New Users Lounge
Weird thing with that hang though,no problem,good you sorted it out -
CPU Shutdown on AMD/VMWare Player 4.0.3
.picodev replied to ashrid's topic in OSx86 10.6 (Snow Leopard)
You have to use a legacy kernel for AMD,you can't use the default vanilla kernel as it's not an Intel processor. -
Getting an ElliotForceLegacy.kext kernal panic
.picodev replied to sags95's topic in New Users Lounge
Where is it stuck at exactly?You're saying that after you enter the rm command,it hangs?You can't type? -
Getting an ElliotForceLegacy.kext kernal panic
.picodev replied to sags95's topic in New Users Lounge
It should happen as soon as you press enter. -
+1 Not gonna happen
-
Getting an ElliotForceLegacy.kext kernal panic
.picodev replied to sags95's topic in New Users Lounge
Heh,it's with two "t" , so Elliott That's why i told you to use Tab and auto complete. -
Getting an ElliotForceLegacy.kext kernal panic
.picodev replied to sags95's topic in New Users Lounge
You have to use the breakout character for the spaces.. \ , so it would be "cd /Volumes/Snow\ Leopard/System/Library/Extensions" One more quick tip,when you know the names of folders,example just type Sno and press Tab,it will autocomplete the name for you. -
Getting an ElliotForceLegacy.kext kernal panic
.picodev replied to sags95's topic in New Users Lounge
Install media > Utilities > Terminal > cd /Volumes/your_partition_name_here_/System/Library/Extensions rm -r ElliottForceLegacyRTC.kext cd .. touch /Extensions reboot -
If you download nawcoms legacy kernel from his blog,and use the .pkg, it patches everything for you.You need to use arch=i386 -force64 bootflags and everything should work out fine,even the 16 gigs of RAM. Info: Mac OS had PAE (Physical Adress Extension) long time so even when booted 32bit,it could use more than 4 gigs of RAM. When you boot with the flags above,only the kernel will be 32 bit, kexts which can will be 64 bit and also the Apps will run in 64 or 32,whatever their arch is.Only in a few cases,some users reported no problems on AMD with 64 bit arch.Back to the issue.. Andy's kernel has fresh code and even nawcom suggests using it but bare in mind,it boots with a custom compiled dyld blob and some apps have problems with it (i for instance,had problems with Dropbox),so if you want to use his kernel,you better off boot with std_dyld=Yes. Hope this all helps
-
Glad it worked out for you.