Re: [LinuxBIOS] cant detect bios with flash software {Scanned}

:) IT WORKED :)

THANK YOU VERY VERY VERY MUCH :)

sucseval read of original bios (didnt write to it!!) and then write to RD1

have jsut swapped original bios with replacement bios chip, and will write the bios image to that as well.

The original bios will be packed away for save keeping, and ill work on the RD1 bios, and the replacement bios :)

I take it that if it read ok, then thats the file working, or is the writing process diferant? if it is, ill insert the original and try writing for you, jsut to confirm it works, if not, then id say thats a sucesful addition to the source :)

again many thanks

Matt

Stefan Reinauer wrote ..
> Stefan Reinauer  [060630 21:49]:
> > > Im not sure what u mean by verifing that the image starts 25 a6???
>
> are
> > > you talking about an image file taken from the BIOS using VIAs flash
> > > utility?
> >
> > I thought that might be the vendor and device id. In fact it is 8c and
> > 00, as it is a 256kb part
>
> Ok, can you please check out revision 2336. I checked in some untested
> support for your flash part.
>
> Can you try the following:
>
> Please be careful which chip you use at a time. If you mess the order up
> you will most likely render your system unusable ...
>
> make a copy of your bios:
>
> switch to the EFST, then do:
>
> ./flashrom -r legacybios.bin
>
> write the copy to your bios savior
>
> switch to the bios savior (Winbond W49F002U)
>
> ./flashrom -w legacybios.bin
>
> Verify the copy in the bios savior
>
> ./flashrom -v legacybios.bin
>
> Overwrite the EMST flash to see if the new flashbios version works
>
> switch to the EMST again!
>
> dd if=/dev/zero of=nullbios.bin bs=256k count=1
>  ./flashbios -w nullbios.bin
>  ./flashbios -v nullbios.bin
>
> (it should say "verified" here!!!!)
>
> then you can write the original bios back to the EMST so you have
> two valid copies for playing later.
>
> ./flashbios -w legacybios.bin
> ./flashbios -v legacybios.bin
>
> Please post the results here..