Re: [LinuxBIOS] Build issue for khepri target

[Lu, Yinghai]

Please change FALLBACK_SIZE in MB Config.lb to

#default FALLBACK_SIZE=0x40000

YH

________________________________

From: [e-mail]
[mailto:[e-mail]] On Behalf Of Anil B G
Sent: Wednesday, July 12, 2006 7:58 AM
To: [e-mail]
Subject: [LinuxBIOS] Build issue for khepri target

Hi,

I am new to LinuxBIOS. I downloaded the latest snapshot of LinuxBIOSv2
and tried building it for a couple of boards (newisys/intel etc).

I was able to build it for intel but when I tried to build it for
newisys/khepri I got the following error:

gcc -o buildrom
/home/anil/LinuxBios/LinuxBIOSv2/util/buildrom/buildrom.c
./buildrom linuxbios.strip linuxbios.rom payload 0x20000 0x20000
payload (77000) + linuxbios (131072) size larger than ROM (131072) size!

make[1]: *** [linuxbios.rom] Error 1
make[1]: Leaving directory
`/home/anil/LinuxBios/LinuxBIOSv2/targets/newisys/khepri/khepri/fallback
'
make: *** [fallback/linuxbios.rom] Error 1

I disabled the fallback option and then was able to get the khepri.rom
whose size was 384K. I am using the FILO as the payload.

Is the size of 384K fine? Has any one used LinuxBIOSv2 on khepri? Would
appreciate any help.

Pls. let me know if any addl. info is reqd.

The gcc version is 3.4.3

Regards

Anil

[LinuxBIOS] Build issue for khepri target

[Anil B G]

Hi,

Thanks for the help. I changed the option FALLBACK_SIZE=262144 in the
targets/newisys/khepri/Config.lb and I was able to build the khepri.rom file
of size 512K. Would be nice to document the same somewhere.

I also managed to try loading the same on a khepri board that I could lay my
hands on.
However the system did not boot . Is there a way to enable some beep() or
something similar early on to know that the
processor has started executing the LinuxBIOS code. I do not have a scope or
other hardware that I could use to probe.
There was some output on the serial but that from the service processor that
my khepri board has.
 Any pointers?

Regards
Anil

On 7/12/06, Lu, Yinghai  wrote:
> Please change FALLBACK_SIZE in MB Config.lb http://config.lb/ to
>
> #default FALLBACK_SIZE=0x40000
>
> YH
>
> *From:* [e-mail] [mailto:
> [e-mail]] *On Behalf Of *Anil B G
> *Sent:* Wednesday, July 12, 2006 7:58 AM
> *To:* [e-mail]
> *Subject:* [LinuxBIOS] Build issue for khepri target
>
> Hi,
>
> I am new to LinuxBIOS. I downloaded the latest snapshot of LinuxBIOSv2
> and tried building it for a couple of boards (newisys/intel etc).
>
> I was able to build it for intel but when I tried to build it for
> newisys/khepri I got the following error:
>
> gcc -o buildrom /home/anil/LinuxBios/LinuxBIOSv2/util/buildrom/buildrom.c
> ./buildrom linuxbios.strip linuxbios.rom payload 0x20000 0x20000
> payload (77000) + linuxbios (131072) size larger than ROM (131072) size!
> make[1]: *** [linuxbios.rom] Error 1
> make[1]: Leaving directory
> `/home/anil/LinuxBios/LinuxBIOSv2/targets/newisys/khepri/khepri/fallback'
> make: *** [fallback/linuxbios.rom] Error 1
>
> I disabled the fallback option and then was able to get the khepri.romwhose size was 384K. I am using the FILO as the payload.
>
> Is the size of 384K fine? Has any one used LinuxBIOSv2 on khepri? Would
> appreciate any help.
>
> Pls. let me know if any addl. info is reqd.
>
> The gcc version is 3.4.3
>
> Regards
>
> Anil

[LinuxBIOS] Build issue for khepri target

[Ronald G Minnich]

Anil B G wrote:
> Hi,
>
> Thanks for the help. I changed the option FALLBACK_SIZE=262144 in the 
> targets/newisys/khepri/Config.lb and I was able to build the khepri.rom 
> file  of size 512K. Would be nice to document the same somewhere.

yes. It's an obsolete mobo, and what I'd rather start doing is culling 
the old non-available mobos from the tree at some point. How do we do this?

It's been over 2 years since I worked with these boards (I did not like 
them at all),  so my memory on how to use it is very shady.

thanks

ron

[LinuxBIOS] Build issue for khepri target

[Richard Smith]

> yes. It's an obsolete mobo, and what I'd rather start doing is culling
> the old non-available mobos from the tree at some point. How do we do this?
>
> It's been over 2 years since I worked with these boards (I did not like
> them at all),  so my memory on how to use it is very shady.

I think thats a mistake.  These are the motherboards that are going to
start showing up on e-bay and other surplus channels. That puts them
in the realm of the home hobbiest and students who want to mess with
this.   Remember that just yesterday got a question about V2 support
for a 440bx board.

Perhaps we can just re-organize the targets tree to indicate whats
current and not current?

[LinuxBIOS] Build issue for khepri target

[Uwe Hermann]

Hi,

On Fri, Jul 14, 2006 at 09:35:55AM -0600, Ronald G Minnich wrote:
> yes. It's an obsolete mobo, and what I'd rather start doing is culling 
> the old non-available mobos from the tree at some point. How do we do this?

Pleas don't. Such "obsolete" hardware is often used to test stuff,
e.g. to get started with LinuxBIOS without investing too
much money or risking breaking "good" hardware.

Mark them as "old" or "deprecated" or something, but please leave the
support for such hardware in the code.

Thanks, Uwe.

[LinuxBIOS] Build issue for khepri target

[Ronald G Minnich]

Richard Smith wrote:
> > yes. It's an obsolete mobo, and what I'd rather start doing is culling
> > the old non-available mobos from the tree at some point. How do we do 
> > this?
> >
> > It's been over 2 years since I worked with these boards (I did not like
> > them at all),  so my memory on how to use it is very shady.
>
> I think thats a mistake.  These are the motherboards that are going to
> start showing up on e-bay and other surplus channels. That puts them
> in the realm of the home hobbiest and students who want to mess with
> this.   Remember that just yesterday got a question about V2 support
> for a 440bx board.
>
> Perhaps we can just re-organize the targets tree to indicate whats
> current and not current?

I guess we'll just leave it as is.

you make a good point.

ron

[LinuxBIOS] Build issue for khepri target

[Stefan Reinauer]

* Anil B G  [060714 17:14]:
> I also managed to try loading the same on a khepri board that I could lay my
> hands on.
> However the system did not boot . Is there a way to enable some beep() or
> something similar early on to know that the
> processor has started executing the LinuxBIOS code. I do not have a scope or
> other hardware that I could use to probe.
> There was some output on the serial but that from the service
> processor that my khepri board has.

The Sun Fire V20z AKA Newisys 2100 AKA Newisys Khepri has a very nice
PPC based service processor that can grab the serial output as well as
the port80 post code.

Type "platform" after logging in to the service CPU with ssh.

There's also a trick to become root on the SP itself. If you put the
machine serial port to be grabbed by the SP, the SP serial port will be
sent to the physical serial connector and you get a ppcboot screen..

Unfortunately the Newisys 2100 I have is running linuxbios.org now, so 
I dont really dare reflashing it remotely. ;-)

Stefan

[LinuxBIOS] Build issue for khepri target

[Anil B G]

Hi,
  Thanks for the response. But my concern is how do I get output of
LinuxBIOS on the serial. Can I disable the service processor output by doing
a platform after logging into the SP?
I am not sure if the LinuxBIOS code itself is running. Is there a way to
confirm that, other than checking the serial?

Regards
Anil

On 7/14/06, Stefan Reinauer  wrote:
> Anil B G  [060714 17:14]:
> > I also managed to try loading the same on a khepri board that I could
>
> lay my
> > hands on.
> > However the system did not boot . Is there a way to enable some beep()
>
> or
> > something similar early on to know that the
> > processor has started executing the LinuxBIOS code. I do not have a
>
> scope or
> > other hardware that I could use to probe.
> > There was some output on the serial but that from the service
> > processor that my khepri board has.
>
> The Sun Fire V20z AKA Newisys 2100 AKA Newisys Khepri has a very nice
> PPC based service processor that can grab the serial output as well as
> the port80 post code.
>
> Type "platform" after logging in to the service CPU with ssh.
>
> There's also a trick to become root on the SP itself. If you put the
> machine serial port to be grabbed by the SP, the SP serial port will be
> sent to the physical serial connector and you get a ppcboot screen..
>
> Unfortunately the Newisys 2100 I have is running linuxbios.org now, so
> I dont really dare reflashing it remotely. ;-)
>
> Stefan

[LinuxBIOS] Build issue for khepri target

[Stefan Reinauer]

* Anil B G  [060717 05:34]:
> Hi,
>   Thanks for the response. But my concern is how do I get output of LinuxBIOS
> on the serial. Can I disable the service processor output by doing a platform
> after logging into the SP?

do you get service processor output on the serial interface at all?

Please refer to the manual of the service processor
> I am not sure if the LinuxBIOS code itself is running. Is there a way to
> confirm that, other than checking the serial?

Whats wrong with checking the serial [output|connection|whatever]?

Stefan

[LinuxBIOS] Build issue for khepri target

[Anil B G]

Hi,
  I only get the output of the SP on the serial interface.
Regards
Anil

On 7/17/06, Stefan Reinauer  wrote:
> Anil B G  [060717 05:34]:
> > Hi,
> >   Thanks for the response. But my concern is how do I get output of
>
> LinuxBIOS
> > on the serial. Can I disable the service processor output by doing a
>
> platform
> > after logging into the SP?
>
> do you get service processor output on the serial interface at all?
>
> Please refer to the manual of the service processor
> > I am not sure if the LinuxBIOS code itself is running. Is there a way to
> > confirm that, other than checking the serial?
>
> Whats wrong with checking the serial [output|connection|whatever]?
>
> Stefan

[LinuxBIOS] Build issue for khepri target

[Stefan Reinauer]

* Anil B G  [060717 17:07]:
> Hi,
>   I only get the output of the SP on the serial interface.

log in to the sp and do "platform console"