I am trying to get LinuxBIOS and AMD SimNOW working.
I tried to follow the how-to and have run into a brick wall.
It gets to the point of compiling linuxbios. Originally it could not find the file linuxbios-svn-2950.tar.gz file under sources and was failing. I then got this revision via svn and created this file. I put it in the sources directory, now the patch file for linuxbios is failing.
It took me a lot work to get to this point as I have been having proxy server problems. The machine I am building/testing with is in a lab and is behind the proxy.
I am pretty close to getting this compiled. I already have a system setup with SimNOW (NDA version). Any help would be appreciated...
On Jan 8, 2008 12:09 PM, Marc Karasek Marc.Karasek@sun.com wrote:
I am trying to get LinuxBIOS and AMD SimNOW working.
I tried to follow the how-to and have run into a brick wall.
It gets to the point of compiling linuxbios. Originally it could not find the file linuxbios-svn-2950.tar.gz file under sources and was failing. I then got this revision via svn and created this file. I put it in the sources directory, now the patch file for linuxbios is failing.
Here's my guess: When you got the revision and made the tarball, your directory structure ended up wrong so the patch won't apply. When you check it out from svn you get a LinuxBIOSv2/* and you need a svn/*
If that doesn't help, I don't have enough information to help you. Are you building for fam10 or the original Serengeti_cheetah? Which payload are you using? What patch is failing? What's the error message?
I just built LAB payloads for both versions of Serengeti Cheetah, and they worked for me.
Myles
It took me a lot work to get to this point as I have been having proxy server problems. The machine I am building/testing with is in a lab and is behind the proxy.
I am pretty close to getting this compiled. I already have a system setup with SimNOW (NDA version). Any help would be appreciated...
-- /********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
On 08/01/08 13:23 -0700, Myles Watson wrote:
On Jan 8, 2008 12:09 PM, Marc Karasek Marc.Karasek@sun.com wrote:
I am trying to get LinuxBIOS and AMD SimNOW working.
I tried to follow the how-to and have run into a brick wall.
It gets to the point of compiling linuxbios. Originally it could not find the file linuxbios-svn-2950.tar.gz file under sources and was failing. I then got this revision via svn and created this file. I put it in the sources directory, now the patch file for linuxbios is failing.
Here's my guess: When you got the revision and made the tarball, your directory structure ended up wrong so the patch won't apply. When you check it out from svn you get a LinuxBIOSv2/* and you need a svn/*
Thats probably right - it would be interesting to figure out why SVN isn't working for you - this is the first time we've had a general SVN failure like this.
Maybe we need to start using qa.linuxbios.org to as a backup for SVN failures.
Jordan
I t has to do with the proxy server here at Sun. I have setup to use it by editing the ~/.subversion/servers file, but it still will not properly do the proxy when I have to do a svn co svn://xxx/yyy. It seems to work ok for http and https checkouts.
I really hate proxy servers...
/********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
Jordan Crouse wrote:
On 08/01/08 13:23 -0700, Myles Watson wrote:
On Jan 8, 2008 12:09 PM, Marc Karasek Marc.Karasek@sun.com wrote:
I am trying to get LinuxBIOS and AMD SimNOW working.
I tried to follow the how-to and have run into a brick wall.
It gets to the point of compiling linuxbios. Originally it could not find the file linuxbios-svn-2950.tar.gz file under sources and was failing. I then got this revision via svn and created this file. I put it in the sources directory, now the patch file for linuxbios is failing.
Here's my guess: When you got the revision and made the tarball, your directory structure ended up wrong so the patch won't apply. When you check it out from svn you get a LinuxBIOSv2/* and you need a svn/*
Thats probably right - it would be interesting to figure out why SVN isn't working for you - this is the first time we've had a general SVN failure like this.
Maybe we need to start using qa.linuxbios.org to as a backup for SVN failures.
Jordan
You are right. I saw that it needed the files under svn/. So I moved the files into this directory under sources. This was from the svn co I did for version 2950. Could I use the tip of the tree for this or is it better to use version 2950?
Now it needs the patch for the compile problems, ld, etc.. for Fedora 8.
Progress no matter how slow is progress, I guess...................... :-)
/********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
Myles Watson wrote:
On Jan 8, 2008 12:09 PM, Marc Karasek Marc.Karasek@sun.com wrote:
I am trying to get LinuxBIOS and AMD SimNOW working.
I tried to follow the how-to and have run into a brick wall.
It gets to the point of compiling linuxbios. Originally it could not find the file linuxbios-svn-2950.tar.gz file under sources and was failing. I then got this revision via svn and created this file. I put it in the sources directory, now the patch file for linuxbios is failing.
Here's my guess: When you got the revision and made the tarball, your directory structure ended up wrong so the patch won't apply. When you check it out from svn you get a LinuxBIOSv2/* and you need a svn/*
If that doesn't help, I don't have enough information to help you. Are you building for fam10 or the original Serengeti_cheetah? Which payload are you using? What patch is failing? What's the error message?
I just built LAB payloads for both versions of Serengeti Cheetah, and they worked for me.
Myles
It took me a lot work to get to this point as I have been having proxy server problems. The machine I am building/testing with is in a lab and is behind the proxy.
I am pretty close to getting this compiled. I already have a system setup with SimNOW (NDA version). Any help would be appreciated...
-- /********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
-----Original Message----- From: Marc.Karasek@Sun.COM [mailto:Marc.Karasek@Sun.COM] Sent: Tuesday, January 08, 2008 3:02 PM To: Myles Watson Cc: LinuxBIOS Subject: Re: [LinuxBIOS] AMD SimNOW question
You are right. I saw that it needed the files under svn/. So I moved the files into this directory under sources. This was from the svn co I did for version 2950. Could I use the tip of the tree for this or is it better to use version 2950?
Now it needs the patch for the compile problems, ld, etc.. for Fedora 8.
Progress no matter how slow is progress, I guess...................... :- )
You can use the head of the tree. Buildrom is supposed to be a stable version, so a working version is always specified for v2.
Good luck, Myles
/********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
Myles Watson wrote:
On Jan 8, 2008 12:09 PM, Marc Karasek Marc.Karasek@sun.com wrote:
I am trying to get LinuxBIOS and AMD SimNOW working.
I tried to follow the how-to and have run into a brick wall.
It gets to the point of compiling linuxbios. Originally it could not find the file linuxbios-svn-2950.tar.gz file under sources and was failing. I then got this revision via svn and created this file. I
put
it in the sources directory, now the patch file for linuxbios is
failing.
Here's my guess: When you got the revision and made the tarball, your directory structure ended up wrong so the patch won't apply. When you check it out from svn you get a LinuxBIOSv2/* and you need a svn/*
If that doesn't help, I don't have enough information to help you. Are you building for fam10 or the original Serengeti_cheetah? Which payload are you using? What patch is failing? What's the error message?
I just built LAB payloads for both versions of Serengeti Cheetah, and they worked for me.
Myles
It took me a lot work to get to this point as I have been having proxy server problems. The machine I am building/testing with is in a lab
and
is behind the proxy.
I am pretty close to getting this compiled. I already have a system setup with SimNOW (NDA version). Any help would be appreciated...
-- /********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
On 08/01/08 15:10 -0700, Myles Watson wrote:
-----Original Message----- From: Marc.Karasek@Sun.COM [mailto:Marc.Karasek@Sun.COM] Sent: Tuesday, January 08, 2008 3:02 PM To: Myles Watson Cc: LinuxBIOS Subject: Re: [LinuxBIOS] AMD SimNOW question
You are right. I saw that it needed the files under svn/. So I moved the files into this directory under sources. This was from the svn co I did for version 2950. Could I use the tip of the tree for this or is it better to use version 2950?
Now it needs the patch for the compile problems, ld, etc.. for Fedora 8.
Progress no matter how slow is progress, I guess...................... :- )
You can use the head of the tree. Buildrom is supposed to be a stable version, so a working version is always specified for v2.
Yes - you can move up.
Jordan
I have found the main problem with svn. It looks like if you use svn co http:// it will use the proxy settings under servers. If you do a svn co svn:// it tries to do a dns lookup, which fails behind a proxy server :-(. I have not been able to find any info on setting svn up to use a proxy when doing svn:// type checkouts.
/********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
Jordan Crouse wrote:
On 08/01/08 15:10 -0700, Myles Watson wrote:
-----Original Message----- From: Marc.Karasek@Sun.COM [mailto:Marc.Karasek@Sun.COM] Sent: Tuesday, January 08, 2008 3:02 PM To: Myles Watson Cc: LinuxBIOS Subject: Re: [LinuxBIOS] AMD SimNOW question
You are right. I saw that it needed the files under svn/. So I moved the files into this directory under sources. This was from the svn co I did for version 2950. Could I use the tip of the tree for this or is it better to use version 2950?
Now it needs the patch for the compile problems, ld, etc.. for Fedora 8.
Progress no matter how slow is progress, I guess...................... :- )
You can use the head of the tree. Buildrom is supposed to be a stable version, so a working version is always specified for v2.
Yes - you can move up.
Jordan
On Tue, Jan 08, 2008 at 05:38:55PM -0500, Marc Karasek wrote:
If you do a svn co svn:// it tries to do a dns lookup, which fails behind a proxy server :-(. I have not been able to find any info on setting svn up to use a proxy when doing svn:// type checkouts.
svn:// is a plain TCP connection. Is it a SOCKS proxy? An HTTP proxy of course may not be able to help.
//Peter
On Jan 8, 2008 4:53 PM, Peter Stuge peter@stuge.se wrote:
On Tue, Jan 08, 2008 at 05:38:55PM -0500, Marc Karasek wrote:
If you do a svn co svn:// it tries to do a dns lookup, which fails behind a proxy server :-(. I have not been able to find any info on setting svn up to use a proxy when doing svn:// type checkouts.
svn:// is a plain TCP connection. Is it a SOCKS proxy? An HTTP proxy of course may not be able to help.
svn co svn://80.190.231.112/... ? It's an ugly hack, but will it work?
-dhbarr.
On Jan 8, 2008 2:38 PM, Marc Karasek Marc.Karasek@sun.com wrote:
I have found the main problem with svn. It looks like if you use svn co http:// it will use the proxy settings under servers. If you do a svn co svn:// it tries to do a dns lookup, which fails behind a proxy server :-(. I have not been able to find any info on setting svn up to use a proxy when doing svn:// type checkouts.
There is a way to do it, maybe: http://subversion.tigris.org/faq.html#proxy
ron
I have managed to cobble together a build structure that tries to build.
It gets to the point of building the linuxbios image and it chokes because the image is to large for the romsize.
Can someone shed some light on what Config.lb should be set to to get this to compile.
The payload buildrom is generating is 790,000+ bytes big.
/********************* Marc Karasek MTS Sun Microsystems mailto:marc.karasek@sun.com ph:770.360.6415 *********************/
ron minnich wrote:
On Jan 8, 2008 2:38 PM, Marc Karasek Marc.Karasek@sun.com wrote:
I have found the main problem with svn. It looks like if you use svn co http:// it will use the proxy settings under servers. If you do a svn co svn:// it tries to do a dns lookup, which fails behind a proxy server :-(. I have not been able to find any info on setting svn up to use a proxy when doing svn:// type checkouts.
There is a way to do it, maybe: http://subversion.tigris.org/faq.html#proxy
ron
In the TARGET file, you can put something like this:
option ROM_SIZE=1024*1024
that gets you 1M
ron
Here are my Config.lb files for Serengeti Cheetah and fam 10.
Good luck, Myles
On Jan 11, 2008 12:17 PM, ron minnich rminnich@gmail.com wrote:
In the TARGET file, you can put something like this:
option ROM_SIZE=1024*1024
that gets you 1M
ron