Incorrect display of the order of lines with memory slots in the profiler.

[ghost]

The order of the memory slot lines in the profiler does not match the actual one.
Instead of:
Channel1-Dimm1 - empty
Channel1-Dimm0 - 32 GB
Channel0-Dimm1 - empty
Channel0-Dimm0 - 32 GB
displayed:
Channel1-Dimm1 - empty
Channel1-Dimm0 - empty
Channel0-Dimm1 - 32 GB
Channel0-Dimm0 - 32 GB
Using the bdmesg command, everything is determined correctly.
When I using OpenCore, the order memory slot lines are displayed in the profiler is also correct.
2024-01-09_10-16_CLOVERX64.EFI.log

[ghost]

Hardware configuration:
CPU: i7-12700kf Alder Lake
MB: Asrock Z690 PG Reptide
RAM: 2x32Gb DDR4 3200 Crucial Technology
GPU: Radeon RX5700 Sapphire Nitro+ 8Gb
SSD: 1Tb WD_BLACK SN850X NVME M2 (PCI-e 4.0) - Mac OS 14.2.1/Windos 11
SSD: 521gb Samsung 860 EVO (SATA-6 Gbit) -
WIFI/BT: bcm943602CS in FV-AC1200 PCI-E adapter
BIOS: v16.01
Display: ViewSonic 4K 60 Hz HDR via Display Port (VX3211-4K)

[jief666]

Have you tried an older Clover to see if the order is correct ?

[SergeySlice]

Set SMBIOS->Trust=true

[SergeySlice]

Also set
SMBIOS->Memory->Channels=2
By default this value = 1

[ghost]

I can’t try Old Clover, since I don’t have it saved, and I couldn’t load either Ventura or Sonoma.
I also doubt that I would be able to compile it now.
Bat I changed my config file like this:

	<dict>
		<key>Memory</key>
		<dict>
			<key>Channels</key>
			<integer>2</integer>
		</dict>
		<key>Trust</key>
		<true/>
	</dict>

and nothing has changed:


[preboot.log](https://github.com/CloverHackyColor/CloverBootloader/files/13907648/preboot.log
And this is from OpenCore:

[SergeySlice]

Test please this version
CLOVERX64.efi.zip
SMBIOS->Trust=true

[ghost]

Test please this version CLOVERX64.efi.zip SMBIOS->Trust=true
Again no change. Here are the results.


[preboot.log](https://github.com/CloverHackyColor/CloverBootloader/files/13928611/preboot.log
And this is a SMBIOS dump before the patches.
smbios.txt.zip

[ghost]

I found my old preboot log, when the order of the dims was determined correctly still to Clover revision: 5119 (HEAD, commit a0948b2).
Motherboard Asus Z77-a Memory Samsung 4096MB 1333MHz
preboot.log

[jief666]

It's not the same computer, so it's hard to compare and see what is now different in Clover (therefore find the bug).
Can you try to boot a Clover 5119 on your new computer ?

[ghost]

It's not the same computer, so it's hard to compare and see what is now different in Clover (therefore find the bug). Can you try to boot a Clover 5119 on your new computer ?

Yes, this is my old computer, but later versions of Clover displayed the same memory error as on the new one. Therefore, I did not update Clover on it, considering that the Mac OS would not be updated either. Now my son plays games previous years on it, since it is still quite powerful for this.

[jief666]

Slice did some modification regarding that, Try this clover : CloverX64-2024-01-15-18-47-28-8697e93-jief.zip.

[ghost]

Slice did some modification regarding that, Try this clover : CloverX64-2024-01-15-18-47-28-8697e93-jief.zip.

Without changes.
preboot.log

[YBronst]

Due to glitches, I was forced to re-create my profile. I apologize for any inconvenience!

[jief666]

@YBronst Sorry, I but I think this fix is beyond my current skill... Let's see what Slice will do.

[YBronst]

Slice writes that he cannot fix what he cannot reproduce.

[jief666]

It's possible by asking to do a lot of test and generates a lot of debug log. But since it's only cosmetic, I'm guessing it's a lot of time for something we almost never look at (system information).
Sorry.

[YBronst]

It's possible by asking to do a lot of test and generates a lot of debug log. But since it's only cosmetic, I'm guessing it's a lot of time for something we almost never look at (system information). Sorry.

Yes, this is a cosmetic problem. I would just like to bring Clover to the level of OpenСore.

[jief666]

Yes, me too. But the quick look I took made me realize I know almost nothing about SMBIOS etc. So, In the time I have, I can't do it sorry.

[YBronst]

Yes, me too. But the quick look I took made me realize I know almost nothing about SMBIOS etc. So, In the time I have, I can't do it sorry.

Could you get Slice to fix it?