So the vmlinux+initrd.gz--> elf, and nrv2b to be the payload...
What is size of final elf?
1. bzImage+initrd.gz
2. vmlinux+initrd.gz --> nrv2b
I wonder if 2 would be bigger than 1.
YH
No FILO need...
Use mkelfImage to put tiny kernel and initrd to make one elf. And
LinuxBIOS can treat that as one payload and just like FILO and
Etherboot.
Someone (from F5) has used 2M flash ROM to put LinuxBIOS+kernel+initrd.
You could do that if you want to spare the CF IDE flash.
With the tiny kernel support, we can have support for all driver support
in kernel for SCSI, USB, Firewire, iSCSI, AOE, IB, Myrinet,
quadric...any media.
We don't need to port the driver to the boot loader. And everyone could
focus on driver in kernel instead of waste time to port driver back and
forth.
That is correct way.
Just like we are talking about UEFI support. We could add the table and
services in LinuxBIOS, but we like to run uefi as linux application on
kernel to re use the driver in kernel.
We don't need to spend dev time on FILO and Etherboot anymore.
YH
-----Original Message-----
From: Myles Watson [mailto:myles@mouselemur.cs.byu.edu]
Sent: Thursday, May 18, 2006 6:49 AM
To: Lu, Yinghai; linuxbios(a)linuxbios.org
Subject: RE: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895
It's starting to seem like a long chain of events from LinuxBIOS to
Etherboot to FILO to kernel on CF to myKernel. I'd also like to be able
to
get to grub eventually. Is there a way to go from LinuxBIOS to grub
more
directly on the s2895?
Thanks again for your help.
Myles
-----Original Message-----
From: Lu, Yinghai [mailto:yinghai.lu@amd.com]
Sent: Wednesday, May 17, 2006 5:09 PM
To: myles(a)mouselemur.cs.byu.edu; linuxbios(a)linuxbios.org
Subject: RE: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895
You can not boot from CK804 sata directly with FILO in Etherboot.
The code only support Sata that can work on compatible IDE mode.
You need to use other media ( network, CF IDE flash) to load kernel with
ck804 sata and kexec support, and use kexec to load final kernel in your
sata disk.
YH
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Myles Watson
Sent: Wednesday, May 17, 2006 3:57 PM
To: linuxbios(a)linuxbios.org
Subject: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895
I am booting linuxbios with etherboot and filo as the payload. I tried
to
follow the s2881 tutorial on the wiki.
Etherboot only finds my cd-rom. When I try to use hde:/ it tells me that
"Drive 4 does not exist". All drives up to j except hda (my cd-rom) give
the
same error message. Sometimes if I try hdg it hangs.
I saw README.filo_in_etherboot where it says it only works on SATA port
1 or
2. I've tried on SATA 0 port 0 and 1, SATA 1 port 2 and 3.
I also seem to need to boot the factory BIOS in between each attempt, or
I
won't get very far.
Is there something simple I've missed?
Thanks,
Myles
Output:
Etherboot 5.4.2
Drivers: TG3 FILO Images: NBI ELF
Protocols: DHCP TFTP
Relocating text ...
Scanning PCI: found 30 devices
Probing pci disk...
[FILO]FILO version 0.4.1
boot: hde3:/boot/vmlinuz... initrd=/boot/initrd...
IDE time out
No drive detected on IDE channel 2
boot: hdc:/
No drive detected on IDE channel 1
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
I have an nrv compressed filo.elf that on linux I can uncompress and have
work.
~/src/LinuxBIOSv2/util/nrv2b/nrv2b d /tmp/filo.elf.nrv /tmp/xyz
39496
in linuxbios, the uncompress is too short:
rom_stream: 0xfff90000 - 0xffff7fff
Uncompressing to RAM 0x00200000 olen = 0x000062fc done.
Cannot Load ELF Image
print/x 39496
$1 = 0x9a48
Any idea what to look for?
ron
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"
fuefi is good.
YH
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Ronald G Minnich
Sent: Wednesday, May 17, 2006 8:42 AM
To: Bryan E. Chafy
Cc: linuxbios(a)linuxbios.org
Subject: Re: [LinuxBIOS] UEFI discussion
Bryan E. Chafy wrote:
>>What do you think?
>
>
> IMO, lots of members-only "standards bodies" that should really end
> in .com instead of .org
>
> is reality
> ----------------------
> uefi.org -> uefi.com
> vesa.org -> vesa.com
> iso.org -> iso.com
> ieee.org -> ieee.com
> pcisig.com -> ok
> wikipedia.org -> ok, so far
>
> Maybe start by making a new framework that is similar/compatible but
not
> exactly the same as UEFI. Call it FUefi or something :)
>
I own both openefi.org and free-efi.org
ron
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
I am booting linuxbios with etherboot and filo as the payload. I tried to
follow the s2881 tutorial on the wiki.
Etherboot only finds my cd-rom. When I try to use hde:/ it tells me that
"Drive 4 does not exist". All drives up to j except hda (my cd-rom) give the
same error message. Sometimes if I try hdg it hangs.
I saw README.filo_in_etherboot where it says it only works on SATA port 1 or
2. I've tried on SATA 0 port 0 and 1, SATA 1 port 2 and 3.
I also seem to need to boot the factory BIOS in between each attempt, or I
won't get very far.
Is there something simple I've missed?
Thanks,
Myles
Output:
Etherboot 5.4.2
Drivers: TG3 FILO Images: NBI ELF
Protocols: DHCP TFTP
Relocating text ...
Scanning PCI: found 30 devices
Probing pci disk...
[FILO]FILO version 0.4.1
boot: hde3:/boot/vmlinuz... initrd=/boot/initrd...
IDE time out
No drive detected on IDE channel 2
boot: hdc:/
No drive detected on IDE channel 1
Hi,
I was about to have a look at implementing UEFI, when I noticed the
following:
I understand that I may download and read the UEFI 2.0
specification without the requirement of a license, and doing so
creates no obligations or commitments on my part. I further
understand and acknowledge that any distribution, additional
reproduction, implementation or other use of the specification
requires a license, which can be obtained by executing the UEFI
Adopters' Agreement.
Reading further, this means I have to pay a yearly (voluntary?) fee to
be allowed to do anything with the UEFI spec.
Is there any interest at all in an Open Source UEFI implementation?
This discussion is popping up from time to time but it is never really
getting forward yet.
What do you think?
Best regards
Stefan Reinauer
--
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/
Then you have to look at efi support code in Linux kernel, and feed the
code with it wants.
YH
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Bryan E. Chafy
Sent: Wednesday, May 17, 2006 8:26 AM
To: linuxbios(a)linuxbios.org
Subject: Re: [LinuxBIOS] UEFI discussion
> What do you think?
IMO, lots of members-only "standards bodies" that should really end
in .com instead of .org
is reality
----------------------
uefi.org -> uefi.comvesa.org -> vesa.comiso.org -> iso.comieee.org -> ieee.compcisig.com -> ok
wikipedia.org -> ok, so far
Maybe start by making a new framework that is similar/compatible but not
exactly the same as UEFI. Call it FUefi or something :)
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
Good.
That will make you boot time longer. Because the com2 only need to set
to 19200.
YH
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Ward Vandewege
Sent: Tuesday, May 16, 2006 2:46 PM
To: linuxbios(a)linuxbios.org
Subject: [LinuxBIOS] COM2 in tyan/s2881
Hi there,
It seems COM2 is disabled by default in the s2881/Config.lb file. Since
the
board has a COM2 connector, and it is what you would use with the IPMI
daughter card, would it make sense to enable it by default?
I've got IPMI console redirection working by letting FILO 0.5 (in grub
mode)
and the kernel talk to COM2 instead of COM1. COM2 is connected to the
IPMI
card. With the latest ipmitool snapshot
(http://ipmitool.sourceforge.net/snapshot/), that gives me have a serial
console over the network without extra hardware (other than the IPMI
card).
Pretty brilliant!
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
