Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

Riley Freeman
Riley Freeman
Posted
Posted

hi

i had the same problem.

with the Bios Z77-DS3H F10h i dont get Full Res, but when i replace the CSMVideo module from the new F10i then i get Full Res without any driver with Clover and ozmosis.

 

 

At first I wasn't sure about replacing the CSMVideo module with one from another manufacturer but I figured I'd give it a shot. And I'm glad I did.

 

14:239 00:343 Setup Graphics Mode 1920 x 1080 (4)

 

It works perfect! Thanks  :guitar:

  • Like 1
Link to comment
Share on other sites
richtig
richtig
Posted
Posted
5.Yes.  Nvidia GTX 6xx,7xx series ATI 7xxx series and never,Intel HD 3000 and never.I am not sure if HD Graphics (HD 2000) have UEFI GOP.

Sometimes brands just dont release this to public and u have to ask them for this becouse there are many UEFI motherboards  that have really bad UEFI GOP support and are not updated frequently.

 

Hope it helps.

 

If u wanna flash your MSI GTX 650 then just go to their forum and search for bios by your PN of card.

If u cannot find then post request and u will get it in no time.

Clarification on buying a video card with UEFI GOP already present:

The onboard Intel graphics UEFI GOP firmware is (if present) included as part of the motherboard bios.

Note: only applies to some Z87 and Z77 chipset boards.

However: AFAIK, the latest standalone video cards do NOT include a UEFI GOP firmware.

Such as: a MSI GTX 760 card,

http://www.newegg.com/Product/Product.aspx?Item=N82E16814127745

Bios update for that card (must be signed in to their forum to view download link):

https://forum-en.msi.com/index.php?topic=172726.msg1257788#msg1257788

which, when sold as new, has only an empty "placeholder" spot for the UEFI GOP bios.

Note: I was able to find an update for my MSI GTX 650 card elsewhere on that same forum. The UEFI GOP bios update indicates that the UEFI portion of the video card bios was digitally signed by Microsoft. Maybe by leaving to the end user the job of bios flash updating, the card makers avoid paying Microsoft some kind of royalty fee?

Link to comment
Share on other sites
xpamamadeus
xpamamadeus
Posted
  • Author
Posted

Clarification on buying a video card with UEFI GOP already present:

The onboard Intel graphics UEFI GOP firmware is (if present) included as part of the motherboard bios.

Note: only applies to some Z87 and Z77 chipset boards.

However: AFAIK, the latest standalone video cards do NOT include a UEFI GOP firmware.

Such as: a MSI GTX 760 card,

http://www.newegg.com/Product/Product.aspx?Item=N82E16814127745

Bios update for that card (must be signed in to their forum to view download link):

https://forum-en.msi.com/index.php?topic=172726.msg1257788#msg1257788

which, when sold as new, has only an empty "placeholder" spot for the UEFI GOP bios.

Note: I was able to find an update for my MSI GTX 650 card elsewhere on that same forum. The UEFI GOP bios update indicates that the UEFI portion of the video card bios was digitally signed by Microsoft. Maybe by leaving to the end user the job of bios flash updating, the card makers avoid paying Microsoft some kind of royalty fee?

My MSI GTX 660 TF3 originaly comes with uefi gop bios.

MSI have bios to remove UEFI GOP support for that card

http://www.msi.com/product/vga/N660-TF-2GD5-OC.html#/?div=BIOS

This bios is used to solve motherboard compatible issue. If your card is Hybrid bios and face this issue, please update your BIOS.

Not all comes with that..

I flash this bios about almost year ago and did not save original one ...

Later i get UEFI GOP again but from forum..

They dont include that on all cards becouse there are motherboards  like my last asus maximus iv extreme (p67)that wass having problems with UEFI GOP bios.

 

i sold that motherboard becouse of that and when i sold it out asus make a bios update that are solving that.

 

Soo i am sure some of manufacturers are leaving UEFI GOP bios to users to flash becouse of that kind of problems.Not becouse they pay microsoft..

Link to comment
Share on other sites
xpamamadeus
xpamamadeus
Posted
  • Author
Posted
Great news for NVRAM not saving on new bioses!! 
As i promise  i will investigate nvram problems using gigabyte new bioses i found a way to fix this problem in new bioses.
 
We must doo 2 things.
First ist to find and delete nvramsmi module in bios.
Second its to find and replace runtime module in bios with one from old bios that work.
U will not find this modules with mmtool! We need to use phoenixtool for finding GUID of module and then we can delete/replace it using MMTOOL 
 
Good luck!
 
Plz report if u have sucess with this new mod :D
 
Now i am running latest F16 bios with working nvram.
 
Fu.k u gigabyte for screw us like that!!
 
here the file we need to replace for z77x ud5h users.
 
and GUID of nvramsmi that need to be deleted.
842A454A-75E5-408B-8B1C-36420E4E3F21

 

one small bug with this fix,flashing using qflash dont work after this mod!

but we can always flash from windows using @bios!

looking at quo bios runtime it seems that its almost identical to ud5h old working version,same lengt only a few bytes changed.

new version that not save nvram its smaller.

 

maybe some smart guy like coderush can investigate this problem and make patch for all gigabyte boards,maybe even asus..

  • Like 5
Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

In trying to find a BIOS that has writable nvram can we take it that any BIOS with the 842A454A-75E5-408B-8B1C-36420E4E3F21 module is unable to write to nvram?

 

My P9X79 Pro can't write to nvram and is running the latest 4302 BIOS. I went looking back through previous updates and BIOS 3305 was the last one that didn't include this module. Would this mean that the runtime from 3305 is the last one that can write to nvram?

 

Update 1: Well, I tried to replace the Runtime file in 4302 with the one from 3305. Deleted the nvramsmi module and threw in Ozmosis while I was at it. Alas, the system powers up but there's no video. I guess the runtime is too old for this BIOS. I'll try flashing stock 3305 now and see if nvram writing works.

 

Update 2: Clover couldn't UEFI-boot my system for some reason after the 3305 BIOS downgrade. It took ages to load and then eventually hung at a blue screen with cursor. I'd removed the DSDT to avoid any clash but that didn't help. I then tried rolling Ozmosis into 3305 but got the same black screen on boot. I don't know if this is an Ozmosis issue or a general issue with editing CAP files but both times I flashed a modified BIOS it wouldn't post.

 

Update 3: I'm wondering if USB Flashback was even writing the modified files. With a stock BIOS the flash is now a 2-step process. Normal flash in EZ Flash and then on reboot a text screen comes up where it starts updating the BIOS. I wasn't getting this second screen with the modified files last night. Maybe it checks the BIOS first before actually updating it. This first appeared a couple of versions back and I guess it's stuck now as it even appeared when flashing 3305. Thanks Asus...

Link to comment
Share on other sites
xpamamadeus
xpamamadeus
Posted
  • Author
Posted

In trying to find a BIOS that has writable nvram can we take it that any BIOS with the 842A454A-75E5-408B-8B1C-36420E4E3F21 module is unable to write to nvram?

 

My P9X79 Pro can't write to nvram and is running the latest 4302 BIOS. I went looking back through previous updates and BIOS 3305 was the last one that didn't include this module. Would this mean that the runtime from 3305 is the last one that can write to nvram?

 

Update 1: Well, I tried to replace the Runtime file in 4302 with the one from 3305. Deleted the nvramsmi module and threw in Ozmosis while I was at it. Alas, the system powers up but there's no video. I guess the runtime is too old for this BIOS. I'll try flashing stock 3305 now and see if nvram writing works.

 

Update 2: Clover couldn't UEFI-boot my system for some reason after the 3305 BIOS downgrade. It took ages to load and then eventually hung at a blue screen with cursor. I'd removed the DSDT to avoid any clash but that didn't help. I then tried rolling Ozmosis into 3305 but got the same black screen on boot. I don't know if this is an Ozmosis issue or a general issue with editing CAP files but both times I flashed a modified BIOS it wouldn't post.

 

Update 3: I'm wondering if USB Flashback was even writing the modified files. With a stock BIOS the flash is now a 2-step process. Normal flash in EZ Flash and then on reboot a text screen comes up where it starts updating the BIOS. I wasn't getting this second screen with the modified files last night. Maybe it checks the BIOS first before actually updating it. This first appeared a couple of versions back and I guess it's stuck now as it even appeared when flashing 3305. Thanks Asus...

Update 3 :D

I think that it must be 2 stage process only when u upgrade intel MEI or downgrade intel MEI

Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

Yeah that's possible. Still doesn't explain why both edited ROMS wouldn't post. The 3305 only had the Ozmosis files added.

 

I was looking through coderush's thread for clues. I assumed flashing with USB Flashback was still the way to bypass the security check, but maybe it isn't anymore?  USB Flashback is my only recovery method if things go bad. I don't have a SPI programmer so I'm gonna have to let the experts do the figuring out on this one.

Link to comment
Share on other sites
xpamamadeus
xpamamadeus
Posted
  • Author
Posted

Yeah that's possible. Still doesn't explain why both edited ROMS wouldn't post. The 3305 only had the Ozmosis files added.

 

I was looking through coderush's thread for clues. I assumed flashing with USB Flashback was still the way to bypass the security check, but maybe it isn't anymore?  USB Flashback is my only recovery method if things go bad. I don't have a SPI programmer so I'm gonna have to let the experts do the figuring out on this one.

Did u try latest bios with only nvramsmi module deleted?

Without replacing runtime ?

Nothing more,clean bios no ozmosis nothing just for test how it works on asus whenn we delete nvram smi module ?

 

I take some time to see the diferences in working vs not working modules but nothing readable found :D

Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

Ok with nvramsmi deleted the flash still worked. However Clover EFI wouldn't boot. I just got a blinking underscore. Chameleon also does the same.

 

Booting UEFI Clover from USB worked the first time, but it was loading EmuVariable. When I disabled EmuVariable it wouldn't boot again (hung at loading Extensions.mkext from cache). It's supposed to boot OS X just after this.

 

Curiously I seem to be having better luck with flashing modified roms today. I just tried 4302 with nvramsmi deleted and the runtime from 3305. Last night this didn't work, but it booted just now (no Ozmosis files this time). Alas, same story as before. Clover EFI won't boot and Clover UEFI won't boot without EmuVariable.

Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

Ok I finally managed to get Clover to UEFI boot on 3305. And I can confirm that nvram is writable.

 

However, I'm now getting TSC sync errors which are new. I guess the later BIOS versions took care of this. Explains why removing VoodooTSCSync seemed to have no ill effect.

 

Just tried flashing 3305 with Ozmosis and it's the old black screen/no post situation again. So it looks like Ozmosis is the reason my modified roms weren't booting last night.

 

Here's my MMTOOL report for 3305 with Oz 801M included.

Link to comment
Share on other sites
tonydickinson
tonydickinson
Posted
Posted

Is there any way that you guys might be able to help me.

 

Z87-DELUXE-DUAL-ASUS-1405.CAP.zip

 

I have a Z87 Asus board as you see. The saving nvram issue was supposedly confined to Z77 according to Asus but not true, as this board which is excellent even the o/b WiFi and Bluetooth works and Realtek o/b will work soon. Audio works now but distorts. But nvram is NOT saved without EmuVariableUefi-64.efi

 

Question - I am completely unable to delete the nvramsmi from the BIOS, would you XP or other expert here be prepared to have a go at removing it for me. There are four bios versions available ex Asus 1008/1205/1305/1405 but all are the same as far as saving Nvram is concerned. So I cannot provide a version which works. Interestedly it appears that the Gryphon board does save nvram.

 

Any thoughts ideas would be appreciated - Tks.

Link to comment
Share on other sites
maleorderbride
maleorderbride
Posted
Posted

Thanks for finding a BIOS version that has working NVRAM Riley!  

 

 

 

I don't know when I will have time for this again, but I will check on 3305 and see if I have a similar problem.

 

I inserted the modules that seemed to me to be responsible for making NVRAM work into my 4302 version, but it did not enable NVRAM.  I'll keep trying.

Link to comment
Share on other sites
VoSi
VoSi
Posted
Posted

i already did in PM..

U didnt get message or ?

https://www.dropbox.com/s/kxx8wsy4kez23kg/z77xud5h_mod4.f16.zip

 

Xpam, can you give me some hint in following

i'm using one of your's z77x-ud5h bioses with ozmosis (Z77XUD5HF14(no hda enabler).rom)

but having trouble with iMessages, it look's like there are no access to nvram? but i successfully changed spec to macmini6.2 (including 2 serials). and it keeps after reboot.

where is the issue?

 

second, i tried this bios https://www.dropbox.com/s/kxx8wsy4kez23kg/z77xud5h_mod4.f16.zip - and got a brick (well, suxessfully downgraded to f14)

i think, its because this bios requires efi from graphics card, but i have rather old one (gtx260)

tried to boot without this cart, with hd4000, tried to change legacy in CSM, then insert gtx260 back - no luck, stuck on AB code

i think that i need some modules, that you had injected for you custom firmware, but what?

Link to comment
Share on other sites
xpamamadeus
xpamamadeus
Posted
  • Author
Posted

Xpam, can you give me some hint in following

i'm using one of your's z77x-ud5h bioses with ozmosis (Z77XUD5HF14(no hda enabler).rom)

but having trouble with iMessages, it look's like there are no access to nvram? but i successfully changed spec to macmini6.2 (including 2 serials). and it keeps after reboot.

where is the issue?

 

second, i tried this bios https://www.dropbox.com/s/kxx8wsy4kez23kg/z77xud5h_mod4.f16.zip - and got a brick (well, suxessfully downgraded to f14)

i think, its because this bios requires efi from graphics card, but i have rather old one (gtx260)

tried to boot without this cart, with hd4000, tried to change legacy in CSM, then insert gtx260 back - no luck, stuck on AB code

i think that i need some modules, that you had injected for you custom firmware, but what?

There are no deleted modules,but it seems that CSM does not work with this F16 becouse it has older runtime module.. ?

To solve imessage u need to set all smbios variables.

 

THX to stlvnub

#!/bin/bash
#SMBIOS
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion=MM61.88Z.0106.B00.1208091121
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName=Macmini6,2
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily=Macmini
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId=Mac-F65AE981FFA204ED
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=Replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU=MD389LL/A
#OzmosisNVRAM
sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="-fakesmc-use-nvram"

#APPLE
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=Replace e.g %90%90%9090%90
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures=%C0%00%7F%FF
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask=%C0%00%14%03 

#CODE
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosDate
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BoardVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:Manufacturer
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProcessorSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ChassisAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:CpuType
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:EnclosureType

#CODE
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

just replace the "Replace"

For imessage most important to set

ROM=macadress of primary ethernet card

Link to comment
Share on other sites
richtig
richtig
Posted
Posted

@xpamamadeus:

Your last "z77xud5h_mod4.f16" bios gave no visible method to simply power the machine on and then successfully boot Windows 8 to desktop.

So, please: remember that the number one priority when offering any of your Ozmosis modded bioses for the Z77X-UD5H board: it must be able to boot any existing operating system without need of changing any bios settings (beyond the default bios settings: Intel SATA ports in AHCI mode, etc.).

That is: nothing required for a successful boot, beyond simply hitting the F12 key and selecting whichever hard drive to boot from, and be able to successfully boot: XP 32-bit, Windows 7, Windows 8.1, OSX Mountain Lion.

So: please keep at least that much flexibility inside whatever bios releases you're offering.

Or, at least: warn ahead of time: "this bios release requires XYZ bios configuration changes" in order to boot Windows at all.

Or: "this bios release only tested to work with a UEFI video card AND only with OSX Mountain Lion, and requires XYZ bios configuration changes (such as: disable CSM, or whatever) from default settings"; or "this bios only works with a GPT-formatted hard drive", etc.

Luckily, the Z77X-UD5H board has dual bios. But even with that, there could still be a possibility for certain unlucky sequences of events to occur, that would result in a bricked motherboard.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

How about you just do not flash what you do not know? GB support web site your best friend... He did not post it for every one.. Also you can even brick MB with official flash...

How can he know it if not flash? It's better to say "never flash hack os modded bioses".

  • Like 1
Link to comment
Share on other sites
StoneTemplePilots
StoneTemplePilots
Posted
Posted

Is there any way that you guys might be able to help me.

 

attachicon.gifZ87-DELUXE-DUAL-ASUS-1405.CAP.zip

 

I have a Z87 Asus board as you see. The saving nvram issue was supposedly confined to Z77 according to Asus but not true, as this board which is excellent even the o/b WiFi and Bluetooth works and Realtek o/b will work soon. Audio works now but distorts. But nvram is NOT saved without EmuVariableUefi-64.efi

 

Question - I am completely unable to delete the nvramsmi from the BIOS, would you XP or other expert here be prepared to have a go at removing it for me. There are four bios versions available ex Asus 1008/1205/1305/1405 but all are the same as far as saving Nvram is concerned. So I cannot provide a version which works. Interestedly it appears that the Gryphon board does save nvram.

 

Any thoughts ideas would be appreciated - Tks.

 

Hey tonydickinson,

 

I own a P8Z77-V LX and I downgraded from 2204 to 1603 ROM, now I can save the NVRAM settings. I found out where the settings are stored for my board:

 

000|               |CEF5B9A3-476D-497F-9FDC-E98143E0422C|00180048|01FFB8|RAW

 

That's my NVRAM firmware volume ; ) if you wan't to I can try to burn in your settings permanently but it would be a good idea

when you send me your smbios.plist settings, so our settings wouldn't overlap ; ) and I know

what's your machine settings that should be stored.

 

Btw. ASUS has no nvramsmi module, those seetings must be stored in any other module.

 

Even I'd like to know if you're able to flash a modified bios ??? ; ) then we know if a mod is worth the effort.

 

regardz

  • Like 1
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted

There are no deleted modules,but it seems that CSM does not work with this F16 becouse it has older runtime module.. ?

To solve imessage u need to set all smbios variables.

 

THX to stlvnub

#!/bin/bash
#SMBIOS
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion=MM61.88Z.0106.B00.1208091121
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName=Macmini6,2
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily=Macmini
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId=Mac-F65AE981FFA204ED
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=Replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU=MD389LL/A
#OzmosisNVRAM
sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="-fakesmc-use-nvram"

#APPLE
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=Replace e.g %90%90%9090%90
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures=%C0%00%7F%FF
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask=%C0%00%14%03 

#CODE
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosDate
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BoardVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:Manufacturer
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProcessorSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ChassisAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:CpuType
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:EnclosureType

#CODE
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

just replace the "Replace"

For imessage most important to set

ROM=macadress of primary ethernet card

 

Hello,

 

sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%01%02%03%04%05%06

This value doesn't saved after reboot, all other are saved.

 

After reboot 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM became 0 !

 

what's wrong ? is-it same for all users ?

 

Fred

Link to comment
Share on other sites
StoneTemplePilots
StoneTemplePilots
Posted
Posted

Hello,

 

sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%01%02%03%04%05%06

This value doesn't saved after reboot, all other are saved.

 

After reboot 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM became 0 !

 

what's wrong ? is-it same for all users ?

 

Fred

 

As I understood it should be somthing like sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=  your firewire mac adress

 

» explained here - thanks to ElNono_@tonymac

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