LinuxBIOS + FreeBSD = true?

2002-10-08 Thread Christer Weinigel

Hi,

a quick question, is LinuxBIOS able to boot any of the BSD-flavours?
I'm especially interested in FreeBSD.

  /Christer

-- 
Just how much can I get away with and still go to heaven?

Freelance consultant specializing in device driver programming for Linux 
Christer Weinigel [EMAIL PROTECTED]  http://www.weinigel.se
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



Ram problem

2002-10-08 Thread steven james

Greetings,

I'm trying to get ram working on an e7500 MCH.
It seems to be actually initting, but when I run ramtest it, I
consistantly see a single bit toggled when reading back such as:

00024ab4:00024a94   
00024abc:00024a9c   
00024ad4:00024af4   
00024adc:00024afc   
00024af4:00024ad4   
00024afc:00024adc   
00024b14:00024b34   
00024b1c:00024b3c   
00024b34:00024b14   
00024b3c:00024b1c   
00024b54:00024b74   
00024b5c:00024b7c   
00024b74:00024b54   
00024b7c:00024b5c   
00024b94:00024bb4   
00024b9c:00024bbc   
00024bb4:00024b94   
00024bbc:00024b9c   
00024bd4:00024bf4   
00024bdc:00024bfc   

Other times, I see that the second read (in order to display the bad
value) actually reads successfully such as 000127a8:000127a8

Does anyone have any ideas what might cause that?

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
---




___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



getting started

2002-10-08 Thread Matt Walsh

All,

I would like to get my feet wet and build a cheap 3 node cluster to play
with linux bios, beowulf, etc.

Soo, if you were starting from scratch and wanted the motherboard that... 

- is cheap
- has good linux bios documentation
- has a good success rate

...which would you choose?

Thanks in advance, --matt

__
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos  More
http://faith.yahoo.com
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



RE: Walmart PC from MicroTel

2002-10-08 Thread Steve M. Gehlbach

 Was the question ever solved as to what chipset is used in the $199 model
 from walmart.com?

It is a Giga-byte mobo, the GA-6VEML:
http://tw.giga-byte.com/products/products.htm.  They list it as the VIA
VT8602 (PLE133T) and VIA VT82C686B chipsets.

-Steve

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



Re: [ARMboot-users] ARMboot vs BLOB

2002-10-08 Thread Bari Ari

Wolfgang Denk wrote:

In message [EMAIL PROTECTED] you wrote:
  

We're looking at trying to merge ARMboot or BLOB into the LinuxBIOS tree 
to give LinuxBIOS
http://www.acl.lanl.gov/linuxbios/ a common code base to boot ARM.



You may consider PPCBoot (or Das U-Boot = the Universal  Booter  as
the next major release will be renamed), too.

PPCboot is where ARMBoot descended from, and where it has been merged
back  (more  or  less  completely).  Ports  for  other  architectures
(including  ColdFire, XScale, and even x86) are in the works or being
discussed.
  

LinuxBIOS has mainly evolved for x86 and Alpha for large clustering 
applications and has built up good a user and developer base. It's also 
gaining popularity for x86 embedded applications. LinuxBIOS also 
includes support for Etherboot. LinuxBIOS currently boots x86 to Linux 
and Plan9. It's also being used to build a new 10TeraFLOP cluster at 
LANL. http://www.lanl.gov/worldview/news/releases/archive/02-106.shtml

Bari



___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



LinuxBIOS in 512KB flash

2002-10-08 Thread Hieu T. Tran

We're working to port LinuxBIOS to a via 133 platform
with a 512KB boot flash.  We believe that the flash is
wired such that on reset, 0x0 is mapped to 0x7FFF0
on the flash, which is slightly below 512KB on the flash.

We have been trying various config file settings
(ROMTOP, ROMSIZE, PAYLOAD_SIZE) to position ROMTOP and 
reset_vector accordingly without much success.  Simply
getting a larger flash wont help since the board will
only recognize the first 512KB.  Has anyone solved this
problem?  

-- HT
[EMAIL PROTECTED]
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



Re: getting started

2002-10-08 Thread Ronald G Minnich

I strongly recommend you just buy one pre-installed with linuxbios to
start. See cwlinux.com

ron

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



Re: LinuxBIOS + FreeBSD = true?

2002-10-08 Thread Eric W Biederman

Christer Weinigel [EMAIL PROTECTED] writes:

 Hi,
 
 a quick question, is LinuxBIOS able to boot any of the BSD-flavours?
 I'm especially interested in FreeBSD.

LinuxBIOS will load etherboot.
etherboot has support for FreeBSD.

But I believe the FreeBSD kernel uses vm86 mode and makes x86 BIOS calls
which LinuxBIOS does not implement.  It should just be a matter of modifying
the BSDs to not make x86 BIOS calls and instead read the LinuxBIOS table.

There may be a few integration issues but it should not be too hard to get
going.

Eric
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



Re: Ram problem

2002-10-08 Thread Eric W Biederman

steven james [EMAIL PROTECTED] writes:

 Greetings,
 
 I'm trying to get ram working on an e7500 MCH.
 It seems to be actually initting, but when I run ramtest it, I
 consistantly see a single bit toggled when reading back such as:

 Other times, I see that the second read (in order to display the bad
 value) actually reads successfully such as 000127a8:000127a8

Hmm.  it sounds very much like you are missing something.
When I finally finally got the ram intialization sequence working the
ram was rock solid.  

Is this known good ram?

 Does anyone have any ideas what might cause that?

There are too many variables for me to have a good guess.  I am just
about to sync my tree with the sourceforge tree and you can compare
notes.

Eric
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



Re: LinuxBIOS + FreeBSD = true?

2002-10-08 Thread Ronald G Minnich

On 8 Oct 2002, Eric W Biederman wrote:

 But I believe the FreeBSD kernel uses vm86 mode and makes x86 BIOS calls
 which LinuxBIOS does not implement.  It should just be a matter of modifying
 the BSDs to not make x86 BIOS calls and instead read the LinuxBIOS table.

yup. That's the state of play. I looked at this 2 years ago and talked to
some freebsd guys but did not get back any hints of interest. A shame too.
I used to always run freebsd clusters ...

ron

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



RE: LinuxBIOS in 512KB flash

2002-10-08 Thread Hieu T. Tran

Ron and Eric,

Thank you for the response.

The problem that we're having is that the generated romimage
positions reset_vector / ROMTOP at 0x0, resulting in an
image size of ~ 1MB.  Put another way, reset_vector is at offset
1MB on the flash device.  At boot, the system fetches the 
address at 0x0, and executes the code there.  As this 
address is truncated to 0x7FFF0 on our platform, or offset 512KB 
of flash, which is more or less random junk rather than the 
intended reset_vector.

To work around this problem, we're trying various methods to 
force reset_vector / ROMTOP to 0x7FFF0.  It appears that there
are several ways to do this, ranging from adorning the build
config file with various ROMTOP, ROMSIZE, and PAYLOAD_SIZE settings,
to providing a customized ldscript.ld file for the mainboard.  

What I'd like to know is if there is a simple way to accomplish this.
Also, I would be much oblidged for pointer to any document, if 
exists, that prescribes how to construct Config file for a given 
platform.  I suspect other developers would enjoy this as well.

-- HT


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Eric W Biederman
Sent: Tuesday, October 08, 2002 5:41 PM
To: Hieu T. Tran
Cc: [EMAIL PROTECTED]
Subject: Re: LinuxBIOS in 512KB flash


Hieu T. Tran [EMAIL PROTECTED] writes:

 We're working to port LinuxBIOS to a via 133 platform
 with a 512KB boot flash.  We believe that the flash is
 wired such that on reset, 0x0 is mapped to 0x7FFF0
 on the flash, which is slightly below 512KB on the flash.

That sounds correct.
Though I would normally use the mapping at: 0xFFF0 
and not even mess with the legacy stuff.

 We have been trying various config file settings
 (ROMTOP, ROMSIZE, PAYLOAD_SIZE) to position ROMTOP and 
 reset_vector accordingly without much success.  Simply
 getting a larger flash wont help since the board will
 only recognize the first 512KB.  Has anyone solved this
 problem?  

What exact problem are you having?  When you build romimage
it always places the entry point at the end of the rom.

Eric
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



Re: LinuxBIOS in 512KB flash

2002-10-08 Thread Eric W. Biederman

Hieu T. Tran [EMAIL PROTECTED] writes:

 Ron and Eric,
 
 Thank you for the response.
 
 The problem that we're having is that the generated romimage
 positions reset_vector / ROMTOP at 0x0, resulting in an
 image size of ~ 1MB.  Put another way, reset_vector is at offset
 1MB on the flash device.  At boot, the system fetches the 
 address at 0x0, and executes the code there.  As this 
 address is truncated to 0x7FFF0 on our platform, or offset 512KB 
 of flash, which is more or less random junk rather than the 
 intended reset_vector.
 
 To work around this problem, we're trying various methods to 
 force reset_vector / ROMTOP to 0x7FFF0.  It appears that there
 are several ways to do this, ranging from adorning the build
 config file with various ROMTOP, ROMSIZE, and PAYLOAD_SIZE settings,
 to providing a customized ldscript.ld file for the mainboard.  
 
 What I'd like to know is if there is a simple way to accomplish this.
 Also, I would be much oblidged for pointer to any document, if 
 exists, that prescribes how to construct Config file for a given 
 platform.  I suspect other developers would enjoy this as well.

For the linuxbios part of the rom:
PAYLOAD_SIZE+ROM_IMAGE_SIZE == bytes in romimage 
PAYLOAD_SIZE is the amount of space reserved for your bootloader.
_ROMBASE is the start address (of the ROM)
ROM_IMAGE_SIZE is far long you go after that, often 64K.

So something like:
option PAYLOAD_SIZE=458752
option ROM_IMAGE_SIZE=65536
option _ROMBASE=0xf 

Should achieve what you are trying to do...

Eric
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios