|
Debian kernel not detected
I am getting following error when running smxi:
:: Code :: Calculating latest Debian kernel version...
Error: the kernel package linux-image-amd64 has no installation candidate. Setting kernel version to null for the debian kernel type. Back to top |
|
do: apt-cache policy linux-image-amd64
i assume this is a 64 bit system. I see that package in debian testing/sid. Back to top |
|
:: Code :: ckosloff@papimalo:~$ apt-cache policy linux-image-amd64
linux-image-amd64: Installed: (none) Candidate: 3.2+46 Version table: 3.10+51~bpo70+1 0 100 http://ftp.debian.org/debian/ wheezy-backports/main amd64 Packages 3.2+46 0 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages 500 http://http.us.debian.org/debian/ wheezy/main amd64 Packages Hi techadmin, Thanks for answer. This system is on wheezy stable + backports so no package here. I read in Synaptic that linux-image-amd64 is a metapackage. :: Quote :: This package depends on the latest Linux kernel and modules for use on PCs with AMD64 or Intel 64 processors.So, yes, it should not be found in stable repo, but why does smxi report error? Just trying to improve this great script. Back to top |
|
I cant' say, show me the output of:
apt-cache show linux-image-amd64 This is what smxi uses to calculate the latest kernel version available. It is precisely because it is a metapackage that it is able to do this, since apt-cache show shows the script what the actual kernel dependency is, which then tells smxi what the latest kernel is. I'd have to feed smxi that exact output you get to see what is wrong. I'm assuming, of course, that you have an active internet connection and that nothing else is wrong or out of place in the system. also, use pastebin.com and paste the entire /var/log/smxi.log file and then copy the url to that paste here so I can see if anything odd is going on. Back to top |
|
pastebin.com/MrYrwvAj
That's the smxi log. Now, the output of apt-cache show linux-image-amd64 :: Code ::
ckosloff@papimalo:~$ apt-cache show linux-image-amd64 Package: linux-image-amd64 Source: linux-latest (51~bpo70+1) Version: 3.10+51~bpo70+1 Installed-Size: 37 Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org> Architecture: amd64 Provides: linux-latest-modules-3.10-0.bpo.2-amd64 Depends: linux-image-3.10-0.bpo.2-amd64 Description-en: Linux for 64-bit PCs (meta-package) This package depends on the latest Linux kernel and modules for use on PCs with AMD64, Intel 64 or VIA Nano processors. . This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. Description-md5: 273d1b43f376fdf9893fad396f2ed5f1 Section: kernel Priority: extra Filename: pool/main/l/linux-latest/linux-image-amd64_3.10+51~bpo70+1_amd64.deb Size: 5820 MD5sum: 08a058aaa9cb771eb1222ef2dc18413d SHA1: 9eff0ded6129bc5fa00075a7979c92784fa04dc6 SHA256: d36822ab1beae23612a485d4d3af18cc6da725dc56d84388e39f4b97b2699916 Package: linux-image-amd64 Source: linux-latest (46) Version: 3.2+46 Installed-Size: 5 Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org> Architecture: amd64 Provides: linux-latest-modules-3.2.0-4-amd64 Depends: linux-image-3.2.0-4-amd64 Description-en: Linux for 64-bit PCs (meta-package) This package depends on the latest Linux kernel and modules for use on PCs with AMD64 or Intel 64 processors. . This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. Description-md5: 31d755b9476c7e69a9867ee7852a2e51 Section: kernel Priority: optional Filename: pool/main/l/linux-latest/linux-image-amd64_3.2+46_amd64.deb Size: 5630 MD5sum: 40f61ec0077e223da12da5fd12675ab3 SHA1: 419acd7805cfd9f2ff95cc57c0441796d0656162 SHA256: 846acdae7fc848fc8ea305a06816c8b1a6950fc3dbcdb9298160f01c18d0d5c4 ckosloff@papimalo:~$ Thanks for answer Back to top |
|
my guess is that bpo in the linux image package name isn't handled by smxi, let's see.
Back to top |
|
show this:
apt-cache policy linux-image-3.10-0.bpo.2-amd64 smxi is getting the kernel version the meta package points to, but when it is checking for that package availability it's showing as not available. This is probably caused by something in how debian handles backports, ie, only packages from the main repo of stable are showing as candidates in apt unless you force the install via a direct override command, but showing apt-cache policy for that package will show it clearly I believe, that is the test smxi uses. My guess is it should show something unusual, but I'll wait to see the output. Back to top |
|
:: Code ::
ckosloff@papimalo:~$ apt-cache policy linux-image-3.10-0.bpo.2-amd64 linux-image-3.10-0.bpo.2-amd64: Installed: (none) Candidate: 3.10.5-1~bpo70+1 Version table: 3.10.5-1~bpo70+1 0 100 http://ftp.debian.org/debian/ wheezy-backports/main amd64 Packages ckosloff@papimalo:~$ Thanks for answer Back to top |
|
so I guess debian stable ignores packages in the backports repo in terms of what apt itself sees.
smxi, however, when it gets multiple responses for kernel version from apt-cache show will pick the one that is highest, ie, latest, to use, that's to avoid multiple kernel images being tested as one package. So basically smxi appears to be working fine, as expected, you just found a case where it won't work. There may be a command to get apt-cache to use backports data, I have never used that much, once or twice, but not enough to learn the intracies of the stuff. Basically, to confirm this, do: apt-get update then do: apt-cache show linux-image-amd64 then find the item for the backports kernel, find what linux-image version it depends on, then do: apt-cache policy linux-image-<the rest of the linux image package name> then if you see nothing, that means smxi also sees nothing. The item under the number 100 means installed on your local system, but present in apt in that form, smxi ignores that since it's not in the actual package pool data, just locally installed. If you see either nothing or 100 then smxi could not get that data, that's what it looks like is happening to me, because in the logs, each time it checked the linux image package specifically, it got the message that it was no in apt-cache database, ie, the package does not as far as apt is concerned exist. My guess backports, to avoid errors in installs, only installs when explicitly told to do so, like apt-get -t wheezy-backports install <package> that's a guess, but that's what it looks like, and apt-cache just ignores the backports completely unless you set it maybe use it first, but that means all packages in backports would replace the stable ones, easy to see why they do not do that. Back to top |
|
:: Code ::
Reading package lists... Done root@papimalo:/home/ckosloff# apt-cache show linux-image-amd64 Package: linux-image-amd64 Source: linux-latest (51~bpo70+1) Version: 3.10+51~bpo70+1 Installed-Size: 37 Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org> Architecture: amd64 Provides: linux-latest-modules-3.10-0.bpo.2-amd64 Depends: linux-image-3.10-0.bpo.2-amd64 Description-en: Linux for 64-bit PCs (meta-package) This package depends on the latest Linux kernel and modules for use on PCs with AMD64, Intel 64 or VIA Nano processors. . This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. Description-md5: 273d1b43f376fdf9893fad396f2ed5f1 Section: kernel Priority: extra Filename: pool/main/l/linux-latest/linux-image-amd64_3.10+51~bpo70+1_amd64.deb Size: 5820 MD5sum: 08a058aaa9cb771eb1222ef2dc18413d SHA1: 9eff0ded6129bc5fa00075a7979c92784fa04dc6 SHA256: d36822ab1beae23612a485d4d3af18cc6da725dc56d84388e39f4b97b2699916 Package: linux-image-amd64 Source: linux-latest (46) Version: 3.2+46 Installed-Size: 5 Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org> Architecture: amd64 Provides: linux-latest-modules-3.2.0-4-amd64 Depends: linux-image-3.2.0-4-amd64 Description-en: Linux for 64-bit PCs (meta-package) This package depends on the latest Linux kernel and modules for use on PCs with AMD64 or Intel 64 processors. . This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. Description-md5: 31d755b9476c7e69a9867ee7852a2e51 Section: kernel Priority: optional Filename: pool/main/l/linux-latest/linux-image-amd64_3.2+46_amd64.deb Size: 5630 MD5sum: 40f61ec0077e223da12da5fd12675ab3 SHA1: 419acd7805cfd9f2ff95cc57c0441796d0656162 SHA256: 846acdae7fc848fc8ea305a06816c8b1a6950fc3dbcdb9298160f01c18d0d5c4 root@papimalo:/home/ckosloff# This is what I get after apt-get update. As you can see it depends on two different kernels, I use linux-image-3.2.0-4-amd64. And here is what I get after :: Code ::
root@papimalo:/home/ckosloff# apt-cache policy linux-image-3.2.0-4-amd64 linux-image-3.2.0-4-amd64: Installed: 3.2.46-1 Candidate: 3.2.46-1 Version table: *** 3.2.46-1 0 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages 500 http://http.us.debian.org/debian/ wheezy/main amd64 Packages 100 /var/lib/dpkg/status 3.2.41-2+deb7u2 0 500 http://security.debian.org/ wheezy/updates/main amd64 Packages root@papimalo:/home/ckosloff# Back to top |
|
All times are GMT - 8 Hours |