> 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
I have inited the hw sensors in LinuxBIOS for s2881. So you could use
lmsensor to check the FAN speed. The config file is on Tyan web.
For the Fan control, there should more some reg setting...to reduce the
FAN speed winbond and adm1027...
YH
The support code is done, and will be released to public tree after the
CPU is released to public.
YH
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Carl-Daniel
Hailfinger
Sent: Wednesday, April 19, 2006 4:35 PM
To: linuxbios(a)linuxbios.org
Subject: [LinuxBIOS] Support for AM2 processors?
Hi,
since the upcoming AM2 processors will have a new (DDR2)
memory controller, does that mean the RAM initialization
has to be rewritten completely? If so, is there any expected
time when LinuxBIOS support for these processors will be
available?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
What's the current status of LinuxBIOS on plain EPIA boards? It seems
to be very unclear. The "Supported motherboards" Wiki page lists it,
but has a lot of "???". The build tutorial page -- like all the others
-- links to nothing. The FreeBIOS howto says it doesn't have VGA
support, though that is of course two years out of date.
When I build it, the generated BIOS image is 256k -- which doesn't leave
space to prepend a VGA BIOS. So is the status of LinuxBIOS on these
boards the same as it was with FreeBIOS 2 years ago?
Thanks
-Alex Mauer "hawke"
Hmm... Let me back up a step. I'm apparently answering a question
you're not asking. Your problem is that you want to disable the
internal video (and PCI header) and use external, right? Is that it?
-- Steve G.
Steve Goodrich (Steven.Goodrich(a)amd.com)
Advanced Micro Devices, Inc.
-----Original Message-----
From: Richard Smith [mailto:smithbone@gmail.com]
Sent: Thursday, April 27, 2006 4:11 PM
To: Goodrich,Steven
Cc: LinuxBIOS
Subject: Re: [LinuxBIOS] MB1030 / 3036 VGA comes up :D
On 4/27/06, Goodrich,Steven <steven.goodrich(a)amd.com> wrote:
> We have an older board (from before I came to be with AMD) which was
built with a GXm, CS5530, and NSC 97317 SIO. I can pull preferred
register settings from a document if that would help.
Yes those would probally help..
> Our preferred settings for this platform were:
>
> BC_XMAP_1 = 0x1300C060
> BC_XMAP_2 = 0x09999999
> BC_XMAP_3 = 0x99****99 (* = don't care)
Or perhpaps just confuse things more. 9's in XMAP2 is PCI accessable,
No Cache, No Write, Read.
I'm not sure how you would load the shadow copy of the bios into this
range with write disabled . Until we started setting the write bit for
these ranges the emulator was getting all 0xFFs for its data.
> Are you loading an SMM handler on this platform?
Dosen't look like it. Is that a big problem? I know for the gx2 it's a
big issue since it dosen't have PCI config space without it. But this
part seems to have PCI config method #1 without SMM.
--
Richard A. Smith
Hi YH and list,
I've been playing with the boot prompt timeouts for Etherboot/filo on my
setup.
I've noticed that if I set the combined timeout (the etherboot ASK_BOOT and
filo AUTOBOOT_DELAY) to less than about 3 seconds, the system won't boot
because filo doesn't see the SATA drives. This example has ASK_BOOT set to -1
(i.e. disabled), and AUTOBOOT_DELAY set to 2 seconds.
---------------------------
Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 1.3
33:stream_init() - rom_stream: 0xfffc0000 - 0xfffdffff
Found ELF candiate at offset 0
Loading Etherboot version: 5.4.1
Dropping non PT_LOAD segment
New segment addr 0x10000 size 0x49090 offset 0x0 filesize 0xf7f0
(cleaned up) New segment addr 0x10000 size 0x49090 offset 0x0 filesize 0xf7f0
Loading Segment: addr: 0x00000000bff90000 memsz: 0x0000000000032000 filesz:
0x000000000000f7f0
Clearing Segment: addr: 0x00000000bff9f7f0 memsz: 0x0000000000022810
Loading Segment: addr: 0x0000000000042000 memsz: 0x0000000000017090 filesz:
0x0000000000000000
Clearing Segment: addr: 0x0000000000042000 memsz: 0x0000000000017090
Jumping to boot code at 0x100b0
CPU 2064 Mhz
Etherboot 5.4.1 (GPL) http://etherboot.org
Drivers: TG3 FILO Images: NBI ELF
Protocols: DHCP TFTP
Relocating _text from: [000100e0,00059090) to [bfeb7050,bff00000)
Probing pci disk...
[FILO]FILO version 0.4.1 (root(a)countzero.vandewege.net) Fri Apr 21 18:47:00 EDT 2006
Press <Enter> for default boot, or <Esc> for boot prompt... 2^H ^H1^H ^Htimed out
boot: hde1:/linuxbios.elf
No drive detected on IDE channel 2
boot: hde1:/linuxbios.elf^H ^H^H ^Hlf
Drive 4 does not exist
boot: hde1:/linuxbios.elf
---------------------------
This is only a problem for a cold boot, i.e. from power off. If I do a warm
reboot, the system boots fine.
Is there something that can be done about this? It seems silly to have to
introduce delays in the bootup sequence to make booting from SATA possible,
particularly since fast bootup is one of LinuxBIOS's strengths.
Thanks,
Ward.
--
Ward Vandewege <ward(a)fsf.org>
Free Software Foundation - Senior System Administrator
1. need to add acpi support in s2881 LinuxBIOS support to get it.
Anyway 8111 acpi support is already there in Serengeti_leopard, so it
will be easy to get that.
YH
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Ward Vandewege
Sent: Monday, April 10, 2006 3:43 PM
To: linuxbios(a)linuxbios.org
Subject: [LinuxBIOS] some more tyan/s2881 questions
So the board is stable now. That's great.
Some observations:
1. 'halt' no longer powers the machine off, which it does with the
proprietary bios. 'halt -p' does the job though. LinuxBIOS oddity?
2. reboots seem to cause problems sometimes. I'm not sure yet what
causes
this, but I've had problems with the machine hanging after
ACPI: Unable to locate RSDP
It normally sits there for a few seconds, but I had the machine in such
a
state that it simply hung at that point.
This may have had something to do with the IPMI card, which I'm
experimenting
with. I had to unplug the power before this problem went away, a cold
restart
didn't help. I will do more testing to see if I can pinpoint this.
Thanks for all your help so far!
Ward.
--
Ward Vandewege <ward(a)fsf.org>
Free Software Foundation - Senior System Administrator
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
Hi,
while I've been working on FILO and OpenBIOS lately I really wished
that they could be used as nrv2b compressed payload, like its possible
with etherboot.
Since etherboot is probably not going to be developed beyond v5.5 and
because the zelf support in etherboot is really ugly, I thought of an
alternative to support compressed payloads easily.
So I wrote a new stream which can be enabled by using
CONFIG_COMPRESSED_ROM_STREAM instead of CONFIG_ROM_STREAM.
When you enable CONFIG_COMPRESSED_ROM_STREAM, the payload you specify
will completely automatically be compressed during the build stage, so
you don't have to do anything except safe space with a few small
changes.
Stefan
--
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: info(a)coresystems.de • http://www.coresystems.de/
