Forum Home
Press F1
 
Thread ID: 93295 2008-09-11 03:06:00 Weird BIOS update error messages Agent_24 (57) Press F1
Post ID Timestamp Content User
704362 2008-09-11 03:06:00 I'm trying to update the BIOS for a motherboard because I get this error (www.imagef1.net.nz)when trying to load ubuntu

It's an EPoX KL-133M

I tried Uniflash but the chip is not detected, even though I'm fairly sure it's supported.

So, I tried with Awdflash instead which detects the chip (Eon EN29F002NT) and seems to work but throws up this error after asking me what image file I want to update with:


Image file is NOT original BIOS

!! BIOS Image file checksum not zero !!

Check to see if FDD & HDD error occurred
Avoid using file saved from M/B directly

Message: Press any key to continue

it then goes on to ask me if I want to save the old BIOS, and then write the new BIOS. I chose no, as I'm not sure what that error means.

According to the readme the file I have is the correct one for this motherboard:


Bios filename: kl0m1a24.bin
Bios date: 10/24/2001
Bios size: 256 KB (For 4Mb BIOS EEPROM)
Bios checksum: EDFB
Model support: KL-133M, KL-133ML
Agent_24 (57)
704363 2008-09-11 03:15:00 I take it, youre doing it in DOS, not in windows or linux?

You sure its not the KL-133ML? Altho its looks like they point to the same file but it doesnt exist (on the US site)
Speedy Gonzales (78)
704364 2008-09-11 03:21:00 DOS of course, I'd only do it under windows if I had no other choice.

It's definitely the KL-133M - well that's what's written on it anyway

I downloaded the file from the Russian site, as the USA site didn't work and the others were down

Currently loaded up the version 8.83 (I think it's the latest) of awdflash which has not shown any error messages... was using 8.13

I'm going to try updating with that, if it fails - well the chip is socketed...
Agent_24 (57)
704365 2008-09-11 03:30:00 Well, that worked - but I still can't boot my Ubuntu CD .... Agent_24 (57)
704366 2008-09-11 04:24:00 Well, I managed to load it using Smart BootManager from a floppy disk.

I guess the only way to make it work properly would be to fix the BIOS. Unfortunately I don't know how to do that :lol:
Agent_24 (57)
1