Jump to content

Chameleon RC4 is out!

Poco

By Poco,
in Front Page News and Rumors

 Share
1,054 posts in this topic

Recommended Posts

  • 3 weeks later...
rcfa
rcfa
Posted
Posted
You're all welcome, I didn't expect that the fix would get so many enthusiastic greetings ouside the P55 mobos thread,

 

but the merit goes to the chameleon and the PCEFI10.5 teams, I just integrated what I still found superior in PCEFI10.5 into this great chameleon RC4 release ;)

 

Concerning the itunes litlle side effect, it probably comes from the fact that since RC4, a new smbios system-id is added,

this UUID makes obsolete the need of kexts like PlatformUUID.kext, but as it defines a new UUID, some applications thinks you're running them from a new system, that make sense and should not be a problem.

 

How does the UUID get determined? The reason I ask is that I can't have it "randomly" change on me in the future, too much depends on it (anything form TimeMachine backups, mobileMe syncing etc.)

Also, since my computer has a real hardware UUID in the BIOS, it would be great if one could either retrieve that UUID out of the BIOS and use it, or if there were a way to override the UUID with a user-supplied one, as a parametern in SMBIOS.plist.

 

Anything like that possible?

 

Thanks!

Link to comment
Share on other sites
drule
drule
Posted
Posted

Is the following possible?

 

Dual-boot system OSX and WinXP. With a normal boot, and no keyboard interaction, the system boots into OSX. To boot into WinXP you must hit key during boot-up and select from menu (second menu choice).

 

While in OSX can one execute a script, or set a flag in Chameleon, that after shutting down the system will then boot into WinXP without the need for any keyboard interaction?

Link to comment
Share on other sites
Azimutz
Azimutz
Posted
Posted

@rcfa: the Chameleon trunk version tries to read the UUID from the "BIOS" and uses it if it finds one. Works fine on my machine.. UUID is always the same. One of the reasons why i ain't going back to RC4 :lol:

 

@drule: set a Timeout and a Default Partition on Boot.plist. Read the Help file.

Link to comment
Share on other sites
drule
drule
Posted
Posted
@drule: set a Timeout and a Default Partition on Boot.plist. Read the Help file.

 

I think you misunderstood what I was asking. I would like to boot into the non-default partition occasionally, without having to change it via the keyboard.

 

So if the default partition is OSX, every time I start the computer it will go into OSX without intervention. But I'd like to be able to set a flag or something in OSX, hit restart, go do something away from the computer, and when I return it will have booted into the non-default partition - but this wouldn't be a regular thing, just a "once in a while" type reboot.

 

Unless you are suggesting to create a script which will change the default partition in Boot.plist? I suppose that would be an option.

 

I'll check the help file.

Link to comment
Share on other sites
drule
drule
Posted
Posted
Xou could use the chameleon prefpane for changing the deafult partition

 

So I can use the pref. pane setting, within OSX, to set which partition to boot into before shutting down or restarting? If so, that's all I need. Thanks.

 

P.s. As you can see I haven't consulted the help yet, as I haven't installed the latest version of Chameleon yet, or SL for that matter, will be doing it this weekend. Thanks for all the help.

Link to comment
Share on other sites
Azimutz
Azimutz
Posted
Posted

@Drule, i think didn't misunderstood, i told you what's possible to do. Unless i'm missing something (it's always possible), all the Pref Pane does is edit the Boot.plist adding the "Default Partition" key, just like if you edit it your self. This will be permanent.. if i did understand you were inquiring about a "one time" option!? The only options that can be considered temporary are the flags we can type at the prompt, another kernel, a debug flag, different dsdt.aml, override a exist flag etc... In the case of Default Partition this doesn't make sense, obviously.

Probably will be an option in the future, with the Praference Pane :) who knows...

Here is a link for the Help file on Chameleon Repo:

http://forge.voodooprojects.org/p/chameleo...oc/BootHelp.txt

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
I confirm this "issue" same for me too

 

numkeypad not work with AsereBNL v1.1.9 (I try inside firefox 3.5.8)

numkeypad work with Chameleon RC5 pre8 (I try inside firefox 3.5.8)

 

Fabio

 

Hi

 

No numkeypad problems here with either AsereBNK 1.1.9 or pre8

 

However both are showing my memory in sys prof' to be 6GB - I only have 4GB !

 

Any ideas?

 

Cheers

D.

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
Did you remove all the memory info from your smbios.plist ?

 

yep!

 

yep!

 

I've just gone back to RC4 with my old smbios with RAM details and it's exactly the same! Must be this MSI board.

 

My second 2GB bank of RAM is seen as 4GB, can't believe I've only just seen this ..

 

post-275122-1270321650_thumb.png

 

D,

Link to comment
Share on other sites
Beerkex'd
Beerkex'd
Posted
Posted
No numkeypad problems here with either AsereBNK 1.1.9

Same here, numpad is fine with AsereBLN 1.1.9. I have Logitech Control Center installed though.

I have a different problem: OS X does not remember my keyboard layout setting - I have to keep selecting it in every app I use, all the time. I wonder if that's what Netkas is talking about in the release blurb for PCI EFI 10.6: http://netkas.org/?p=372

However both are showing my memory in sys prof' to be 6GB - I only have 4GB !

Try dumping your DMI info with this tool

http://www.insanelymac.com/forum/index.php?showtopic=153582

Maybe it'll give some clues, who knows.

Link to comment
Share on other sites
FKA
FKA
Posted
Posted

Thanks for the tip ..

 

Can see a 4GB and 2GB blocks .

 

Handle 0x002D, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 4 GB
Error Information Handle: 0x002E
Number Of Devices: 4

Handle 0x002E, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Bad Read
Granularity: Device Level
Operation: Read
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x002F, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Array Handle: 0x002D
Partition Width: 0

Handle 0x0030, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x002D
Error Information Handle: 0x0031
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: BANK0
Type: DDR2
Type Detail: Synchronous
Speed: 800 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00001020
Asset Tag: AssetTagNum0
Part Number: 996580X

Handle 0x0031, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Bad Read
Granularity: Device Level
Operation: Read
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x0032, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x0030
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 1
Interleaved Data Depth: 1

Handle 0x0033, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x002D
Error Information Handle: 0x0034
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM2
Bank Locator: BANK1
Type: DDR2
Type Detail: Unknown
Speed: 800 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00003021
Asset Tag: AssetTagNum1
Part Number: 996580X

Handle 0x0034, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Bad Read
Granularity: Device Level
Operation: Read
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x0035, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000000003FF
Range Size: 1 kB
Physical Device Handle: 0x0033
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 1
Interleaved Data Depth: 1

Handle 0x0036, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x002D
Error Information Handle: 0x0037
Total Width: 64 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: DIMM
Set: None
Locator: DIMM3
Bank Locator: BANK2
Type: DDR2
Type Detail: Synchronous
Speed: 800 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00003021
Asset Tag: AssetTagNum2
Part Number: 996580X

Handle 0x0037, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Bad Read
Granularity: Device Level
Operation: Read
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x0038, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x0017FFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x0036
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 1
Interleaved Data Depth: 1

Handle 0x0039, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x002D
Error Information Handle: 0x003A
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM4
Bank Locator: BANK3
Type: DDR2
Type Detail: Unknown
Speed: 800 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00003021
Asset Tag: AssetTagNum3
Part Number: N/A

Handle 0x003A, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Bad Read
Granularity: Device Level
Operation: Read
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x003B, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000000003FF
Range Size: 1 kB
Physical Device Handle: 0x0039
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 1
Interleaved Data Depth: 1

 

D

 

I wonder if that's what Netkas is talking about in the release blurb for PCI EFI 10.6: http://netkas.org/?p=372

 

could be.

Link to comment
Share on other sites
Beerkex'd
Beerkex'd
Posted
Posted

wow, that looks really strange.

 

According to the dump, the sticks in slots 2, 3 and 4 have the same serial number (impossible!) but it looks like slots 2 and 4 are unpopulated?

 

What's the actual, physical layout, how many modules, which slots are populated and with what size sticks?

 

2GB sticks in slot 1 and 3, right?

Link to comment
Share on other sites
Beerkex'd
Beerkex'd
Posted
Posted

Could there be a defect in the second RAM stick's SPD programming? What happens if you swap the two sticks?

 

The empty slots 2 and 4 get a serial number - the same as the stick in slot 3 - and also has the manufacturer listed.

The empty slot 2 has a part number listed as well. But both slots are listed as unpopulated :-)

 

So the most buggy readout comes from the empty slot 2 (ignoring the phantom 2GB in slot 3!)

 

What happens if you plug your RAM into slots 2 and 4 instead?

 

Maybe it's something in your DSDT? Could it have something to do with this code:

http://www.insanelymac.com/forum/index.php...t&p=1431895

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
Could there be a defect in the second RAM stick's SPD programming? What happens if you swap the two sticks?

 

The empty slots 2 and 4 get a serial number - the same as the stick in slot 3 - and also has the manufacturer listed.

The empty slot 2 has a part number listed as well. But both slots are listed as unpopulated :-)

 

So the most buggy readout comes from the empty slot 2 (ignoring the phantom 2GB in slot 3!)

 

What happens if you plug your RAM into slots 2 and 4 instead?

 

Maybe it's something in your DSDT? Could it have something to do with this code:

http://www.insanelymac.com/forum/index.php...t&p=1431895

 

stuck at work ... I'll have a mess around later . Removing the mem device from dsdt may be the way forward if there is no fault with the sticks, I'm pretty sure there isn't!

 

Cheers

D.

Link to comment
Share on other sites
FKA
FKA
Posted
Posted
stuck at work ... I'll have a mess around later . Removing the mem device from dsdt may be the way forward if there is no fault with the sticks, I'm pretty sure there isn't!

 

Cheers

D.

 

removing Device (MEM ... has made no difference!

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