Re: [casper] 64-bit toolflow computer?

2010-05-22 Thread John Ford
> Hi Mandana
>
> Yes, things have definitely improved since the early Linux versions. I
> am now running Matlab R2008b and Xilinx 11.5 on RHEL5 Linux and am
> reasonably happy with it. Matlab still segfaults from time-to-time,
> but it's manageable.  There are still a few quirks (eg Simulink
> doesn't have a taskbar under Linux, dragging blocks sometimes
> dissapear etc) but they're all minor.
>
> 10.1 under Windows is stable, but will not be used moving forward
> (ROACH-II will require a lot of memory for larger designs, more than
> any 32-bit windows can handle). CASPER is now recommending RHEL5 as
> the OS of choice for the 11.x toolflow, and will likely be the case
> for 12.x and onwards. For this reason, I recommend you switch to
> Linux.

A full or nearly full ROACH-1 chip (sx-95) will also exceed the memory
limit imposed by Windows.  We also have a Linux install and it is better. 
It's faster, and allows bigger designs.

Same setup as Jason described above.

John

>
> Also, if possible, I strongly recommend you try to install things with
> their defaults (standard locations, no symlinks or network drives
> etc). This makes it much easier to support and we can more easily help
> you track down any problems you might have.
>
> Jason
>
> On 22 May 2010 01:52, Mandana Amiri  wrote:
>> Hi,
>>
>> We are going to use the Roach board (arriving soon!) for a
>> proof-of-concept
>> design. I am in the process of setting up the toolflow and I need to
>> decide
>> between windows versus RHEL. I read the following thread dated
>> mid-March:
>>
>> http://www.mail-archive.com/casper@lists.berkeley.edu/msg01328.html
>>
>> Has this recommendation changed since?
>>
>> Thanks,
>> Mandana
>>
>>
>> Jason Manley wrote:
>>>
>>> I too find RHEL a very frustrating OS to use on a day-to-day basis.
>>> But it seems the Xilinx tools rely on some of those ancient libraries
>>> that RedHat packages. We've had some success with installing newwer
>>> Debian-based distros, and then manually adding the older libraries
>>> (perl is the big annoyance). But this is far from reliable and not
>>> recommended. As Dan says, we've found some quirky behaviour where some
>>> designs compile and others do not.
>>>
>>> If you insist on running something other than RHEL (as I do), then I
>>> can suggest you get yourself a copy of the full RHEL5 root filesystem
>>> and do a chroot before starting matlab/xilinx tools. It works
>>> reliably, but is painful to setup (not to mention that it consumes
>>> ~20GB of diskspace). This is not something a Linux newbie should try
>>> and is not recommended for those who are not familiar with these tools
>>> and concepts. You can also do things like faking the hostname (using
>>> chname) and the ethernet adaptor's MAC (must be eth0; set up a null
>>> tap device) to ease licensing troubles when upgrading or moving your
>>> compile environment to a different hardware platform. In this way, as
>>> far as the toolflow is concerned, the system is RedHat (apart from the
>>> kernel, which is mostly the same).
>>>
>>> I mention this to illustrate that there are other toolflow
>>> possibilities. But please note that this is not a CASPER recommended
>>> configuration and we can not (and will not) offer support for anything
>>> other than a vanilla RHEL5 install.
>>>
>>> Jason
>>>
>>> On 21 May 2010 05:54, Dan Werthimer  wrote:
>>>

 hi bay, andy,

 i strongly recommend using Xilinx supported operating systems
 (eg: RHEL5).

 we've encountered some very strange bugs with other
 linux variants - these bugs don't appear like they might be operating
 system
 related, but when we switched over to RHEL5, the bugs vanished.

 also, xilinx will refuse to answer questions if you aren't using one
 of
 the
 operating systems they support.

 i'm hoping the bulk of the casper community will use RHEL5 or another
 xilinx supported system so we can all help each other.

 our group has switched to RHEL5 and i recommend it to other groups.

 dan





 On 5/20/2010 6:39 PM, Andrew Lutomirski wrote:

>
> On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:
>
>
>>>
>>> Hi Bay,
>>>
>>> We had to move to RHEL5 (64-bit ok) to get versions above 11.3
>>> working.
>>>  I've heard that CentOS works too.
>>>
>>>
>>
>> And you really need 64 bit...
>>
>>
>
> We're in the process of setting up a Fedora 13 system, since it's
> annoying to have packages as old as RHEL's.  Has anyone had any
> trouble with that?
>
> (There's also RHEL6 Beta, but I haven't gotten that to install
> without
> crashing, so I don't think it's quite ready for prime time.)
>
> --Andy
>
>
>
>>
>> John
>>
>>
>>
>>
>>>
>>> Mark
>>>
>>>
>>> On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
>>> wrote:
>>>

Re: [casper] 64-bit toolflow computer?

2010-05-22 Thread Jason Manley
Hi Mandana

Yes, things have definitely improved since the early Linux versions. I
am now running Matlab R2008b and Xilinx 11.5 on RHEL5 Linux and am
reasonably happy with it. Matlab still segfaults from time-to-time,
but it's manageable.  There are still a few quirks (eg Simulink
doesn't have a taskbar under Linux, dragging blocks sometimes
dissapear etc) but they're all minor.

10.1 under Windows is stable, but will not be used moving forward
(ROACH-II will require a lot of memory for larger designs, more than
any 32-bit windows can handle). CASPER is now recommending RHEL5 as
the OS of choice for the 11.x toolflow, and will likely be the case
for 12.x and onwards. For this reason, I recommend you switch to
Linux.

Also, if possible, I strongly recommend you try to install things with
their defaults (standard locations, no symlinks or network drives
etc). This makes it much easier to support and we can more easily help
you track down any problems you might have.

Jason

On 22 May 2010 01:52, Mandana Amiri  wrote:
> Hi,
>
> We are going to use the Roach board (arriving soon!) for a proof-of-concept
> design. I am in the process of setting up the toolflow and I need to decide
> between windows versus RHEL. I read the following thread dated mid-March:
>
> http://www.mail-archive.com/casper@lists.berkeley.edu/msg01328.html
>
> Has this recommendation changed since?
>
> Thanks,
> Mandana
>
>
> Jason Manley wrote:
>>
>> I too find RHEL a very frustrating OS to use on a day-to-day basis.
>> But it seems the Xilinx tools rely on some of those ancient libraries
>> that RedHat packages. We've had some success with installing newwer
>> Debian-based distros, and then manually adding the older libraries
>> (perl is the big annoyance). But this is far from reliable and not
>> recommended. As Dan says, we've found some quirky behaviour where some
>> designs compile and others do not.
>>
>> If you insist on running something other than RHEL (as I do), then I
>> can suggest you get yourself a copy of the full RHEL5 root filesystem
>> and do a chroot before starting matlab/xilinx tools. It works
>> reliably, but is painful to setup (not to mention that it consumes
>> ~20GB of diskspace). This is not something a Linux newbie should try
>> and is not recommended for those who are not familiar with these tools
>> and concepts. You can also do things like faking the hostname (using
>> chname) and the ethernet adaptor's MAC (must be eth0; set up a null
>> tap device) to ease licensing troubles when upgrading or moving your
>> compile environment to a different hardware platform. In this way, as
>> far as the toolflow is concerned, the system is RedHat (apart from the
>> kernel, which is mostly the same).
>>
>> I mention this to illustrate that there are other toolflow
>> possibilities. But please note that this is not a CASPER recommended
>> configuration and we can not (and will not) offer support for anything
>> other than a vanilla RHEL5 install.
>>
>> Jason
>>
>> On 21 May 2010 05:54, Dan Werthimer  wrote:
>>
>>>
>>> hi bay, andy,
>>>
>>> i strongly recommend using Xilinx supported operating systems
>>> (eg: RHEL5).
>>>
>>> we've encountered some very strange bugs with other
>>> linux variants - these bugs don't appear like they might be operating
>>> system
>>> related, but when we switched over to RHEL5, the bugs vanished.
>>>
>>> also, xilinx will refuse to answer questions if you aren't using one of
>>> the
>>> operating systems they support.
>>>
>>> i'm hoping the bulk of the casper community will use RHEL5 or another
>>> xilinx supported system so we can all help each other.
>>>
>>> our group has switched to RHEL5 and i recommend it to other groups.
>>>
>>> dan
>>>
>>>
>>>
>>>
>>>
>>> On 5/20/2010 6:39 PM, Andrew Lutomirski wrote:
>>>

 On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:


>>
>> Hi Bay,
>>
>> We had to move to RHEL5 (64-bit ok) to get versions above 11.3
>> working.
>>  I've heard that CentOS works too.
>>
>>
>
> And you really need 64 bit...
>
>

 We're in the process of setting up a Fedora 13 system, since it's
 annoying to have packages as old as RHEL's.  Has anyone had any
 trouble with that?

 (There's also RHEL6 Beta, but I haven't gotten that to install without
 crashing, so I don't think it's quite ready for prime time.)

 --Andy



>
> John
>
>
>
>
>>
>> Mark
>>
>>
>> On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
>> wrote:
>>
>>
>>
>>>
>>> We're setting up a new toolflow computer after Ubuntu stopped
>>> working.
>>> Should we be installing RHEL 64-bit install or 32-bit? The wiki
>>> mentions
>>> 64-bit in passing, but I remember there being some problems with
>>> 64-bit
>>> earlier...
>>>
>>> --
>>> Bay Grabowski
>>> b...@umail.ucsb.edu
>>>
>>>
>>>
>>>
>>>

Re: [casper] 64-bit toolflow computer?

2010-05-21 Thread Mandana Amiri

Hi,

We are going to use the Roach board (arriving soon!) for a 
proof-of-concept design. I am in the process of setting up the toolflow 
and I need to decide between windows versus RHEL. I read the following 
thread dated mid-March:


http://www.mail-archive.com/casper@lists.berkeley.edu/msg01328.html

Has this recommendation changed since?

Thanks,
Mandana


Jason Manley wrote:

I too find RHEL a very frustrating OS to use on a day-to-day basis.
But it seems the Xilinx tools rely on some of those ancient libraries
that RedHat packages. We've had some success with installing newwer
Debian-based distros, and then manually adding the older libraries
(perl is the big annoyance). But this is far from reliable and not
recommended. As Dan says, we've found some quirky behaviour where some
designs compile and others do not.

If you insist on running something other than RHEL (as I do), then I
can suggest you get yourself a copy of the full RHEL5 root filesystem
and do a chroot before starting matlab/xilinx tools. It works
reliably, but is painful to setup (not to mention that it consumes
~20GB of diskspace). This is not something a Linux newbie should try
and is not recommended for those who are not familiar with these tools
and concepts. You can also do things like faking the hostname (using
chname) and the ethernet adaptor's MAC (must be eth0; set up a null
tap device) to ease licensing troubles when upgrading or moving your
compile environment to a different hardware platform. In this way, as
far as the toolflow is concerned, the system is RedHat (apart from the
kernel, which is mostly the same).

I mention this to illustrate that there are other toolflow
possibilities. But please note that this is not a CASPER recommended
configuration and we can not (and will not) offer support for anything
other than a vanilla RHEL5 install.

Jason

On 21 May 2010 05:54, Dan Werthimer  wrote:
  

hi bay, andy,

i strongly recommend using Xilinx supported operating systems
(eg: RHEL5).

we've encountered some very strange bugs with other
linux variants - these bugs don't appear like they might be operating system
related, but when we switched over to RHEL5, the bugs vanished.

also, xilinx will refuse to answer questions if you aren't using one of the
operating systems they support.

i'm hoping the bulk of the casper community will use RHEL5 or another
xilinx supported system so we can all help each other.

our group has switched to RHEL5 and i recommend it to other groups.

dan





On 5/20/2010 6:39 PM, Andrew Lutomirski wrote:


On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:

  

Hi Bay,

We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
 I've heard that CentOS works too.

  

And you really need 64 bit...



We're in the process of setting up a Fedora 13 system, since it's
annoying to have packages as old as RHEL's.  Has anyone had any
trouble with that?

(There's also RHEL6 Beta, but I haven't gotten that to install without
crashing, so I don't think it's quite ready for prime time.)

--Andy


  

John





Mark


On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
wrote:


  

We're setting up a new toolflow computer after Ubuntu stopped working.
Should we be installing RHEL 64-bit install or 32-bit? The wiki
mentions
64-bit in passing, but I remember there being some problems with 64-bit
earlier...

--
Bay Grabowski
b...@umail.ucsb.edu





  




  






  





Re: [casper] 64-bit toolflow computer?

2010-05-21 Thread Tom Kuiper

John Ford wrote:

Obligatory car analogy!

I have a race car that's highly modified and hand-built and tuned.  I race
it on Friday nights.  It's fun to play with, drive, and work on.

But I drive my old subaru station wagon to work most days (unless we take
my  wife's Legacy GT turbo...), because I just want to get to work, not
play with the car.

Now, you young whippersnappers stay off my lawn while you play with your
newfangled OS and other toys...
  

I would call Debian stable a Volvo and Red Hat a Model T.  :-)

Tom



Re: [casper] 64-bit toolflow computer?

2010-05-21 Thread John Ford
Obligatory car analogy!

I have a race car that's highly modified and hand-built and tuned.  I race
it on Friday nights.  It's fun to play with, drive, and work on.

But I drive my old subaru station wagon to work most days (unless we take
my  wife's Legacy GT turbo...), because I just want to get to work, not
play with the car.

Now, you young whippersnappers stay off my lawn while you play with your
newfangled OS and other toys...

:)

John


> I too find RHEL a very frustrating OS to use on a day-to-day basis.
> But it seems the Xilinx tools rely on some of those ancient libraries
> that RedHat packages. We've had some success with installing newwer
> Debian-based distros, and then manually adding the older libraries
> (perl is the big annoyance). But this is far from reliable and not
> recommended. As Dan says, we've found some quirky behaviour where some
> designs compile and others do not.
>
> If you insist on running something other than RHEL (as I do), then I
> can suggest you get yourself a copy of the full RHEL5 root filesystem
> and do a chroot before starting matlab/xilinx tools. It works
> reliably, but is painful to setup (not to mention that it consumes
> ~20GB of diskspace). This is not something a Linux newbie should try
> and is not recommended for those who are not familiar with these tools
> and concepts. You can also do things like faking the hostname (using
> chname) and the ethernet adaptor's MAC (must be eth0; set up a null
> tap device) to ease licensing troubles when upgrading or moving your
> compile environment to a different hardware platform. In this way, as
> far as the toolflow is concerned, the system is RedHat (apart from the
> kernel, which is mostly the same).
>
> I mention this to illustrate that there are other toolflow
> possibilities. But please note that this is not a CASPER recommended
> configuration and we can not (and will not) offer support for anything
> other than a vanilla RHEL5 install.
>
> Jason
>
> On 21 May 2010 05:54, Dan Werthimer  wrote:
>>
>> hi bay, andy,
>>
>> i strongly recommend using Xilinx supported operating systems
>> (eg: RHEL5).
>>
>> we've encountered some very strange bugs with other
>> linux variants - these bugs don't appear like they might be operating
>> system
>> related, but when we switched over to RHEL5, the bugs vanished.
>>
>> also, xilinx will refuse to answer questions if you aren't using one of
>> the
>> operating systems they support.
>>
>> i'm hoping the bulk of the casper community will use RHEL5 or another
>> xilinx supported system so we can all help each other.
>>
>> our group has switched to RHEL5 and i recommend it to other groups.
>>
>> dan
>>
>>
>>
>>
>>
>> On 5/20/2010 6:39 PM, Andrew Lutomirski wrote:
>>>
>>> On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:
>>>
>
> Hi Bay,
>
> We had to move to RHEL5 (64-bit ok) to get versions above 11.3
> working.
>  I've heard that CentOS works too.
>

 And you really need 64 bit...

>>>
>>> We're in the process of setting up a Fedora 13 system, since it's
>>> annoying to have packages as old as RHEL's.  Has anyone had any
>>> trouble with that?
>>>
>>> (There's also RHEL6 Beta, but I haven't gotten that to install without
>>> crashing, so I don't think it's quite ready for prime time.)
>>>
>>> --Andy
>>>
>>>

 John



>
> Mark
>
>
> On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
> wrote:
>
>
>>
>> We're setting up a new toolflow computer after Ubuntu stopped
>> working.
>> Should we be installing RHEL 64-bit install or 32-bit? The wiki
>> mentions
>> 64-bit in passing, but I remember there being some problems with
>> 64-bit
>> earlier...
>>
>> --
>> Bay Grabowski
>> b...@umail.ucsb.edu
>>
>>
>>
>>
>
>




>>>
>>>
>>
>>
>>
>
>





Re: [casper] 64-bit toolflow computer?

2010-05-21 Thread Jason Manley
I too find RHEL a very frustrating OS to use on a day-to-day basis.
But it seems the Xilinx tools rely on some of those ancient libraries
that RedHat packages. We've had some success with installing newwer
Debian-based distros, and then manually adding the older libraries
(perl is the big annoyance). But this is far from reliable and not
recommended. As Dan says, we've found some quirky behaviour where some
designs compile and others do not.

If you insist on running something other than RHEL (as I do), then I
can suggest you get yourself a copy of the full RHEL5 root filesystem
and do a chroot before starting matlab/xilinx tools. It works
reliably, but is painful to setup (not to mention that it consumes
~20GB of diskspace). This is not something a Linux newbie should try
and is not recommended for those who are not familiar with these tools
and concepts. You can also do things like faking the hostname (using
chname) and the ethernet adaptor's MAC (must be eth0; set up a null
tap device) to ease licensing troubles when upgrading or moving your
compile environment to a different hardware platform. In this way, as
far as the toolflow is concerned, the system is RedHat (apart from the
kernel, which is mostly the same).

I mention this to illustrate that there are other toolflow
possibilities. But please note that this is not a CASPER recommended
configuration and we can not (and will not) offer support for anything
other than a vanilla RHEL5 install.

Jason

On 21 May 2010 05:54, Dan Werthimer  wrote:
>
> hi bay, andy,
>
> i strongly recommend using Xilinx supported operating systems
> (eg: RHEL5).
>
> we've encountered some very strange bugs with other
> linux variants - these bugs don't appear like they might be operating system
> related, but when we switched over to RHEL5, the bugs vanished.
>
> also, xilinx will refuse to answer questions if you aren't using one of the
> operating systems they support.
>
> i'm hoping the bulk of the casper community will use RHEL5 or another
> xilinx supported system so we can all help each other.
>
> our group has switched to RHEL5 and i recommend it to other groups.
>
> dan
>
>
>
>
>
> On 5/20/2010 6:39 PM, Andrew Lutomirski wrote:
>>
>> On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:
>>

 Hi Bay,

 We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
  I've heard that CentOS works too.

>>>
>>> And you really need 64 bit...
>>>
>>
>> We're in the process of setting up a Fedora 13 system, since it's
>> annoying to have packages as old as RHEL's.  Has anyone had any
>> trouble with that?
>>
>> (There's also RHEL6 Beta, but I haven't gotten that to install without
>> crashing, so I don't think it's quite ready for prime time.)
>>
>> --Andy
>>
>>
>>>
>>> John
>>>
>>>
>>>

 Mark


 On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
 wrote:


>
> We're setting up a new toolflow computer after Ubuntu stopped working.
> Should we be installing RHEL 64-bit install or 32-bit? The wiki
> mentions
> 64-bit in passing, but I remember there being some problems with 64-bit
> earlier...
>
> --
> Bay Grabowski
> b...@umail.ucsb.edu
>
>
>
>


>>>
>>>
>>>
>>>
>>
>>
>
>
>



Re: [casper] 64-bit toolflow computer?

2010-05-20 Thread Dan Werthimer


hi bay, andy,

i strongly recommend using Xilinx supported operating systems
(eg: RHEL5).

we've encountered some very strange bugs with other
linux variants - these bugs don't appear like they might be operating system
related, but when we switched over to RHEL5, the bugs vanished.

also, xilinx will refuse to answer questions if you aren't using one of the
operating systems they support.

i'm hoping the bulk of the casper community will use RHEL5 or another
xilinx supported system so we can all help each other.

our group has switched to RHEL5 and i recommend it to other groups.

dan





On 5/20/2010 6:39 PM, Andrew Lutomirski wrote:

On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:
   

Hi Bay,

We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
  I've heard that CentOS works too.
   

And you really need 64 bit...
 

We're in the process of setting up a Fedora 13 system, since it's
annoying to have packages as old as RHEL's.  Has anyone had any
trouble with that?

(There's also RHEL6 Beta, but I haven't gotten that to install without
crashing, so I don't think it's quite ready for prime time.)

--Andy

   

John


 

Mark


On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
wrote:

   

We're setting up a new toolflow computer after Ubuntu stopped working.
Should we be installing RHEL 64-bit install or 32-bit? The wiki mentions
64-bit in passing, but I remember there being some problems with 64-bit
earlier...

--
Bay Grabowski
b...@umail.ucsb.edu



 
   




 
   





Re: [casper] 64-bit toolflow computer?

2010-05-20 Thread Mark Wagner
Hi Andrew,

I did try Fedora 12, which didn't work either.  I really wasn't happy with
RHEL5 for the same reason you mention, but it was the only OS I was able to
get to work with the newest tools.  It also meant Xilinx would answer our
questions, or at least attempt to.

Mark



On Thu, May 20, 2010 at 6:39 PM, Andrew Lutomirski  wrote:

> On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:
> >> Hi Bay,
> >>
> >> We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
> >>  I've heard that CentOS works too.
> >
> > And you really need 64 bit...
>
> We're in the process of setting up a Fedora 13 system, since it's
> annoying to have packages as old as RHEL's.  Has anyone had any
> trouble with that?
>
> (There's also RHEL6 Beta, but I haven't gotten that to install without
> crashing, so I don't think it's quite ready for prime time.)
>
> --Andy
>
> >
> > John
> >
> >
> >>
> >> Mark
> >>
> >>
> >> On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
> >> wrote:
> >>
> >>> We're setting up a new toolflow computer after Ubuntu stopped working.
> >>> Should we be installing RHEL 64-bit install or 32-bit? The wiki
> mentions
> >>> 64-bit in passing, but I remember there being some problems with 64-bit
> >>> earlier...
> >>>
> >>> --
> >>> Bay Grabowski
> >>> b...@umail.ucsb.edu
> >>>
> >>>
> >>>
> >>
> >
> >
> >
> >
>


Re: [casper] 64-bit toolflow computer?

2010-05-20 Thread John Ford
> On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:
>>> Hi Bay,
>>>
>>> We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
>>>  I've heard that CentOS works too.
>>
>> And you really need 64 bit...
>
> We're in the process of setting up a Fedora 13 system, since it's
> annoying to have packages as old as RHEL's.  Has anyone had any
> trouble with that?

We use RHEL 5:

Yes, Master<1002> uname -a
Linux tokra 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64
x86_64 x86_64 GNU/Linux

If you look at the list archives, you'll see a stretch where people tried
different OS's, and I think the only ones that work without problems are
RHEL and centos.  It would be a service to all if you can figure out how
to make it all work on some other OS.  But xilinx won't be able to help
you...

John





Re: [casper] 64-bit toolflow computer?

2010-05-20 Thread Andrew Lutomirski
On Thu, May 20, 2010 at 9:34 PM, John Ford  wrote:
>> Hi Bay,
>>
>> We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
>>  I've heard that CentOS works too.
>
> And you really need 64 bit...

We're in the process of setting up a Fedora 13 system, since it's
annoying to have packages as old as RHEL's.  Has anyone had any
trouble with that?

(There's also RHEL6 Beta, but I haven't gotten that to install without
crashing, so I don't think it's quite ready for prime time.)

--Andy

>
> John
>
>
>>
>> Mark
>>
>>
>> On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
>> wrote:
>>
>>> We're setting up a new toolflow computer after Ubuntu stopped working.
>>> Should we be installing RHEL 64-bit install or 32-bit? The wiki mentions
>>> 64-bit in passing, but I remember there being some problems with 64-bit
>>> earlier...
>>>
>>> --
>>> Bay Grabowski
>>> b...@umail.ucsb.edu
>>>
>>>
>>>
>>
>
>
>
>



Re: [casper] 64-bit toolflow computer?

2010-05-20 Thread John Ford
> Hi Bay,
>
> We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
>  I've heard that CentOS works too.

And you really need 64 bit...

John


>
> Mark
>
>
> On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski
> wrote:
>
>> We're setting up a new toolflow computer after Ubuntu stopped working.
>> Should we be installing RHEL 64-bit install or 32-bit? The wiki mentions
>> 64-bit in passing, but I remember there being some problems with 64-bit
>> earlier...
>>
>> --
>> Bay Grabowski
>> b...@umail.ucsb.edu
>>
>>
>>
>





Re: [casper] 64-bit toolflow computer?

2010-05-20 Thread Mark Wagner
Hi Bay,

We had to move to RHEL5 (64-bit ok) to get versions above 11.3 working.
 I've heard that CentOS works too.

Mark


On Thu, May 20, 2010 at 3:49 PM, Bay E. Grabowski wrote:

> We're setting up a new toolflow computer after Ubuntu stopped working.
> Should we be installing RHEL 64-bit install or 32-bit? The wiki mentions
> 64-bit in passing, but I remember there being some problems with 64-bit
> earlier...
>
> --
> Bay Grabowski
> b...@umail.ucsb.edu
>
>
>


[casper] 64-bit toolflow computer?

2010-05-20 Thread Bay E. Grabowski
We're setting up a new toolflow computer after Ubuntu stopped working.  
Should we be installing RHEL 64-bit install or 32-bit? The wiki  
mentions 64-bit in passing, but I remember there being some problems  
with 64-bit earlier...


--
Bay Grabowski
b...@umail.ucsb.edu