Jump to content

Testing


Jief_Machak
 Share

105 posts in this topic

Recommended Posts

If I'm not mistaken, this page can be read by anyone https://docs.google.com/spreadsheets/d/1AsobMYlCfQRREav_wG0ywbx-r_UaQqCnj2ULCBGWacM/edit#gid=0

There is the efi that is currently tested.

It's also currently the last commit, so if you compile yourself, you'll get it also. Everyone has always access to everything, all the time.

 

In this spreadsheet document, you'll find one tab per person from the beta-testers team (that's how I call it). If you are interested in helping the release quality by doing tests each time we want to release a version, you're welcome.

I can set up a tab for you. Have a look.

Let's doing only if you're ok to try to do the tests at (almost)each release.

Of course, there is no commitment and everyone is working on his free time here. But if you already know just want to test this one, just do it by getting the efi from the page.

  • Like 3
Link to comment
Share on other sites

@Jief_Machak @Slice

 

good night friends

Jief Slice

I have here problems with the clover r5129 above all with the graphics part being:

HP DV6 2140ef

inetl core i5-M430
HP GeForce GT 320M
8Go ram

.... everything working fine, it is true that with each new version I have had problems with processor management that I always re-use and this summer it has to be adjusted again but now the worst is:
if i use the original r5129 config.plist i can't access the system if i use the nvidia inject
if you use nv_disable = 1 I get to the system but without QE / CI
if i use r5129 and use r5128's config.plist in it i can use normal


my question is:
what has changed in config.plist to crash the Nvidia inject?
can anything be done to correct this impasse?

thank you in advance to everyone for your outstanding work and very interesting for the community

I wish you good luck

if you have any solution or idea for me to test, I will be there to do it

 

Google translate ! 

logs.zip

  • Like 1
Link to comment
Share on other sites

@PG7

It is not a difference between 5128 and 5129. It was hundreds releases before. You have to inject Nvidia explicitly now. It was automatically with versions <5000.

Graphics->Inject->Nvidia=YES.

Be sure there are no # in any of these keys.

  • Like 1
Link to comment
Share on other sites

6 hours ago, Slice said:

It is not a difference between 5128 and 5129. It was hundreds releases before. You have to inject Nvidia explicitly now. It was automatically with versions <5000.

 

Graphics->Inject->Nvidia=YES.

 

Be sure there are no # in any of these keys.

 

 

*****  SORTED OUT *****

 

solution

 

(<key> NoDefaultProperties </key>
         <false />)

 

Thank you all

 

 

@Slice

 

I use in all versions this form "Inject Nvidia" but the config.plist of r5129 is not working!

I posted everything inside the Logs file
have:
bootlogs du config r5128 = OK
config.plist r5128 = ok

bootlogs du config r5129 = NO Boot kp
config.plist r5129 = No boot kp

use the r5129 to do the tests but tested it with the r5128 and the same happens

I checked as far as I know the r5129 config.plist and it seems to be the same as r5128 but something is not working!

I have NO problems with any of my hackintosh where I tested the r5129

thanks for any kind of clarification

 

18 hours ago, PG7 said:

Google translate ! 

logs.zip 57.38 kB · 1 download

 

Edited by PG7
Link to comment
Share on other sites

Just search a differences between these two configs.

For example

Boot OK

19:615  0:011  Apply DsdtFixMask=0x10008010

KP

11:262  0:043  Apply DsdtFixMask=0x10000000

What about other ACPI patches? Kernel and kext patches? SMBIOS settings?

Link to comment
Share on other sites

One more

Boot OK

22:195  0:002  OCSMC: SmcReadValue Key 4D534163 Size 2
22:210  0:014  FixOwnership() -> begin
22:210  0:000  Base=DB105C00 Oper=DB105C20 eecp=68
22:210  0:000  usbcmd=00080000 usbsts=00001000 usbintr=00000000
22:210  0:000  usblegsup=01000001 isOSowned=1 isBIOSowned=0 usblegctlsts=40002000
22:210  0:000  usbcmd=00080000 usbsts=00001000 usbintr=00000000
22:210  0:000  usbcmd=00080000 usbsts=00001000 usbintr=00000000
22:210  0:000  usblegsup=00000001 isOSowned=0 isBIOSowned=0 usblegctlsts=20000000
22:210  0:000  Legacy USB Off Done
22:211  0:000  USB EHCI Ownership for device 3B3C value=1000001
22:211  0:000  Base=DB105800 Oper=DB105820 eecp=68
22:211  0:000  usbcmd=00080000 usbsts=00001000 usbintr=00000000
22:211  0:000  usblegsup=01000001 isOSowned=1 isBIOSowned=0 usblegctlsts=40002000
22:212  0:000  usbcmd=00080000 usbsts=00001000 usbintr=00000000
22:212  0:000  usbcmd=00080000 usbsts=00001000 usbintr=00000000
22:212  0:000  usblegsup=00000001 isOSowned=0 isBIOSowned=0 usblegctlsts=20000000
22:212  0:000  Legacy USB Off Done
22:212  0:000  USB EHCI Ownership for device 3B34 value=1000001
22:213  0:000  ++++++++++++++++++++++++++++++++

KP

13:907  0:002  OCSMC: SmcReadValue Key 4D534163 Size 2
13:925  0:017  ++++++++++++++++++++++++++++++++

So you forget to apply FixOwnership leading to KP.

Снимок экрана 2021-01-30 в 18.10.02.png

Link to comment
Share on other sites

  • 2 weeks later...
48 minutes ago, Jief_Machak said:

Hi all,

 

the spreadsheet for testing the 5130 is here https://docs.google.com/spreadsheets/d/1AsobMYlCfQRREav_wG0ywbx-r_UaQqCnj2ULCBGWacM/edit#gid=0

@Slice Could you send me the binary, so I can put it in the spreadsheet ?

 

Thanks.


Write access, please 

Link to comment
Share on other sites

in my hacks, no problem detected; apart from the usual bug of my high sierras that being all in HFS, when I start them where there is a big sur, they go to modify the systemversion.plist in the preboot


Partial OT, I wondered if in Clover's config samples, it would not be appropriate to change the CsrActiveConfig 0X3E7 with perhaps a more functional 0X67 ???

Link to comment
Share on other sites

19 hours ago, Jief_Machak said:

Hi all,

 

the spreadsheet for testing the 5130 is here https://docs.google.com/spreadsheets/d/1AsobMYlCfQRREav_wG0ywbx-r_UaQqCnj2ULCBGWacM/edit#gid=0

@Slice Could you send me the binary, so I can put it in the spreadsheet ?

 

Thanks.

Sorry, I was too busy yesterday. Will give you the version today evening.

  • Like 1
Link to comment
Share on other sites

I don’t think I can put this binary in the spreadsheet tonight (I’m on the road and I have only my smartphone tonight.

@eveyone : could you use this exact binary for tests ? Because this is this binary that will be realeased, it’s better to test this one instead of the one you compiled yourself. A difference in build system might produce different results... See what happened with Xcode compilation few days ago...

  • Like 2
Link to comment
Share on other sites

12 hours ago, Slice said:

 

@Slice @Jief_Machak


Z390 config (Big Sur 11.3 Beta 1): boot BS + Recovery = OK :)

Please, can you push this commit. So I can try local Build with XCODE (on my IvyBridge config, Mojave, XCODE 11.3.1).

 

  • Like 2
Link to comment
Share on other sites

10 minutes ago, Matgen84 said:

 

@Slice @Jief_Machak


Z390 config (Big Sur 11.3 Beta 1): boot BS + Recovery = OK :)

Please, can you push this commit. So I can try local Build with XCODE (on my IvyBridge config, Mojave, XCODE 11.3.1).

 

It is already committed.

 

I tested this version while updating BigSur from 11.1 to 11.3.1b. This update went automatically!

First reboot to ...Install..from Preboot...

Second and third reboot  ..MacOS ...from Preboot.

That's all! All is fine, new system works as it should.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

32 minutes ago, Slice said:

It is already committed.

 

I tested this version while updating BigSur from 11.1 to 11.3.1b. This update went automatically!

First reboot to ...Install..from Preboot...

Second and third reboot  ..MacOS ...from Preboot.

That's all! All is fine, new system works as it should.

 

@Slice

 

Thanks. "Already committed" means that  commit 93196411a = pre-release r5130. Right.

I would try to build it.


 

Edited by Matgen84
Link to comment
Share on other sites

 Share

×
×
  • Create New...