Jump to content

marvelloard

Members
  • Content count

    127
  • Joined

  • Last visited

About marvelloard

  • Rank
    InsanelyMac Geek

Recent Profile Visitors

2,537 profile views
  1. marvelloard

    Windows killed MacOS

    Forgot to mention, my "old configuration" is without DSDT, so right now I'm up and running from hard-disk Clover without DSDT.
  2. marvelloard

    Windows killed MacOS

    If I use the same Clover folder as on the HDD, no. I identified the DSDT as the problem, so I posted into the thread (link above). With my own old configuration I can boot just fine, but I get the same issues I've had before MaLd0n patched my DSDT...
  3. marvelloard

    Reboots on sleep (sometimes)

    Hi madLd0n, In the meantime I tried to install Windows on a separate HDD which caused a lot of trouble, but also updated the BIOS. Maybe that screwed with the DSDT. Your DSDT no longer works. As soon as the loading bar appears the computer just reboots or in verbose mode gets stuck. Booting with dsdt=bios.aml option (Clover) works. Could you help me again? Send me Nemesis.fritz.box.zip
  4. marvelloard

    MAYA44 eX sampling rate issues

    Pretty sure it's a driver bug. I only use it for editing now, and onboard sound for everyday use. Since the DAW sets the sampling rate on startup, this setup is fine for me.
  5. marvelloard

    Windows killed MacOS

    Yes. But it worked fine before, MaLd0n helped me a lot here:
  6. marvelloard

    Windows killed MacOS

    Unfortunately it didn't help at all....
  7. marvelloard

    Windows killed MacOS

    BIOS settings are OK. How do I clear NVRam in Clover? I read by entering the shell, but I can't find a way to do so.. Edit: CFG Lock had to be set to disabled, Intel Virtualization Technology too. I missed those settings as they are hidden in "Overclocking".. Windows seems to adjust them. Edit2: OK I don't get it. For no reason it now doesn't work again. And I can't seem to find any pattern. Edit3: It works fine booting verbose, booting "regular" reboots the machine as soon as the loading bar appears. Even when doing a clean install. Edit4: Now it won't work again even for verbose.
  8. marvelloard

    Windows killed MacOS

    Hi, I tried to install Windows 10 (sorry) on a completely separate HDD. Since then my previously fine-working HS install will not boot any longer. It stops as seen on the attached screenshot. Booting from Clover USB doesn't work. How can I fix this?
  9. marvelloard

    Reboots on sleep (sometimes)

    Thank you once again. Here we go again... Send me Nemesis.fritz.box.zip After some unproblematic sleeps something very strange happened: It woke up fine. My USB hub was unplugged so I plugged it in again. Screen went black. Had to cut the power 2x until it would boot again... I have no explanation. Edit: In the last couple of days it has been perfectly fine. Maybe a one-time glitch.
  10. marvelloard

    Reboots on sleep (sometimes)

    OK, system booted fine with your folder. Hardware encoding fine, everything appears to be working. Now I must wait and see if the error will happen again. Thank you already! Send me Nemesis.fritz.box.zip
  11. marvelloard

    Reboots on sleep (sometimes)

    I'm doomed I actually found a Clover folder complete with a patched DSDT here in this form, patch done by MaLd0n. Let's see how it will perform.
  12. marvelloard

    Reboots on sleep (sometimes)

    I wasn't able to find one on the internet, how do I get one for my mainboard?
  13. marvelloard

    Reboots on sleep (sometimes)

    Here we go... By the way it just happened again, it's not related to uptime. Updated all the kexts lately too, removed some unnecessary... Send me Nemesis.fritz.box.zip
  14. marvelloard

    Reboots on sleep (sometimes)

    Just happened again. Clicked sleep, and the machine rebootet... Any other idea?
  15. marvelloard

    Reboots on sleep (sometimes)

    It seems to be fine now, thank you. But let's wait a few days... Edit: Now after sleep my DVD/BR drive stops working and doesn't eject/detect a disc. I fixed this by deactivating spin-down in energy saving. It's still deactivated, but the error occurs nevertheless. Edit2: Drive survived a few sleeps just fine, not sure what the heck. The bigger sleep issue seems to be gone.
×