Jump to content

Getting kernel panic with mach_kernel AMD SSE3 activated (or no SSE2 patch applied)


16 posts in this topic

Recommended Posts

Hi folks,

 

i am giving this thing now over to you, i really don't know how to continue fixing my installation.

 

FujitsuSiemens AMILO A3667

AMD mobile Athlon64 4000+ (SSE3 capable)

1GB DDR 333

VIA K8T890 + VT8237R

ATI Mobility Radeon X700

 

Tried 10.4.6 HOTiSO & now using 10.4.7 JaS - both running native

 

Now, setting up the System (doesn't matter with which of those two images) with kernel patched to SSE3 emulation everything runs pretty well (mach_kernel from DVD root, with base patch, amd enabler, sse3 emulation and so on). Sound, ATA, Ethernet, AirPort, Video, etc... is OK. The machine is a bit slow due to the emulation, but it works. Now using a mach_kernel without SSE3 patch my machine hangs during bootup! It recognizes SSE3, continues booting and hangs (kernel panic 0x0019c352) sometimes on com.apple.driver.ApplePS2Controller, sometimes on some ACPI or AHCI extensions, and the best is: sometimes it finishes booting and starts the OS X desktop, but then (can happen every second) it hangs again and nothing moves. I've tried everything, i.e. tried to choose other combinations on customised setup, tried to exchange the files causing panic with other versions, don't know... nearly tried everything...

 

Why does my machine hang on SSE3?? When it succeeded booting without SSE3 emulation it is really fast, and the fact that my hardware is well supportet makes it worth trying to fix my problem, but i really don't know how.

 

There is something else i am wondering about: The HOTiSO image has an option for AMD SSE3 on installation, the JaS image only has AMD kernel to choose, which already contains the maxxuss patch for SSE3 emu. Why isn't there an option for SSE3 like the HOTiSO has??

 

Thanks for reading...

Alex

the hotiso and jas images are pretty much the same thing, might want to try myzar's iso.....some people running amd's report more sucess with it.

 

However some processor's even though they are sse3 capable can't get it to run for some reason. Luck of the draw sorta thing...

Hi!!

 

I've got the same problem as Pelle007, on very similar hardware.

My computer is

 

FujitsuSiemens Amilo A 1667 - only difference between Amilo A 3667, and Amilo A 1667 is the CPU speed (and socket, but i'm not sure).

CPU is AMD mobile Athlon 64 SSE3 Capable 3400+

 

I've tried all OS X relases from JaS, HOTISO, and Myzar - every one of them gives the same problem described by Pelle007.

 

Maybe anyone will find a solution for us..........

Hi,

 

i think wondergod is right, i had the same idea.

I think the problem is the 'mobile' Athlon64 CPU, they seem to be the same as the desktop versions are (exept of power consumption and power saving options), but probably there is one relevant thing in the architecture that differs from the desktop versions and causes the panics at boot...

 

Anyone here running OS X on mobile Athlon64?? Never read of anyone before...

 

Alex

Is it right that the SSE2 patch catches invalid SSE3 instructions to emulate them? I've read somewhere that a CPU capable of SSE3 does't care about the SSE2 patch and takes SSE3 tasks before they are going to be emulated (This would be the reason why there is only one kernel with all patches applied for AMD on the newer releases). This means that our mobile Athlon64 should work with SSE3 activated, not caring about the SSE2 patch and patched system files. And this is why the questions comes up for me: Why does the system run that slow with SSE2 patch? And why does it run so fast without SSE2 patch, but crashes then?? There must be s.th. strange about the AMD mobile Athlon64 SSE3 function...

 

...i've been reading this forum for hours, searching for i.e. 'mobile athlon(64)' and 'applePS2controller.kext' and so on. Many Fujitsu-Siemens users expirience problems with the mentioned .kext file, but the main problem they have are not working keyboards and mouse, solution: deleting the kext, use USB mouse and keyboard.

 

Deleting the .kext ends in other extensions to crash for me, i.e. broadcom wireless driver or acpi driver.

During the new releases (10.4.4 and 'higher') the ApplePS2controller.kext seems to be replaced with a maxxuss patched one, has anyone tried 10.4.3 and lower .kext? Or complete installation with earlier release and tried applying each patch and update by your own? Can't get my hands on this versions anymore, no seeds. Really would like to try, i think the newer versions have too many patches installed for compatibility which could also be a reason for our problems. It could probably be an advantage stocking an early virgin version of OSX up by applying patch for patch (only with those for our machine's needs).

 

I regret not beeing involved in Mac OS x86 from the early beginning (wasn't 100% interested, have had G3 Powerbook), it is difficult for me to find information about which files have been patched (why, and what they all do), how each single update was applied and so on...

 

After thinking long enough about a new idea i have, i remember again how strange the problem is (working nearly perfectly with SSE2 patch, but leaving it for making use of my strong CPU causes only problems and kernel panics), and realise that it must be a hardware problem i can't solve that easy and tend to give up finally (about 6 hours spent daily for 3 weeks now, on weekends sometimes more time, damn).

 

:D

 

Alex

  • 3 weeks later...

Hi!!!!

 

Now I've got OS X 10.4.1 - it has got huge kernel - about 8MB.

The point is that this kernel works just perfect for me, but unfortunetly it's very diffrent than 10.4.3 kernel and it's not replacable by another kernels.

 

SSE3 is fully working - my computer is faster than Mac Pro G5 - it's amazing!!

Hi!

 

Thanks for this info, i've nearly forgotten this thread already.

 

Will try this as soon as possible, had the same idea to try this one - a friend just downloaded the nessesary version for me, i only have to catch it...

 

Thanks again...

;)

 

I can confirm this version is working for my system!!

For installation i used the 10.4.1 generic install disk, SSE3 is working perfectly from scratch!!!

 

There is only one thing causing the system to slow down sometimes:

 

My chipset is VT8237R, AppleVIAATA.kext is loading without problems - the info.plist already contained all needed device ids. I'm using a PATA drive in my laptop, though it has a SATA supporting chipset.

 

The system is really getting slow sometimes, not reproducable, but appearing regularly. The harddisk starts working suddenly, while the system is not usable anymore, until it finishes it's activities. I also experienced this issue with other versions of OS i tried before(see above), but thought the problem has to do with the overall bad running system. Apart from this problem i was not sure whether UDMA is enanbled, but it seemed it wasn't.

 

Now i'm using the AppleGenericATA.kext, the problem disappeard and the system is faster than before, but i'm sure it never will be like it would with a working AppleVIAATA.kext, UDMA enabled.

This solution is enough to work on getting the right kext running without problems. Actually i'm reading various posts dealing with "VT8237R" and "AppleVIAATA.kext" to gather some information, probably this problem is already known?!

 

BUT I'M VERY HAPPY MY LAPTOP IS RUNNING A USEABLE OSX, PEOPLE WITH FSC A3667 TRY THIS!!

THANK YOU chmielu FOR YOUR HELP!! EVEN MY USB MOUSE IS WORKING, BEFORE IT DIDN'T. AND I WAS SURPRISED ABOUT THE BATTERY STATUS APPEARING THE FIRST TIME FOR ME!

 

There are some smaller problems left, which i really do not care about right now: sound is workling, enabled 48kHz, good sound, one speaker so far, system's volume bar not working, keyboard volume and software does. wlan is not recognised. etc.

 

When DL finishes, i'll try 10.4.3. I want to find out what really stops me using the versions i already tried, by approaching in little steps to newer versions.

 

This whole thing really starts beeing a new hobby for me...

Hi!!!

 

I'm glat that you're happy with this version and everything is working for you.

 

I've tried 10.4.3 alredy, and I know it acts exactly like 10.4.5 and newer versions - everything works, but performance is very slow. It's because of REAL TIME CLOCK issue - something in newer kernel is f***ed up.

 

 

You wrote that your USB wont work with newer versions - its because new USB kext-s - they aren't good, but i have solution for it. I've search this forum and downloaded 10.4.3 USB KEXT form some thread, and repleace my system kext with those, witch I've downloaded, and suddenly my USB start working.

 

About BATTERY STATUS INDICATOR ypu have to search this forum. Ther is a solution for this issue too. Try to search PowerManagementBUNDLE.kext - or something like this...

 

Keep me informing about your progress

 

GOOD LUCK

 

Chmielu

:idea:

 

I can confirm this version is working for my system!!

For installation i used the 10.4.1 generic install disk, SSE3 is working perfectly from scratch!!!

 

There is only one thing causing the system to slow down sometimes:

 

M

 

i guess you have deadmoo image (tiger.img) cause you say 10.4.1

about the slowdowns ,in case you havent done allready : (HUGE DIFFERENCE)

 

There is a file on all newly-installed OSX86 PCs called "AppleTPMACPI.kext," it tries to find a TPM chip that is only on the real Intel Developer Machines. It uses all system resources trying to accomplish its impossible task. Here is how to delete it:

/System/Library/Extensions/" Delete the file "AppleTPMACPI.kext" in this folder, reboot.

i guess you have deadmoo image (tiger.img) cause you say 10.4.1

about the slowdowns ,in case you havent done allready : (HUGE DIFFERENCE)

 

There is a file on all newly-installed OSX86 PCs called "AppleTPMACPI.kext," it tries to find a TPM chip that is only on the real Intel Developer Machines. It uses all system resources trying to accomplish its impossible task. Here is how to delete it:

/System/Library/Extensions/" Delete the file "AppleTPMACPI.kext" in this folder, reboot.

 

Wrong, no deadmoo image!

I worte that i am using the generic install disk, there is no AppleTPMACPI.kext loaded!! ;)

The problem is definitly the AppleVIAATA.kext...

 

@chmielu:

 

Thank you again for this new information!

Everything new i gonna post here...

×
×
  • Create New...