coreboot October 2002

coreboot@coreboot.org

77 participants
164 discussions

Start a nNew thread

I need some help about BOOT VIA IDE!
by 王海明 15 Oct '02

15 Oct '02

1 0

I need some help about BOOT VIA IDE!
by 王海明 15 Oct '02

15 Oct '02

1 0

I need some help about BOOT VIA IDE!
by 王海明 15 Oct '02

15 Oct '02

1 0

I need some help about BOOT VIA IDE!
by 王海明 15 Oct '02

15 Oct '02

1 0

I need some help about BOOT VIA IDE!
by 王海明 15 Oct '02

15 Oct '02

1 0

MTRR on P4
by hcyun＠etri.re.kr 15 Oct '02

15 Oct '02

Hello. I have problems in setting MTRR registers on our SIS645 based custom P4 mainboard. More precisely my system hangs on set_fixed_mtrrs() function on mtrr.c Because I'm using recently updated cvs tree, that function already use disable/enable cache but it doen't work for me. I investigated your configuration files of supermicro p4dxx boards because they are the only P4 boards in the cvs tree. And I found your comment about mtrr. You said that 'Don't do generic MTRR setup, instead use values from the fixed_mtrr_values array' So I saw the code and I found that fixed_mtrr_values array is defined but never used anywhere. Can you tell me more about your comments and please suggest how can I pass this problem if possible. Best regards, Heechul

1 0

(no subject)
by 王海明 15 Oct '02

15 Oct '02

HI ALL: I want to boot the kernel from harddisk(ide) using Linuxbios. I found a rominage in www.cwlinux.com which can boot successfully via ide hardisk . From the output message, I found they use etherboot-5.0.6.But I don't know how they build the romimage.If some one can give me some advice ,i will appreciate your help! 　　　　　　　　　　致礼！　　　　　　　　　　　　　　王海明　　　　　　　　　　　　　　whm_buaa(a)sina.com 　　　　　　　　　　　　　　　　　2002-10-15

1 0

strange error on sis900 ethernet
by zhu shi song 15 Oct '02

15 Oct '02

I met one strange error on sis900 ethernet driver. I'm using cvs freebios on 6 Oct, 2002 , kernel 2.4.17, mainboard is winfast6300. After booting using linuxbios stored in DOC, I boot my host linux system using normal bios. the host linux is the same system as in DOC. I test pings, the result is ( after linuxbios booting): ping -s 2592 192.12.11.1 ( remote ip addr ) 0% lost ping -s 2593 192.12.11.1 ( remote ip addr ) no response, 100% lost I can't make the mainboard work correctly until I have booted windows98. Then I use my host linux system to boot, the thing is ok. (after windows98 booting ) ping -s 2592 192.12.11.1 0% lost ping -s 2593 192.12.11.1 0% lost What's the problem, maybe something wrong with pci ,or sis900 init code. thanks zhu __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com

2 3

Re: the plan for stable
by ebiederman＠lnxi.com 14 Oct '02

14 Oct '02

Ronald G Minnich <rminnich(a)lanl.gov> writes: > A short sketch. > > What I want to do, but have not had time to do. For each mainboard, we > designate an owner. The owner is responsible for letting us know that > their mainboard works. Mainboards are in one of 3 states: (stable, > unstable, unsupported) > > Mainboards start out in the unstable or unsupported state. > > We pick a date (1/1/03?) and say we want all owners of all mainboards to > tell us that their mainboard is stable. We freeze the tree one month > ahead of that time and the only changes that go in are for stabilization. 1 January 2003 is a bad date for me as I have plans to be far away from computers over christmas. > If nobody steps up for a board, it goes to unsupported state. Boards with > owners start out in the unstable state. The challenge is for a lot of boards we do not get active feedback after a port has been completed. So for any ongoing work we need to very very careful not to make changes to the core that break ports. I am probably the worst offender, except for the various bits of debug code that come and go but still. > Mainboards move to the stable state when the owner confirms stability. > When patches are made for a problem, ALL stable mainboards revert to > unstable. We iterate until we get it solid, then freeze it. For the first round this looks o.k, it really depends on what kind of feedback we have. > This information is maintained by a file in each mainboard directory > called STATUS, which consists of name/value paris. One file in the root directory called STATUS should do it.. > Will this work? Sounds like a good rough draft. The very important thing about the stable series is that nothing happens to the core code that could possibly break a motherboard port. That way within a stable series we can get more but not fewer boards working. Then whenever a new port gets working we can do another release. Of course if the come in fast enough we can delay... > thanks (I'm off email for a bit -- at a workshop) Speaking of which we probably should put together some kind of conference/workshop for LinuxBIOS. So the developers can get together and talk face to face. Eric

3 2

strange error on sis900 ethernet
by zhu shi song 14 Oct '02

14 Oct '02

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
17
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 October 2002