At the risk of sounding in inappropriately (again), I wanted to
reiterate that the bug report I filed was when I tried to update my
Pentium M ThinkPad from Ubuntu 12.04 to 12.04.3 / 12.04.4.
That was where I created unmet dependencies and hosed my upgrade
manager until I undid via the Synaptic Package Manager.
Neither in the read me nor on any of the above pages did I understand
that I should not do such an upgrade on a notebook with non-PAE
processor. Also, as I was trying to perform the update, I did not get
an error message until the upgrade was partially complete.
Will the work done help people like me, those with a non-PAE processor
who try to upgrade to a more current version of the 12.04 LTS?
Again, I want to repeat how much respect and appreciation I have for
the work you folks do.
-F. Stephen Costa
On Thu, Mar 6, 2014 at 12:48 AM, Chris Bainbridge
<email address hidden> wrote:
> I added some text about Pentium M to
> https://help.ubuntu.com/community/EnablingPAE . There is now some
> overlap with https://help.ubuntu.com/community/PAE - they pages could
> probably do with being merged and cleaned up.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1280638).
> https://bugs.launchpad.net/bugs/1160346
>
> Title:
> do-release-upgrade from Ubuntu 12.04 on Pentium-M fails, breaks system
> without any warning (This kernel does not support a non-PAE CPU)
>
> Status in Ubuntu Release Upgrader:
> New
> Status in "linux" package in Ubuntu:
> Invalid
> Status in "ubuntu-release-upgrader" package in Ubuntu:
> Fix Released
>
> Bug description:
> Attempting to upgrade from Precise with a non-PAE kernel will result
> in a failed upgrade. do-release-upgrade should check whether the user
> is using a non-PAE kernel and refuse to run, rather than upgrading to
> a broken system with no installed kernel.
>
> After downloading 1.5GB+ of data and over 1000 new packages, the
> upgrade will eventually report failure. Looking through the logs there
> is no kernel installed because of the error "This kernel does not
> support a non-PAE CPU.":
>
> Selecting previously unselected package linux-image-3.5.0-26-generic.^M
> Unpacking linux-image-3.5.0-26-generic (from .../linux-image-3.5.0-26-generic_3.5.0-26.42_i386.deb) ...^M
> This kernel does not support a non-PAE CPU.^M
> dpkg: error processing /var/cache/apt/archives/linux-image-3.5.0-26-generic_3.5.0-26.42_i386.deb (--unpack):^M
> subprocess new pre-installation script returned error exit status 1^M
> No apport report written because MaxReports is reached already
>
> Related bugs:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897786 Kernel is dropping non-PAE flavour
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068862 upgrade from 12.04 to 12.10 on a sans-pae CPU leaves kernel broken
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1160346/+subscriptions
Folks,
At the risk of sounding in inappropriately (again), I wanted to
reiterate that the bug report I filed was when I tried to update my
Pentium M ThinkPad from Ubuntu 12.04 to 12.04.3 / 12.04.4.
http:// askubuntu. com/questions/ 336527/ how-to- upgrade- ubuntu- 12-04-2- 12-04-3- to-12-04- 4-the-next- hardware- enablement/ 417581# 417581
http:// www.omgubuntu. co.uk/2014/ 02/ubuntu- 12-04-4- released- new-kernel
http:// www.ubuntuask. com/q/answers- why-12- 04-2-to- 12-04-3- didnt-upgrade- kernel- 3-5-3-8- and-or- xorg-368181. html
That was where I created unmet dependencies and hosed my upgrade
manager until I undid via the Synaptic Package Manager.
Neither in the read me nor on any of the above pages did I understand
that I should not do such an upgrade on a notebook with non-PAE
processor. Also, as I was trying to perform the update, I did not get
an error message until the upgrade was partially complete.
Will the work done help people like me, those with a non-PAE processor
who try to upgrade to a more current version of the 12.04 LTS?
Again, I want to repeat how much respect and appreciation I have for
the work you folks do.
-F. Stephen Costa
On Thu, Mar 6, 2014 at 12:48 AM, Chris Bainbridge /help.ubuntu. com/community/ EnablingPAE . There is now some /help.ubuntu. com/community/ PAE - they pages could /bugs.launchpad .net/bugs/ 1160346 release- upgrader" package in Ubuntu: 3.5.0-26- generic. ^M 3.5.0-26- generic (from .../linux- image-3. 5.0-26- generic_ 3.5.0-26. 42_i386. deb) ...^M apt/archives/ linux-image- 3.5.0-26- generic_ 3.5.0-26. 42_i386. deb (--unpack):^M /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/897786 Kernel is dropping non-PAE flavour /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1068862 upgrade from 12.04 to 12.10 on a sans-pae CPU leaves kernel broken /bugs.launchpad .net/ubuntu- release- upgrader/ +bug/1160346/ +subscriptions
<email address hidden> wrote:
> I added some text about Pentium M to
> https:/
> overlap with https:/
> probably do with being merged and cleaned up.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1280638).
> https:/
>
> Title:
> do-release-upgrade from Ubuntu 12.04 on Pentium-M fails, breaks system
> without any warning (This kernel does not support a non-PAE CPU)
>
> Status in Ubuntu Release Upgrader:
> New
> Status in "linux" package in Ubuntu:
> Invalid
> Status in "ubuntu-
> Fix Released
>
> Bug description:
> Attempting to upgrade from Precise with a non-PAE kernel will result
> in a failed upgrade. do-release-upgrade should check whether the user
> is using a non-PAE kernel and refuse to run, rather than upgrading to
> a broken system with no installed kernel.
>
> After downloading 1.5GB+ of data and over 1000 new packages, the
> upgrade will eventually report failure. Looking through the logs there
> is no kernel installed because of the error "This kernel does not
> support a non-PAE CPU.":
>
> Selecting previously unselected package linux-image-
> Unpacking linux-image-
> This kernel does not support a non-PAE CPU.^M
> dpkg: error processing /var/cache/
> subprocess new pre-installation script returned error exit status 1^M
> No apport report written because MaxReports is reached already
>
> Related bugs:
>
> https:/
> https:/
>
> To manage notifications about this bug go to:
> https:/