"CSM not found or cannot open/extract file"

Zitat von westlake im Beitrag #122

---

"CSM not found or cannot open/extract file"

---

Hi Fernando,

I didn't want to blame the UBU Tool in any way. I am fully aware what I do and that it is risky.

Zitat

---

It was your choice and not my suggestion.

---

Neither wanted I to blame you . Probably I used the 13.1 ROM because I had good experiences with it on other systems in the past and only saw later that in your suggestions thread for Z68 systems v12.x was recommended. It was late at night .

Zitat

---

Nobody is forced to update all BIOS modules, which are offered by the UBU tool

---

Of course, but with firmwares and BIOSes "new is always better" often applies. This is why I prefer to have most recent ROMs.

Zitat

---

The newest BIOS modules are not always the best

---

I partly disagree. The newest of its generation (such that it remains fully compatible) are most often the best (due to the bugfixes). In many cases the manufacturer just doesn't release any more updates and rather wants to sell a new board.

Zitat

---

1. Which source BIOS version did you use (ASUS offers 2 different variants of the BIOS 3603)?

---

The Win7/Vista-variant. Although I think that the only difference between the XP variant and the Win7-variant is the newer Intel RST ROM, which is probably unsupported by drivers in WinXP.

Zitat

---

2. How did your flash the modded BIOS?

---

Using the BIOS-integrated EZ-Flash. I avoid Windows-based flashing whenever it is possible. I prefer old-school flashing. In the case of bricked BIOS, I extracted the chip and flashed it with the EEPROM CH341A writer on another PC using Linux and flashtool.

I am in contact with @Lost_N_BIOS and showed him, what I did. And to repeat: I don't want to blame UBU in any way, I just want to preserve people without an EEPROM writer to brick their board by choosing the latest and greatest.

Best regards
weaker

@weaker - flash program tools are so cheap (usually $2.50 for a cheap programmer + $3.50 for SOIC8 test clip cable if needed), that everyone should have a set no matter what, especially if they are modifying BIOS.
Flashing stock BIOS can brick a board, even using manufacturer standard suggested procedures, with a good valid BIOS that doesn't brick other boards, so it's always a risk and the tools are so cheap everyone should order a set.

From your PM, I don't think it was quite summarized here, I think you narrowed the issue down to the replacement of the Intel GbE PXE ROM 1.3.72 >> Update to >> 1.5.62 (I checked this, it appears to be inserted properly, so maybe just in compatible with the board?)

Hi Fernando,

I also have this problem.

The JMicron ROM seems to be the very first in the boot order. When I tried v1.08.01 I saw nothing on screen, v1.07.28 showed a message and even detected an attached disk, but booting didn't continue.

In the case of UBU 1.69.17.2, we could upgrade to 1.07.28. However, in the case of 1.73.2, the same problem as the above sentence occurred.How is this

The way was the same as weaker.

Fernando,
UBU_v1.69.17.5_without-MMTool linked to MEGA can not be used without invoking bios. Please fix this. Thank you.

@nobi - if you didn't also update Intel PXE rom, then you may have found the culprit.
From what you mentioned, J.Micron rom is the issue, I wasn't sure based on some comments @weaker said, suspected it initially but I moved past it and suspected Intel PXE rom after he said xx j.micron rom was used and showed disk detected and then BIOS failed after that, so I assumed the Intel PXE instead.
Sounds like the j.micron rom works partially, then fails after it shows the detected disk.

@Fernando

The reason for the update is simple, because it was updated with UBU 1.69.17.2
I understand what you are saying.
However, I am puzzled that the update failed in UBU 1.73.2

There is nothing to fix. The download link works fine by doing a right-click onto the related file and choosing the "Standard download" option.

I'm sorry. This is not that sense. UBU 1.69.17.2 can be launched
When launched with UBU_v1.69.17.5_without-MMTool

https://imgur.com/a/8UI1J3q

Please correct it as it becomes this.

@nobi It's not very easy to understand what you mean.

I happen to have some old versions of UBU and I can confirm that 1.69.17.2 does read your bios and 1.69.17.5 doesn't. The reason is an updated UEFIfind.exe in 1.69.17.5.
That's not rocket sience to find out- I simply checked for different (exe-)files in both versions and copied the older files from 1.69.17.2 one by one into the folder with 1.68.17.5 and checked after each copy if UBU would work.
=> Use UEFIfind from 1.69.17.2 in 1.69.17.5 and it will work.

In addition I don't understand the worries about UBU 1.73.2- it works with your bios just fine (see the pictures)

@Fernando

Thank you Fernando will be happy to use it. As there are things that Bios does not support UBU v1.69 or more If you use a new UBU then it's probably microcode

@lfb6

I know how to do that. But I dare to ask Fernando to fix it.

If you look at your photos at the site, it looks like the UBU 1.73.2 update is successful
But I failed to update UBU 1.73.2

The JMicron ROM seems to be the very first in the boot order. When I tried v1.08.01 I saw nothing on screen, v1.07.28 showed a message and even detected an attached disk, but booting didn't continue
I'm jealous of this problem.

Did you succeed in updating the JMicron ROM?

If anyone cares or is looking for, i can upload ubu 1.69.16. (contains alot of modules for IRST aswell). It is the oldest version i still have.