Jump to content

Clover Problems and Solutions

ErmaC

By ErmaC,
in Clover Development

 Share
3205 posts in this topic

Recommended Posts

Needy
Needy
Posted
Posted

Strange issue. It seems to be a bug of my compiler (Xcode 4.4.1 - strange that it works at all!). There is impossible to use address of global variables as a parameters of global functions (gBS->xxx).

Now it is OK.

3:564  0:000  ScanSPD() start
3:564  0:000  SMBus device : 8086 27DA class=0C0500 status=Success
3:564  0:000  SMBus CmdReg: 0x1
3:564  0:000  Scanning SMBus [8086:27DA], mmio: 0x0, ioport: 0x500, hostc: 0x1
3:564  0:000  Slots to scan [8]...
3:568  0:003  SPD[0]: Type 8 @0x50
3:681  0:112  DDR speed 800MHz
3:681  0:000  Slot: 0 Type 19 2048MB 800MHz Vendor=Kingston PartNo= SerialNo=0501030C0A040503
3:685  0:004  SPD[2]: Type 8 @0x52
3:794  0:108  DDR speed 800MHz
3:794  0:000  Slot: 2 Type 19 2048MB 800MHz Vendor=Samsung PartNo=M378T5663SH3-CF73S SerialNo=04050709030D0003
3:799  0:005  ScanSPD() end

Committed to 3528.

What is mean "Windows"? I don't know it!.

 

Well done, Slice.  :) 

 

Revision 3528.

1:759  0:000  ScanSPD() start
1:759  0:000  SMBus device : 8086 27DA class=0C0500 status=Success
1:759  0:000  SMBus CmdReg: 0x1
1:759  0:000  Scanning SMBus [8086:27DA], mmio: 0x0, ioport: 0x500, hostc: 0x1
1:759  0:000  Slots to scan [8]...
1:763  0:003  SPD[0]: Type 8 @0x50
1:887  0:123  DDR speed 800MHz
1:887  0:000  Slot: 0 Type 19 2048MB 800MHz Vendor=A-DATA Technology PartNo= SerialNo=0000000000000000
1:891  0:004  SPD[2]: Type 8 @0x52
2:004  0:112  DDR speed 800MHz
2:004  0:000  Slot: 2 Type 19 2048MB 800MHz Vendor=Kingston PartNo= SerialNo=0B0F000E0E0B0305
2:009  0:005  ScanSPD() end

Furthermore, the information in "Windows"  :D , is correct except the memory type, which is Unknown.

 

Огромное спасибо.

post-1378824-0-49259900-1463398588_thumb.png

Needy
Needy
Posted
Posted

 

3528 isn't good for me

0:303  0:000  ScanSPD() start
0:304  0:000  SMBus CmdReg: 0x1
0:304  0:000  Scanning SMBus [8086:8D22], mmio: 0xFB235004, ioport: 0x580, hostc: 0x1
0:304  0:000  Slots to scan [8]...
0:305  0:001  ScanSPD() end

Did you build it? If so, did you update the source code?

 

Best regards.

Slice
Slice
Posted
Posted

 

3528 isn't good for me

0:303  0:000  ScanSPD() start
0:304  0:000  SMBus CmdReg: 0x1
0:304  0:000  Scanning SMBus [8086:8D22], mmio: 0xFB235004, ioport: 0x580, hostc: 0x1
0:304  0:000  Slots to scan [8]...
0:305  0:001  ScanSPD() end

There is wrong boot.log.

Revision 3528 must contain one new line

1:759  0:000  SMBus device : 8086 27DA class=0C0500 status=Success

Well done, Slice.  :) 

 

Revision 3528.

1:759  0:000  ScanSPD() start
1:759  0:000  SMBus device : 8086 27DA class=0C0500 status=Success
1:759  0:000  SMBus CmdReg: 0x1
1:759  0:000  Scanning SMBus [8086:27DA], mmio: 0x0, ioport: 0x500, hostc: 0x1
1:759  0:000  Slots to scan [8]...
1:763  0:003  SPD[0]: Type 8 @0x50
1:887  0:123  DDR speed 800MHz
1:887  0:000  Slot: 0 Type 19 2048MB 800MHz Vendor=A-DATA Technology PartNo= SerialNo=0000000000000000
1:891  0:004  SPD[2]: Type 8 @0x52
2:004  0:112  DDR speed 800MHz
2:004  0:000  Slot: 2 Type 19 2048MB 800MHz Vendor=Kingston PartNo= SerialNo=0B0F000E0E0B0305
2:009  0:005  ScanSPD() end

Furthermore, the information in "Windows"  :D , is correct except the memory type, which is Unknown.

 

Огромное спасибо.

Update Windows!

Clover has no relation to memory type detection in Windows.

Needy
Needy
Posted
Posted

There is wrong boot.log.

Revision 3528 must contain one new line

1:759  0:000  SMBus device : 8086 27DA class=0C0500 status=Success
Update Windows!

Clover has no relation to memory type detection in Windows.

Shall I write a new version of Windows? ? As I am using the latest one.

 

That's what you said last time. And it turns out that the code in clover's repository was the reason.

 

Well, clover does not affect the Windows boot, but the "UEFI firmware" that is included in the repository surely does.

 

However, what was done in r. 3528 is quite enough, indeed.

 

Best regards.

smolderas
smolderas
Posted
Posted

Well done, Slice.  :) 

 

Revision 3528.

1:759  0:000  ScanSPD() start
1:759  0:000  SMBus device : 8086 27DA class=0C0500 status=Success
1:759  0:000  SMBus CmdReg: 0x1
1:759  0:000  Scanning SMBus [8086:27DA], mmio: 0x0, ioport: 0x500, hostc: 0x1
1:759  0:000  Slots to scan [8]...
1:763  0:003  SPD[0]: Type 8 @0x50
1:887  0:123  DDR speed 800MHz
1:887  0:000  Slot: 0 Type 19 2048MB 800MHz Vendor=A-DATA Technology PartNo= SerialNo=0000000000000000
1:891  0:004  SPD[2]: Type 8 @0x52
2:004  0:112  DDR speed 800MHz
2:004  0:000  Slot: 2 Type 19 2048MB 800MHz Vendor=Kingston PartNo= SerialNo=0B0F000E0E0B0305
2:009  0:005  ScanSPD() end

Furthermore, the information in "Windows"  :D , is correct except the memory type, which is Unknown.

 

Огромное спасибо.

The default windows bootloader shows for me "unknown" either. It has nothing to do with clover...

Slice
Slice
Posted
Posted

 

Well, clover does not affect the Windows boot, but the "UEFI firmware" that is included in the repository surely does.

 

 

Can you show that Windows booted by Clover shows other hardware information then booted directly from BIOS?

Fljagd
Fljagd
Posted
Posted

There is wrong boot.log.

Revision 3528 must contain one new line

I confirm I made a mistake

now with 3529

0:304  0:000  ScanSPD() start
0:304  0:000  SMBus device : 8086 8D22 class=0C0500 status=Success
0:304  0:000  SMBus CmdReg: 0x1
0:304  0:000  Scanning SMBus [8086:8D22], mmio: 0xFB235004, ioport: 0x580, hostc: 0x1
0:304  0:000  Slots to scan [8]...
0:305  0:001  ScanSPD() end
joevt
joevt
Posted
Posted

I see we are using the same build options but -n3 instead of -n9 correspond to different CPU. My CPU has only two cores (3 = # cores + 1).

And I compiled under 10.7.5 with Xcode 4.4.1. We can expect that the result will be different so why I was asking about problem with my compilation.

 

Other differences looks like different sources. Your source 3469 is really differ from my 3526. You should update before compare.

Right, I had posted result of failed --xcode5 build. I didn't realize I was still using my older build from --gcc49. I have to figure out why --xcode5 isn't working for me...

 

Below are 2 screenshots of task manager, I suppose you'll understand what those represent by the names.

In Windows, I see Speed, Slots, and Form factor and don't see Unknown. It's the same whether I boot from Clover 3526, or from the BIOS boot menu (skipping Clover). Maybe mine doesn't say Unknown because I have DDR4? I don't know what Unknown is supposed to mean, unless someone sees something other than Unknown and blank in that upper right corner.
joevt
joevt
Posted
Posted

now with 3529

0:304  0:000  ScanSPD() start
0:304  0:000  SMBus device : 8086 8D22 class=0C0500 status=Success
0:304  0:000  SMBus CmdReg: 0x1
0:304  0:000  Scanning SMBus [8086:8D22], mmio: 0xFB235004, ioport: 0x580, hostc: 0x1
0:304  0:000  Slots to scan [8]...
0:305  0:001  ScanSPD() end

 

This is the same problem reported by dgsga.

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-39?do=findComment&comment=2237624

 

Does your unpatched (origin) DSDT or other aml files contain any more information about the SMBus device than his did?

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-40?do=findComment&comment=2238114

 

The smb_read_byte routine is not reading your spd for some reason. The first thing the code does is reset the SMBus controller. Then it waits for the device to be ready (the code does not note if the device starts as not ready - doing that might help indicate whether it's working properly).

 

When the device is ready, the code tries to read byte 2 of the spd (the DDR type field). This is where it fails for you. I would uncomment the read status change dbg messages (if (c != p) {...}). Maybe remove the read error check (if (c&4) {...}) and let it time out. Maybe increase the time out from 5 ms (although a read should take much less time than that).

 

Maybe the reset SMBus code needs additions. Maybe we need to start reading from byte 0, or use a different read command. If your DSDT has read/write methods for the SMBus, then we can compare those with the Clover code. If your DSDT does not, then we can compare DSDT methods from other motherboards, to see if the Clover code is missing anything.

Micky1979
Micky1979
Posted
Posted

@Fljagd did you use the Clover r3530 coming with Ares?

0:281  0:000  ScanSPD() start
0:281  0:000  SMBus device : 8086 1E22 class=0C0500 status=Success
0:281  0:000  SMBus CmdReg: 0x3
0:281  0:000  Scanning SMBus [8086:1E22], mmio: 0xD4615004, ioport: 0x5040, hostc: 0x1
0:281  0:000  Slots to scan [8]...
0:282  0:000  SPD[0]: Type 11 @0x50
0:301  0:019  Not using XMP because it is not present
0:301  0:000  DDR speed 1600MHz
0:301  0:000  Slot: 0 Type 24 4096MB 1600MHz Vendor=Micron Technology PartNo=16KTF51264HZ-1G6M1M1 SerialNo=0E0A07000D030301
0:301  0:000  SPD[2]: Type 11 @0x52
0:320  0:019  Not using XMP because it is not present
0:320  0:000  DDR speed 1600MHz
0:320  0:000  Slot: 2 Type 24 4096MB 1600MHz Vendor=Micron Technology PartNo=16KTF51264HZ-1G6M1M1 SerialNo=0E0A07000D03020F
0:321  0:000  ScanSPD() end
joevt
joevt
Posted
Posted

@Fljagd did you use the Clover r3530 coming with Ares?

I believe the problem is the same as the one reported by dgsga. They both have the 8086:8D22 SMBus Controller. I have not been able to find an example of a log that reports a successful read of the spd using that device, as I mentioned before in #772.

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-39?do=findComment&comment=2237663

 

There may also be a problem with 8086:1D22 and 8086:1D70 devices. If anyone has those devices, post your ScanSPD results here. The solution for those may be the same as for 8086:8D22 (if one is found...).

Slice
Slice
Posted
Posted

I compiled and edk2 updated itself and prompted me for a conflict. Which one is correct to select, TC or MC?

Always MC

I believe the problem is the same as the one reported by dgsga. They both have the 8086:8D22 SMBus Controller. I have not been able to find an example of a log that reports a successful read of the spd using that device, as I mentioned before in #772.

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-39?do=findComment&comment=2237663

 

There may also be a problem with 8086:1D22 and 8086:1D70 devices. If anyone has those devices, post your ScanSPD results here. The solution for those may be the same as for 8086:8D22 (if one is found...).

May be timeouts?

There is a check

    t1 = AsmReadTsc(); //rdtsc(l1, h1);
    while ( IoRead8(base + SMBHSTSTS) & 0x01) {   // wait until host is not busy
      t2 = AsmReadTsc(); //rdtsc(l2, h2);
      t = DivU64x64Remainder((t2 - t1),
                             DivU64x32(gCPUStructure.TSCFrequency, 1000),
                             0);
      if (t > 5) {
        DBG("host is busy for too long for byte %2X:%d!\n", adr, cmd);
        return 0xFF;                  // break
      }
    }

next cycle no such check.

 

We can change 1000 -> 200 to test.

  • Like 1
calibre™
calibre™
Posted
Posted 
Build with: [Args: ./ebuild.sh -xcode5 -mc | Command: build -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -D CLANG -p Clover/Clover.dsc -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.11.5 | XCODE: 7.3.1]

UEFI ok, boot6 ok, boot7 unfurtunately crash:

attachicon.gif20160509_211118.jpg

rev 3513

install log

 

 

Backing up EFI files

Backing up stage2 file /Volumes/Pandora Installer/EFIROOTDIR/boot  to /Volumes/Pandora Installer/EFI-Backups/r3513/2016-05-09-21h05/boot
Backing up /Volumes/Pandora Installer/EFIROOTDIR/EFI folder to /Volumes/Pandora Installer/EFI-Backups/r3513/2016-05-09-21h05/EFI
No Active Partition

Stage 0 - Writting boot0af to /dev/disk2
/Volumes/Pandora Installer/usr/local/bin/fdisk440 -u -f /Volumes/Pandora Installer/usr/standalone/i386/boot0af -y /dev/disk2

Stage 1 - Writting boot1f32 to /dev/rdisk2s1
dd if=/dev/rdisk2s1 count=1 bs=512 of=/tmp/origbs
boot volume format is FAT32
cp /tmp/boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=/tmp/newbs of=/dev/rdisk2s1

Stage 2 - Written boot7 (x64) to /Volumes/ESP/boot

======================================================
=========== Clover EFI Installation Finish ===========
======================================================

 

 

EDIT

nasm logs:

 

 

nasm configure log:

configure: WARNING: No acsciidoc package found
configure: WARNING: No xmlto package found

nasm make log

warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.
warning: unknown warning option '-Wno-pedantic-ms-format'; did you mean '-Wno-pedantic'? [-Wunknown-warning-option]
warning: unknown warning option '-Wc90-c99-compat'; did you mean '-Wc99-compat'? [-Wunknown-warning-option]
2 warnings generated.

 

 

 

Hi Mickey1979

this has been fixed?

Micky1979
Micky1979
Posted
Posted

I believe the problem is the same as the one reported by dgsga. They both have the 8086:8D22 SMBus Controller. I have not been able to find an example of a log that reports a successful read of the spd using that device, as I mentioned before in #772.

http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-39?do=findComment&comment=2237663

 

There may also be a problem with 8086:1D22 and 8086:1D70 devices. If anyone has those devices, post your ScanSPD results here. The solution for those may be the same as for 8086:8D22 (if one is found...).

I'v asked @Fljagd because I know He use Pandora. (but fortunately he told me that the build used was not mine, and is compiled from source as He already said, using his method)

Hi Mickey1979

this has been fixed?

Sure! This is the latest script I use: CloverBuilder.command.zip

Is done following Slice-Zenith432 advices discussed here. If you want to try, please delete or backup the src folder.

This v2.1 automatically add the --no-lto flag with XCODE5 toolchain when Xcode version is older than 7.3. I tested it only with Xcode 7.3 onward in EC, and offcourse also with gnu ccc too (4.9 and 6.1)

Zenith432
Zenith432
Posted
Posted

Slice:

 

The crash experienced by calibre comes from GetTagCount() in rEFIt_UEFI/Platform/plist.c...

INTN GetTagCount( TagPtr dict )
{
	INTN count = 0;
	TagPtr tagList, tag;
  
  if (dict->type != kTagTypeDict && dict->type != kTagTypeArray) {
    return 0;
  }
	tag = 0;
  tagList = dict->tag;
The value in ESI 0xFFFFFFFF is dict->tag. I've searched the code in plist.c, and I see it using NULL to mark this field as having no value - but I don't see how it could possibly get assigned the value 0xFFFFFFFF. So I'm not sure what to do about it.

 

[Note: the instruction that crashes "cmp dword [esi], 2" is the comparison tag->type != kTagTypeKey down the code]

 Share
Go to topic listing
×
×
  • Create New...