View Full Version : Kernel & system.kext doesnt match
richiekh
09-20-2010, 02:52 PM
Searching on the net, this seems to be a common issue. I'm not able to plug any usb device without rebooting the mac. First thing i've found on the net, was that (most likely) the kernel and system.kext doesn't match.
I've checked, and indeed it didnt match.
System.kext
System Resource Pseudoextentsion, Apple Inc, 10.4.0
Kernel
Darwin Richie-Holzkens-Mac-Pro.local 10.0.0 Darwin Kernel Version 10.0.0: Mon Oct 12 04:06:05 AST 2009; anappirtrvh:xnu-1456.1.26/BUILD/obj/RELEASE_I386 i386
Now I want to fix this obviously, but how? How do I update my kernel without harming the computer as it is right now. I've been struggling to get it working. Right now, everything works (as far I know) except the USB.
Specs:
Mobo: Asus M2N-XE
CPU: AMD Phenom X4 9500 Quad Core
GPU: Asus Nvidia Geforce 8800GT 512mb
RAM: 2x 1GB OCZ XTC GOLD 800 Mhz DDR2
richiekh
09-20-2010, 03:45 PM
Allright, I've updated the kernel to darwin 10.4.0, though the usbs still doesnt seem to work :S
Taisto
09-20-2010, 07:17 PM
Try to install the newest AnV kernel package from Andy ( it's in New Releases forum here ) then replace both mach_kernel and system.kext, both from the same source. Remember to fix all permissions, and boot with -f to rebuild the cached set of kexts. This might help cause they sometimes don't want to work with files from "other source".
richiekh
09-20-2010, 09:58 PM
Well the problem is, some how I can't really see what the kernel is.
If I go to the root folder of my mac system, all possible kernels I see are the following:
Chocolate_kernel
mach_kernel.backup
and legacy_kernel which doesnt have an icon.
So my suggest would be that there is some file who points the system which kernel it must use.. Right?
Even though, which one would you suggest?
Taisto
09-21-2010, 06:17 PM
Exactly, the point in where you choose which kernel to load is your boot.plist file. If you open it, you'll see those lines :
<key>Kernel</key>
<string>mach_kernel</string>
And i think that this is the source of your problem. I see that you have a file named Chocolate_kernel, and i assume that your boot.plist file by default points to a file named mach_kernel - which is simply not there. Unless you were editing your boot file that is.
Just to check:
In bootloader, type in Chocolate_kernel and hit enter. If it boots, then try the following.
Main solution:
Simply edit your boot.plist file and replace "<string>mach_kernel</string>" with "<string>Chocolate_kernel</string>", or rename the kernel file back to mach_kernel. Hopefully that's the only problem and you'll be able to boot normally :)
richiekh
09-21-2010, 09:41 PM
Just before I'll do this action, I want to be sure.
If I do this, and it may damage the system, am I able to use single user mode, to edit that file again and change it back?
(following by booting with -f)
Imkantus
09-21-2010, 09:52 PM
As Taisto wrote you can just type the name of your desired kernel file at the bootprompt. This would be the recommended way of testing a different kernel - if you know it works you can still edit the Boot.plist
system.kext is just kind of pseudo kernel extension on Snow Leopard / Darwin10. It's version should not be the source of your problem...
richiekh
09-21-2010, 09:54 PM
As you see here, it uses the legacy kernel:
http://img192.imageshack.us/img192/6784/screen001x.jpg
(as you see, i allready feel home in the mac osx world :P.)
As you can see here, it does exist: http://img696.imageshack.us/img696/305/screenshot20100921at105.png
If I'm correct, I'm using the kernel of the guy you referred me to. Though I'm not entirely sure :-\
Though the kernel version did change. (Comparing with the other 2 results)
richiekh
09-21-2010, 10:03 PM
As Taisto wrote you can just type the name of your desired kernel file at the bootprompt. This would be the recommended way of testing a different kernel - if you know it works you can still edit the Boot.plist
system.kext is just kind of pseudo kernel extension on Snow Leopard / Darwin10. It's version should not be the source of your problem...
Though, does a kernel change directly react on the hardware? I mean, as far I know, the only problem right now, is the USB Detection. Though I did install the "fix". Also I'm able to do some boot changes with the bootloader (Charmeleon RC4)
see:
http://img375.imageshack.us/img375/305/screenshot20100921at105.png
http://img199.imageshack.us/img199/305/screenshot20100921at105.png
Though I will try different kernels, I do have my doubts, that it will fix it. Not that I know a lot about kernels and such.
richiekh
09-22-2010, 07:46 AM
I've tried some kernels, by typing it in the bootloader, but there didnt change a lot systemwise.
The Chocolate_kernel brought me back to 10.0.0, and the Legacy_kernel to 10.4.0, If I use lec_kernel (renamed it to that, easier to remember), which is the newest from Andy. I get the same results of the Legacy_kernel.
Though, the USB hardware still don't recognize any USB devices, except from my mouse. (Logitech G500) My keyboard is a PS/2 one (Also from Logitech).
Noticed something new though. When I plug my 4GB USB-Stick, nothing happends, ok.. Thats not new. Though If I replug it, no matter if it is in the same USB port or a differend one, the whole system stops responding. (Most likely a Kernel Panic.)Though I don't see any errors appearing.
edit: This is the kernel result right now (the newest one)
Darwin Richie-Holzkens-Mac-Pro.local 10.4.0 Darwin Kernel Version 10.4.0: Tue Jul 27 15:35:59 EDT 2010; annappirtrvh v4 :xnu-1504.7.4/BUILD/obj/RELEASE_I386 i386