RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,007
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Why you need problem reporting files ?
Because the files you attached prove you're not running the current build.
Why you need problem reporting files ?
Because the files you attached prove you're not running the current build.
Files added.
0:100 0:000 Starting Clover revision: 4658.RM-4903.24249(ca9576f3.a0344119e7) on HPQ EFI
Like i said before:Your Clover bootlog proves you're not running the latest RehabMan Clover build.
Look:
Code:0:100 0:000 Starting Clover revision: 4658.RM-4903.24249(ca9576f3.a0344119e7) on HPQ EFI
edit: i added my old "problem reporting files" - with clover 4658.
RehabMan added features/fixes
Released as Clover_v2.4k_r4701.RM-4963.ca6cca7c.zip on bitbucket, 2018-10-10:
Released as Clover_v2.4k_r4701.RM-4961.695d25a4.zip on bitbucket, 2018-10-10 (removed):
- fix bug where EDID specified in Devices/Properties would not be injected if Graphics/EDID/Inject=false
Released as Clover_v2.4k_r4697.RM-4952.c464150b.zip on bitbucket, 2018-10-07 (removed):
- allow EDID settings from Graphics/EDID to apply to EDID injection properties (override-no-connect, override-no-edid) in Devices/Properties
- update to latest Clover svn (4701)
- update to latest Clover svn (4697) -- Note: EFI/FV2 drivers group refactor in the Clover installer
But in changelog - no fixes related to this problem :/
sorry for asking - but do you read what i am posting to you ? (post date and etc. When i posted this issue - clover 4701 was not available, 4658 was the latest release).It was not something I caused, nor something I fixed.
This is all on svn/sourceforge Clover.
I don't know why you're using an old build when the guide clearly instructs to use the latest.
sorry for asking - but do you read what i am posting to you ? (post date and etc.
Updating to "Clover_v2.4k_r4701.RM-4963.ca6cca7c.zip" - fixed clover countdown issue !!! Thanks!
Yes, of course.
Post #3079 was written by you on Oct 22, 2018.
r4701.RM-4963 was released Oct 10, 2018 (twelve days prior).
Yes, of course.
Nope, I had this issue earlier than Oct 10