[LinuxBIOS] Gigabyte's DualBios and recovery from a botched Linuxbios flash?

David Hendricks cro_marmot at comcast.net
Wed Dec 28 11:47:31 CET 2005

Oops--I forgot that I'm not running my old crappy mainboard anymore and
my current one *does* have a socketed PLCC. 

Richard does have a good idea, though. Yhlu added a start and end
exclusion option to flash rom to specify which portions of the ROM to
erase and reprogram. I have not tried it yet as this patch was made
specifically for the pm49fl004 (The standard ROM on a bunch of Tyan
boards). I also seem to recall that this required IO chipset support
for legacy programming mode, but I could be wrong on that point. Still,
perhaps this would help out Mr. Brown if it could be adapted to
whatever his board uses.

PS -- Sorry for the dupe, Richard!

On Wed, 28 Dec 2005 00:06:18 -0600
Richard Smith <smithbone at gmail.com> wrote:

> On 12/27/05, David Hendricks <cro_marmot at comcast.net> wrote:
> > MSI does the same thing with their dual BIOS approach--I found
> > out the hard way from purchasing a K8N-Neo3. My advice is to avoid
> > these gimmicky 0v3rc!0ck3r BIOSes and get a BIOS Savior RD-1 or
> > something if you can get your hands on a socketed mainboard.
> If you can find out what the address is that the recovery image jumps
> to after boot then it seems possible to add Linuxbios there without
> nuking your recovery code.
> You would have to modify the flash programer to not erase the sections
> where your recovery stuff was and add some sort of offset ability as
> well.
> > Or, I think someone on this list (Bari Ari?) can modify your board
> > to use socketed flash parts as well.
> Is the flash a PLCC or TSOP?
> --
> Richard A. Smith

More information about the coreboot mailing list