Need some help on testing semthex kernel...

[Fernando Birra]

Hi,

 

I think I managed to build the semthex kernel with the famous Karma key but I haven't been able to load into the GUI. It hangs on the Starting OSX Windos...

 

This is what I did:

 

1. put the karma key into the commpage.c

2. compiled kernel and copied to second osx partition

3. replaced IOATAFamily.kext in new partition to be able to boot (ICH6 in my motherboard)

4. Copied AppleSMBIOS from 10.4.7 to new partition

5. Copied r2d2 from 10.4.7 to new partition

 

On first boot I noticed that r2d2 was restarting my computer so I disabled it. This got me to the point where I am now. I can boot into single user but if I try to launch the GUI it hangs on Starting OSX screen.

 

My Jas 10.4.8 DVD is 2 or 3 days away from being complete.

 

My questions are:

 

1. Is the karma key exactly what is inside the semthex files? I noticed some things different from the strings present in the previous kernel. Like the ':' after 'today' and the final © message. I opted to make an exact copy of the 256 bytes present on the previous kernels. Not sure if this is the way...

 

2. Do I need to load r2d2.ext ?

 

3. Should I use AppleSMBios.kext from 10.4.7 or stick with the original from 10.4.8?

 

Thanks in advance...

[Fernando Birra]

Come on guys. I really want to test my NVidia card...

 

No one wants to answer ?

 

Fernando

[MichalK]

No one wants to answer ?

Fernando

 

First of all, you're stuck because you have disabled the r2d2 thus cannot load encrypted binaries. Try to grab the decrypts somewhere (I don't have them as I'm using mifki's), or get a kernel with r2 inside (such as mifki's if your hardware supports xd/hpet, or LSD which is supposed to be semthex with added r2).

 

Regarding your karma - I haven't compiled it, but looking at the sources it's clear that it must be exactly 256bytes. Before putting anything check karma's length.

 

Good luck

[Fernando Birra]

First of all, you're stuck because you have disabled the r2d2 thus cannot load encrypted binaries. Try to grab the decrypts somewhere (I don't have them as I'm using mifki's), or get a kernel with r2 inside (such as mifki's if your hardware supports xd/hpet, or LSD which is supposed to be semthex with added r2).

 

Regarding your karma - I haven't compiled it, but looking at the sources it's clear that it must be exactly 256bytes. Before putting anything check karma's length.

 

Good luck

 

Thank you for your help. I made some progress with mifki's kernel (but not the first one).

 

 

I also noticed that the karma needs to be *at least* 256 bytes since the rest will end up ignored. The poem is slightly longer. But, as I told you, there is this little difference with the missing ':' but that's perhpaps because semthex didn't want to run into legal problems. But I checked the equivalent sections on my 8.4.1 and my 8.8.1 kernel and they were the same, so the Karma was probably ok.

 

I had to disable r2d2.kext because it rebooted the machine the moment it got loaded. I tried booting in single user mode and load it manually before proceeding. It just simply rebooted. No panic no nothing. Reboot!

 

Then I started to play with mifki's kernel. The first time I had a lot of 'coreservicesd' crashing and the GUI didn't start most of the times. Then I followed someone's suggestion to install the apple 10.4.8 update directly on top of a working Jas 10.4.7 install instead of virgin one (like I did before).

 

This time it booted into the GUI but it kept crashing during the registration process. The demo sound that plays in the background enters a loop and the computer hangs.

 

I tried the second version of mifki's kernel and it worked like a charm.

 

I still have some problems now:

 

1. My integrated Intel915 isn't working (no problem since I will be putting my NVidia inside it)

2. My Belkind Wireless PCI card seems to need a warm start most of the times (I need to boot windows for it to be properly initialized before being able to use it in OS X). I installed the Wireless support from Jas 10.4.7 DVD

3. My integrated Yukon Gigabit ethernet is recognized but I'm far from the router so I don't know if I also have problems with it like others complain (cable disconnected).

 

So, one final question. If I want to play with semthex kernel I will need the r2d2 extension or the decrypted binaries. And what shoud I do with the AppleSMBios from mifki? should I keep it or replace it with the original one from Apple 10.4.8 update?

 

Thanks once again for replying.

 

Fernando

 

Ps. Can't wait to test NVidia with Titan

[semthex]

Try to grap latest LSD somewhere. It will ahve all you need.

[MichalK]

Thank you for your help. I made some progress with mifki's kernel (but not the first one).

I also noticed that the karma needs to be *at least* 256 bytes since the rest will end up ignored. The poem is slightly longer. But, as I told you, there is this little difference with the missing ':' but that's perhpaps because semthex didn't want to run into legal problems. But I checked the equivalent sections on my 8.4.1 and my 8.8.1 kernel and they were the same, so the Karma was probably ok.

 

If you're unsure of your Karma, just leave compilation of own kernels. You'll never be sure if you have failed due to bad compilation or because of other factors. Go for a ready-built kernel.

 

I had to disable r2d2.kext because it rebooted the machine the moment it got loaded. I tried booting in single user mode and load it manually before proceeding. It just simply rebooted. No panic no nothing. Reboot!

8.8.1 kernels require a special R*d*. If you don't own one, you'll fail.

 

I still have some problems now:

1. My integrated Intel915 isn't working (no problem since I will be putting my NVidia inside it)

2. My Belkind Wireless PCI card seems to need a warm start most of the times (I need to boot windows for it to be properly initialized before being able to use it in OS X). I installed the Wireless support from Jas 10.4.7 DVD

3. My integrated Yukon Gigabit ethernet is recognized but I'm far from the router so I don't know if I also have problems with it like others complain (cable disconnected).

1. You mean GMA900? Replace AppleIntelIntegratedFramebuffer.kext and OpenGL.framework with the files found on your JAS DVD in the GMA900 package, then delete AppleIntelGMA950.kext (or similar name).

2. Don't know since don't have WIFI

3. That's typical problem with updated Yukon. Get the working kext in here: http://art5dog.com/IONetworkingFamily.zip , look at the info.plist for the AppleYukon plugin, and copy-paste the ID section to 10.4.8's AppleYukon plugin of IONetworkingFamily.kext . You might also copy this downloaded kext directly to your extensions if you don't mind using older drivers.

4. On the D915 you'll find ATA issues with 10.4.8 update. Follow the Paulicats guide posted on hackintosh.

 

So, one final question. If I want to play with semthex kernel I will need the r2d2 extension or the decrypted binaries. And what shoud I do with the AppleSMBios from mifki? should I keep it or replace it with the original one from Apple 10.4.8 update?

For mifki's you don't need decrypts (as there's a built-in R*d*). For plain semthex you do need them, but if you use LSD (which is semthex+r*d*) you don't need the decrypts.

You must use patched (mifki's package or some patched distros) SMBIOS to support basic kernel calls.

[Fernando Birra]

If you're unsure of your Karma, just leave compilation of own kernels. You'll never be sure if you have failed due to bad compilation or because of other factors. Go for a ready-built kernel.

8.8.1 kernels require a special R*d*. If you don't own one, you'll fail.

1. You mean GMA900? Replace AppleIntelIntegratedFramebuffer.kext and OpenGL.framework with the files found on your JAS DVD in the GMA900 package, then delete AppleIntelGMA950.kext (or similar name).

2. Don't know since don't have WIFI

3. That's typical problem with updated Yukon. Get the working kext in here: http://art5dog.com/IONetworkingFamily.zip , look at the info.plist for the AppleYukon plugin, and copy-paste the ID section to 10.4.8's AppleYukon plugin of IONetworkingFamily.kext . You might also copy this downloaded kext directly to your extensions if you don't mind using older drivers.

4. On the D915 you'll find ATA issues with 10.4.8 update. Follow the Paulicats guide posted on hackintosh.

For mifki's you don't need decrypts (as there's a built-in R*d*). For plain semthex you do need them, but if you use LSD (which is semthex+r*d*) you don't need the decrypts.

You must use patched (mifki's package or some patched distros) SMBIOS to support basic kernel calls.

 

Ok, kernel compilaton left aside, I'm using mifki's kernel now. Seems that r2d2 functionality is inside since I don't need it. But I do need his own AppleSMBios.kext.

 

1. Yep, GMA900! I solved the problem like you said but only after trying the fix from Jas 10.4.7 DVD installer. Only to find some nice kernel panics at boot. Had to restart from Apple's 10.4.8 update, then mifki's kernel and extension, then IOATAFamiliy (to have ICH6 support) and finally all was ok.

 

2. Solved the problem. It seems that Shared key WEP encription isn't working very well. I changed it to open and even the signal meter gets higher readings. Go guess...

 

3. Ok, I will try your suggestions and I don't mind using older drivers at all. Specially if they work

 

4. Ooops. And I thought semthex was sending me for a walk when he mentioned LSD in his post! I'll search for LSD then.

 

Forgive all my ignorance and thank your for all your help.

 

Fernando

[MichalK]

4. Ooops. And I thought semthex was sending me for a walk when he mentioned LSD in his post! I'll search for LSD then.

 

My opinion is: stay with mifki's, if only your hardware is compatible (and since you've managed to boot, it IS compatible). The reason for me is that the less patches, the more stable our kernel should be. I've compared the code (mifki's/semthex's) on the field of mifki's changes, and it seems that they both have chosen the same solutions there. However, you'll not experience any hpet-replacement issues. But it's just my opinion. I appreciate both approaches (close-to-apple-hw and as-compatible-as-possible) but there's always a tradeoff.