> On Wed, Aug 03, 2005 at 11:59:20AM +0900, Jun OKAJIMA wrote:
> > Probably, most guys here use BIOS Saver.
> > And it works well?
> > In mine, RD1 for PLCC gets not being writable suddenly.
> > I mean, it seems writable but # flash_rom -v fails.
> > I solved this problem by a quick hack.
> >
> > How about yours? You can write RD1 or W49F002U well?
> > Any problem happen?
Johnathan McDowell wrote:
> Even after that it's sometimes a bit flakey and I have to erase, then
> write it. I've put the board's original BIOS in the RD1 and am writing
> to the SST 39SF020A instead, which works without problems.
I've read posts about the RD1 that suggest its integrated flash device
is low quality and it may take 10 or more flash attempts to get a good
flash update to the RD1 flash device.
As a result, many RD1 BIOS Savior users will flash the commercial
BIOS image (or other known good BIOS image) into the RD1 integrated
flash device as many times as needed to get an image that boots.
Then use the original BIOS device to flash test BIOS image (usually
LinuxBIOS images among this group), since the original BIOS device
usually flashes OK on the first attempt.
I've used the RD1 in the above fashion with great success on the
Tyan S2885 mainboard.
The same RD1 would not work on the nVidia CK8-04 CRB mainboard.
I think the CK8-04 CRB requires a flash device that the RD1 does
not support. However, the RD1 worked well as an "do nothing" adapter
which allowed swapping the BIOS flash device between my flash burner
and the mainboard without any wear to the mainboard's BIOS socket.
BTW, my flash burner is an older Enhanced Willem Universal Programmer.
I got mine for only $60 US over a year ago. I've seen it for less
than $40 on eBay a few weeks ago. The newest model is going for about
$50 US. It does a LinuxBIOS flash in about 5 minutes; not bad for a
$60 burner. However, it does require changing DIP switches to match
an image for each device it can program. Great for the amateur or
professional with a small budget.
> > BTW, a cable of your RD1 is not broken?
> > I needed soldering to fix it.
> Mine was fine out of the box.
Mine cable and switch worked fine out of the box as well.
Sincerely,
Ken Fuchs <kfuchs(a)winternet.com> ami-mac-sun
Please check the issue 41, I make K8 MB can be compiled, and It include
bus0/dev0 and fidvid change enhancement
HT_CHAIN_UNITID_BASE
Default is 1, and if it is 6, then amd8131 will be from 6, also
if it is 0, will assume ht chain only have one HT device...
HT_CHAIN_END_UNITID_BASE
Default is 0x20 --- mean do not use that, if it is 0, the
amd8111 will be dev0
SB_HT_CHAIN_UNITID_OFFSET_ONLY
Default is 1, so if HT_CHAIN_UNITID_BASE!=1, will only offset
unitid of SB CHAIN.
K8_SB_HT_CHAIN_ON_BUS0
Deault is 0, if it is 1, will put sb chain on bus 0, even for
S2885 sb ht is on link2, it will put on bus0.
K8_SET_FIDVID in cache_as_ram_auto.c or auto.c
Fidvid change to sync the fid on 4 way or more system with different cpu
installed....
Put following sequence in your cache_as_ram_auto.c after ht is set.
enable_fid_change();
enable_fid_change_on_sb();
init_fidvid_bsp(bsp_apicid);
please check init_cpus.c and fidvid.c and amd8111_early_ctrl.c for
detail....
YH
I am going to start trying to catch up our svn info.
Will those of you have a mobo working, please send me:
the mobo name
the xvn revision
so I can fill out the table.
ron
Hi greg,
coming back on your thread-entry. We would like to get the
IWILL DK8-HTX Rev. 1.0 running. Is it possible to use devbios
or mtd to access the bios or is the hardware flash programmer
the only possible (better) way?
The board uses an AMIbios, SVR 2000, AA46 (6827) with the following
layout:
(x7)
, , , , , , ,
- -
- -
- -
- -
- - (x9)
- -
- -
- -
- -
, , , , , , ,
What hardware flash programmer would you suggest to get started?
thx a lot
-- phil
On Fri, Dec 09, 2005 at 08:24:34AM -0600, Young, Jeff wrote:
>
> > I see that the Iwill board dk82s is supported? Does anyone know
> > if the dk8-hkt board will work? It
> > is interesting because it has an HTK connector on it.
>
> Do you mean the DK8-HTX ? If so, we ran LinuxBios during initial
> bring-up of this board, and I believe we contributed back the changes
> we needed for it.
>
>
> -- greg
Young, Jeff S. wrote:
>
>
> Howdy folks,
>
> I have been trying to build the tyan s2895 board with gcc
> 3.3 on SuSE 10.0
>
> It doesn’t build. The loader tries to overlap some sections. I got
> around this by
>
> laying out my own ldscript.lb file (similarly to what Ron wants to do).
sorry for this confusion, but what you did and what I am doing are
totally unrelated.
I am merely proposing to mod the standard LinuxBIOS makefile so that the
ldscript.ld is not a sequence of INCLUDE statements, but instead a
sequence of ld commands. (Sorry, folks, I have not done this yet)
What you did is hack the ldscript.ld script to make things fit. This is
going to burn you big time next time you need to run buildtarget -- you
will lose those changes. You need to set proper options in your
targets/tyan/s2895/Config.lb -- for best results, however, make your own
copy of that file.
Please see my linux journal web article, wherein the way you size rom
images is explained.
Sorry you are having trouble, we are looking at this board too and will
try to make sure it works.
thanks
ron
Howdy again,
Things are getting better now, so I wanted to keep everyone
up to date with what I had
To do in order to get as far as I have.
System: Tyan s2895 with 2 Dual Core AMDs and 8GB
memory
BIOS: Using RD1 Bios savior (4mbit)
OS: Linux - SuSE 10.0 stock (ie, gcc 4)
Build issues: when building, there was an overlapping
section. I created the following
Section and it fixes it:
.rodata. : {
*(.rodata.str1.*);
}
This was placed after .rom section
Payload not found. It wasn't clear
from the writeup that I had to get the
Payload from the web site. Stefan
was an immense help in this arena.
Maybe the payload directory should
be bundled with the snapshots because
You need it anyway.
Run issues: I build the s2895 bios (fallback and
normal) and flash the RD1. I don't know
If the fact that the RD1 is 4mbit
and the original chip was 8mbit will cause any
Problems. The BIOS starts up just
fine until the time comes to enable the cache
The second time around. (This is
after the device enumeration and is in the
Initialization stuff.) It hangs
right after the code gets cr0 to update it.
I get the impression that I am the only one seeing these
issues. It seems that everyone else
Can just build and run. Is this really true? If you just grab
snapshot 2163, untar it, and buildtarget tyan/s2895
Cd tyan/s2895/s2895, and make, it does it just fine???
Any ideas on the cache enable?
Thanks,
Jeff
* Young, Jeff S. <Jeff.Young(a)gd-ais.com> [060125 12:21]:
> objcopy --gap-fill 0xff -O binary linuxbios linuxbios.strip
>
> ./buildrom linuxbios.strip linuxbios.rom ../../../../payloads/
> forcedeth--filo_hda2_vga.zelf 0x20000 0x40000
>
> ../../../../payloads/forcedeth--filo_hda2_vga.zelf: No such file or directory
It does not find your payload image.
try using an absolute path in your target configuration file
You said you are using gcc 3.3 in suse 10. Did you install this compiler
yourself? I use the same distribution, but I have gcc 4 installed.
> PS: Can anyone actually build the S2895 without any errors
> today? If so, exactly how do you do it. (Note that I have tried
> several snapshots from 2007 -> 2163 without success.)
It builds fine here, see build log
http://snapshots.linuxbios.org/stats/abuild-LinuxBIOSv2-2163.log
Your gcc might make things larger than gcc 4 which is why you saw the
overlap error. increasing ROM_IMAGE_SIZE(?) should help without changing
the LD script.
Also I am pretty sure you get your image compiling when you fix your
payload path above..
Stefan
