Voodoo Kernel BETA 2 - Available now

[Detosx]

Guys, though in a sense this is the wrong place to post this, if anyone out there can help me with Chameleon, in relation to voodoo 9.5.0 beta 2c, I would be most grateful.

 

Having googled, I haven't found anyone with a similar partition set up to mine -- EFIv8/vista32/kalway

OS X/kalyway OSX/ on a GUID partition table - and I am having problems installing Chameleon on it, either using Zeff's installer or 0SX86Tools installer. If I install it to the first OS X partition and make it active, I am left with a blinking

cursor on boot. I then have to resort to using iATKOSv4 DVD, F8 -S and then then the Darwin command to return things

to how they were. Same problem if I do the same with the second OSX partition.

Worse, the vista partition, though repaired, no longer shows on the OSX desktop

and 'Foreign boot' is no longer listed on the bootloader, though the blank Vista

entry boots. Any pointers welecome. Certainly voodoo beta 2c doesn't work with my current setup, which is an Acer 4720z with dual core rather than C2D but I think it may briefly have done so with Chameleon in an earlier test rig I was using; in a subsequent reboot it was back to running crazy fast with VLC player, even with busratio=12.

[the J]

everything that i'm trying to connect to it (my iPhone, USB flash drive, card reader) won't be visible unless i make a reboot, is there any solution to that?

 

Hi DJNIX

 

yes theres a kext that correct this somewhere in this forum.

Currently at work and not on my usb key but If you didn't find it PM me and I'll try to find the name for you (working with last osx server from Leo 4v5 / acer aspire 9422wsmi)

While you're here you may have a look at

http://forum.insanelymac.com/index.php?showtopic=95789

 

 

;-)))

 

a+

JJ

[laetilodie]

All work very good with kernel voodoo beta2c

 

Test 1 Passed: [X] Yes [_] No [_] With issues

Test 2 Passed: [X] Yes [_] No [_] With issues

Test 3 Passed: [X] Yes [_] No [_] With issues

Test 4 Passed: [X] Yes [_] No [_] With issues

Test 5 Passed: [X] Yes [_] No [_] With issues

Test 7 Passed: [X] Yes [_] No [_] With issues

 

I have only one bug. I try different kernel and the bug is still there.

With cpus=2 i have the laggy mouse problem ( mouse not reponding, no network ) but keyboard work and i can restart leopard. The problem appears after 1 or 2 hours watching tv for example.

If i use cpus=1 no problems.

 

Do you think it's possible to correct this problem. I think it's exactly the same amd problem.

 

My configuration

leopard 10.5.5 ( kernel voodoo 2c)

Msi P6 SLI-FI ( nforce 650i )

Core2duo 4300 @ 3000 ( 9*333 )

8800GT

4Gb DDR2 667

rtl 8139 (i try different network card with the same problem )

Mouse logitech MX Revolution

[NHJ]

there's a trouble i have with all non vanilla kernels is the loss of bluetooth, it's unable to detect anything.

 

for the rest that kernel is working fine exept both cores but this is a trouble on my laptop that can't be fixed right now.

[Dxn]

Okay, the responses regarding 64-bit and >4Gb memory got me thinking. What is the point of using 64-bit software, if not to allow users to utilize larger amounts of RAM? If that can be accomplished without native 64-bit support, what is the purpose of 64-bit? Does the emulation of the larger address space cause a noticeable performance hit?

[mercurysquad]

Okay, the responses regarding 64-bit and >4Gb memory got me thinking. What is the point of using 64-bit software, if not to allow users to utilize larger amounts of RAM? If that can be accomplished without native 64-bit support, what is the purpose of 64-bit? Does the emulation of the larger address space cause a noticeable performance hit?

Check this post

[Snerler]

Hi,

 

I have a problem with USB devices not mounting after the computer has been on for some time. Is it because I am using the older APPLEsmbios.kext?

[Harvey Dent]

hello, I'm a nub I want to know if someone can type a step by step on testing new kernel it says copy to root i assume its just your hd and boot using voodoo_beta2 -v i tried that and goes to my default one please help im a nub

[Dxn]

hello, I'm a nub I want to know if someone can type a step by step on testing new kernel it says copy to root i assume its just your hd and boot using voodoo_beta2 -v i tried that and goes to my default one please help im a nub

 

You have to set permissions, too. You'd be better off to download ~pcwiz's Osx86 Tools. It has options for backing up and installing kernels.

 

 

 

 

Also, thanks for the link, Merc. Makes sense

[NickRiley]

the J, Snerler,

Guys, of course, this is an offtop, but read carefully previous posts, check Dabluest's -

Your problem with mounting USB devices might be related to not having matching versions of the kernel and System.kext. Since this version of the Voodoo kernel is 9.5.0 you must also have version 9.5.0 System.kext or you may run into problems like you described.

 

To check your System.kext version go to: /System/Library/Extensions/. Right click on System.kext and select Get Info. If it doesn't say version 9.5.0, then download the correct System.kext here.

[Moro21]

sorry.. the beta3 should not be released on this week??

[mercurysquad]

Sadly there seems to be more delay .. waiting on kaitek/dense/zef to finish off the patcher and new bootloader. We are all busy with real work too

[Juker]

hello Mrs Fantastic mercurysquad

 

How to compiler kernel for Amd

 

Can you write setences and flags

 

example:

A. How to build XNU

B. How to install a new header file from XNU

 

=============================================

A. How to build XNU:

 

1) Type: "make"

 

This builds all the components for kernel, architecture, and machine

configurations defined in TARGET_CONFIGS. Additionally, we also support

architectures defined in ARCH_CONFIGS and kernel configurations defined in

KERNEL_CONFIGS. Note that TARGET_CONFIGS overrides any configurations defined

in ARCH_CONFIGS and KERNEL_CONFIGS.

 

By default, architecture defaults to the build machine

architecture, and the kernel configuration is set to build for DEVELOPMENT.

The machine configuration defaults to S5L8900XRB for arm and default for i386 and ppc.

 

This will also create a bootable image, mach_kernel, and a kernel binary

with symbols, mach_kernel.sys.

 

Examples:

/* make a debug kernel for H1 arm board */

make TARGET_CONFIGS="debug arm s5l8900xrb"

 

$(OBJROOT)/DEBUG_ARM_S5L8900XRB/osfmk/DEBUG/osfmk.o: pre-linked object for osfmk component

$(OBJROOT)/DEBUG_ARM_S5L8900XRB/mach_kernel: bootable image

 

/* make debug and development kernels for H1 arm board */

make TARGET_CONFIGS="debug arm s5l8900xrb development arm s5l8900xrb"

 

$(OBJROOT)/DEBUG_ARM_S5L8900XRB/osfmk/DEBUG/osfmk.o: pre-linked object for osfmk component

$(OBJROOT)/DEBUG_ARM_S5L8900XRB/mach_kernel: bootable image

$(OBJROOT)/DEVELOPMENT_ARM/osfmk/DEVELOPMENT/osfmk.o: pre-linked object for osfmk component

$(OBJROOT)/DEVELOPMENT_ARM/mach_kernel: bootable image

 

/* this is all you need to do to build H1 arm with DEVELOPMENT kernel configuration */

make TARGET_CONFIGS="default arm default"

 

or the following is equivalent

 

make ARCH_CONFIGS=ARM

 

2) Building a Component

 

Go to the top directory in your XNU project.

 

If you are using a sh-style shell, run the following command:

$ . SETUP/setup.sh

 

If you are using a csh-style shell, run the following command:

% source SETUP/setup.csh

 

This will define the following environmental variables:

SRCROOT, OBJROOT, DSTROOT, SYMROOT

 

From a component top directory:

 

$ make all

 

This builds a component for all architectures, kernel configurations, and

machine configurations defined in TARGET_CONFIGS (or alternately ARCH_CONFIGS

and KERNEL_CONFIGS).

 

Example:

$(OBJROOT)/RELEASE_PPC/osfmk/RELEASE/osfmk.o: pre-linked object for osfmk component

 

From the component top directory:

 

$ make mach_kernel

 

This includes your component in the bootable image, mach_kernel, and

in the kernel binary with symbols, mach_kernel.sys.

 

WARNING: If a component header file has been modified, you will have to do

the above procedure 1.

 

3) Building DEBUG

 

Define kernel configuration to DEBUG in your environment or when running a

make command. Then, apply procedures 4, 5

 

$ make TARGET_CONFIGS="DEBUG PPC DEFAULT" all

 

or

 

$ make KERNEL_CONFIGS=DEBUG all

 

or

 

$ export TARGET_CONFIGS="DEBUG ARM MX31ADS"

$ make all

 

Example:

$(OBJROOT)/DEBUG_PPC/osfmk/DEBUG/osfmk.o: pre-linked object for osfmk component

$(OBJROOT)/DEBUG_PPC/mach_kernel: bootable image

 

4) Building fat

 

Define architectures in your environment or when running a make command.

Apply procedures 3, 4, 5

 

$ make TARGET_CONFIGS="RELEASE PPC default RELEASE I386 default" exporthdrs all

 

or

 

$ make ARCH_CONFIGS="PPC I386" exporthdrs all

 

or

 

$ export ARCH_CONFIGS="PPC I386"

$ make exporthdrs all

 

5) Verbose make

To display complete tool invocations rather than an abbreviated version,

$ make VERBOSE=YES

 

6) Debug information formats

By default, a DWARF debug information repository is created during the install phase; this is a "bundle" named mach_kernel.dSYM

To select the older STABS debug information format (where debug information is embedded in the mach_kernel.sys image), set the BUILD_STABS environment variable.

$ export BUILD_STABS=1

$ make

 

7) Build check before integration

 

From the top directory, run:

 

$ ~rc/bin/buildit . -arch ppc -arch i386 -noinstallsrc -nosum

 

or for multiple arm builds

 

$ ~rc/bin/buildit . -noinstallsrc -nosum -- TARGET_CONFIGS="release arm MX31ADS release arm LN2410SBC"

 

or for default arm build (kernel config DEVELOPMENT and machine config MX31ADS)

 

$ ~rc/bin/buildit . -arch arm -noinstallsrc -nosum -- TARGET_CONFIGS="release arm MX31ADS release arm LN2410SBC"

 

 

8) Creating tags and cscope

 

Set up your build environment as per instructions in 2a

 

From the top directory, run:

 

$ make tags # this will build ctags and etags on a case-sensitive

# volume, only ctags on case-insensitive

 

$ make TAGS # this will build etags

 

$ make cscope # this will build cscope database

 

=============================================

B. How to install a new header file from XNU

 

[Note: This does not covers installing header file in IOKit framework]

 

1) XNU installs header files at the following locations -

a. $(DSTROOT)/System/Library/Frameworks/Kernel.framework/Headers

b. $(DSTROOT)/System/Library/Frameworks/Kernel.framework/PrivateHeaders

c. $(DSTROOT)/System/Library/Frameworks/System.framework/Headers

d. $(DSTROOT)/System/Library/Frameworks/System.framework/PrivateHeaders

e. $(DSTROOT)/usr/include/

 

Kernel.framework is used by kernel extensions. System.framework

and /usr/include are used by user level applications. The header

files in framework's "PrivateHeaders" are only available for Apple

Internal development.

 

2) The directory containing the header file should have a Makefile that

creates the list of files that should be installed at different locations.

If you are adding first header file in a directory, you will need to

create Makefile similar to xnu/bsd/sys/Makefile.

 

Add your header file to the correct file list depending on where you want

to install it. The default locations where the header files are installed

from each file list are -

 

a. DATAFILES : To make header file available in user level -

$(DSTROOT)/System/Library/Frameworks/System.framework/Headers

$(DSTROOT)/System/Library/Frameworks/System.framework/PrivateHeaders

$(DSTROOT)/usr/include/

 

b. PRIVATE_DATAFILES : To make header file available to Apple internal in

user level -

$(DSTROOT)/System/Library/Frameworks/System.framework/PrivateHeaders

 

c. KERNELFILES : To make header file available in kernel level -

$(DSTROOT)/System/Library/Frameworks/Kernel.framework/Headers

$(DSTROOT)/System/Library/Frameworks/Kernel.framework/PrivateHeaders

 

d. PRIVATE_KERNELFILES : To make header file available to Apple internal

for kernel extensions -

$(DSTROOT)/System/Library/Frameworks/Kernel.framework/PrivateHeaders

 

3) The Makefile combines the file lists mentioned above into different

install lists which are used by build system to install the header files.

 

If the install list that you are interested does not exists, create it

by adding the appropriate file lists. The default install lists, its

member file lists and their default location are described below -

 

a. INSTALL_MI_LIST : Installs header file to location that is available to

everyone in user level.

Locations -

$(DSTROOT)/System/Library/Frameworks/System.framework/Headers

$(DSTROOT)/usr/include/

Definition -

INSTALL_MI_LIST = ${DATAFILES}

 

b. INSTALL_MI_LCL_LIST : Installs header file to location that is available

for Apple internal in user level.

Locations -

$(DSTROOT)/System/Library/Frameworks/System.framework/PrivateHeaders

Definition -

INSTALL_MI_LCL_LIST = ${DATAFILES} ${PRIVATE_DATAFILES}

 

c. INSTALL_KF_MI_LIST : Installs header file to location that is available

to everyone for kernel extensions.

Locations -

$(DSTROOT)/System/Library/Frameworks/Kernel.framework/Headers

Definition -

INSTALL_KF_MI_LIST = ${KERNELFILES}

 

d. INSTALL_KF_MI_LCL_LIST : Installs header file to location that is

available for Apple internal for kernel extensions.

Locations -

$(DSTROOT)/System/Library/Frameworks/Kernel.framework/PrivateHeaders

Definition -

INSTALL_KF_MI_LCL_LIST = ${KERNELFILES} ${PRIVATE_KERNELFILES}

 

4) If you want to install the header file in a sub-directory of the paths

described in (1), specify the directory name using two variable

INSTALL_MI_DIR and EXPORT_MI_DIR as follows -

 

INSTALL_MI_DIR = dirname

EXPORT_MI_DIR = dirname

 

5) A single header file can exist at different locations using the steps

mentioned above. However it might not be desirable to make all the code

in the header file available at all the locations. For example, you

want to export a function only to kernel level but not user level.

 

You can use C language's pre-processor directive (#ifdef, #endif, #ifndef)

to control the text generated before a header file is installed. The kernel

only includes the code if the conditional macro is TRUE and strips out

code for FALSE conditions from the header file.

 

Some pre-defined macros and their descriptions are -

a. PRIVATE : If true, code is available to all of the xnu kernel and is

not available in kernel extensions and user level header files. The

header files installed in all the paths described above in (1) will not

have code enclosed within this macro.

 

b. KERNEL_PRIVATE : Same as PRIVATE

 

c. BSD_KERNEL_PRIVATE : If true, code is available to the xnu/bsd part of

the kernel and is not available to rest of the kernel, kernel extensions

and user level header files. The header files installed in all the

paths described above in (1) will not have code enclosed within this

macro.

 

d. KERNEL : If true, code is available only in kernel and kernel

extensions and is not available in user level header files. Only the

header files installed in following paths will have the code -

$(DSTROOT)/System/Library/Frameworks/Kernel.framework/Headers

$(DSTROOT)/System/Library/Frameworks/Kernel.framework/PrivateHeaders

 

http://www.opensource.apple.com/darwinsource/10.5.5/

[Moro21]

Sadly there seems to be more delay .. waiting on kaitek/dense/zef to finish off the patcher and new bootloader. We are all busy with real work too

 

ok..thnk for info and good job.

[Detosx]

Guys, though in a sense this is the wrong place to post this, if anyone out there can help me with Chameleon, in relation to voodoo 9.5.0 beta 2c, I would be most grateful.

 

Having googled, I haven't found anyone with a similar partition set up to mine -- EFIv8/vista32/kalway

OS X/kalyway OSX/ on a GUID partition table - and I am having problems installing Chameleon on it, either using Zeff's installer or 0SX86Tools installer. If I install it to the first OS X partition and make it active, I am left with a blinking

cursor on boot. I then have to resort to using iATKOSv4 DVD, F8 -S and then then the Darwin command to return things

to how they were. Same problem if I do the same with the second OSX partition.

Worse, the vista partition, though repaired, no longer shows on the OSX desktop

and 'Foreign boot' is no longer listed on the bootloader, though the blank Vista

entry boots. Any pointers welecome. Certainly voodoo beta 2c doesn't work with my current setup, which is an Acer 4720z with dual core rather than C2D but I think it may briefly have done so with Chameleon in an earlier test rig I was using; in a subsequent reboot it was back to running crazy fast with VLC player, even with busratio=12.

I managed to get Chameleon to install per a thread by Pcwiz that people having trouble with OSX86 Tools should uninstall it and install the older version 1.0.149. That worked perfectly - except... my Vista partition doesn't show up in Chameleon's boot loader.

 

Unfortunately it hasn't resolved the issue with 9.5.0 beta2c, though iTunes works.

 

What's your baseline test rig, by which I mean which distro, I'm using Kalyway, was it updated with Mysticus C* 10.5.5 and so on? At least then I could eliminate any unseen variable. If there is anything else that I can try for you, please let me know. Thanks.

[BartNijland]

Okay, discoverd a new problem.

 

The mouse issue from AMD is fixed, but now the mouse just randomly freezes, while the buttons work, i can't move it. Then after a while it just works again (this happens after i booted the os for a while).

[Alex HQuest]

Unable to reset/power off on Retail 10.5.5.

 

Using Munky's guide to boot using EFI partition to host kernel/modified kexts.

 

Any tip I'm missing?

[inimicus]

Voodoo Beta 2c working on Pentium D820.

Increased Xbench score over 5 points compared to 9.4 modbin kernel.

 

Video and audio perform the same, no mal effects.

 

 

Noticeably snappier response.  Stable.

 

Vanilla AppleSMBIOS (With AppleSMBIOSEFI), AppleACPIPlatform, and System.kext.

[BartNijland]

Okay, discoverd a new problem.

 

The mouse issue from AMD is fixed, but now the mouse just randomly freezes, while the buttons work, i can't move it. Then after a while it just works again (this happens after i booted the os for a while).

 

Never mind this, it was Transmission.

 

Good thing AMD users can game now too! C&C3 (Cider port) running great over here!

[Detosx]

I almost never use Quicktime but in a follow up test with Chameleon installed I notice that Quicktime, along with iTunes are running at the correct speed, as far as I can tell. However, the Date&Times seconds hand is still going around too fast and VLC player, version 0.8.6f, makes videos run far too fast with broken sound. Aforementioned processor Intel dual-core T2330. Any suggestions or further tests that I might run for you are welcome.

[mercurysquad]

I almost never use Quicktime but in a follow up test with Chameleon installed I notice that Quicktime, along with iTunes are running at the correct speed, as far as I can tell. However, the Date&Times seconds hand is still going around too fast and VLC player, version 0.8.6f, makes videos run far too fast with broken sound. Aforementioned processor Intel dual-core T2330. Any suggestions or further tests that I might run for you are welcome.

I've been very busy lately but your issue is one of the issues being investigated. Thanks for the follow-ups.

[howarchaic]

Voodoo Beta 2c working on Pentium D820.

Increased Xbench score over 5 points compared to 9.4 modbin kernel.

 

Video and audio perform the same, no mal effects.

 

 

Noticeably snappier response.  Stable.

 

Vanilla AppleSMBIOS (With AppleSMBIOSEFI), AppleACPIPlatform, and System.kext.

 

 

You are still {censored}.

 

 

What bootloader are you using these days?

[Detosx]

I've been very busy lately but your issue is one of the issues being investigated. Thanks for the follow-ups.

Glad to help. Tried a few other things. One of which worked but perhaps isn't ideal. I used the -f command at boot. I noticed at once that the bounces on the dock had slowed down. Played a video on VLC, everything fine. The Date&Time clock, the seconds hand is turning at the right speed. My technical knowledge is limited but -f would suggest some kext isn't loading up which should? I am probably missing something obvious but thank you for your patience. Anyone have any suggestions how I can narrow this one down?

[inimicus]

You are still {censored}.

 

 

What bootloader are you using these days?

 

Teh standard.  No Boot132/Chameleon.

 

 

 

 

Urz {censored}.

[mercurysquad]

Teh standard.  No Boot132/Chameleon.

Urz {censored}.

You mean the kernel is working... without an EFI bootloader? I'll be surprised.