基於 Voodoo 的 9.6.0 核心
Andy 利用 Voodoo 的原始碼編譯了一個 9.6.0 核心。它以安裝套件的形式提供,運作表現應該與目前的 9.5.0 核心相同。引用 Andy 的話:我一直致力於將 Voodoo XNU 核心原始碼移植到 XNU 9.6.0。…
- 主筆作者
-
@pαuℓzurrr.
發表於 2009-01-01
- 所屬專區
- OSx86 10.X 核心架構與安裝配置
- 典藏規模與紀錄
- 351,844 次歷史閱讀 · 66 則精選技術筆記(萃取自 73 則原始回帖) · 2009-01-01 – 2009-11-22
- 參與貢獻成員 (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
- 相關硬件參考
- SATA III & NVMe SSDs ↗ USB 3.2 Boot Flash Drives ↗ AMD Radeon GPUs (QE/CI) ↗
Andy 利用 Voodoo 的原始碼編譯了一個 9.6.0 核心。
它以安裝套件(PKG)的形式提供,運作表現應該與目前的 9.5.0 核心相同。
引用 Andy 的話:
@Andy Vandijck我一直致力於將 Voodoo XNU 核心原始碼移植到 XNU 9.6.0,剛剛終於成功了。安裝程式已包含在兩個 StuffIt 壓縮檔內,其餘部分則是 xnu 原始碼的 diff 差異檔。祝大家新年快樂。
PKG 安裝套件的內容包括:
另外,如果你在使用這個核心時遇到任何問題,請直接向 Andy 反映,不要去打擾 Voodoo 團隊。
核心下載位址:media fire.com/download.php?gl1nmwjen0y
原始碼下載位址:media fire.com/download.php?g3nootmzymy
社群實測與技術補充筆記
自 73 則原始討論回帖中萃取 66 則高價值技術回應
我一直在測試這個新核心,運作似乎很正常,就跟原版一樣。我唯一要做的改動是還原 10.5.6 的 seatbelt,因為舊版在掛載映像檔時會隨機引發五國死機(KP)。
@eMatoS我一直在測試這個新核心,運作似乎很正常,就跟原版一樣。我唯一要做的改動是還原 10.5.6 的 seatbelt,因為舊版在掛載映像檔時會隨機引發五國死機(KP)。
對,我也剛發現這個問題
你可以把 10.5.6 的 seatbelt.kext 傳給我嗎?
多謝!
好吧 ...
目前為止看起來還不錯 ... 除了在系統監視程式(Console)裏看到一些沙盒(sandbox)錯誤之外 ...
順帶一問,那些額外的核心延伸模組(kext)和執行檔是怎樣一回事?
它們是必須安裝的嗎?
Insanelymac
這個新核心有甚麼好處?
也許能讓 USB2 正常運作?
http://code.google.com/p/xnu-dev/wiki/NewsArchive ↗
2009 年 1 月 2 日:近期市面上出現了一些基於我們所發佈原始碼修補檔而獨立移植/衍生的 Voodoo 核心版本。請注意,獲取官方版本核心、安裝套件、說明文件、原始碼及所有相關檔案的唯一途徑是本網站。原始碼授權條款明確禁止衍生作品…
嗯……我的 USB 無法掛載,我想是因為 System.kext 是 9.6 版本,但我的核心仍然是 9.5……mach_kernel.voodoo 依然顯示為 9.5,而當我把它重新命名以嘗試直接使用 mach_kernel 時,就無法開機了……有甚麼辦法嗎?
@biird嗯……我的 USB 無法掛載,我想是因為 System.kext 是 9.6 版本,但我的核心仍然是 9.5……mach_kernel.voodoo 依然顯示為 9.5,而當我把它重新命名以嘗試直接使用 mach_kernel 時,就無法開機了……有甚麼辦法嗎?
很可能是 com.apple.Boot.plist 裏面寫死了指向 mach_kernel_voodoo 的設定?
檢查一下這個檔案,把它改成 mach_kernel。
然後放入任何你想用的核心,Andy 的 9.6 核心配合最新的 system.kext 可以正常運作,
或者乾脆等官方 xnu 準備好再說!
P
@peppi911很可能是 com.apple.Boot.plist 裏面寫死了指向 mach_kernel_voodoo 的設定?檢查一下這個檔案,把它改成 mach_kernel。然後放入任何你想用的核心,Andy 的 9.6 核心配合最新的 system.kext 可以正常運作,或者乾脆等官方 xnu 準備好再說!P
沒錯……這樣就搞定了。完全忘了 com.apple.Boot.plist 這回事。多謝!(現在是時候去修好 Firewire 了)太好了。
看起來運作正常,但我無法執行那幾個 PPC 應用程式。
@Xanthrax
在 64 位元模式下執行,可能會導致透過 Rosetta 執行 PPC 應用程式時出現問題。你可以使用開機參數 -legacy 強制進入 32 位元模式。在 10.6 推出之前,我懷疑你不會感受到任何效能上的差異。
如果這方法對你有效的話,可以把它加進你的 com.apple.boot.plist 裏。
Voodoo 是不是能讓 AMD 用家無需任何修補檔就能安裝 10.5.6?(不好意思,這可能是個蠢問題)
另外,如果我已經安裝了舊版的 Voodoo,這個安裝程式會直接覆蓋舊版而不會出問題嗎?
Voodoo 會讓你像使用 Intel 處理器一樣進行更新,但這並不代表完全不需要任何修補檔。看看這裏和 InsanelyMac 上的 10.5.6 更新討論串,你就明白我在說甚麼了(例如需要安裝處理解決 appleintelcpupowermanagement)。
@pαuℓzurrr.Andy 利用 Voodoo 的原始碼編譯了一個 9.6.0 核心。它以安裝套件的形式提供,運作表現應該與目前的 9.5.0 核心相同。引用 Andy 的話;PKG 安裝套件的內容包括;另外,如果你在使用這個核心時遇到任何問題,請直接向 Andy 反映,不要去打擾 Voodoo 團隊。核心下載位址:media…
安裝了這個版本,但在安裝 iLife09 試用版時出現五國死機(KP)。這是當時的畫面相片。
aevange,你需要 10.5.6 版本的 seatbelt。
已經發了私訊(PM)給你
我安裝了這個核心之後,現在我所有的 PPC 應用程式在載入前都會崩潰,並顯示「EXC_BAD_ACCESS (SIGBUS)」:-| 我已經是用 -legacy 參數開機了。有甚麼頭緒嗎?
你的 com.apple.boot.plist 裏面該不會剛好有 -force64 這個參數吧?
@aevange安裝了這個版本,但在安裝 iLife09 試用版時出現五國死機(KP)。這是當時的畫面相片。
你在哪裏弄到 iLife '09 的 ?
而且正如 eMatoS 所建議,你需要換上 10.5.6 的 seatbelt...
@pαuℓzurrr
你在哪裏弄到 iLife '09 的?
對啊,當我看到人臉辨識功能時簡直興奮死了,真迫不及待想看看它的實際效果有多好。
我試用了 Andy 的安裝程式,因為我原本是 9.5.0 核心配搭 9.6.0 的 system.kext,我認為這導致我的 USB 手指無法掛載。但安裝後核心依然是 9.5.0,順帶一提,我在機上找不到 com.apple.boot.plist 這個檔案?
Louise
我是這方面的新手,不確定你們需要甚麼資訊,先列出以下配置:
Chameleon 1.0.11 開機引導程式
4 GB 記憶體
SATA 500 GB 硬碟
使用 iDeneb 10.5.5 安裝
使用這個檔案升級核心:feelin gentity.com/2008/11/28/voodoo-xnu-kernel-hits-release-candidate/
透過 Apple 軟件更新升級至 Leopard 10.5.6
好幾個應用程式無法再運作
另外我還注意到,使用 Andy 的安裝套件升級核心之後,有好幾個應用程式無法再運作了。最明顯的是 Microsoft Word、Excel、Powerpoint 以及 Filemaker 都會彈出「應用程式 Microsoft Word 意外結束」的訊息。刪掉偏好設定檔(prefs)也無法解決問題。玩了幾個星期黑蘋果之後,我的新座右銘是:「這不是一部電腦,這是一門嗜好」!
Louise
@outwithspam另外我還注意到,使用 Andy 的安裝套件升級核心之後,有好幾個應用程式無法再運作了。最明顯的是 Microsoft Word、Excel、Powerpoint 以及 Filemaker 都會彈出「應用程式 Microsoft Word 意外結束」的訊息。刪掉偏好設定檔(prefs)也無法解決問題。玩了幾個星期之後,我的新座右銘是…
你是怎樣更新到 10.5.6 的?
打開終端機(Terminal)並輸入:
uname -a
請回覆它顯示你的核心版本是甚麼。應該會類似這樣:9.5.0 Darwin Kernel Version 9.5.0 Voodoo; Release 1.0 :xnu-1228.7.58/BUILD/obj/RELEASE_I386
你下載的 DMG 映像檔裏面應該有一個名為「Files」的資料夾,裏面會有 9.5.0 版本的 System.kext。我們可以手動安裝它。打開 DMG 並將 system.kext 拖曳到桌面上,然後在終端機輸入以下指令(這些指令假設 system.kext 已經放在你的桌面上):
1. 取得 root 權限以修改檔案。
sudo -s
2. 切換目錄到 /s/l
cd /System/Library/
3. 移除現有的 system.kext。(如果你願意,可以先備份它)
rm -rf Extensions/system.kext
4. 複製你從下載檔案中解壓縮出來的 9.5.0 版 system.kext
cp -r ~/Desktop/system.kext Extensions/system.kext
5. 為 Extensions 資料夾設定正確的權限
chmod -R 755 Extensions/
6. 為 Extensions 資料夾設定正確的擁有者
chown -R root:wheel Extensions/
7. 更新 Extensions 資料夾的時間戳記(touch)
touch Extensions/
8. 移除核心延伸模組快取,強制 OSX 使用新的 system.kext 重建快取
rm -rf Extensions.mkext
9. 修復整顆硬碟的權限
diskutil repairpermissions /
使用 -v -f 參數重新開機
現在你的核心與 system.kext 應該版本一致了。雖然有更簡短的指令寫法可以完成這些步驟,但這樣一步步來能讓你更清楚整個運作流程。
你是怎樣更新到 10.5.6 的?
打開終端機(Terminal)並輸入:
uname -a
請回覆它顯示你的核心版本是甚麼。應該會類似這樣:9.5.0 Darwin Kernel Version 9.5.0 Voodoo; Release 1.0 :xnu-1228.7.58/BUILD/obj/RELEASE_I386
回答你的問題:我是透過 Apple 軟件更新升級到 Leopard 10.5.6 的(但在那之前我曾安裝過 Voodoo_Kernel_Release_1.0_Rev_A.dmg 裏面的更新)。
我無法照你的建議去做,因為我已經無法掛載磁碟映像檔(DMG)了。不過,從你的提問以及閱讀上述 Voodoo 映像檔附帶的說明文件,我意識到問題出在 Apple 的軟件更新安裝了一個名為 mach_kernel 的新核心,但那並不是 com.apple.boot.plist 裏面所指定的核心(沒錯,我終於找到這個檔案了……正如我所說,我是新手)。我把 mach_kernel 重新命名為 mach_kernel.apple(只是為了記住它的來源),編輯了 plist 檔案,現在輸入「uname -a」顯示為 9.5.6,與 system.kext 的版本一致了。目前 MS Office(Word、Excel、Powerpoint)和 Filemaker 在嘗試載入時仍然會意外結束,但其他所有東西到目前為止都運作良好。因為我需要這些軟件來做一些「真正的工作」,我會再去多爬一些文章,盡快解決這個問題。如果你覺得你能幫上忙,我會非常感激。多謝。
重新安裝「Rosetta 轉譯環境」依然無效
我以為無法打開 Word、Filemaker(以及其他幾個「較舊」的應用程式)是 Rosetta 轉譯的問題,於是我從這裏找到的安裝套件重新安裝了「translate」檔案:
hosted.file front.com/iSynic
當發現這招無效後,我又從自己那台運行 Leopard 10.5.6 的 Apple MacBook Pro 複製了該檔案過來,結果還是不行。當嘗試打開這些「較舊」的應用程式時,系統監視程式(Console)會回報「bus error」(匯流排錯誤)。
@outwithspam
打開磁碟映像檔(DMG)的問題
這個無法打開 DMG 檔案的問題我們可以解決。只要你把 seatbelt.kext 替換回 10.5.6 之前的舊版本就能正常運作了。如果你手頭沒有備份,可以下載 10.5.5 獨立更新檔,然後用 Pacifist 把該檔案提取出來。
核心問題
你是指 9.5.0 嗎?因為你寫成了 9.5.6,我猜是手誤打錯了。它有顯示 Voodoo RC1 嗎?
NFOav8or 對於管理核心給過很好的建議。他的做法是保留一份名為 mach_kernel.voodoo 的 Voodoo 核心副本,同時將第二份副本命名為 mach_kernel;這樣即使系統更新覆蓋了 mach_kernel,你也可以直接複製蓋過去。就算重新開機時系統卡住,你也可以在開機選項中設定讓 OSX 載入 mach_kernel.voodoo。
PPC 應用程式問題
關於 Rosetta 的問題,我唯一知道的原因就是強制啟用了 64 位元模式。你的 com.apple.boot.plist 裏面還有設定其他開機參數(flags)嗎?
手動安裝核心、system.kext 與 seatbelt.kext
請將 mach_kernel.voodoo、seatbelt.kext 及 system.kext 放在桌面上(以下指令依賴放在桌面上的這些檔案)。我會逐一解釋每條指令。打開終端機並輸入:
1. 取得 root 權限以修改檔案
sudo -s
2. 將 voodoo 核心複製到根目錄
cp -r ~/Desktop/mach_kernel.voodoo /mach_kernel.voodoo
3. 將 mach_kernel.voodoo 複製一份為 mach_kernel(這會覆蓋原有的同名檔案)
cp -r /mach_kernel.voodoo /mach_kernel
4. 切換目錄到 /System/Library
cd /System/Library
5. 將桌面上的 9.5.0 版 system.kext 複製到 Extensions 資料夾
cp -r ~/Desktop/system.kext Extensions/system.kext
6. 將桌面上 10.5.5 版本的 seatbelt.kext 複製到 Extensions 資料夾
cp -r ~/Desktop/seatbelt.kext Extensions/seatbelt.kext
7. 設定所有核心檔案的擁有者
chown root:wheel /mach_kernel*
8. 設定所有核心檔案的權限
chmod 644 /mach_kernel*
9. 設定 Extensions 資料夾內所有 kext 的權限
chmod -R 755 Extensions/
10. 設定 Extensions 資料夾內所有 kext 的擁有者
chown -R root:wheel Extensions/
11. 更新 Extensions 資料夾的時間戳記
touch Extensions/
12. 移除核心延伸模組快取,強制 OSX 重建快取
rm -rf Extensions.mkext
13. 修復整顆硬碟的磁碟權限
diskutil repairpermissions /
使用 -v -f 重新開機。如果你在 com.apple.boot.plist 中指定了核心路徑,請將該設定移除。重新開機前最好檢查一下 com.apple.boot.plist,確保它沒有指向其他核心。如果裏面寫的是 mach_kernel、mach_kernel.voodoo 或完全沒指定,那就沒問題。
以下是上述指令的完整匯總,方便一次過執行:
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
打開磁碟映像檔(DMG)的問題
這部分現在已經修好了。
核心問題
你是指 9.5.0 嗎?因為你寫成了 9.5.6,我猜是手誤打錯了。它有顯示 Voodoo RC1 嗎?
NFOav8or 對於管理核心給過很好的建議。他的做法是保留一份名為 mach_kernel.voodoo 的 Voodoo 核心副本,同時將第二份副本命名為 mach_kernel;這樣即使系統更新覆蓋了 mach_kernel,你也可以直接複製蓋過去。就算重新開機時系統卡住,你也可以在開機選項中設定讓 OSX 載入 mach_kernel.voodoo。
對,是 9.5.0,而且我確實有把舊核心重新命名並保留下來。真是好建議。
PPC 應用程式問題
關於 Rosetta 的問題,我唯一知道的原因就是強制啟用了 64 位元模式。你的 com.apple.boot.plist 裏面還有設定其他開機參數(flags)嗎?
我想這正是我需要處理的地方。請問我該怎樣做?
檢查位於 /Library/Preferences/SystemConfiguration 的 com.apple.boot.plist,如果看到類似 -force64 的參數,將它移除。
完成後重新開機,並在開機時使用 -v -legacy 參數。
-legacy 應該會強制進入 32 位元模式。試試看你的 PPC 應用程式能否正常運作。至於 translate 檔案,我不確定你之前做的改動會不會有影響。
@lanceomni檢查位於 /Library/Preferences/SystemConfiguration 的 com.apple.boot.plist,如果看到類似 -force64 的參數,將它移除。完成後重新開機,並在開機時使用 -v -legacy 參數。-legacy 應該會強制進入 32 位元模式。試試看你的 PPC 應用程式能否正常運作。至於 translate 檔案,我不確定你之前做的改動會…
plist 裏面沒有 -force64 或類似的東西,但我還是用 -v legacy 重新開機試了,依然無效。而且我在移除又放回一些項目時,不知怎的把 Core Services 搞砸了,現在系統完全無法開機。我想我應該考慮重新安裝系統了,因為我真的很需要用到那些應用程式……
再次感謝你的鼎力相助。
有人可以貼出還原回 10.5.6 原生核心(Vanilla Kernel)的步驟嗎?
拜託了,萬分感謝。
除非我漏看了甚麼……官方根本還沒發佈過 9.6.0 的 Voodoo 核心。他們最新的版本是 9.5.0。這裏是 Voodoo 的 Google 原始碼頁面連結:http://code.google.com/p/xnu-dev/ ↗
我之所以這樣問,是因為這個測試版修復了我的微星(MSI)底板在 10.5.6 原生零售版(Vanilla Retail)下使用 cpus=2 參數時出現的「死鎖(deadlock)」五國死機(KP)問題。我猜你必須是開發團隊成員才能查閱測試版的更新日誌吧。(我原本以為它對所有人都是完全開源的,包括未完成的版本。)
為甚麼就沒有人肯上傳 10.5.6 的 seatbelt 呢,真是的……現在我們還得乾等 paul 或 eMatos 或其他人……我現在急需用它啊!
在這裏貼個連結有那麼難嗎?
在進行任何形式的更新之前,強烈建議先備份你的 Extensions 資料夾。這樣萬一遇到問題,你也能自行修復。
請查看你的私訊(PM)
展開其餘 34 則社群技術筆記完整歷史討論紀錄
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
文獻來源與貢獻者溯源名錄(共 32 位具名成員 · 原始討論串 #1858)
| 成員用戶名 | 本卷貢獻角色 | 發帖數 | 活躍時間窗 |
|---|---|---|---|
| @andyvand | 核心貢獻者 | 10 | 2009-04-26 → 2009-05-06 |
| @lanceomni | 核心貢獻者 | 8 | 2009-01-07 → 2009-02-09 |
| @maya77 | 核心貢獻者 | 6 | 2009-01-02 → 2009-05-17 |
| @outwithspam | 核心貢獻者 | 6 | 2009-01-12 → 2009-01-13 |
| @pαuℓzurrr. | 主筆作者 | 4 | 2009-01-01 → 2009-01-10 |
| @eMatoS | 核心貢獻者 | 4 | 2009-01-01 → 2009-01-10 |
| @kocoman | 核心貢獻者 | 3 | 2009-02-04 → 2009-05-23 |
| @xXrkidXx | 核心貢獻者 | 3 | 2009-05-01 → 2009-06-06 |
| @Kabyl | 核心貢獻者 | 3 | 2009-05-05 |
| @biird | 協作成員 | 2 | 2009-01-04 |
| @oneshot | 協作成員 | 2 | 2009-01-09 → 2009-03-20 |
| @Valentine | 協作成員 | 2 | 2009-05-06 |
| @mindlessmissy | 協作成員 | 1 | 2009-01-01 |
| @Alphaman | 協作成員 | 1 | 2009-01-01 |
| @FirstHackTosh | 協作成員 | 1 | 2009-01-02 |
| @peppi911 | 協作成員 | 1 | 2009-01-04 |
| @Xanthrax | 協作成員 | 1 | 2009-01-06 |
| @aevange | 協作成員 | 1 | 2009-01-10 |
| @scififan68 | 協作成員 | 1 | 2009-01-10 |
| @belmarduk | 協作成員 | 1 | 2009-01-21 |
| @zyph3r | 協作成員 | 1 | 2009-02-09 |
| @Wayang-NT | 協作成員 | 1 | 2009-03-05 |
| @cj95 | 協作成員 | 1 | 2009-03-09 |
| @lateralusman | 協作成員 | 1 | 2009-03-17 |
| @Thopedam | 協作成員 | 1 | 2009-03-25 |
| @dracea | 協作成員 | 1 | 2009-03-25 |
| @esz | 協作成員 | 1 | 2009-03-28 |
| @Sokairyk | 協作成員 | 1 | 2009-04-26 |
| @Zeblade | 協作成員 | 1 | 2009-05-16 |
| @xandizitxu | 協作成員 | 1 | 2009-05-17 |
| @mercurysquad | 協作成員 | 1 | 2009-05-23 |
| @paradox | 協作成員 | 1 | 2009-11-22 |