Hello.
I am looking for M/B with these specs.
1. Boots fast (2 or 3 secs) with linuxbios ( or other utils).
2. Supports VGA, including X.
3. High performance. Like over 2GHz or such.
How about S2850? it suppors VGA with X?
Or, you know any other M/B?
--- Okajima
Do you know any other fast boot solution than linuxbios?
I tested Via fast boot util, but it is not so fast...
For example, how about this.
General Software Embedded BIOS
http://www.gensw.com/pages/prod/firmbase/firmbase.htm
--- Okajima, Jun. Tokyo, Japan.
Hi list,
I'd like to know the exact support status of LinuxBIOS on VIA EPIA
M10000 (Nehemiah) CentaurHauls Stepping 5. I've seen messages (August
2005) that say VGA is supported, and more recent threads that say it
isn't. So, what is supported by the mainstream LinuxBios v2 ? And what
is not yet?
Are these any patches around that could achieve better support?
All different messages I see are rather confusing ...
Another question: VIA has published a "FastBoot" BIOS that seems to be a
fork of LinuxBIOS, since it's a fork and LinuxBIOS is covered by GPL, is
FastBoot a GPL violation? Someone has ever had the sources of FastBoot?
If ever, could it lead to a better support of EPIA motherboards?
Thanks for you answers,
Tristan
Hi,
I download a lateset snapshot from linuxBIOS.org yesterday. I don't know if it is bad luck or something, I can not successfully build any BIOS from the tree I downloaded. I tried following three platform.
tyan/s2891
tyan/s2895
amd/serenade
Does anybody has similar issue or know what happened?
Below are the details on the things I got for these three different target platform
1. Both tyan/s2891 and tyan/s2895 have similar behavior
I changed a few lines in Options.lb:
default USE_DCACHE_RAM=1
default CONFIG_USE_INIT=1
default DEFAULT_CONSOLE_LOGLEVEL=7
default MAXIMUM_CONSOLE_LOGLEVEL=7
I get a error output like below: (Note: Changing options in the Options.lb above were not the cuase of the problem. Without changing USE_DCACHE_RAM and CONFIG_USE_INIT, I still get same results)
------------
gcc -m32 -nostdlib -nostartfiles -static -o linuxbios_ram -T /export/1/new/src/config/linuxbios_ram.ld linuxbios_ram.o
linuxbios_ram.o(.text+0x13db9): In function `smp_write_config_table':
: undefined reference to `get_apicid_base'
collect2: ld returned 1 exit status
make[1]: *** [linuxbios_ram] Error 1
make[1]: Leaving directory `/export/1/new/targets/tyan/s2895/s2895/normal'
make: *** [normal/linuxbios.rom] Error 1
2. amd/serenade gets the build error like below. It probably is the side product of the tree enabled dual core and cache as RAM?
-----
gcc -m32 -nostdlib -nostartfiles -static -o linuxbios_ram -T /export/1/new/src/config/linuxbios_ram.ld linuxbios_ram.o
linuxbios_ram.o(.text+0x14d2): In function `model_fxx_init':
: undefined reference to `get_node_core_id'
linuxbios_ram.o(.text+0x14e6): In function `model_fxx_init':
: undefined reference to `amd_sibling_init'
collect2: ld returned 1 exit status
make[1]: *** [linuxbios_ram] Error 1
make[1]: Leaving directory `/export/1/new/targets/amd/serenade/serenade/normal'
make: *** [normal/linuxbios.rom] Error 1
Any help would be appriciated.
Thanks
Beneo
Who want it? LinuxBIOS, current System BIOS or EFI?
For LinuxBIOS, We will use LinuxBIOS+tiny kernel for booting. The Tiny
kernel could include IB and IP over IB, So we don't need to port driver
from kernel to everywhere....
YH
________________________________
From: etherboot-developers-admin(a)lists.sourceforge.net
[mailto:etherboot-developers-admin@lists.sourceforge.net] On Behalf Of
Eli Cohen
Sent: Wednesday, November 09, 2005 3:53 AM
To: etherboot-developers(a)lists.sourceforge.net
Subject: [Etherboot-developers] Infiniband driver
Hi,
We have developed a driver for Mellanox's HCA device MT23108. In our
plans is a to add support for a second line of devices. This will allow
a host having an HCA to use it for doing remote boot. It is based on
Etherboot and we would like to open the source to the public and we
would like it to be part of Etherboot. I would like to know how to move
in this direction.
Thanks
Eli
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When the going gets tough the tough get going
I'm sticking this back on the list so others can suggest things as well.
On 11/9/05, Anton Borisov <a.borisov(a)tesv.tmb.ru> wrote:
> On Tue, 8 Nov 2005 23:56:53 -0600
> Richard Smith <smithbone(a)gmail.com> wrote:
>
> > > > See if you can load any payload at all or if its just the ADLO payload
> > > > thats causing you trouble. Try memtest without the video bios so you
> > > > don't have to change any settings.
> > >
> > > You're quite right - ADLO payload causing this problem. FILO just works perfectly. I'm ready to blame the size of my ADLO payload ;-) - more then 120 kb. But I wasn't able to start ADLO without VIDEO as well.
> > >
> >
> > So ADLO with no video bios won't load either? Do you still get an elf
> > load error?
>
> I probed 2 versions of ADLO: with integrated VIDEO ROM and without it. Sizes accordingly are 58Kb and 124Kb. Tracing with minicom revealed the same effect -
> ==
> Found ELF candiate at offset 0
> Cannot Load ELF Image
> ==
> Maybe I've run into improper understanding of XIP_ROM_SIZE and ROM_SIZE params inside Config.lb, but I doubt this ;-)
I don't think your problem is related to size. The elf image is found
but failed to load properly. I believe the size is embedded in the
elf segment. If your sizes were all wrong I would expect that it
either wouldn't boot or it would not find the payload.
Are you using XIP? If so you might try turning it off.
You will probally have to go look in the elf load code and see what
causes that message I've not looked at the elf load code so I don't
have many suggestions.
Is you adlo.elf really a valid elf image? What do you get for a
'readelf -a adlo.elf'
--
Richard A. Smith
Hi.
I have compiled ADLO from LX1 (freebios--devel--1.0--base-0.tar.bz2). Pure BOCHS BIOS ~58k. Payload with VGABIOS - 124k.
My Config.lb is below:
=
target epia-m
mainboard via/epia-m
option MAXIMUM_CONSOLE_LOGLEVEL=8
option DEFAULT_CONSOLE_LOGLEVEL=8
option CONFIG_CONSOLE_SERIAL8250=1
option ROM_SIZE=256*1024
option HAVE_OPTION_TABLE=1
option CONFIG_ROM_STREAM=1
option HAVE_FALLBACK_BOOT=1
option FALLBACK_SIZE=0x30000
option _RAMBASE=0x00004000
romimage "fallback"
option USE_FALLBACK_IMAGE=1
option ROM_IMAGE_SIZE=0x10000
option ROM_SECTION_OFFSET=0x10000
option ROM_SECTION_SIZE=0x30000
option LINUXBIOS_EXTRA_VERSION=".0Fallback"
payload /home/anthony/src/payloads/adlo.elf
end
buildrom ./linuxbios.rom ROM_SIZE "fallback"
=
Some comments regarding FALLBACK_SIZE. This is done intentionally to include VIA's VGABIOS into fallback portion.
linuxbios.rom being composed this way is written into flash chip.
Unfortunately I wasn't able to load ADLO payload (see messages below).
=
Moving GDT to 0x500...ok
Wrote linuxbios table at: 00000530 - 00000b28 checksum 97d3
Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 1.3
33:stream_init() - rom_stream: 0xfffd0000 - 0xfffeffff
Found ELF candiate at offset 0
Cannot Load ELF Image
=
I assume this is a problem with improper configuring ROM_IMAGE_SIZE, ROM_SECTION_OFFSET in my example. I did increase it to 0x20000 value. And I've got this error while compiling with ROMCC:
=
./romcc -mcpu=c3 -O -I/home/lx/src/LinuxBIOSv2-2080/src -I. -I/home/lx/src/LinuxBIOSv2-earlymtrr.c:21.45: Integer constant to large
=
Where I've done wrong? Does anybody experienced with ADLO applying to LX2 recently?
Thanks.
--
Sincerely, Anton Borisov
Northbridge.c cpu_bus_scan need to be modified too, you need to assume
the CONFIG_LOGICAL_CPU==1 there..
YH
-----Original Message-----
From: linuxbios-bounces(a)openbios.org
[mailto:linuxbios-bounces@openbios.org] On Behalf Of Lu, Yinghai
Sent: Monday, November 07, 2005 3:55 PM
To: Greg Johnson
Cc: linuxbios(a)openbios.org
Subject: Re: [LinuxBIOS] dual core disable?
OK,
We may need to set the nbcfg 54 bit even disable the dual core.
Please several lines
1. src/cpu/dualcore/dualcore.c
//If(read_option(CMOS_VSTART_dual_core.....
2. in you cache_as_ram_auto.c
//#if CONFIG_LOGICAL_CPUS == 1
Set_apicid_cpuid_lo();
//#endif
YH
-----Original Message-----
From: Greg Johnson [mailto:gjohnson@lanl.gov]
Sent: Monday, November 07, 2005 3:37 PM
To: Lu, Yinghai
Cc: Ronald G Minnich; Greg Johnson; linuxbios(a)openbios.org
Subject: Re: [LinuxBIOS] dual core disable?
On Mon, Nov 07, 2005 at 03:00:09PM -0800, Lu, Yinghai wrote:
> ?
>
> In Normal BIOS, is there option to disable dual core?
>
No. I'm pretty sure that I'm really getting two cores on one socket.
Memory bandwidth is affected when running on both cores. In any case,
Linux K8 NUMA is confused:
p5:~# numactl --show
policy: default
preferred node: current
cpubind: 0
membind: 0 1
Greg
--
LinuxBIOS mailing list
LinuxBIOS(a)openbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
