Jump to content

[AMD] Yosemite Kernel Testing (for help use the Help Topic)


Duran Keeley
 Share

1,948 posts in this topic

Recommended Posts

it works with fsb=200 at boot and I screenshot some info to see if it helps to fix the issue and im using chameleon only for booting the osx.

thanks in advance!!!

Thank for info ! This cpu-x is wrong ! What bootloader you use ? ))) 

 

 

What's i do wrong, i used u last kernel(kernel_10.10.5_rc2.zip)?

My PC config:

CPU: AMD-FX6300

Motherboard: Gigabyte 970A-DS3P

GPU:Radeon R7 265

Ram:4gb

 

kernel flags: -v kext-dev-mode=1 darkwake=0 USBBusFix=Yes npci=0x2000 dart=0, tried used npci=0x3000, GraphicsEnabler=No arch=x86_64

 

kexts: FakeSMC.kext, NULLCPUPowerManagement.kext, RealtekRTL8111.kext

 

BIOS Settings: VT-d: disable, OS Type: Other OS, USB3 controller:Disable, Legacy USB: enabled, Sata type: AHCI

 

 

 

It is problem model , you need replace model MacPro3,1 to iMac... ! And try ! If same problem , try delete kext AppleMobileFileIntegrity.kext ! 

Link to comment
Share on other sites

Boot with flag fsb=200

 

Thank for info ! This cpu-x is wrong ! What bootloader you use ? ))) 

 

 

It is problem model , you need replace model MacPro3,1 to iMac... ! And try ! If same problem , try delete kext AppleMobileFileIntegrity.kext ! 

1)fsb=200

kernel panic

2)model iMac 14.1

kernel panic

3)fsb=200 + model iMac 14.1

kernel panic

4)delete kext AppleMobileFileIntegrity.kext

9g3W74ZQrWo.jpg

 

no panic, but not working =)

Link to comment
Share on other sites

@Jaylex + Hiragent

.

 Backtrace with Extensions with AppleMobileFileIntegrity.. this has nothing to do with the kernel.
you must install the AppleMobileFileIntegrity.kext from a previous OS X version, or delete it.
but I think it's better to change the drivers from a previous version, then fixed the permissions then your system should work
 
Edit:
... but the cause with opcode problem .... may be related with the kernel
 
Edit2:
....you used a fresh Install? or uses an existing OS X version? you should always test a new kernel on a new installtion,Otherwise the result can be falsified, my opinion.
Edited by spakk
Link to comment
Share on other sites

1)fsb=200

kernel panic

2)model iMac 14.1

kernel panic

3)fsb=200 + model iMac 14.1

kernel panic

4)delete kext AppleMobileFileIntegrity.kext

 

 

no panic, but not working =)

You delete flags kext-dev-mode=1 darkwake=0 dart=0 GraphicsEnabler=No arch=x86_64 and try .

  • Like 1
Link to comment
Share on other sites

You delete flags kext-dev-mode=1 darkwake=0 dart=0 GraphicsEnabler=No arch=x86_64 and try .

nothing changed(

You delete flags kext-dev-mode=1 darkwake=0 dart=0 GraphicsEnabler=No arch=x86_64 and try .

:excl: Installer run with kernel (10.10.5_SSEPlus_V2.zip in this thread at 80 page) and restored AppleMobileFileIntegrity.kext

Link to comment
Share on other sites

@Jaylex + Hiragent

.

 

 Backtrace with Extensions with AppleMobileFileIntegrity.. this has nothing to do with the kernel.

you must install the AppleMobileFileIntegrity.kext from a previous OS X version, or delete it.

but I think it's better to change the drivers from a previous version, then fixed the permissions then your system should work

 

Edit:

... but the cause with opcode problem .... may be related with the kernel

 

Edit2:

....you used a fresh Install? or uses an existing OS X version? you should always test a new kernel on a new installtion,Otherwise the result can be falsified, my opinion.

 

With your kernel I don't have issues only with Bronya kernels and I can boot the osx with Bronya kernel with the fsb=200 flag so I think the issue is between the bootloader and the bronya kernel, the installation was made with the chameleon USB installer app and I did it a while ago I try to use enorch to update the bootloader last time but It didn't work.

I'm not using clover or anything like that just the chameleon.

Thanks!

Link to comment
Share on other sites

nothing changed(

:excl: Installer run with kernel (10.10.5_SSEPlus_V2.zip in this thread at 80 page) and restored AppleMobileFileIntegrity.kext

If with my kernel installer don't works ? )))

 

 

With your kernel I don't have issues only with Bronya kernels and I can boot the osx with Bronya kernel with the fsb=200 flag so I think the issue is between the bootloader and the bronya kernel, the installation was made with the chameleon USB installer app and I did it a while ago I try to use enorch to update the bootloader last time but It didn't work.

I'm not using clover or anything like that just the chameleon.

Thanks!

What version chameleon you use ? )

Link to comment
Share on other sites

If with my kernel installer don't works ? )))

 

 

 

What version chameleon you use ? )

I don't know cause I'm at work right now but when I get home at night I let you know and by the way your kernel in benchmarks is the fastest out of all of the ones I have try and it feels fast too!!

 

Thanks!

  • Like 1
Link to comment
Share on other sites

With your kernel I don't have issues only with Bronya kernels and I can boot the osx with Bronya kernel with the fsb=200 flag so I think the issue is between the bootloader and the bronya kernel, the installation was made with the chameleon USB installer app and I did it a while ago I try to use enorch to update the bootloader last time but It didn't work.

I'm not using clover or anything like that just the chameleon.

Thanks!

I can not give a statement about what advantage or disadvantage of the kernel has. I have not tested the kernel and can not be able to give a commentary.
I think that you should have a little patience, Bronya gives everything to adjust the kernel to your system...... and if it should not be possible, then you can use the other kernel.
I wait for El Capitain xnu source.
  • Like 1
Link to comment
Share on other sites

 

Sorry, but with u kernel it's don't work

Cool ! )) Should work ! ))

 
P.S.
One strange ! 
I found one that if in BIOS costs auto multiplier , is boot or kernel reads other multiplier , example should receive mult is 18 , but give 19 . Is strange . 
If in BIOS used manual multiplier to 18 , then kernel or boot is reads this correct and gives correct multiplier !
  • Like 2
Link to comment
Share on other sites

I can not give a statement about what advantage or disadvantage of the kernel has. I have not tested the kernel and can not be able to give a commentary.

I think that you should have a little patience, Bronya gives everything to adjust the kernel to your system...... and if it should not be possible, then you can use the other kernel.

I wait for El Capitain xnu source.

Thank you for everything your kernel works awesome I'm just curious why the bronya kernel works with fsb=200 and not without,I think he should look at your kernel to see the difference's in your kernel and he's kernel.
Link to comment
Share on other sites

 

 

Cool ! )) Should work ! ))

 
P.S.
One strange ! 
I found one that if in BIOS costs auto multiplier , is boot or kernel reads other multiplier , example should receive mult is 18 , but give 19 . Is strange . 
If in BIOS used manual multiplier to 18 , then kernel or boot is reads this correct and gives correct multiplier !

 

mac is installed now, but not work(

It's reboot after that i try to start it from usb

Link to comment
Share on other sites

Thank you for everything your kernel works awesome I'm just curious why the bronya kernel works with fsb=200 and not without,I think he should look at your kernel to see the difference's in your kernel and he's kernel.

I can fix this and is will work 100 % ! But i did other metod and should works correct is how original kernel intel , but i getting interesting problem )))

  • Like 1
Link to comment
Share on other sites

I do not know what change has Gils made to its system to boot with bronya's kernel. With or without driver package from carlo_67?... or using clover bootloader? ....?

he should describe now, how-to, so that you can boot your system.

because Bronya does not build the kernel for the first time, he knows what he's doing.

Link to comment
Share on other sites

@Bronya, 

can it may possibly to be related the BIOS settings: "VT-X" Enabled or Disabled are the cause.?

Link to comment
Share on other sites

I read a post that may be in connection with opcode error, if the BIOS settings are not set correctly. Therefore, he should first check the BIOS settings.

(which can not hurt to test it, only a few minutes, he needs to test, then we know whether this is the cause or not.)

Link to comment
Share on other sites

@spakk[/size] I am using Bronya's kernel (r2 version),enoch bootloader.It's working with fx 8320 and i didn't change anything.With these kernel flags : kext-dev-mode=1 PCIRootUID=1 npci=0x3000 GraphicsEnabler=No UserKernelCache=No UsbBusFix=Yes ---> my system works perfectly.

 

You had the same issue that I'm having I try the 2nd kernEl and still the same what did you do different ?

  • Like 1
Link to comment
Share on other sites

You had the same issue that I'm having I try the 2nd kernEl and still the same what did you do different ?

With r1 i used these kernel flags : -v kext-dev-mode=1 npci=0x3000 UseKernelcache=No GraphicsEnabler=No PCIRootUID=1.It did not work at first (it's going to restart while booting).I added fsb=200 busratio=17 flags with macdrive pro 9 from windows.After that i boot my yosemite with -x and it worked. Now i am using kernel r2 and boot file without fsb=200 busratio=17 flags.It's working :)

 

Edit:Please make disk permission verify with disk utility app and boot with -x fsb=200 busratio=17 at first boot,it must works 

  • Like 2
Link to comment
Share on other sites

 Share

×
×
  • Create New...