On 16/11/14 14:39, Andrew McRae wrote:
On 16 November 2014 14:22, Rathgeber, Florian <florian.rathgeber@imperial.ac.uk <mailto:florian.rathgeber@imperial.ac.uk>> wrote:
[Please keep list in CC]
On 16/11/14 14:12, Lee, Suet wrote: > Not sure if I'm doing it correctly but I tried this: > > mosh@ubuntu:~$ dpkg -s mpich2 > dpkg-query: package 'mpich2' is not installed and no information is > available > Use dpkg --info (= dpkg-deb --info) to examine archive files, > and dpkg --contents (= dpkg-deb --contents) to list their contents. > > So the problem isn't down to mpich2?
Sorry, the package you want to look for is libmpich-dev
Is there any reason to use a 32bit system? We explicitly do *not* support 32bit systems and there isn't really a reason not to use 64bit.
Ah, I wasn't aware of this.
Context:Suet got the following error when she tried powering up a 64bit VM, a couple of months ago:
"This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible. This host does not support Intel VT-x. For more detailed information, see http://vmware.com/info?id=152." [The graphics problem was something different]
I guessed that pointing her at the 32bit Ubuntu iso would be easier than making BIOS changes (assuming her processor does support VT-x, but that it's disabled in BIOS).
Exactly, see my other answer :)
Florian: do you think the problem is related to 32bit-ness? If so, Suet can bring her laptop to Huxley or WPL some time this week and we'll go the 64bit route.
I'm not sure, I suspect not, but then I have no experience on 32bit systems (last time I used a 32bit system was 2009). Florian
Andrew
Florian
> Suet