Jump to content

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


Duran Keeley
 Share

1,948 posts in this topic

Recommended Posts

:thanks_speechbubble:

:afro:  @Gils83

 

look  :w00t:  :hysterical:             #20            

the Pentium's folies  !!! at 2 € 

Looking good with Bronya's kernel on legacy Intel Paxville dual-core Xeon  :)

 

It's booting the installer and appears willing to install Yosemite (on non-AHCI SATA I disks)! :D Sleep & Wake even work in the installer!!! :D :D :D

 

attachicon.gifP1020894.JPG attachicon.gifP1020895.JPG attachicon.gifP1020896.JPG

attachicon.gifP1020897.JPG attachicon.gifP1020898.JPG

 

Graphics appear buggy but, hey, it's a start! Congrats guys, this definitely deserves a little € contribution from my part...

woooh !!! good :)

 

HDD fail ? 

  • Like 1

Hey guys, I got the App store to work with a trick. 
launch the appstore, click on update really fast before it tries to load the main page. then you can use the search function to go to apps and install them.
I even got the main page to work once.

 

This is the log from when you try to use the appstore.

11/10/14 7:38:22.474 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc5844239b0> connection from pid 9901 with interface <AccountServiceInterface: 0x7fc581e202c0> (PID 9901)
11/10/14 7:38:22.492 PM App Store[9901]: Unknown class 'FRPageController', using 'NSObject' instead. Encountered in Interface Builder file at path /System/Library/PrivateFrameworks/StoreUI.framework/Resources/Base.lproj/FRStoreViewController.nib.
11/10/14 7:38:22.493 PM App Store[9901]: Failed to connect (delegate) outlet from (NSObject) to (FRNavigationController): missing setter or instance variable
11/10/14 7:38:22.493 PM App Store[9901]: Failed to connect (view) outlet from (NSObject) to (FRWindowBackgroundView): missing setter or instance variable
11/10/14 7:38:22.493 PM App Store[9901]: Failed to connect (pageController) outlet from (FRNavigationController) to (NSObject): missing setter or instance variable
11/10/14 7:38:22.508 PM storeassetd[9760]: AssetServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f836ad89870> connection from pid 9901 with interface <AssetServiceInterface: 0x7f836ad93000> (PID 9901)
11/10/14 7:38:22.538 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc5842cc580> connection from pid 9901 with interface <AccountServiceInterface: 0x7fc581e1f050> (PID 9901)
11/10/14 7:38:22.589 PM App Store[9901]: NSWindow warning: adding an unknown subview: <_NSThemeCloseWidget: 0x61000018f2f0>
11/10/14 7:38:22.592 PM App Store[9901]: Call stack:
(
0   AppKit                              0x00007fff8f62cb3c -[NSThemeFrame addSubview:] + 107
1   AppKit                              0x00007fff8f01bb8f -[NSView addSubview:positioned:relativeTo:] + 208
2   StoreUI                             0x000000010a9a613a -[FRWindow handleToolbarViewChangedNotification:] + 1085
3   CoreFoundation                      0x00007fff91120cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
4   CoreFoundation                      0x00007fff910121b4 _CFXNotificationPost + 3140
5   AppKit                              0x00007fff8ef97ad9 -[NSView _postFrameChangeNotification] + 422
6   AppKit                              0x00007fff8ef96ae6 -[NSView setFrameOrigin:] + 862
7   StoreUI                             0x000000010a9a5fc0 -[FRWindow handleToolbarViewChangedNotification:] + 707
8   StoreUI                             0x000000010a9a5b54 -[FRWindow setToolbar:] + 183
9   App Store                           0x000000010a97215f App Store + 8543
10  AppKit                              0x00007fff8f1ad637 -[NSWindowController _windowDidLoad] + 586
11  AppKit                              0x00007fff8f1947f2 -[NSWindowController window] + 110
12  App Store                           0x000000010a9719d8 App Store + 6616
13  CoreFoundation                      0x00007fff91120cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
14  CoreFoundation                      0x00007fff910121b4 _CFXNotificationPost + 3140
15  Foundation                          0x00007fff88eb2ea1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
16  AppKit                              0x00007fff8ef5f2d7 -[NSApplication finishLaunching] + 440
17  AppKit                              0x00007fff8ef5eda1 -[NSApplication run] + 128
18  AppKit                              0x00007fff8ef4a424 NSApplicationMain + 1832
19  libdyld.dylib                       0x00007fff8a3025c9 start + 1
20  ???                                 0x0000000000000001 0x0 + 1
)
11/10/14 7:38:22.777 PM storeassetd[9760]: addOperation <LoadUpdateQueueOperation: 0x7f836afa6640>{name = '(null)'}
11/10/14 7:38:22.779 PM storeuid[1569]: UIServiceDelegate: Accepting new connection <NSXPCConnection: 0x7ffebbd22630> connection from pid 9901 with interface <UIServiceInterface: 0x7ffebbd22a60> (PID 9901)
11/10/14 7:38:22.780 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc58442f500> connection from pid 9760 with interface <AccountServiceInterface: 0x7fc584409210> (PID 9760)
11/10/14 7:38:22.000 PM kernel[0]: BUG in process suhelperd[9756]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external)
11/10/14 7:38:22.815 PM storeassetd[9760]: AssetServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f836af99a30> connection from pid 9901 with interface <AssetServiceInterface: 0x7f836af94a00> (PID 9901)
11/10/14 7:38:22.819 PM storeassetd[9760]: addOperation <AdoptionEligibilityCheckOperation: 0x7f836aead350>{name = '(null)'}
11/10/14 7:38:22.819 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc584524780> connection from pid 9760 with interface <AccountServiceInterface: 0x7fc584516790> (PID 9760)
11/10/14 7:38:22.826 PM com.apple.CommerceKit.TransactionService[9761]: TransactionServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fbf60d734f0> connection from pid 9760 with interface <TransactionServiceInterface: 0x7fbf60d736c0> (PID 9760)
11/10/14 7:38:22.825 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc58470c6e0> connection from pid 9760 with interface <AccountServiceInterface: 0x7fc5842cbef0> (PID 9760)
11/10/14 7:38:22.832 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc584439560> connection from pid 9761 with interface <AccountServiceInterface: 0x7fc584408bf0> (PID 9761)
11/10/14 7:38:22.835 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc58451e770> connection from pid 9903 with interface <AccountServiceInterface: 0x7fc58451ed40> (PID 9903)
11/10/14 7:38:22.838 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc581fe6870> connection from pid 9903 with interface <AccountServiceInterface: 0x7fc5843ebbb0> (PID 9903)
11/10/14 7:38:22.842 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc58440d250> connection from pid 9760 with interface <AccountServiceInterface: 0x7fc5842cb8d0> (PID 9760)
11/10/14 7:38:22.845 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc58451f1c0> connection from pid 9903 with interface <AccountServiceInterface: 0x7fc584526290> (PID 9903)
11/10/14 7:38:22.855 PM com.apple.CommerceKit.TransactionService[9761]: TransactionServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fbf60f59010> connection from pid 9760 with interface <TransactionServiceInterface: 0x7fbf60f5ab00> (PID 9760)
11/10/14 7:38:22.863 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc58470aff0> connection from pid 9761 with interface <AccountServiceInterface: 0x7fc58470dae0> (PID 9761)
11/10/14 7:38:22.878 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc5847106a0> connection from pid 9760 with interface <AccountServiceInterface: 0x7fc58440c600> (PID 9760)
11/10/14 7:38:23.779 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc58470f510> connection from pid 9901 with interface <AccountServiceInterface: 0x7fc58470c3b0> (PID 9901)
11/10/14 7:38:23.780 PM storeaccountd[293]: -[PushServiceStoreDispatch getEnabledMediaTypesWithReply:]
11/10/14 7:38:23.780 PM storeaccountd[293]: addOperation <ISStoreURLOperation: 0x7fc5843f0f00 - request=<ISURLRequest:0x7fc584603da0 (null)> urlBagKey=enabled-media-types>
11/10/14 7:38:23.782 PM com.apple.CommerceKit.TransactionService[9754]: TransactionServiceDelegate: Accepting new connection <NSXPCConnection: 0x7f89f14167a0> connection from pid 293 with interface <TransactionServiceInterface: 0x7f89f14169c0> (PID 293)
11/10/14 7:38:23.784 PM storeaccountd[293]: AccountServiceDelegate: Accepting new connection <NSXPCConnection: 0x7fc584603e30> connection from pid 9754 with interface <AccountServiceInterface: 0x7fc5843f4c70> (PID 9754)

post-1147257-0-63972300-1415740157_thumb.jpgpost-1147257-0-89266000-1415740326_thumb.jpg

  • Like 1

The App Store & Safari are crashing because of WebKit, to be specific the JavaScript. libllvmForJSC.dylib in the JavaScriptCore.framework (in the nightly build of WebKit). Most likely when Apple added LLVM to their JavaScript engine Nitro (just a theory).

 

This is kernel related.

  • Like 1

Interesting.

 

Does it (or do they, but Safari seems to be working here, since I access Netflix from it here) crash with FX CPUs? That's the question we all must have answered from testers at the moment. If the bug is restricted to old CPUs, it's not only kernel related, but opemu related as well.

 

All the best!

  • Like 1

 

 

Interesting.

 

Does it (or do they, but Safari seems to be working here, since I access Netflix from it here) crash with FX CPUs? That's the question we all must have answered from testers at the moment. If the bug is restricted to old CPUs, it's not only kernel related, but opemu related as well.

 

All the best!

 

 

Hey theconnactic

 

Can you try the icloud.com website and see if it crashes on your side.

Agreed, if we can get some FX CPU testers to give it a try (icloud.com seems to be the biggie when it comes to crashing the JS) and also some users to try the nightly builds of WebKit: http://nightly.webkit.org/

 

EDIT: theconnactic, up for help building WebKit from source?

 

EDIT 2: Moved our conversation over to the General Chat, Questions & Answers


 

AMD Athlon Bug
amd-1010-bug.jpg
 

 

This..

I have the same problem but I'm running an AMD Phenom X4 955 and AMD Radeon 5770. It presents itself exactly as shown in the screenshot. Also I noticed that Icons are only selectable at all times if I click the text underneath them, which I'm guessing is related. 

 

That said, impressed with the general performance.


First of all, thank you guys!

 

Just for registering, the Bronya 10.10 Kernel RC1 worked fine in my (very) old Acer Aspire 5050 (AMD Turion [Athlon x1 CPU]) with little glitches and artifacts, as early mentioned by Bronya.

 

Using [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] installer, added the Bronya kernel and SuperVIAATA.kext to the USB drive installer and HD installation drive (post-install). Note: in my machines, I use no HD boot files, so boot always from the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] prepared USB drive, that means, no "local" chimera or other HD installed bootloader, also no boot flags in org.chameleon,bootloader.plis or smbios.plist. I want keep it that way unless the installation/machine ask for a change (maybe this is time!)

 

Of course, have no QE/CI as there is no driver solution for my ATI x1100 graphics in this OSX version. No such a problem while using the machine for internet and mail apps only.

Changed the original wifi card for a compatible Broadcom, so at least got wireless internet.

Still, no audio, bluetooth, card reader, etc... working on it.

 

I got OSX working on that machine only with Mavericks and, now, Yosemite Bronya kernels, tried SL, Lion but not succeeded. Hope it helps someone!


Well, the installation went through, however I'm booting to a set of white screens which reminds me of what I encountered with post-10.9.1 updates until AppleACPIPlatform + IOPCIFamily kexts were replaced by 10.9.1's versions.

 

So, for the moment, I can only reach Yosemite desktop if booting with nv_disable=1 Chameleon option which leads me to a very poor unaccelerated 10.10 system.

  • Like 1

Well, the installation went through, however I'm booting to a set of white screens which reminds me of what I encountered with post-10.9.1 updates until AppleACPIPlatform + IOPCIFamily kexts were replaced by 10.9.1's versions.

 

So, for the moment, I can only reach Yosemite desktop if booting with nv_disable=1 Chameleon option which leads me to a very poor unaccelerated 10.10 system.

 

tu es dieux le père !!! j'aurais jamais cru que ça marche !!!  :yoji:

 

seulement , il y a beaucoup de kext à remplacer  qui dépendent de ACPIPlaform Mavericks , impressionnant , je vais faire un mkext de ceux ML 10.9 (13A603) 

 

Merci hervé ;)

 

 

you are the father gods !!! I never thought that it works !!!     :yoji:

 
only, there is a lot of kext to replace dependent ACPIPlaform Mavericks, awesome, I'll make a mkext those ML 10.9 (13A603)
 
Herve thank you  ;)

post-1093405-0-75342400-1415835690_thumb.png


In addition to the graphical glitches I'm seeing my kernel log is also spammed with the following entries

opemu error: high reg ssse

 

Anyone know what's causing this or whether it's important?


Maybe is high-reg-ssse not included in the kernel .... Bronya can you check it please? One user in German osx forum has the same problem.


Hi !

Please see have or no have "nigh reg sse3".

Fix glitches on Desktop ...

In archive two files kernel with name folders "1" or "2", because in 1 kernel with opemu , in  2 kernel with sinetek opemu .

attachicon.gifkernel_10.10.rc2.zip

many thanks for the the new kernel, Bronya

unfortunately I can not test today. Tomorrow I will test the kernel and report.


I will test i have tried the first one and had a prob where i could only open files by clicking there name in icon view i will test and report if the problem persists.


Alright, so it seems I'm back with similar situation as with post-10.9.1 Mavericks: unable to get full QE/CI with MacPro3,1 profile on the GeForce 9800GT...
 
Once again, changing profile to MBP5,1 SMBIOS got me to desktop with some form of QE/CI but significant overall lagging. Dual display is functional, GPU core & RAM frequencies are reported Ok, full resolution switching is available and LCD displays are properly detected. The attached screenshots are self explanatory (sorry for degraded quality but that's an old known side effect of AMD kernels).
post-851564-0-18522200-1415928938_thumb.png post-851564-0-37227000-1415923981_thumb.png post-851564-0-17274900-1415923996_thumb.png
 
iMac8,1 SMBIOS (and others) leads me to dual white screens, same as with post-10.9.1 Mavericks updates initially. 
 
Solution is again likely to be IOPCIFamily related... Getting there, getting there...
 
Edit #1: I confirm that graphics glitches are gone with 10.10 RC2. Thanks Bronya!
 
Edit #2: 'seems QE/CI issue is fixed for MP3,1 profile with axmanA's IOPCIFamily kext (yes, him again, as per Mavericks! Thanks man!) + boot option msibase=0x90:thumbsup_anim:


RC2 #1 does allow me to take screenshots with CMD-SHIFT-3/CMD-SHIFT-4 (with old known bug), something that RC2 #2 does not permit (returns above error message all the time, i.e. "Your screen shot can't be saved. Failure to write image data."). Sticking to RC2 #1 as a result.

 

Changing desktop wallpaper appears very buggy with both kernels, the resulting screen background being usually totally corrupt.

 

I've also noticed that icon selection or icon double clicking has to be done at or very near icon's name. Double clicking the top half of a folder icon does not open it for instance. I have to click much lower than usual.

  • Like 1

Here on an athlon II X4 620

 

with the bronya's rc2 kernel (with bronya's opemu) almost all graphical glitches are gone (launchpad, mouse), but some icons and apps corners still have them.

-The opemu error (high reg ssse ) on the console vanished as well.

-Safari and appstore are totally broken, much more than before.

 

Much better than rc1!!!

Congrats and thank you!


RC2 #1 does allow me to do screenshots with CMD-SHIFT-3/CMD-SHIFT-4 (with old known bug), something that RC2 #2 does not permit (returns above error message all the time, i.e. "Your screen shot can't be saved. Failure to write image data.").

 

Changing desktop wallpaper appears very buggy with both kernels, the resulting screen background being usually totally corrupt.

change the screenshot format to BMP.

 

Here on an athlon II X4 620

 

with the bronya's rc2 kernel (with bronya's opemu) almost all graphical glitches are gone (launchpad, mouse), but some icons and apps corners still have them.

-The opemu error (high reg ssse ) on the console vanished as well.

-Safari and appstore are totally broken, much more than before.

 

Much better than rc1!!!

Congrats and thank you!

check out the fix for the app store and safari Duran poster earlier.

Found Here: http://www.insanelymac.com/forum/topic/295176-amd-general-chat-questions-answers/page-6?p=2084311&do=findComment&comment=2084311

 

:)

 

Hello Bronya ,

 

kernel1 is better of kernel2 :)

 

look vidéo :)

 

sempron_kernel1.mp4.zip

 

is rendering in iMovie/final cut working for you? was screenflow rendering working for you with old kernel?

 

I cant test the kernels yet, my house has no power :(


I meant with the safari and appstore fix already applied :(

I tested with the old webkit frameworks and the original ones, both give no chance of even load google.com (With rc1 kernel the fix does work tough)


I meant with the safari and appstore fix already applied :(

I tested with the old webkit frameworks and the original ones, both give no chance of even load google.com (With rc1 kernel the fix does work tough)

 

that sucks :( 


 Share

×
×
  • Create New...