coreboot

coreboot@coreboot.org

12 participants
39779 discussions

答复: 答复: FILO 0.4 [PMX:#]
by YhLu 06 Apr '04

06 Apr '04

choose_stream can be moved into freebios2. hardware main can call that before elfboot. Need to get boot_order from CMOS and device load which pay load first. YH -----邮件原件----- 发件人: Steven James [mailto:pyro@linuxlabs.com] 发送时间: 2004年4月6日 11:38 收件人: YhLu 抄送: ron minnich; Eric W. Biederman; Takeshi Sone; linuxbios(a)clustermatic.org 主题: Re: 答复: FILO 0.4 [PMX:#] Greetings, You can use bootselect in utils/baremetal to choose between multiple payloads. G'day, sjames -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 2701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 ----------------------------------------------------------------------- On Tue, 6 Apr 2004, YhLu wrote: > So you must use filo as normal payload and Etherboot as fallback payload. > > Then if I want to boot from network in normal mode, how to do? > > Why just merge filo into Etherboot? > > So we can use tg3--filo.zelf instead of tg3--ide_disk.zelf. > > Regards > > YH > > -----邮件原件----- > 发件人: ron minnich [mailto:rminnich@lanl.gov] > 发送时间: 2004年4月6日 10:28 > 收件人: Eric W. Biederman > 抄送: Takeshi Sone; linuxbios(a)clustermatic.org > 主题: Re: FILO 0.4 [PMX:#] > > On 5 Apr 2004, Eric W. Biederman wrote: > > > I am looking at using FILO as a disked based bootloader. So I might > > just write that code and send you a patch. > > We want FILO in FLASH, not on disk. We are using FLASH-based FILO to > replace FLASH-based Etherboot on Pink and will be using FILO to replace > Etherboot on Lightning and Blue Steel to load images from IDE-FLASH. We > are very happy with its capability in that mode. It's just a ton easier > for a sysadmin to mount the IDE-FLASH as ext2 and change kernel file names > instead of dd-ing raw kernel images onto an IDE-FLASH. FILO lets us treat > IDE-FLASH as a file system, and Etherboot had us treating it as a raw > disk. We prefer FILO at this point, and I think we will not be the only > ones. Also we have found the build procedure for FILO to be less prone to > error and problems than for Etherboot. > > That's not to say Etherboot does not have *many* applications: it is > terrific for lots of things, just not for our clusters right now. > > > Right now I think a bootloader of this type with a config file is > > not terribly useful. > > It is all context. I think we need to turn our thinking a bit. The BIOS > you use is going to become more application-specific. What you have in an > embedded "black box" will not need to be identical to what you have on > your desk or your cluster. I think this is all to the good. > > ron > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

1 0

答复: FILO 0.4 [PMX:#]
by YhLu 06 Apr '04

06 Apr '04

So you must use filo as normal payload and Etherboot as fallback payload. Then if I want to boot from network in normal mode, how to do? Why just merge filo into Etherboot? So we can use tg3--filo.zelf instead of tg3--ide_disk.zelf. Regards YH -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2004年4月6日 10:28 收件人: Eric W. Biederman 抄送: Takeshi Sone; linuxbios(a)clustermatic.org 主题: Re: FILO 0.4 [PMX:#] On 5 Apr 2004, Eric W. Biederman wrote: > I am looking at using FILO as a disked based bootloader. So I might > just write that code and send you a patch. We want FILO in FLASH, not on disk. We are using FLASH-based FILO to replace FLASH-based Etherboot on Pink and will be using FILO to replace Etherboot on Lightning and Blue Steel to load images from IDE-FLASH. We are very happy with its capability in that mode. It's just a ton easier for a sysadmin to mount the IDE-FLASH as ext2 and change kernel file names instead of dd-ing raw kernel images onto an IDE-FLASH. FILO lets us treat IDE-FLASH as a file system, and Etherboot had us treating it as a raw disk. We prefer FILO at this point, and I think we will not be the only ones. Also we have found the build procedure for FILO to be less prone to error and problems than for Etherboot. That's not to say Etherboot does not have *many* applications: it is terrific for lots of things, just not for our clusters right now. > Right now I think a bootloader of this type with a config file is > not terribly useful. It is all context. I think we need to turn our thinking a bit. The BIOS you use is going to become more application-specific. What you have in an embedded "black box" will not need to be identical to what you have on your desk or your cluster. I think this is all to the good. ron _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

3 2

FILO 0.4
by SONE Takeshi 06 Apr '04

06 Apr '04

I just released FILO 0.4. http://te.to/~ts1/filo/ It can boot distro CDs if you give a proper command line. SuSE 8.2 LiveEval CD worked without a glitch, I enjoyed the KDE desktop, OpenOffice, etc, from the CD on an EPIA booted from LinuxBIOS. Also added support for booting from BIOS flash, to boot an alternative bootloader like Etherboot. PCI support in IDE driver is also added (or recovered), but the native PCI mode is not fully tested. I tried to configure EPIA (V1) code to use native mode, and the ports read something not 0xff, but the drive doesn't respond to soft reset. I don't know the bug is in FILO, LinuxBIOS, or the hardware. I'll work on config file support next time. Version 0.4 ts1 2003-10-15 * Support for ATAPI CD-ROM. * ISO-9660 filesystem is taken from a GRUB patch by Leonid Lisovskiy <lly(a)pisem.net>. The filesystem code was originally written by Kousuke Takai <tak(a)kmc.gr.jp> for GRUB/98 project. * Support for mounting boot disk image of El Torito bootable CD-ROM. ("hdc1" means the boot disk image of the CD-ROM at hdc.) * Support for memory as device, raw device as image, and user-specifiable device offset and length. (eg. boot: mem@0xfffd0000,0x10000) * PCI support in IDE driver. Now it by default uses PCI enumeration to find the PCI IDE controller, and can use native PCI mode if the controller is configured to this mode by BIOS. To disable this, turn off SUPPORT_PCI. * Fixed Linux loader to boot RedHat 9 kernel properly. -- Takeshi

8 23

Re: FILO 0.4 [PMX:#]
by Takeshi Sone 06 Apr '04

06 Apr '04

Eric, Sorry for not replying soon. I've been busy with real job and life, config file support is not yet written, though I'm still willing to do it (+ USB support etc..) This situation would not seem to change in a month or two.. > -----Original Message----- > From: ebiederman(a)lnxi.com (Eric W. Biederman) > Sent: 04 Apr 2004 21:10:51 -0600 > To: ron minnich <rminnich(a)lanl.gov> > Subject: Re: FILO 0.4 [PMX:#] > > ron minnich <rminnich(a)lanl.gov> writes: > > > On Sun, 4 Apr 2004, Yinghai Lu wrote: > > > > > I have checked the Etherboot, and it would be some easier to integrate filo > > > into Etherboot. > > > > Not everyone here at LANL is that satisfied with etherboot, and in fact we > > are moving over to FILO. There are a lot of reasons. We\'ve just had lots > > better luck with FILO when all things are considered. > > Ron, is LANL going to maintain FILO then? > > Unless I hear from SONE soon it is starting to look like like FILO is > unmaintained. > > Has any one implemented config files? > Has any one implemented listing of files? > > What do you do when you don\'t have a disk? > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios ___________________________________________________________________________

4 4

int 15 e820h
by YhLu 06 Apr '04

06 Apr '04

Ron, When kernel is loading, it will call int 15, e820h to get memory map. Where does LinuxBIOS put the int 15 e820h processing code? Regards YH

3 2

Largest BIOS Workspace
by Don Brown 06 Apr '04

06 Apr '04

Within BIOS in general and LinuxBIOS in particular, what is the largest workspace available. Are we limited to a 4 meg chip to store LinuxBIOS? Can we build or lever into some larger area? Don Brown, Atlanta GA

3 2

答复: FILO 0.4 [PMX:#]
by YhLu 05 Apr '04

05 Apr '04

Eric, If the put the etherboot and filo in the ROM at the same time for fallback mode, Is it possible to make payload be selected by the elfboot? ( Controlled by cmos layout or key) Or let the Etherboot load another elf in ROM instead of HD? ( in the boot option add BOOT_ELF or BOOT_ZELF together with BOOT_NIC, BOOT_DISK, BOOT_FLOPPY). Regards YH -----邮件原件----- 发件人: Stefan Reinauer [mailto:stepan@openbios.org] 发送时间: 2004年4月5日 5:47 收件人: Eric W. Biederman 抄送: Greg Watson; YhLu; 'SONE Takeshi'; linuxbios(a)clustermatic.org 主题: Re: FILO 0.4 [PMX:#] * Eric W. Biederman <ebiederman(a)lnxi.com> [040405 05:02]: > If we want to take a snapshot of the source tree of FILO or any other > bootloader into the LinuxBIOS tree under util. Build that part of the > build and build a complete romimage that works. I am fine > with that. It is even reasonable to make it so you can drop in > external trees like etherboot and have everything build together > nicely. > > Actual linking things together instead of including them together > is unacceptable. What about the following: Currently LinuxBIOS divides into 2 fundamental parts: 1) hardware initialization 2) getting and starting the payload This second part consists of two parts, again: i) elfloader ii) payload Note, this is only one possible design. Maybe, this design is bloated for some application cases. Eric, you want to make a hard cut between what is LinuxBIOS and what is not. This is generally a good idea, as it keeps the different initialization steps distinct from reach other. What, if we add another cut by dividing hardware initialization frin the payload-loader? Instead of packing stuff like filo to util, we could do: * create a directory loader which can hold all "loaders" * move the elf loader with a Config.lb to a subdirectory in there * create other directories for other "loaders" like filo. If done right, filo can still be compiled as a payload, or built in if the win in size is noticable. A target config file could probably choose which method to use, without overhead. Also, syncing with other trees, like Takeshi's filo tree could be fairly easy, too. I don't think we really have a conflict in direction here at all. LinuxBIOS itself should be as small as possible, and the different parts should be as independent as possible. But we also want to be a lot more flexible than the existing solutions.. > In addition we have had way to many questions of what is the right > policy for a bootloader to implement, on this list. I refuse > to couple that to the LinuxBIOS core. And I don't want some stupid > policy in there like FILO's that would require me to upgrade > my firmware just to upgrade my OS. Please explain, how is filo worse here than putting linux in flash? Stefan

1 0

答复: FILO 0.4 [PMX:#]
by YhLu 05 Apr '04

05 Apr '04

Sone, You may add the zelf make option as Etherboot to make payload smaller. YH. -----邮件原件----- 发件人: Takeshi Sone [mailto:ts1@tsn.or.jp] 发送时间: 2004年4月5日 2:40 收件人: ebiederman(a)lnxi.com 抄送: linuxbios(a)clustermatic.org 主题: Re: FILO 0.4 [PMX:#] Eric, Sorry for not replying soon. I've been busy with real job and life, config file support is not yet written, though I'm still willing to do it (+ USB support etc..) This situation would not seem to change in a month or two.. > -----Original Message----- > From: ebiederman(a)lnxi.com (Eric W. Biederman) > Sent: 04 Apr 2004 21:10:51 -0600 > To: ron minnich <rminnich(a)lanl.gov> > Subject: Re: FILO 0.4 [PMX:#] > > ron minnich <rminnich(a)lanl.gov> writes: > > > On Sun, 4 Apr 2004, Yinghai Lu wrote: > > > > > I have checked the Etherboot, and it would be some easier to integrate filo > > > into Etherboot. > > > > Not everyone here at LANL is that satisfied with etherboot, and in fact we > > are moving over to FILO. There are a lot of reasons. We\'ve just had lots > > better luck with FILO when all things are considered. > > Ron, is LANL going to maintain FILO then? > > Unless I hear from SONE soon it is starting to look like like FILO is > unmaintained. > > Has any one implemented config files? > Has any one implemented listing of files? > > What do you do when you don\'t have a disk? > > Eric > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios ___________________________________________________________________________ _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Linux Startup Times [PMX:#]
by John Usher (Maptek) 03 Apr '04

03 Apr '04

without rc scripts - I'm talking before getting to the starting init stage... -----Original Message----- From: ron minnich [mailto:rminnich@lanl.gov] Sent: Friday, 2 April 2004 12:09 PM To: John Usher (Maptek) Cc: linuxbios(a)clustermatic.org Subject: Re: Linux Startup Times [PMX:#] On Fri, 2 Apr 2004, John Usher (Maptek) wrote: > Linux startup times? Linux on our systems is taking more than 10 seconds > to start, and I guess its due to it searching for devices and the like. with/without the rc scripts? ron

2 1

Can I execute a linuxbios image from linux?
by Svante Signell 03 Apr '04

03 Apr '04

Hello, I'm trying to upgrade the CPU on a 440BX dual board MSI-6210 from dual Celerons (Mendocino) to a single Celeron2 (Tualatin) using a socket 370 to slot 1 adapter, SLOT-T from Upgradeware. On other 440BX based motherboards, this works perfectly. Two computers I have upgraded are a QDI BrillianX 1 based box and the Compaq 5670. The lates BIOS for the 6120 does not support Coppermine or Tualatin processors. With the 6120, I get a successful boot too, but the effective speed is 7 MHz as compared to expected 1.3GHz (measured with lmbench). I have made a small kernel module testing the level 2 cache activation code, without any improvements. Also mtrr seems to be set up correctly. Now I would like to execute a full linuxbios image after boot to linux, in order to avoid the problem of re-flashing the BIOS. Is this possible? The Upgradeware support pages mentions that the IO chips have to be of correct type for a similar single CPU board, the MSI-6119 to uork with the SLOT-T adapter. What function does the IO chip have, and how can in be tested? Thanks, Svante

5 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot