coreboot May 2004

coreboot@coreboot.org

35 participants
149 discussions

Lbcc tool
by Mathieu Deschamps 24 May '04

24 May '04

Hello, I use a home made tool since the beginnig and during my test it goes more and more powerful and usefull. through making and using it I've understood the build process, may it be the same for you. There is nothing really new in it, it centralize and does everything in one command (prior settings needed of course) ... finally i'll name it lbcc. Lbcc a script that does build your target machine (ex : VIA config) and build your rom with log and so on. Heavily refactored and strenghen to be more portable and robust. Form it you can control the whole process of making a LinuxBIOS booting a payload. It does : - config LinuxBios - Log ALL activity - Calculate build time - Display rom bindings - Choose payload - Configure payload - Make payload - Make the rom - Flash the rom - Make coffee .. err .. no still not :) To come : - Itegrate videobios some advices : It needs to be copied into the freebios2/target and it need lb_flash, think of making symbolic link to it and after to the lbcc generated logs like buildtaget.log and make.log, etc.. It'll *NEED* some of *YOUR* path fix into its head. If it bugs, think of this, anyway, find in script bug's exact place. Since this logs everything think of having a look to theses and often you'll get your answer (that's the aim of this facility :) If you are lost into it or troubled with a bug I can reply/explain to detailed requested. disclaim: Actually, this is a comfort and maybe it *couldn't be usefull to everyone*, ask yourself if some necessary adapt time is worth this ease. A last number : It is 400 lines of bash script code any comments, ideas, etc.. reply onto this thread. Good lxbiosing. mathieu.

2 1

Re: Hear.sh
by Mathieu Deschamps 24 May '04

24 May '04

Typically this is a ' or a " that's not close where it should, maybe have i missed copy/paste the script. Anyhow here are a new version. Let me know if it goes wrong. Both theses script in the same directory. Hear script-------------- #!/bin/sh # # Hear script listen & log onto ttyS0 (serial port a.k.a COM1) # # VERSION="24/05/04|09:32:49 MD" SPEED="115200" i="Bienvenu(e) dans Hear! v. $VERSION j'ecoute sur ttyS0 ..." ter=`tty` if [ "x$1" = "x" ]; then echo "Usage $0 log_to_file" exit 0 else LOG="$1" fi echo $i echo "Logging in $LOG" stty ispeed $SPEED stty | tee -a "$LOG" echo "****************************************************" >>"$LOG" echo " Hear! Boot Log started on `date +%d/%m/%y\|%T` " >> "$LOG" echo " tty in use : $ter from ttyS0 " >>"$LOG" echo "****************************************************" >>"$LOG" /usr/bin/time -pao "$LOG" -- cat -sbA </dev/ttyS0 | tee -a "$LOG" ./digest.sh "$LOG" -s echo "----------------------------------------------" >> "$LOG" echo -e "\n" echo "Please add a comment to this boot log .." sleep 3 vi tmp echo -e "Comments :\n" >> "$LOG" cat tmp >> "$LOG" rm -f tmp echo "done." Digest script-------------- #!/bin/bash # # Script to digest hard-human readable hear! logs # Mathieu Deschamps for mangrove-systems # VERSION="11/05/04|09:40:28 MD" SUPP=0 DAT="`date +%d\-%m\-%y\ %T`" if [ "x$1" = "x" ]; then echo "usage: $0 hear!_log_file [--suppress-log,-s] " echo "v. $VERSION" exit 0 else FIL="$1" fi [ "x$2" = "x-s" ] || [ "x$2" = "x--suppress-log" ] && SUPP=1 if [ -f "$FIL.adv" ]; then mv "$FIL.adv" "$FIL.adv.$DAT" fi cat $FIL | while read line; do [ "x$line" != "x$" ] && echo "$line" done > "$FIL.adv" mv -f $FIL $FIL.digested mv -f $FIL.adv $FIL ( [ $? -eq 0 ]; echo "$FIL digested, rename old as $FIL.digested" ) || echo "Digestion gets harden ...blurp (error) " [ $SUPP -eq 1 ] && rm -f $FIL.digested 2>&1 >/dev/null Le ven 21/05/2004 à 17:28, Thomas Spear a écrit : > Mathieu - > > I can't run your hear.sh script. I get "Line 25: unexpected end of file" > when I try. What do I need to do to fix it? Thanks. > > _________________________________________________________________ > FREE pop-up blocking with the new MSN Toolbar get it now! > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ > >

1 0

答复: USB boot
by YhLu 21 May '04

21 May '04

Steven, I have moved ED/TD processing from 2.4.22 to the usb support of FILO/Etherboot. the ED and TD have been linked already, but the HC didn't precess the list??? Please let me know if you want my latest tar ball. Regards YH

1 0

EPIA V2 VGA build succeeded, getting inspired from tyan ?
by Mathieu Deschamps 21 May '04

21 May '04

Hello, I've been making some port/adapt for epiam vgabios V2 for a few days now ... and it *seems* my build have succeeded :). Still have some minor warning though... I've seen in the tyan source (in the mainboard.c) that the DO VGA was *called* here (setup_realmode_idt() and do_vgabios()). Am I on the good way doing same with via/epia/mainboard.c ? In other words, is there another c file called first ? If not so it's obvious it's in it to call the vga init, isn't ? Thanks for your help, advices, and your good work ...of course. :) mathieu

2 1

256MB or 512MB on EPIA-M
by M. Renee Hopkins 20 May '04

20 May '04

Does anyone have ideas about modifications to support higher DDR RAM than 128MB? I've read some attempts in the list, but they seem to be in error as far as I can tell. Many thanks... MR _________________________________________________________________ Get 200+ ad-free, high-fidelity stations and LIVE Major League Baseball Gameday Audio! http://radio.msn.click-url.com/go/onm00200491ave/direct/01/

2 1

Re: Making payloads
by Hendricks David W. 20 May '04

20 May '04

Oops, I forgot to mention Stefan's patch for FILO to make IDE work on the S2885. I think this is the one: http://www.clustermatic.org/pipermail/linuxbios/2003-October/005753.html On Thu, 13 May 2004, Jay Miller wrote: > The reason why my S2885 image wasn't working is because my system only > has 1 CPU populated. A little tweaking to remove the second processor > and I can get FILO to come up. Unfortunately FILO does not detect the > IDE disk. > > I noticed in the payloads section of Config.lb there are some multi-part > payloads, like tg3--ide_disk.zelf, and tg3--filo.zelf. > > How do I create the multi-part payloads? Ideally I would be interested > in a FILO that recognizes IDE. Alternatively I am also pursuing a tg3 > payload that will load my kernel over the network. > > Thanks, > > Jay Miller > Actuality Systems, Inc. > jmiller(a)acutality-systems.com > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios >

3 4

Re: Getting Started with freebios2!
by backblue 18 May '04

18 May '04

I like to develop, linuxbios to my motherboards, but none of them are suported, i will show you some lspci of them: #1: 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5597 [SiS5582] (rev 02) 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 01) 00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) 00:0a.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06) 00:13.0 VGA compatible controller: Silicon Integrated Systems [SiS] 5597/5598/6326 VGA (rev 65) #2: 00:00.0 Host bridge: Intel Corp. 430VX - 82437VX TVX [Triton VX] (rev 02) 00:07.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01) 00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] 00:13.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64) #3: 00:00.0 Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 01) 00:07.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02) 00:07.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02) 00:0e.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] 00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) #4: 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06) 00:04.2 USB Controller: VIA Technologies, Inc. USB (rev 16) 00:04.3 USB Controller: VIA Technologies, Inc. USB (rev 16) 00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:0d.0 SCSI storage controller: Initio Corporation 360P (rev 02) 01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 02) I have some more machines, but i would like to know if any of these ones it's suported? Tks On Tue, 18 May 2004 08:20:49 -0400 "Jay Miller" <jmiller(a)actuality-systems.com> wrote: > Disclaimer: I too am a N00B and these are my observations thus far. > They may not be 100% correct, but these things have worked for me. I > hope that they'll help other N00Bz get started. > > WHAT IS FREEBIOS2? > > Well I stumbled upon freebios2 when I couldn't find support in the > freebios tree for my Tyan s2885. Then I noticed under the CVSWeb > browser for the project the freebios2 directory. > > Apparently, this is what will be LinuxBIOS V2. They've done away with > kernel patches, so you don't need to worry about patching the kernel > like in V1. Instead there is an intermediary payload that can be > Etherboot, FILO, or some other loader to get your Linux kernel into > memory. > > WHY CAN'T I GET THE SOURCES FROM SOURCEFORGE (ANYMORE)? > > If you're like me, all of a sudden CVS access stopped working. Well, > they changed the BIND implementation, so the documentation is out of > date. You need to use, "cvs > -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/freebios login". > There is still no password for anonymous login. > > WHERE DO I START? > > Build the documentation under freebios2/documentation. It will give you > a solid overview of how the project works, including how to download the > source you just downloaded. ;-) > > Freebios2 supports a number of newer boards. Tyan are particularly > well-supported and the EPIA boards are actively being worked on. Look > under, "freebios2/targets..." for the collection. > > HOW DO I BUILD FREEBIOS2? > > Once you've selected a vendor and mainboard you should execute, > "./buildtarget <vendor>/<board>". This will generate all sources > specific to your mainboard. To make a rom image, start your make in the > freebios2/targets/<vendor>/<board>/<board> directory. If all goes > smoothly you should get a linuxbios.rom image. > > HOW DO I FLASH A ROM? > > There are a number of methods and I'm not versed enough to cover them > all. But I have successfully used the BIOS flash utility from AMI, and > I currently use a professional Data I/O burner. I spent a lot of time > trying to figure out the proper format to use on my burner. There is no > format; it's just a straight binary image, so use binary mode (on the > Data I/O it's "absolute binary (16)"). > > There is also a flash-n-burn utility in the source tree. Perhaps > someone on the list can add the specifics of how to get that going on > this thread. > > > HOW DO I CHANGE CONFIGURATION OF MY IMAGE? > > First take a look at freebios2/targets/<vendor>/<board>/Config.lb. This > is the main configuration file for your ROM image. This is where you > specify what payload to use, and most of the settings that anyone would > care about. Make sure to do a "./buildtarget <vendor>/<board>" whenever > you modify this file. > > However, in my case I was running into issues running my dual-processor > board with only one processor. As it turns out there is another > Config.lb located in freebios2/src/mainboard/<vendor>/<board>. This > file controls the contents of some of the generated sources for your > board. To date, this is the only way I was able to prevent my ROM image > from trying to initialize a CPU that wasn't there. > > WHY DON'T I SEE ANYTHING HAPPENING? > > In most cases the VGA support just isn't there yet. So go find yourself > a null modem cable and hook up your console at 15200-8-N-1, and sit back > and watch the fireworks! > > > WHAT ABOUT PAYLOADS? > > I'm currently exploring this area. The first payload I used > successfully was FILO. No you don't make pastry with it. It is a > bootloader that acts much like LILO. You can get the source here: > http://felixx.tsn.or.jp/~ts1/filo. > > If you have an IDE disk with a Linux kernel on it, this is the way to > get started. > > If you're diskless then you may want to try Etherboot: > http://etherboot.sourceforge.net. This payload gives you the ability to > load over the network, but requires you to configure a DHCP server and > TFTP server at a minimum. > > Like LinuxBIOS, Etherboot expects an ELF formatted image, so if you're > loading a kernel across the network you need to run it through > mkelfImage. As of now the correct version to use is 2.5. You can get > the latest sources here: > ftp://ftp.lnxi.com/pub/mkelfImage/mkelfImage-2.5.tar.gz. > > > WHAT ABOUT ZELF? > > This is my latest N00B stumbling block, and unfortunately I haven't > found an answer. I know that it's a compressed elf format, but I can't > figure out what I need to do to get elfboot (part of LinuxBIOS) to load > payloads with the ZELF extension. So for now I would recommend N00Bz > stick with ELF format, until we get a definitive answer. > > > Hope this is helpful, good luck! > > > Jay Miller > Actuality Systems, Inc. > jmiller(a)acutality-systems.com > > > > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Content violation (fwd)
by ron minnich 18 May '04

18 May '04

even better. I get this bounce all the time. And no, the whitelist registration did not work at all :-) ron ---------- Forwarded message ---------- Date: Tue, 18 May 2004 23:00:23 +02120 (MEST) From: contentfilter(a)becker.de To: linuxbios-admin(a)clustermatic.org Subject: RE: Content violation (fwd) Absender/Sender: linuxbios-admin(a)clustermatic.org Betreff/Subject: Content violation (fwd) Datum/Date: Tue, 18 May 2004 14:55:21 -0600 (MDT) Empfänger/Recipients: IBaab(a)becker.de Nachrichten-ID/Message ID: T69a6c0d26eac10df0fa3c [DEUTSCHER TEXT - SIEHE UNTEN] The message has not been delivered! It has been classified as unsolicited automatic mass advertising email (spam) by our content filtering systems. If this happened in error please send your mail again with the following keyword added somewhere to the message body: nospam231 If your emails frequently get misclassified as spam, please contact us at the address below and we will add you to our whitelist of known senders. This is an automatically generated email.Do not reply directly. For further inquiry please contact mailsweeper(a)harmanbecker.com ************************************************** Die Nachricht wurde nicht zugestellt! Sie wurde von unseren Content Filtern als unerwuenschte automatische Massenwerbemail (Spam) klassifiziert und gesperrt. Falls es sich hierbei um einen Irrtum handelt, senden Sie Ihre Nachricht bitte noch einmal, indem Sie an beliebiger Stelle im Nachrichtentext folgendes Schluesselwort hinzufuegen: nospam231 Falls Ihre Nachrichten haeufig faelschlicherweise als Spam klassifiziert werden, benachrichtigen Sie uns bitte unter nachfolgender Mailadresse. Wir werden Sie dann in unsere Liste bekannter Sender aufnehmen. Dies ist eine automatisch generierte EMail! Antworten Sie nicht direkt darauf. Bei Rueckfragen wenden Sie sich bitte an mailsweeper(a)harmanbecker.com

1 0

Content violation (fwd)
by ron minnich 18 May '04

18 May '04

Don't let your stupid virus scanner do this :-) if you can imagine ... the word free in the subject is lo longer allowed at some sites. ron ---------- Forwarded message ---------- Date: Tue, 18 May 2004 15:18:47 -0400 From: Symantec_AntiVirus_for_SMTP_Gateways(a)amcc.com To: linuxbios-admin(a)clustermatic.org Subject: Content violation Content violation found in email message. From: linuxbios-admin(a)clustermatic.org To: tdeclerck(a)3ware.com Subject: Re: Getting Started with freebios2! Matching Subject: *free*

1 0

Re: Getting Started with freebios2!
by Hendricks David W. 18 May '04

18 May '04

Excellent work! This should prove helpful to those new to the project get started. I'd like to elaborate on a few points you have made. On Tue, 18 May 2004, Jay Miller wrote: > > HOW DO I FLASH A ROM? > There is also a flash-n-burn utility in the source tree. Perhaps > someone on the list can add the specifics of how to get that going on > this thread. Flash-n-burn should work on many newer mainboards, particularly those supported by LinuxBIOS such as your Tyan S2885 with an AMD8111 southbridge. It is currently not capable of flashing in "parallel programming" mode like many older chipsets and flash parts require. It should work with many newer SST parts and with the PM that comes on your S2885. If you require support for another part, let us know and we'll try to add it in. On Tue, 18 May 2004, Jay Miller wrote: > HOW DO I CHANGE CONFIGURATION OF MY IMAGE? > > First take a look at freebios2/targets/<vendor>/<board>/Config.lb. This > is the main configuration file for your ROM image. This is where you > specify what payload to use, and most of the settings that anyone would > care about. Make sure to do a "./buildtarget <vendor>/<board>" whenever > you modify this file. Also, one must run "make" in the <vendor>/<board>/<board> directory. If all goes well, linuxbios.rom should appear and will be the appropriate size (A power of two, like 2^19 for a half meg part). The size can be set in the <vendor>/<board>/Config.lb file. On Tue, 18 May 2004, Jay Miller wrote: > > WHY DON'T I SEE ANYTHING HAPPENING? > > In most cases the VGA support just isn't there yet. So go find yourself > a null modem cable and hook up your console at 15200-8-N-1, and sit back > and watch the fireworks! We have limited support right now. If you cvs update, you should be able to boot LinuxBIOS, run the VGABIOS with the "testbios" utility, and get X up and running fully accelerated with an nVidia card (GeForce FX) on that S2885 of yours. Here's how you get your VGABIOS (This might have to be done with the factory AWARD BIOS): dd if=/dev/mem of=vgabios.bin skip=1536 count=128 Ollie Lo is making a lot of progress on support for add-in cards. Please check back in upcoming weeks for updates (Ollie is currently in Austin, Texas for a conference). For those wishing to use their integrated RageXL chips, which are common for many Tyan mainboards and others like the Arima HDAMA, YhLu has recently added support for those as well. Add this to your src/mainboard/<vendor>/<board>/Config.lb file: ## ATI Rage XL framebuffering graphics driver dir /drivers/ati/ragexl Then add these lines to your targets/<vendor>/<board>/Config.lb file: uses CONFIG_CONSOLE_BTEXT option CONFIG_CONSOLE_BTEXT=1 YhLu has a modified version of FILO available which should be used for this. I think it's here: http://www.clustermatic.org/pipermail/linuxbios/2004-April/007650.html And lastly, apply YhLu's kernel patch ( http://www.clustermatic.org/pipermail/linuxbios/2004-May/007734.html ) and enable framebuffering in your kernel. This should allow you to see LinuxBIOS, FILO, and your kernel coming up on screen. X should work, too. I'll get patches and stuff up on personal webspace at a later date. Good luck!

1 0

← Newer
1
2
3
4
5
6
7
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2004