Ubuntu
update-manager package

Same distro release, different kernel versions?

Asked by keepitsimpleengr

Same distro release, different kernel versions?

I have a 10.10 64bit workstation and a 10.10 64bit HomeTheaterPC.

I keep them both updated regularly using update manager to ensure a mthtc frontend remote client stays compatible. Both have nvidia video adapters. The htpc has AMD and 4GB memory and the wrksta64 has Intel Quad with 8GB memory.

Now they have different kernel versions.

keepitsimpleengr@wrksta64:~$ uname -r
2.6.35-28-generic

keepitsimpleengr@htpc64:~$ uname -r
2.6.35-30-generic

linux-headers-2.6.35-30 and linux-headers-2.6.35-30-generic are installed on wrksta64 but not linux-image-2.6.35-30-generic
All three are installed on htpc64

Both are set for important security and recommended updates only

Why is this? Something wrong?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu update-manager Edit question
Assignee:
No assignee Edit question
Solved by:
keepitsimpleengr
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Can you give the output of:

uname -a

On both

Thanks

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) said : 		#2

⋯@htpc64:~$ uname -a
Linux htpc64 2.6.35-30-generic #54-Ubuntu SMP Tue Jun 7 18:41:54 UTC 2011 x86_64 GNU/Linux
⋯@wrksta64:~$ uname -a
Linux wrksta6 2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64 GNU/Linux

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Can you give the output of:

lsb_release -a

on both too as well as:

apt-cache policy linux-image-generic

on both

Thanks

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) said : 		#4

⋯@wrksta64:~$ lsb_release -a
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 10.10
Release: 10.10
Codename: maverick
⋯@wrksta64:~$ apt-cache policy linux-image-generic
linux-image-generic:
  Installed: (none)
  Candidate: 2.6.35.30.38
  Version table:
     2.6.35.30.38 0
        500 http://mirrors.us.kernel.org/ubuntu/ maverick-updates/main amd64 Packages
        500 http://mirrors.us.kernel.org/ubuntu/ maverick-security/main amd64 Packages
     2.6.35.22.23 0
        500 http://mirrors.us.kernel.org/ubuntu/ maverick/main amd64 Packages

⋯@htpc64:~$ lsb_release -a
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 10.10
Release: 10.10
Codename: maverick
⋯@htpc64:~$ apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 2.6.35.30.38
  Candidate: 2.6.35.30.38
  Version table:
 *** 2.6.35.30.38 0
        500 http://mirrors.us.kernel.org/ubuntu/ maverick-updates/main amd64 Packages
        500 http://mirrors.us.kernel.org/ubuntu/ maverick-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2.6.35.22.23 0
        500 http://mirrors.us.kernel.org/ubuntu/ maverick/main amd64 Packages

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#5

ok then try:

sudo apt-get update; sudo apt-get dist-upgrade

Should be ok

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) said : 		#6

$⋯@htpc64:~$ sudo apt-get update
[sudo] password for ⋯:
Hit http://mirrors.us.kernel.org maverick Release.gpg
Ign http://mirrors.us.kernel.org/ubuntu/ maverick/main Translation-en
Ign http://mirrors.us.kernel.org/ubuntu/ maverick/main Translation-en_US
<⋯snip⋯>
Hit http://packages.medibuntu.org maverick/free amd64 Packages
Hit http://packages.medibuntu.org maverick/non-free amd64 Packages
Ign http://dl.google.com/linux/earth/deb/ stable/main Translation-en
Ign http://dl.google.com/linux/earth/deb/ stable/main Translation-en_US
Get:3 http://dl.google.com stable Release [1,351B]
Get:4 http://dl.google.com stable Release [1,338B]
Get:5 http://dl.google.com stable/main amd64 Packages [1,251B]
Get:6 http://dl.google.com stable/main amd64 Packages [469B]
Fetched 4,805B in 10s (458B/s)
Reading package lists... Done
⋯@htpc64:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#7

On wrksta64 (the machine where the kernel is not updating), run:

sudo apt-get update
sudo apt-get install linux-image-generic

That should fix the problem. If it does not, please post again, with *all* the text from the Terminal. (You can edit out your username as you have been doing, if you wish.)

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) said : 		#8

I forced the kernel update using synaptic.

The question was: why or how could this happen?

Now I verify all kernel updates, but if I knew the reason, I wouldn't have to.

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#9

The general answer, which you already know, is that this happened because linux-image-generic was not installed. If you have now installed linux-image-generic, then this should not happen again. If you have only installed the specific package for the new kernel, whose name is similar to that but has a version number as part of the time, then this *will* happen again.

As for why it was that linux-image-generic was not installed, I don't know. If you want to investigate it, you could examine the logs (/var/log/dpkg.log and the rotated logs /var/log/dpkg.log.1, /var/log/dpkg.log.2.gz and so forth), and search for it.

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#10

Correction: "but has a version number as part of the time" --> "but has a version number as part of the NAME"

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) said : 		#11

This happened again 2011-11-23.

I installed linux-image-generic.

The update then occurred as expected.

I searched dpkp.log. I discovered this:

:/var/log# cat dpkg.log.12 | grep linux-image-generic
2010-11-25 09:27:41 upgrade linux-image-generic 2.6.35.22.23 2.6.35.23.25
2010-11-25 09:27:41 status half-configured linux-image-generic 2.6.35.22.23
2010-11-25 09:27:41 status unpacked linux-image-generic 2.6.35.22.23
2010-11-25 09:27:41 status half-installed linux-image-generic 2.6.35.22.23
2010-11-25 09:27:41 status half-installed linux-image-generic 2.6.35.22.23
2010-11-25 09:27:41 status unpacked linux-image-generic 2.6.35.23.25
2010-11-25 09:27:41 status unpacked linux-image-generic 2.6.35.23.25
2010-11-25 09:29:08 configure linux-image-generic 2.6.35.23.25 2.6.35.23.25
2010-11-25 09:29:08 status unpacked linux-image-generic 2.6.35.23.25
2010-11-25 09:29:08 status half-configured linux-image-generic 2.6.35.23.25
2010-11-25 09:29:09 status installed linux-image-generic 2.6.35.23.25
2010-11-25 09:53:41 status installed linux-image-generic 2.6.35.23.25
2010-11-25 09:53:41 remove linux-image-generic 2.6.35.23.25 2.6.35.23.25
2010-11-25 09:53:41 status half-configured linux-image-generic 2.6.35.23.25
2010-11-25 09:53:41 status half-installed linux-image-generic 2.6.35.23.25
2010-11-25 09:53:41 status config-files linux-image-generic 2.6.35.23.25
2010-11-25 09:53:41 status config-files linux-image-generic 2.6.35.23.25
2010-11-25 09:53:41 status config-files linux-image-generic 2.6.35.23.25
2010-11-25 09:53:41 status not-installed linux-image-generic <none>