Jump to content

Chameleon RC5 mode with mem detection enabled and automatic P-States & C-States generation for native power managment

kozlek

By kozlek,
in Chameleon

 Share
1,214 posts in this topic

Recommended Posts

rekursor
rekursor
Posted
Posted

Confirmed, there was also this(though it would it still work, it would be sometimes ugly)

I merged back your modification to the trunk :(

 

Here's r217:

boot_4.zip

It was a problem with Serial Number conversion to ASCII string in our latest revision. I've posted changes, should work now like in everest or asere's boot. Maybe only needed to refine conversion algo.
Link to comment
Share on other sites
zef
zef
Posted
Posted

Hey rek!

 

Very nice, the speed is reported as 1066MHz again, thanks :)

 

The serial gets better, let me post Everest's SPD results (it can't report the speed correctly :P):

 

[ DIMM1: Kingston 2G-UDIMM ]

 

Memory Module Properties:

Module Name Kingston 2G-UDIMM

Serial Number B5CC1B43h (1125895349)

Manufacture Date Week 11 / 2009

Module Size 2 GB (2 ranks, 8 banks)

Module Type Unbuffered DIMM

Memory Type DDR2 SDRAM

Memory Speed DDR2-800 (400 MHz)

Module Width 64 bit

Module Voltage SSTL 1.8

Error Detection Method None

Refresh Rate Reduced (7.8 us), Self-Refresh

 

Memory Timings:

@ 400 MHz 5-5-5-18 (CL-RCD-RP-RAS) / 23-51-3-6-3-3 (RC-RFC-RRD-WR-WTR-RTP)

@ 266 MHz 4-4-4-12 (CL-RCD-RP-RAS) / 16-34-2-4-2-2 (RC-RFC-RRD-WR-WTR-RTP)

@ 200 MHz 3-3-3-9 (CL-RCD-RP-RAS) / 12-26-2-3-2-2 (RC-RFC-RRD-WR-WTR-RTP)

 

Memory Module Features:

Analysis Probe Not Present

FET Switch External Disabled

Weak Driver Supported

 

[ DIMM3: Kingston 2G-UDIMM ]

 

Memory Module Properties:

Module Name Kingston 2G-UDIMM

Serial Number A4CC9B78h (2023476388)

Manufacture Date Week 11 / 2009

Module Size 2 GB (2 ranks, 8 banks)

Module Type Unbuffered DIMM

Memory Type DDR2 SDRAM

Memory Speed DDR2-800 (400 MHz)

Module Width 64 bit

Module Voltage SSTL 1.8

Error Detection Method None

Refresh Rate Reduced (7.8 us), Self-Refresh

 

Memory Timings:

@ 400 MHz 5-5-5-18 (CL-RCD-RP-RAS) / 23-51-3-6-3-3 (RC-RFC-RRD-WR-WTR-RTP)

@ 266 MHz 4-4-4-12 (CL-RCD-RP-RAS) / 16-34-2-4-2-2 (RC-RFC-RRD-WR-WTR-RTP)

@ 200 MHz 3-3-3-9 (CL-RCD-RP-RAS) / 12-26-2-3-2-2 (RC-RFC-RRD-WR-WTR-RTP)

 

Memory Module Features:

Analysis Probe Not Present

FET Switch External Disabled

Weak Driver Supported

 

Update:

Memory Slots:

 

ECC: Disabled

 

BANK0/DIMM0:

 

Size: 2 GB

Type: DDR2 SDRAM

Speed: 1066 MHz

Status: OK

Manufacturer: Kingston

Part Number: 2G-UDIMM

Serial Number: 431BCCB5

 

BANK2/DIMM2:

 

Size: 2 GB

Type: DDR2 SDRAM

Speed: 1066 MHz

Status: OK

Manufacturer: Kingston

Part Number: 2G-UDIMM

Serial Number: 789BCCA4

 

I think the serial number needs an endian conversion or maybe Everest needs that? How can we get a proof who's doing this correctly?

 

Sysprofiler's 431BCCB5 should be Everest's B5CC1B43 for DIMM0.

Sysprofiler's 789BCCA4 should be Everest's A4CC9B78 for DIMM1.

 

Very nice progress rek and Mozo :) Many thanks!

Link to comment
Share on other sites
Smith@@™
Smith@@™
Posted
Posted
Unfortunately, the OC speed can't be fixed with latest changes because it needs special (new) code addon to read the oc speed directly from the memory controller ...

 

i understand...

Link to comment
Share on other sites
scrax
scrax
Posted
Posted
The new version (download in the first post) resolves issue with improper ACPI CPU name detection causing not working C-States and/or P-States in some cases.

 

It's the problem I was having with the Scope (_PR) at line 300, isn't it?, I can confirm that now it works without moving it at the top of the DSDT!

 

thank you mozodojo!

 

now that speedStep is working good i'll post my memory recognition problems:

 

Slot memoria:

 ECC:	Disabilitato

Bank0/1/A0:

 Dimensioni:	2 GB
 Tipo:	DDR2 SDRAM
 Velocità:	800 MHz
 Stato:	OK
 Produttore:	N/A
 Codice prodotto:	N/A
 Numero di serie:	N/A

Bank2/3/A1:

 Dimensioni:	2 GB
 Tipo:	DDR2 SDRAM
 Velocità:	800 MHz
 Stato:	OK
 Produttore:	N/A
 Codice prodotto:	N/A
 Numero di serie:	N/A

 

this is what i get from rev204

now i'll test rev218 and report back if there are any differences.

Link to comment
Share on other sites
rekursor
rekursor
Posted
Posted

Litlle endian to big endian conversion should now happen in r221 :)

Hey rek!

...

Sysprofiler's 431BCCB5 should be Everest's B5CC1B43 for DIMM0.

Sysprofiler's 789BCCA4 should be Everest's A4CC9B78 for DIMM1.

 

Very nice progress rek and Mozo :) Many thanks!

Link to comment
Share on other sites
scrax
scrax
Posted
Posted

218 still no ram detected, let's go with 221 222 :)

 

Here the (unofficial and unsupported) installer I use: MozodojoCameleon2RC5r222.zip

 

EDIT;

WIth 222 at boot I can see:

 

Start Memory detection --->

 

<--- END memory detection

 

and of course still nothing recognized...

 

If there is somethink that I need to provide to help for finding out where is the roblem let me know.

Link to comment
Share on other sites
mm67
mm67
Posted
Posted

These memory sticks seem to have incorrect SPD information since all Windows programs also see them PC2-6400 sticks. Here for example Everest and Memset:

post-375259-1279986994_thumb.png

 

I guess the real speed would have to be read from somewhere else:

post-375259-1279987063_thumb.png

Link to comment
Share on other sites
mm67
mm67
Posted
Posted

In my case even reading EPP wouldn't help since that profile is for only 1066 MHz. There is a Windows program called spdtool, with that it's possible to change SPD information and set serial number for example. Maybe I'll try that with some old cheaper sticks.

Link to comment
Share on other sites
scrax
scrax
Posted
Posted
Hi all.

 

Too early to request an update to the Chameleon prefpanel adding new key flags?

 

Fabio

For now you can use Lizard with the custom options.

 

And this is a good time to bump my old request to add a similar option in the pref panel so it will work with any branch of chameleon not only with the official one.

Link to comment
Share on other sites
rekursor
rekursor
Posted
Posted

I'm incorporating a new algorithm for mem detection now featuring pci dram controller read,

Thanks to iNDi support, this was easy to incorporate,

 

Overclocking ram is soon handled ! (and much more in near future)

 

But I need your help for incorporating your recent chipset (I already handle lots of them)

 

if your pci host controller (id 0x600) is not in this list please report:

	{ 0x8086, 0x7190, "VMWare",	NULL, NULL, NULL },

{ 0x8086, 0x1A30, "i845",	NULL, NULL, NULL },

{ 0x8086, 0x2970, "i946PL/GZ",		setup_p35, get_fsb_i965,  get_timings_i965 },
{ 0x8086, 0x2990, "Q963/Q965",		setup_p35, get_fsb_i965,  get_timings_i965 },
{ 0x8086, 0x29A0, "P965/G965",		setup_p35, get_fsb_i965,  get_timings_i965 },

{ 0x8086, 0x2A00, "GM965/GL960",	setup_p35, get_fsb_im965, get_timings_im965 },
{ 0x8086, 0x2A10, "GME965/GLE960",	setup_p35, get_fsb_im965, get_timings_im965 },
{ 0x8086, 0x2A40, "PM/GM45/47",		setup_p35, get_fsb_im965, get_timings_im965 },	

{ 0x8086, 0x29B0, "Q35",			setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x29C0, "P35/G33",		setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x29D0, "Q33",			setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x29E0, "X38/X48",		setup_p35, get_fsb_i965,  get_timings_p35 },			
{ 0x8086, 0x2E00, "Eaglelake",		setup_p35, get_fsb_i965,  get_timings_p35 },
{ 0x8086, 0x2E10, "Q45/Q43",		setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x2E20, "P45/G45",		setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x2E30, "G41",			setup_p35, get_fsb_i965,  get_timings_p35 },

{ 0x8086, 0xD131, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },
{ 0x8086, 0x3400, "NHM IMC",		setup_nhm, get_fsb_nhm,	  get_timings_nhm },
{ 0x8086, 0x3401, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },
{ 0x8086, 0x3402, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },
{ 0x8086, 0x3403, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },	{ 0x8086, 0x1A30, "i845",	NULL, NULL, NULL },
{ 0x8086, 0x2970, "i946PL/GZ",		setup_p35, get_fsb_i965,  get_timings_i965 },
{ 0x8086, 0x2990, "Q963/Q965",		setup_p35, get_fsb_i965,  get_timings_i965 },
{ 0x8086, 0x29A0, "P965/G965",		setup_p35, get_fsb_i965,  get_timings_i965 },

{ 0x8086, 0x2A00, "GM965/GL960",	setup_p35, get_fsb_im965, get_timings_im965 },
{ 0x8086, 0x2A10, "GME965/GLE960",	setup_p35, get_fsb_im965, get_timings_im965 },
{ 0x8086, 0x2A40, "PM/GM45/47",		setup_p35, get_fsb_im965, get_timings_im965 },	

{ 0x8086, 0x29B0, "Q35",			setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x29C0, "P35/G33",		setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x29D0, "Q33",			setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x29E0, "X38/X48",		setup_p35, get_fsb_i965,  get_timings_p35 },			
{ 0x8086, 0x2E00, "Eaglelake",		setup_p35, get_fsb_i965,  get_timings_p35 },
{ 0x8086, 0x2E10, "Q45/Q43",		setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x2E20, "P45/G45",		setup_p35, get_fsb_i965,  get_timings_p35 },	
{ 0x8086, 0x2E30, "G41",			setup_p35, get_fsb_i965,  get_timings_p35 },

{ 0x8086, 0xD131, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },
{ 0x8086, 0x3400, "NHM IMC",		setup_nhm, get_fsb_nhm,	  get_timings_nhm },
{ 0x8086, 0x3401, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },
{ 0x8086, 0x3402, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },
{ 0x8086, 0x3403, "NHM IMC",		setup_nhm, get_fsb_nhm,   get_timings_nhm },

In order to check it easily use lspci (or EvoToolsX that uses it) and read the first line containing:

Host bridge [0600]

 

then copy and paste here your dev id (example: [8086:d131]) located at the end of the same line...

 

Thanks!

Link to comment
Share on other sites
scrax
scrax
Posted
Posted

00:00.0 Host bridge [0600]: nVidia Corporation MCP79 Host Bridge [10de:0a80] (rev b1)

 

 

MB: Zotac GF9300-D-E WIFI ITX rev1

CPU: Intel Q9300 @ 2.5GHz

 

For the next hour i'm here around, so if there will be something to test, i'm ready (and in irc) :);)

Link to comment
Share on other sites
Geenz
Geenz
Posted
Posted
The new version (download in the first post) resolves issue with improper ACPI CPU name detection causing not working C-States and/or P-States in some cases.

Still causing my system to reboot with GeneratePStates enabled. However, I did notice one thing while booting recently. The bootloader says that it failed to read *something* the moment I begin booting. Unfortunately, it goes by too fast for me to completely read it or take a picture of it.

 

Just to be safe, I checked my DSDT to make sure I wasn't putting my CPU's _CST or _PSS stuff in it.

Link to comment
Share on other sites
kellis
kellis
Posted
Posted
use lspci (or EvoToolsX that uses it) and read the first line containing:

Host bridge [0600]

 

then copy and paste here your dev id (example: [8086:d131]) located at the end of the same line...

Hi, I am not even seeing host 0600, here's what I have:

 

Mac-Pro:~ John$ lspci |grep -i host

00:00.0 Host bridge: Intel Corporation Unknown device d132 (rev 11)

05:00.2 SD Host controller: JMicron Technologies, Inc. Unknown device 2381

ff:00.0 Host bridge: Intel Corporation Unknown device 2c52 (rev 04)

ff:00.1 Host bridge: Intel Corporation Unknown device 2c81 (rev 04)

ff:02.0 Host bridge: Intel Corporation Unknown device 2c90 (rev 04)

ff:02.1 Host bridge: Intel Corporation Unknown device 2c91 (rev 04)

ff:03.0 Host bridge: Intel Corporation Unknown device 2c98 (rev 04)

ff:03.1 Host bridge: Intel Corporation Unknown device 2c99 (rev 04)

ff:03.4 Host bridge: Intel Corporation Unknown device 2c9c (rev 04)

ff:04.0 Host bridge: Intel Corporation Unknown device 2ca0 (rev 04)

ff:04.1 Host bridge: Intel Corporation Unknown device 2ca1 (rev 04)

ff:04.2 Host bridge: Intel Corporation Unknown device 2ca2 (rev 04)

ff:04.3 Host bridge: Intel Corporation Unknown device 2ca3 (rev 04)

ff:05.0 Host bridge: Intel Corporation Unknown device 2ca8 (rev 04)

ff:05.1 Host bridge: Intel Corporation Unknown device 2ca9 (rev 04)

ff:05.2 Host bridge: Intel Corporation Unknown device 2caa (rev 04)

ff:05.3 Host bridge: Intel Corporation Unknown device 2cab (rev 04)

 

is something really messed up with my system?

Link to comment
Share on other sites
rekursor
rekursor
Posted
Posted

it's the first line :)

so your chipset id is 8086:d132 -> not handled yet

 

I could possibly handle it if you give me you mobo exact reference and cpu used.

 

Thanks!

 

PS: please add your full config info to your signature when asking questions, it'll get much simpler for us to support you

 

-Rek

Link to comment
Share on other sites
scrax
scrax
Posted
Posted
Hi, I am not even seeing host 0600, here's what I have:

you need to use:

lspci -nn

 

if i don't remember wrong or click Lspci normal in EvoToolsX

 

@rek

I don't know if something was wrong with the downoad or extraction, but boot-5 for me don't load. now i'l retry

 

EDIT: posted together with rek.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...