aims team mailing list archive

[Doug Coulter <dcfusor@xxxxxxxxx>]

I tried that too, no good (4.2.x, using the directions on the oracle site -
these are a little different, so something new to try) but I've not tried
every possible combination yet - only about 10 permutations so far
(speaking of frustration).  When I tried the -proposed, it took the stuff
straight from oracle out and substituted 4.1.x during the install process.
I'd been doing the straight from oracle thing on 10.04 mostly, but not
upgrading everytime it asked, since that was causing my win-7 DRM to kick
in (till I got and used a key-cracker).  That stank as I've paid for win7
twice and couldn't even run it at all after I upgraded VB - it detected a
"hardware change" on the upgrade and decided I'd stolen it.
So now I AM running a stolen iso with a key cracker, once, to get what I
paid for twice, on the 5-6 machines that *do not* run 12.04.  Last night
the 12,.04 machine grabbed a new kernal, so now I get to try all this again
I suppose, but for now - it still does not work and even crashes linux back
to bios, with the usual bad effects on things like mail and web program
context for unexpected crashes (my own running code doesn't have issues
with sudden crashes since I wrote it with that expectation, it's an edge
case that gets hit here due to arcs in nearby HV supplies).  Ugh.

To clarify - the other above suggestions did let me install VB "at all",
and import an image - but all images crash during boot, before the main
screen shows up, usually.  I once had win7 show me the login, but logging
in - boom, it crashed, then linux went down.

Could it matter that since I have plenty ram (8g) for what I use this for,
I didn't put in a swap partition?  I've never had an issue with that
before, other than the linux install kinda whining when I don't.  Since I'm
running a combo of SSD and spinner - I put / on the SSD, but /home and /tmp
on a spinner to prolong SSD life.

Doug


On Tue, Apr 9, 2013 at 5:56 AM, Tim Edwards <1081307@xxxxxxxxxxxxxxxxxx>wrote:

> @Doug I've had a good experience with uninstalling Virtualbox packages
> that come from the Ubuntu repositories and instead getting Virtualbox
> directly from virtualbox.org's repository for Ubuntu.
>
> Instructions: http://www.itworld.com/virtualization/308757/install-
> virtualbox-424-ubuntu-1204-or-1210
>
> Works well for me even on 12.04.2 with the new kernel and it means you
> always have the latest Virtualbox version.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1165520).
> https://bugs.launchpad.net/bugs/1081307
>
> Title:
>   virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
>   failed to build [merge request]
>
> Status in “virtualbox” package in Ubuntu:
>   Fix Released
> Status in “virtualbox” source package in Precise:
>   Fix Committed
> Status in “virtualbox” source package in Quantal:
>   Fix Released
> Status in “virtualbox” source package in Raring:
>   Fix Released
>
> Bug description:
>   I'm using aptitude as a packet manager.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 12.04
>   Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
>   ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
>   Uname: Linux 3.5.0-26-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.0.1-0ubuntu15
>   Architecture: amd64
>   DKMSKernelVersion: 3.5.0-18-generic
>   Date: Tue Nov 20 23:13:23 2012
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
>   MarkForUpload: True
>   PackageArchitecture: all
>   PackageVersion: 4.1.12-dfsg-2ubuntu0.2
>   SourcePackage: virtualbox
>   Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
> failed to build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
>   [Impact]
>   Users are not able to use virtualbox from the repository on 12.04 with
> 3.5 kernel. It is totally broken.
>   The patch proposed backports only the relevant parts from upstream to
> fix the bug.
>   The patch is from: https://www.virtualbox.org/changeset/41660/vbox
>
>   [Test Case]
>   Upgrade to 3.5 kernel on 12.04 and install virtualbox.
>
>   [Development Fix]
>   Fixed during Quantal cycle.
>
>   [Stable Fix]
>   Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.
>
>   [Regression Potential]
>   It is best to use the latest upstream version. But since that will cause
> major disruption, we have to track this package and corresponding bugs for
> regressions.
>
>   jamespage: Please also check backwards compatibility with the 3.2
>   kernel; the patch should support this but best to make sure (not all
>   12.04 installs with have 3.5).
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions
>


-- 
Why guess when you can know.  Measure!

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to a duplicate bug report (1126315).
https://bugs.launchpad.net/bugs/1081307

Title:
  virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
  failed to build [merge request]

Status in “virtualbox” package in Ubuntu:
  Fix Released
Status in “virtualbox” source package in Precise:
  Fix Committed
Status in “virtualbox” source package in Quantal:
  Fix Released
Status in “virtualbox” source package in Raring:
  Fix Released

Bug description:
  I'm using aptitude as a packet manager.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  DKMSKernelVersion: 3.5.0-18-generic
  Date: Tue Nov 20 23:13:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  MarkForUpload: True
  PackageArchitecture: all
  PackageVersion: 4.1.12-dfsg-2ubuntu0.2
  SourcePackage: virtualbox
  Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]
  Users are not able to use virtualbox from the repository on 12.04 with 3.5 kernel. It is totally broken.
  The patch proposed backports only the relevant parts from upstream to fix the bug.
  The patch is from: https://www.virtualbox.org/changeset/41660/vbox

  [Test Case]
  Upgrade to 3.5 kernel on 12.04 and install virtualbox.

  [Development Fix]
  Fixed during Quantal cycle.

  [Stable Fix]
  Is being fixed in 4.1.12-dfsg-2ubuntu0.3 upload to precise-proposed.

  [Regression Potential]
  It is best to use the latest upstream version. But since that will cause major disruption, we have to track this package and corresponding bugs for regressions.

  jamespage: Please also check backwards compatibility with the 3.2
  kernel; the patch should support this but best to make sure (not all
  12.04 installs with have 3.5).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions