On 08/01/2012 02:44 AM, Brig McCoy wrote: > We've got one that we're not using... what would be involved in setting it up > for use as a build/porter?
Best would be to have it somewhere at a location where we host Debian hardware already. We want to avoid to have yet another hosting location :) Where is the machine located? And would you be willing to give it out of your hands? Feel free to reply to hardware-donati...@debian.org instead. Thanks, Bernd > > ...brig > ________________________________________ > From: Bernd Zeimetz [be...@bzed.de] > Sent: Tuesday, July 31, 2012 6:30 PM > To: T.J. Yang > Cc: Michel Schanen; debian-sparc@lists.debian.org > Subject: Re: Oracle Sun T5120 support getting better in debian 6.0.5 ? > > Hi, > > On 07/13/2012 03:20 PM, T.J. Yang wrote: >> Hi, Michel >> >> Thanks for sharing your info on running Debian on Sun T5120. I really >> appreciate this. >> >> I haven't made the switch yet. I will probably start with running the >> test using LDOM since I don't have a physical T5120 for testing. > > the debian project also doesn't have a T5120 or similar machine - would be > nice > to have as a buildd/porter box to ensure the sparc port keeps going on. Just > in > case somebody has a spare one ;) > > Cheers, > > Bernd > >> >> tj >> >> On Fri, Jul 13, 2012 at 6:48 AM, Michel Schanen >> <michel.scha...@googlemail.com> wrote: >>> Hi, >>> >>> we installed Debian SPARC 6.0.3 on 20 Sun T5120 Enterprise nodes >>> interconnected with infiniband cards and onboard network cards. The >>> infiniband cards are very buggy and only work over IP. Problem is that there >>> are no supported infiniband drivers for Linux/SPARC. >>> >>> I recommend the Debian installation guide for SPARCs. We used the TFTP >>> method, which worked fairly well. We ran into the same trouble as you when >>> connecting a CDROM drive. >>> >>> http://www.debian.org/releases/stable/sparc/ch04s03.html.en >>> >>> Only trick was that the image had to be named after the IP of the >>> installation target, e.g. 192.168.0.2 -> C0.A8.00.02 >>> >>> We received these cluster nodes at no costs and we use them essentially for >>> simulation codes/testing. As the tools are all SPARC and not SPARC64 we had >>> some problems using OpenMP. For instance the atomic statement was very slow. >>> After compiling gcc with arch=SPARC64 we had a considerable performance >>> boost using OpenMP. In the end, all our development tools are now recompiled >>> with arch=SPARC64. >>> >>> Other than that, everything works flawlessly! NFS crashes after some weeks >>> of uptime. Therefore we do a weekly reboot. >>> >>> You will be able to log in to the ILOM SPs over SSH and eventually to your >>> system console. >>> >>> Oh and don't forget to recompile your kernel with 64 CPU support. Otherwise >>> you will be stuck with 32 or something. >>> >>> Michel >> >> >> > > > -- > Bernd Zeimetz Debian GNU/Linux Developer > http://bzed.de http://www.debian.org > GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F > > > -- > To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/50186aa9.4030...@bzed.de > > > > -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5022dade.6050...@bzed.de