Jump to content


  • Content Count

  • Joined

  • Last visited

About ole2

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
  • Location
    Grenoble, France
  1. an error in verbose "AppleUSBEHCI: Could not get chip to halt within 100ms." is happening while trying to install 10.6.x macosx. it's due to missing elements inside DSDT bios configuration. it's happening at least on Packard Bell imedia pv.u58 motherboard. the board chipset is: NVIDIA GeForce 6150 SE and NVIDIA nForce 430 please share your DSDT.aml and or dsl in order to fig-out what's missing. original BIOS ACPI files are attached. imediaDSDT.zip
  2. that's relatively easy to fix - just boot back with any distro, run FDisk and assign Active Partition back to your Windows one.
  3. yes, Openminded, we are exactly here, so you'll be able to understand, where to spend your next 3K$ for...
  4. thanks for the input about cpus, but could you be so kind to list all options being selected by you while installing ?
  5. following topic may help to resolve this issue along with Chameleon 2 bootloader. see description on what to do in following post: unlocking defective bios with a help of dsdtpatcher
  6. ole2

    DSDT Patcher

    hello fassl it would be good to include xxd and grep inside Tools subfolder of your patcher. also fix dsdt extraction script for using xxd and grep from Tools instead of from /usr/bin in this case it would be possible to use your patcher from USB key (and in the future from DVD dists). using this tool on installation time will help to resolve defective BIOS blocking issue and will help to unlock following topic: Using 16384 buffer headers and 4096 cluster IO buffer headers, It just stop there when I try to boot
  7. ole2

    ACPI (DSDT) Patcher for BIOS and AML

    attached is a bios image for ASUS X66 (aka K61) model with nForce chipset and Intel CPU. could you please guide, which decompiler is suitable for this type (internally it's AMI bios) and how it would be possible to integrate into ACPI patcher tool? thanks K70ICAS209.zip
  8. * a direct link to the BIOS file, http://support.asus.com/download/download....SLanguage=en-us laptop->family X66->model X66IC but also match model K70IC bios file K70ICAS209 bios AMI version 209 attached it to the message, just in case if it's difficult to discover on site * your PC specs (CPU, Chipset and Graphics Card), processor intel dual-core T4300, mb model ASUS NVidia K61IC, chipset NVIDIA ID0A86, southbridge NVIDIA nForce 730i, graphics NVIDIA GeForce GT220M code name G96 * and a description of the issues. freeze on 16384 buffers message... probably the same issue as before with ASUS F5SL bios one. thanks for patching, will be waiting for one K70ICAS209.zip
  9. yes, please, keep posting your success about GeForce 310M here and on os86project.org wiki. thanks
  10. just discovered much less panics after temporary disabling voodoohda.kext loading. could it be they both conflicting for resources? PCI bus DMA or IRQ or something else? any thoughts, Dong? are you using voodooHDA on your development workstation along with RadeonHD.kext? thanks for comments, will be waiting.
  11. ole2

    Is there any solution for Ati Xpress 1250?

    you may try following method first, but apply your DevID 1E79 instead 8A71 one recommended there. and as usual, don't forget to post here your results, others will be waiting.
  12. the problem appeared to be not related directly to radeonHD, but to overall system behavior under 9.8.0 - the system is AMD dual(only!) core has to be warmed up before it stops crashing with KP happening. it takes usually for 5-10 minutes after first power up, while all re-boots will ends up with KP and message on the screen, no matter if system managed to popup desktop or just in a boot stage. after warm up process, system works, stable, all kexts loaded successfully and reboot progress fast and reliable. anybody observe same behavior? it's discovered and confirmed as IOKit issue from 9.8.0, so if your system is AMD processor based one, avoid using System.kext from 9.8.0 and stay with System.kext from 9.5.0, but kernel (patched for AMD of course) could be any one (personally using 9.8.0 build by BigB)
  13. Qoopz 9.8.0 get's crashing always until dual (only!) cores based AMD mobile processor get's hot enough (on single core ones it isn't happening ever). maybe, before that happened it seems like frequency is floating and doesn't match sync between cores, so kernel panic on some miss-sync operations. and so we are having different tasks crashing during the boot, but only until that. and so when it get's hot enought it starts working fine for a while (during one session), and even after that it's fine to reboot and nothing will crash anymore. please confirm anybody having same behavior.
  14. yes, that was exactly way to fix Atom330 "Should have 2 cores, but only found1 for die 0" message, while keeping both cores working fine (and simultaneously). thank you for guidance!
  15. no, this is probably same story, as mine with RS690G (mobility xpress x1200 series). by default you shouldn't need any resolution hardcoding inside Boot.plist, instead you'll have display menu with choices to select. on my side this fixed once I applied ACPIfix (available inside iDeneb 1.6), please confirm about yours. I'm going to look on how to extract logs in such case.