Jump to content

Clover General discussion

Bootloader EFI Clover

  • Please log in to reply
4243 replies to this topic

#621
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,209 posts
  • Gender:Male
yep

#622
Peter_sm

Peter_sm

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 265 posts
can clover lapic patch kernel on the fly?

#623
dmazar

dmazar

    InsanelyMac Sage

  • Coders
  • 256 posts
  • Gender:Male

So that's where I'm at, can wake fine but only w/ power button, OR w/ peripherals and restart after 30 seconds or so. For the record, my usb devices do work fine after waking.

So,
1. if you stop Clover from injecting USB device values with USBInjection=No, then you are missing some USB device values that would allow you to wake with USB mouse/keyboard
2. but if you let Clover to inject USB device values, then Clover injects values which are not good for your system

This sounds like you need to inject USB stuff, but a bit different then Clover is doing by default. You can check what Clover is injecting by using DarwinDumper to dump "Device Properties". And you can inject your own values to USB devices in DSDT.

Also, my mouse doesn't work properly within the bootloader when UEFI booting, I think somewhere back towards the beginning of the thread dmazar said it's due to OsxAptioFixDrv-64.efi... Basically it actually works, it just doesn't refresh its position when I move the mouse. However, if I right click the mouse it jumps to the place that I moved it to, so I can quasi use it by guessing and right clicking to refresh its position lol.

Yes, mouse does not work in UEFI boot here also. It's not related to AptioFix. It's just that mouse driver built inside our UEFI does not behave as it should (as specified by UEFI spec), and Clover does not get proper movement values from it.

#624
magnifico

magnifico

    InsanelyMac Deity

  • Donators
  • 2,209 posts
  • Gender:Male

Yes, mouse does not work in UEFI boot here also. It's not related to AptioFix. It's just that mouse driver built inside our UEFI does not behave as it should (as specified by UEFI spec), and Clover does not get proper movement values from it.


but you can do something for the future, or will not work ever?

#625
shiecldk

shiecldk

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 221 posts
  • Gender:Male
  • Location:Taiwan
@Slice
Wake works better with the drivers64UEFI in r911.
But I still need -v to get it wake.

I've tried to boot with "WithKexts" in normal boot (none -v), but still no luck.
So the problem is not about kernelcache.

And darkwake=0 dosen't work on my system. (need to press power button twice to get it wake)

#626
antipop2323

antipop2323

    InsanelyMac Protégé

  • Members
  • Pip
  • 48 posts

So,
1. if you stop Clover from injecting USB device values with USBInjection=No, then you are missing some USB device values that would allow you to wake with USB mouse/keyboard
2. but if you let Clover to inject USB device values, then Clover injects values which are not good for your system

This sounds like you need to inject USB stuff, but a bit different then Clover is doing by default. You can check what Clover is injecting by using DarwinDumper to dump "Device Properties". And you can inject your own values to USB devices in DSDT.


Yes, mouse does not work in UEFI boot here also. It's not related to AptioFix. It's just that mouse driver built inside our UEFI does not behave as it should (as specified by UEFI spec), and Clover does not get proper movement values from it.


I just want to point out that when I boot w/ Boot0 and

USBInjection=No then I can use my peripherals to wake and there isn't a reset. I have the same dilemma as shiecldk I think, It's only when using USBInjection = No when booting

through UEFI that my system resets itself about 30 seconds after waking. I find it curious that I'd need a patched DSDT for UEFI booting and not boot0. Seems like a driver dilemma, but the aptiofix driver schiecldk uploaded isn't helping me.



#627
Mrengles

Mrengles

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 114 posts
  • Gender:Male
  • Location:United States

1. if you stop Clover from injecting USB device values with USBInjection=No, then you are missing some USB device values that would allow you to wake with USB mouse/keyboard
2. but if you let Clover to inject USB device values, then Clover injects values which are not good for your system


When I inject USB with my system its wont allow me to use keyboard or mouse to wake the system. Actually all of the USB ports are dead on wake and one of the USB plugs needs to be reconnected to get it working again.


I just want to point out that when I boot w/ Boot0 and

USBInjection=No then I can use my peripherals to wake and there isn't a reset. I have the same dilemma as shiecldk I think, It's only when using USBInjection = No when booting

through UEFI that my system resets itself about 30 seconds after waking. I find it curious that I'd need a patched DSDT for UEFI booting and not boot0. Seems like a driver dilemma, but the aptiofix driver schiecldk uploaded isn't helping me.


We have a very similar system. I have everything working 99.99%. Maybe you should look at my conf.plist to get some ideas...

USBInjection=No
DsdtFixMask=0x20E4

Fixed my issues....

PS. Devs I'm booting UEFI and everything works, should I upload darwin dumper output for you to look at? The only issue I have is KP-restart when using Bluetooth, but from my research its a apple issue as real macs have the same problem with 10.8.2

#628
Mrengles

Mrengles

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 114 posts
  • Gender:Male
  • Location:United States
Keep in mind the only reason I said 99.99% is because of a bug with Bluetooth, but this is an apple related problem and nothing to do with Clover. So essentially clovers got me at 100%. All systems are a go Langly. =)

#629
antipop2323

antipop2323

    InsanelyMac Protégé

  • Members
  • Pip
  • 48 posts

Keep in mind the only reason I said 99.99% is because of a bug with Bluetooth, but this is an apple related problem and nothing to do with Clover. So essentially clovers got me at 100%. All systems are a go Langly. =)


Knydder actually helped me w/ my DSDT a bit and now am sleeping and waking fine w/o reboots, can wake from all peripherals wired keyboard/mouse & magic trackpad/wireless keyboard... I've never had dead USB ports on wake with this system or eject errors on wakes though... or bluetooth KPs on restart (using flashed DBT-120 B2)... my config.plist is very light and i'm using very few kexts (sound, lan & fakesmc) dsdt & sddt.

Tentatively my only remaining issues are w/ UEFI booting WoL still doesn't work and in bootloader mouse is super tweaky (position only refreshes when right clicking). dmazar seems to think it's just our board's uefi though w/ mouse bootloader issue, strange yours doesn't have the issue though and you're also using something from p8z77-v family.

#630
Mrengles

Mrengles

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 114 posts
  • Gender:Male
  • Location:United States

Knydder actually helped me w/ my DSDT a bit and now am sleeping and waking fine w/o reboots, can wake from all peripherals wired keyboard/mouse & magic trackpad/wireless keyboard... I've never had dead USB ports on wake with this system or eject errors on wakes though... or bluetooth KPs on restart (using flashed DBT-120 B2)... my config.plist is very light and i'm using very few kexts (sound, lan & fakesmc) dsdt & sddt.

Tentatively my only remaining issues are w/ UEFI booting WoL still doesn't work and in bootloader mouse is super tweaky (position only refreshes when right clicking). dmazar seems to think it's just our board's uefi though w/ mouse bootloader issue, strange yours doesn't have the issue though and you're also using something from p8z77-v family.


Good to hear you got everything working! What patches did you use to fix your DSDT? I'm curious if we are using the same exact patches. Can you list what patched you used or did you fix with Dsdtfixmask?

Also I'm am still having the UEFI mouse issue same as you. But this does not bother me what's so ever. I'm only in the main menu for a few seconds if at all.

Knydder help me get my problems fixed too. If clover had a technical support hotline Knydder would be the one answering the phone. =)

Thanks

-mrengles

PS. What asus bios/UEFI version are using, and if overclocked to what GHz?

After fixing my DSDT, I though it might have fixed the Bluetooth kp restart but it started acting up about a week later. It's very weird...

#631
kyndder

kyndder

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 113 posts
  • Gender:Male
  • Location:Brazil

Good to hear you got everything working! What patches did you use to fix your DSDT? I'm curious if we are using the same exact patches. Can you list what patched you used or did you fix with Dsdtfixmask?


He's using the same tips that I told here > #466

But on his case, he's not using any DSDT Fix Mask...

#632
antipop2323

antipop2323

    InsanelyMac Protégé

  • Members
  • Pip
  • 48 posts

Good to hear you got everything working! What patches did you use to fix your DSDT? I'm curious if we are using the same exact patches. Can you list what patched you used or did you fix with Dsdtfixmask?

Also I'm am still having the UEFI mouse issue same as you. But this does not bother me what's so ever. I'm only in the main menu for a few seconds if at all.

Knydder help me get my problems fixed too. If clover had a technical support hotline Knydder would be the one answering the phone. =)

Thanks

-mrengles

PS. What asus bios/UEFI version are using, and if overclocked to what GHz?

After fixing my DSDT, I though it might have fixed the Bluetooth kp restart but it started acting up about a week later. It's very weird...


Well, I'm using 1708 modded firmware for my P8Z77-V Pro, I believe it's UEFI 2.1 (what's yours?) I'm not using any dsdtixmask's in my config.plist. I'm only using fakesmc, applehda, and lan kexts (oh and patch for cuda cores on gtx 670)... my dsdt.aml just has warnings cleaned up, adds for HDEF & USB "stuff" kyndder did it unfortunately, I'd have to compare to my clean to figure out what was changed. My config.plist is basically stock, just added GraphicsInjection=no and USBInjection=No

Not sure about your eject error and dead usb ports on wake, I've simply never had this issue with or without DSDT, though without DSDT edits my system would reboot 30 seconds after waking when using USBinection=no

as for mouse, idc either, would be nice to get rid of the pointer I guess though or ideally just disable it all together.

#633
Mrengles

Mrengles

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 114 posts
  • Gender:Male
  • Location:United States

He's using the same tips that I told here > #466

But on his case, he's not using any DSDT Fix Mask...


I actually removed my DsdtFixMask and ended up patching my DSDT with the same fixes.

It works just the same.

Thanks, I just like learning about this stuff. The more the better. =]

Mrengles

#634
kyndder

kyndder

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 113 posts
  • Gender:Male
  • Location:Brazil

I actually removed my DsdtFixMask and ended up patching my DSDT with the same fixes.

It works just the same.


Sorry, I didn't understand what you meant....

The changes had no effect or fixed your issues???

#635
Mrengles

Mrengles

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 114 posts
  • Gender:Male
  • Location:United States

Sorry, I didn't understand what you meant....

The changes had no effect or fixed your issues???


Yes everything is working, just like a real Mac. I'm using only 3 extra extension FakeSMC, patched AppleHDA, and Realtek Ethernet driver.

What I ment to say, that I removed my Dsdtfixmask and patched my DSDT with the same fixes my fixMask had.

The only problem I'm having is when using Bluetooth devices my hack will restart on wake because of a KP. This is an issue effecting allot of real Mac users at the moment. After we discussed my problems the other day, I though this issue was fixed, but it started occurring about 3-4 days later. I really don't think my kp/restart is related to clover. I can upload my Darwin dump if you want to look at it.

Reguagless of the DSDT I still have issue with my mouse in UEFI main menu, but this is not a concern of mine all.

Before fixing my DSDT I had dead USB ports on wake, and wake on LAN issue.

-mrengles

#636
kyndder

kyndder

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 113 posts
  • Gender:Male
  • Location:Brazil

Yes everything is working, just like a real Mac. I'm using only 3 extra extension FakeSMC, patched AppleHDA, and Realtek Ethernet driver.


Nice...

Maybe with 10.8.3 update this bluetooth issue can be fixed...

#637
shiecldk

shiecldk

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 221 posts
  • Gender:Male
  • Location:Taiwan
@dmazar
The first OsxAptioFixDrv-64.efi in post #604 is from r806.

#638
FredWst

FredWst

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 162 posts
  • Gender:Male
  • Location:France
Hello,

How works kext patch ?
Can we use it to patch info.plist to add missing ids or is it just binary patching ?

Regards

#639
dmazar

dmazar

    InsanelyMac Sage

  • Coders
  • 256 posts
  • Gender:Male

The first OsxAptioFixDrv-64.efi in post #604 is from r806.

Well, I do not know what could make a difference. The only change in the code of AptioFix from r806 till now is just pausing 1 second instead of 10 seconds if error in exiting boot services occurs. Apart from that, possible changes are:
- changes in edk libraries that this driver uses
- changes in compiler

Is this behaviour with that AptioFix constant? Does it solve the issue for anybody else?

Can we use it to patch info.plist to add missing ids or is it just binary patching ?

Just binary patching.

#640
antipop2323

antipop2323

    InsanelyMac Protégé

  • Members
  • Pip
  • 48 posts

So,
1. if you stop Clover from injecting USB device values with USBInjection=No, then you are missing some USB device values that would allow you to wake with USB mouse/keyboard
2. but if you let Clover to inject USB device values, then Clover injects values which are not good for your system

This sounds like you need to inject USB stuff, but a bit different then Clover is doing by default. You can check what Clover is injecting by using DarwinDumper to dump "Device Properties". And you can inject your own values to USB devices in DSDT.


Yes, mouse does not work in UEFI boot here also. It's not related to AptioFix. It's just that mouse driver built inside our UEFI does not behave as it should (as specified by UEFI spec), and Clover does not get proper movement values from it.


Yah, you were spot on with this post... w/ DSDT fixed or by just using StringInjector w/ device properties from Chameleon I no longer get that consistent reboot 30 seconds after sleep.

I have one other issue, which is that the bootloader never shows my volume names for boot drives when booting through UEFI (this was never a problem w/ Boot0 booting). just the icon and "booting mac osx from _______" Any idea what that might be about?

Edit: Nevermind, I was using old HFSPlus driver, I get Volume names now :)





Also tagged with one or more of these keywords: Bootloader, EFI, Clover


5 user(s) are reading this topic

2 members, 3 guests, 0 anonymous users


© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   Web hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy