Should be fine... :)

And patcher patched up the apps?
Did you boot verbosely?
If so at least that allready works... ;)

well the apps would not have worked if not rite ???... he did boot verbosly but not recognizable he will hopefully test again and will get a dmesg out if that helps

Even with the increased message buffer it won't be enough to store the 49 option.
It will do for a 48 though...

It doesnt seem to me that this will help ya but here it is with 48

You're right it doesn't.
If you boot with patcher_opts=49 -amd does it show the libraries it loads?
Because I see no reference to any libraries...
EDIT: Could it be that the boot arguments aren't handled correctly? It seems weird -force64 typed didn't work... it seems we have a bug in Chameleon...

here is anything he could get out with 49

so would a bootloader debug clue u in on that possibility ?:-d

Damn... it didn't set the boot args...
Editing /Extra/com.apple.Boot.plist may help but it's still with risk...
Which bootloader are you using?

Shit, instant reboot, but I will try with blank HDD and chameleon usb.

he used r1460 on vanilla
and i tried on amd 1095 and 1457 .....wastez tried cparm boot also on amd

What bootloader should we be using?
 

I'm interested in helping test your kernel. I have three partitions.

Chameleon bootloader
part0 10.6.8 (my fulltime workstation)
part1 10.6.5 (repair)
part2 10.7.0 GM installed from macpro using ccc

Snow Leopard is running on an AM2+ Phenom x4 9650 2.3 ghz. DAO78l Acer Mainboard with nforce 780a chipset. This is a cheap setup and I believe an excellent candidate for testing the kernel with 4gb of ram. Lion of course does not boot (just blackscreen reboot after chameleon bootloader.) I'm running two other systems with same specs without the Lion partition, snow leopard runs on all three very well. One running osx server.

Should I install the Boot beta or will Chameleon work with your new kernel?

In the moment the kernel is not working until now.

You can download a few pages before but as i said it is not working.
I posted it on Page 7, it is compiled with xcode 4.1 but if you want to you can download the source on insanelymac and compile it by yourself.

I found the routines that do code signature checks on the pages + through dyld syscall.
I modified the code slightly so it will verify all code signature kernel checks as valid.
This means we can use stock dyld too...
I also noticed the panic.
It panics on map_text_segment_sys (that's where the trap gets called).
I modified the code slightly for the new syscall format (it shouldn't panic anymore).
I'll post the results soon, please test on that P4... ;)

I tried running in a modded bootcd but it restarts after the message

Starting Darwin x86

Seems like can't boot on i386, even with arch=i386 -force64, extracting i386 part also doesn't work

http://opensource.apple.com/release/mac-os-x-1071/

good luck :)

Garageband crashes on my AMD x2 cpu, any suggestions?

Thanks

Here is part of the crash log:



Process: GarageBand [950]
Path: /Applications/GarageBand.app/Contents/MacOS/GarageBand
Identifier: com.apple.garageband
Version: 6.0.4 (427.84)
Build Info: GarageBand_App-4278400~1
Code Type: X86 (Native)
Parent Process: launchd [102]

Date/Time: 2011-08-26 21:34:08.338 -0400
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 458742 sec
Crashes Since Last Report: 51
Per-App Interval Since Last Report: 72 sec
Per-App Crashes Since Last Report: 6
Anonymous UUID: 21CC8BE4-B7A4-44C8-8A4A-57425D706890

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Add std_dyld=Yes to your boot flags :)

I thought the whole point of the custom dyld kernel was to avoid that? Or am i missing something, lol

Just give me a Shout when u Updated it will recompile it on lion :-d

Installer partition is awaiting :)

Good luck with the kernel :D

I've been following this thread with great interest. I currently run SL quite happily on a Pentium D system. I'm really excited about the possibility of getting Lion to go on my old system. I have tried to install Lion from a USB key. With the real Lion kernel I just get a black screen after the kexts have loaded. With the kernel compiled by Wastez (in Post #65, length 15,400,176) I get the same black screen after loading kexts. With AnV's kernel (posted on I.M. length 19,678,036) the boot does go further but I get the same KP as reported by scififan68 in Post #92. I'm using Chameleon v2.0-RC5 r1083 on the USB key. One other note: when I try AnV's atom kernel (mach_kernel_dp4_atom_apic) the boot proceeds past the kext loading, but stops/hangs after the "BSD root:" line instead of KPing.

We're all rooting for you AnV!! Thanks for your efforts.

Question for Roseman
 

Hey Roseman,
Because I am experimenting too, I was curious if you have booted in -s single user mode, or -x safe mode with the ANV mach_kernel_dp4_atom_apic kernel? Have you gotten any further in the boot process? In the past I have disabled just about everything with regards to kexts and startup items and found I wasn't having a kernel problem but other system files weren't playing well with each other. I was able to use older files to at least get booted in safe mode. Just wondering about your troubleshooting efforts so I don't duplicate over here. -thx

Can someone split or rename this thread to "Lion on AMD"?

The only other thing I had tried was to remove AppleIntelCPUPowerManagement.kext from S/L/E and it made no visible difference. Just now I tried -s & -x in various combinations on the different kernels and found no changes in behavior. One funny little thing I did notice, though, is that when trying the atom kernel, after it stops/hangs following the "BSR root:" line there is still some process running that echos what I type on my (PS/2) keyboard to the screen.

shot in the dark
 

I have not experienced this result. I don't know if this has any significance, but did you try to issue any commands while it was in the hang state?
ls
cd ..
while it echoed your keyboard output?

acermac3: You seem to have PM's disabled, my reply to your PM is below:

I'm not sure what/when you mean "before the kexts loaded". I get the keyboard echoed to the screen after Chameleon says it has loaded a particular kernel, then the names of lots of kexts scroll by, then the system changes (text mode) resolution and starts to initialize various things. I think I see the Firewire get setup, and the keyboard, and near the end of what is shown is a listing of my usb key as the boot device, then there is a line that says"BSD root: disk....." (I'm not at my test system right now, so I'm just going from memory). Then the system just sits there. If I type stuff it appears on screen, but I get no response or prompts. I don't see the disks run or anything. I did try entering some commands, but didn't see anything happen. Whatever is echoing the keystrokes though it does take my pressing 'Enter' as both a Carriage Return and a New Line. That is, if I type something and then hit enter, the next things I type will appear at the begining of the next line on the screen. When I get a chance tonight I will compare this behavior to what I get if I boot my SL installer into Single User mode (-s). Also, tonight I will let you know what is in my /extra directory.

Any progress with the new legacy kernel??? :)

Good luck , Andy! ^_^

I tried both atom and non-atom kernel (on first post) on sse2 only cpu, but I get panic "invalid kernel ip"

http://img832.imageshack.us/img832/6962/unled2ix.th.png

Uploaded with ImageShack.us

while at a sse3 supported cpu, it boots fine

both laptops is USB booting, so I didn't change anything expect the kernel

Problem with dyld patcher where Outlook 2011 and Quicken Essentials both will not open. I tried to manually patch both with the amd instruction patch tool, but no luck. Then I tried going back to the 10.6.8 legacy kernel from nawcom, which doesn't have the corrected AMD FSB detection, and sure enough, it worked perfectly. Any ideas on how this can be fixed? I had to manually put FSB=200000000 like back in the 10.6.2 days when I added my FSB patcher to the old kernel. I haven't yet found the source to the nawcom kernel in order to try reversing my patch now that Chameleon has it.

blackknight with anvs kernel u used the bootflag std_dyld=yes ?

wich disables the integrated dyld and uses the standard one (i guess patching the bins doesnt help when they dont get detected cause they switched off

also with anvs kernel u can use doublefsb=Yes to set your fsb rite when its messed up

Thanks for the bootflag for std_dyld, I couldn't remember what it was. Also, the FSB is correct with AnV's kernel, it's nawcom's that doesn't get it right, though it does apparently use the std_dyld.

Yap after meklort fixed the workaround in Chameleon its there double time once with the kernel and with the bootloader and then things get messed up like sound and stuff by the the time that was done nawcom was off due to illness and didnt fix it in his latest legacy version


btw did u see netkas got the 6970 working last nite ;P

Your welcome:-d

That was just what I needed. It works great and now that I can use AnV's kernel without hardcoding the FSB, sound doesn't skip anymore.

Yeah, I did see that netkas got 6970 working. I have a 6950 unlocked to 6970 that I'd love to get working, but I can't yet run Lion since I'm on AMD. I guess once we get a working kernel, I'll get a chance to try it.

Oops didnt read the top line ....my bad

Hello, newbie here
What do you with all the files you downloaded? First post link leads to 37MB file and I see boot files and whole bunch of other stuffs. I guess it's the source for dyld.
Do I just replace the kernel only with the one i downloaded?


Can someone lead me to the right direction on what to do with this?

Thanks in advance.

Any Progress in the Lion Legacy Mission m8 ?:-d

No, not yet but I've taken a different approach.
I've diffed the standard SL kernel against the standard Lion kernel (to find out what was changed).
Lots of code to go through.
I've also disassembled the Lion DP1 kernel as well as the GM one and have written a little program to strip of the addresses.
I've diffed these together to get instruction changes in the diff.
Studying both may reveal a solution. ;)
I'll upload the diff later.

I've posted the assembly diffs between 10.7.0 DP1 and 10.7.0 GM
I hope somebody can help me identify which instructions enable 32bit (and thus also AMD) support.
They can be found here:
http://www.insanelymac.com/forum/ind...&#entry1750568
I also included my custom otx tool
NOTE: There is a 64bit part to otx but it is untested. If trouble, run it in 32bit, it also needs Xcode

a needle in a haystack looks more sexy ;)



wondering if these compare programms would help us in searching by comparing the 2 files next to each other and find our needle .... just wondering

yeah, I agree, I've been trying for weeks.
Currently I'm designing a custom 10.7.0 kernel with 10.6.8 osfmk directory (requires a lot of adjustments).
I'll keep you posted if it works, then we at least know where to look. ;)

10.7 Kernel for AMD
 

AnV heard that you were on the LION kernel for AMD...was just wondering if you were still on it, cause didn't hear you for a while???!!!
Thanks.

but u did read the topic before u posted did ya ? because that would have made things a little clearer and the question would have answered all itself

Looooots of work on getting it done... haven't isolated the problem yet...

@ AnV
Is there a possibility to run the Lion GM with the 32 bit kernel of the DP Version?
And if it work would it be possible to create an modified version?

Yes DP1 kernel and some other files (like Finder and finder cache), it'll only work on Atom / Yonah though.
Look on the internet (google ;)) for more info.

Did not think on it that there is no source from dp.

I´m also starring at the kernel txt file since yesterday and it´s gona to drive me crazy.

Yeah, I also wish Apple had released their xnu-1699.21.x sources (instead of 1699.22 ones).
With a bit of work they at least would have worked just fine on AMD.

Thank you a lot guys and keep it up, I know there's lots of hard work ahead before getting it done...:).
Also, looks like nawcom too is on it, but didn't really heard lots of him since he came back.
May be you guys can rock together and get it done...:)

I know that this question should have been asked in the 10.7 forum, its just on a hurry that I forgot.