Jump to content

Chameleon RC4 is out!

Poco

By Poco

 Share

Chameleon Logo

 

In addition to the many patches a fixes included in this new version, a few new features for the bootloader made this cut.

We’re back again with this new RC4 version. Since the last RC3 release, we received many patches and fixes, and also backported some important features like ATI graphics device injection, EFI64 tables and PCI root configuration. Also added a new boot option for hiding unwanted foreign partitions from the boot menu.

 

Hide Partition

Using this option you can enumerate all your partitions what you would like to remove from the boot menu, the syntax is similar to the Default Partition option but here you can specify many volumes in your com.apple.Boot.plist:

 

 

PciRoot

This is a similar option what you can find in PC_EFI, but we’re doing this a bit different: The default value is still 0 but you can set to any arbitrary value.

 

Visit http://chameleon.osx86.hu for more info and download links.

 

Credit goes to:

Developers: Crazor, Dense, fassl, iNDi, Kabyl, kaitek, mackerintel, mercurysquad, munky, Turbo, zef

Thanks to: bumby, cosmo1t, dfe, Galaxy, kalyway, netkas, sckevyn, XyZ

 

Installer

Dr.Hurt has put together an installer package which is available for download here

As mentioned please do not report problems related to the installer to the Voodoo Team

 Share
Go to articles

User Feedback

Recommended Comments



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

 

So everything is OK if I have the sticks in slots 1 and 2 but in 1 and 3 the stick in 3 is shown as 4GB.

 

The duplicate serial numbers where from smbios I'd forgotten to take out when I went back to arsen's bootloader!

 

Here's the dump with Device (MEM .. or in my case ^^RMEM ... removed from DSDT, memory info injected by bootloader and no mem info in smbios.plist.

 

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: 801 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00000000
Asset Tag: AssetTagNum0
Part Number: 991580X

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: 801 MHz (1.2 ns)
Manufacturer: N/A
Serial Number: N/A
Asset Tag: AssetTagNum1
Part Number: N/A

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: 801 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00000000
Asset Tag: AssetTagNum2
Part Number: 991580X

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: 801 MHz (1.2 ns)
Manufacturer: N/A
Serial Number: N/A
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

 

EDIT - I've done some swapping around and it appears it's whichever stick I have in the B channel (furthest from CPU) is shown as 2x actual size.

 

I wnt to run dual channel so .....

 

D

Link to comment
Share on other sites
mikeetastic

Thanks a lot azimus.. last question, which branch should i use to test the latest and greatest?

 

and yes not much terminal knowledge.. really new too so i'm gonna try this while looking at prasys guide.

 

 

@mikeetastic, i'm assuming you have minimal Terminal knowledge :unsure:

Create a Folder some were called Chameleon (not mandatory).

Open Terminal, change dir to the Chameleon folder and checkout the trunk via svn with:

svn co http://forge.voodooprojects.org/svn/chameleon/trunk

the source will be on a folder named "trunk".

To checkout Prasys branch, for instance:

svn co http://forge.voodooprojects.org/svn/chameleon/branches/prasys

etc...

 

You can visit the repo at http://forge.voodooprojects.org

Link to comment
Share on other sites
FKA
Thanks a lot azimus.. last question, which branch should i use to test the latest and greatest?

 

and yes not much terminal knowledge.. really new too so i'm gonna try this while looking at prasys guide.

 

If you're not sure, personaly, I'd stick with the trunk.

Link to comment
Share on other sites
Azimutz

Yeah, follow FormerlyKnownAs's advice and do follow some guide. The trunk is pretty stable as is, at least on my system..

i use it all the time. Also learning my self :)

Svn support is already included on OS X, you just need the basic commands, checkout (co), update (up), help (?, h), etc...

For Terminal you'll also find plenty of stuff over Google. Just take time to learn some basic stuff and you'll be fine and learning

more in no time ;)

Link to comment
Share on other sites
FKA
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

 

 

 

could be.

 

Just resolved this:

 

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: 802 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00000000
Asset Tag: AssetTagNum0
Part Number: 991580X

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: 802 MHz (1.2 ns)
Manufacturer: N/A
Serial Number: N/A
Asset Tag: AssetTagNum1
Part Number: N/A

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: 2048 MB
Form Factor: DIMM
Set: None
Locator: DIMM3
Bank Locator: BANK2
Type: DDR2
Type Detail: Synchronous
Speed: 802 MHz (1.2 ns)
Manufacturer: Mushkin
Serial Number: 0x00000000
Asset Tag: AssetTagNum2
Part Number: 991580X

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: 0x000FFFFFFFF
Range Size: 2 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: 802 MHz (1.2 ns)
Manufacturer: N/A
Serial Number: N/A
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

Handle 0x003C, DMI type 22, 26 bytes
Portable Battery
Location: Left side of System
Manufacturer: Nikon Battery
Manufacture Date: 08/11/97
Serial Number: NI00123
Name: Nikon Ultra Plus
Chemistry: Nickel Cadmium
Design Capacity: Unknown
Design Voltage: Unknown
SBDS Version: SMART Ver 0123
Maximum Error: Unknown
OEM-specific Information: 0x00000000

 

On my MSI MB there is a setting under the Cell menu, sub DRAM, called Enhanced Setting.

It is meant to improve RAM OC capabilities but I'd read on the MSI forum that it actually lead to less stable system when OC'ing so I'd disabled it.

 

It needs to be enabled !!

 

D

Link to comment
Share on other sites
dgobe

Since 10.6.3 the system has the code to recognize Core i7/i5 as a CPU type.

 

EDIT:

 

You have to account for Gulftown in this cpu.c line

 

			/* Nehalem CPU model */
		if (p->CPU.Family == 0x06 && (p->CPU.Model == 0x1a || p->CPU.Model == 0x1e)) {

 

and also populate BrandString in the Platform structure unless there is another way to distinguish i7 from i5

 

smbios_patcher.c

static int sm_get_cputype (const char *name, int table_num)
{
const char *brandstring = NULL;

if (Platform.CPU.NoCores == 1) {
	return 0x0101;   // <01 01> Intel Core Solo?
} else if (Platform.CPU.NoCores == 2) {
	return 0x0301;   // <01 03> Intel Core 2 Duo
} else if (Platform.CPU.NoCores >= 4) {
	if (Platform.CPU.Model == 0x1a || Platform.CPU.Model == 0x1e || Platform.CPU.Model == 0x2c) {
		brandstring = strstr((const char*) &Platform.CPU.BrandString,"i7");
		if(brandstring != NULL) {
			return 0x0701;  // <01 07> Intel Core i7 1a=Bloomfield 1e=Lynnfield 2c=Gulftown
		} else {
			return 0x0601;  // <01 06> Intel Core i5
		}
	}
	return 0x0501;   // <01 05> Quad-Core Intel Xeon
} else {
	return 0x0301;   // Default to Core 2 Duo
}
}

 

You get the idea, just thought I'd bring it up if no one was aware of it already. That stuff may not work so I'll let the pros have at it...thanks

Link to comment
Share on other sites
THe KiNG
I switched to Chameleon, but there is one PCI card in system profiler. PCEFI shows two cards.

I have a PCI Ethernet Controller and Chameleon doesn't show that.

 

Screenshoot: http://bit.ly/9mDe2d

Any idea, why?

B/c PCEFI code is wrong, built-in Ethernet card(soldered on board) shouldn't show up on PCI cards in system profiler. only those that use PCI/PCI express slot.

Link to comment
Share on other sites
Detrich
B/c PCEFI code is wrong, built-in Ethernet card(soldered on board) shouldn't show up on PCI cards in system profiler. only those that use PCI/PCI express slot.

 

I think he talk about this ,so PCEFI is OK. :)

Link to comment
Share on other sites
cparm
B/c PCEFI code is wrong, built-in Ethernet card(soldered on board) shouldn't show up on PCI cards in system profiler. only those that use PCI/PCI express slot.

 

humm, i don't know,

i use a modded chameleon version and it also show my ethernet card in the pci section because i added a _sun entry in the (GIGE) section,

if he use dsdt maybe he should look into it :)

Link to comment
Share on other sites
leslieking
B/c PCEFI code is wrong, built-in Ethernet card(soldered on board)

I don't use built-in ethernet. I have a NetGear GA311M PCI LAN card.

There is not GIGE section in DSDT.

Link to comment
Share on other sites
THe KiNG

Built-in cards shouldn't show up on PCI Cards under system profiler, adding _SUN for soldered stuff is so WRONG, then why to inject built-in code if is on pci/pcie slot? LOL

 

If is about a PCI or PCIe card then things changes, it should show up on system profiler PCI section, but only if there is a _SUN added on DSDT to identify the slot number plus a check to see if the slot is empty or not(and not publish the pcibridge if empty), or booter can do the same if it can enumerate the slots correctly, most cases NOT(at least with actual code).

 

Apple can give you a free exampe in his DSDT's...

Link to comment
Share on other sites
leslieking
The King is right! And zolik, cross posting is rude :) check your same post on VoodooProject forums.

Calm down, dude. I just posted because I wanted a fast answer.

No, I'm not a cross poster. It's not my habit. I made a mistake and sorry!

 

Built-in cards shouldn't show up on PCI Cards under system profiler, adding _SUN for soldered stuff is so WRONG, then why to inject built-in code if is on pci/pcie slot? LOL

 

If is about a PCI or PCIe card then things changes, it should show up on system profiler PCI section, but only if there is a _SUN added on DSDT to identify the slot number plus a check to see if the slot is empty or not(and not publish the pcibridge if empty), or booter can do the same if it can enumerate the slots correctly, most cases NOT(at least with actual code).

 

Apple can give you a free exampe in his DSDT's...

Thank you very much!

Link to comment
Share on other sites
cparm
Built-in cards shouldn't show up on PCI Cards under system profiler, adding _SUN for soldered stuff is so WRONG, then why to inject built-in code if is on pci/pcie slot? LOL

 

only because it's possible to do ;)

Link to comment
Share on other sites
Azimutz

Zolik, i'm calm.. very calm! Belive me, i wont loose my sleep or have nightmares because of this. Next time i will just ignore.

A simple "i'm sorry" would have been enough, dude ;) now i'm pissed.. but calm...

Link to comment
Share on other sites
donkey

Hello guys,

 

I'm using Chameleon RC5 PreRelease 18 Build 112. I am using the restart fix and its great when it works but its a 50 50 chance that it works. Has anyone else experienced this?

 

Thanks!

D

Link to comment
Share on other sites
THe KiNG
only because it's possible to do :)

Adding _SUN on a built-in component kills the built-in feature, however you can still inject the built-in stuff but "apple" will see that component as external device and that is wrong...especial for network :P

Link to comment
Share on other sites
leslieking
Hello guys,

 

I'm using Chameleon RC5 PreRelease 18 Build 112. I am using the restart fix and its great when it works but its a 50 50 chance that it works. Has anyone else experienced this?

 

Thanks!

D

I'm using RC5 prerelease (trunk). I never had problems with restart.

 

Adding _SUN on a built-in component kills the built-in feature, however you can still inject the built-in stuff but "apple" will see that component as external device and that is wrong...especial for network ;)

Is it better to avoid _SUN for the PCI LAN adater? Or do you mean just "on-board" stuff? I'm totally confused.

post-66455-1271147089_thumb.jpg

Link to comment
Share on other sites

×
×
  • Create New...