Problem Sage 3.4 windows XP

[madison...@gmail.com]

I am also having a problem running Sage 3.4 on windows XP. Vmware
starts up, but when I run the notebook command it flashes the IP
address and then returns to the main vmware text menu. I thought it
was a problem with my upgrade from Sage 3.2.3. So I uninstalled
vmware and redown loaded Sage 3.4 I got the same problem after a
reinstalled vmware and Sage 3.4. I was able to run WINSCP to move my
old sage files from the IP address. I just can't log on to sage from
windows explorer.

I have reinstalled Sage 3.2.3 and it runs fine with notebook. The IP
address has changed, but I assume this is due to my reinstall of
VMware.

I am running windows XP on a 1.4 GHz intel processor with 1 GB of
memory. Thanks Mike

[William Stein]

On Wed, Mar 18, 2009 at 1:22 PM, <madison...@gmail.com> wrote:
>
> I am also having a problem running Sage 3.4 on windows XP.   Vmware
> starts up, but when I run the notebook command it flashes the IP

Just out of curiosity, has *anybody* successfully used
sage-vmware-3.4.zip? Maybe it is seriously broken?

William

> address and then returns to the main vmware text menu.  I thought it
> was a problem with my upgrade from Sage 3.2.3.  So I uninstalled
> vmware and redown loaded Sage 3.4  I got the same problem after a
> reinstalled vmware and Sage 3.4.  I was able to run WINSCP to move my
> old sage files from the IP address.  I just can't log on to sage from
> windows explorer.
>
> I have reinstalled Sage 3.2.3 and it runs fine with notebook.  The IP
> address has changed, but I assume this is due to my reinstall of
> VMware.
>
> I am running windows XP on a 1.4 GHz intel processor with 1 GB of
> memory. Thanks Mike
> >
>

--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

[SG]

> Just out of curiosity, has *anybody* successfully used
> sage-vmware-3.4.zip? Maybe it is seriously broken?

sage-vmware-3.4.zip worked fine on my home laptop running Windows
Vista, but when I tried installing it on
my work PC (running XP), and I had the same problem that madison.mich
is talking about. Please help..

SG

On Mar 18, 1:33 pm, William Stein <wst...@gmail.com> wrote:
> On Wed, Mar 18, 2009 at 1:22 PM,  <madison.mich...@gmail.com> wrote:
>
> > I am also having a problem running Sage 3.4 onwindowsXP.   Vmware

> > starts up, but when I run the notebook command it flashes the IP
>
> Just out of curiosity, has *anybody* successfully used
> sage-vmware-3.4.zip?  Maybe it is seriously broken?
>
> William
>
> > address and then returns to the main vmware text menu.  I thought it
> > was a problem with my upgrade from Sage 3.2.3.  So I uninstalled
> > vmware and redown loaded Sage 3.4  I got the same problem after a
> > reinstalled vmware and Sage 3.4.  I was able to run WINSCP to move my
> > old sage files from the IP address.  I just can't log on to sage from
> >windowsexplorer.
>
> > I have reinstalled Sage 3.2.3 and it runs fine with notebook.  The IP
> > address has changed, but I assume this is due to my reinstall of
> > VMware.
>

> > I am runningwindowsXPon a 1.4 GHz intel processor with 1 GB of

[Nasser Abbasi]

On Mar 18, 1:33 pm, William Stein <wst...@gmail.com> wrote:

> On Wed, Mar 18, 2009 at 1:22 PM,  <madison.mich...@gmail.com> wrote:
>
> > I am also having a problem running Sage 3.4 on windows XP.   Vmware
> > starts up, but when I run the notebook command it flashes the IP
>
> Just out of curiosity, has *anybody* successfully used
> sage-vmware-3.4.zip?  Maybe it is seriously broken?
>
> William
>

I downloaded sage-vmware-3.4.zip on my XP SP2, and doubled click on
the vmx and it starts up with no problem, and the I am using it now
from firefox.

4 GB RAM, the VM player I am using is 2.5, build=118166

--Nasser

[madison...@gmail.com]

I just tried increasing my virtual memory (swap) from 3.048 GB to
6.096 GB and than did not help. I also tried increasing my vmplayer
memory from 512 MB to 788 MB and 1776 MB and this did not fix the
problem. Again, I have a 1.4 GHz with 1 GB of ram on windows XP. I
still have not been able to get Sage 3.4 to work. Mike

[tclendenen]

I'm having the same problem. Sage 3.1.4 works but after upgrading to
3.4 the notebook command appears to fail and goes back to the sage
login menu. I'm using VMware Workstation 6.5.2, the OS is WinXP sp3,
and the machine has 1.5 GB of memory.

[gemili]

a) Same problem. Sage 3.2.3 runs, Sage 3.4.1 does not run. Both on
WindowsXP, Service Pack 3, with VMware-player-2.5.2-156735. I tried on
two different computers (one with XP-Professional, one with XP-home)
but both with Service Pack 3.

b) I tried to type "manage" instead of "notebook", then "sudo su" and
then "sage".
Following happened on the first computer:

Sage Version 3.4.1, Release Date: 2009-04-21
Type notebook() for the GUI, and license () for information.
/usr/local/sage/bin/sage-sage: line 198: 4057 Illegal
instruction sage-ipython "$@" -i
root@sage:/home/manage# _

Following happened on the second computer:

Sage Version 3.4.1, Release Date: 2009-04-21
Type notebook() for the GUI, and license () for information.

**************************************************************************
Warning! This Sage install was build on a machine that supports
instructions
that are not available on this computer. Sage will likely fail
with Illegal
Instruction errors! The following processor flags were on the build
machine
but are not on this vomputer:
sse2

Email ...
root@sage:/home/manage# sage
.... and then again I got the error message regarding line 198 like
above.

[gemili]

Same problem on two different computers running WindowsXP Service Pack
3 with VMware-player-2.5.2-156735: SAGE 3.2.3 works and SAGE 3.4.1
does not work.

It looks that there is something wrong on "line 198" as I got an error
message as following. Trying to start the command line Version with
"manage", "sudo su" and then "sage" I got the following message on
both computers:

Sage Version 3.4.1, Release Date : 2009-04-21
Type notebook() for the GUI, and license() for information.

/usr/local/sage/local/bin/sage-sage: line 198: 4084 Illegal
instruction sag
e-ipython "$@" -i
root@sage:/home/manage#

[William Stein]

Hi,

What is the output of

cat /proc/cpuinfo

on both computers? You need to use manage before typing the above.

The error message you're getting specifically means that Sage was
built on a machine with a processor that is much newer than yours.
Did you actually read the error message? Here it is: " Warning! This

Sage install was build on a machine that supports instructions
that are not available on this computer. Sage will likely fail with
Illegal Instruction errors!"

-- William

[gemili]

Thank you for the fast answer.

1.) One of my computers is a five year old "Fujitsu-Siemens Livebook
C1110D"
1a) I tried WindowsXP, SP3 --> SAGE 3.4.1 did not work.
1b) I tried WindowsXP, SP2 --> SAGE 3.4.1 did not work.
1c) I tried the "Sage LiveCD" (which has its own UNIX operation
system) on this computer and it also didn't work. Maybe it is a hint,
that the problem is independent from the Operating system (but it can
be also a problem with the LiveCD).

1d) Following is the result of cat /proc/cpuinfo for this computer:
processor: : 0
vendor_id: GenuineIntel
cpu family: 6
model: 9
model name: Intel(R) Pentium(R) M processor 1400Mhz
stepping: 5
cpu Mhz: 1399.177
cache size: 1024 kB
fdiv_bug: no
hlt_bug: no
f00f_bug: no
coma_bug: no
fpu: yes
fpu_exeption: yes
cupid level: 2
wp: yes
flags: fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov pat
clflush dts acpi mmx fxsr sse sse2 up
bogomips: 2803.98

2.) Second computer is a Desktop with WindowsXP, SP3.
2a) When starting SAGE 3.4.1, it will not work and I receive the error
message concerning the sse2 flag. (I don't receive this message with
the above mentioned Siemens Laptop, No 1.). The message is

"Warning! This Sage install was build on a machine that supports
instructions that are not available on this computer. Sage will

likely fail with Illegal Instruction errors! The following processor
flags were on the build machine
but are not on this vomputer: sse2 "

2b) Following is the result of this Desktop:

processor: : 0
vendor_id: AuthenticAMD
cpu family: 6
model: 8
model name: AMD Athlon (TM) XP2200+
stepping: 1
cpu Mhz: 1799.135
cache size: 256 kB
fdiv_bug: no
hlt_bug: no
f00f_bug: no
coma_bug: no
fpu: yes
fpu_exeption: yes
cupid level: 1
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts
bogomips: 3615.72

3) The third computer is also a Desktop. SAGE 3.4.1 is running on this
computer under WindowsXP, Service Pack 2.

3a) Cpuinfo reports the following flages: "fpu vme de pse tsc msr pae
mce cx8 apic sep mtrr pge cmov pat clflush acpi mmx fxse sse sse2 nx
up pni rng rng_en ace ace_en."


RESULT:
Computer No 1 has the sse2 flag, but doesn't run SAGE 3.4.1 (SAGE
3.2.3 did run). Computer No. 2 doen't have the sse2 flag and doesn't
run SAGE 3.4.1. Computer No. 3 has the ss2 flag and runs SAGE 3.4.1.

The result seams to be independent from SP2 or SP3.

Maybe it would be a good idea to compile Sage without the sse2 flag
(whatever it is...)

Hopefully it helps.
Gemili

[William Stein]

Computer no 2 should not be able to run Sage, so let's ignore that for now.

Compute 1: doesn't run Sage

Computer 3: runs Sage

We have

# computer 1
sage: a = "fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge cmov

pat clflush acpi mmx fxse sse sse2 nx up pni rng rng_en ace ace_en."

# computer 3
sage: b = "fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov

pat clflush dts acpi mmx fxsr sse sse2 up"

sage: a = set(a.split())
sage: b = set(b.split())

# what (1) has the (3) doesn't:
sage: ' '.join([x for x in a if x not in b])
'fxse nx rng_en pae ace_en. rng pni ace'

# what (3) has the (1) doesn't:
sage: ' '.join([x for x in b if x not in a])
'fxsr mca dts'

This suggests that fxsr, mca, or dts is relevant. My build machine
has all those flags, but your machine (1) doesn't.

fxsr is: "FXSAVE/FXRSTOR. (The FXSAVE instruction writes the current
state of the x87 FPU, MMX technology, Streaming SIMD Extensions, and
Streaming SIMD Extensions 2 data, control, and status registers to the
destination operand. The destination is a 512-byte memory location.
FXRSTOR will restore the state saves)."

dts is your digital thermal sensor, which is irrelevant.

mca is "Machine Check Architecture." No clue.

This is from http://blog.hbcom.info/archives/152/.

Your testing thus suggests that fxsr is really important, and we
should be explicitly checking for it and not allowing Sage to run if
the user doesn't have it. Also, we should look to see what part(s) of
sage actually use it.

I've made a trac ticket for this:
http://trac.sagemath.org/sage_trac/ticket/5998

> The result seams to be independent from SP2 or SP3.
>
> Maybe it would be a good idea to compile Sage without the sse2 flag
> (whatever it is...)
>
> Hopefully it helps.
> Gemili
>
> >
>

[gemili]

I could solve the problem with a hint given by Prof. William Stein in
another discussion (just do a search for "cd /usr/local; rm -rf
sage"). The solution is to compile the sage source code within VMware
player on my own computer. I added line 0, 6 and 7 and changed some
comments:

0. Type "manage" and then "sudo su" to become "root".
1. Delete /usr/local/sage by typing:
cd /usr/local; rm -rf sage
2. Download sage-3.4.2.tar by typing :
wget http://sagemath.org/src/sage-3.4.2.tar
3. Extract it by typing:
tar xvf sage-3.4.2.tar
4. Move it to be /usr/local/sage by typing:
mv sage-3.4.2 sage
5. Start the compiling process by typing:
cd sage; make
6. Wait several hours.
7. When it's done, you might remove the souce code (I didn't test
this):
rm sage-3.4.2.tar

The "make" command run about 6 hours to compile on my 1.4 GHz
computer. Now sage-3.4.2 runs perfekt on the above mentioned five year
old "Fujitsu-Siemens Livebook C1110D"

Wouldn't it be a good idea to distribute SAGE in two versions
including a second one beeing compiled on a not so new comuter without
all those fixsr, sse2 flags. This second version might not run as fast
as the first one, but it will work. Or, (even if I don't know a lot
about UNIX,) I think that it should be possible to run the "make"
command with some options excluding the use of the problematic flags
to produce a more stable code even on a new computer (but I'm not
sure). Or I might support the project compiling the second version on
my computer.

But for now I'm happy. Thank you for helping!
Gemili

[mabshoff]

On May 6, 11:26 am, William Stein <wst...@gmail.com> wrote:
> On Wed, May 6, 2009 at 7:01 AM, gemili <j...@gmx.de> wrote:

<SNIP>

> Your testing thus suggests that fxsr is really important, and we
> should be explicitly checking for it and not allowing Sage to run if
> the user doesn't have it.  Also, we should look to see what part(s) of
> sage actually use it.
>
> I've made a trac ticket for this:
>    http://trac.sagemath.org/sage_trac/ticket/5998

No, the problem is not fxsr IMHO as it predates SSE2 (I think it has
been around 10+ years, but I cannot find a reference). The fix here is
plainly and simple to compile MPIR with the appropriate flags since as
is MPIR is build for a Nehalem and it is absolutely no surprised that
Sage blows up spectacularly on older CPUs. So far ATLAS's SSE3
instructions always caught the problem since ATLAS is loaded before
MPIR (due to load order of extensions), so once we fixed the SSE3
problem we get hit by the next one. And no, the problem in MPIR isn't
SSE instructions per se - at least my detection script did not find
anything.

And I doubt we will ever build a pre-SSE2 binary, even for x86, due to
lack of hardware. In theory you could fudge with the build system, but
the effort is in no relationship to the benefit. And performance for
some things would be disastrous. Obviously if someone wants to do it I
am happy to review patches ;). If your system is that old just used a
Sage server somewhere else. This is obviously a problem if you don't
have net or it is too expensive. But in that case you just have to do
the painful build from source.

Cheers,

Michael

[ccandide]

I'm not very lucky with the Sage software : binaries don't work under
Ubuntu (cf. my recent post on this forum) and, on the other and, under
Windows XP, I'm experimenting exactly the same problem as above. More,
under Ubuntu, sources don't compile without error. So I even cannot
try Sage, whatever the OS is, very frustrating :( and consequently I
keep using Maple ...


My machine is old but wide-spread Dell-Optiplex GX-240 with Pentium IV
1.60GHz processor + 512 MB ram running under Windows XP SP3 and Ubuntu
Hardy Heron.