Fix CPU Name with RestrictEvents

[Aluveitie]

The latest builds of Acidanthera's RestrictEvents also fixes AMD CPU names in About This Mac:



Required is just the latest build of the upcoming 1.0.2: RELEASE:

Builds

This also removes the need to map memory on MacPro7,1 SMBIOS:

Note
If your CPU is shown as Unknown on OC 0.6.7 or later try setting ProcessorType to 1537 for 6 cores or less and 3841 for 8 cores or higher in the config.plist under PlatformInfo > Generic.

 

[AudioGod]

i was just looking at that just this second on the git hub. Awesome. Are you using your memory map with it or are you now using the kext for your memory too now?

I don’t like the way the new memory mapping makes you have to map 4 slots of ram even if you only have two. It’s annoying and can cause the system to trip out every now and again. Ggggrrrrr lol

 

[Aluveitie]

Still using memory mapping. What do you mean by trip out?

 

[AudioGod]

Still using memory mapping. What do you mean by trip out?

When you only use two sticks or ram but have to map 4 sticks in the map (2 being dummy) it can sometimes try and use the dummy ram when it wakes from sleep and the system fails hard….lol
ive already reported to the Oc crew and they are blaming it on AMD and saying get two more sticks or ram instead…lol
charming

 

[Aluveitie]

I have two slots and mapped all 12, never experienced a crash after sleep.

 

[Shaneee]

Even with this I'm stuck with Unknown lol

 

[AudioGod]

I have two slots and mapped all 12, never experienced a crash after sleep.

It’s on the new 0.6.9 map.
It never happened to me until the other day and just after I updated 0.6.9 and the mapping.

 

[Aluveitie]

Good to know when I upgrade to 0.6.9 once it is released…

 

[AudioGod]

just a thought but if RestricEvents is in use and the memory map is correct with it and no longer showing an error then wouldn’t it be better to drop the mapping anyway? (That’s if the memory is correct everywhere with just the kext of course)

 

[AudioGod]

I will try it out in a moment and find out.
did you add a boot argument for the cpu rename or is the kext doing it all for you?

 

[Aluveitie]

I’ve added the boot-arg but as I’ve read it should not be necessary on AMD.

 

[AudioGod]

I shall experiment with it and find out. Il report back soon.

 

[AudioGod]

@Shaneee add a boot argument

• revcpuname=value custom CPU brand string (max 48 characters, 20 or less recommended, taken from CPUID otherwise)

 

[Shaneee]

@Shaneee add a boot argument

• revcpuname=value custom CPU brand string (max 48 characters, 20 or less recommended, taken from CPUID otherwise)

Not sure how it would work with spaces. Although in theory without this it should still show as an Intel CPU. ProcessorType isn't set in PlatformInfo so I'm not sure what's going on.

Edit: Even with revcpuname=AMD it doesn't change lol

 

[AudioGod]

Yeah same thing here actually...lol
Im being dumb.

@Aluveitie What boot argument did you add to get it going?

Ive tested the memory without my map and its perfect everywhere with no errors showing at all. might as well not use a custom map anymore if it works this well.

 

[Aluveitie]

Nice, I’ll probably switch too.

The boot arg I’ve added is revcpu=1

 

[Shaneee]

Nice, I’ll probably switch too.

The boot arg I’ve added is revcpu=1

That was the first thing I tried. Guess I need to fix the Unknown string first...

 

[AudioGod]

That was the first thing I tried. Guess I need to fix the Unknown string first...

Its not working for me either

 

[AudioGod]

Is it SIP being enabled possibly?

 

[Aluveitie]

I habe SIP enabled