Jump to content

Mavericks kernel testing on AMD (formerly Mountain Lion kernel testing on AMD)


theconnactic
 Share

6,414 posts in this topic

Recommended Posts

Will do,, I may take a bit.. hopefully not :)

 

maybe your right, I have mavericks on extended mbr partition... wiill do stand alone guid w/ clover


I might take a bit I gotta do it to USB its all I've got...

 


Ok I tried:

 

Updated .

I delete amdtlbfix and fixed cpuid.c .

Try !

attachicon.gifmach_RC5_with_SECURE_test.zip

 

and the one you in msg no go blackscreen, I will continue transfering to drive.


I did get this however at kextload from drive:

 

post-513502-0-36316700-1383361073_thumb.jpg

 

where graphics properties go.. from test kernl

 

clearer pic test1:

 

 

post-513502-0-11292200-1383362136_thumb.jpg

Link to comment
Share on other sites

Updated .

I delete amdtlbfix and fixed cpuid.c .

Try !

attachicon.gifmach_RC5_with_SECURE_test.zip

 

Trying to boot a mavericks installer created with myHack, panics. (note: using an AMD cpu without SSSE3 support)

Can't take a pic, so i'll just type it out

 

panic(cpu 0 caller 0xffffff800002e0074): "tsc_init: EFI not supported!\n"@/Users/iMac/Desktop/xnu-2422.1.72_rc5/osfmk/i386/tsc.c:650

Debugger called: <panic>

Backtrace (CPU 0), Frame : Return Address

0xffffff000010beb0 : 0xffffff0000222f79

0xffffff000010bf30 : 0xffffff00002e0074

0xffffff000010bf90 : 0xffffff00002d2e37

0xffffff000010bff0 : 0xffffff00002d7d98

can't perform kext scan: no kext memory

BSD process name corresponding to current thread: Unknown

Boot args: boot-uuid=<UUID here> rd=*uuid -v GraphicsEnabler=no busratio=14

 

EDIT: yep, my busratio is 1! /s

Link to comment
Share on other sites

Trying to boot a mavericks installer created with myHack, panics. (note: using an AMD cpu without SSSE3 support)

Can't take a pic, so i'll just type it out

 

panic(cpu 0 caller 0xffffff800002e0074): "tsc_init: EFI not supported!\n"@/Users/iMac/Desktop/xnu-2422.1.72_rc5/osfmk/i386/tsc.c:650

Debugger called: <panic>

Backtrace (CPU 0), Frame : Return Address

0xffffff000010beb0 : 0xffffff0000222f79

0xffffff000010bf30 : 0xffffff00002e0074

0xffffff000010bf90 : 0xffffff00002d2e37

0xffffff000010bff0 : 0xffffff00002d7d98

can't perform kext scan: no kext memory

BSD process name corresponding to current thread: Unknown

Boot args: boot-uuid=<UUID here> rd=*uuid -v GraphicsEnabler=no busratio=14

 

EDIT: yep, my busratio is 1! /s

What your cpu processor ???

Link to comment
Share on other sites

void
ml_cpu_get_info(ml_cpu_info_t *cpu_infop)
{
	boolean_t	os_supports_sse;
	i386_cpu_info_t *cpuid_infop;

	if (cpu_infop == NULL)
		return;
 
	/*
	 * Are we supporting MMX/SSE/SSE2/SSE3?
	 * As distinct from whether the cpu has these capabilities.
	 */
	os_supports_sse = !!(get_cr4() & CR4_OSXMM);

	if (ml_fpu_avx_enabled())
		cpu_infop->vector_unit = 9;
	else if ((cpuid_features() & CPUID_FEATURE_SSE4_2) && os_supports_sse)
		cpu_infop->vector_unit = 8;
	else if ((cpuid_features() & CPUID_FEATURE_SSE4_1) && os_supports_sse)
		cpu_infop->vector_unit = 7;
	else if ((cpuid_features() & CPUID_FEATURE_SSSE3) && os_supports_sse)
		cpu_infop->vector_unit = 6;
	else if ((cpuid_features() & CPUID_FEATURE_SSE3) && os_supports_sse)
		cpu_infop->vector_unit = 5;
	else if ((cpuid_features() & CPUID_FEATURE_SSE2) && os_supports_sse)
		cpu_infop->vector_unit = 4;
	else if ((cpuid_features() & CPUID_FEATURE_SSE) && os_supports_sse)
		cpu_infop->vector_unit = 3;
	else if (cpuid_features() & CPUID_FEATURE_MMX)
		cpu_infop->vector_unit = 2;
	else
		cpu_infop->vector_unit = 0;

	cpuid_infop  = cpuid_info();

	cpu_infop->cache_line_size = cpuid_infop->cache_linesize; 

	cpu_infop->l1_icache_size = cpuid_infop->cache_size[L1I];
	cpu_infop->l1_dcache_size = cpuid_infop->cache_size[L1D];
  
        if (cpuid_infop->cache_size[L2U] > 0) {
            cpu_infop->l2_settings = 1;
            cpu_infop->l2_cache_size = cpuid_infop->cache_size[L2U];
        } else {
            cpu_infop->l2_settings = 0;
            cpu_infop->l2_cache_size = 0xFFFFFFFF;
        }

        if (cpuid_infop->cache_size[L3U] > 0) {
            cpu_infop->l3_settings = 1;
            cpu_infop->l3_cache_size = cpuid_infop->cache_size[L3U];
        } else {
            cpu_infop->l3_settings = 0;
            cpu_infop->l3_cache_size = 0xFFFFFFFF;
        }
}

vector unit??? there's a dylib for vector acceleration... machine_routines.c 

  • Like 2
Link to comment
Share on other sites

@andy,I use your RC5,and working good! But cannot qe/ci! My card is hd7750,and 10.9 support my card. I can open qe/ci on 10.8.3. So,maybe reason is your kernel?

sorry my English!

Thank you!

@andy,I use your RC5,and working good! But cannot qe/ci! My card is hd7750,and 10.9 support my card. I can open qe/ci on 10.8.3. So,maybe reason is your kernel?

sorry my English!

Thank you!

Link to comment
Share on other sites

it is my kernel ?

yes it is from your kernel and also from all other kernels here

void
ml_cpu_get_info(ml_cpu_info_t *cpu_infop)
{
	boolean_t	os_supports_sse;
	i386_cpu_info_t *cpuid_infop;

	if (cpu_infop == NULL)
		return;
 
	/*
	 * Are we supporting MMX/SSE/SSE2/SSE3?
	 * As distinct from whether the cpu has these capabilities.
	 */
	os_supports_sse = !!(get_cr4() & CR4_OSXMM);

	if (ml_fpu_avx_enabled())
		cpu_infop->vector_unit = 9;
	else if ((cpuid_features() & CPUID_FEATURE_SSE4_2) && os_supports_sse)
		cpu_infop->vector_unit = 8;
	else if ((cpuid_features() & CPUID_FEATURE_SSE4_1) && os_supports_sse)
		cpu_infop->vector_unit = 7;
	else if ((cpuid_features() & CPUID_FEATURE_SSSE3) && os_supports_sse)
		cpu_infop->vector_unit = 6;
	else if ((cpuid_features() & CPUID_FEATURE_SSE3) && os_supports_sse)
		cpu_infop->vector_unit = 5;
	else if ((cpuid_features() & CPUID_FEATURE_SSE2) && os_supports_sse)
		cpu_infop->vector_unit = 4;
	else if ((cpuid_features() & CPUID_FEATURE_SSE) && os_supports_sse)
		cpu_infop->vector_unit = 3;
	else if (cpuid_features() & CPUID_FEATURE_MMX)
		cpu_infop->vector_unit = 2;
	else
		cpu_infop->vector_unit = 0;

	cpuid_infop  = cpuid_info();

	cpu_infop->cache_line_size = cpuid_infop->cache_linesize; 

	cpu_infop->l1_icache_size = cpuid_infop->cache_size[L1I];
	cpu_infop->l1_dcache_size = cpuid_infop->cache_size[L1D];
  
        if (cpuid_infop->cache_size[L2U] > 0) {
            cpu_infop->l2_settings = 1;
            cpu_infop->l2_cache_size = cpuid_infop->cache_size[L2U];
        } else {
            cpu_infop->l2_settings = 0;
            cpu_infop->l2_cache_size = 0xFFFFFFFF;
        }

        if (cpuid_infop->cache_size[L3U] > 0) {
            cpu_infop->l3_settings = 1;
            cpu_infop->l3_cache_size = cpuid_infop->cache_size[L3U];
        } else {
            cpu_infop->l3_settings = 0;
            cpu_infop->l3_cache_size = 0xFFFFFFFF;
        }
}

vector unit??? there's a dylib for vector acceleration... machine_routines.c 

 

about vector

this plugins prevent illustrator to start don't know if this is related to that or not  :angel:

 

 

Adobe Illustrator CC

Working with workarounds (trash he following plugins)

  • Illustrator Folder -> Plug-in's -> Extensions -> BNPlugin.aip
  • Illustrator Folder -> Plug-in's -> Photoshop Filters -> PSLFilterAdapter.aip
  • Illustrator Folder -> Plug-in's -> Illustrator Formats -> TIFF.aip

installed ilfie iwork 2013

when open imove and press on new trilar   the screen turn off and open  on black screen many time then rest on turn off 

 

i think the problem  on preview and imove affects the stability of gfx card driver and make it to turn off

Link to comment
Share on other sites

Will do,, I may take a bit.. hopefully not :)

 

maybe your right, I have mavericks on extended mbr partition... wiill do stand alone guid w/ clover

 

I might take a bit I gotta do it to USB its all I've got...

 

 

Ok I tried:

 

 

and the one you in msg no go blackscreen, I will continue transfering to drive.

 

I did get this however at kextload from drive:

 

boot.jpg

 

where graphics properties go.. from test kernl

 

clearer pic test1:

Don't use kernelpatcher...

It'll panic the kernel on AMD

 

void
ml_cpu_get_info(ml_cpu_info_t *cpu_infop)
{
	boolean_t	os_supports_sse;
	i386_cpu_info_t *cpuid_infop;

	if (cpu_infop == NULL)
		return;
 
	/*
	 * Are we supporting MMX/SSE/SSE2/SSE3?
	 * As distinct from whether the cpu has these capabilities.
	 */
	os_supports_sse = !!(get_cr4() & CR4_OSXMM);

	if (ml_fpu_avx_enabled())
		cpu_infop->vector_unit = 9;
	else if ((cpuid_features() & CPUID_FEATURE_SSE4_2) && os_supports_sse)
		cpu_infop->vector_unit = 8;
	else if ((cpuid_features() & CPUID_FEATURE_SSE4_1) && os_supports_sse)
		cpu_infop->vector_unit = 7;
	else if ((cpuid_features() & CPUID_FEATURE_SSSE3) && os_supports_sse)
		cpu_infop->vector_unit = 6;
	else if ((cpuid_features() & CPUID_FEATURE_SSE3) && os_supports_sse)
		cpu_infop->vector_unit = 5;
	else if ((cpuid_features() & CPUID_FEATURE_SSE2) && os_supports_sse)
		cpu_infop->vector_unit = 4;
	else if ((cpuid_features() & CPUID_FEATURE_SSE) && os_supports_sse)
		cpu_infop->vector_unit = 3;
	else if (cpuid_features() & CPUID_FEATURE_MMX)
		cpu_infop->vector_unit = 2;
	else
		cpu_infop->vector_unit = 0;

	cpuid_infop  = cpuid_info();

	cpu_infop->cache_line_size = cpuid_infop->cache_linesize; 

	cpu_infop->l1_icache_size = cpuid_infop->cache_size[L1I];
	cpu_infop->l1_dcache_size = cpuid_infop->cache_size[L1D];
  
        if (cpuid_infop->cache_size[L2U] > 0) {
            cpu_infop->l2_settings = 1;
            cpu_infop->l2_cache_size = cpuid_infop->cache_size[L2U];
        } else {
            cpu_infop->l2_settings = 0;
            cpu_infop->l2_cache_size = 0xFFFFFFFF;
        }

        if (cpuid_infop->cache_size[L3U] > 0) {
            cpu_infop->l3_settings = 1;
            cpu_infop->l3_cache_size = cpuid_infop->cache_size[L3U];
        } else {
            cpu_infop->l3_settings = 0;
            cpu_infop->l3_cache_size = 0xFFFFFFFF;
        }
}

vector unit??? there's a dylib for vector acceleration... machine_routines.c
Interesting.

It won't detect the ssse3 emulator as it uses the cpuid_features bits.

This can be patched in cpuid.c by putting the needed bit |=...

Worth investigating... :D

  • Like 2
Link to comment
Share on other sites

@andy,I use your RC5,and working good! But cannot qe/ci! My card is hd7750,and 10.9 support my card. I can open qe/ci on 10.8.3. So,maybe reason is your kernel?

sorry my English!

Thank you!

Odd...

It's not an APU I hope?

Should work if dedicated graphics card.

Normally not the kernel at fault as I also have an ATI Radeon (HD6450 from Asus).

I need to patch the 6000 controller and then it works...

Link to comment
Share on other sites

Yes,my cpu is AthlonIIX2 245.My card id (68bf)is in info.plist of x4000.kext.But ati7000controller.kext don't have the info.plist. It'strange,because ati4000/5000/6000 all have info.plist. My 10.9 is 603,is gm2? And i use chameleon R2255,when -v -f boot,i not see ''load x4000"and "load ati7000" in updating kext.

Link to comment
Share on other sites

Hello guys i get a strange error

opemu error: no rip yet
Screen: -929206895.jpg

 

CPU: AMD Phenom x3 8550

GPU: ATI HD4850 1GB

 

it boots only in safe mode..

Which kernel?

It halts the launchd...

Yes,my cpu is AthlonIIX2 245.My card id (68bf)is in info.plist of x4000.kext.But ati7000controller.kext don't have the info.plist. It'strange,because ati4000/5000/6000 all have info.plist. My 10.9 is 603,is gm2? And i use chameleon R2255,when -v -f boot,i not see ''load x4000"and "load ati7000" in updating kext.

That's the problem right there.

It should have an Info.plist...

Some posts back there is a proper kext.

Link to comment
Share on other sites

@Andy i used latest kernel: http://www.osx86.net/files/file/3631-kernel-os-x-mavericks-109-amd/

 

@Andy after the install the corecrypto kext needs to be in the E/E folder?

 

@Andy I also added my device id on AMD4800Controller kext 0x94421002

1. It's not the latest...

RC5 is latest of me...

2. Kernel doesn't require patched corecrypto

3. Also the IOAccelerator or boot for install without GraphicsEnabler/GraphicsInjector and fix all afterwards.

Link to comment
Share on other sites

I have an idea (and going to implement myself in my own testing): to organize things better, what about a standardized report form?

 

I was thinking about this:

 

- Kernel name and revision;

- Boots (y/n): If doesn't, a screenshot of the verbose output is mandatory;

- Panics (y/n): same as above;

- Artifacts: self-explanatory. Usually screenshots would be inaccurate, so a pic taken with a tablet/mobile phone would do;

- Glitches: programs that malfunction etc: detailed descriptions and screenshots if they apply;

- Crashes: crash reports;

- Miscellaneous: any further info you should add.

 

I think that could help devs to pinpoint issues better.

 

All the best!

  • Like 5
Link to comment
Share on other sites

 Share

×
×
  • Create New...