TWO kernels in one update?

Micronaut · 2020-02-10 21:16:20

It's time to get my Linux boxes updated, and the one I've started with is downloading TWO kernel updates. ??? Why would this happen? I admit I'm not checking very frequently for updates. Maybe every couple weeks. Could the release of one kernel update right after another cause both to be downloaded? Or would something else make this happen?

Head_on_a_Stick · 2020-02-11 06:04:22

Can you post the actual command output? Or the APT history that shows the problem?

How about:

aptitude search '?narrow(?installed, linux-image)'

EDIT: use aptitude's search terms instead of piping to grep.

Last edited by Head_on_a_Stick (2020-02-12 20:30:50)

ToxicExMachina · 2020-02-11 11:50:02

Which kernel updates you have downloaded? I think you installed two kernels before.

Micronaut · 2020-02-12 19:18:06

Well, this is getting weirder. First:

i A linux-image-4.9.0-11-amd64 - Linux 4.9 for 64-bit PCs
i A linux-image-4.9.0-6-amd64 - Linux 4.9 for 64-bit PCs
i A linux-image-4.9.0-9-amd64 - Linux 4.9 for 64-bit PCs
i linux-image-amd64 - Linux for 64-bit PCs (meta-package)

There are THREE images showing as installed, besides the meta-package. But beyond that, I checked for new updates again and there is ANOTHER linux-image available for my machine. Maybe this is a correction for the mistake that resulted in multiple install entries?

Micronaut · 2020-02-12 19:22:13

Ack! Updating has added another line to the list!

i A linux-image-4.9.0-11-amd64 - Linux 4.9 for 64-bit PCs
i A linux-image-4.9.0-12-amd64 - Linux 4.9 for 64-bit PCs
i A linux-image-4.9.0-6-amd64 - Linux 4.9 for 64-bit PCs
i A linux-image-4.9.0-9-amd64 - Linux 4.9 for 64-bit PCs
i linux-image-amd64 - Linux for 64-bit PCs (meta-package)

WTF is going on???

Head_on_a_Stick · 2020-02-12 19:29:35

You have a metapackage (linux-image-amd64, to keep the kernel updated) and four different ABI versions.

Run

# aptitude purge linux-image-4.9.0-{6,9,11}-amd64

To get rid of the old ABI versions.

See also https://kernel-team.pages.debian.net/ke … sions.html

EDIT: better link.

EDIT2: I can't count...

Last edited by Head_on_a_Stick (2020-02-12 19:32:44)

Head_on_a_Stick · 2020-02-12 20:38:11

I think you have the proposed-updates repository enabled, are you sure that's what you want? Those packages can be buggy.

Devuan beowulf's current ABI is 4.19.0-8: https://pkginfo.devuan.org/stage/beowul … b10u3.html

Micronaut · 2020-02-12 20:59:56

OK, I removed those from one system but now that system cannot connect to anything online. It's like the network driver or DNS or something is broken. This latest update has apparently broken something. I'll definitely wait before updating the others....

Proposed repositories? What are those? The only thing remotely experimental in my sources.list is backports. Do they put kernels into backports? Should I roll back somehow?

deb http://deb.devuan.org/merged ascii contrib main non-free
deb http://deb.devuan.org/merged ascii-updates contrib main non-free
deb http://deb.devuan.org/merged ascii-security contrib main non-free
deb http://deb.devuan.org/merged ascii-backports contrib main non-free

Micronaut · 2020-02-12 21:27:54

Hmm, I've still got:

linux-image-amd64_4.9+80+deb9u9_amd64.deb
linux-headers-amd64_4.9+80+deb9u9_amd64.deb

In my apt archives directory, but can't figure out how to re-install it.

Micronaut · 2020-02-12 22:28:35

Actually, I have to wonder if it was the kernel the broke my network. Here is the log of the upgrade that broke the system. MANY things were changed:

Start-Date: 2020-02-12 14:19:07
Install: linux-headers-4.9.0-12-common:amd64 (4.9.210-1, automatic), linux-image-4.9.0-12-amd64:amd64 (4.9.210-1, automatic), linux-headers-4.9.0-12-amd64:amd64 (4.9.210-1, automatic)
Upgrade: perl-base:amd64 (5.24.1-3+deb9u5, 5.24.1-3+deb9u6), libopenjp2-7:amd64 (2.1.2-1.1+deb9u3, 2.1.2-1.1+deb9u4), libcups2:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), linux-libc-dev:amd64 (4.9.189-3+deb9u2, 4.9.210-1), libjaxen-java:amd64 (1.1.6-1, 1.1.6-1+deb9u1), perl-modules-5.24:amd64 (5.24.1-3+deb9u5, 5.24.1-3+deb9u6), cups-server-common:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), linux-compiler-gcc-6-x86:amd64 (4.9.189-3+deb9u2, 4.9.210-1), cups-common:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), libpq5:amd64 (9.6.15-0+deb9u1, 9.6.16-0+deb9u1), libperl5.24:amd64 (5.24.1-3+deb9u5, 5.24.1-3+deb9u6), cups-ppdc:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), libcupsmime1:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), linux-image-amd64:amd64 (4.9+80+deb9u9, 4.9+80+deb9u10), libglib2.0-bin:amd64 (2.50.3-2+deb9u1, 2.50.3-2+deb9u2), linux-headers-amd64:amd64 (4.9+80+deb9u9, 4.9+80+deb9u10), linux-kbuild-4.9:amd64 (4.9.189-3+deb9u2, 4.9.210-1), libglib2.0-data:amd64 (2.50.3-2+deb9u1, 2.50.3-2+deb9u2), libtimedate-perl:amd64 (2.3000-2, 2.3000-2+deb9u1), libmariadbclient18:amd64 (10.1.41-0+deb9u1, 10.1.44-0+deb9u1), libcupsppdc1:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), libidn11:amd64 (1.33-1, 1.33-1+deb9u1), libfreetype6:amd64 (2.6.3-3.2, 2.6.3-3.2+deb9u1), perl:amd64 (5.24.1-3+deb9u5, 5.24.1-3+deb9u6), cups-bsd:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), cups-core-drivers:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), cups-daemon:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), libcupsimage2:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), cups:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), libcupscgi1:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), cups-client:amd64 (2.2.1-8+deb9u4, 2.2.1-8+deb9u5), libglib2.0-0:amd64 (2.50.3-2+deb9u1, 2.50.3-2+deb9u2), libxslt1.1:amd64 (1.1.29-2.1+deb9u1, 1.1.29-2.1+deb9u2)
End-Date: 2020-02-12 14:20:13

Head_on_a_Stick · 2020-02-13 06:17:26

Sorry Micronaut, my dyslexia is playing up again — I read "4.9" as "4.19", you have the correct kernel version for ASCII.

For your networking problem check the output of rfkill, there have been a couple of threads involving that recently.

rolfie · 2020-02-13 10:33:55

Got two PC running ASCII with backports kernel 4.19.6, 4.9.12 also is installed as backup, no network issues since the ASCII installation about two years ago. I have wired GBit lan here. Basically the same sources.list entries here.

What exactly is your setup? Wifi? Can you try wired network?

Regards, rolfie

Last edited by rolfie (2020-02-13 10:34:55)

Micronaut · 2020-02-13 21:37:31

The system having the problems is a desktop, no wifi involved. I simply downloaded updates using the above sources.list, "aptitude update" and then "aptitude safe-upgrade" and the network stopped working. The log posted above is all of the packages installed by that update. Looks like a lot of CUPS updates. But the only thing I can figure has anything to do with network access is the kernel. Hmm...

rolfie · 2020-02-13 22:10:28

Well, I just recently had a case with my wifes desktop where also the network stopped working, the onBoard Realtek chip went bad. Indication was that the usual lights for speed and activity did no more work.

I put in EE1000 card I had laying around, and the network was up again.

Consider such a scenario.

Good luck, rolfie

Micronaut · 2020-02-13 22:30:07

All I have to do is reboot into Windows and there are no network problems. Something in the Linux updates broke my networking. Which is really shocking. Bad updates are supposed to be a Windows thing...

Micronaut · 2020-02-13 23:20:01

Alright, I give up. Since I don't have access to the network anymore, I can't get the files I deleted to try again. Looks like I have no option but a complete re-install when I have some time. This is the first time I have had such a debacle with Linux. But if I re-install and updating breaks my networking again, what then?

fsmithred · 2020-02-14 02:26:30

dpkg -i /var/cache/apt/archives/linux-image*.deb

Micronaut · 2020-02-14 02:42:36

That would install all of the kernels in the directory. Sounds messy.

Fortunately, after some more struggles I figured out what was wrong. The resolv.conf file was set read-only even for root, and contained only 127.0.0.1 as the nameserver. Well, whatever was in those latest updates broke dnssec-trigger. I don't know enough about it to say what exactly went wrong. When unbound stopped working, it prevented any network access from working since all applications would think that 127.0.0.1 was the place to request DNS information. When I finally figured out how to free resolv.conf (it was a completely different file control system than chmod, something I've never heard of before "chattr") it returned to the control of network manager and the system is usable again.

So now it looks like dnssec-trigger is not safe to use since these updates broke it. I'll have to remove it from all my systems and continue trying to figure out how to setup unbound independently.

Head_on_a_Stick · 2020-02-14 05:57:43

Sorry for the trouble, I presumed you had tested the new kernel before attempting to remove the old versions.

Use apt to re-install the old kernel versions:

cd /var/cache/apt/archives
sudo apt install ./name_of_old_kernel_version.deb

^ That will downgrade automatically.

Micronaut wrote:

it was a completely different file control system than chmod, something I've never heard of before "chattr"

You did that yourself, Devuan ASCII doesn't have dnssec-trigger installed by default and /etc/resolv.conf is not set immutable.

Micronaut · 2020-02-14 15:20:31

No, I didn't even know the immutable attribute existed until I figured out how to remove it. Something else set it. And that was a peripheral problem. The real problem is that dnssec-trigger doesn't work anymore. DNS info is not looked up and the machine cannot use the network with it installed. Something in the batch of updates I downloaded broke it.

Head_on_a_Stick · 2020-02-14 18:45:17

Micronaut wrote:

No, I didn't even know the immutable attribute existed until I figured out how to remove it. Something else set it

You must have blindly copy&pasted some forum suggestion, no De??an package would use such an awful hack.

Micronaut wrote:

The real problem is that dnssec-trigger doesn't work anymore. DNS info is not looked up and the machine cannot use the network with it installed. Something in the batch of updates I downloaded broke it.

You should probably open a new thread for that problem, dnssec-trigger & unbound should work just fine.

Micronaut · 2020-02-16 00:25:00

Maybe Devan would not, but the dnssec-trigger package comes from nlnet labs, and they would:

https://www.nlnetlabs.nl/projects/dnssec-trigger/about/

There used to be a race condition between dnssec-trigger and the system but this was fixed in 0.6, with a 'system preferences' override on OSX and Windows, and chattr immutable on Linux and BSD.

Head_on_a_Stick · 2020-02-16 09:07:02

Micronaut wrote:

but the dnssec-trigger package comes from nlnet labs, and they would

Well I've just tried installing the dnssec-trigger package in the Devuan ASCII live environment and it did not set resolv.conf immutable, I was able to alter and delete the file afterwards with the usual root permissions.

Micronaut · 2020-02-17 04:04:52

Well, on my systems (all of them now) is locks resolv.conf and fails to provide the DNS lookups that it has forced the system to ask it for. I've now removed it from all of my systems. It worked for a few days and then went haywire. Frustrating. Hasn't there been a recent update of the "master" signing key? Could that have broken it?

Head_on_a_Stick · 2020-02-17 13:13:16

Please open a new thread for this problem, thanks.

I am absolutely sure that the dnssec-trigger package from Devuan does not set /etc/resolv.conf immutable so please include details of how you installed it and also the full output of apt policy in the new OP.

The officially official Devuan Forum!

#1 2020-02-10 21:16:20

TWO kernels in one update?

#2 2020-02-11 06:04:22

Re: TWO kernels in one update?

#3 2020-02-11 11:50:02

Re: TWO kernels in one update?

#4 2020-02-12 19:18:06

Re: TWO kernels in one update?

#5 2020-02-12 19:22:13

Re: TWO kernels in one update?

#6 2020-02-12 19:29:35

Re: TWO kernels in one update?

#7 2020-02-12 20:38:11

Re: TWO kernels in one update?

#8 2020-02-12 20:59:56

Re: TWO kernels in one update?

#9 2020-02-12 21:27:54

Re: TWO kernels in one update?

#10 2020-02-12 22:28:35

Re: TWO kernels in one update?

#11 2020-02-13 06:17:26

Re: TWO kernels in one update?

#12 2020-02-13 10:33:55

Re: TWO kernels in one update?

#13 2020-02-13 21:37:31

Re: TWO kernels in one update?

#14 2020-02-13 22:10:28

Re: TWO kernels in one update?

#15 2020-02-13 22:30:07

Re: TWO kernels in one update?

#16 2020-02-13 23:20:01

Re: TWO kernels in one update?

#17 2020-02-14 02:26:30

Re: TWO kernels in one update?

#18 2020-02-14 02:42:36

Re: TWO kernels in one update?

#19 2020-02-14 05:57:43

Re: TWO kernels in one update?

#20 2020-02-14 15:20:31

Re: TWO kernels in one update?

#21 2020-02-14 18:45:17

Re: TWO kernels in one update?

#22 2020-02-16 00:25:00

Re: TWO kernels in one update?

#23 2020-02-16 09:07:02

Re: TWO kernels in one update?

#24 2020-02-17 04:04:52

Re: TWO kernels in one update?

#25 2020-02-17 13:13:16

Re: TWO kernels in one update?

Board footer