Kernel 9.6.0 basado en Voodoo
Andy Vandijck ha portado las fuentes del kernel Voodoo XNU a la versión XNU 9.6.0 (Mac OS X 10.5.6) en un paquete instalador listo para usar, manteniendo toda la compatibilidad del kernel 9.5.0 para procesadores AMD e Intel Legacy.
- Autor principal
-
@pαuℓzurrr.
Publicado el 2009-01-01
- Colección
- Arquitectura Base OSx86 10.X y Arranque
- Registro histórico
- 351,844 lecturas históricas · 66 notas de campo seleccionadas (de 73 mensajes) · 2009-01-01 – 2009-11-22
- Voces acreditadas (32)
- @andyvand (10)@lanceomni (8)@maya77 (6)@outwithspam (6)@pαuℓzurrr. (4)@eMatoS (4)@kocoman (3)@xXrkidXx (3)@Kabyl (3)@biird (2)@oneshot (2)@Valentine (2)@mindlessmissy@Alphaman@FirstHackTosh@peppi911+16 more
- Referencia de hardware
- SATA III & NVMe SSDs ↗ USB 3.2 Boot Flash Drives ↗ AMD Radeon GPUs (QE/CI) ↗
Andy ha compilado un kernel 9.6.0 a partir del código fuente de Voodoo.
Viene en formato de paquete instalador (.pkg) y debería funcionar igual de bien que el actual kernel 9.5.0.
Cita de Andy:
@Andy VandijckHe estado trabajando en portar el código fuente del kernel Voodoo XNU a XNU 9.6.0 y acabo de lograrlo. El instalador está incluido en los dos archivos comprimidos de StuffIt; el resto corresponde al archivo diff para el código fuente de XNU. Feliz año nuevo a todos.
El contenido del paquete PKG se muestra a continuación:
Además, cualquier duda o problema con este kernel debe dirigirse a Andy y no al equipo oficial de Voodoo.
Descarga del instalador aquí: media fire.com/download.php?gl1nmwjen0y
Descarga del código fuente aquí: media fire.com/download.php?g3nootmzymy
Notas de campo y pruebas de la comunidad
66 respuestas técnicas seleccionadas de 73 intervenciones originales
He estado probando este nuevo kernel y parece ir muy bien, igual que el original; el único cambio que tuve que hacer fue restaurar el Seatbelt.kext de 10.5.6 porque el anterior me provocaba Kernel Panics aleatorios al montar imágenes de disco.
@eMatoSHe estado probando este nuevo kernel y parece ir muy bien, igual que el original; el único cambio que tuve que hacer fue restaurar el Seatbelt.kext de 10.5.6 porque el antiguo me provocaba Kernel Panics aleatorios al montar imágenes de disco.
Sí, yo también acabo de notarlo.
¿Podrías pasarme el archivo seatbelt.kext de 10.5.6?
¡Gracias!
Vale...
De momento pinta bastante bien... salvo por algunos errores de sandbox que aparecen en la Consola...
Por cierto, ¿qué son todos esos kexts y binarios adicionales que incluye el instalador?
¿Son realmente necesarios?
¿Cuáles son las ventajas de este nuevo kernel respecto al 9.5.0?
¿Arregla por casualidad el soporte de USB 2.0?
http://code.google.com/p/xnu-dev/wiki/NewsArchive ↗
2 de enero de 2009: Han aparecido algunas adaptaciones o derivados independientes del kernel Voodoo basados en los parches de código fuente que publicamos. Tened en cuenta que el único lugar donde obtener versiones oficiales del kernel, paquete instalador, documentación, código fuente y todo el material relacionado es este sitio web. La licencia del código fuente prohíbe expresamente la distribución de obras derivadas sin autorización...
Mmm, no consigo que se monten las unidades USB y creo que se debe a que mi System.kext es la versión 9.6, pero mi kernel sigue siendo el 9.5... mach_kernel.voodoo sigue figurando como 9.5 y, cuando cambio el nombre para intentar arrancar con el nuevo mach_kernel, el equipo no arranca... ¿Alguna idea?
@biirdMmm, no consigo que se monten las unidades USB y creo que se debe a que mi System.kext es la versión 9.6, pero mi kernel sigue siendo el 9.5… mach_kernel.voodoo sigue figurando como 9.5 y, cuando cambio el nombre para intentar arrancar con el nuevo mach_kernel, el equipo no arranca... ¿Alguna idea?
Probablemente tu archivo com.apple.Boot.plist tenga fijado explícitamente el arranque con mach_kernel.voodoo.
Revísalo y cámbialo a mach_kernel.
A partir de ahí podrás poner el kernel que quieras: el 9.6 de Andy encaja perfectamente con el nuevo System.kext 9.6.0 y funciona muy bien,
o bien puedes esperar a que el equipo oficial de XNU-dev publique su versión.
P
@peppi911Probablemente tu archivo com.apple.Boot.plist tenga fijado explícitamente el arranque con mach_kernel.voodoo. Revísalo y cámbialo a mach_kernel...
Sí, ¡eso era! Me había olvidado por completo de mirar com.apple.Boot.plist. ¡Muchas gracias! (Ahora toca arreglar el FireWire) w00.
El sistema parece funcionar bien, pero no puedo abrir las pocas aplicaciones PowerPC (PPC) que tengo instaladas.
@Xanthrax
Ejecutar el kernel en modo de 64 bits suele causar problemas al abrir aplicaciones PowerPC a través de Rosetta. Puedes usar el parámetro de arranque -legacy para forzar el modo de 32 bits; dudo mucho que notes diferencia de rendimiento hasta que salga 10.6 Snow Leopard.
Si con eso se soluciona, puedes dejarlo añadido permanentemente en tu com.apple.Boot.plist.
¿El kernel Voodoo permite que los usuarios de AMD instalen la actualización 10.5.6 directamente sin ningún parche? (Disculpad si es una pregunta tonta).
Y otra duda: si ya tengo una versión anterior de Voodoo instalada, ¿este instalador la sobrescribirá sin problemas?
Voodoo te permite actualizar el sistema de forma muy parecida a un equipo Intel, pero eso no significa que no necesites ningún parche adicional: échale un vistazo a los hilos sobre la actualización a 10.5.6 aquí y en InsanelyMac (por ejemplo, sigue siendo necesario contar con un bloqueador para AppleIntelCPUPowerManagement.kext y parchear los CPUID si usas AMD).
@pαuℓzurrr.Andy ha compilado un kernel 9.6.0 a partir del código fuente de Voodoo. Viene en formato de paquete instalador (.pkg) y debería funcionar igual de bien que el actual kernel 9.5.0...
Instalé esta versión y me dio un Kernel Panic al intentar abrir el instalador de prueba de iLife '09. Aquí adjunto una foto de la pantalla.
aevange, necesitas instalar el Seatbelt.kext de 10.5.6.
Te he enviado un mensaje privado.
Instalé este kernel y ahora todas mis aplicaciones PowerPC (PPC) se cierran inesperadamente antes de terminar de cargar con el error "EXC_BAD_ACCESS (SIGBUS)" :-| Ya estoy arrancando con el parámetro -legacy. ¿Alguna idea?
¿No tendrás por casualidad el parámetro -force64 puesto dentro de tu com.apple.Boot.plist?
@aevangeInstalé esta versión y sufrí un Kernel Panic al intentar instalar la versión de prueba de iLife '09. Aquí dejo una foto de la pantalla.
¿De dónde sacaste una versión de prueba de iLife '09?
Y como bien apuntó eMatoS, necesitarás instalar el Seatbelt.kext de 10.5.6 para que no falle al montar el DMG...
@pαuℓzurrr
¿De dónde sacaste iLife '09?
Jaja, me quedé alucinado cuando vi la función de reconocimiento facial en la presentación. Tengo muchísimas ganas de probar qué tal funciona.
Probé el instalador de Andy porque tenía el kernel 9.5.0 junto con el System.kext 9.6.0, lo que impedía que se montaran mis memorias USB. Sin embargo, tras ejecutarlo sigo teniendo el kernel 9.5.0 y, por cierto, no logro encontrar el archivo com.apple.Boot.plist en mi equipo.
Louise
Soy nueva en esto, así que no sé muy bien qué datos necesitáis, pero ahí van:
Chameleon 1.0.11
4 GB de RAM
Disco duro SATA de 500 GB
Instalado originalmente con iDeneb 10.5.5
Kernel actualizado previamente con: feelin gentity.com/2008/11/28/voodoo-xnu-kernel-hits-release-candidate/
Actualizado a Leopard 10.5.6 mediante Actualización de Software de Apple
Varias aplicaciones han dejado de funcionar
También he notado que, tras actualizar el kernel con el paquete instalador de Andy, varias aplicaciones han dejado de abrir: en concreto, Microsoft Word, Excel, PowerPoint y FileMaker muestran el mensaje "La aplicación Microsoft Word se ha cerrado inesperadamente". Borrar los archivos de preferencias no ha servido de nada. Mi nuevo lema después de un par de semanas en este mundillo es: "¡No es un ordenador, es un pasatiempo!".
Louise
@outwithspamTambién he notado que, tras actualizar el kernel con el paquete instalador de Andy, varias aplicaciones han dejado de abrir: en concreto, Microsoft Word, Excel, PowerPoint y FileMaker muestran el mensaje "La aplicación Microsoft Word se ha cerrado inesperadamente"...
¿Cómo actualizaste exactamente a 10.5.6?
Abre la Terminal y escribe:uname -a
Dinos qué versión de kernel devuelve; debería mostrar algo parecido a: 9.5.0 Darwin Kernel Version 9.5.0 Voodoo; Release 1.0 :xnu-1228.7.58/BUILD/obj/RELEASE_I386
El archivo DMG oficial de Voodoo que descargaste antes contiene una carpeta llamada "Files" donde viene el System.kext versión 9.5.0. Podemos reinstalarlo manualmente para que coincida con tu kernel Voodoo 9.5.0: abre el DMG, arrastra System.kext a tu Escritorio y escribe lo siguiente en la Terminal:
1. Obtén permisos de superusuario (root) para modificar archivos del sistema:
sudo -s2. Cambia al directorio /System/Library:
cd /System/Library/3. Elimina el System.kext actual (puedes hacer una copia de seguridad antes si quieres):
rm -rf Extensions/system.kext4. Copia el System.kext 9.5.0 desde el Escritorio:
cp -r ~/Desktop/system.kext Extensions/system.kext5. Asigna los permisos correctos a la carpeta Extensions:
chmod -R 755 Extensions/6. Establece el propietario correcto en la carpeta Extensions:
chown -R root:wheel Extensions/7. Actualiza la fecha de modificación de la carpeta Extensions:
touch Extensions/8. Elimina la caché de extensiones para forzar a OS X a reconstruirla con el nuevo System.kext:
rm -rf Extensions.mkext9. Repara los permisos de todo el disco:
diskutil repairpermissions /Reinicia con los parámetros -v -f.
Con esto volverás a tener el kernel y System.kext emparejados en la misma versión.
En respuesta a tu pregunta: utilicé Actualización de Software de Apple para pasar a Leopard 10.5.6 (habiendo instalado previamente Voodoo_Kernel_Release_1.0_Rev_A.dmg).
No pude seguir directamente tus pasos porque ya no me dejaba montar imágenes de disco (.dmg), pero gracias a tu explicación y a la documentación de Voodoo me di cuenta de lo que pasaba: al actualizar a 10.5.6, el instalador de Apple colocó un nuevo kernel llamado mach_kernel, pero mi archivo com.apple.Boot.plist (¡sí, por fin lo encontré!) seguía apuntando al kernel anterior. Renombré el de Apple como mach_kernel.apple, edité el archivo plist para cargar el kernel 9.6.0 de Andy y ahora uname -a muestra la versión 9.6.0, coincidiendo por fin con mi System.kext. El único problema que me queda es que MS Office (Word, Excel, PowerPoint) y FileMaker se siguen cerrando inesperadamente al abrirlos, aunque todo lo demás funciona bien. Como necesito esas aplicaciones para trabajar a diario, seguiré investigando cómo solucionarlo; si se os ocurre algo, os lo agradecería muchísimo.
Reinstalar el traductor "Rosetta" tampoco ha funcionado
Pensé que mi problema al abrir Word, FileMaker y otras aplicaciones menos recientes diseñadas para PowerPC se debía a un fallo del traductor binario Rosetta, así que reinstalé el binario translate desde un paquete que encontré aquí:
hosted.file front.com/iSynic
Como no surtió efecto, copié directamente el archivo desde mi MacBook Pro original con Leopard 10.5.6, pero tampoco funcionó: cada vez que intento abrir una de esas aplicaciones PowerPC, la Consola registra un error de bus ("bus error").
@outwithspam
Problema al abrir imágenes de disco (DMG)
Si vuelves al kernel Voodoo 9.5.0 oficial, basta con reemplazar Seatbelt.kext por la versión de 10.5.5 (si no tienes copia de seguridad, puedes extraerla del paquete de actualización 10.5.5 con Pacifist).
Cuestiones del kernel
NFOav8or dio un consejo muy práctico para gestionar kernels: guardar una copia del kernel Voodoo como mach_kernel.voodoo y otra copia idéntica llamada mach_kernel; así, si una actualización del sistema sobrescribe mach_kernel, siempre puedes arrancar escribiendo mach_kernel.voodoo en el gestor de arranque y restaurarlo en un segundo.
Problemas con aplicaciones PowerPC (Rosetta)
En el kernel Voodoo 9.5.0 oficial Rosetta funciona sin problemas en modo de 32 bits, mientras que en algunas compilaciones de 9.6.0 o al activar el modo de 64 bits falla con error de bus.
Instalación manual de Kernel, System.kext y Seatbelt.kext (9.5.0 / 10.5.5)
Coloca mach_kernel.voodoo (9.5.0), seatbelt.kext (10.5.5) y system.kext (9.5.0) en tu Escritorio y abre la Terminal:
1. Obtén privilegios de superusuario (root):
sudo -s2. Copia el kernel Voodoo al directorio raíz:
cp -r ~/Desktop/mach_kernel.voodoo /mach_kernel.voodoo3. Haz una copia de mach_kernel.voodoo como mach_kernel:
cp -r /mach_kernel.voodoo /mach_kernel4. Cambia al directorio /System/Library:
cd /System/Library5. Copia el System.kext 9.5.0 desde el Escritorio a la carpeta Extensions:
cp -r ~/Desktop/system.kext Extensions/system.kext6. Copia el Seatbelt.kext (versión 10.5.5) desde el Escritorio a la carpeta Extensions:
cp -r ~/Desktop/seatbelt.kext Extensions/seatbelt.kext7. Asigna el propietario correcto a los kernels:
chown root:wheel /mach_kernel*8. Establece los permisos de los kernels:
chmod 644 /mach_kernel*9. Establece los permisos de los kexts en la carpeta Extensions:
chmod -R 755 Extensions/10. Asigna el propietario de los kexts en la carpeta Extensions:
chown -R root:wheel Extensions/11. Actualiza la fecha de la carpeta Extensions:
touch Extensions/12. Elimina la caché de extensiones para obligar a OS X a reconstruirla:
rm -rf Extensions.mkext13. Repara los permisos de todo el disco:
diskutil repairpermissions /Reinicia con -v -f revisando antes que com.apple.Boot.plist apunte a mach_kernel o a mach_kernel.voodoo.
Aquí tienes todos los comandos seguidos para copiar y pegar de una vez:
sudo -s
cp -r ~/Desktop/mach_kernel.voodoo /mach_kernel.voodoo
cp -r /mach_kernel.voodoo /mach_kernel
cd /System/Library
cp -r ~/Desktop/system.kext Extensions/system.kext
cp -r ~/Desktop/seatbelt.kext Extensions/seatbelt.kext
chown root:wheel /mach_kernel*
chmod 644 /mach_kernel*
chmod -R 755 Extensions/
chown -R root:wheel Extensions/
touch Extensions/
rm -rf Extensions.mkext
diskutil repairpermissions /@outwithspam
Problema al abrir imágenes de disco (DMG)
¡Esto ya me funciona!
Cuestiones del kernel
Sí, me refería a 9.5.0 y guardé copias renombradas de mis kernels anteriores. Muy buen consejo.
Problemas con aplicaciones PowerPC
¿Cómo compruebo o desactivo el modo de 64 bits para que Rosetta no falle?
Revisa el archivo com.apple.Boot.plist ubicado en /Library/Preferences/SystemConfiguration y, si ves algún parámetro como -force64, elimínalo.
A continuación reinicia utilizando los parámetros -v -legacy.
El parámetro -legacy fuerza la ejecución en modo de 32 bits; comprueba si así ya abren tus aplicaciones PowerPC.
@lanceomniRevisa el archivo com.apple.Boot.plist ubicado en /Library/Preferences/SystemConfiguration y, si ves algún parámetro como -force64, elimínalo. A continuación reinicia utilizando los parámetros -v -legacy...
No tenía -force64 en el archivo plist, pero probé a reiniciar con -v -legacy y tampoco hubo suerte. Para colmo, trasteando con archivos dentro de CoreServices terminé corrompiendo algo y ahora el sistema ya no arranca. Creo que voy a reinstalar en limpio porque necesito urgentemente mis programas de trabajo...
Mil gracias de nuevo por toda tu ayuda.
¿Alguien podría indicar los pasos para volver al kernel Vanilla original de 10.5.6 tras haber probado este?
Muchas gracias de antemano.
A menos que me haya perdido algo... el equipo oficial de Voodoo todavía no ha lanzado ningún kernel 9.6.0; su última versión oficial es la 9.5.0. Aquí está la página oficial del proyecto en Google Code: http://code.google.com/p/xnu-dev/ ↗
Lo preguntaba porque esta versión solucionó los Kernel Panics por interbloqueo (deadlock) que sufría con el kernel Vanilla de 10.5.6 al usar cpus=2 en mi placa base MSI. Pensaba que el repositorio de desarrollo estaba abierto a todo el mundo.
¿Por qué nadie sube un enlace directo al maldito Seatbelt.kext de 10.5.6? Ahora nos toca esperar a que alguien lo mande por privado y lo necesito ya mismo.
¿Tanto cuesta poner un enlace AQUÍ?
Es altamente recomendable hacer siempre una copia de seguridad completa de la carpeta Extensions antes de aplicar cualquier actualización del sistema; así, si surge algún problema, puedes restaurar el kext necesario al instante.
Revisa tus mensajes privados.
Mostrar 34 notas adicionales de la comunidadRegistro de archivo completo
it this kext that you've lookin' for? dunno the version is, but i run mine with kernel 9.6.0 …hope you can use it…
ATTACHMENT REMOVED
"Please dont post Apples own material Thanks LawlessPPC"
what is the point of installing this if it will work same as 9.5.0?
Would this fix my ongoing mouse lag problem with the VooDoo 9.5.0 Kernel?
Linky: Mouse Lag/Choppiness →
can I install this on 10.5.5 or do I have to be at 10.5.6?
I LOVE YOU! awesome work.! now everything what was wrong works!
ok so a strict guide where to download files and what need to do to update from 9.5.0 to 9.6.0?
i just don`t understand here anything ...
Can someone post the seatbelt fix for the voodoo 9.6.0?
I tried to install this but when the install finished my system crashed and I wasn't booting up.So i reinstalled leopard again.Why i can't install this ? I have voodoo 9.5.0 kernel
and my system is 10.5.6.
@FirstHackToshInsanelymac What are the benefits of the new kernel? Working USB2, maybe?
USB2 support has nothing to do with my kernel...
BTW: this kernel is obsolete...
The new one also has mac model override configurable and has a built-in decrypter...
It also supports the old HPET driver (emulation of HPET for those without HPET and other things)
You can find the newer one at:
laptopneeds.forum otion.co.uk/anv-releases-f10/anv-xnu-kernel-v14-t10.htm
The installer and the sources are available from the black link at the bottom...
Also included is a full explanation of the kernels features...
If you need better USB2 support use my USB2 drivers available from:
laptopneeds.forum otion.co.uk/other-drivers-f8/anv-iousbfamily-32740-including-pcgenusbehci-t5.htm
They will offer you better and faster USB2 support with hard BIOS reset... they are based on the latest sources from Apple (so all is for 10.5.6 offcourse).
Any questions you can ask me...
EDIT: Those issues you all are talking about all got fixed since release V1.4 of the kernel... now everything works as it should...
You are still using V1.1 of the kernel which still used old dynamic linker and didn't have as much features + some issues...
Try the new one... you all will be much more satisfied...
@maya77Post links here when it's updated?
Sure... next release will be for 10.5.7 though...
I fixed up all of the major issues with the kernel so...
Works fine here, except I had kernel panic yesterday, after long time, but not sure what caused it, as both, Firefox and kernel was updated before that. Only Firefox was running and kernel panic error said it has something with the FF...
whats the benifets? is it like 9.6.0 Vanillia? does this mean we can boot retail? im very confused lol
@xXrkidXxwhats the benifets? is it like 9.6.0 Vanillia? does this mean we can boot retail? im very confused lol
It's just like Voodoo but with improvements...
For more info look at the download site...
@maya77Works fine here, except I had kernel panic yesterday, after long time, but not sure what caused it, as both, Firefox and kernel was updated before that. Only Firefox was running and kernel panic error said it has something with the FF...
Did it happen only once or did it happen each time Firefox was running?
@andyvandDid it happen only once or did it happen each time Firefox was running?
Fortunately only once.
@maya77Fortunately only once.
OK then I doubt it is a kernel bug...
It may just have been "bad luck"...
Lets hope it doesn't happen again...
yea i went to the google code web page but it there wasn't any info about it... it said the newest version was 9.5.0 not 9.6.0
@xXrkidXxyea i went to the google code web page but it there wasn't any info about it... it said the newest version was 9.5.0 not 9.6.0
Yeah I know... they still haven't completed their port to 9.6.0...
I'll beat them to the punch too with 9.7.0 if I get the chance
It is a matter of honour since some of the Voodoo team didn't threat me very well...
You fix up the warnings in the VoodooPS2 sources and give them the diffs (actually first the sources but next they nagged for the diffs...) and all they did was criticize...
They also argued that one big project over 6 smaller ones was "harder to debug"...
Man are you devs or not is the question I tend to have then...
It makes no difference as one can switch the target etc...
Star Trek: These are romulans... They are without honour
Before I start, I want you to know that I wouldn't reply if the drama wasn't started by the above poster, but I couldn't just let this go unanswered.
@andyvandYeah I know... they still haven't completed their port to 9.6.0... I'll beat them to the punch too with 9.7.0 if I get the chance It is a matter of honour since some of the Voodoo team didn't threat me very well... You fix up the warnings in the VoodooPS2 sources and give them the diffs (actually first the sources but next they nagged…
I'm really wondering as to what level you can lower yourself to, to say what you say, and release stuff the way you do.
Voodoo didn't complete the port to 9.6.0 because it takes "time" and "effort" (which isn't available) to do it "properly", you think after the work they did, they can't just go and make the fast dirty port you did? Are you going to say "Man are you devs or not is the question I tend to have then..." because of that too?
What is this attitude of "beat to the punch" from you? Is it all about that for you? /shame
I see people doing "real" work, the Voodoo kernel, VoodooPower..., the IOPCIFamily/IOUSBFamily.. kext mods, and I see you take that, fix warnings (most of the time unproperly), retag/rebrand, increment the version, and make it look like an update to the official releases. /shame
You never replied to direct technical questions concerning your additions to the voodoo kernel/projects, and the explanation is obviously because you have no idea. You would have answered otherwise, wouldn't you?
The Voodoo group (specifically, Dense here on this post ↗) contacted you (twice if not more) and invited you to join us on IRC to have a little chat about how to get working together, as we did with few others which are with us now, joined the efforts together, and you already have seen the fruits of it, but you didn't accept to come (IIRC you didn't even reply).
Why? my guess is you don't want to join a group of people, you prefer to be on your own, because all you care about is some childish fame which you obviously have got it on the InsanelyMac forum (and apparently, here too).
About your "stripped" version of the VPS2 story, why not post the link to the real source, so people know what happens?
http://forum.voodooprojects.org/index.php/topic,168.0.html ↗
I read that this forum isn't like InsanelyMac, so I'm sure this post will be here when I check back.
I'm going to ask the people who read this not to reply (except AnV, if he wants), so the drama doesn't grow, and the flaming doesn't start, please?
@Kabyl"properly"
First of all last release is more than proper...
The technical questions about my port?
Ask away... I've never seen any message directed at me with any questions nor have I ever received a mail stating any q's about it...
My point is not a "beat to the puch" attitude... it is to make something better with more features...
Retagging and rebranding only occurs if it is either something I made or it isn't desired to keep that name (like with the kernel after integration of the decrypter...)
And it is my thought that fixing warnings up and perfecting code will result in a faster and better product (I've seen this proven many times...) also I find it important to use the latest toolset and some updated libraries from the kernel...
Next the IOPCIFamily and IOUSBFamily releases are slightly different from the others and in case of the IOUSBFamily parts it does state for PCGenUSBEHCI the proper copyrights (me and the other author...)
You are wrong stating that I don't want to join a group of people and you are wrong stating that I don't allready work togheter with some...
Also fast and dirty port? the first two ones: yes... the last 2: absolutely not...
@KabylYou would have answered otherwise, wouldn't you?
I've never even noticed the posts... how could I have replied then?
@KabylThe Voodoo group (specifically, Dense here on this post (http://www.insanelymac.com/forum/index.php?s=&showt… ↗))
If I click that link I do not even get a request or anything...
Just the main page and page 3 selected below...
But I don't want there to be any further future misunderstandings between us though...
If you should have any questions you should mail me for them...
@andyvandFirst of all last release is more than proper... The technical questions about my port? Ask away... I've never seen any message directed at me with any questions nor have I ever received a mail stating any q's about it...
I've never even noticed the posts... how could I have replied then? If I click that link I do not even get a request or anything... Just the main page and page 3 selected below...
If you let the post I linked to finish loading, you'll see it, and actually the are questions asked in that same page, and you ignored them, questions about adding HPET back (no proper answer from you), I even asked you about the "proper" Apple ID you added to Chameleon 1.0.11 (I've not seen anything in the first sources you released as 1.0.12 that is worthy of adding your copyright). which made many people who understand what programming is think of it as re-tagging.
My point is not a "beat to the puch" attitude... it is to make something better with more features...
Since you like the proper way of things, there is a proper way of expressing your point, but it happens that people reveal what they really think and have inside.
And it is my thought that fixing warnings up and perfecting code will result in a faster and better product (I've seen this proven many times...) also I find it important to use the latest toolset and some updated libraries from the kernel...
I agree that fixing and perfecting code is wanted, but anyone who knows the basics of coding will agree that in many (not all), of what you've released, lacks any real improvements, and I have yet to see a real proof of that, and what you claim to be faster.
Next the IOPCIFamily and IOUSBFamily releases are slightly different from the others and in case of the IOUSBFamily parts it does state for PCGenUSBEHCI the proper copyrights (me and the other author...)
I've checked some of the first mods you posted for IOPCIFamily, maybe that was your first "work", I was disappointed.
And what shows that you usually have no idea what you're doing is something like this ↗; (quoting you):
I could also do that mod of the sources for you... if you send or PM me the patches...
If you did modify the sources and know what you did, you wouldn't ask for patches, because you already have them, /dang
You are wrong stating that I don't want to join a group of people and you are wrong stating that I don't allready work togheter with some...
It's an assumption anyone would make, because all your releases don't mention that you've worked with others, and don't tell about any group.
It's just your regular way of releasing;
NEW (lack of info..) works a lot better (no info..)
Enjoy (a smiley showing confidence)
Edit: fixed more issue (no idea what..)
You get asked each time what's new, what improvements does it bring, and then there is the usual kind of replies;
fixed warnings, perfecting the code, proper Apple IDs, and then something that may look useful (but unfortunately, not after checking the code...)
You, now, need to do much more to get your stuff working with this solution..
But I don't want there to be any further future misunderstandings between us though...
I think there is big misunderstanding from your side, specially what happened with VPS2 (you didn't comment about it)
Star Trek: These are romulans... They are without honour
Is there anything to misunderstand from that?
And I have to say that you can do better than this.
@KabylIf you did modify the sources and know what you did, you wouldn't ask for patches, because you already have them
It is for supplemental patches which someone claims to have...
I would gladly check them and improve the IOUSBFamily if they really are good...
Also did I not make a new PPF generation and applying tool?
That one is fully mine... so...
Also the point of putting the HPET code back in the kernel is simple...
It also has emulation of HPET code added which allows the standard timers and so on to be used for people without HPET...
In essence thus emulating HPET with an older (V1.1 max) AppleHPET.kext...
@andyvandIt is for supplemental patches which someone claims to have... I would gladly check them and improve the IOUSBFamily if they really are good...
You've just confirmed you have no idea what it is.
Also did I not make a new PPF generation and applying tool? That one is fully mine... so...
That's why I was fair and used words like "most" and "not all", is there anything else? anything "new" you brought to the scene? any issues you've fixed that were not fixed before? I would be glad to hear about that.
Also the point of putting the HPET code back in the kernel is simple... It also has emulation of HPET code added which allows the standard timers and so on to be used for people without HPET... In essence thus emulating HPET with an older (V1.1 max) AppleHPET.kext...
I give up on getting any "proper" answers from you. If you expect me to understand the "..." (dots), I'm sorry, It's over my head and level of knowledge.
@KabylI give up on getting any "proper" answers from you.
I give up on trying to reply to you.
Useability
A propper manual/description of your works Andy would improve a lot.
To my disapointment (for the better or worse) I must say I stopped checking out your developments, cos I am really left in the dark
and only can figur some out when I read the next 10 or 20 experiances testers post.
I liked the fact that your 9.6 kernel (back on AMD) saved me the 9.5 system.kext/seatbelt,
but I then really lost track. Version here, version there. What's this for? What's that for?
I simply switched back to the original and ignored all else you done. Shame really.
Maybe some stuff would have improved something. I'll never know...
@ValentineA propper manual/description of your works Andy would improve a lot. To my disapointment (for the better or worse) I must say I stopped checking out your developments, cos I am really left in the dark and only can figur some out when I read the next 10 or 20 experiances testers post. I liked the fact that your 9.6 kernel (back on AMD)…
Well I've included full description of the kernels features lately...
You can read them and get the latest release here:
laptopneeds.forum otion.co.uk/anv-releases-f10/anv-xnu-kernel-v14-t10.htm
Thats nice, but there is a slight misunderstanding here. It is really about how you release.
One might be interested to try someting, but on a reasonable efford basesis.
Remember OS X is very much liked cos of it's useabillity, even if we are putting our selfs there through hackintoshes.
Great products allways have a great useabillity and not just 1 million features.
Like I said, me personally: I won't be looking into things anymore, even when they might be beneficial, cos I been put off by this release policy and don't know what's next. Others might feel the same.
Due to my switch to an Intel machine, there is really no need for another kernel for me personally. But I surely will try the original new Voodoo kernel when(ever) it comes out, cos even though it's not here now, I already know what I'll be getting.
(Also, manual link: one might not want to become a member of another forum, to get a manual of something he or she gets from the "release" forum)
hmm its so easy to answer any question. Anyone can put the question in " " and then give an answer. In this thread here.. I have seen questions being asked yet a very clear reply of not wanting to answer the questions. If it was me maybe I lets say start to get a little pissed and would say.. fine .. this is what I have done.. blah blah blah.. yet here I am still trying to guess at what has really been changed. I know less about all this yet even I can tell you what has and has not been changed... anyway.
ME.. I feel ANYONE that came before and started something, deserves credit. But is not coming out with a 9.7 kernel nothing more than ADDING something to what was already there? Now ME I would have to rewrite something and then say .. its mine.. but thats just me. If I added to something that I had nothing to do with makeing I would ALWAYS give credit to those 1ST!.
Andy, ur kernel is working nice here, never crashed like 9.5.0 that crashed when I was browsing the net, but its crashing on Chess
Im using ur v1.1
thanks. Any suggestions.
Latest version is 1.4, so you may want to upgrade before asking and see if problem is gone.
@andyvandAlso the point of putting the HPET code back in the kernel is simple... It also has emulation of HPET code added which allows the standard timers and so on to be used for people without HPET... In essence thus emulating HPET with an older (V1.1 max) AppleHPET.kext...
Andy, thankfully you've finally provided an answer, about which I have asked you at least 3 times before.
Now, my assessment of your answer: if you had any kind of understanding of the Voodoo kernel changes, or even the xnu kernel only, you would know that we expressly got rid of HPET emulation of the PIT because it added to the complexity, was very poorly written, and most importantly: was completely unnecessary. Are you aware of the fact that the HPET is not used for anything at all since 10.5.6? What then, is the point of emulating it?
I don't mean to sound rude or arrogant, but your reason for putting HPET back is simply wrong. Had you discussed this with us beforehand, you'd have avoided having to add several new bootflags and asking people to use your customized AppleHPET.kext and what not.
@xandizitxuAndy, ur kernel is working nice here, never crashed like 9.5.0 that crashed when I was browsing the net, but its crashing on Chess
Andy: You said you'd like to end any misunderstandings and start contributing as a team player. For starters, you can try to fix this problem with Chess. As a hint: it is an almost trivial fix which requires changing barely 4-5 lines. Sadly I've not had time to actually test it (but Turbo has verified the fix should work). You are welcome to try it and send a patch.
What is "Kernel: Voodoo Kernel Beta C"
I've posted here in the past when I used AnV's 10.5.6 (9.6.0) beta kernel from this thread because Voodoo only had 9.5.0 kernel (Version 1), and it did not work with dual core processor. (Get the wait queue deadlock)
comes time again for 10.5.7 update, and (9.7.0) gives me the same problem, so I look back at this thread and find things have change for the worse. (crying)
Since Anv file was in a pkg format, I could not extract the mach_kernel (still newbie)
So I used my 'safe/backup retail install partition', boot it, used the qoopz mach_kernel for 10.5.7 to the "just upgraded 10.5.7" one, then reboot, (It seems OSX can detect the mach_kernel change and automatically update my softraid/Boot OSX partitions..) Anyway, reboot and 10.5.7 works.
Hello, i have prepared a kernel for 9.70 using the sources of AnV, i removed everything extra it brings, like hpet that isnt needed since 9.5.0, and the builtin decrypter that uses a magic poem, and enverything that was marked "anv"
It seems this guy don't like Anv also..
But I agree that Voodoo official kernel is a bit "slow", if it wasn't for Anv's 10.5.6 beta kernel in the first place I would not have gotten dual core to work.
Thanks AnV.
its running amazingly
only one problem(so far, SMBIOS isn't working anymore... Its calling my comp a MacBookPro 5,1, when I have it set to be a MacPro 3,1 any idea's?
how to compile custom kernel via source? ive done it with Linux via the libcurses method and menuconfig, however i dont think that will work here lol. any ideas? try to keep concise im wayyy to ADD as it is already lol.
Much thanks.
The Paradox
Fuentes y registro de autoría (32 usuarios acreditados · Hilo #1858)
| Usuario | Rol en la monografía | Mensajes | Periodo activo |
|---|---|---|---|
| @andyvand | Colaborador clave | 10 | 2009-04-26 → 2009-05-06 |
| @lanceomni | Colaborador clave | 8 | 2009-01-07 → 2009-02-09 |
| @maya77 | Colaborador clave | 6 | 2009-01-02 → 2009-05-17 |
| @outwithspam | Colaborador clave | 6 | 2009-01-12 → 2009-01-13 |
| @pαuℓzurrr. | Autor principal | 4 | 2009-01-01 → 2009-01-10 |
| @eMatoS | Colaborador clave | 4 | 2009-01-01 → 2009-01-10 |
| @kocoman | Colaborador clave | 3 | 2009-02-04 → 2009-05-23 |
| @xXrkidXx | Colaborador clave | 3 | 2009-05-01 → 2009-06-06 |
| @Kabyl | Colaborador clave | 3 | 2009-05-05 |
| @biird | Colaborador | 2 | 2009-01-04 |
| @oneshot | Colaborador | 2 | 2009-01-09 → 2009-03-20 |
| @Valentine | Colaborador | 2 | 2009-05-06 |
| @mindlessmissy | Colaborador | 1 | 2009-01-01 |
| @Alphaman | Colaborador | 1 | 2009-01-01 |
| @FirstHackTosh | Colaborador | 1 | 2009-01-02 |
| @peppi911 | Colaborador | 1 | 2009-01-04 |
| @Xanthrax | Colaborador | 1 | 2009-01-06 |
| @aevange | Colaborador | 1 | 2009-01-10 |
| @scififan68 | Colaborador | 1 | 2009-01-10 |
| @belmarduk | Colaborador | 1 | 2009-01-21 |
| @zyph3r | Colaborador | 1 | 2009-02-09 |
| @Wayang-NT | Colaborador | 1 | 2009-03-05 |
| @cj95 | Colaborador | 1 | 2009-03-09 |
| @lateralusman | Colaborador | 1 | 2009-03-17 |
| @Thopedam | Colaborador | 1 | 2009-03-25 |
| @dracea | Colaborador | 1 | 2009-03-25 |
| @esz | Colaborador | 1 | 2009-03-28 |
| @Sokairyk | Colaborador | 1 | 2009-04-26 |
| @Zeblade | Colaborador | 1 | 2009-05-16 |
| @xandizitxu | Colaborador | 1 | 2009-05-17 |
| @mercurysquad | Colaborador | 1 | 2009-05-23 |
| @paradox | Colaborador | 1 | 2009-11-22 |