Gin | 1 Nov 02:19 2004
Picon

PXE support

Hello,
It seems like linuxbios supports PXE. Can anyone tell me how it works if
you have experience with it? Thanks

Gin

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Yinghai Lu | 1 Nov 05:16 2004

RE: Merge/Cleanup status

> I'm not really a fan, I am still more productive with printf debugging.  

Yes, also post code to port 80 is useful before the console is setup.

Regards

YH

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Stefan Reinauer | 1 Nov 11:05 2004

Re: PXE support

* Gin <ginlin <at> nexcom.com.tw> [041101 02:19]:
> Hello,
> It seems like linuxbios supports PXE. Can anyone tell me how it works if
> you have experience with it? Thanks

etherboot supports PXE. If you use etherboot as LB payload it should
work. Never tried this though since I can't really recognize an
advantage over the usual dhcp/tftpboot scenario. It's unlikely that you
are able to use any driver like code on the network adapters without
16bit bios.

Stefan

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

tyson | 1 Nov 14:38 2004

Re: status information

Li-Ta Lo wrote:
> On Thu, 2004-10-28 at 16:58, Eric W. Biederman wrote:
> 
>>As for CF.  I guess I have only seen LANL doing that, and it
>>seems a little unsatisfactory.  There is no reason why beoboot
>>needs that much space for example.
>>
> 
> 
> I bet there are a lot of people using CF in the embedded world, they 
> can't use Etherboot to fetch the kernel from the net as you do. We 
> should not only think about HPC applications. People in embedded
> market are in different enviroment and have different cost structure
> than you.

I haven't been following many linuxbios threads but this one caught my eye.

Though we are still using a very old version of Linuxbios and thus not 
currently doing any development here :-( we do boot from a CF and the 
ability to do so is very important.

Ollie is right, embedded usage patterns are VERY different from HPC.

Cheers!
Ty

--

-- 
Tyson D Sawyer                     iRobot Corporation
Lead Systems Engineer              Government & Industrial Robotics
tsawyer <at> irobot.com                 Robots for the Real World
(Continue reading)

Dave Aubin | 1 Nov 14:47 2004

RE: Kernel for linuxbios

Two things strike me as odd.

1.  Your ," PCI: IRQ 0 for device 0000:02:00.1 doesn't match PIRQ mask -
try
pci=usepirqmaskPCI: 02:01.0 [1022/7462] disabled"
   Type of errors.  Looks like you pcirqp map is bad?  Are you making
your
Own mother board?  If so it is important that you get this and the mp
Table correct based on your wiring.  

2.  You did get to initramfs, good job, but it did fail to mount you
File system.  This could be anything.  Please send your init script
And Describe what are you trying to mount.  A USB stick, ide, what?

-----Original Message-----
From: Sagiv Yefet [mailto:sagivy <at> 3vium.com] 
Sent: Sunday, October 31, 2004 5:45 AM
To: Dave Aubin
Cc: linuxbios <at> clustermatic.org
Subject: RE: Kernel for linuxbios

I took your advise and try the 2.6.
I am using the initramfs_data.cpio.gz from the link you send me.

The mkelf command is:

./objdir/sbin/mkelfImage -t bzImage-i386
--kernel=/home/sagivy/bzImage-2.6. 	--command-line="rw
console=ttyS0,115200 root=/dev/ram0"
	--initrd=/home/sagivy/initramfs_data.cpio.gz 
(Continue reading)

Ronald G. Minnich | 1 Nov 17:59 2004

RE: FILO fixups


On Fri, 29 Oct 2004, YhLu wrote:

> You can get filo only under Etherboot.
> 
> make bin/filo.zelf

but you won't get my speed improvements, although we can see about putting 
those in too. 

we'll probably continue with filo-only here for now. 

thanks

ron
_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Ronald G. Minnich | 1 Nov 18:08 2004

Re: status information


On Fri, 29 Oct 2004, Eric W. Biederman wrote:

> As for size, the beoboot userland is one of the reasons why you are
> still using CF.  But that can be tuned.

No, beoboot really is not the reason at all! 

We had a cluster at SC '03 with linuxbios/linux/beoboot in the flash part,
NOT the cf. That booted over ethernet (faster than etherboot, which was
interesting). As soon as you put IB drivers or myrinet drivers or quadrics
drivers into the picture, you need the CF. That's just the way it is.
Those drivers and their support code push the kernel size over the edge.

Plus, on Pink, the 1024 node cluster, we have a fallback/normal linuxbios,
fallback/normal FILO in flash; the fallback/normal kernel and initrd are
in CF. There's no room at all to do this in a 1 MB flash part. 

Use of CF is not a beoboot/kexec issue at all.

ron

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Ronald G. Minnich | 1 Nov 18:16 2004

Re: status information


On Sat, 30 Oct 2004, Stefan Reinauer wrote:

> What was the original intention of the structure? It might be nice to
> know how many sockets there are and what CPUs are in those sockets.. 
> (ie some dmi kind of information)

it would have allowed for more debug information, but it appear that 
requests from a number of people to leave it in there were ignored.

ron
_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Adam Sulmicki | 1 Nov 19:19 2004
Picon

RE: LinuxBIOS debugging with an emulator

On Thu, 28 Oct 2004, Li-Ta Lo wrote:

> BTW, if you specify the -g option for gcc, you can use the -S option
> in objdump to see the source code with the disassebmly (-d).

BTW, this is a very usefull tip. I had been using it lately all the time
to trace ooops in kernel.

	objdump -S -C ./vmadump.ko  |less

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios

Li-Ta Lo | 1 Nov 19:32 2004

Re: status information

On Fri, 2004-10-29 at 17:38, Eric W. Biederman wrote:
> 
> As for size, the beoboot userland is one of the reasons why you are
> still using CF.  But that can be tuned.
> 

I see no relation between CF an beoboot. As I said, not everyone is 
happy with booting kernel over network. They don't use beoboot
an they want CF !!!

Ollie

_______________________________________________
Linuxbios mailing list
Linuxbios <at> clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios


Gmane