Jump to content
214 posts in this topic

Recommended Posts

Back up ur old mach_kernel, u can just drop in Documents and call it mack_kernel.old.

Delete the one in root folder.

Unpack the zip file of Daemon or mifki, the mifki one has also AppleSMBIOS.kext.

(use the latest downloads).

Then copy the kernel u want to try in your root directory by dropping it there.

And drop AppleSMBIOS.kext into /System/Library/Extensions (after backing up and deleting the original one).

I tried DaemonES without mifki's AppleSMBIOS.kext, and it worked fine.

I used AppleSMBIOS.kext with mifki's because he included it, and since they do not put a guide file, I guess I wanted to play safe, but AppleSMBIOS.kext modified is included in JaS release installation, but maybe mifki did more, I dont know...

Delete Kextcache files in /System/Library

Repair permissions as usual, and it should work.

This is how i do mine...

Good luck

 

So fast reply!!!

Thanks Billy!!!

In my case: I have the Intel 3.0G with SEE3 & HPET supported, while NX unsupported!, can U suggest me to use which kernel is better for me?

Thanks again!

Well I dont know, I am currently using latest mifki's which is hpet and non-nx.

I do not know what hpet does (its a timer), maybe it is useful, and mifki's kernel is supporting, so i am giving it a go.

For me they seem all the same (semthex and these ones), it will be good if you collect them, and if u get a crash, replace another...

i have hpet so i use one that support hpet, but DaemonES one is good too, and there are dudes who dont have hpet support, so he is doing them a favor...

good luck

I'll see, what I can to do with this.

 

Thank you, it would be greatly appreciated :pirate2:

 

 

How to change the kernel after I installed Mac OSX Jas 10.4.8 with Semthex's kernel without reinstall everything?

 

mv /mach_kernel /mach_kernel.??

 

cp /??/mach_kernel /mach_kernel

 

Repair Permissions.

dragonheart what cpu do you have?

 

JaS sorry men, misunderstand from my side (english is a third language in my real live).

I know you kernel devs all hate each other hand have your issues,but dont drag me into it.
Nooo. I've worked with mifki, but he has no interested in current kernel, so I get dev process in my hands. I like semthex, he is a good guy, but I don't like his way...

I believe, that someday we'll be working together with CVS, mailing list and so on, and that will be absolutely legal (e.g. w/o r*d* in kernel).

Ezhoon your welcome.

Billy

But they both work good, and they report PCI cards (which not the case with Semthex)
That's strange, because in my system profiler pci cards disappeared.
However your kernel, DaemonES does not work with vmware, it gives a kernel stack fault, like first semthex releases.
Try to boot with -legacy boot parameter. If you want, I can autodetect VMWare and activate -legacy key automatically.

dvil

Your kernel is working perfectly in my system, thanks for add a solution for the bug on the Dells
Yes it activate additional cpuid functions for Core 2 Duo/Core Solo cpu's.

 

OK so my version of kernel works through HPET, if you have Intel ICH based board, and w/o it in another cases, also it has noNX JaS patch.

dragonheart what cpu do you have?

 

JaS sorry men, misunderstand from my side (english is a third language in my real live).

Nooo. I've worked with mifki, but he has no interested in current kernel, so I get dev process in my hands. I like semthex, he is a good guy, but I don't like his way...

I believe, that someday we'll be working together with CVS, mailing list and so on, and that will be absolutely legal (e.g. w/o r*d* in kernel).

 

I agree 100%. I hope you guys can get it together, and we can have one working kernel.

With 3 different kernel makers, I am now really confused about which to use on my system. I don't like the trend toward no-NX and no-HPET kernels, as I feel it introduces unnecessary changes for those who have modern hardware. I hope kernels will eventually evolve to 2 versions: modern and legacy, and that kernel hackers will collaborate on them instead of each growing their own.

 

In the meantime, can anyone suggest appropriate kernel for my hardware?

With 3 different kernel makers, I am now really confused about which to use on my system. I don't like the trend toward no-NX and no-HPET kernels, as I feel it introduces unnecessary changes for those who have modern hardware. I hope kernels will eventually evolve to 2 versions: modern and legacy, and that kernel hackers will collaborate on them instead of each growing their own.

 

In the meantime, can anyone suggest appropriate kernel for my hardware?

 

Daemon's kernel is modified(for more compatible) mifki's kernel.

So you may choose between semthex's and Daemon's kernels.

:)

DaemonES, I think the kernel is the one that loads /var/vm/sleepimage which is supposed to save your memory state in that moment, so in other words when you safe sleep it writes that file which contains all your ram info so maybe the kernel doesn't loads that file at startup and that's why it cant safe sleep

 

Remember safe sleep is not equal to sleep

mv /mach_kernel /mach_kernel.??

 

cp /??/mach_kernel /mach_kernel

 

Repair Permissions.

 

thanks for reply but I don't know extractly what U mean with the "??"!

Use your way, we can replace the match_kernel even the mach_kernel is invisible, rite?

Hmmmm..this is weird.

 

I thought DaemonES's newest kernel fixed the reboot problem for my ds3 mobo but,

last night, when I tried to shut down the computer it just rebooted again and wouldn't shut down. :blink:

 

Is there anyone having the same problem?

DaemonES, anything new with Merom 2cpu :D

 

thanks for reply but I don't know extractly what U mean with the "??"!

Use your way, we can replace the match_kernel even the mach_kernel is invisible, rite?

 

 

??= where your kernel is, put it in /Users so its easy to remember.

 

.??= what you want to call it, I use m1, m2 or s1, s2 or DS1, DS2.

 

There are so many now you should name them to keep track.

 

If your using semthex, look to _Prasys_ thread

: http://forum.insanelymac.com/index.php?showtopic=33039

DaemonES said on the Russian forum, that he will probably stop the development of his kernel.

The good news, however, is that he is trying to bring together a team of coders to work on a Darwin port of ALSA – and that means if they succeed we’re gonna have working OS X drivers for nearly every sound card out there.

DaemonES, Merom owners need your help :angel:

It seems no one els can make a compatible kernel :construction:

 

This is basicly most of the time because ppl cannot read FAQ and submit a useful bugreports. Sorry to say but "oh panic" is not realyl enough to tell what is wrong with you and that is all I got from you since days. Not even on IRC I got ANY useful answer yet, so pls don't complain you get any solution. If you are really intrested in a soultion, submit a bug report and you will be fine for sure.

DaemonES, the message before boot, with no flags or with cpu=2 is

 

mDNSResponder: mDNSPlatformRawTime: last_mach_absolute_time (There are a bunch of numbers here)

mDNSResponder: mDNSPlatformRawTime: this_mach_absolute_time (There are a bunch of numbers here)

mDNSResponder: mDNSPlatformRawTime: this_mach_absolute_time went backwards by (numbers) ticks: setting correction factor...

 

It will repeat the same thing but with different numbers for the missed time. If I'm able to boot it will only stay on for a minute or two then either shuts down or goes to black screen with prompt saying the same stuff as when it doesn't boot.

I will get a bug-report to you and semthex, and hopefully something can be figured out :)

semthex stop your marketing here :(

joe75 it seems to timer problem. Try to enable all ACPI, RTC stuff in your BIOS settings.

 

chelhydra it's not possible without binary hacking. This id's hardcoded to SPPlatformReporter.

×
×
  • Create New...