Clevo BIOS Thread

I did the same going into 1.00.06, but there's only one way to find out because the error that you're seeing is the same when you don't run MeSet.exe.

 

ok let me try again

 

done!
by the way have u tried to put usb stick to other ports?

 

I have tried but the fact is that the BIOS doesn't show USB as a choice to boot up to.

Did yours show when you were on .06? Or did you flash using a CD?

Glad to see you got yours flashed!

 

yes my .06 did show the boot from usb stick option
maybe you can try another usb stick?

 

That's what it was! I got it now.

I don't think it was the USB stick or the USB port though. I think the BIOS is slow on catching on if there was anything inserted. But everything is good now.

 

good to hear that is ok now. i just hope clevo will put more options to the bios

 

Lol. That's what I'm hoping for but we both know that's not going to happen.

 

And me? I am hoping for that and in three or four days i will buy the Clevo P170EM on my signature! So imagine my anxiety?! hehehe

 

I just found out that even though there is RAID support on the p150em that you can't raid 0 (stripe) with a drive in the optical bay. Is there another version of a bios that I can flash to enable this (even if it is just SATA II) because I am just going to raid 2x750gb 7200rpm drives together.

 

Probably not.

 

Are you sure?

I can't find a section on my dumped bios to enable or disable this?

 

There are only two official BIOS versions, the stock Clevo one which is the base version, and the Sager version which is a slightly modified version. I don't know if you have a Sager branded notebook or a stock Clevo notebook. Either way, it is highly unlikely that the Sager version will have such a fix, therefore if it's not in the stock Clevo BIOS, then my certainty level is 99.5%.

 

Is it possible to flash the bios in my Sager branded notebook to the Clevo bios and apply the fix?

 

It is possible, although it will be difficult to go back to a Sager BIOS. Once you are on a Clevo BIOS, you need to stick to Clevo BIOS updates.
What fix are you referring to ?

 

I just want to enable Raid 0 support that csoren was referring to. Is there something I would lose by not being able to go back to the Sager bios? 680m support?

 

No, you won't lose anything. But I am not sure how you can enable Raid 0 for your caddy. The Clevo BIOS is locked.

 

I have seen two posts about it being done already. One that Mythlogic can add a custom bios that would enable Raid 0 with the Caddy and even 5 with the msata drive, and then I saw that csoren was looking into adding Raid 0 to his p150em as well and that's what mythlogic told him (as you can configure a machine on their site with raid in the caddy drive). I can't find anything else about it except his post where he said it was easy using AMIBCP, but I can find no such option when I dump my bios and open it with AMIBCP. Just a few string texts about enabling different RAID modes.

 

In that case, you need to contact Mythologic for that BIOS and all future BIOS updates you will need to get from Mythologic.

Provided they are willing to help you.

 

What is making the BIOSes so hard to change/update for the same hardware? It seems if one piece of the same hardware can do something it shouldn't be too hard to change the BIOS and have the same functionality on something else. The main reason I bought a p150em was for modding/customization , but apparently it's not as easy as I thought... but I guess better than some random HP/Dell.

 

I think it's best if you refer to this thread: http://forum.notebookreview.com/sager-clevo/648848-clevo-bios-mods.html

 

WebFile -
http://s49.radikal.ru/i124/1208/13/88f1e73dc553.jpg

not a test... maybe tomorrow.

 

That new fan table keeps the fan at 50% while idle....it will lower the idle temps, but won't switch off anymore...not sure if that's what people want...

 

Could you see what is available for P150EM?

 

I got the bios random. I ask, but there is no certainty.


P.S. sorry for the language I use a translator.

 

Wise words. Wise words indeed.

 

Oh how did you find it randomly?

 

New BIOS and EC for W150ERx/W170ER can be found on the first page.

 

Regarding New BIOS and EC for W150ERx/W170ER: Step2 gives a "Bad command or file name" error...

 

Probably Clevo screwed up something this time. But I can't figure out what.

 

I´m trying to compare it to other BIOS batch commands, but i don´t i´m going to try anything, i don´t want to brick anymore hardware... my boss might kick my ...

 

Just wait for Prema or someone else to have a look over it.

 

From a small look I can't tell either. Only addition is the force (/x) command, which is mostly to cover up some mess they did before...

Try the old school basic bats attached. V1 is regular command v2 is without the new force flash command.

 

It looks like step2.bat is trying to run GMSDM.exe, but it's not there?

 

Can anyone share the secret how to extract the files from the ISO images? The files are "hidden" with any ISO reader I've tried can only see them when booting from the ISO in DOS in VM or actual. Thanks in advance.

 

Mount ISO - Open UltraISO - Extract boot sector from CD/DVD - Save bif file - Open bif file - Drag and drop files to desktop.

 

Thanks a bunch iaTa. Stupid mistake I made. Thanks for your time and patience.

 

i flashed to this latest w150er bios + ec and the fix prema provided didnt work for me for step1, so i used the step1 batch command for the ec update, update2 worked perfectly. Now to see what changed

Does clevo provide a changelog for what they changed perhaps?

 

EC firmware 1.00.05 for P150EM only
System BIOS 1.00.05 for P150EM only
foto
P170EM
Bios 1.00.07
ЕС 1.00.06

 

Oh, it sounded as if you had already flashed the EC, the bat I provided is just for the BIOS.

So did the update or update2 flash the BIOS, so I can fix the original bat.

 

Did you try 7-Zip?

 

It seemed to me the 2 files you made did the same thing, both flashed the bios, bit now im beginning to have doubts myself, maybe i did twice the same then hahaha. but that other one worked to flash the ec and afterwards i updated the bios once more cause was recommended to always flash the ec before the bios.

Many thanx for all ur efforts prema! cant wait for ur nvidia voltage mods for the w150er series

 

Hi,

I am building something that may interests you, and help people find the right BIOS for their Clevo
Index of /clevo-mirror

Currently, I only managed to find files for the W150HRM, that I own.
I hope it will help other W150HRM users

BUT, it's likely that I will add resources for other models in the future. Please e-mail me (or send me a PM) for more infos.

 

Does somebody know the details about P1xxEM BIOSes?

- In the service manual, there is an inconsistence: the specification says "AMI BIOS (48Mb SPI Flash-ROM)" but ROM IC on the schematic is MX25L1606EM2I-12 (16 Mbit).

- The firmware consists of two parts: EC/KBD and main BIOS. EC/KBD looks like a typical BIOS firmware (device control, startup/initialization, Setup, boot etc.). What functions are performed by the "main BIOS"? If EC/KBD is fine but BIOS corrupted, how laptop functionality looks?

- mmtool shows that both parts contain almost the same list of modules. Does main BIOS supersede EC/KBD? EC/KBD size is 4 MB (32 Mbit) and BIOS size if 6 MB (48 Mbit). Even if ROM size is 48 Mbit, they both cannot fit into the ROM separately.

- While EC/KBD is flashed by the native AFU utility from AMI, BIOS is flashed by "fpt" tool. What fpt does?

- EC/KBD should contain AMI boot block capable to recover a corrupted firmware via Ctrl-Home/Ctrl-PgUp/Ctrl-PgDn. But the boot block reads and flashes EC/KBD part only. As already mentioned here, if improper BIOS is flashed over proper EC, the laptop may not boot. Does it occur because an improper BIOS flashing can overwrite EC sections in the ROM, or main BIOS is absolutely needed to boot, even in pure DOS?

I googled hardly but found nothing about exact EC/KBD and main BIOS relationships. Any information will be greatly appreciated.

Looking quickly into P150/151/170EM firmware files (both EC and BIOS ones, different versions), I found some repeated .rom file names:

For P150EM: P15EMx008.rom
For P151EM: P151EM008.rom
For P170EM: P17EM_08.rom

No other .rom strings present. Looks like recovery firmware file names. People who have laptops bricked after improper EC/BIOS versions and/or sequence, you could try them in AMI recovery procedure. P1xxEM firmwares look like they support even CD and Serial recovery methods but USB stick is a simplest one. If FAT32 will not work, try to format it in FAT16. To make sure, you can search your firmware files for the ".rom" pattern.

As I understood, on P1xxEM keyboard that does not have a separate Home key, you can press Fn+B instead of Ctrl-Home.

Unfortunately, I don't know what file should be renamed to one of these .ROM names, EC file or BIOS file. But if you flashed BIOS without EC, it means BIOS is obviously in place and the logic suggests to use EC file, and vice versa.

 

P1x0EM mainboard got two flash memory 32Mbit and 16Mbit ( HM series also got it )

 

i can use this if i can't entry in windows / bios / dos ?

 

Where did you find the .08 roms?

 

Both single 48 Mbit and two 16 and 32 Mbit ROMs can contain up to 48 Mbit, right? But EC firmware file size is 4 MB (32 Mbit) and BIOS firmware file size is 6 MB (48 Mbit). How they both can be stored? If BIOS is stored in the same ROM, overwriting some parts of EC, why such strange placing is used? Why not to have a single file?

There are no .08 firmwares actually released, but only the appropriate .rom file names stored in all firmware files. The most likely purpose to store such file names in the firmware is to specify file names for AMI Boot Block recovery process.

Of course, it might be wrong but people having bricks after improper flashing could try another chance.

 

During flash, rom files are used partialy and change chosen sections only.
Look at rom file in MMTool or phoenix you will see padding sections that keep segments on place

-- EDIT --

MMTool doesn,t show padding sections in file, PhoenixTool does and extraxt whole dump with padding sections ( first is EC flash block )

 

Surely, I saw the segmentation but I really cannot understand why Clevo developers use two separate files. It is a very strange solution, and together with the exact flashing order requirement, it becomes really weird.

Looks like that developers got a complete solution from someone else and don't want to learn about it deeply, preferring to just slightly modify it.