Jump to content

Chameleon 2.4svn Official PKG Installer


ErmaC
 Share

4,261 posts in this topic

Recommended Posts

After update boot loader can't boot anymore !

 

system 10.10.4 (14E17e) - MacPro 6.1

 

rev2686 is last that works fine

rev2698 / 2700 can't boot

 

Pls provide your machine spec.

 

ErmaC

Link to comment
Share on other sites

Pls provide your machine spec.

 

ErmaC

ProductName  : Mac OS X ProductVersion: 10.10.4 BuildVersion: 14E17e

Kernel       : Darwin Kernel Version 14.4.0: Tue May 5 14:17:52 PDT 2015
Model ID     : MacPro6,1 KernelMode: x86_64
CPU TYPE     : Intel® Core i5-4440 CPU @ 3.10GHz
CPU ID       : Ox306C3 (198339) 
Cores        : 4 Cores, 4 Threads @ 3099MHz Bus: 6275MHz FSB: 25100MHz
Caches       : L1i:32Kb L1d:32Kb L2:256Kb L3:6144Kb

 

MB: ASROCK Z87 Extreme3

Graphics: NVIDIA GT740 2Gb

RAM: 2x 8192MB (DDR3 SDRAM) 1600MHz Vendor=Crucial Technology

Link to comment
Share on other sites

 

 

Cores        : 4 Cores, 4 Threads @ 3099MHz Bus: 6275MHz FSB: 25100MHz

MB: ASROCK Z87 Extreme3

Graphics: NVIDIA GT740 2Gb

RAM: 2x 8192MB (DDR3 SDRAM) 1600MHz Vendor=Crucial Technology

 

Bus: 6275MHz FSB: 25100MHz -- is wrong . Should how example Bus: 133MHz FSB: 1333MHz

  • Like 1
Link to comment
Share on other sites

for me doesn't work.. 
I've just copied boot in "/" but like last public rev... 
doesn't boot... seems like a graphics problem

 

I use my machine for audio & video edit so i didn't use internal audio but I did a test.
I install AppleHDA.kext patched and now I can boot normally with 2702 Test rev. 

  • Like 1
Link to comment
Share on other sites

for me doesn't work.. 

I've just copied boot in "/" but like last public rev... 

doesn't boot... seems like a graphics problem

 

I use my machine for audio & video edit so i didn't use internal audio but I did a test.

I install AppleHDA.kext patched and now I can boot normally with 2702 Test rev. 

Ok , but how show Bus and Fsb ? 

Link to comment
Share on other sites

I read this from kext utility and I think that it's wrong ... there is another way to read it ? Sorry for this lame questions 

You can write in terminal :

bdmesg 

and search External Clock and Speed .

Link to comment
Share on other sites

You can write in terminal :

bdmesg 

and search External Clock and Speed .

Chameleon 2.3svn (svn-r2702 ErmaC Test v1) [2015-05-24 13:16:04]

Logging started: 2015/05/24, 17:21:33

[ CPU INFO ]

Sticking with [bCLK: 99Mhz, Bus-Ratio: 31]

 

.....

Processor Information

Socket Designation: CPUSocket

Type: Central Processor

Family: 0xCD

Manufacturer: Intel

ID: 0x306C3

Version: Intel® Core i5-4440 CPU @ 3.10GHz

External Clock: 0 MHz

Max Speed: 3099 MHz

Current Speed: 3100 MHz

Upgrade: Socket BGA1155

Serial Number: Not Specified

Asset Tag: Fill By OEM

Part Number: Fill By OEM

Core Count: 4

Core Enabled: 4

 

Thread Count: 4

Link to comment
Share on other sites

same result

 

External Clock: 0 MHz

Max Speed: 3098 MHz

Current Speed: 3100 MHz

what this error can affects ?

Yes affects, this for work system . 

Maybe is wrong is bootloader . You can test old's boot ... 

Link to comment
Share on other sites

  • 2 weeks later...

"name" not a kext
"Kernel-__SYMTAB" not a kext

how to delete these messages, create by "Add the symtab to the memory-map." /i386/libsaio/load.c
 

static long DecodeSymbolTable (long cmdBase)
 

AllocateMemoryRange ("Kernel -__ symtab" gSymbolTableAddr, gSymbolTableSize, -1);

when the kernel at boot kicks in
 

Link to comment
Share on other sites

ntfs_fixup: magic does not match! = 454c4946

Why this error every boot "ntfs_fixup: magic does not match! = 454c4946"

which here comes from a windows 8.1 partition
 

Link to comment
Share on other sites

"name" not a kext

"Kernel-__SYMTAB" not a kext

 

how to delete these messages, create by "Add the symtab to the memory-map." /i386/libsaio/load.c

 

 

The short answer is that the message is harmless and you can ignore it.

 

The long answer is that it's indirectly caused by the KernelPatcher module and/or the FileNVRAM module These modules enable a code path in the kernel that allows kexts to be loaded even though you're loading a prelinked kernel. This is normally disabled by Apple, however it's needed to inject kexts during bootup w/o regenerating the prelinked kernel. If you take a look at the XNU source code, the kext loading code that gets executed in this case parses all sections in the memory map. If these sections are not kexts it throws the warning and skips over them. Ideally the kernel should be modified to only parse kexts that start with the Kext or MKext name (all kexts that are injected by the booloader start with this, I believe). I've never bothered to file a bug report with apple about it, because it's harmless and they probably don't care about it.

  • Like 2
Link to comment
Share on other sites

 Share

×
×
  • Create New...