Forum - RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions

#1156 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Dec 27, 2014 1:26 pm

Zitat von kevindd992002 im Beitrag #1217
Could updating the LAN OROM, in any way, fix the problem that I'm having where the computer is randomly turning on by itself even though Wake-On-LAN is already disabled?

You can try it (it wouldn't harm anything), but I doubt, that it will solve your problem.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#1157 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Dec 27, 2014 2:06 pm (Last edited: Sat Dec 27, 2014 2:07 pm)

Zitat von kevindd992002 im Beitrag #1217
Could updating the LAN OROM, in any way, fix the problem that I'm having where the computer is randomly turning on by itself even though Wake-On-LAN is already disabled?

No. That could be due to mouse/keyboard/lan wakeup which can be changed via Device Manager (Power Management tab) or Intel Smart Connect option in BIOS etc. Either way, this is offtopic at this point.

This thread has been closed.

#1158 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Dec 27, 2014 2:28 pm (Last edited: Sat Dec 27, 2014 2:34 pm)

Zitat von plutomaniac im Beitrag #1219
Zitat von kevindd992002 im Beitrag #1217
Could updating the LAN OROM, in any way, fix the problem that I'm having where the computer is randomly turning on by itself even though Wake-On-LAN is already disabled?
No. That could be due to mouse/keyboard/lan wakeup which can be changed via Device Manager (Power Management tab) or Intel Smart Connect option in BIOS etc. Either way, this is offtopic at this point.

I understand. And no, wakeup due to mouse and keyboard is already isolated. When I ran powercfg, it points to the Gigabit LAN being the culprit and so I disabled all power management-related things related to it to no avail. There is no Intel Smart Connect Technology in the BIOS as well.
Yes, it's going off topic I guess. This was my whole point of updating the LAN OROM at first and I guess I realized that it only affects PXE boot and not the LAN driver in Windows itself. With all these, I'd just leave the original BIOS alone as it already has an updated microcode for SB anyway.
Two final questions:
1.) All OROMs have an effect only during boot-time (before Windows), correct?
2.) The NVM firmware of the LAN hardware is different from that of the LAN PXE OROM, correct?
Thanks for all the help!

EDIT by Fernando: Post size shrinked by deleting unneeded quoted text and blank lines

Mainboard: Asus MAXIMUS X Code , CPU: Intel Core i7-8700K, Disks: Samsung 970 EVO 500GB SSD + Samsung 850 EVO 500GB SSD + Samsung SATA3 1TB HDD, Graphics: Intel Gigabyte GTX 1080 Ti, RAM: 2x8GB G.Skill Trident Z (F4-3200C14D-16GTZKW), OS: Windows 10 Enterprise x64

This thread has been closed.

#1159 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Dec 27, 2014 2:43 pm (Last edited: Sat Dec 27, 2014 2:51 pm)

Zitat von kevindd992002 im Beitrag #1220
1.) All OROMs have an effect only during boot-time (before Windows), correct?

Yes, and the EFI "Drivers" (SataDriver, GopDriver etc.) as well. But that doesn't mean, that the loaded ROM/EFI "Driver" modules don't have any effect on the system while working.
Example: The "TRIM in RAID0" feature, which has been implemented by loading the related (modded) Intel RAID ROM or SataDriver module, lets the TRIM command pass through the Intel RAID Controller into the RAID0 array as long as the computer is running.

Zitat
2.) The NVM firmware of the LAN hardware is different from that of the LAN PXE OROM, correct?

Yes!

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#1160 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Dec 27, 2014 4:16 pm (Last edited: Sat Dec 27, 2014 4:56 pm)

Zitat von Fernando im Beitrag #1221
Zitat von kevindd992002 im Beitrag #1220
1.) All OROMs have an effect only during boot-time (before Windows), correct?
Yes, and the EFI "Drivers" (SataDriver, GopDriver etc.) as well. But that doesn't mean, that the loaded ROM/EFI "Driver" modules don't have any effect on the system while working.
Example: The "TRIM in RAID0" feature, which has been implemented by loading the related (modded) Intel RAID ROM or SataDriver module, lets the TRIM command pass through the Intel RAID Controller into the RAID0 array as long as the computer is running.
Zitat
2.) The NVM firmware of the LAN hardware is different from that of the LAN PXE OROM, correct?
Yes!

Got it. But in my case, my board's BIOS is using all OROMs, and so the only ROM that will have an effect to my system while in the OS (running) is the example that you gave (modded TRIM in RAID0). Other than that, the remaining OROMs in the UBU Tool (jmicron, gop, lan pxe, etc.) won't have an effect while the system is running. Did I get it right?

Mainboard: Asus MAXIMUS X Code , CPU: Intel Core i7-8700K, Disks: Samsung 970 EVO 500GB SSD + Samsung 850 EVO 500GB SSD + Samsung SATA3 1TB HDD, Graphics: Intel Gigabyte GTX 1080 Ti, RAM: 2x8GB G.Skill Trident Z (F4-3200C14D-16GTZKW), OS: Windows 10 Enterprise x64

This thread has been closed.

#1161 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Dec 27, 2014 4:55 pm

Zitat von kevindd992002 im Beitrag #1222
But in my case, my board's BIOS is using all OROMs, and so the only ROM that will have an effect to my system while in the OS (running) is the example that you gave (modded TRIM in RAID0). Other than that, the remaining OROMs in the UBU Tool (jmicron, gop, lan pxe, etc.) won't have an effect while the system is running. Did I get it right?

Not really. The Option ROM modules are somehow the "Firmware" of the related Controllers. They are loaded once (while booting), but the features (and the bugs) they got implemented by the Controller manufacturer will be present all the time until you power-off your computer.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#1162 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sat Dec 27, 2014 11:09 pm

Zitat von SoniX im Beitrag #1197
... Intel GOP Driver Clover View is version 6.0.1032...

I did had some doubts about it. Anyway, it is older and for tablets only. It was extracted from an Acer Iconia W510.

Found a new AMD GOP 1.55.0.0.0 in some VBIOS, like the ones from Station-Drivers. Here are some observations:
- up until GOP 1.52.0.0.0 (or even 1.50.0.15.36), the GOP was customized for every board, by inserting a dummy OROM for the corresponding GPU.
- with GOP 1.52.0.0.0 there is a universal GOP in main BIOS, but the GPU still has a customized GOP with OROM inserted.
- starting with GOP 1.53.0.0.0, the GOP is universal and the same in main BIOS and GPU. Just that the one in GPU is signed.

I have attached a pack for you to check this on yourself. It contains:
- AtiFlash.exe, atidgllk.sys, atikia64.sys, atillk64.sys are taken from official ATIFlash 2.6.7 package. Just the basic for info display. NOT for flashing!!!
- atiflash-info.bat is for displaying the info about an AMD VBIOS file. Just drop the AMD VBIOS on this bat.
- nvflash.exe, nvflsh32.sys, nvflsh64.sys are the official NVflash 5.196 package.
- nvflash-info.bat is for displaying the info about an Nvidia VBIOS file. Just drop the Nvidia VBIOS on this bat.
- UEFIRomExtract.exe, UEFIRomExtract.bat are for decompressing the EFI stored in second image of AMD/Nvidia VBIOS. Just drop the AMD/Nvidia VBIOS on this bat.

UEFIRomExtract.py is not really needed, but added for two reasons:
a) UEFIRomExtract expects that OROM header starts at 0x00 offset, which is not the case for Nvidia VBIOS, which has an IFR header. This script creates a temp file with IFR header removed, UEFIRomExtract is happy. The original file is left untouched.
b) extracts the EFI image in compressed format, to be used for patching a VBIOS for GOP support. For once, AMD has done it easier for the user, you just take the latest compressed GOP from another VBIOS, patch the ID and add/replace the second image. Last part is to switch the "last image indicator" byte and fix checksum in the first image only. Nvidia is a little bit tricky, because you need a compatible board. The rest is the same - with taking the latest compressed GOP from another VBIOS, patch the ID, add/replace the second image, switch the "last image indicator" byte - but fix checksum in both images. It seems there are GOP variants for GT21X, GF10X, GF119, GK1XX, GM1xx, GM2xx.

Note: [vbios_name]_dump.efi is the decompressed image provided by UEFIRomExtract.exe, while [vbios_name]_compr.efirom is the compressed EFI image extracted by UEFIRomExtract.py script.

lordkag has attached files to this post

This thread has been closed.

#1163 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sun Dec 28, 2014 3:57 am (Last edited: Sun Dec 28, 2014 9:47 am)

Zitat von Fernando im Beitrag #1223
The Option ROM modules are somehow the "Firmware" of the related Controllers. They are loaded once (while booting), but the features (and the bugs) they got implemented by the Controller manufacturer will be present all the time until you power-off your computer.

Ok. So do you recommend I just update the RAID, GOP, AND LAN PXE OROMs even though I won't use them in Windows just to be sure that there won't be any bugs of any sort? They are all disabled in my BIOS anyway, so I'm not sure. RAID is disabled (AHCI enabled), GOP disabled (onboard GPU disabled), and LAN PXE disabled (LAN boot disabled).

EDIT by Fernando: Post size shrinked by deleting unneeded quoted text and blank lines

Mainboard: Asus MAXIMUS X Code , CPU: Intel Core i7-8700K, Disks: Samsung 970 EVO 500GB SSD + Samsung 850 EVO 500GB SSD + Samsung SATA3 1TB HDD, Graphics: Intel Gigabyte GTX 1080 Ti, RAM: 2x8GB G.Skill Trident Z (F4-3200C14D-16GTZKW), OS: Windows 10 Enterprise x64

This thread has been closed.

#1164 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sun Dec 28, 2014 9:52 am

@kevindd992002:
You can update the "Firmware" of on-board Controllers, which have been disabled in the BIOS, but it doesn't make any sense as long as they are not in use.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#1165 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sun Dec 28, 2014 9:59 am (Last edited: Sun Dec 28, 2014 10:53 am)

Zitat von Fernando im Beitrag #1226
@kevindd992002:
You can update the "Firmware" of on-board Controllers, which have been disabled in the BIOS, but it doesn't make any sense as long as they are not in use.

Ok, I guess I'll just leave them as it is. Thanks!

Mainboard: Asus MAXIMUS X Code , CPU: Intel Core i7-8700K, Disks: Samsung 970 EVO 500GB SSD + Samsung 850 EVO 500GB SSD + Samsung SATA3 1TB HDD, Graphics: Intel Gigabyte GTX 1080 Ti, RAM: 2x8GB G.Skill Trident Z (F4-3200C14D-16GTZKW), OS: Windows 10 Enterprise x64

This thread has been closed.

#1166 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sun Dec 28, 2014 8:55 pm

Hello everyone!
I use a MSI 970A-G43 (MS-7693) motherboard, which have an NEC/Renesas µPD720202. In "Device Manager" it shows "Firmware Version: 2018". On the internet I found version 2.0.2.4 (or 2024).
Is there any posibility to update the onboard USB 3.0 Option ROM in the near future? Thanks in advance.

Best regards,
Daniel Ciuperca

This thread has been closed.

#1167 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Sun Dec 28, 2014 10:08 pm

@ danielciuperca:
Hello Daniel, welcome at Win-RAID Forum!

Zitat von daniel.ciuperca im Beitrag #1228
I use a MSI 970A-G43 (MS-7693) motherboard, which have an NEC/Renesas µPD720202. In "Device Manager" it shows "Firmware Version: 2018". On the internet I found version 2.0.2.4 (or 2024).
Is there any posibility to update the onboard USB 3.0 Option ROM in the near future?

According to my knowledge there are only Firmware packages (with installer) and no Option ROM modules available for USB 3.0 Controllers.
You can download the latest Firmware version 2.0.2.4 for your Resenas USB 3.0 Controller µPD720202 from >here<.

Happy New Year!
Fernando

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

#1168 | RE: RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Tue Dec 30, 2014 10:17 am

Realtek UEFI UNDI Driver 2.032

ex58 has attached files to this post

RtkUndiDxe.2.032.2014.12.12_signed.zip

Z590/490/390 AORUS Master
Z370 AORUS Gaming 7,
GA-Z170X-SOC Force ,
GA-Z97X-SOC Force ,Core i7-4790K ,G.Skill F3-2933C12D-8GTXDG
2xSSD Corsair Force GS 128 (RAID 0), WD Caviar Black 1TB
Win 7 SP1 x64;Win 8.1 x64 ;Win 10 x64

This thread has been closed.

#1169 | RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Wed Dec 31, 2014 1:45 pm

I used v1.9 RC2 a few days ago to upgrade all the ROMs and microcode of the my board's (ASUS P8Z68-V/GEN3) BIOS and flashed it over. Will using the new v1.9 have any changes if I modify the BIOS again? Or will it do the exact same thing?

I noticed that in the changelogs, it says "altered the procedure for updating microcode files" so I was wondering if v1.9 final does something that the v1.9 RC2 doesn't.

Mainboard: Asus MAXIMUS X Code , CPU: Intel Core i7-8700K, Disks: Samsung 970 EVO 500GB SSD + Samsung 850 EVO 500GB SSD + Samsung SATA3 1TB HDD, Graphics: Intel Gigabyte GTX 1080 Ti, RAM: 2x8GB G.Skill Trident Z (F4-3200C14D-16GTZKW), OS: Windows 10 Enterprise x64

This thread has been closed.

#1170 | RE: [Discussions] UBU Tool related Questions, Reports and Suggestions datum

Wed Dec 31, 2014 1:51 pm

Zitat von kevindd992002 im Beitrag #1232
Will using the new v1.9 have any changes if I modify the BIOS again?

Probably not for you and your current mainboard BIOS, because the final version of UBU 1.9.0 doesn't contain any new or updated Option ROM modules.

Zitat
I noticed that in the changelogs, it says "altered the procedure for updating microcode files" so I was wondering if v1.9 final does something that the v1.9 RC2 doesn't.

Changing the method doesn't automaticly mean, that the results will be changed as well.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

This thread has been closed.

Please enter a reason for warning.