Ubuntu 12.04.1-AMD64-desktop installed from alternate-CD

[Andreas Glaeser]

The normal installation-method did not work on this PC in 64-bit mode, installation from the live-CD environment failed, too.
So I downloaded the alternate-desktop CD, which did the job, but clearly not too well, because problems occured, which were reported anonymously, automatically.
In my opinion the packages 'cpufreqd' and 'cpufrequtils' should be installed automatically by defaullt for 64-bit architecture, because very most of these computers actually do support cpu-frequency-scaling and it can save some electrical energy, even when it does not work too effectively. cpufreqd was not configured correctly either, so I file a separate bugreport against the 'cpufreqd'-package.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: installation-report 2.46ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Sun Sep 16 16:34:47 2012
Dependencies:

InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: installation-report
UpgradeStatus: No upgrade log present (probably fresh install)

[Andreas Glaeser (aglaeser1)]

The attached picture shows the screen when the installation process hung from live-CD-environment. The standard-installation-method failed when the system tried to configure apt and hung, too, at this point.

[Dimitri John Ledkov (xnox)]

Invalid OPCODE is a linux kernel issue. What type of CPU do you have?

[Andreas Glaeser (aglaeser1)]

It is an AMD Athlon 64 x2 CPU @ 2 GHz, I do not know if it matters, but actually the installation itself was done with an Athlon 64 X2e , 45 W @ 2,5 GHz. It did not work in the expected way, did not really save any additional energy, so I decided to reinsert the original 2GHz-CPU.
You can get more info from the closed Debian-installation-report from the same machine here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685127