coreboot

coreboot@coreboot.org

12 participants
39780 discussions

Newbie install question
by Jeffrey Knight 16 Jan '03

16 Jan '03

Hi all: I'm looking for a linux version/distribution that will boot as fast as possible. I have a PII intel motherboard, and am interested in trying to get linuxBIOS on it (the Phoenix BIOS alone take a good 15+ seconds). My questions are: do I need any special *hardware* to install linuxBIOS? In reading the FAQ's on the website, I'm a bit confused by "burning a flash ROM" using a flash burner. and is there any documentation on installing linuxBIOS other than the FAQ's? Although I'm very familiar with linux, a lot of this is new to me. Thanks! Jeff _________________________________________________________________ Help STOP SPAM: Try the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

1 0

quick start
by Paweł Wojtal 16 Jan '03

16 Jan '03

Hi! Is there somewhere a site, I can find an idiot-image(s) of linuxbios ready to flash into rom? Any kind of support: ide0 boot, or dhcp or others... any board (I will find any board on second-hand market). I need to temporary decrease my frustration with compiling from sources and start to play with anything ;-))). Excuse my English, please. Thanks. femur

2 1

subscription
by erto＠katamail.com 16 Jan '03

16 Jan '03

Hi! Please UNSUBSCRIBE my address. Best Regards

1 0

Latest source code of LinuxBIOS.
by sivakumar 15 Jan '03

15 Jan '03

Hi, I have downloaded the source code tar from the following link, http://sourceforge.net/project/showfiles.php?group_id=3206&release_id=42674 But it seems to br one year old. I am not able to connect to CVS respository. Where can I get the latest tar ball of the Linuxbios source code. Thanks, Siva -- sivakumar <sivakumar.subramani(a)wipro.com> wipro

2 1

RE: Boot from etherboot - blocked by INT 10
by Lawrence LL. Dai 15 Jan '03

15 Jan '03

Hi, All I have made my image download the kernel from the server and boot up successfully. But an error comes out at the end of the serial output: ... ... Kernel command line: bz.elf -retaddr 0X000940A4 ... ... VFS: Cannot open root device "" or 00:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 00:00 Compare with the normal Linux output: ... ... Kernel command line: auto BOOT_IMAGE=linux ro root=301 BOOT_FILE=/boot/vmlinuz-2 .4.18-3 console=tty0 console=ttyS0,9600n8 ... ... So I have tried the followings: 1. Add the option (--command-line= "root= ..." or --append="root= ...") when I mkelfimage. 2. Try the latest version 2.0 of mkelfimage 3. Add command line ="root = ..." in Linux bios CONFIG file But the error does exit. How can I fix it? Thanks, Lawrence -----Original Message----- From: Eric W. Biederman [mailto:ebiederman@lnxi.com] Sent: 2003?1?10? 15:38 To: LinuxBIOS Cc: Lawrence LL. Dai Subject: Re: Boot from etherboot - blocked by INT 10 "Lawrence LL. Dai" <lawrence(a)tyanchina.com> writes: > Hi, Eric > > I suppose that mknbi and mkelf would also cause this problem.Because > they both tag a kernel, but the kernel must be the one like vmlinuz and vmlinux > needs BIOS functions such as INT 10. (I know vmlinux does not need INT X, but > vmlinux can not be tagged by mknbi and mkelf. Or I have missed something else?) The difference is mknbi/mkelf that come standard with etherboot when the process the linux kernel start the kernel in 16bit mode and run it's BIOS code, mkelfImage simulates the effect of the 16bit BIOS code by reading LinuxBIOS tables or making the needed BIOS calls itself, and then it enters Linux at it's unofficial 32bit entry point. mkelfImage can take either a bzImage or a vmlinux. Eric

1 0

Wow! A hole in linuxbios PCI mastery setup?
by Kevin Hester 14 Jan '03

14 Jan '03

Hi all, I think I've noticed a general linux-BIOS problem: Some PCI devices are not being enabled for bus mastery! Let me more clearly explain the context: 1) According to my handy PCI book: All bus master capable PCI devices must implement bit 2 of the command register. 2) Most devices that implement this bit power up default to 1. This is good, because linuxbios has not been setting this bit to 1. 3) A user reported a problem with a 802.11b card, and upon investigation I discovered the chip used on this card does not default to a 1 for bus master enable. (See attached lspci output) After some testing, I realized that the same card on a non LinuxBIOS based machine works correctly - i.e. by the time the kernel is up I see that this bus master enable bit is 1. I know that the Award BIOS on this second machine must have set this bus master enable bit - because the kernel and drivers are identical. I verified this by dumping the appropriate config registers early on in kernel start-up. My theory is that the Award BIOS is doing something that we are not: During the IO/Mem space assignment process it is setting the bus master bit for most devices. By "most devices" I mean any device that is not behind a bridge that inhibits bus mastery. My PCI Sys Arch book (by Shanley and Anderson) says that some crummy bridges may not support bus mastery (i.e. they have a bit 2 of the command register that always reads as zero). If a device is behind a bridge that does not support mastery, it must have its mastery bit cleared. Does anyone have a copy of the $$$ PCI architecture spec so they can check this? My PCI System Architecture book is vague on the topic. My proposed fix: * Add pci_enable_bus_masters() that does the following: * Calls pci_enable_bus_master(0) to enable devices directly connected to the host bridge * Add pci_enable_bus_master(devfn) that does the following: * Try to enable bus mastery for this device. * If the device is a bridge: * If the write of master enable fails, then write zero to all "bus master enable" bits for devices behind that bridge (including all subordinate buses) * If the write of master enable succeeds, then call pci_enable_bus_master for all devices on the secondary bus behind this bridge. (i.e. not for all subordinate busses) I've added these functions and called them after the standard linuxbios PCI setup. The problem card now works as well as it did with Award BIOS. What to ya'll think? I'm particularly interested in quotes from the PCI architecture spec. Kevin --- On a linux BIOS machine: 00:14.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev 01) Subsystem: D-Link System Inc: Unknown device 3501 Flags: medium devsel, IRQ 5 Memory at feb00000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 00: 60 12 73 38 02 00 90 02 01 00 80 02 08 40 00 00 10: 08 00 b0 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 11 01 35 30: 00 00 00 00 dc 00 00 00 00 00 00 00 05 01 00 00 40: 80 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 7e e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 On a non linux BIOS machine: 00:0a.0 Network controller: Harris Semiconductor: Unknown device 3873 (rev 01) Subsystem: D-Link System Inc: Unknown device 3501 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at ee000000 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 00: 60 12 73 38 07 00 90 02 01 00 80 02 08 20 00 00 10: 08 00 00 ee 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 11 01 35 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 00 00 40: 80 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 7e e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

4 5

[ANNOUNCE] mkelfImage 2.0
by ebiederman＠lnxi.com 14 Jan '03

14 Jan '03

After a long and tedious grind I am pleased to announce version 2.0 of mkelfImage. New features. - One single binary - Itanium support - All of the code is in C. - New and exciting easter eggs (err bugs can you find them before I do?...) Available at: ftp://ftp.lnxi.com/pub/src/mkelfImage/mkelfImage-2.0.tar.gz rpms can be built with rpm -ta mkelfImage-2.0.tar.gz alien will make perfectly serviceable debs from those... The decision to go with pure C is that it is both relatively portable, and it reduces maintenance when I add a feature. I tried perl and it handles the interesting code only with the utmost protest. Adding checksums and other interesting pieces is much easier if it only needs to be both coded in one language, and usually the C implementation is much easier than the perl. Plus C is fast :) Have fun, Eric

2 2

help!
by xu xuning 14 Jan '03

14 Jan '03

Hi, I have success to boot from my doc by using the pre-made images from http://www.cwlinux.com/download/,but now i want to know how to boot from IDE drive? BTW,how to use winfast6300-etherboot.rom and winfast6300-ide.rom? _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com

1 0

[commit] TigerMPX (760MPX)
by steven james 13 Jan '03

13 Jan '03

Greetings, Primary and fallback images are working with this commit. It's looking fairly solid. G'day, sjames -- -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office 404.577.7747 fax 404.577.7743 -----------------------------------------------------------------------

1 0

Option Parameters for Linuxbios.
by sivakumar 11 Jan '03

11 Jan '03

Hi all, Can any one help me in understanding the following parameter used for the configuration of the LinuxBIOS. biosbase 0xffff0000 rambase 0x00000800 option XIP_ROM_BASE=0xffff0000 option XIP_ROM_SIZE=0x10000 option STACK_SIZE=0x2000 option ZKERNEL_START=0xfff40000 option ZKERNEL_MASK=0x3ed Also I have one more query, When executing the linuxbios, it is executing the instrcution twice (i.e., I am getting output twice). I have attached the serial console output below. How to get rid of this? LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4 (four)starting... Ram1 Ram2 Ram3 Ram Enable 1 Ram Enable 2 Ram Enable 3 Ram Enable 4 000001d0Ram Enable 5 Ram Enable 6 Content of CAPPTR 04Content of BCC 06Ram4 Ram5 Ram6 Copying LinuxBIOS to ram. 00000800ffff0f80 ecx value during image copy 00000000Jumping to LinuxBIOS. Calling hardwaremain ... LinuxBIOS-1.0.0 Sat Jan 11 18:18:32 IST 2003 Revision - 4 (four)starting... Ram1 Ram2 Ram3 Ram Enable 1 Ram Enable 2 Ram Enable 3 Ram Enable 4 000001d0Ram Enable 5 Ram Enable 6 Content of CAPPTR 04Content of BCC 06Ram4 Ram5 Ram6 Copying LinuxBIOS to ram. 00000800ffff0f80 ecx value during image copy 00000000Jumping to LinuxBIOS. Calling hardwaremain ... Thanks, Siva -- sivakumar <sivakumar.subramani(a)wipro.com> wipro

4 6

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