Jump to content

Private alpha test of Voodoo 9.5 Kernel


mercurysquad
 Share

214 posts in this topic

Recommended Posts

So what will be noticeable differences between the alpha 11 kernel and the beta 1 kernel?

 

Also what will be incorporated/improved on in future kernels?

 

There will be little noticeable difference for most users between the latest alpha and the first beta. The beta will be up when we have fixed all current known bugs and the kernel works on most target systems. There will be comprehensive beta test procedure (will be put online) and debug procedure which all testers should follow. Then we'll iron out any remaining bugs which pop out before the final is released. There could be more than one beta.

 

As for future work - check the IM frontpage for big announcement regarding AMD! There are more goodies to come in the future but at this stage we are only concentrating on bug fixes as the feature list is complete for now.

Link to comment
Share on other sites

Sorry guys, those who downloaded alpha 12 in the past 2 hour or so -- I accidentally uploaded the wrong version! :)

 

I have uploaded the correct version now on googlecode, but renamed it alpha 13 just to avoid confusion.

 

Please test this, specially AMD Athlon/Phenom users. Thanks.

Download Alpha 13

 

NOTE: fsb=xx option is always specified in Hz, not MHz!

Link to comment
Share on other sites

I have been running fine on Alpha 11:

Rainbow:~ lrh$ uname -a
Darwin Rainbow 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 24 03:22:36 IST 2008; Voodoo; based on ToH:xnu-1228.7.58/BUILD/obj/RELEASE_I386 i386

 

However, when I try to use Alpha 12 the system finishes the loading messages and then re-boots. I see messages about the cpu and multiplier 15 and a few other things all of which flash too fast for me to copy them. Then the screen blanks and the system re-boots.

 

Under Alpha 11 I see the same messages about cpu, multiplier etc.. The screen blanks. But then the process continues with messages from natit e.t.all and the system runs.

 

Sorry I can't give more info. I have tried dmesg, but that only has the current messages starting sometime after the loading messages.

Link to comment
Share on other sites

Well, Alpha12 worked for me :rolleyes:

 

Running Alpha13 now, i'm curious if this kernel solves the AMD timing problems, i've been running with cpus=1 for a while now, otherwise i would get the "jumpy mouse cursor" problem after a while, which is unworkable.

 

Is there anything wrong with putting busratio=13 and fsb=200000000 in com.apple.Boot.plist? I believe you are aiming for an autodetecting kernel so it's not neccesary, but it doesn't really have disadvantages right?

Link to comment
Share on other sites

Well, Alpha12 worked for me :)

 

Running Alpha13 now, i'm curious if this kernel solves the AMD timing problems, i've been running with cpus=1 for a while now, otherwise i would get the "jumpy mouse cursor" problem after a while, which is unworkable.

 

Is there anything wrong with putting busratio=13 and fsb=200000000 in com.apple.Boot.plist? I believe you are aiming for an autodetecting kernel so it's not neccesary, but it doesn't really have disadvantages right?

 

Actually hardcoding fsb and busratio is not recommended. The system clock is very sensitive to fsb, and it is most often not a nice rounded number like 200000000. On my system for example, it's something like 133798012 Hz instead of 133000000. And this can in some cases change by a little every time you boot. So let the fsb freq be auto-detected.

 

The busratio can be hardcoded though, but again, let it be autodetected if it works for you. Only use the workarounds if the autodetect doesn't work.

 

As for timing issues and cpus=1, this kernel *should* fix those. Try booting without cpus=1 and see if it works. This kernel includes tsc sync patch which might help. Once again, I don't have a multicore or an amd cpu so I can't test this myself.

Link to comment
Share on other sites

ok, first off I would like to thank you very much for your hard work.

 

now, I am including 2 files with this post, one from using the modbin kernel 9.4.0 and one from using your voodoo_alpha13 kernel.

 

 

both seem to run almost everything I have fine, except for system profiler (alpha13 does not run profiler at all).

SYSLog from sysprofiler crash

9/24/08 6:36:02 PM com.apple.launchd[573] ([0x0-0x1b01b].com.apple.SystemProfiler[989]) Exited abnormally: Floating point exception

9/24/08 6:37:03 PM com.apple.launchd[573] ([0x0-0x1d01d].com.apple.SystemProfiler[1039]) Exited abnormally: Floating point exception

All programs run without crashing with modbin9.4.0

included the crash report from system profiler

 

 

my Specs are as follows

ECS 945G-M3 board with a Intel® Pentium® D CPU 3.00GHz

2 gig DDR2 ram @ 533

1 nvidia 8600gt 256 model

and allot of drives.

booting off of normal running system is Raid using chameleon

 

with alpha13 I can Sleep, with modbin I can not ;(

 

the CPUID logs are at the end of the log reports you asked for.

 

I would rather use your kernel when it is fulling running due to having sleep and NX :)

Keep up the Great work.

I'll keep an eye out for fixes.

HBP112358

CPUID_Log.alpha13.txt

CPUID_Log.modbin9.4.0.txt

System_Profiler_2008_09_24_191721_Macintosh.crash.txt

Link to comment
Share on other sites

I just installed Alpha 13 - it boots and all appears well at this time.

Rainbow:~ lrh$ uname -a
Darwin Rainbow 9.5.0 Darwin Kernel Version 9.5.0: Thu Sep 25 05:59:23 IST 2008; Voodoo; based on ToH:xnu-1228.7.58/BUILD/obj/RELEASE_I386 i386

 

My WinXP under Parallels appears to be running correctly.

System Profiler appears happy providing hardware, graphics and extension information.

Hardware Overview:

 Model Name:	Mac
 Model Identifier:	8183XXD
 Processor Speed:	3 GHz
 Number Of Processors:	1
 Total Number Of Cores:	1
 L2 Cache:	512 KB
 Memory:	2 GB
 Bus Speed:	400 MHz
 Boot ROM Version:	BOOT.EFI.V80
 Serial Number:	CK157KMHK5B

 

One thing I don't understand (well, there are many things) is where the Boot Rom Version value is getting set. Back when I was using EFI strings I set that value in the strings. Since I started using the Munky EFI boot partition I removed the efi strings and installed natit. I also reverted to the vanilla System.kext.

 

Still, the Boot Rom and L2 cache values remain as they have been for a long time. ????

 

Probably my imagination, but it appears faster than when running the 9.4 modbin kernel.

Link to comment
Share on other sites

System Profiler says "L2 Cache (per processor): 1 MB". I assume that it actually means "per core", otherwise it would be incorrect. The Toledo/Denmark chips have 1MB cache per core for 2MB total. I attached my cpuid_log for reference.

 

Otherwise everything seems to run totally fine with 2 cores enabled. No more timing issues so far!

The only bootflag in use now is cpus=2, which probably isn't even necessary.

 

Thanks again to the entire team for all the time and effort spend! :thumbsup_anim:

 

Now we just need powernow/cool'n'quiet support and everybody's happy. :)

CPUID_Log.txt

Link to comment
Share on other sites

9/24/08 6:36:02 PM com.apple.launchd[573] ([0x0-0x1b01b].com.apple.SystemProfiler[989]) Exited abnormally: Floating point exception

HBP112358

 

 

Thanks for the GREAT bug report - bug has been identified and fix will appear in the beta which will be out soon.

Link to comment
Share on other sites

don't know if this is an issue related with the proyect, but since I started testing these kernels it seems that the screensaver and the screen sleep functions (can't remember how it's called in english) are not working anymore. If I leave the pc inactive for a while it won't start the screensaver or sleep, but if I call the function from expose it works just fine.

Link to comment
Share on other sites

System Profiler says "L2 Cache (per processor): 1 MB". I assume that it actually means "per core", otherwise it would be incorrect. The Toledo/Denmark chips have 1MB cache per core for 2MB total. I attached my cpuid_log for reference.

 

Otherwise everything seems to run totally fine with 2 cores enabled. No more timing issues so far!

The only bootflag in use now is cpus=2, which probably isn't even necessary.

 

Thanks again to the entire team for all the time and effort spend! :thumbsup_anim:

 

Now we just need powernow/cool'n'quiet support and everybody's happy. :)

 

Cool'n'quiet support will come in my speedstep kext, just been busy with kernel now.

 

As for the cache - it is per-core. I'll change it to total cache if that's what's supposed to be displayed? I have a single core CPU so I have no clue what it's supposed to say. The processor reports cache size per-core, though.

 

Also, I recommend you to boot without any flag. I noticed your cpuid log says you have 2 physical cpus!

Link to comment
Share on other sites

Alpha 13

With no boot flags (except maxmem=2048 -v) success.

 

a11

Sep 24 19:41:42 localhost kernel[0]: rtclock_init: Taking bus ratio path 0 (Boot-time argument)

Sep 24 19:41:42 localhost kernel[0]: TSC: Frequency = 2200.0000MHz, bus frequency = 200.0000MHz, multiplier = 11

Sep 24 19:41:42 localhost kernel[0]: Darwin Kernel Version 9.5.0: Wed Sep 24 03:22:36 IST 2008; Voodoo; based on ToH:xnu-1228.7.58/BUILD/obj/RELEASE_I386

 

a13

Sep 25 07:11:28 localhost kernel[0]: rtclock_init: Taking bus ratio path 3 (AMD Phenom)

Sep 25 07:11:28 localhost kernel[0]: rtclock_init: Phenom MSR 0xc0010071 returned: 0x30003806

Sep 25 07:11:28 localhost kernel[0]: TSC: Frequency = 2160.930508MHz, bus frequency = 98.224114MHz, multiplier = 22

Sep 25 07:11:28 localhost kernel[0]: Darwin Kernel Version 9.5.0: Thu Sep 25 05:59:23 IST 2008; Voodoo; based on ToH:xnu-1228.7.58/BUILD/obj/RELEASE_I386

 

a13

hw.packages: 1

hw.tbfrequency: 1000000000

hw.l3cachesize: 2097152

hw.l2cachesize: 524288

hw.l1dcachesize: 64

hw.l1icachesize: 64

hw.cachelinesize: 64

hw.cpufrequency_max: 2200000000

hw.cpufrequency_min: 2200000000

hw.cpufrequency: 2200000000

hw.busfrequency_max: 200000000

hw.busfrequency_min: 200000000

hw.busfrequency: 200000000

hw.pagesize: 4096

hw.cachesize: 2147483648 64 524288 2097152 0 0 0 0 0 0

hw.cacheconfig: 4 1 1 4 0 0 0 0 0 0

 

Cache info above is now correct.

 

Sound etc... All good.

 

Announcing on-the-fly opcode patching!

 

Thanks to great work done by kaitek, we are pleased to announce that Voodoo kernel will include an on-the-fly cpuid/opcode patcher. This will bridge the divide between intel and AMD users, as it nullifies the need to patch any binaries for AMD.

 

Excellent news. :thumbsup_anim:

Link to comment
Share on other sites

Without the Boot flags, kernel panic and writes:

 

TSC: Fregency = 2204.9755115MHz bus fregency = 209.997630 MHz multiplier = 10.5

 

Hi can you also post, when it panics, on screen you should see "Taking bus ratio path X" - can you post which path it is taking?

 

Alpha 13

With no boot flags (except maxmem=2048 -v) success.

 

Sep 24 19:41:42 localhost kernel[0]: rtclock_init: Taking bus ratio path 0 (Boot-time argument)

Sep 24 19:41:42 localhost kernel[0]: TSC: Frequency = 2200.0000MHz, bus frequency = 200.0000MHz, multiplier = 11

Sep 24 19:41:42 localhost kernel[0]: Darwin Kernel Version 9.5.0: Wed Sep 24 03:22:36 IST 2008; Voodoo; based on ToH:xnu-1228.7.58/BUILD/obj/RELEASE_I386

 

Sound etc... All good.

 

Are you sure this is with no bootflags except maxmem and -v?

The rtclock_init says "Taking bus ratio path 0 (Boot-time argument)" !

This will only appear if you specify busratio=xx option.

 

Also, your kernel timestamp says 03:22:36 IST -- for alpha 13 this should be 05:59:23 IST.

Check md5: a645413c43e6d315ff69e45279f7a9a3

Link to comment
Share on other sites

mercurysquad, any Hope for older xnu Versions?

 

YES!

Dense's black magic will bring Voodoo features to base kernels from 9.0 to 9.5 -- all Leopard kernels will be available.

 

But these will be provided only as a service and main focus will still be 9.5 (or the next latest) kernel. Beta test will also only be for 9.5.

 

Note that you can run kernel 9.5 on almost *any* version of Leopard (as long as you have a System.kext from 10.5.5), so no one really needs to run an older version. The main development of 9.5 kernel is being done on a leopard 10.5.1 system!

 

Tiger kernels are not supported.

Link to comment
Share on other sites

 Share

×
×
  • Create New...